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

[Junxiao Shi]

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
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/nfd-dev/attachments/20141012/a7df996a/attachment.html>