[Nfd-dev] License boilerplate for code imported from NFD to ndn-cxx

[Alex Afanasyev]

You should always read the license / contact the original copyright holders whenever you're borrowing any code.  For some popular licenses, such as GPL/LPGL, there are a numerous explanations on the Internet describing how properly use that code in the project.

In this specific case, we were re-licensing the code and we finally recommended you a correct boilerplate.

---
Alex

On Oct 20, 2014, at 10:26 PM, Jiewen Tan <alanwake at ucla.edu> wrote:

> Hi All,
>  
> 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.
>  
> Regards,
> Jiewen Tan
>  
>  
> From: Lan Wang (lanwang) [mailto:lanwang at memphis.edu] 
> Sent: Wednesday, October 15, 2014 8:15 AM
> To: Alex Afanasyev
> Cc: Junxiao Shi; <nfd-dev at lists.cs.ucla.edu>; alanwake at ucla.edu
> Subject: Re: [Nfd-dev] License boilerplate for code imported from NFD to ndn-cxx
>  
> 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.
>  
> Lan
>  
>  
> On Oct 12, 2014, at 7:22 PM, Alex Afanasyev <alexander.afanasyev at ucla.edu> wrote:
> 
> 
> Junxiao,
>  
> 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.
>  
> 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.
>  
> Licenses are pretty simple to read (at least the boilerplate) and it is important for everybody to understand the limitations of the licenses.
>  
> ---
> Alex
>  
> On Oct 12, 2014, at 4:49 PM, Junxiao Shi <shijunxiao at email.arizona.edu> wrote:
> 
> 
> Hi Davide
>  
> Developers are not lawyers. License is to be interpreted by a lawyer. Requiring consulting a lawyer every time importing NFD code is counter-productive.
> The guideline should be some mechanical steps that developers could easily follow.
>  
> Note the scope of this discussion is specifically for importing code from NFD, and probably NLSR and repo-ng.
> I agree that importing code from an external project should involve consulting with a lawyer.
>  
> Yours, Junxiao
>  
> On Sun, Oct 12, 2014 at 4:26 PM, Davide Pesavento <davide.pesavento at lip6.fr> wrote:
> Well then maybe the first rule should be: read (and understand) the
> license of the code you're touching/using.
> 
> Best,
> Davide
> 
> > ---------- Forwarded message ----------
> > From: Jiewen Tan <alanwake at ucla.edu>
> > Date: Sat, Oct 11, 2014 at 11:53 PM
> >
> > Hi All,
> >
> > I am the owner. I do agree with Junxiao there should be a guideline,
> > otherwise new people like me will be confused while importing codes.
> >
> > Regards,
> > Jiewen Tan
> >
> > On Oct 11, 2014, at 11:09 PM, Junxiao Shi <shijunxiao at email.arizona.edu>
> > wrote:
> >
> > Dear folks
> >
> > There needs a guideline on how to write license boilerplate for code
> > imported from NFD to ndn-cxx.
> > The necessity of such a guideline is illustrated by
> > http://gerrit.named-data.net/1254 where the Change Owner fails to produce a
> > correct license boilerplate in 3 patchsets.
> >
> > Yours, Junxiao
> >
> _______________________________________________
> Nfd-dev mailing list
> Nfd-dev at lists.cs.ucla.edu
> http://www.lists.cs.ucla.edu/mailman/listinfo/nfd-dev
>  
> _______________________________________________
> Nfd-dev mailing list
> Nfd-dev at lists.cs.ucla.edu
> http://www.lists.cs.ucla.edu/mailman/listinfo/nfd-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/nfd-dev/attachments/20141020/2d1dfff4/attachment.html>