From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Yann CARDAILLAC <yann.cardaillac@smile.fr>
Cc: yocto@yoctoproject.org
Subject: Re: [layerindex-web] Add SPDX Identifier
Date: Tue, 29 Oct 2019 16:27:37 +1300 [thread overview]
Message-ID: <3141867.2GmitW1KQV@shodan> (raw)
In-Reply-To: <CAA984JVPt_iwehB6EjcWBC507Efkjgs0Muz0g6Hczw_3mVygGA@mail.gmail.com>
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.eggleton@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
prev parent reply other threads:[~2019-10-29 3:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-21 15:15 [layerindex-web] Add SPDX Identifier Yann CARDAILLAC
2019-10-21 19:37 ` Paul Eggleton
2019-10-22 13:25 ` Yann CARDAILLAC
2019-10-29 3:27 ` Paul Eggleton [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3141867.2GmitW1KQV@shodan \
--to=paul.eggleton@linux.intel.com \
--cc=yann.cardaillac@smile.fr \
--cc=yocto@yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.