[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Repo-criteria-discuss] Criteria updated to version 1.1
From: |
Juuso Lapinlampi |
Subject: |
Re: [Repo-criteria-discuss] Criteria updated to version 1.1 |
Date: |
Sat, 25 Jun 2016 11:30:31 +0000 |
User-agent: |
Mutt/1.5.24 (2015-08-30) |
On Sat, Jun 25, 2016 at 01:04:47AM -0400, Mike Gerwitz wrote:
> That solves a different problem: we want users to choose GPLv3+, but
> they also have to apply it correctly; simply including the text of the
> GPL in COPYING/LICENSE doesn't provide the "or later" clause---it only
> provides GPLv3.
>
> With regards to putting the license header at the top of each
> non-trivial source file---this is to ensure that the file is clearly
> licensed should it become detached from the rest of the source tree.
I understood the issue itself, but my question was about how Git service
providers should approach in fulfilling the criteria. Would an advisory
be enough?
The GPLv3+ is not required in A-criteria, only encouraged.
I don't like the idea of Git service providers moderating works on the
basis if they have license information in the files or not, so I thought
the criteria is poorly worded.