Re: "License": public-domain (original) (raw)
[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]
- To: Ghislain Vaillant <ghisvail@gmail.com>
- Cc: Narcis Garcia <debianlists@actiu.net>, Debian Mentors List <debian-mentors@lists.debian.org>
- Subject: Re: "License": public-domain
- From: "Gabriel F. T. Gomes" <gabriel@inconstante.eti.br>
- Date: Thu, 14 Sep 2017 07:15:58 -0300
- Message-id: <[π] 20170914071558.57bb133d@lenin>
- In-reply-to: <[π] CAFzxpWoJiYnphS60XY1wp62VQAEqFKiFv_7b3Dr3GvuTLoev8Q@mail.gmail.com>
- References: <[π] 20170913154604.nuldpbm4m6cxsgmi@qor.donarmstrong.com> <[π] 1678154e-388c-8fa3-6f35-cb454462000a@actiu.net> <[π] CAFzxpWoJiYnphS60XY1wp62VQAEqFKiFv_7b3Dr3GvuTLoev8Q@mail.gmail.com>
On Thu, 14 Sep 2017 10:13:18 +0100 Ghislain Vaillant ghisvail@gmail.com wrote:
Le 14 sept. 2017 9:45 AM, "Narcis Garcia" debianlists@actiu.net a Γ©crit :
In my humble opinion, Lintian should mark a warning when detecting this. This could make some developers and/or packagers to reconsider chosen license.
And why should they? CC0 or Unlicense have clear terms. Problems arise when upstream only specifies public domain without an explicit definition for it.
This fact (that the problem with public domain only happens upstream, and that Debian deals well with it) could also be documented in the new FAQ (I wouldn't know how to write it properly, so I'd like to ask for someone to do it). At least for me, this information is new.
Reply to:
- References:
- Re: "License": public-domain
* From: Don Armstrong don@debian.org - Re: "License": public-domain
* From: Narcis Garcia debianlists@actiu.net - Re: "License": public-domain
* From: Ghislain Vaillant ghisvail@gmail.com
- Re: "License": public-domain
- Prev by Date:Bug#875679: RFS: goldendict/1.5.0~rc2+git20170908+ds-1
- Next by Date:Bug#875693: RFS: python-meshio/1.8.16-1
- Previous by thread:Re: "License": public-domain
- Next by thread:Bug#875693: RFS: python-meshio/1.8.16-1
- Index(es):