Technical team

The Technical Team consists of interested developers and two Board-appointed Co-Chairs. The Co-Chairs act as administrative chairs of the Technical Team, e.g., calling meetings and coordinating development efforts. They also have administrative privileges for the MEI repositories. The MEI Technical Team holds regular virtual and in-person meetings, maintains the MEI repository on GitHub (https://github.com/music-encoding), prepares new releases of MEI by reviewing and implementing revisions and features requested by the community, and supports the wider MEI community with their technical expertise.

• Benjamin W. Bohl (Technical Co-Chair), Institut für Musikwissenschaft, Goethe Universität Frankfurt, Frankfurt am Main and Musikwissenschaftliches Seminar Detmold/Paderborn
• Stefan Münnich (Technical Co-Chair), Anton Webern Gesamtausgabe, University of Basel
• Sophia Dörner, Humboldt-Universität zu Berlin
• Ichiro Fujinaga, McGill University, Montréal
• Andrew Hankinson, RISM Digital Center, Bern
• Johannes Kepper, Musikwissenschaftliches Seminar Detmold/Paderborn
• Laurent Pugin, RISM Digital Center, Bern
• Klaus Rettinghaus, Enote GmbH, Berlin
• Perry D. Roland, Charlottesville
• Daniel Röwenstrunk, Musikwissenschaftliches Seminar Detmold/Paderborn
• Craig Sapp, Center for Computer-Assisted Research in the Humanities, Stanford University
• Martha E. Thomae, McGill University, Montréal
• Raffaele Viglianti, Maryland Institute for Technology in the Humanities
• Thomas Weber, Notengrafik Berlin GmbH

MEI ODD meetings

MEI ODD Fridays and ODD Thursdays are a monthly video conference call with anyone interested in the development of MEI. During these calls, we discuss open pull requests with additions to and revisions of both the MEI Schema and Guidelines. There are two requirements for accepting changes:

• There have to be matching proposals for both the Schema and the Guidelines (i.e., changes without proper documentation won’t get accepted, but may collect feedback),
• there needs to be wide acceptance for these changes at the meetings and in the corresponding PRs.

If a proposal doesn’t match these two criteria, it will be postponed and should be revised for the next ODD meeting.

We aim to organize, schedule, and document these meetings with the help of a GitHub dashboard: https://github.com/orgs/music-encoding/projects/9. We also plan to send out timely reminders in advance of these meetings. The intention is to increase both comprehensibility and transparency of the MEI development workflow, and make it more accessible and inviting to newcomers.

The schedule for these developer workshops is the last Friday of every odd month, and last Thursday of every even month, at 3pm UTC (in summer) resp. 4pm UTC (in winter). Calls are scheduled for:

2024

• November 29, 2024 4pm UTC ODD Friday
• October 31, 2024 4pm UTC ODD Thursday
• September 27, 2024 3pm UTC ODD Friday
• August: summer break
• July 26, 2024 3pm UTC ODD Friday
• June 27, 2024 3pm UTC ODD Thursday
• May 31, 2024 3pm UTC ODD Friday
• May 20–23, 2024: MEC conference
• Apr 25, 2024 3pm UTC ODD Thursday
• March 22, 2024 4pm UTC ODD Friday
• March 6, 2024 3pm UTC ODD Thursday (= Wednesday)
• January 26, 2024 4pm UTC ODD Friday
• January 18–20, 2024: Developer workshop, Vienna