This is a tentative template for managing an experimental project via gitHub. The important sections are:
Protocols: collected in protocols folder
Sequences: collected in sequences folder
Project Management Board: see the Projects section on github
Customized templates for the issue tracker
Low-key web site: edit pages in docs folder, access it under https://graik.github.io/wetproject/
Example cards and issues are supposed to show how this can be useful. A more detailed description how the workflow could look like is given here: suggested workflow
Fork this repository (see Fork
Button up right)
Copy the project board -- GitHub help
Menu
(upper right)copy
and chose your new repository as a destinationAdapt the links in this README.md
to point to your new project rather than the template
Issue templates will be copied but Issue labels won't -- re-create the labels manually
A potential problem is that protocols will get spread out over many project repositories. This could be avoided if we either:
... collect protocols in one separate repository that is used by the whole lab (e.g. strube-protocols) and create project-specific repositories only for project management
... or use this template repository as the central protocol repository
... and / or merge any changes in protocols that happen in forked repositories back to this central repository using pull requests. Project boards and issues will not be affected by the merge and will remain separate. Issue templates and the minimal website in docs will be affected though and child repositories could in theory mess up the common templates or website.
For more details see GitHub Flavored Markdown.