New member onboarding: Difference between revisions

From GO Wiki
Jump to navigation Jump to search
(12 intermediate revisions by 2 users not shown)
Line 26: Line 26:
=All new members: joining the GO project=
=All new members: joining the GO project=
* Go over the '''[[Background reading on Ontologies, the Gene Ontology and Annotation]].'''
* Go over the '''[[Background reading on Ontologies, the Gene Ontology and Annotation]].'''
* Register to the project at '''[https://github.com/geneontology/helpdesk/issues/new?assignees=&labels=&template=new-member-onboarding.md&title=New+User+Onboarding New User Onboarding]'''
==Checklist for all Gene Ontology Consortium Members and Contributors==
==Checklist for all Gene Ontology Consortium Members and Contributors==
#'''[http://wiki.geneontology.org/index.php/Special:CreateAccount Create a GO wiki account]'''
#'''[http://wiki.geneontology.org/index.php/Special:CreateAccount Create a GO wiki account]'''
Line 35: Line 36:
#*'''Be added to the [https://calendar.google.com/calendar?cid=Z2VuZW9udG9sb2d5QGdtYWlsLmNvbQ GO Google calendar],''' so you can view conference call information
#*'''Be added to the [https://calendar.google.com/calendar?cid=Z2VuZW9udG9sb2d5QGdtYWlsLmNvbQ GO Google calendar],''' so you can view conference call information
#*'''Be added to [https://github.com/geneontology/go-site/blob/master/metadata/group-contacts.csv Group contacts]:''' Please provide your expertise (1-3 keywords)  
#*'''Be added to [https://github.com/geneontology/go-site/blob/master/metadata/group-contacts.csv Group contacts]:''' Please provide your expertise (1-3 keywords)  
#*'''Be added to [https://github.com/geneontology/go-site/blob/master/metadata/users.yaml Users]:''' Please provide your ORCID, the name of your organization, and [https://github.com/geneontology/go-site/blob/master/metadata/groups.yaml group].
#*'''Be added to [https://github.com/geneontology/go-site/blob/master/metadata/users.yaml Users]:''' Please provide your ORCID (can be obtained at [https://orcid.org/signin ORCID]), the name of your organization, and [https://github.com/geneontology/go-site/blob/master/metadata/groups.yaml group].
#'''Sign up to the [https://mailman.stanford.edu/mailman/listinfo/go-consortium GO-consortium mailing list]'''.  This will automatically also send you emails from the <code>[https://mailman.stanford.edu/mailman/listinfo/go-friends go-friends]</code> list.
#'''Sign up to the [https://mailman.stanford.edu/mailman/listinfo/go-consortium GO-consortium mailing list]'''.  This will automatically also send you emails from the <code>[https://mailman.stanford.edu/mailman/listinfo/go-friends go-friends]</code> list.
#'''Get an ORCID''' at [https://orcid.org/signin ORCID]


==Checklist for new Biocurators==
==Checklist for new Biocurators==
Line 45: Line 45:
** GitHub: Biocurators should be following the [https://github.com/geneontology/go-ontology/issues ontology] and [https://github.com/geneontology/go-annotation/issues annotation] GitHub repositories.  
** GitHub: Biocurators should be following the [https://github.com/geneontology/go-ontology/issues ontology] and [https://github.com/geneontology/go-annotation/issues annotation] GitHub repositories.  
*** For queries or feedback on specific tools, see the list of our [[Instructions_for_GitHub_for_GO#Main_repositories_and_their_scope |Main repositories and their scope]].
*** For queries or feedback on specific tools, see the list of our [[Instructions_for_GitHub_for_GO#Main_repositories_and_their_scope |Main repositories and their scope]].
** [https://gitter.im/geneontology/go-annotation go-annotation Gitter]: Live chat with other GO curators.
** [https://geneontologyworkspace.slack.com/home GO Slack]
** [https://geneontologyworkspace.slack.com/home GO Slack]
** [https://alliance-project.slack.com/ Genome Alliance Function Group Slack].  
** [https://alliance-project.slack.com/ Genome Alliance Function Group Slack].  
Line 54: Line 53:
* Relevant orgs: http://github.com/geneontology/
* Relevant orgs: http://github.com/geneontology/
** See all pinned repos
** See all pinned repos
* [http://github.com/berkeleybop/ Javascript libs]
* [http://github.com/owlcollab/ OWLTools]
* [http://github.com/biolink/ APIs, python]
* [http://github.com/biolink/ APIs, python]
* [http://ontobio.readthedocs.org ontobio documentation (Python)]
* [http://ontobio.readthedocs.org ontobio documentation (Python)]
* [https://docs.google.com/document/d/1w3mkF1RQIzwROOCMTkqjYaOn8ZbdsW52t-xA4DKt0vg/edit#heading=h.du3v9zif59jp Noctua Stack technical docs]
* [https://docs.google.com/document/d/1w3mkF1RQIzwROOCMTkqjYaOn8ZbdsW52t-xA4DKt0vg/edit#heading=h.du3v9zif59jp Noctua Stack technical docs]
* For continuous Integration, we use Travis for per-repo checks
* For continuous Integration, we use GitHUb Actions for per-repo checks
** https://build.geneontology.org/ (GO pipeline)
* For data pipeline, we use Jenkins https://build.geneontology.org/ (GO pipeline)
* Communication:
* Communication:
** https://groups.io/g/godev-internal/
** https://groups.io/g/godev-internal/
** Slack: function group on alliance slack
** [https://geneontologyworkspace.slack.com/home GO Slack]: Informal group chats
** [https://gitter.im/geneontology/noctua Gitter (for developers)]


==Checklist for new Ontology Editors==
==Checklist for new Ontology Editors==
* Read the Ontology Editors manual: '''[[Ontology Development| Ontology Development documentation]].'''
* Read the Ontology Editors manual: '''[[Ontology Development| Ontology Development documentation]].'''
* Subscribe to the <code>[https://mailman.stanford.edu/mailman/listinfo/go-ontology go-ontology email list]</code>.
* Subscribe to the <code>[https://mailman.stanford.edu/mailman/listinfo/go-ontology go-ontology email list]</code>.
* Be sure to follow the '''[https://github.com/geneontology/go-ontology/issues Ontology GitHub repository]'''.
* Follow the '''[https://github.com/geneontology/go-ontology/issues Ontology GitHub repository]'''.
* Get an id range in go-idranges.owl.
* Get an id range in go-idranges.owl.
* Do the '''[http://go-protege-tutorial.readthedocs.io/en/latest/ GO Protege/OWL tutorial]'''.
* Do the '''[http://go-protege-tutorial.readthedocs.io/en/latest/ GO Protege/OWL tutorial]'''.
Line 82: Line 78:
* '''[https://github.com/geneontology/ GO GitHub Project]'''
* '''[https://github.com/geneontology/ GO GitHub Project]'''
* '''[http://geneontology.org/ GO website]'''
* '''[http://geneontology.org/ GO website]'''
* '''[http://amigo.geneontology.org/amigo AmiGO]'''  
* '''[http://amigo.geneontology.org AmiGO]'''  
* '''[http://noctua.berkeleybop.org/ Noctua]'''
* '''[http://noctua.geneontology.org/ Noctua]'''
* '''[http://wiki.geneontology.org GO wiki]'''
* '''[http://wiki.geneontology.org GO wiki]'''


Line 129: Line 125:
== Review Status ==
== Review Status ==


Last reviewed: October 13, 2021
Last reviewed: February 28, 2022

Revision as of 12:48, 16 March 2022

Welcome to the GO Consortium!

This page explains how to join and contribute to the Gene Ontology project, either as a biocurator, a software developer, or to provide feedback on the ontology or the annotations.

Project organization

The Gene Ontology project is a consortium of different groups and individuals associated with the project to various degrees. We welcome contributions from anyone.

There are different groups within the project (see also sidebar 'GOC Project' menu). Note that members of the different groups may overlap.

  • Annotation: Responsible for developing annotation guidelines, as well as training and guiding biocurators in applying GO terms correctly to gene products. This group also includes phylogenetic annotation, annotation inferences across evolutionary related proteins based on known function of proteins within PANTHER phylogenetic family trees (annotations can be view with the Pantree browser).
  • Ontology: This group is responsible for maintaining the ontology itself, and related products such as links to other resources.
  • Quality Control: Ensures the integrity of the ontology and the annotations.
  • Outreach: Responsible for the GO public presence and communication with the general research community, via the GO website, Twitter, the GO helpdesk, etc.
  • Software and Utilities: Develops and implement the software required to build the ontology, generate annotations (Noctua), and view annotations (AmiGO).
  • GO Managers oversee and prioritize projects.

Communication

  • Phone conferences. The different groups meet on a regular basis via phone conferencing (zoom). Meetings are announced by email on one of the mailing lists, and are listed in the GO Google calendar. Follow the steps in the checklist of the New Member Onboarding: joining the GO project section of this document below.

Project management: GitHub

  • The GO consortium uses GitHub to track tasks for the various aspects of the project: software development, ontology maintenance, annotation issues, etc. See Instructions for GitHub for GO for details.
  • Within GitHub, group of related tasks are organized into 'projects'. See GO projects for details.

All new members: joining the GO project

Checklist for all Gene Ontology Consortium Members and Contributors

  1. Create a GO wiki account
  2. Create a GitHub account at GitHub
    • Check your mail (including spam), and accept the invitation when you receive it.
  3. Create a ticket in the Gene Ontology's GitHub Helpdesk repository to request to (please copy the following list in the ticket):
    • Be invited to the Gene Ontology Project: Please mention your role: Biocurator, software developer or domain expert.
    • Get access to GO google drive: Please provide the email account you want to use
    • Be added to the GO Google calendar, so you can view conference call information
    • Be added to Group contacts: Please provide your expertise (1-3 keywords)
    • Be added to Users: Please provide your ORCID (can be obtained at ORCID), the name of your organization, and group.
  4. Sign up to the GO-consortium mailing list. This will automatically also send you emails from the go-friends list.

Checklist for new Biocurators

Checklist for new Software Developers

Checklist for new Ontology Editors

Checklist for new GO Managers, Product Owners, Technical Leads

Useful links

Key contacts

Role Name GitHub handle email
Project management & Ontology development Pascale Gaudet @pgaudet pascalegaudet-at-swib.swiss
Technical Lead Seth Carbon @kltm sjcarbon-at-lbl.gov
Annotation Kimberly VanAuken @vanaukenk vanauken-at-caltech.edu
GO-CAM modeling David Hill @ukemi david.hill-at-jax.org
Phylogenetic Annotation Huaiyu Mi @huaiyumi huaiyumi-at-usc.edu
Outreach and User Support Suzi Aleksander @suzialeksander suzia-at-stanford.edu

Review Status

Last reviewed: February 28, 2022