Instructions for GitHub for GO: Difference between revisions
Jump to navigation
Jump to search
Line 18: | Line 18: | ||
* '''[https://github.com/geneontology/geneontology.github.io GO website]''' - The GO public presence, '''[http://geneontology.org/ geneontology.org]'''. | * '''[https://github.com/geneontology/geneontology.github.io GO website]''' - The GO public presence, '''[http://geneontology.org/ geneontology.org]'''. | ||
* '''GO-CAM models and Noctua''' | |||
** '''[https://github.com/geneontology/noctua-models noctua-models] - GO-CAM models repository. | |||
** '''[https://github.com/geneontology/noctua Noctua tool]''' - Repo for bug reports and feature requests for the Noctua Graph Editor workbench. | |||
** '''[https://github.com/geneontology/simple-annoton-editor]''' - Repo for bug reports and feature requests for the Noctua Simple Annotation Editor workbench. | |||
** '''[https://github.com/geneontology/neo]] - Repo for bug reports and feature requests for the Noctua entity ontology. | |||
Reasoner (?)=== | |||
noctua-reasoner = minerva | noctua-reasoner = minerva | ||
Revision as of 07:04, 8 April 2019
GitHub account
Main repositories and their scope
- Ontology - Source files for the Gene Ontology.
- Annotation - Annotation queries/issues, disputes, including PAINT disputes.
- GO-site - A collection of metadata, tools, and files associated with the Gene Ontology public web presence.
- AmiGO bugs and feature requests.
- GO website - The GO public presence, geneontology.org.
- GO-CAM models and Noctua
- noctua-models - GO-CAM models repository.
- Noctua tool - Repo for bug reports and feature requests for the Noctua Graph Editor workbench.
- [1] - Repo for bug reports and feature requests for the Noctua Simple Annotation Editor workbench.
- [2]] - Repo for bug reports and feature requests for the Noctua entity ontology.
Reasoner (?)=== noctua-reasoner = minerva
PAINT bugs and feature requests for PAINT
paint (Huaiyu?)
Repo coordinators
Each repo has a coordinator. The responsibilities of the coordinator are to:
- Add assignee(s) to each issue
- Add labels as appropriate
- Follow up
- Propose prioritization for tickets (shared responsibility with product owner, technical lead, PIs, managers, creator of ticket, etc)
Procedure for using the GitHub repositories
- Create issue in the appropriate tracker
- If you want, add label for your group
- Other labels are added by the repo coordinator
Tracking issues
Daily Emails to go-consortium
Automatic emails are sent daily to the go-consortium
mailing list with a list of the new and updated tickets for these two trackers:
- Github Ontology Tracker Update
- Github Annotation Tracker Update
Make sure to look at these emails and comment on tickets that may impact your work as appropriate.