Manager Call 2019-01-23: Difference between revisions
| Line 14: | Line 14: | ||
== Zoom meetings == | == Zoom meetings == | ||
Need to remove all publicly accessible URLs: | |||
The old Annotation and Developers URLs were compromised over the weekend. Those were meeting IDs 828-418-143 and 976-175-422. I have disabled those URLs and sent replacements to David and Kimberly. It appears that Zoom had caught on to the sudden over-usage and that’s why the setting ‘enable join before host’ had been disabled. | |||
We have been requested to please no longer publish any Zoom URLs on any public facing pages, or to any URL or namespace to which access cannot be restricted by some sort of authentication. (this is a must-do) | |||
It has also been recommended that we password-protect meetings. (this is a suggestion) | |||
== Calendar == | |||
Nothing really to report but have been issues lately with things going missing, etc. Seems OK this week, anything we need to make official? | |||
== Reactome pipeline == | == Reactome pipeline == | ||
Revision as of 20:56, 22 January 2019
Meeting URL
https://stanford.zoom.us/j/754529609
Agenda
Upcoming Meetings
Cambridge (11-12 April) - any developments?
Next working meeting
- Next week, Berkeley (28 Jan- 1 Feb)
- Review more detailed meeting agenda
Zoom meetings
Need to remove all publicly accessible URLs:
The old Annotation and Developers URLs were compromised over the weekend. Those were meeting IDs 828-418-143 and 976-175-422. I have disabled those URLs and sent replacements to David and Kimberly. It appears that Zoom had caught on to the sudden over-usage and that’s why the setting ‘enable join before host’ had been disabled.
We have been requested to please no longer publish any Zoom URLs on any public facing pages, or to any URL or namespace to which access cannot be restricted by some sort of authentication. (this is a must-do)
It has also been recommended that we password-protect meetings. (this is a suggestion)
Calendar
Nothing really to report but have been issues lately with things going missing, etc. Seems OK this week, anything we need to make official?
Reactome pipeline
From https://github.com/geneontology/helpdesk/issues/97
Reactome is double-ingested, natively and via Reactome->GOA->GOC. Decide between:
- remove reactome from the pipeline and assume we get these from goa
- filter from goa
New website
Test site at: http://test.geneontology.io
Final critical items https://github.com/geneontology/go-site/issues/789