Follow-up Comment #36, sr #111226 (group administration): On Sun, Nov 02, 2025 at 06:49:43AM -0500, Hossein wrote: >> Just to be on the same page: when speaking about > 'files in the project', we discuss what the tarball contains---and in our > case, it's a working copy of the 'main' branch of your Git repository. Do I > mean the same as you? If yes, then a closer look is needed into how you make > that list. I find more. > > Yes we're on the same page. I'm afraid I don't find any other files, or my > grep command is mistaken `grep -RL GNU` shows exactly that list.
I see; this is where we diverge: you grepped for the word whereas
I looked for copyright and license notices.
>> This is too terse to see if the person who wrote this understands the
>> requirements.
>
> The files in the "./sources/man" folder are exactly one line therefore
> trivial. The guideline accepts this exception for very short files.
> NEWS, AUTHORS and TODO are metadata
I would classify them as 'documentation' or at least 'supporting
files' in terms of
www.gnu.org/prep/maintain/html_node/Copyright-Notices.html
As far as I understand it, metadata are access permissions,
timestamps, sizes and so on.
> (the first and last one could be generated by git for example)
How can the current texts of those files be generated by git?
> that are generally facts and not subject to copyright.
The facts are not subject to copyright. The selections of facts and their
expressions may be.
>> I don't think you've addressed one of my previous comments... their texts
>> are
>> not consistent
>
> It appears that I didn't send my reply to this one on my second attempt, when
> my initial text was not sent for some reason.
Sorry.
> Both texts show LGPLv3+, I didn't catch how they are in conflict with each
> other or could be misinterpreted/the reason for recommendation for a change.
First, the sets of copyright years differ; second, the wording
of the license notice is important. The current recommendation
was carefully designed by lawyers who used the experience of free
software community to avoid possible misunderstanding and other
issues. We may use terms like 'LGPLv3+' when we speak to each other
informally because the context makes the meaning quite certain,
however, one can't assume any user who gets the tarball will
understand it as well as we do in this conversation.
And generally, it isn't a good idea to do the same thing twice.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/support/?111226>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
signature.asc
Description: PGP signature
