Anonymous user
Curated First Tasks: Difference between revisions
→What makes for a good bug?
imported>Paulproteus |
imported>Paulproteus |
||
Line 37:
=== What makes for a good bug? ===
Keep these things in mind when choosing tasks:
* The typical attendee has 1-2 semesters of programming background (naturally this depends on the year they are, and the program they are in, and their programming experiences outside of college).
* We aim that someone experienced with the code should be able to fix it within 15-30 minutes, including any work required to isolate the issue.
* Students who attend are probably using git (and version control in general) for the first time, and will probably spend a substantial amount of time cleaning up their patch before submitting, and discussing good commit log messages with mentors at the event.
* Documentation bugs are totally germane, so long as the documentation issue doesn't require an extremely deep understanding of the project or code.
To get a sense of good tasks from past events:
* https://redmine.open-bio.org/issues/3340 (see further discussion at http://lists.open-bio.org/pipermail/biopython-dev/2012-September/009958.html )
(We'll add more over time.)
| |||