Manager Call 2018-07-19: Difference between revisions

From GO Wiki
Jump to navigation Jump to search
mNo edit summary
 
(3 intermediate revisions by 2 users not shown)
Line 1: Line 1:
[[Category:GO Managers Meetings]]
[[Category:GO Managers Meetings]]


Regrets: Kimberly
== Regrets ==
*Kimberly


==Pipeline==  
==Pipeline==  
Line 37: Line 38:
Managers should help define the tasks of the helpdesk group
Managers should help define the tasks of the helpdesk group


Proposal: (Pascale)
Proposal: from the managers
* monitor helpdesk repo
* Monitor helpdesk repo
* monitor Biostars for GO-related questions
* Monitor Biostars and Stack Exchange, Twitter and Facebook '''for GO-related questions'''
* Create and maintain FAQs
* ++?





Latest revision as of 11:55, 18 July 2018


Regrets

  • Kimberly

Pipeline

Are the files on Jenkins still valid ? http://build.berkeleybop.org/view/GAF/job/gaf-check-pombase/ This is what PomBase uses

New repo: go-announcements

Pascale: I created the repo: https://github.com/geneontology/go-announcements I have been adding the new obsoletion notices there, and I also copied some older tickets that had label 'major change' Proposed guidelines: It should be used by

Website migration status

Laurent-Philippe, Suzi (Note that Kimberly, David and Pascale are still slowing moving content to the wiki, as discussed at the Documentation meeting in Jan 2018)

Noctua 1.1 plan

Kimberly and Seth https://docs.google.com/document/d/1p0VfgTRaYe0vTGMjMDc48Wz2HWpry_JufSS2X3dqccA/edit

Closing pull requests

There are a number of PR in the go-ontology repo - can we close or assign someone to help close the tickets? https://github.com/geneontology/go-ontology/pulls



The next topics were moved from the June 20th call)

From PI call

Managers should help define the tasks of the helpdesk group

Proposal: from the managers

  • Monitor helpdesk repo
  • Monitor Biostars and Stack Exchange, Twitter and Facebook for GO-related questions
  • Create and maintain FAQs
  • ++?


Managers should help define the tasks of the outreach group

  • help new groups make annotations submissions

Topics not discussed at last meeting

  • 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
  • (Suzi/Seth) Zotero as home for collected help/starter documentation?

Minutes