@floriang@McPizza These are the type of massive code changes I'd like to avoid 😅
Anything requiring separating the website into two parts, or adding a separate user type with different privileges would complicated a lot of the code.
I don't mind adding some complexity in a specific area, but if it's something so fundamental, it tends to slow down all product development going forward.
I prefer a solution that's more isolated.
Maybe one of the application questions could be "pick a question from the forum and answer it in a helpful way". And we'd save that answer not as a regular answer, but simply as part of the application. We'd then also link it to the original question and notify the author of that and get their vote on whether the answer was helpful or not.
Something like this would still allow applicants to demonstrate their value-add, without requiring structural changes throughout the code.
I'm curious if we can come up with more ideas like this or fine-tune the one I mentioned?
@floriang @McPizza These are the type of massive code changes I'd like to avoid 😅
Anything requiring separating the website into two parts, or adding a separate user type with different privileges would complicated a lot of the code.
I don't mind adding some complexity in a specific area, but if it's something so fundamental, it tends to slow down all product development going forward.
I prefer a solution that's more isolated.
Maybe one of the application questions could be "pick a question from the forum and answer it in a helpful way". And we'd save that answer not as a regular answer, but simply as part of the application. We'd then also link it to the original question and notify the author of that and get their vote on whether the answer was helpful or not.
Something like this would still allow applicants to demonstrate their value-add, without requiring structural changes throughout the code.
I'm curious if we can come up with more ideas like this or fine-tune the one I mentioned?