[MEI-L] MEC2016 Follow up: Customizations
zoltan.komives at tido-music.com
Mon May 23 16:06:44 CEST 2016
It was a great pleasure to see so many of you last week in Montreal. It was
also great to see such a welcoming reception of the Tido customization
<http://tido.github.io/mei-customization/>. For those of you who weren't
there, it sparked (or re-sparked) a lively discussion about issue #285
eventually turned into a 2-hour long workshop on Friday. We discussed
several technical details, as well as brainstormed for a name: currently
MEI Go! (with or without the exclamation mark) seems to be the favourite.
Raffaele and I were trying to capture the moment and the resulting,
somewhat messy notes are available here
for editing too, I realise it was shared for viewing only with most
participants during the meeting, apologies for that!). Due to the
fragmentary nature of it, and since it may even contain errors, I suggest
we consider it a record of what was discussed, rather than what was
I think the next step would be to decide what repository MEI Go! should
live in, and compile the notes into github issues within that repository.
Even though it is dependent on the main MEI schema, it may be easier to
keep track of its development in a separate repository. Since our test
framework received some attention too, I propose to simply fork
https://github.com/music-encoding, rename it to MEI Go! and take it
Tido (UK) Ltd, 2–6 Baches Street, London N1 6DN, United Kingdom.
Disclaimer: The information in this e-mail including any attachments is
confidential and may be legally privileged. If you have received this
message in error, please contact the sender immediately and delete this
message and any copies from your computer and network. The unauthorized
use, distribution, copying or alteration of this e-mail and any attachments
is strictly forbidden.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the mei-l