Follow-up Comment #21, sr #111226 (group administration): Alright! Thanks again for the URLs. Let me know if my latest commit rectifies the problems. I have: 1. Removed the git2changelog which used GPLv2-or-later. 2. Made my own copyright claim in a new line.
I checked and the copyright notice is otherwise verbatim from the notice in [https://www.gnu.org/licenses/gpl-howto.html GPL HowTo]. I was also unable to find any other file that uses any other license, let me know if there are any. I also read a fair part of [http://www.gnu.org/licenses/gpl-faq.html#WhyMustIInclude GPL FAQ] and it was a nice rabbit-hole. > Hi Hossein: unless you plan to make it a GNU package, you can save yourself > tons of energy (and etc.) by staying on codeberg, which is certainly at least > passing the ethical repo standard (recent news learned from another source). > savannah doesn't offer much benefits over codeberg and the downside is too > apparent. This is the advice from a junior savannah hacker. Hi Luke! Thanks for the advice. Actually I'd love jcal to become a GNU package, however I am not the sole copyright holder and therefore I won't be able to do that. I am also aware of the shortcomings of Savannah. But as strict as the rules maybe, I like that I'm learning throughout the process. It's like having a mentor on licensing, which is nice and I'd love it if Codeberg offered it too. _______________________________________________________ Reply to this item at: <https://savannah.nongnu.org/support/?111226> _______________________________________________ Message sent via Savannah https://savannah.nongnu.org/
signature.asc
Description: PGP signature
