Instructions for GitHub for GO

From GO Wiki
Jump to: navigation, search


Main repositories and their scope

  • Helpdesk. For general questions about GO, or if you are unsure which repo to submit a ticket to.
  • 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 for the AmiGO GO browser.
  • GO-CAM models and Noctua
    • noctua-models - GO-CAM models repository.
    • noctua - Repo for bug reports and feature requests for the Noctua Graph Editor workbench.
    • simple-annoton-editor - Repo for bug reports and feature requests for the Noctua Simple Annotation Editor workbench.
    • neo - Repo for bug reports and feature requests for the Noctua entity ontology.

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.

For operating on resource metadata on go-site, we have started a more specialized guide here.

Tracking issues

When you are added as a member of the GO GitHub project, you automatically follow a number of repositories (different ones, depending on your role). By default, emails will be sent for all new and updated tickets. You can reduce this by going to the individual repo, and clicking on the 'eye' icon at the top right of the screen. Options are:

  • Not watching: Be notified only when participating (ie when you comment on a ticket or manually watch it) or @mentioned. This is the optimal option to get relevant information.
  • Releases only: Be notified of new releases, and when participating or @mentioned.
  • Watching: Be notified of all notifications
  • Ignoring: Never be notified

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.

GO Projects

  • Within GitHub, group of related tasks are organized into Projects.
  • Projects may be associated with the top-level repository or with individual repositories (see the 'Projects' tab within each repo, for example Ontology Projects).
  • Projects may represent a task with a specific goal (for example, the conversion of Reactome data into GO-CAM models), or an ongoing project (such as ontology development). In this case, projects are used to keep track of progress from one milestone to the next.
  • Milestones usually correspond to GO Consortium meetings.

Product Owner and Technical lead

Each ongoing project has two key participants: the Product Owner and Technical lead.

  • The Product Owner is responsible to provide user specifications for the project, and approve work done for public deployment.
  • The Technical lead is responsible to propose technical solutions to implement the specifications, and to supervise the technical tasks.
  • The Product Owner and Technical lead work together to agree on the scope of a project.

Review Status

Last reviewed: April 11, 2019