<div dir="auto"><div style="border-color:rgb(255,255,255)" dir="auto">In <a href="https://lists.aau.at/pipermail/mpeg-otspec/2016-February/000674.html">https://lists.aau.at/pipermail/mpeg-otspec/2016-February/000674.html</a></div><div style="border-color:rgb(255,255,255)" dir="auto"><br></div><div style="border-color:rgb(255,255,255)" dir="auto">> [Opentype-layout] DRAFT 1.1 : Proposal to redefine OpenType Layout joining features</div><div style="border-color:rgb(255,255,255)" dir="auto"><br></div><div style="border-color:rgb(255,255,255)" dir="auto">Vlad wrote: </div><div style="border-color:rgb(255,255,255)" dir="auto"><br></div><div style="border-color:rgb(255,255,255)" dir="auto">> 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.<br></div></div><div dir="auto"><br></div><div dir="auto">The key part being:</div><div dir="auto"><br></div><div dir="auto">> <span style="color:rgb(0,0,0)">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></div><div dir="auto"><br></div><div dir="auto">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*. </div><div dir="auto"><br></div><div dir="auto">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. </div><div dir="auto"><br></div><div dir="auto">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).</div><div dir="auto"><br></div><div dir="auto">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. </div><div dir="auto"><br></div><div dir="auto">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.</div><div dir="auto"><br></div><div dir="auto">A.</div><div dir="auto"><br></div><div dir="auto"><br></div><div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, 24 Sep 2020 at 05:13, Dave Crossland <<a href="mailto:dcrossland@google.com">dcrossland@google.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;padding-left:1ex;border-left-color:rgb(204,204,204)"><div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Sep 23, 2020 at 1:23 PM John Hudson <<a href="mailto:john@tiro.ca" target="_blank">john@tiro.ca</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;padding-left:1ex;border-left-color:rgb(204,204,204)">
<div>
<div>[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., </div></div></blockquote><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;padding-left:1ex;border-left-color:rgb(204,204,204)"><div><div> </div></div></blockquote><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;padding-left:1ex;border-left-color:rgb(204,204,204)"><div><div>[b] and only after it has completed its work on specific issues should
it submit, through national standards bodies, proposals to OFF. </div></div></blockquote><div><br></div><div>To the first part, I am optimistic that soon enough, <a href="https://github.com/MPEGGroup/OpenFontFormat" target="_blank">https://github.com/MPEGGroup/OpenFontFormat</a> can work as a place better than <a href="https://github.com/commontype" target="_blank">https://github.com/commontype</a> or <a href="https://github.com/opentype" target="_blank">https://github.com/opentype</a> or <a href="https://github.com/googlefonts/colr-gradients-spec" target="_blank">https://github.com/googlefonts/colr-gradients-spec</a> or <a href="http://github.com/font-text" target="_blank">github.com/font-text</a> or <a href="http://github.com/microsoft/typography-issues" target="_blank">github.com/microsoft/typography-issues</a> or $many_other_examples, for this kind of authoring of proposals. </div><div><br></div><div>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. </div><div><br></div><div>I think the process documentation that I've proposed at <a href="https://github.com/MPEGGroup/OpenFontFormat/pull/5/files?short_path=04c6e90#diff-04c6e90faac2675aa89e2176d2eec7d8" 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. </div><div><br></div><div>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. </div><div><br></div><div></div></div></div>
_______________________________________________<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://lists.aau.at/mailman/listinfo/mpeg-otspec" rel="noreferrer" target="_blank">https://lists.aau.at/mailman/listinfo/mpeg-otspec</a><br>
</blockquote></div></div>