Re: all-permissive license notice

Bruno Haible via Gnulib discussion list writes: > Collin Funk wrote: >> I've noticed a few other files using the "unlimited" license and added >> the disclaimer. They should all be correct now. > > Thanks! I missed these while searching for all affected files. Should config.rpath be fixed too?

Re: all-permissive license notice

Collin Funk wrote: > I've noticed a few other files using the "unlimited" license and added > the disclaimer. They should all be correct now. Thanks! I missed these while searching for all affected files. Bruno

Re: all-permissive license notice

Hi Bruno, Bruno Haible via Gnulib discussion list writes: > 2024-10-17 Bruno Haible > > Use a warranty disclaimer in all-permissive license notices. > * etc/license-notices/unlimited: Add a short warranty disclaimer > sentence. > * m4/*.m4: Update. > * build-aux/

Re: all-permissive license notice

Paul Eggert wrote: > The sentence "This file is offered as-is, without warranty of any kind." > was added to maintain.texi in 2009[1]. I assume this sentence was due to > advice from FSF legal. We should definitely add it. Done: 2024-10-17 Bruno Haible Use a warranty disclaimer in a

Re: all-permissive license notice

Simon Josefsson wrote: > Another consideration is license proliferation. License proliferation is bad because - it creates incompatibilities, - it creates doubt about the intent. > But at least please let's not create a new variation > of these existing variants: > > https://spdx.org/license

Re: all-permissive license notice

Paul Eggert wrote: > The sentence "This file is offered as-is, without warranty of any kind." > was added to maintain.texi in 2009[1]. I assume this sentence was due to > advice from FSF legal. We should definitely add it. OK. I will do that. > I don't know where I got the wording in my 2005 Gn

Re: all-permissive license notice

Another consideration is license proliferation. I would prefer to be consistent with the GNU maintainers guide, unless we want to express some other intent. But at least please let's not create a new variation of these existing variants: https://spdx.org/licenses/FSFAP.html https://spdx.org/lice

Re: all-permissive license notice

The sentence "This file is offered as-is, without warranty of any kind." was added to maintain.texi in 2009[1]. I assume this sentence was due to advice from FSF legal. We should definitely add it. I don't know where I got the wording in my 2005 Gnulib commit[2]. Maybe from your earlier Gnulib

Re: all-permissive license notice

Collin Funk wrote: > A good lawyer could probably argue that free software develoeprs aren't > "sellers" or something. But adding the disclaimer probably saves them > from the arguement entirely. Thanks. Hopefully this mis-perception, partially caused by the ambiguous word "free", will change in t

Re: all-permissive license notice

Hi Bruno, Bruno Haible via Gnulib discussion list writes: > Oh, I missed that it already says > "Older versions of this license did not have the second sentence with >the express warranty disclaimer." > So, adding this sentence appears to be a good idea. I think it is best to add a line a

Re: all-permissive license notice

Simon Josefsson wrote: > Bruno Haible via Gnulib discussion list writes: > > > Hi, > > > > The all-permissive copyright + license notice that we currently use is: > > > > dnl Copyright (C) YEARS Free Software Foundation, Inc. > > dnl This file is free software; the Free Software Foundation >

Re: Adding slice-by-4 and slice-by-8 to CRC32

> I have one use-case (although not published so less > important) where the table size increase is a problem, and would prefer > to use the current smaller crc.c (or even better, a smaller one that > generate the tables on the fly, I forgot that it is possible). There's another approach for table

Re: all-permissive license notice

Bruno Haible via Gnulib discussion list writes: > Hi, > > The all-permissive copyright + license notice that we currently use is: > > dnl Copyright (C) YEARS Free Software Foundation, Inc. > dnl This file is free software; the Free Software Foundation > dnl gives unlimited permission to cop

Re: gettext-and-autopoint documentation update?

Assaf Gordon wrote in : > The gnulib manual says: > "2. After running gettextize, invoke gnulib-tool and import > the gettext module. " > https://www.gnu.org/software/gnulib/manual/html_node/gettextize-and-autopoint.html >

Re: all-permissive license notice

> The all-permissive copyright + license notice that we currently use is: > > dnl Copyright (C) YEARS Free Software Foundation, Inc. > dnl This file is free software; the Free Software Foundation > dnl gives unlimited permission to copy and/or distribute it, > dnl with or without modificati

all-permissive license notice

Hi, The all-permissive copyright + license notice that we currently use is: dnl Copyright (C) YEARS Free Software Foundation, Inc. dnl This file is free software; the Free Software Foundation dnl gives unlimited permission to copy and/or distribute it, dnl with or without modifications, a

Re: Adding slice-by-4 and slice-by-8 to CRC32

Simon Josefsson wrote: > If we are splitting this module up into several, maybe it even make more > sense to have a 'crc-slice-by-8' module for that particular portable > optimization. I have one use-case (although not published so less > important) where the table size increase is a problem, and