-
Notifications
You must be signed in to change notification settings - Fork 6
2021 07 22 MerMEId Community Call #7
This meeting is held during the MEC Un-conference day on Thursday, 22 July 2021, 17:40-18:40 (CEST).
Daniel Jettka, David Lewis, Clemens Gubsch, Margrethe Støkken Bue, Iacopo Cividini, Jonathan Gammert, Kevin Page, Omar Siam, Mark Saccomano, Mirijam Beier, Stefan Münnich, Peter Stadler
Some MEI board members have raised the question whether this group would like to be considered an MEI IG. Some information (about the formal procedure) is detailed at https://music-encoding.org/community/interest-groups.html.
The discussion at the meeting centers around
- whether there would be too much overlap with the Metadata IG
- whether a "Tools" IG might be better (to embrace other MEI related software projects like Verovio)
Margrethe (as chair of the Metadata IG) sees no obstacles and Kevin remarks that clear aims and objectives are important for every group. Group members dedicate time to this particular MerMEId project but might not be able or willing when the focus is lost. Since the visibility of this group will be increased by the formation as an IG, the group tasks Peter to initiate the formal process by applying to the MEI board.
For an overview, see the list of closed issues and pull requests.
For an overview, see https://github.com/Edirom/MerMEId/pulls
For an overview, see https://github.com/Edirom/MerMEId/issues
- "Viewing without logging in" #73. Which areas should be read-protected?
The current behaviour is considered a regression and the default setting for all MerMEId pages should be "world-readable". Kevin points out that (again) a clear distinction and support of both an editable and a published catalogue would be benefitial. While this is considered a long term goal, for a timely solution Daniel and Peter are assigned to #73.
Peter proposes (in addition to last meeting's decision to tag the progress more frequently) to merge the development branch into the main branch with every tag and rename the "master" branch to "main". The group agrees, that although the current version is not considered stable (i.e. bug free and feature complete), it's way better than the current (two years behind) status of the master branch. Thus merging into main will add to the project's visibility of activity, tidy up the messiness, and provide a clearer entrypoint to newcomers.
06/09/2021 15:30 (GMT +02:00) – Zoom link is pinned in the Slack channel.
We'll skip the August meeting for many participants have declared their unavailability. The new 4-weekly meeting cycle will then start on September 6.