<div dir="auto">Sure, but what concrete steps can we take to do that? <div dir="auto"><br></div><div dir="auto">Adam blathering on about dropping CFF/CFF2 seems to be a much more egregious "in passing" comment than what Li Renzhi said.... :)</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Sep 11, 2020, 5:24 PM Levantovsky, Vladimir <<a href="mailto:Vladimir.Levantovsky@monotype.com">Vladimir.Levantovsky@monotype.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div lang="EN-US" link="blue" vlink="purple">
<div class="m_421242564527154608WordSection1">
<pre><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">I think that if we want to introduce breaking changes we need to build the foundation for future discussions and consensus. Adam summed it up nicely in his previous email: </span><span style="color:black">explicit discussion, agreement, and also a benefit-cost analysis.</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"> (<a href="https://lists.aau.at/pipermail/mpeg-otspec/2020-September/002263.html" target="_blank" rel="noreferrer">https://lists.aau.at/pipermail/mpeg-otspec/2020-September/002263.html</a>)<u></u><u></u></span></pre>
<pre><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"><u></u> <u></u></span></pre>
<pre><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">Vlad<u></u><u></u></span></pre>
<pre><span style="color:black"><u></u> <u></u></span></pre>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"><u></u> <u></u></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"> Dave Crossland <<a href="mailto:dcrossland@google.com" target="_blank" rel="noreferrer">dcrossland@google.com</a>>
<br>
<b>Sent:</b> Friday, September 11, 2020 4:58 PM<br>
<b>To:</b> Levantovsky, Vladimir <<a href="mailto:Vladimir.Levantovsky@monotype.com" target="_blank" rel="noreferrer">Vladimir.Levantovsky@monotype.com</a>><br>
<b>Cc:</b> Renzhi Li <<a href="mailto:Renzhi.Li@microsoft.com" target="_blank" rel="noreferrer">Renzhi.Li@microsoft.com</a>>; mpeg-otspec <<a href="mailto:mpeg-otspec@lists.aau.at" target="_blank" rel="noreferrer">mpeg-otspec@lists.aau.at</a>><br>
<b>Subject:</b> Re: Introducing breaking changes into the spec (was: RE: [MPEG-OTSPEC] [EXTERNAL] Proposal to deprecate derived search values)<u></u><u></u></span></p>
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<div>
<p class="MsoNormal">On Fri, Sep 11, 2020 at 4:12 PM Levantovsky, Vladimir <<a href="mailto:Vladimir.Levantovsky@monotype.com" target="_blank" rel="noreferrer">Vladimir.Levantovsky@monotype.com</a>> wrote:<u></u><u></u></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"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">I did NOT say they can’t happen here, but this is exactly the kind of decision that cannot be taken
lightly, and it is definitely not a joke!</span><u></u><u></u></p>
</div>
</div>
</blockquote>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">Thanks for clarifying - so you are saying, comments made about 1.X vs. 2.0 _are_ helpful and welcome here, but not "in passing"? If yes, how to formalize such discussions? :)<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">On Github, we can have issues assigned to Milestones so its very clear what context they are in: <u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">1. Current Spec Changes (Editorial - no differences for implementations, "OT 1.8.x)<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">1. Iterative Spec Changes (Small to medium work required by implementations to meet the standard, "OT 1.9.x")<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">3. Incompatible Spec Changes (Large impact for implementations, "OT 2.0")<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal"> <u></u><u></u></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"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">New specs can be written easily, but it’s the wide adoption [not the spec itself] that we should care
about the most because, in the end, it is what benefits users. You seem to care a lot about consensus decisions, and this is exactly why consensus decisions are so important.</span><u></u><u></u></p>
</div>
</div>
</blockquote>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">Harfbuzz is now adopted widely (Google, Adobe, MS...) and anyone can fork and implement anything and submit it mainly harfbuzz. <u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
</div>
</div>
</div>
</div>
</blockquote></div>