mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Roland Hieber <rhi@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH 2/2] doc: working with licensing information in packages
Date: Tue, 2 Jun 2020 17:14:13 +0200	[thread overview]
Message-ID: <20200602151413.rvpaoem65twhlpap@pengutronix.de> (raw)
In-Reply-To: <20200602131634.GJ31789@pengutronix.de>

On Tue, Jun 02, 2020 at 03:16:34PM +0200, Michael Olbrich wrote:
> On Sun, May 31, 2020 at 09:56:15PM +0200, Roland Hieber wrote:
> > On Fri, May 29, 2020 at 02:03:00PM +0200, Michael Olbrich wrote:
> > > On Fri, May 29, 2020 at 11:40:49AM +0200, Roland Hieber wrote:
> > > > https://git.pengutronix.de/cgit/rhi/ptxdist/commit/?h=6dc705e869353f24d3cd1be7698afcd119e8da95
> > > 
> > > "The whole package, starting with version 1.1.22, is distributed under·
> > > the GNU GPL license, found in the accompanying file 'COPYING'."
> > > 
> > > And the COPYING file does not exist... But check the latest version: The
> > > COPYING exist there and it's GPL-2.0 and with the wording above I'd say
> > > GPL-2.0-only.
> > 
> > Given that this release is from 2007, I'd rather file another staging
> > patch than do a version bump...
> 
> ok, can you rebase your branch to remove corresponding the license patch?

Yes, I'll send a PULL v2.

> > But what does that mean for the documentation patch above? Of course it
> > very much concerns only edge cases, but then, edge cases is what that
> > section is really about ^^ So I think only the wording needs to be
> > adapted to clarify that it applies only when not even a GPL text is
> > available. Or what was the reason in your view that the package was not
> > even distributable?
> 
> For the documentation, the main thing is "don't assume". If it's really
> unclear, then just use 'custom' and add all relevant texts to the license
> files. Then whoever creates a BSP must decide for themself if the license
> is acceptable.
> The license identifier is just a hint. And it must be the correct one not
> just whatever is closest. Otherwise it's useless.

Right, that sounds reasonable.

Also I found old documentation in the dev_manual.rst, which I'll
integrate into this patch. It also fits better in the developer manual
instead of the daily use chapter.

 - Roland

-- 
Roland Hieber, Pengutronix e.K.          | r.hieber@pengutronix.de     |
Steuerwalder Str. 21                     | https://www.pengutronix.de/ |
31137 Hildesheim, Germany                | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686         | Fax:   +49-5121-206917-5555 |

_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-request@pengutronix.de

  reply	other threads:[~2020-06-02 15:14 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-11 10:03 [ptxdist] [PATCH 1/2] doc: ref_make_variables: link to the SPDX license list Roland Hieber
2020-05-11 10:03 ` [ptxdist] [PATCH 2/2] doc: working with licensing information in packages Roland Hieber
2020-05-26 10:29   ` Roland Hieber
2020-05-26 11:12   ` Alexander Dahl
2020-05-29  6:23   ` Michael Olbrich
2020-05-29  8:27     ` Roland Hieber
2020-05-29  8:55       ` Michael Olbrich
2020-05-29  9:40         ` Roland Hieber
2020-05-29 12:03           ` Michael Olbrich
2020-05-31 19:56             ` Roland Hieber
2020-06-02 13:16               ` Michael Olbrich
2020-06-02 15:14                 ` Roland Hieber [this message]
2021-06-08 10:36 ` [ptxdist] [PATCH] " Roland Hieber
2021-06-16 14:19   ` Michael Olbrich
2021-06-16 14:40     ` Roland Hieber
2021-08-05  9:18     ` [ptxdist] [PATCH v3] " Roland Hieber
2021-08-06  6:29       ` Michael Olbrich
2021-08-06 10:44         ` [ptxdist] [PATCH] " Roland Hieber
2021-10-07 10:18           ` [ptxdist] [APPLIED] " Michael Olbrich

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=20200602151413.rvpaoem65twhlpap@pengutronix.de \
    --to=rhi@pengutronix.de \
    --cc=ptxdist@pengutronix.de \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox