|Mondo meetings should be added to the Monarch shared google calendar. Members of the curation and technical teams are outlined here.
|Any upcoming workshops should be organized and advertised. Ideally we should have community based Mondo workshops every 4-6 months.
|Workshops should be advertised on our website, on our Slack channel, on the mailing list
|Set milestones and triage tickets
|All tickets should be: 1. Acknowledged, thank the contributor for the ticket, 2. Assigned to a curation or technical team member, 3. Assigned to a monthly milestone, 4. Given a label
|Mondo should be released on a monthly basis on/around the first of the month. Please refer to the pre-release checklist for necessary tasks before the release. Instructions are here. If there are any delays with the release (more than a couple days), please communicate these to the Mondo users on the mailing list and in Slack. Some of our users depend on the regular releases, such as EFO.
|Announce Mondo Release on Mastadon
|Post about Mondo release, see text here
|1. Link Mondo tickets to Phenomics First Operations Board 2. Ensure deliverables for P1 grant are being addressed, 3. Send all dissemination artifacts to the 'nuggets' address for Monarch/TISLab (to help RPPR prepping)
|Coordinate reporting for yearly RPPR
|The Mondo website should be regularly updated (instructions are here). Regular updates that may be needed include: Mondo users, Mondo contributors, Resources- including new papers, presentations, blog posts, etc., Workhops, FAQs should be updated as new questions arise
|Liaise with Mondo Users
|Keep track of Mondo users (keep contact info up to date, what project they are working on, how they are using Mondo)
|Onboarding of new contributors
|Refer to the onboarding doc here