Manager Call 2018-06-07: Difference between revisions

From GO Wiki
Jump to navigation Jump to search
 
(9 intermediate revisions by 5 users not shown)
Line 4: Line 4:
==Review action points from NYC meeting==
==Review action points from NYC meeting==
https://docs.google.com/document/d/1Px8AgghIABKaGP174Av2XYXQ8NfUrkMRT1yJ8kwCgx4/edit
https://docs.google.com/document/d/1Px8AgghIABKaGP174Av2XYXQ8NfUrkMRT1yJ8kwCgx4/edit
No tickets created:
* ACTION ITEM: Share presentations, teaching materials for GO presentations at non-GO conferences and meetings; send GOC members to meetings as ‘GO representatives’.  Update GO calendar with conferences that GOC members are attending, then broadcast this to GOC social media sites.
GO’ll fix it
* ACTION ITEM: Schedule a hackathon for developers.
* ACTION ITEM: Managers meeting - review call for annotation documentation from consortium members.
Need clarification:
* Are we still updating GAF specifications? https://github.com/geneontology/go-site/issues/674
==Process for adding annotations from non-consortium groups==
(Mangrove)


==Communicating with users==
==Communicating with users==
Line 13: Line 25:
* Other important ontology changes
* Other important ontology changes
* releases
* releases
* QC annoucements
* QC announcements
* GO meting announcements  
* GO meeting announcements  
* etc
* 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)
* Laurent-Philippe: collect information / links / contacts about the GO user communities (e.g. R/bioconductor and ?)
* (Pascale) Rules, especially taxon checks: can we have this for the July release? https://github.com/geneontology/go-annotation/issues/1928
==Minutes==
*On call: Chris, David, Huaiyu, Judy, Kimberly, Nomi, Pascale, Seth, Suzi A., Suzi L.

Latest revision as of 11:05, 6 June 2018


Review action points from NYC meeting

https://docs.google.com/document/d/1Px8AgghIABKaGP174Av2XYXQ8NfUrkMRT1yJ8kwCgx4/edit

No tickets created:

  • ACTION ITEM: Share presentations, teaching materials for GO presentations at non-GO conferences and meetings; send GOC members to meetings as ‘GO representatives’. Update GO calendar with conferences that GOC members are attending, then broadcast this to GOC social media sites.

GO’ll fix it

  • ACTION ITEM: Schedule a hackathon for developers.
  • ACTION ITEM: Managers meeting - review call for annotation documentation from consortium members.

Need clarification:

Process for adding annotations from non-consortium groups

(Mangrove)

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)
  • Laurent-Philippe: collect information / links / contacts about the GO user communities (e.g. R/bioconductor and ?)
  • (Pascale) Rules, especially taxon checks: can we have this for the July release? https://github.com/geneontology/go-annotation/issues/1928


Minutes

  • On call: Chris, David, Huaiyu, Judy, Kimberly, Nomi, Pascale, Seth, Suzi A., Suzi L.