Overview
Provide a model of reputation system for d.o which will expose a wide range of contributions of community members. Not only direct contributions via commits but contributions in forms of other activities: documentation, support, UX, design etc. Provide a model for exposing member's field of expertise. Define ways to show that community value non-code contributions as well as code ones, encouraging more non-code contributions.
Description
The original idea is floating around community for some time already. Particularly it is being discussed within ongoing Prairie initiative. Main goals of which are:
- Improve the collaboration tools on Drupal.org so that we can do more and better work together and make Drupal better, faster.
- Grow the pool of contributors by making Drupal.org a better and easier place to become a contributor - to make it less intimidating to people who want to get started contributing.
Problems:
- For many of possible non-code contributors it is not clear that they can actually contribute to Drupal and how can they do it.
- Currently the only contribution which being measured and shown - code commits. Which leaves outside lots of people contributing in forms of documentation, UX reviews, patch reviews, providing support via forums and irc etc.
- The "tools" for contributors are currently being more focused/prepared for code contributions, which is not helping to encourage other types of contributions into community
The idea of this project is to suggest a model of expertise/reputation system which will cover all the different types of contribution (including non-code ones), show the value of non-code contributions, encourage more non-code contributions, encourage more possible contributors to start actually contributing.
The project has 3 goals:
- Define a model of exposing person's field of expertise and skill set. Based on person's field of expertise, provide him/her with information on how he/she can contribute;
- Define a way to acknowledge contributions
This includes ways to:
1. Capture
2. Measure
3. Display
wide range of contributions.Contributions include:
- code commits
- reviewed and tested patches
- documentation
- UX reviews
- graphic design
- participating in marketing activity
- translations
- support via forums, irc (and supposedly new support.drupal.org)
- other (to be defined in process). - Define basic types of non-code contributors and suggest improvements for tools they use for their contributions.
Schedule
May 23 - June 5 Work on the first part of the project
- May 23 - May 29 Research examples of expertise exposure on various community websites including other open source projects, Q&A sites, social networks etc. Research of existing opinions on the topic within Drupal community.
- May 30 - April 5 Defining ways how to insert expertise info into user profile. How and where to display this info, how to match existing activity in community with user expertise and provide him with information on possible ways of his contribution. Preparing wireframes for affected pages.
June 6 - August 15 Work on the second and third parts of the project
- June 6 - June 19 Research the ways contributions being measured/displayed on various community websites including other open-source projects, Q&A sites etc. Investigating existing reputation systems, used on various community websites.
- June 20 - July 10 Community research of what types of contributions need to be included into system, defining basic types of contributors to Drupal, defining the way they contribute, defining their needs for tools for their contribution.
- July 11 Submit mid term evaluation
- July 11 - August 14 Defining how each type of contribution can be captured and measured. Defining how and where to display reputation. Defining how to improve current tools of collaboration for non-code contributors. Preparing wireframes of all the affected parts of d.o, g.d.o etc.
August 15 - August 22 Preparing final report, posting project results including wireframes on d.o
August 22 Submit final evaluation
Mentor : Leisa Reichelt