<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Sun, Apr 27, 2014 at 6:28 AM, Mateusz Jończyk <span dir="ltr"><<a href="mailto:mat.jonczyk@o2.pl" target="_blank">mat.jonczyk@o2.pl</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="">-----BEGIN PGP SIGNED MESSAGE-----<br>
Hash: SHA1<br>
<br>
</div>Hello,<br>
<br>
W dniu <a href="tel:27.04.2014%2011" value="+12704201411">27.04.2014 11</a>:33, Luc Verhaegen pisze:<br>
<div class="">> Thanks so very much for taking me in CC.<br>
</div>Right, I should have CC You. Please excuse me. I am new to this project.<br>
<div class=""><br>
><br>
> I am quite certain that if i hadn't mentioned the origins of these calculations,<br>
> you would never have bothered.<br>
</div>Yep, that would be probably lost and forgotten.<br>
<div class="">> I amazed that you bother now, now that it spread to a buzzword project.<br>
</div>Somebody simply noticed the fact of possible copyright problems here.<br>
<div class="">><br>
> I clearly explained the origins for a reason: namely so that we could update our<br>
> code to match in the unlikely case some changes happen, i even explained that<br>
> reasoning.<br>
><br>
> CVT is a VESA standard. I did not and do not have access to VESA documents, and<br>
> the dog ate the Xorg boards homework, as noone seems to remember what happened<br>
> to the Xorg VESA membership. My feeling however is that this spreadsheet is a<br>
> rather direct implementation of the VESA standard, and that if the Xorg board<br>
> gets its act together (for a change), we will actually be able to verify where<br>
> this information originally came from.<br>
><br>
> The xls however, felt as if it was meant as a reference implementation, aimed at<br>
> improving the proliferation of CVT. If graham does get contacted, i think he<br>
> would agree.<br>
</div>I don't have any doubts that the Authors of the XLS would agree to inclusion of its<br>
derivative works in XOrg and other programs.<br>
Until that happens, however, we cannot rely on it.<br>
<div class="">><br>
> Now, before we do get access to those documents, how are you intending to<br>
> circumvent this claimed copyright infringement without infringing yourself under<br>
> your very strict rules?<br>
</div>We could just rewrite it using the Chinese wall principle:<br>
<a href="http://en.wikipedia.org/wiki/Clean_room_design" target="_blank">http://en.wikipedia.org/wiki/Clean_room_design</a><br></blockquote><div><br></div><div>Patches welcome.<br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
> Luc Verhaegen.<br>
<div class="">><br>
<br>
- --<br>
Pozdrawiam,<br>
Mateusz Jończyk<br>
AEI, Informatyka, Semestr 2 Magisterskich, BDiIS<br>
<br>
-----BEGIN PGP SIGNATURE-----<br>
Version: GnuPG v1.4.11 (GNU/Linux)<br>
Comment: My public key: 0x2C64C488 on hkp://<a href="http://pool.sks-keyservers.net" target="_blank">pool.sks-keyservers.net</a><br>
Comment: Using GnuPG with Thunderbird - <a href="http://www.enigmail.net/" target="_blank">http://www.enigmail.net/</a><br>
<br>
</div>iQEcBAEBAgAGBQJTXNvXAAoJELLT9LcsZMSI+WkIAIqQPwI/D1LPudUOFygjmnPq<br>
fBMmm7i8f1H7InVRHHavLN8hSGl3XddyKvu1ZTBbEyR8jXFwFElykxFRaGG7RxYs<br>
MWJyz+/f4FYbpRx0xm17QIQr9dfxvHbtStIsiTR4ZuVU0FdB40wQp73ZI/D1EPa5<br>
y33pjR3ivkbISGPDFDGyueXzdBHW7Sd5gszTTfyh1Pn3Se2L2cEsWPdmIEQXPO5l<br>
tz6i75qOCy+D2UrXNZT9LTbA/lxo5r6WQl9XtnYANAoibgkwz/H8fvHu4DgS5a//<br>
crNyPLd+my0mzEcdxezpKzGpnGtxZe1W3tTKDMZRDjXQ1bnRtrIuonNgQrUdljc=<br>
=EsiA<br>
-----END PGP SIGNATURE-----<br>
<div class="HOEnZb"><div class="h5">_______________________________________________<br>
<a href="mailto:xorg-devel@lists.x.org">xorg-devel@lists.x.org</a>: X.Org development<br>
Archives: <a href="http://lists.x.org/archives/xorg-devel" target="_blank">http://lists.x.org/archives/xorg-devel</a><br>
Info: <a href="http://lists.x.org/mailman/listinfo/xorg-devel" target="_blank">http://lists.x.org/mailman/listinfo/xorg-devel</a></div></div></blockquote></div><br><br clear="all"><br>-- <br> Jasper<br>
</div></div>