<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Thank you Adam,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">I will definitely recommend that the newly established GitHub repo
<a href="https://github.com/MPEGGroup/OpenFontFormat">https://github.com/MPEGGroup/OpenFontFormat</a> be considered for inclusion as already established, additional AHG communication channel, but it would be reckless on my part to promise that everything can
change overnight when a new AHG mandate is established. Most likely, both the AHG email list and the new GitHub Repo will co-exist, and it will be truly up to us to use them both to the best of our abilities while respecting the limitations of ISO process
and navigating through many rules and procedures defined by the ISO Directives and by JTC1 supplement.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">As AHG, we do have a voice, but it is the WG and the Subcommittee who make decisions related to AHGs, and they have to comply with both documents I just mentioned.
Sometimes, patience is a virtue (or, paraphrasing Neil Armstrong, “one small step for AHG, …)<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Vlad<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> mpeg-otspec <mpeg-otspec-bounces@lists.aau.at>
<b>On Behalf Of </b>Adam Twardoch (Lists)<br>
On Wednesday, October 7, 2020 12:56 AM Adam Twardoch wrote:<br>
<b>To:</b> Dave Crossland <dcrossland@google.com><br>
<b>Cc:</b> mpeg-otspec <mpeg-otspec@lists.aau.at><br>
<b>Subject:</b> Re: [MPEG-OTSPEC] Proposal to discontinue the AdHoc Group<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div style="border:none white 1.0pt;padding:0in 0in 0in 0in">
<p class="MsoNormal">In <a href="https://protect-us.mimecast.com/s/43RXCKr2BLhq4BPWIMCGBX">
https://lists.aau.at/pipermail/mpeg-otspec/2016-February/000674.html</a><o:p></o:p></p>
</div>
<div style="border:none white 1.0pt;padding:0in 0in 0in 0in">
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div style="border:none white 1.0pt;padding:0in 0in 0in 0in">
<p class="MsoNormal">> [Opentype-layout] DRAFT 1.1 : Proposal to redefine OpenType Layout joining features<o:p></o:p></p>
</div>
<div style="border:none white 1.0pt;padding:0in 0in 0in 0in">
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div style="border:none white 1.0pt;padding:0in 0in 0in 0in">
<p class="MsoNormal">Vlad wrote: <o:p></o:p></p>
</div>
<div style="border:none white 1.0pt;padding:0in 0in 0in 0in">
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div style="border:none white 1.0pt;padding:0in 0in 0in 0in">
<p class="MsoNormal">> And, as far as the choice of email lists are concerned, I believe the mpeg-OTspec list offers a spectacular choice of features (that I outlined in the beginning of this email) but if you believe that there is another worthy alternative
that is far superior to what we have and ought to be considered as a new industry-wide forum, I would be more than happy to consider moving the ISO ad-hoc group communications to a new medium. The reality of today is that none of the lists we are all subscribed
to offer the same set of rich features that Yahoo Group does. Active participation of all interested parties is all it takes to make it as good of the industry forum as it can possibly be. And, when it comes to list / group status - this is OUR forum where
every member can be heard, every voice counted and where people can join the discussions and speak up without list moderator's approval.<o:p></o:p></p>
</div>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">The key part being:<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">> <span style="color:black">if you believe that there is another worthy alternative that is far superior to what we have and ought to be considered as a new industry-wide forum, I would be more than happy to consider moving the ISO ad-hoc
group communications to a new medium</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">To me this reads that in 2016, the AHG chair did not exclude the possibility to replace the Yahoo-hosted or Australian University hosted e-mail list by another *medium*. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">To me this also reads that, for example, a Github issues system could be seen as such medium. Several AHG members now explained how, 4 years after that exchange, Github has developed into a platform where technical discussions happen. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">The Github issues system can effectively replace e-mail threads, with formatting being better preserved than in e-mail (I really have difficulties sometimes to pick who said what in a long e-mail thread because the quoting styles are so
inconsistent).<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">The Github repo itself can act as a versionable file repository, much more effectively than e-mail attachments. The underlying Git system takes care of the version tracking. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">If the AHG mandate is up for renewal soon, I'd like to suggest that the AHG adopts the Github repo as the "reflector", with this e-mail list only being used as a supplementary medium for non-technical communication such as organizational
announcements etc.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">A.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal">On Thu, 24 Sep 2020 at 05:13, Dave Crossland <<a href="mailto:dcrossland@google.com">dcrossland@google.com</a>> wrote:<o:p></o:p></p>
</div>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal">On Wed, Sep 23, 2020 at 1:23 PM John Hudson <<a href="mailto:john@tiro.ca" target="_blank">john@tiro.ca</a>> wrote:<o:p></o:p></p>
</div>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<div>
<div>
<p class="MsoNormal">[a] [authoring proposals for OFF] needs to be entirely separate and self-governing, with its own procedures and tools for communication, collaborative editing, versioning, etc., <o:p></o:p></p>
</div>
</div>
</blockquote>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
</div>
</blockquote>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<div>
<div>
<p class="MsoNormal">[b] and only after it has completed its work on specific issues should it submit, through national standards bodies, proposals to OFF. <o:p></o:p></p>
</div>
</div>
</blockquote>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">To the first part, I am optimistic that soon enough, <a href="https://protect-us.mimecast.com/s/DaDRCL92DvfPQmV9Cqe3BQ" target="_blank">
https://github.com/MPEGGroup/OpenFontFormat</a> can work as a place better than <a href="https://protect-us.mimecast.com/s/o5EPCM82gJs5zRD3uJSXhL" target="_blank">https://github.com/commontype</a> or <a href="https://protect-us.mimecast.com/s/UuUpCNk2jYtNjEJ3sRB47N" target="_blank">https://github.com/opentype</a>
or <a href="https://protect-us.mimecast.com/s/IoIFCOY2kPUAv0lxIPkT6n" target="_blank">https://github.com/googlefonts/colr-gradients-spec</a> or
<a href="https://protect-us.mimecast.com/s/iIFlCW6lvQhjDPZqTBuYx4" target="_blank">
github.com/font-text</a> or <a href="https://protect-us.mimecast.com/s/FQsFCXD0wrhnOqjKSxdm-1" target="_blank">
github.com/microsoft/typography-issues</a> or $many_other_examples, for this kind of authoring of proposals. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">To the second part, I think submitting the proposals directly through national standards bodies is a terrible idea, and the AHG has been working really well as a buffy to take proposals from the dispersed expert community and "buffer" them
from the ISO processes. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">I think the process documentation that I've proposed at <a href="https://protect-us.mimecast.com/s/UDSQCR60nPhr5RoWS0bZZt" target="_blank">https://github.com/MPEGGroup/OpenFontFormat/pull/5/files?short_path=04c6e90#diff-04c6e90faac2675aa89e2176d2eec7d8</a>
and Vlad has collaboratively edited with contributioins from Caleb is demonstrating that this MPEG repo can work. I said the other day it would be nice to move whole-hog from this mailing list to that repo, but I accept that for now there is a 2 step process
for the expert community, where proposals are authored "elsewhere" in the first step, and secondly submitted here to this email list. I think ideally the bulk of discussion can (rather, will continue to) happen 'elsewhere' and this 2nd step on this list will
hopefully not involve much discussion, and rather the traffic on this list will subside and become focused on voicing approvals or objections to proposals. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">I also am happy that by having that MPEGGroup repo, it is much easier to track what happens in all the other Github repos, if they continue, from a central place. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</div>
<p class="MsoNormal">_______________________________________________<br>
mpeg-otspec mailing list<br>
<a href="mailto:mpeg-otspec@lists.aau.at" target="_blank">mpeg-otspec@lists.aau.at</a><br>
<a href="https://protect-us.mimecast.com/s/1PemCVOkr7Tlg5mycrd1Ta" target="_blank">https://lists.aau.at/mailman/listinfo/mpeg-otspec</a><o:p></o:p></p>
</blockquote>
</div>
</div>
</div>
</body>
</html>