Manager Call 2018-06-07: Difference between revisions
Jump to navigation
Jump to search
mNo edit summary |
No edit summary |
||
| Line 23: | Line 23: | ||
* licensing sign-over or statement (annotation input) | * licensing sign-over or statement (annotation input) | ||
* zenodo and user metadata; proposal: "active" users and cull users.yaml (possibly a small sub-group from there, about half an hour) | * zenodo and user metadata; proposal: "active" users and cull users.yaml (possibly a small sub-group from there, about half an hour) | ||
* collect information / links / contacts about the GO user communities (e.g. R/bioconductor and ?) | |||
==Minutes== | ==Minutes== | ||
Revision as of 13:11, 5 June 2018
Review action points from NYC meeting
https://docs.google.com/document/d/1Px8AgghIABKaGP174Av2XYXQ8NfUrkMRT1yJ8kwCgx4/edit
Communicating with users
How about creating a repo that people can sign up for, or just as they want ? This would include
- changes in file format
- obsoletion and merge notices
- Other important ontology changes
- releases
- QC announcements
- GO meeting announcements
- etc
Additional topics
- create a simple challenge form? (see noctua new user form)
- licensing and "remix" for upstream sources (e.g. Reactome)
- licensing sign-over or statement (annotation input)
- zenodo and user metadata; proposal: "active" users and cull users.yaml (possibly a small sub-group from there, about half an hour)
- collect information / links / contacts about the GO user communities (e.g. R/bioconductor and ?)