Packaging text licenses

Hi all, Yesterday, I was looking for the CC-BY license text to start a new project. I had to dig up to CreativeCommons's github repository to find the text version. (I didn't want to copy/paste the HTML version on their website). My question to you is: "Would it be interesting for others if I we

Re: Packaging text licenses

Hi Baptiste, On Sat, 14 Dec 2019, 13:04 Baptiste BEAUPLAT, wrote: > I had to dig up to CreativeCommons's github repository to find the text > version. (I didn't want to copy/paste the HTML version on their website). > It's https://creativecommons.org/licenses/by/4.0/legalcode.txt. One just has

Re: Packaging text licenses

On 12/14/19 12:27 PM, Andrius Merkys wrote: > It's https://creativecommons.org/licenses/by/4.0/legalcode.txt. One just > has to add .txt suffix to legal code link URL. Ah thanks Andrius, I was completely oblivious to that. -- Baptiste BEAUPLAT - lyknode signature.asc Description: OpenPGP digi

Re: Packaging text licenses

Hi Baptiste, Quoting Baptiste BEAUPLAT (2019-12-14 11:55:40) > Yesterday, I was looking for the CC-BY license text to start a new > project. > > I had to dig up to CreativeCommons's github repository to find the > text version. (I didn't want to copy/paste the HTML version on their > website).

Re: Packaging text licenses

On 12/14/19 1:03 PM, Jonas Smedegaard wrote: > A rich collection of Free license fulltexts is relevant, not only for > our users to pick from (even on a lonely island) and copy into new > development project, but also as reference e.g. for testing license > checkers. > > What is _not_ helpful i

Re: Packaging text licenses

On 12/14/19 2:01 PM, Baptiste BEAUPLAT wrote: > On 12/14/19 1:03 PM, Jonas Smedegaard wrote: >> A rich collection of Free license fulltexts is relevant, not only for >> our users to pick from (even on a lonely island) and copy into new >> development project, but also as reference e.g. for testin

Re: Packaging text licenses

Quoting Baptiste BEAUPLAT (2019-12-14 15:12:38) > On 12/14/19 2:01 PM, Baptiste BEAUPLAT wrote: > > On 12/14/19 1:03 PM, Jonas Smedegaard wrote: > >> A rich collection of Free license fulltexts is relevant, not only > >> for our users to pick from (even on a lonely island) and copy into > >> new

Re: Packaging text licenses

On Sat, 14 Dec 2019 14:01:18 +0100 Baptiste BEAUPLAT wrote: > On 12/14/19 1:03 PM, Jonas Smedegaard wrote: > > A rich collection of Free license fulltexts is relevant, not only for > > our users to pick from (even on a lonely island) and copy into new > > development project, but also as referen

Re: Packaging text licenses

Quoting Francesco Poli (2019-12-14 17:22:09) > On Sat, 14 Dec 2019 14:01:18 +0100 Baptiste BEAUPLAT wrote: > > > On 12/14/19 1:03 PM, Jonas Smedegaard wrote: > > > A rich collection of Free license fulltexts is relevant, not only > > > for our users to pick from (even on a lonely island) and copy

Re: Packaging text licenses

Francesco Poli writes: > A number of license texts are not themselves licensed under DFSG-free > terms. For example, the GNU General Public License. Copyright (C) 2007 Free Software Foundation, Inc. Everyone is permitted to copy and distribute verbatim copies of this licens

Re: Packaging text licenses

On Sat, Dec 14, 2019 at 05:22:09PM +0100, Francesco Poli wrote: > A number of license texts are not themselves licensed under DFSG-free > terms. > > And Debian promises to remain 100 % free, see [SC] #1. Any content of a > Debian package (in main) must be free according to the DFSG. Sure. > Licen