Posted by mradcliffe on April 10, 2011 at 1:21am
One of the initial release objectives is to have some sort of point tracking. StackExchange's reputation system is explained here.
Questions
- Maximum point value?
- Track points by category (code, site-building, etc...)?
- Anything else?
Here's a template to use (add your own new exciting things to this):
trigger | action
------------ | ----------
answer is voted up | +10
question is voted up | +5
answer is accepted | +15 (+2 to acceptor)
post is voted down | -2 (-1 to voter)
gain 15 points | vote up privilege granted
gain 15 points | flag question / answer / comment privilege grantedHere's how it looks:
| trigger | action |
|---|---|
| answer is voted up | +10 |
| question is voted up | +5 |
| answer is accepted | +15 (+2 to acceptor) |
| post is voted down | -2 (-1 to voter) |
| gain 15 points | vote up privilege granted |
| gain 15 points | flag question / answer / comment privilege granted |
Comments
Can we start up this
Can we start up this discussion again? I'd like to be educated on the subject of points versus achievements (trophies/whatever).
Some things to consider:
Assumptions are my own; feel free to state your own.
My two bits ...
From what I've understood, it seems like there are maybe three major goals community point/badge systems pursue:
The major traps seem to be:
All in all, I think StackExchange does a decent job at all of this.
As far as I've understood them, the key ideas it has pursued are:
All in all, it seems a decent approach to motivating people to contribute, inculculating a positive atmosphere, while making it approachable for anybody to use the support system.
Excellent insight,
Excellent insight, @chipclearly.
There are some things I don't agree with StackExchange, though:
1. You can't downvote comments, just "flag" it as unconstructive/spam.
2. Comments aren't threaded.
3. Comments aren't important enough.
Well, downvoted comments would go down, and would eventually fade completely as people downvote them. This would distribute the power a little more, and actually make people think a little more before commenting crap.
and 3. In my opinion, no solution is perfect for any problem, and this is especially true in a vast area like Drupal. I'm only content with a solution when I am aware of its drawbacks and extra information about it. That's why the comments are almost as important as the answer itself (at least for me).
By making comments threaded, we are incentivating people not only to improve the answer, but also making parallel statements and conclusions on the things that surround the answer, still in the scope of the answer.
@chipclearly++. Very well
@chipclearly++. Very well explained.
@Fidelix : I think answers are more important than comments in a Q&A system. If they're made (almost) equal then we have a forum, not a Q&A system, even if I got you about parallel statements. But focusing in answering questions is at the heart of a Q&A system. As @chipclearly said, having comments ~= answers is "Creating a system where long debates readily become the focus instead of setting on a decent answer quickly". The solution could be to create an issue if necessary in the proper place, but I'm not sure about it.