| 76 | | * Github Repo |
| 77 | | * IRC Handle |
| 78 | | * LinkedIn Profile |
| 79 | | * Tasks Logged |
| 80 | | * Tasks Resolved |
| 81 | | * Comments |
| 82 | | * Links to trunk contributors |
| 83 | | * Links to messages on mailing list |
| 84 | | * Irc Messages in Channel?() |
| 85 | | * Wiki updates |
| 86 | | * What access people have (Sunflower Admin, Mailing List Admin, Has CI Server Access, Facebook, Twitter...) |
| 87 | | * What groups/teams people belong to (eg. Board, GSoC Mentors, GCI Student...) |
| 88 | | * Summary of the contributions |
| 89 | | |
| | 80 | * Contact Details: |
| | 81 | * Github Repo |
| | 82 | * IRC Handle |
| | 83 | * LinkedIn Profile |
| | 84 | * Phone No. |
| | 85 | * Skype |
| 116 | | * Subscription of tasks - |
| 117 | | * Using teams - |
| 118 | | * Tasks can be assigned to some team (Eg - "A-team" for automated testing team). |
| 119 | | * All people that belong to this team are subscribed to receive updates about these tasks. |
| 120 | | * The people can update their subscription, filtering the tasks and frequency of updates. |
| 121 | | * Marking as "I'm Interested" |
| 122 | | * A person can mark himself/herself as interested in the task. |
| 123 | | * All the people interested in the task are visible to all, so that one may wish to contact any of them for exchanging ideas, etc. |
| 124 | | * All the people interested get updates of the task using the subscriptions. |
| 125 | | |
| 126 | | * Settings to have new tasks automatically assigned to specific teams. |
| 137 | | |
| 138 | | ==== Points ==== |
| 139 | | There have been suggestions that we determine a way in which to recognise top contributors - one way of doing this would be to give people "Points" (Sunflower seeds?) for completing tasks. This could work something like: |
| 140 | | * All contributors can vote on the number of points a task is worth (0-5). The value of the task is the average of those votes. If there are no votes, a task gets 1 point. |
| 141 | | * Tasks are often assigned value by the person who creates them. I think that's a good way to establish not just their difficulty but also their priority level. Additionally, it would be nice if the person who completes the task also indicates the amount of time they put into that task. Both factors could be recorded to create more useful information about community contributors and their contributions. |
| 142 | | * When a task is completed, the contributors that the task is assigned to gets the average value of their votes (although their own vote is ignored) |
| 143 | | * On the homepage the top contributors based on points accumulated over the past month are displayed |
| 144 | | * We can also keep historic point talleys over time |
| 145 | | * I think it's useful to think about the types of rewards that could be offered to people with lots of points. |
| 146 | | * I also think this would be a good reason to incorporaespeciallyte badges into EDEN, specifically http://openbadges.org/ which could be used as a reward mechanism as well as a way to share information about people's skills and experiences. |
| 147 | | |
| 148 | | ==== Github Integration ==== |
| 149 | | * Tag tasks in Github comments log and have add comments in Sunflower |
| | 290 | |
| | 291 | === Personal Profiles === |
| | 292 | |
| | 293 | A personal profile should record: |
| | 294 | |
| | 295 | * Tasks Logged |
| | 296 | * Tasks Resolved |
| | 297 | * Comments?() |
| | 298 | * Links to trunk contributors |
| | 299 | * Links to messages on mailing list |
| | 300 | * Irc Messages in Channel?() |
| | 301 | * Wiki updates |
| | 302 | * What access people have (Sunflower Admin, Mailing List Admin, Has CI Server Access, Facebook, Twitter...) |
| | 303 | * What groups/teams people belong to (eg. Board, GSoC Mentors, GCI Student...) |
| | 304 | * Summary of the contributions |
| | 305 | |
| 337 | | * Ability to mark yourselve as "interested" in a task |
| | 325 | * Subscription of tasks - |
| | 326 | * Using teams - |
| | 327 | * Tasks can be assigned to some team (Eg - "A-team" for automated testing team). |
| | 328 | * All people that belong to this team are subscribed to receive updates about these tasks. |
| | 329 | * The people can update their subscription, filtering the tasks and frequency of updates. |
| | 330 | * Marking as "I'm Interested" |
| | 331 | * A person can mark himself/herself as interested in the task. |
| | 332 | * All the people interested in the task are visible to all, so that one may wish to contact any of them for exchanging ideas, etc. |
| | 333 | * All the people interested get updates of the task using the subscriptions. |
| | 334 | * Settings to have new tasks automatically assigned to specific teams. |
| | 335 | * Filter lists for different users. |
| | 374 | === Points === |
| | 375 | There have been suggestions that we determine a way in which to recognise top contributors - one way of doing this would be to give people "Points" (Sunflower seeds?) for completing tasks. This could work something like: |
| | 376 | * All contributors can vote on the number of points a task is worth (0-5). The value of the task is the average of those votes. If there are no votes, a task gets 1 point. |
| | 377 | * Tasks are often assigned value by the person who creates them. I think that's a good way to establish not just their difficulty but also their priority level. Additionally, it would be nice if the person who completes the task also indicates the amount of time they put into that task. Both factors could be recorded to create more useful information about community contributors and their contributions. |
| | 378 | * When a task is completed, the contributors that the task is assigned to gets the average value of their votes (although their own vote is ignored) |
| | 379 | * On the homepage the top contributors based on points accumulated over the past month are displayed |
| | 380 | * We can also keep historic point talleys over time |
| | 381 | * I think it's useful to think about the types of rewards that could be offered to people with lots of points. |
| | 382 | * I also think this would be a good reason to incorporaespeciallyte badges into EDEN, specifically http://openbadges.org/ which could be used as a reward mechanism as well as a way to share information about people's skills and experiences. |
| | 383 | |
| | 384 | === Github Integration === |
| | 385 | * Tag tasks in Github comments log and have add comments in Sunflower |
| | 386 | |
