The amount of open source projects not following reuse and SPDX best practice is sad to see.
Checkout https://reuse.software/ , it is good thing to adopt for your software and makes it a lot more convenient to share code and ideas between projects while also respecting the software license. #KDE and the #Linux kernel massively make use of that.
@carlschwan Thanks for sharing.
@carlschwan Yet another thing to investigate for my todo list. I wish there was more automating for this, given author info is in git commit logs it feels it should be possible to auto-generate this.
@SylvieLorxu Here is a good starting point :) https://invent.kde.org/-/snippets/2770
Feel free to adapt it, it's licensed under MIT ;)
@SylvieLorxu And now I turned that into a very short blog post so that this doesn't get lost in a Gitlab snippet https://carlschwan.eu/2023/08/05/reuse-annotate-automation/ :)
If it helps, this may be a bit more precise (but more resource intensive)
I also made the following #FishShell command for it:
https://gitlab.com/hook/dotfiles#reuse-wrapper-for-existing-git-repos
It’s missing the copyright holder automation, because I feel that one is even more iffy to automate – if you decide to do that, at least make sure to differentiate between the Author and the Committer fields in #git
@hook @carlschwan Thanks y'all, made a new issue to look into this later when I have more time: https://github.com/CatimaLoyalty/Android/issues/1467
@SylvieLorxu, if you need help, happy to lend a hand with that. Thanks for Catima.
@hook @SylvieLorxu @carlschwan Looking into reuse for my own projects is still somewhere on my massive to-do list (though I do use SPDX headers). Happy to help figure out how we can use it for Catima (and then finally use it for my own projects too) :)
@hook @SylvieLorxu @carlschwan Thanks for the links.