Manager Call 2019-09-04: Difference between revisions

From GO Wiki
Jump to navigation Jump to search
Line 31: Line 31:
== Need for a IT/Cloud strategy ==
== Need for a IT/Cloud strategy ==
While not yet critical / urgent, it is important to have a IT/Cloud strategy for the project to ease the sharing of resources, virtual machines, protocols, loggings etc. LPA created a document for the USC AWS account in April, this could serve as a basis of discussion. Ticket example: https://github.com/geneontology/operations/issues/30
While not yet critical / urgent, it is important to have a IT/Cloud strategy for the project to ease the sharing of resources, virtual machines, protocols, loggings etc. LPA created a document for the USC AWS account in April, this could serve as a basis of discussion. Ticket example: https://github.com/geneontology/operations/issues/30
== Better integration of GO-CAMs in GO site ==
Main goal is to support the article for now, not to be perfect: https://github.com/geneontology/geneontology.github.io/issues/180


==Cross references on GO website/AmiGO page==
==Cross references on GO website/AmiGO page==

Revision as of 07:38, 4 September 2019

Agenda

  • Agenda: David
  • Minutes: Laurent-Philippe

Review action items from last week

  • Seth: Set up a wiki page for GO users meeting, and start announcing. (DONE)
  • PIs/managers: Start on the GO meeting agenda (this is a reminder. Normally this is in the Google drive)
    • Current projects
    • Ask if people want to present anything.
  • Kimberly: talk to Pankaj to see whether they can clean up their file, and correct annotations
    • We will ask if we can handle any annotation edits in P2GO for now.


GO Meeting general

Agenda first draft (by Pascale) https://docs.google.com/document/d/16ZCV1vyTHSEf20z_PO4F8S-uqD2ZvnyExV0McMWnFI0/edit

Review of project process

Aims GO meeting

  • Look at priority tasks for GO meeting.
    • GO-CAM specifications
    • Whole genome annotations from GAF to GO-CAM

Pipeline progress

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

Need for a IT/Cloud strategy

While not yet critical / urgent, it is important to have a IT/Cloud strategy for the project to ease the sharing of resources, virtual machines, protocols, loggings etc. LPA created a document for the USC AWS account in April, this could serve as a basis of discussion. Ticket example: https://github.com/geneontology/operations/issues/30

Cross references on GO website/AmiGO page


Present