gnuboot-patches
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH v2] site,site/news: add Spanish news translation and improve


From: Denis 'GNUtoo' Carikli
Subject: Re: [PATCH v2] site,site/news: add Spanish news translation and improve translations
Date: Fri, 26 Apr 2024 21:53:01 +0200

Hi,

On Thu, 18 Jan 2024 17:47:32 +0100
Adrien 'neox' Bourmault via Gnuboot-patches <gnuboot-patches@gnu.org>
wrote:
> Also it adds a licence file covering these translations : COPYING.es
[...]
>  site/COPYING.es                       |   8 +
> +Copyright (C) iShareFreedom <https://isf.neocities.org/>
> +
> +    Permission is granted to copy, distribute and/or modify this 
> +    document under the terms of the GNU Free Documentation License, 
> +    Version 1.3 or any later version published by the Free Software 
> +    Foundation; with no Invariant Sections, no Front-Cover Texts,
> and no 
> +    Back-Cover Texts. A copy of the license is included in the
> section 
> +    entitled "GNU Free Documentation License".

There are several issues with this part of the patch:
- There is already a COPYING file which contain the full license. And
  this file (which is supposed to replace COPYING if we follow the
  website generator file naming) doesn't contain the full license.
- This new file doesn't contain a translation.
- The translations are at least a combined work of all the authors
  that create the files that were translated, and possibly of the
  translator as well (here "isf").

A better way could be to find another place/file to add information
about the contributions. The commit messages already have to contain
proper authorship (here 'Jordán (isf)'), but since we already have
translations from the same author inside GNU Boot, a better way could
be to find where to add a work in progress ChangeLog for the next
release and mention that Jordán (isf) translated several files in
Spanish.

And while we're at it we could try to gather information about what
happened outside of git commits, like in the bug tracker and also try
to add that to the release ChangeLog somehow.

In any case it's better to have the copyright situation clarified
before reviewing the rest just to be on the safe side legally speaking.

Denis.

Attachment: pgpFiqxVFyZEe.pgp
Description: OpenPGP digital signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]