<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=us-ascii"><meta name=Generator content="Microsoft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:Helvetica;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
{font-family:SimSun;
panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
{font-family:SimSun;
panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:SimSun;
panose-1:2 1 6 0 3 1 1 1 1 1;}
/* 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;}
span.apple-style-span
{mso-style-name:apple-style-span;}
span.im
{mso-style-name:im;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.25in 1.0in 1.25in;}
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'>Hi All,<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'>My confusion is what should be done to the license declaration part of the code. For example, if I copy code from NFD to ndn-cxx, what kind of information I should add to the license declaration part of the file containing the code I just copied.<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'>Regards,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Jiewen Tan<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><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Lan Wang (lanwang) [mailto:lanwang@memphis.edu] <br><b>Sent:</b> Wednesday, October 15, 2014 8:15 AM<br><b>To:</b> Alex Afanasyev<br><b>Cc:</b> Junxiao Shi; <nfd-dev@lists.cs.ucla.edu>; alanwake@ucla.edu<br><b>Subject:</b> Re: [Nfd-dev] License boilerplate for code imported from NFD to ndn-cxx<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I think it's best for Jiewen to explain what specific problems (questions, confusion) he had when importing the code. If it's something that can be solved by "reading the license and license boilerplate", then there's no need for guidelines. Otherwise, guidelines will be helpful. <o:p></o:p></p><div><p class=MsoNormal><o:p> </o:p></p><div><div><div><div><p class=MsoNormal><span style='font-size:13.5pt;font-family:"Helvetica","sans-serif";color:black'>Lan<o:p></o:p></span></p></div></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 Oct 12, 2014, at 7:22 PM, Alex Afanasyev <<a href="mailto:alexander.afanasyev@ucla.edu">alexander.afanasyev@ucla.edu</a>> wrote:<o:p></o:p></p></div><p class=MsoNormal><br><br><o:p></o:p></p><div><div><p class=MsoNormal>Junxiao,<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Please, don't make an issue from a non-issue. The license (and license boilerplate) is in itself instructions on how code can be used, re-used, and moved around. There is noting special that needs to be added.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>For the cases you're referring to. This is the point of code review, when you noticed that boilerplate is not the one we usually use / incorrect copyright/license attribute. There is no guidelines, rather you just need to tell what is the right way. That's it.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Licenses are pretty simple to read (at least the boilerplate) and it is important for everybody to understand the limitations of the licenses.<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>Alex<o:p></o:p></p></div><p class=MsoNormal><o:p> </o:p></p><div><div><p class=MsoNormal>On Oct 12, 2014, at 4:49 PM, Junxiao Shi <<a href="mailto:shijunxiao@email.arizona.edu">shijunxiao@email.arizona.edu</a>> wrote:<o:p></o:p></p></div><p class=MsoNormal><br><br><o:p></o:p></p><div><p class=MsoNormal>Hi Davide <o:p></o:p></p><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Developers are not lawyers. License is to be interpreted by a lawyer. Requiring consulting a lawyer every time importing NFD code is counter-productive.<o:p></o:p></p></div><div><p class=MsoNormal>The guideline should be some mechanical steps that developers could easily follow.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Note the scope of this discussion is specifically for importing code from NFD, and probably NLSR and repo-ng.<o:p></o:p></p></div><div><p class=MsoNormal>I agree that importing code from an external project should involve consulting with a lawyer.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Yours, Junxiao<o:p></o:p></p><div><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal>On Sun, Oct 12, 2014 at 4:26 PM, Davide Pesavento <<a href="mailto:davide.pesavento@lip6.fr" target="_blank">davide.pesavento@lip6.fr</a>> wrote:<o:p></o:p></p><p class=MsoNormal>Well then maybe the first rule should be: read (and understand) the<br>license of the code you're touching/using.<br><br>Best,<br>Davide<br><br><span class=im>> ---------- Forwarded message ----------</span><br><span class=im>> From: Jiewen Tan <<a href="mailto:alanwake@ucla.edu">alanwake@ucla.edu</a>></span><br><span class=im>> Date: Sat, Oct 11, 2014 at 11:53 PM</span><br><span class=im>></span><br><span class=im>> Hi All,</span><br><span class=im>></span><br><span class=im>> I am the owner. I do agree with Junxiao there should be a guideline,</span><br><span class=im>> otherwise new people like me will be confused while importing codes.</span><br><span class=im>></span><br><span class=im>> Regards,</span><br><span class=im>> Jiewen Tan</span><br><span class=im>></span><br><span class=im>> On Oct 11, 2014, at 11:09 PM, Junxiao Shi <<a href="mailto:shijunxiao@email.arizona.edu">shijunxiao@email.arizona.edu</a>></span><br><span class=im>> wrote:</span><br><span class=im>></span><br><span class=im>> Dear folks</span><br><span class=im>></span><br><span class=im>> There needs a guideline on how to write license boilerplate for code</span><br><span class=im>> imported from NFD to ndn-cxx.</span><br><span class=im>> The necessity of such a guideline is illustrated by</span><br><span class=im>> <a href="http://gerrit.named-data.net/1254" target="_blank">http://gerrit.named-data.net/1254</a> where the Change Owner fails to produce a</span><br><span class=im>> correct license boilerplate in 3 patchsets.</span><br><span class=im>></span><br><span class=im>> Yours, Junxiao</span><br><span class=im>></span><o:p></o:p></p></div></div></div></div><p class=MsoNormal>_______________________________________________<br>Nfd-dev mailing list<br><a href="mailto:Nfd-dev@lists.cs.ucla.edu">Nfd-dev@lists.cs.ucla.edu</a><br><a href="http://www.lists.cs.ucla.edu/mailman/listinfo/nfd-dev">http://www.lists.cs.ucla.edu/mailman/listinfo/nfd-dev</a><o:p></o:p></p></div><p class=MsoNormal><o:p> </o:p></p></div><p class=MsoNormal>_______________________________________________<br>Nfd-dev mailing list<br><a href="mailto:Nfd-dev@lists.cs.ucla.edu">Nfd-dev@lists.cs.ucla.edu</a><br><a href="http://www.lists.cs.ucla.edu/mailman/listinfo/nfd-dev">http://www.lists.cs.ucla.edu/mailman/listinfo/nfd-dev</a><o:p></o:p></p></div><p class=MsoNormal><o:p> </o:p></p></div></div></body></html>