github user strategy

[MKLau]

1. each project has a repo
2. each repo has a notebook (available for inspection at all times, and see article in PLoS below)
3. issues help develop ideas-questions-additions to projects
4. issues can be referred to by both name and number
5. issues must be annotated before they are closed
6. all project coordinators should be on github and subscribe to all project repos
7. use projects and organizations

[MKLau]

• http://www.ploscompbiol.org/article/info%3Adoi%2F10.1371%2Fjournal.pcbi.1000424
• http://www.normalesup.org/~vorgogoz/BioInfoCourses/40-Yannick-Wurm-tips.pdf
• http://arxiv.org/pdf/1210.0530v4.pdf