Curated First Tasks: Difference between revisions
imported>Shauna (Created page with "__toc__ ===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, i...") |
imported>Shauna No edit summary |
||
| Line 3: | Line 3: | ||
===Context & Process=== |
===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 “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 [https://openhatch.org/wiki/Curated_First_Tasks#What_makes_for_a_good_bug.3F 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: |
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: |
||
Revision as of 23:05, 4 January 2013
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
We wish to stress that for any individual bugs, members of the community are more than welcome to say:
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.