Re: [openstack-dev] Gamification and on-boarding ...
On 2014-02-14 13:48, Russell Bryant wrote: On 02/13/2014 08:53 AM, Sean Dague wrote: The delays on reviews for relatively trivial fixes I think is something that is probably more demotivating to new folks than the lack of badges. So some ability to keep on top of that I think would be really great. Sure, I agree. I still think badges just sound fun. :-) It's at least something that can be automated. Mentoring and such is important, of course, but takes a much bigger time investment from a much bigger group of people. I think we can view improving mentoring and on-boarding as a slightly different but related issue than badges, which could be a fun way to recognize and reward contributions. As an added bonus, if I'm looking for someone who knows about doing $SOMETHING in OpenStack, I could potentially just go look up who has the $SOMETHING badge and ask them. To me it mostly comes down to how much work it ends up being. If it takes a huge effort to make this happen then there are probably better places to spend that effort. But if we can make it happen without a huge investment of time then I think it could be worthwhile. -Ben ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] Gamification and on-boarding ...
On 02/13/2014 08:53 AM, Sean Dague wrote: > The delays on reviews for relatively trivial fixes I think is > something that is probably more demotivating to new folks than the > lack of badges. So some ability to keep on top of that I think > would be really great. Sure, I agree. I still think badges just sound fun. :-) It's at least something that can be automated. Mentoring and such is important, of course, but takes a much bigger time investment from a much bigger group of people. I think we can view improving mentoring and on-boarding as a slightly different but related issue than badges, which could be a fun way to recognize and reward contributions. -- Russell Bryant ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] Gamification and on-boarding ...
+1 Mentoring and devoted mentors and not demotivating new folks (but instead "growing" and fostering them) is IMHO 10x more important than a badge program. Badges seem nice and all but I think it's not the "biggest win for the buck". Sent from my really tiny device... > On Feb 13, 2014, at 6:06 AM, "Sean Dague" wrote: > >> On 02/13/2014 05:37 AM, Thierry Carrez wrote: >> Sandy Walsh wrote: >>> 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. >> >> I think that works if you only keep the ones you can automate. >> "Constructive in IRC" for example sounds a bit subjective to me, and you >> don't want to issue those badges one-by-one manually. >> >> Second thing, you don't want the game to start polluting your bug >> status, i.e. people randomly setting bugs to "triaged" to earn the >> "Triaged a bug" badge. So the badges we keep should be provably useful ;) >> >> A few other suggestions: >> "Found a valid security issue" (to encourage security reports) >> "Fixed a bug submitted by someone else" (to encourage attacking random bugs) >> "Removed code" (to encourage tech debt reduction) >> "Backported a fix to a stable branch" (to encourage backporting) >> "Fixed a bug that was tagged nobody-wants-to-fix-this-one" (to encourage >> people to attack critical / hard bugs) >> >> We might need "protected" tags to automate this: tags that only some >> people could set to bugs/tasks to designate "gate-freeing" or >> "nobody-wants-to-fix-this-one" bugs that will give you badges if you fix >> them. >> >> So overall it's a good idea, but it sounds a bit tricky to automate it >> properly to avoid bad side-effects. > > Gamification is a cool idea, if someone were to implement it, I'd be +1. > > Realistically, the biggest issue I see with on-boarding is mentoring > time. Especially with folks completely new to our structure, there is a > lot of confusing things going on. And OpenStack is a ton to absorb. I > get pinged a lot on IRC, answer when I can, and sometimes just have to > ignore things because there are only so many hours in the day. > > I think Anita has been doing a great job with the Neutron CI onboarding > and new folks, and that's given me perspective on just how many > dedicated mentors we'd need to bring new folks on. With 400 new people > showing up each release, it's a lot of engagement time. It's also > investment in our future, as some of these folks will become solid > contributors and core reviewers. > > So it seems like the only way we'd make real progress here is to get a > chunk of people to devote some dedicated time to mentoring in the next > cycle. Gamification might be most useful, but honestly I expect a "Start > Here" page with the consolidated list of low-hanging-fruit bugs, and a > Review Here page with all reviews for low hanging fruit bugs (so they > don't get lost by core review team) would be a great start. > > The delays on reviews for relatively trivial fixes I think is something > that is probably more demotivating to new folks than the lack of badges. > So some ability to keep on top of that I think would be really great. > >-Sean > > -- > Sean Dague > Samsung Research America > s...@dague.net / sean.da...@samsung.com > http://dague.net > > ___ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] Gamification and on-boarding ...
> From: Sean Dague ... > Realistically, the biggest issue I see with on-boarding is mentoring > time. Especially with folks completely new to our structure, there is a > lot of confusing things going on. And OpenStack is a ton to absorb. I > get pinged a lot on IRC, answer when I can, and sometimes just have to > ignore things because there are only so many hours in the day. A great way to magnify your effort is to write things down where seekers can find it. The documentation is pretty confusing for someone just starting out. I am going through this myself. I just made several updates to the wiki, adding things that newbies need to know (I hope I got them right, and trust someone will speak up if I did not). I also posted a couple of doc bugs for non-wiki issues. Answering questions on mailing lists and ask.openstack.org also leaves a helpful written trail. I just posted a question on the openstack mailing list yesterday, I must be doing something stupid with DevStack, but nobody has answered it and there are several related-looking questions on ask.openstack.org with no answers. Regards, Mike___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] Gamification and on-boarding ...
On Thu, Feb 13, 2014 at 7:53 AM, Sean Dague wrote: > On 02/13/2014 05:37 AM, Thierry Carrez wrote: > > Sandy Walsh wrote: > >> 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. > > > > I think that works if you only keep the ones you can automate. > > "Constructive in IRC" for example sounds a bit subjective to me, and you > > don't want to issue those badges one-by-one manually. > > > > Second thing, you don't want the game to start polluting your bug > > status, i.e. people randomly setting bugs to "triaged" to earn the > > "Triaged a bug" badge. So the badges we keep should be provably useful ;) > > > > A few other suggestions: > > "Found a valid security issue" (to encourage security reports) > > "Fixed a bug submitted by someone else" (to encourage attacking random > bugs) > > "Removed code" (to encourage tech debt reduction) > > "Backported a fix to a stable branch" (to encourage backporting) > > "Fixed a bug that was tagged nobody-wants-to-fix-this-one" (to encourage > > people to attack critical / hard bugs) > > > > We might need "protected" tags to automate this: tags that only some > > people could set to bugs/tasks to designate "gate-freeing" or > > "nobody-wants-to-fix-this-one" bugs that will give you badges if you fix > > them. > > > > So overall it's a good idea, but it sounds a bit tricky to automate it > > properly to avoid bad side-effects. > > Gamification is a cool idea, if someone were to implement it, I'd be +1. > > Realistically, the biggest issue I see with on-boarding is mentoring > time. Especially with folks completely new to our structure, there is a > lot of confusing things going on. And OpenStack is a ton to absorb. I > get pinged a lot on IRC, answer when I can, and sometimes just have to > ignore things because there are only so many hours in the day. > > I think Anita has been doing a great job with the Neutron CI onboarding > and new folks, and that's given me perspective on just how many > dedicated mentors we'd need to bring new folks on. With 400 new people > showing up each release, it's a lot of engagement time. It's also > investment in our future, as some of these folks will become solid > contributors and core reviewers. > > Yep, it's not just docs, wiki pages, well-triaged bugs, badges, but it's mostly people. We need mentors and to treat them like gold! (We do.) Julie Pichon is a great mentor, mentors with the Outreach Program for Women, and is using Open Hatch for this contributor recruiting, onboarding, and retaining. [1] I'd encourage finding ways like this rather than building a badge system. Not that I'd stop you, but I just don't know if a badges.openstack.org is the goal when we can repurpose another site. And when what we really need is mentors. Love that we're all noodling on this. Anne 1 http://openhatch.org/projects/OpenStack%20dashboard%20(Horizon) > So it seems like the only way we'd make real progress here is to get a > chunk of people to devote some dedicated time to mentoring in the next > cycle. Gamification might be most useful, but honestly I expect a "Start > Here" page with the consolidated list of low-hanging-fruit bugs, and a > Review Here page with all reviews for low hanging fruit bugs (so they > don't get lost by core review team) would be a great start. The delays on reviews for relatively trivial fixes I think is something > that is probably more demotivating to new folks than the lack of badges. > So some ability to keep on top of that I think would be really great. > > -Sean > > -- > Sean Dague > Samsung Research America > s...@dague.net / sean.da...@samsung.com > http://dague.net > > > ___ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] Gamification and on-boarding ...
On 14 February 2014 02:53, Sean Dague wrote: > So it seems like the only way we'd make real progress here is to get a > chunk of people to devote some dedicated time to mentoring in the next > cycle. Gamification might be most useful, but honestly I expect a "Start > Here" page with the consolidated list of low-hanging-fruit bugs, and a > Review Here page with all reviews for low hanging fruit bugs (so they > don't get lost by core review team) would be a great start. > > The delays on reviews for relatively trivial fixes I think is something > that is probably more demotivating to new folks than the lack of badges. > So some ability to keep on top of that I think would be really great. +2 -Rob -- Robert Collins Distinguished Technologist HP Converged Cloud ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] Gamification and on-boarding ...
+1, nice idea, it could be really funny. agreed with Thierry's note about automation. On Thu, Feb 13, 2014 at 5:53 PM, Sean Dague wrote: > On 02/13/2014 05:37 AM, Thierry Carrez wrote: > > Sandy Walsh wrote: > >> 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. > > > > I think that works if you only keep the ones you can automate. > > "Constructive in IRC" for example sounds a bit subjective to me, and you > > don't want to issue those badges one-by-one manually. > > > > Second thing, you don't want the game to start polluting your bug > > status, i.e. people randomly setting bugs to "triaged" to earn the > > "Triaged a bug" badge. So the badges we keep should be provably useful ;) > > > > A few other suggestions: > > "Found a valid security issue" (to encourage security reports) > > "Fixed a bug submitted by someone else" (to encourage attacking random > bugs) > > "Removed code" (to encourage tech debt reduction) > > "Backported a fix to a stable branch" (to encourage backporting) > > "Fixed a bug that was tagged nobody-wants-to-fix-this-one" (to encourage > > people to attack critical / hard bugs) > > > > We might need "protected" tags to automate this: tags that only some > > people could set to bugs/tasks to designate "gate-freeing" or > > "nobody-wants-to-fix-this-one" bugs that will give you badges if you fix > > them. > > > > So overall it's a good idea, but it sounds a bit tricky to automate it > > properly to avoid bad side-effects. > > Gamification is a cool idea, if someone were to implement it, I'd be +1. > > Realistically, the biggest issue I see with on-boarding is mentoring > time. Especially with folks completely new to our structure, there is a > lot of confusing things going on. And OpenStack is a ton to absorb. I > get pinged a lot on IRC, answer when I can, and sometimes just have to > ignore things because there are only so many hours in the day. > > I think Anita has been doing a great job with the Neutron CI onboarding > and new folks, and that's given me perspective on just how many > dedicated mentors we'd need to bring new folks on. With 400 new people > showing up each release, it's a lot of engagement time. It's also > investment in our future, as some of these folks will become solid > contributors and core reviewers. > > So it seems like the only way we'd make real progress here is to get a > chunk of people to devote some dedicated time to mentoring in the next > cycle. Gamification might be most useful, but honestly I expect a "Start > Here" page with the consolidated list of low-hanging-fruit bugs, and a > Review Here page with all reviews for low hanging fruit bugs (so they > don't get lost by core review team) would be a great start. > > The delays on reviews for relatively trivial fixes I think is something > that is probably more demotivating to new folks than the lack of badges. > So some ability to keep on top of that I think would be really great. > > -Sean > > -- > Sean Dague > Samsung Research America > s...@dague.net / sean.da...@samsung.com > http://dague.net > > > ___ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > -- Sincerely yours, Sergey Lukjanov Savanna Technical Lead Mirantis Inc. ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] Gamification and on-boarding ...
On 02/13/2014 05:37 AM, Thierry Carrez wrote: > Sandy Walsh wrote: >> 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. > > I think that works if you only keep the ones you can automate. > "Constructive in IRC" for example sounds a bit subjective to me, and you > don't want to issue those badges one-by-one manually. > > Second thing, you don't want the game to start polluting your bug > status, i.e. people randomly setting bugs to "triaged" to earn the > "Triaged a bug" badge. So the badges we keep should be provably useful ;) > > A few other suggestions: > "Found a valid security issue" (to encourage security reports) > "Fixed a bug submitted by someone else" (to encourage attacking random bugs) > "Removed code" (to encourage tech debt reduction) > "Backported a fix to a stable branch" (to encourage backporting) > "Fixed a bug that was tagged nobody-wants-to-fix-this-one" (to encourage > people to attack critical / hard bugs) > > We might need "protected" tags to automate this: tags that only some > people could set to bugs/tasks to designate "gate-freeing" or > "nobody-wants-to-fix-this-one" bugs that will give you badges if you fix > them. > > So overall it's a good idea, but it sounds a bit tricky to automate it > properly to avoid bad side-effects. Gamification is a cool idea, if someone were to implement it, I'd be +1. Realistically, the biggest issue I see with on-boarding is mentoring time. Especially with folks completely new to our structure, there is a lot of confusing things going on. And OpenStack is a ton to absorb. I get pinged a lot on IRC, answer when I can, and sometimes just have to ignore things because there are only so many hours in the day. I think Anita has been doing a great job with the Neutron CI onboarding and new folks, and that's given me perspective on just how many dedicated mentors we'd need to bring new folks on. With 400 new people showing up each release, it's a lot of engagement time. It's also investment in our future, as some of these folks will become solid contributors and core reviewers. So it seems like the only way we'd make real progress here is to get a chunk of people to devote some dedicated time to mentoring in the next cycle. Gamification might be most useful, but honestly I expect a "Start Here" page with the consolidated list of low-hanging-fruit bugs, and a Review Here page with all reviews for low hanging fruit bugs (so they don't get lost by core review team) would be a great start. The delays on reviews for relatively trivial fixes I think is something that is probably more demotivating to new folks than the lack of badges. So some ability to keep on top of that I think would be really great. -Sean -- Sean Dague Samsung Research America s...@dague.net / sean.da...@samsung.com http://dague.net signature.asc Description: OpenPGP digital signature ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] Gamification and on-boarding ...
Sandy Walsh wrote: > 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. I think that works if you only keep the ones you can automate. "Constructive in IRC" for example sounds a bit subjective to me, and you don't want to issue those badges one-by-one manually. Second thing, you don't want the game to start polluting your bug status, i.e. people randomly setting bugs to "triaged" to earn the "Triaged a bug" badge. So the badges we keep should be provably useful ;) A few other suggestions: "Found a valid security issue" (to encourage security reports) "Fixed a bug submitted by someone else" (to encourage attacking random bugs) "Removed code" (to encourage tech debt reduction) "Backported a fix to a stable branch" (to encourage backporting) "Fixed a bug that was tagged nobody-wants-to-fix-this-one" (to encourage people to attack critical / hard bugs) We might need "protected" tags to automate this: tags that only some people could set to bugs/tasks to designate "gate-freeing" or "nobody-wants-to-fix-this-one" bugs that will give you badges if you fix them. So overall it's a good idea, but it sounds a bit tricky to automate it properly to avoid bad side-effects. -- Thierry Carrez (ttx) ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] Gamification and on-boarding ...
+1 to Rohit. I am new too and looking forward to help in cinder part of OpenStack for starters. On Thu, Feb 13, 2014 at 12:36 PM, Rohit Vaidya wrote: > I am new to open stack and python. But I really liked the live community > here and great suggestions that crop up. This one is seriously good and > helps new people stay motivated. I installed dev stack on my sluggish > laptop and that's all. Could not move any further. Looking forward to > taking the next step. Keep up with the good work people. > > Regards, > Rohit Vaidya > > On Thu, Feb 13, 2014 at 12:14 PM, wu jiang wrote: > >> +1. This looks very interesting. :) >> >> >> On Thu, Feb 13, 2014 at 2:09 PM, Russell Bryant wrote: >> >>> On 02/12/2014 11:35 AM, Ben Nemec wrote: >>> > On 2014-02-12 12:00, Sandy Walsh wrote: >>> >> 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 >>> >> >>> >> [1] http://en.wikipedia.org/wiki/Gamification >>> >> [2] http://gamify.com/ (and many others) >>> >> [3] https://badges.fedoraproject.org/ >>> > >>> > +1 from me, if this can be done without a huge amount of ongoing >>> > maintenance for someone. I will admit that climbing the reviewstats >>> > "leaderboard" is good motivation for those days when I just don't feel >>> > like reviewing. Ditto for Launchpad karma. :-) >>> >>> I really like the badges idea. It sounds like a really fun way to >>> encourage folks. It's a refreshing alternative to just looking at raw >>> numbers all the time. >>> >>> -- >>> Russell Bryant >>> >>> ___ >>> OpenStack-dev mailing list >>> OpenStack-dev@lists.openstack.org >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >>> >> >> >> ___ >> OpenStack-dev mailing list >> OpenStack-dev@lists.openstack.org >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> >> > > > ___ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > -- Thanks, Ibad Khan 9686594607 ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] Gamification and on-boarding ...
I am new to open stack and python. But I really liked the live community here and great suggestions that crop up. This one is seriously good and helps new people stay motivated. I installed dev stack on my sluggish laptop and that's all. Could not move any further. Looking forward to taking the next step. Keep up with the good work people. Regards, Rohit Vaidya On Thu, Feb 13, 2014 at 12:14 PM, wu jiang wrote: > +1. This looks very interesting. :) > > > On Thu, Feb 13, 2014 at 2:09 PM, Russell Bryant wrote: > >> On 02/12/2014 11:35 AM, Ben Nemec wrote: >> > On 2014-02-12 12:00, Sandy Walsh wrote: >> >> 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 >> >> >> >> [1] http://en.wikipedia.org/wiki/Gamification >> >> [2] http://gamify.com/ (and many others) >> >> [3] https://badges.fedoraproject.org/ >> > >> > +1 from me, if this can be done without a huge amount of ongoing >> > maintenance for someone. I will admit that climbing the reviewstats >> > "leaderboard" is good motivation for those days when I just don't feel >> > like reviewing. Ditto for Launchpad karma. :-) >> >> I really like the badges idea. It sounds like a really fun way to >> encourage folks. It's a refreshing alternative to just looking at raw >> numbers all the time. >> >> -- >> Russell Bryant >> >> ___ >> OpenStack-dev mailing list >> OpenStack-dev@lists.openstack.org >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> > > > ___ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] Gamification and on-boarding ...
+1. This looks very interesting. :) On Thu, Feb 13, 2014 at 2:09 PM, Russell Bryant wrote: > On 02/12/2014 11:35 AM, Ben Nemec wrote: > > On 2014-02-12 12:00, Sandy Walsh wrote: > >> 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 > >> > >> [1] http://en.wikipedia.org/wiki/Gamification > >> [2] http://gamify.com/ (and many others) > >> [3] https://badges.fedoraproject.org/ > > > > +1 from me, if this can be done without a huge amount of ongoing > > maintenance for someone. I will admit that climbing the reviewstats > > "leaderboard" is good motivation for those days when I just don't feel > > like reviewing. Ditto for Launchpad karma. :-) > > I really like the badges idea. It sounds like a really fun way to > encourage folks. It's a refreshing alternative to just looking at raw > numbers all the time. > > -- > Russell Bryant > > ___ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] Gamification and on-boarding ...
On 02/12/2014 11:35 AM, Ben Nemec wrote: > On 2014-02-12 12:00, Sandy Walsh wrote: >> 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 >> >> [1] http://en.wikipedia.org/wiki/Gamification >> [2] http://gamify.com/ (and many others) >> [3] https://badges.fedoraproject.org/ > > +1 from me, if this can be done without a huge amount of ongoing > maintenance for someone. I will admit that climbing the reviewstats > "leaderboard" is good motivation for those days when I just don't feel > like reviewing. Ditto for Launchpad karma. :-) I really like the badges idea. It sounds like a really fun way to encourage folks. It's a refreshing alternative to just looking at raw numbers all the time. -- Russell Bryant ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] Gamification and on-boarding ...
On 2014-02-12 12:00, Sandy Walsh wrote: 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 [1] http://en.wikipedia.org/wiki/Gamification [2] http://gamify.com/ (and many others) [3] https://badges.fedoraproject.org/ +1 from me, if this can be done without a huge amount of ongoing maintenance for someone. I will admit that climbing the reviewstats "leaderboard" is good motivation for those days when I just don't feel like reviewing. Ditto for Launchpad karma. :-) -Ben ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] Gamification and on-boarding ...
I¹m kind of new in Openstack. +1 to this On 12/02/14 15:00, "Sandy Walsh" wrote: >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 > >[1] http://en.wikipedia.org/wiki/Gamification >[2] http://gamify.com/ (and many others) >[3] https://badges.fedoraproject.org/ > >___ >OpenStack-dev mailing list >OpenStack-dev@lists.openstack.org >http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
