Gohelp: Difference between revisions

From GO Wiki
Jump to navigation Jump to search
mNo edit summary
mNo edit summary
Line 12: Line 12:
# Check the [http://geneontology.org/faq-page FAQ].  Answers might already be there.
# Check the [http://geneontology.org/faq-page FAQ].  Answers might already be there.
#* If needed, improve FAQ documentation on website.
#* If needed, improve FAQ documentation on website.
# Create tickets in other trackers as appropriate:
#* Ontology, taxon constraints: https://github.com/geneontology/go-ontology/issues
#* Annotation: https://github.com/geneontology/go-annotation/issues
#* AmiGO: https://github.com/geneontology/amigo/issues
#* Pipeline: https://github.com/geneontology/go-site/issues
#* Rules: https://github.com/geneontology/go-site/issues
#* Noctua: https://github.com/geneontology/noctua/issues
#* Evidence codes: https://github.com/evidenceontology/evidenceontology/issues
# Mark tickets as "stale" after ~ 1 month of no response from OP or after a solution has been proposed.  Prompt OP for any further related questions; tickets can be closed due to inactivity after a further appropriate amount of time.
# Mark tickets as "stale" after ~ 1 month of no response from OP or after a solution has been proposed.  Prompt OP for any further related questions; tickets can be closed due to inactivity after a further appropriate amount of time.



Revision as of 07:52, 25 February 2019

All GO help queries go to the Github GO Helpdesk tracker


Actions for person responsible for overseeing tracker:

  1. Triage queries.
    • Mark as "accepted" immediately, add additional flags as appropriate
    • Assign queries to the person with appropriate expertise.
      • This page list GOC's members expertise [1] to help identify the best people to assign the different queries to.
  2. Check the FAQ. Answers might already be there.
    • If needed, improve FAQ documentation on website.
  3. Create tickets in other trackers as appropriate:
  4. Mark tickets as "stale" after ~ 1 month of no response from OP or after a solution has been proposed. Prompt OP for any further related questions; tickets can be closed due to inactivity after a further appropriate amount of time.


Review Status

Last reviewed: February 25, 2019