Curated First Tasks

Context & Process

Our “Open Source Comes to Campus” events rely heavily on students attempting to fix real bugs in active open source projects. As such, it's important for us to identify a large number of good "bite-size" bugs that students can work on. Past experience has taught us that an appropriate list of bugs can not be generated at the last minute, but rather needs to be curated over the weeks leading up to an event.

Our intention is to create a list of open source projects which we will work with to collect good beginner bugs for our events. Where possible, we will:

• email maintainers and/or the broader community to announce our intentions
• create an Open Hatch account in that project's bug tracker which can claim and/or be assigned bite sized bugs
• assign ourselves bugs, for which we will provide a release-by date (never longer than four months, but usually not shorter than two weeks, from assignment)

We are happy to work with project communities to make sure we are not taking too many bugs or in any way impeding development. We also wish to stress that, for any individual bugs, members of the community would be welcome to say, "Actually, I would like to claim this one" or "If you can't have this done by X data, please release it."

Bug List

These are hand-picked bugs we intend to use at Open Source Comes to Campus events. If this goes well, we will work on merging the current automatic import process of the volunteer opportunity finder with this manually-curated list.