<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
<meta name="Generator" content="Microsoft Exchange Server">
<!-- converted from text --><style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left: #800000 2px solid; } --></style>
</head>
<body>
<meta content="text/html; charset=UTF-8">
<style type="text/css" style="">
<!--
p
{margin-top:0;
margin-bottom:0}
-->
</style>
<div dir="ltr">
<div id="x_divtagdefaultwrapper" dir="ltr" style="font-size:12pt; color:#000000; font-family:Calibri,Helvetica,sans-serif">
<p>Dear MEI community,</p>
<p><br>
</p>
<p></p>
<div>As another follow-up, today we continued the discussed transition and renamed the "master" branch for all main MEI GitHub repositories
<span>to "main"</span>. This includes</div>
<div><br>
- https://github.com/music-encoding/music-encoding.github.io<br>
- https://github.com/music-encoding/sample-encodings<br>
- https://github.com/music-encoding/encoding-tools<br>
- https://github.com/music-encoding/guidelines<br>
- https://github.com/music-encoding/schema</div>
<p></p>
<p><br>
</p>
<p><span>While this will not affect you if you have not forked any of the aforementioned repositories, fork owners may want to adjust their respective local branches to keep in sync.
<span>A nice and easy to follow description of the necessary steps can be found here: https://stevenmortimer.com/5-steps-to-change-github-default-branch-from-master-to-main/ (There are 5 simple steps that can be completed in under 1 minute).</span></span></p>
<p><span><span><br>
</span></span></p>
<p><span><span>Many thanks to everyone involved in this important step towards a more inclusive terminology (see Anna's mail for background)! And special thanks to you, Andrew, for the technical implementation.</span></span></p>
<p><span><span><br>
</span></span></p>
<p><span><span>Cheers,</span></span></p>
<p><span><span>Stefan<br>
</span></span></p>
<p><span><span><br>
</span></span></p>
<p><span><span></span></span><br>
</p>
</div>
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="x_divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" color="#000000" style="font-size:11pt"><b>Von:</b> mei-l <mei-l-bounces@lists.uni-paderborn.de> im Auftrag von Andrew Hankinson <andrew.hankinson@rism.digital><br>
<b>Gesendet:</b> Mittwoch, 5. Mai 2021 13:56:52<br>
<b>An:</b> Music Encoding Initiative<br>
<b>Betreff:</b> Re: [MEI-L] Rename the MEI master-branch</font>
<div> </div>
</div>
</div>
<font size="2"><span style="font-size:10pt;">
<div class="PlainText">Hello everyone,<br>
<br>
To follow up on this discussion, the community has decided on 'stable' as the appropriate replacement. This is just a 'heads-up' that I will be making the change today, so please update any of your tools, workflows, and other dependencies to reflect this change.<br>
<br>
Cheers,<br>
<br>
-Andrew<br>
<br>
> On 13 Apr 2021, at 16:46, Benjamin W. Bohl <b.w.bohl@gmail.com> wrote:<br>
> <br>
> Dear Anna,<br>
> <br>
> Thanks for this valuable addition ;-)<br>
> <br>
> /Benni<br>
> <br>
>> On 13. Apr 2021, at 16:45, Kijas, Anna E <Anna.Kijas@tufts.edu> wrote:<br>
>> <br>
>> Thank you, Benjamin for this! Here is some additional context for folks who may not be following these conversations,https://www.nytimes.com/2021/04/13/technology/racist-computer-engineering-terms-ietf.html. Also I’d like to share a guide created by several
of my colleagues at the Association for Computers and the Humanities - <a href="https://ach.org/toward-anti-racist-technical-terminology/">
https://ach.org/toward-anti-racist-technical-terminology/</a> - which addresses racist technical terminology. We also have an open bibliography on Zotero for Inclusive Technology -https://www.zotero.org/groups/2554430/ach_inclusive_technology.<br>
>> <br>
>> Best,<br>
>> Anna<br>
>> <br>
>> Please note: Lilly Music Library hours and additional details can be viewed athttps://tischlibrary.tufts.edu/use-library/lilly-music-library. Updates about library services can be found at
<a href="https://tischlibrary.tufts.edu/about-us/news/2020-03-16-9900">https://tischlibrary.tufts.edu/about-us/news/2020-03-16-9900</a>. All instruction, meetings, and consultations will be conducted over Zoom.
<br>
>> <br>
>> Anna E. Kijas<br>
>> Head, Lilly Music Library<br>
>> Granoff Music Center<br>
>> Tufts University<br>
>> 20 Talbot Avenue, Medford, MA 02155<br>
>> Pronouns: she, her, hers<br>
>> Book an appointment | (617) 627-2846<br>
>> <br>
>> From: mei-l <mei-l-bounces@lists.uni-paderborn.de> on behalf of "Benjamin W. Bohl" <b.w.bohl@gmail.com><br>
>> Reply-To: Music Encoding Initiative <mei-l@lists.uni-paderborn.de><br>
>> Date: Tuesday, April 13, 2021 at 10:32 AM<br>
>> To: MEI-L <mei-l@lists.uni-paderborn.de><br>
>> Subject: [MEI-L] Rename the MEI master-branch<br>
>> <br>
>> Dear MEI Community,<br>
>> <br>
>> following a suggestion by the Software Freedom Conservancy GitHub renamed their master-branch to main in order to avoid potentially offensive vocabulary or allusions to slavery.<br>
>> <br>
>> MEI would like to follow this lead and rename the master-branch of <a href="https://github.com/music-encoding/music-encoding">
https://github.com/music-encoding/music-encoding</a> and other repositories where applicable. Following the discussion on GitHub (<a href="https://github.com/music-encoding/music-encoding/issues/776">https://github.com/music-encoding/music-encoding/issues/776</a>)
the Technical Team set up this poll to take in the community's votes on a closed list of potential new names for our current master-branch, used to disseminate tagged versions (e.g. MEI 3.0.0, MEI 4.0.0 MEI 4.0.1).<br>
>> <br>
>> Please cast your vote until 2021-04-28 using the form available at:<br>
>> <a href="https://abstimmung.dfn.de/tNOBDWgWAFtVz6lr">https://abstimmung.dfn.de/tNOBDWgWAFtVz6lr</a><br>
>> <br>
>> On behalf of the MEI Board and Technical Team,<br>
>> Benjamin W. Bohl<br>
>> MEI Technical Co-chair<br>
>> <br>
>> _______________________________________________<br>
>> mei-l mailing list<br>
>> mei-l@lists.uni-paderborn.de<br>
>> <a href="https://lists.uni-paderborn.de/mailman/listinfo/mei-l">https://lists.uni-paderborn.de/mailman/listinfo/mei-l</a><br>
> <br>
> <br>
> _______________________________________________<br>
> mei-l mailing list<br>
> mei-l@lists.uni-paderborn.de<br>
> <a href="https://lists.uni-paderborn.de/mailman/listinfo/mei-l">https://lists.uni-paderborn.de/mailman/listinfo/mei-l</a><br>
<br>
<br>
_______________________________________________<br>
mei-l mailing list<br>
mei-l@lists.uni-paderborn.de<br>
<a href="https://lists.uni-paderborn.de/mailman/listinfo/mei-l">https://lists.uni-paderborn.de/mailman/listinfo/mei-l</a><br>
</div>
</span></font>
</body>
</html>