Annotation Conf. Call 2017-12-12: Difference between revisions
Jump to navigation
Jump to search
(→Agenda) |
|||
Line 3: | Line 3: | ||
= Agenda = | = Agenda = | ||
== Infrastructure == | |||
== github review == | == github review == | ||
*go-annotation tracker is used for issues and project management related to the annotation working group | *go-annotation tracker is used for issues and project management related to the annotation working group | ||
Line 21: | Line 22: | ||
*All curators who need to work on an issue should be listed in the Assignee field | *All curators who need to work on an issue should be listed in the Assignee field | ||
**Remove your name from the list when you've addressed or complete the work | **Remove your name from the list when you've addressed or complete the work | ||
== HTP annotations == | |||
[[Category:Annotation Working Group]] | [[Category:Annotation Working Group]] |
Revision as of 17:17, 30 November 2017
Meeting URL
Agenda
Infrastructure
github review
- go-annotation tracker is used for issues and project management related to the annotation working group
- Issues:
- Annotation review
- PAINT family review
- Keyword mapping questions
- Questions about annotation practice
- Proposals for annotation guidelines
- Requests for annotation rules
- Requests for documentation
- Use of labels
- Please always add a label to your issue
- Trying to simplify the list of labels
- Removed some that were overlapping, not applicable to this repo
- Would like to move from using group labels to tracking submission via author
- is:issue author:vanaukenk
- All curators who need to work on an issue should be listed in the Assignee field
- Remove your name from the list when you've addressed or complete the work