Reclama: Difference between revisions

← Older edit

Reclama (view source)

Revision as of 14:18, 30 June 2015

1,454 bytes added , 30 June 2015

Usage of the bugs sprints tool

Kinger

Confirmed users

887

edits

@@ Line 28: / Line 28: @@
 * Code can be found here [https://github.com/mozilla/navras github.com/mozilla/reclama]
 * Bugs and issues can be found in our [https://github.com/mozilla/reclama/issues issues]
+== Usage ==
+If you want to have a Bug Sprint event setup for your event, the following steps need to be taken:
+* Gather the list of bugs that you want to work with. This should involve outreach to engineering teams at Mozilla, who would like contributions to their bugs. The general guidelines (not all need to be met) for choosing bugs are:
+** Good first bugs
+** Bugs that have good impact on the project
+** Developers can work unsupervised
+** Bonus points if setting up the environment for working on the bugs is not too complicated and is well documented
+* Ask the team providing the bugs to have someone on call during the event to monitor the bugs for developers that comment and ask questions in Bugzilla.
+* Contact [[Participation|Brian or Pierros]] on the Participation team to setup the event for you and populate it with the bugs you want added, and the incentives you many have for getting bugs fixed.
+* Setup a Discourse thread for the sprint, to monitor for support during the event. [https://discourse.mozilla-community.org/t/fosdem-2015-bug-sprint/1529 Here is an example]. Use the Reps Events category. Monitor the thread during the event and try to give prompt answers.
+* Work on a followup strategy for bugs that have been worked on during the event. This could include things like:
+** Ensuring momentum on bugs started during the event, e.g. encouragement, making connections, code review, and so on.
+** Recognition of contributors
 == Contact ==
 See the [[Participation/Infrastructure|Participation Infrastructure]] group for more details.