Follow-up Comment #34, sr #111226 (group administration): On Mon, Oct 27, 2025 at 03:44:14PM -0400, Hossein wrote: > > I made another commit that removes pyjalali docs that I didn't know how to > license and the reason for your question.
Savannah has certain hosting requirements. We have no resources
to continually check that every hosted package follows them, so we
have to rely on package maintainers to comply with them. This means
that we should make sure that the prospective admins understand
our hosting requirements and know how to follow them.
Is anyting still unclear to you?
> Currently the only files in the project that don't have the word "Copyright"
> or "GNU" are these:
>
> ./README.md
...
> ./.gitignore
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.
> I see no reason to add a copyright header to any of them.
This is too terse to see if the person who wrote this understands
the requirements. What would do is if you, for example, listed all
the reasons you've considered, and why they don't apply to each
file.
I'd also like to suggest to stick to common terminology:
there are valid copyright notices and valid license notices. Those
are distinct well-defined things, and the term to cover both
categories is 'legal notices'. If we use other wording, we
may miscommunicate.
> Let me know if there is any other thing that needs to be done.
I don't think you've addressed one of my previous comments,
> By the way, files like sources/man/jstrptime.3 include copyright
> and license notices twice, in comments at the top and at the
> bottom, and their texts are not consistent. I would recommend
> only leaving the user-visible one and updating it to the form
> recommended in GNU guidelines (another minor note is, GNU
> currently uses a HTTPS URL rather than HTTP in the license
> notices).
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/support/?111226>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
signature.asc
Description: PGP signature
