lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ib7p6mx6sltp2bu6vxw7n2urxuaq2lk4a6efsgnjym43svpvy3@wbgmnm6sy23o>
Date: Fri, 9 May 2025 14:57:56 +0200
From: Alejandro Colomar <alx@...nel.org>
To: Vincent Lefevre <vincent@...c17.net>, 
	"Andries E. Brouwer" <aeb@....nl>, linux-man@...r.kernel.org, linux-kernel@...r.kernel.org, 
	libc-alpha@...rceware.org, "G. Branden Robinson" <branden@...ian.org>, 
	Carlos O'Donell <carlos@...hat.com>, Eugene Syromyatnikov <evgsyr@...il.com>
Subject: Re: man-pages-6.14 released

Hi Vincent,

On Fri, May 09, 2025 at 02:48:29PM +0200, Vincent Lefevre wrote:
> Hi,
> 
> On 2025-05-09 14:28:23 +0200, Alejandro Colomar wrote:
> > On Fri, May 09, 2025 at 02:14:54PM +0200, Andries E. Brouwer wrote:
> > > Hi Alejandro,
> > > 
> > > > > I wonder about the legal status of such a change.
> > > > > There is ownership of the pages, and a license that allows
> > > > > others to do certain things.
> > > > 
> > > > I also wonder about it.  We discussed it for several (~3) months, and I
> > > > documented links to the discussion in the commit message:
> > > > 
> > > > commit 9f2986c34166085225bb5606ebfd4952054e1657
> > > > Author: Alejandro Colomar <alx@...nel.org>
> > > > Date:   Fri Apr 11 02:19:48 2025 +0200
> > > > 
> > > >     *, CREDITS: Unify copyright notices
> > > >     
> > > >     Link: <https://lore.kernel.org/linux-man/jpin2dbnp5vpitnh7l4qmvkamzq3h3xljzsznrudgioox3nn72@57uybxbe3h4p/T/#u>
> > > >     Link: <https://www.linuxfoundation.org/blog/blog/copyright-notices-in-open-source-software-projects>
> > > 
> > > So I read this last link, and see
> > > 
> > > "Don’t change someone else’s copyright notice without their permission
> > > You should not change or remove someone else’s copyright notice unless
> > > they have expressly (in writing) permitted you to do so. This includes
> > > third parties’ notices in pre-existing code."
> > 
> > I understood that paragraph as not changing copyright notices from
> > people unrelated to the project.
> 
> I don't think so. But IMHO, it would be OK to provide the old copyright
> notices in an indirect way: put them in a different file and just give
> a reference to this file, as long as this file is distributed together
> with the man pages and can be found easily.

Hmmm, I considered that the copyright attributed to the contributors
and then a CREDITS file that lists the contributors is an indirect way
of keeping the notices.  The CREDITS file is distributed together with
the manual pages, and can be found easily (root of the repo).  It
doesn't keep the original notice text verbatim, though.


Have a lovely day!
Alex

-- 
<https://www.alejandro-colomar.es/>

Download attachment "signature.asc" of type "application/pgp-signature" (834 bytes)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ