+1 from me I think one thing that would help for bug fixes is to have labels for them to help developers quickly identify where they can help. I heard there are lots of bugs that are easy to fix for new developers. I tried finding them because I want to help, but I found it difficult for me to identify bugs. It would be nice to have an easy way to find bugs that a newcomer can fix.
What are the expectations for code reviews as well? It's a little intimidating for a newbie to do a code review. I can review for easy things like spacing, comments, etc., but I don't know if I should give a +1 because I don't always have the big architecture picture. It's even more intimidating to give a -1. I'm not sure what constitutes a -1. I don't want to seem like I'm nitpicking. -Nate > At the Nova mid-cycle meetup we've been talking about the problem of helping > new contributors. It got into a discussion of karma, code reviews, bug fixes > and establishing a name for yourself before screaming in a chat room "can > someone look at my branch". We want this experience to be positive, but not > everyone has time to hand-hold new people in the dance. > > The informal OpenStack motto is "automate everything", so perhaps we should > consider some form of gamification [1] to help us? Can we offer badges, quests > and challenges to new users to lead them on the way to being strong > contributors? > > "Fixed your first bug" badge > "Updated the docs" badge > "Got your blueprint approved" badge > "Triaged a bug" badge > "Reviewed a branch" badge > "Contributed to 3 OpenStack projects" badge > "Fixed a Cells bug" badge > "Constructive in IRC" badge > "Freed the gate" badge > "Reverted branch from a core" badge > etc. > > These can be strung together as Quests to lead people along the path. It's > more > than karma and less sterile than stackalytics. The Foundation could even > promote the rising stars and highlight the leader board. > > There are gamification-as-a-service offerings out there [2] as well as Fedora > Badges [3] (python and open source) that we may want to consider. > > Thoughts? > -Sandy _______________________________________________ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack