In case it helps, here’s a rough list of the thoughts that have come to mind:
Simplicity is usually best with voting systems. It may be worth looking at a reddit style up/down system for popularity. With importance you probably want high/mid/low. If you track the ‘importance profile’ of a user, you could use that to promote projects to their attention that other users with similar profiles find important. Also, in all these rankings it should be clear to the user exactly what metric is being used.
Make use of the wisdom of crowds by getting users to evaluate projects/tasks/comments for things like difficulty, relevance, utility, marginal utility—along the lines of this xkcd comic.
It seems to me that good open source management tool should direct attention to the right places. Having inbuilt problem flags that users can activate to have the problem brought to the attention of someone who can solve it seems like a good idea.
Skill matching. Have detailed skill profiles for users and have required skills flagged up for tasks.
Could try breaking projects up into a set of tasks, sub-tasks and next actions a-la Getting Things Done
Duolingo provides free language courses. They plan to make this financially viable by crowd sourcing translations from their students. Perhaps a similar thing could be implemented—maybe by getting university students involved.
Gamification across a broad range of possible tasks. Give points for things like participation, research, providing information. While rewarding programmers for coding is good, we should seek to reward anything that lowers the activation energy of a task for someone else.
Keep a portfolio of work that each user has completed in a format that is easy for them to access, customize and print out and reference in job applications.
Encourage networking between users with similar skills, areas of interest and the like. This would provide a benefit to being part of the community.
You could have a Patreon like pledging system where people pledge a small amount to projects they consider important. When the project reaches a milestone the contributors then get rewarded a portion of the pledge.
Duolingo provides free language courses. They make this financially viable by crowd sourcing translations from their students. Perhaps a similar thing could be implemented—maybe by getting university students involved.
Duolingo doesn’t make profits. It’s investors believe in it, but it still to early to say that it’s really financially viable.
Good advice. Since I wanted a lot of things to be weighted when determining the search order, I considered just hiding all the complexity ‘under the hood’. But if people don’t know what they are voting on they might be less inclined to vote at all.
Since I wanted a lot of things to be weighted when determining the search order, I considered just hiding all the complexity ‘under the hood’.
The way I view it, search rankings are a tool like any other. In my own experience in academic research I’ve always found that clearly defined search rankings are more useful to me than generic rankings; if you know how the tool works, it’s easier to use correctly. That said, there’s probably still a place for a complex algorithm alongside other search tools, it just shouldn’t be the only search tool.
But if people don’t know what they are voting on they might be less inclined to vote at all.
Well I think it’s more a matter of efficiently extracting information from users. Consider the LessWrong karma system, while it serves its purpose of filtering out spam, its a very noisy indicator of anything other than ‘people thought this comment should get karma’. This is because some users think that we should vote things up or down based on different criteria, such as: do I agree with this comment?; did this comment contain valuable information for me?; was this an amusing comment?; was this comment well reasoned?; and so on.
By clearly defining the voting criteria, you’re not just making users more likely to vote, you’re also more efficiently extracting information out of them. From a user perspective this can be really useful, knowing that a particular rating is the popularity or the importance of a project, they can then choose whether they want to pay attention to or ignore that metric.
In case it helps, here’s a rough list of the thoughts that have come to mind:
Simplicity is usually best with voting systems. It may be worth looking at a reddit style up/down system for popularity. With importance you probably want high/mid/low. If you track the ‘importance profile’ of a user, you could use that to promote projects to their attention that other users with similar profiles find important. Also, in all these rankings it should be clear to the user exactly what metric is being used.
Make use of the wisdom of crowds by getting users to evaluate projects/tasks/comments for things like difficulty, relevance, utility, marginal utility—along the lines of this xkcd comic.
It seems to me that good open source management tool should direct attention to the right places. Having inbuilt problem flags that users can activate to have the problem brought to the attention of someone who can solve it seems like a good idea.
Skill matching. Have detailed skill profiles for users and have required skills flagged up for tasks.
Could try breaking projects up into a set of tasks, sub-tasks and next actions a-la Getting Things Done
Duolingo provides free language courses. They plan to make this financially viable by crowd sourcing translations from their students. Perhaps a similar thing could be implemented—maybe by getting university students involved.
Gamification across a broad range of possible tasks. Give points for things like participation, research, providing information. While rewarding programmers for coding is good, we should seek to reward anything that lowers the activation energy of a task for someone else.
Keep a portfolio of work that each user has completed in a format that is easy for them to access, customize and print out and reference in job applications.
Encourage networking between users with similar skills, areas of interest and the like. This would provide a benefit to being part of the community.
You could have a Patreon like pledging system where people pledge a small amount to projects they consider important. When the project reaches a milestone the contributors then get rewarded a portion of the pledge.
Duolingo doesn’t make profits. It’s investors believe in it, but it still to early to say that it’s really financially viable.
Thanks. I’ve edited the comment to reflect this better.
Good advice. Since I wanted a lot of things to be weighted when determining the search order, I considered just hiding all the complexity ‘under the hood’. But if people don’t know what they are voting on they might be less inclined to vote at all.
The way I view it, search rankings are a tool like any other. In my own experience in academic research I’ve always found that clearly defined search rankings are more useful to me than generic rankings; if you know how the tool works, it’s easier to use correctly. That said, there’s probably still a place for a complex algorithm alongside other search tools, it just shouldn’t be the only search tool.
Well I think it’s more a matter of efficiently extracting information from users. Consider the LessWrong karma system, while it serves its purpose of filtering out spam, its a very noisy indicator of anything other than ‘people thought this comment should get karma’. This is because some users think that we should vote things up or down based on different criteria, such as: do I agree with this comment?; did this comment contain valuable information for me?; was this an amusing comment?; was this comment well reasoned?; and so on.
By clearly defining the voting criteria, you’re not just making users more likely to vote, you’re also more efficiently extracting information out of them. From a user perspective this can be really useful, knowing that a particular rating is the popularity or the importance of a project, they can then choose whether they want to pay attention to or ignore that metric.