Hi Yann

On Wednesday, 23 October 2019 2:25:48 AM NZDT Yann CARDAILLAC wrote:
> On Mon, Oct 21, 2019 at 9:37 PM Paul Eggleton <paul.eggle...@linux.intel.com>
> wrote:
> > On Tuesday, 22 October 2019 4:15:03 AM NZDT Yann CARDAILLAC wrote:
> > > https://bugzilla.yoctoproject.org/show_bug.cgi?id=13527
> > >
> > > I'm beginning the work of updating the layerindex-web repo, this one is a
> > > bit tricky, how should I treat the files generated using Django ?
> >
> > I believe the correct license for Django-derived files is BSD-3-Clause:
> >
> >   https://github.com/django/django/blob/master/LICENSE
> >
> > > I've yet to do html, txt and sh files, do you have any advices before I
> > > start?
> >
> > Note that some of the templates used for authentication originally came
> > from
> > here:
> >
> >   https://github.com/macdhuibh/django-registration-templates
> >
> > The LICENSE file indicates MIT for those though.
> >
> > The txt files are tricky because any stray newlines will affect
> > formatting. I would probably avoid touching them.
>
> I did not yet add MIT to html files, I don't really know if that makes
> sense or not?  I didn't do that because it seemed a bit weird to me, but I
> don't know what to think of that. Most of the time you'll find copyright on
> the footer of the page, but I'm not sure about Licensing those.
> 
> So here is a first iteration of the patch without htmls file licensed.

I think it's fine to add to the HTML as long as you add it as part of the 
Django template comment at the top and not in the actual text that gets 
rendered.

Looking over the license definitions they look fine, except the migrations - if 
these are considered derived from Django (which is fine) then they should all 
be BSD-3-Clause rather than some being MIT. It looks like some of the earlier 
ones don't have a "generated by django" comment, but they were all initially 
generated with ./manage.py makemigrations; some then had additional code added 
to them.

Cheers
Paul

-- 

Paul Eggleton
Intel System Software Products


-- 
_______________________________________________
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Reply via email to