<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Dear Perry, Laurent, and especially Andrew,<br>
<br>
many thanks for your efforts in migrating the MEI repository to
GitHub! This is great news in terms of code management and community
envolvement in the development of the schemata, the guidelines and
the sample encodings!<br>
<br>
I think you've done excellent work with the contribution guidelines,
too!<br>
<br>
All the best,<br>
Benjamin<br>
<pre class="moz-signature" cols="72">
</pre>
<div class="moz-cite-prefix">Am 21.09.2015 um 20:17 schrieb Laurent
Pugin:<br>
</div>
<blockquote
cite="mid:CAJ306HZMCD+pEKiQ4GF_SNiji5mp7kRZdLMUeQz04Or1SjbTjg@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>Dear all,</div>
<div> </div>
<div>This is an official announcement of the new GitHub account
and repository for MEI. The new MEI repository is accessible
at</div>
<div><a moz-do-not-send="true"
href="https://github.com/music-encoding/music-encoding">https://github.com/music-encoding/music-encoding</a>.
All the information from the previous GoogleCode repository
has been migrated to the GitHub one, including issues,
branches, tags, etc.</div>
<div> </div>
<div>This announcement means that GoogleCode repository is no
longer in use and will not be maintained. We recommend not to
refer to it, including for schema validation. All the schemata
are now permanently available directly from <a
moz-do-not-send="true" href="http://music-encoding.org">music-encoding.org</a>
under 'schema' plus the version number. For example, the
latest release is available at <a moz-do-not-send="true"
href="http://www.music-encoding.org/schema/2.1.1/mei-all.rng">http://www.music-encoding.org/schema/2.1.1/mei-all.rng</a></div>
<div> </div>
<div>The move to GitHub has also been an opportunity for us to
re-think workflows and contribution guidelines for MEI. Of
course, since MEI is a schema and not a software product, we
expect all contributions to be thoughtfully discussed by the
community before they find their way to the MEI source.
Contributors should not expect any pull request to be included
in MEI straight away without the required discussion, even if
the contribution does not create any conflict and seems
straight forward to integrate. In order to clarify this,
Andrew Hankinson has written some contributions guidelines
that we strongly recommend reading if you are interested in
contributing to the MEI schema. </div>
<div> </div>
<div>The GitHub account of MEI includes other repositories than
the MEI source one. MEI also hosts repositories for the
customization service and the SibMEI plugin, for example. You
can see all of them listed directly on the MEI GitHub account:
<a moz-do-not-send="true"
href="https://github.com/music-encoding">https://github.com/music-encoding</a>.
At some point, we will evaluate whether parts of the current
MEI repository should become distinct repositories themselves.
As specified by the MEI by-laws, the GitHub account of MEI is
managed by the co-chairs of the technical teams. At their
discretion, the co-chairs may provide write access to the
repositories to other members of the technical team. </div>
<div> </div>
<div>Thank you to all who contributed to the migration to
GitHub. We are looking forward to your feed-back and to your
contributions.</div>
<div><br>
</div>
<div>For the technical team</div>
<div>Perry and Laurent</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
mei-l mailing list
<a class="moz-txt-link-abbreviated" href="mailto:mei-l@lists.uni-paderborn.de">mei-l@lists.uni-paderborn.de</a>
<a class="moz-txt-link-freetext" href="https://lists.uni-paderborn.de/mailman/listinfo/mei-l">https://lists.uni-paderborn.de/mailman/listinfo/mei-l</a>
</pre>
</blockquote>
<br>
</body>
</html>