Gohelp: Difference between revisions
Jump to navigation
Jump to search
mNo edit summary |
mNo edit summary |
||
Line 1: | Line 1: | ||
==GO Helpdesk== | ==GO Helpdesk== | ||
All queries are directed to the [https://github.com/geneontology/helpdesk/issues GitHub GO Help Desk tracker ] | |||
==Guidelines for person responsible for overseeing the Helpdesk tracker== | ==Guidelines for person responsible for overseeing the Helpdesk tracker== |
Revision as of 05:18, 26 February 2019
GO Helpdesk
All queries are directed to the GitHub GO Help Desk tracker
Guidelines for person responsible for overseeing the Helpdesk tracker
- 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.
- Check the FAQ. Answers might already be there.
- If needed, improve FAQ documentation on website.
- Create tickets in other trackers as appropriate. Helpdesk ticket remains open until the query has been addressed.
- 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
- GO Homepage: https://github.com/geneontology/geneontology.github.io/issues
- Metadata: https://github.com/geneontology/go-site/issues
- Pipeline: https://github.com/geneontology/pipeline/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.
Review Status
Last reviewed: February 25, 2019