All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] core/web-legal-info: Generate html page with minimal legal info
Date: Wed, 30 Oct 2019 23:21:17 +0100	[thread overview]
Message-ID: <20191030222117.GA5289@scaer> (raw)
In-Reply-To: <e39aac32-a53c-0b21-c980-07c50d1bdc00@mind.be>

Arnout, All,

On 2019-10-30 11:19 +0100, Arnout Vandecappelle spake thusly:
> On 30/10/2019 10:09, Yann E. MORIN wrote:
> >      * python (version 2.7 or any later)
>  The problem is: I would like to have some autobuilders without installed
> python. Since the autobuilders do run legal-info, that would not be possible...

Didn't we also conclude that, given that the autobuild scripts are
witten in python, it is thus forcibly present on an autobuilder
instance?

> > Also, have you had a look at Nicolas' alternate proposal, which is much
> > more lightweight and simple:
> >     http://lists.busybox.net/pipermail/buildroot/2019-October/264344.html
>  Note that that patch is missing a documentation update (which could be done in
> a separate patch).

And did not actually work for me, so might need refinement, or maybe I
was missing a few pre-requisites... Needs investigations

> > Such copyright identifiers are not required: the Berne Convention states
> > that the copyright is implicit, that is, a work does not have to carry a
> > copyright identifier to be properly copyrighted [https://en.wikipedia.org/wiki/Berne_Convention].
> 
>  However, all open source licenses (GPL, BSD, MIT, ...) kind of require it,
> because they require to mention the authors. Some projects (e.g. CMake) keep an
> explicit list of authors in the top-level LICENSE file. Other projects just say
> "the FOO contributors". Oh, and REUSE [1] requires it as well. And finally:
> (almost?) all our existing scripts do have a copyright line.

Which is sad, because it is definitely not exhaustive, far from it,
while the git log is.

> > Also, as time passes, other contributors will modify this script. We do
> > not want to have a copyright identifier for each and every contribution
> > that will be made to this script. Especially since the git log keeps an
> > accurate authorship of all contributors.
> > 
> > So I would suggest we do add such new copyright identifiers, and get rid
> > of the existing ones (as time passes).
> 
>  We should decide on a convention and stick to it :-)

Hey, I indeed meant "we should _not_ add any more". ;-)

But if the trend in the licensing galaxy is to require them, that's a
shame that we have to abide to this limitation, when we have better
technical solutions... :-(

Regards,
Yann E. MORIN.

>  Regards,
>  Arnout
> 
> 
> > 
> > Regards,
> > Yann E. MORIN.
> 
> [1] https://reuse.software/
> 

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 561 099 427 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

  reply	other threads:[~2019-10-30 22:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-29  9:51 [Buildroot] [PATCH] core/web-legal-info: Generate html page with minimal legal info Mickaël Tansorier
2019-10-29 22:40 ` Arnout Vandecappelle
2019-10-30  9:09   ` Yann E. MORIN
2019-10-30 10:19     ` Arnout Vandecappelle
2019-10-30 22:21       ` Yann E. MORIN [this message]
2019-10-30 16:16     ` Mickaël Tansorier
2019-10-31 21:38   ` Thomas Petazzoni
2019-11-01 15:21     ` Yann E. MORIN

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=20191030222117.GA5289@scaer \
    --to=yann.morin.1998@free.fr \
    --cc=buildroot@busybox.net \
    /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.