Manager Call 2019-08-21: Difference between revisions

From GO Wiki
Jump to navigation Jump to search
Line 8: Line 8:
* Next: start announcing  
* Next: start announcing  


== GO Meeting general ==
* Get your people to sign up
* Get your people to pay (used for badges, etc.--the true reg)
* There is only "Yes" and "No", there is no "Maybe"


==Pipeline progress==
==Pipeline progress==


* release process started
== Project for improving mappings? ==
...[L]et's discuss whether we should initiate a project for improving the mappings: documentation, workflow processes, quality control, staying up to date.
We are of course doing a good job in specific instances, whether it is ones we bring in (interpro/reactom) or ones we maintain (e.g rhea), but this project would be about a broader approach.


==Cross references on GO website/AmiGO page==
==Cross references on GO website/AmiGO page==
Line 16: Line 28:
* Seth was to create documentation describing how that page is generated; where is that ?
* Seth was to create documentation describing how that page is generated; where is that ?


==Collaborators Webpage===
==Collaborators Webpage==
We need to decide who we put as collaborators and as contributing groups. There is some redundancy.  
We need to decide who we put as collaborators and as contributing groups. There is some redundancy.  
https://github.com/geneontology/geneontology.github.io/issues/130
https://github.com/geneontology/geneontology.github.io/issues/130

Revision as of 16:03, 19 August 2019

Agenda

  • Agenda: Seth
  • Minutes: Pascale

GO users meeting Berkeley 2019

  • TODO: Finalize decision on topics/speakers/target audience.

Preliminary agenda is here: https://docs.google.com/document/d/1YBCEeSl1MKPvtRNAMGBGcOZqdZl3wlbwWC1nuDnccqE/edit

  • Next: start announcing

GO Meeting general

  • Get your people to sign up
  • Get your people to pay (used for badges, etc.--the true reg)
  • There is only "Yes" and "No", there is no "Maybe"

Pipeline progress

  • release process started

Project for improving mappings?

...[L]et's discuss whether we should initiate a project for improving the mappings: documentation, workflow processes, quality control, staying up to date.

We are of course doing a good job in specific instances, whether it is ones we bring in (interpro/reactom) or ones we maintain (e.g rhea), but this project would be about a broader approach.

Cross references on GO website/AmiGO page

Collaborators Webpage

We need to decide who we put as collaborators and as contributing groups. There is some redundancy. https://github.com/geneontology/geneontology.github.io/issues/130

GO stats

Status, remaining work and decision on computing or not the stats for previous releases original issue and recent issue

Notes on zenodo archives and solr 3.6.

Projects status

Minutes

Present