Instructions for GitHub for GO

Main repositories and their scope

• Helpdesk.

• Ontology. Source ontology 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

AmiGO bugs and feature requests.

GO website

GO's public presence, geneontology.org.

GO-CAM models repository

noctua-models

Noctua stack

Bugs/feature requests: noctua

Noctua Simple Annotation Editor workbench

Bugs/feature requests: simple-annoton-editor

Noctua entity ontology

neo

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.