Discussion
Maintaining a #FreeSoftware project?
Make your licensing unambiguous (for humans and machines🤖 ) with REUSE. Used by @kde, the @Linux kernel, Siemens, @NGIZero projects, and more.
1️⃣ Choose and provide licenses
2️⃣ Add copyright and license information to each file
3️⃣ Confirm REUSE compliance
Get started ➡️ https://reuse.software/
@fsfe the immediate rebuttal i would raise to the straightforward claim that SPDX encodes "best practices" would be the sqlite blessing SPDX keyword: https://spdx.org/licenses/blessing.html
May you do good and not evil.
sqlite is well within its rights to put that in its own license file if it wants to! but it doesn't "clarify" a damn thing. the correct license for sqlite is "public domain". that SPDX wastes keywords on prozelytizing is not a terribly strong argument for its correspondence to "best practices"
@fsfe furthermore, there's this section https://reuse.software/faq/#copyright-holder-author
What is a copyright holder, and what is an author?
In these resources, we maintain a distinction between the copyright holder and the author.
it's......remarkably strange to summarize an answer to this very extensive question without linking to any external resources on the matter???
despite a multitude of implications and snide remarks on this "FAQ" page, there is no straightforward example on this page of "what might happen if the copyright/authorship distinction is unclear"
@fsfe the canonical example might be esr refusing to give up the copyright to ncurses, which he had contributed nothing to but had managed to finagle himself into an unofficial maintainership role.
does REUSE help with that? or does it instead work to obscure the distinction between copyright and authorship?
@fsfe @kde @NGIZero How to annotate AI/LLM-created/contributed content using REUSE? asked originally at https://github.com/fsfe/reuse-website/issues/127
Install bonfire.cafe
Get the full app experience
@fsfe @NGIZero having personally spent a great deal of time on python language packaging, i at first came to appreciate the REUSE methodology as a cross-language metadata format. however, i have a few concerns at this point, and it largely revolves around who the REUSE metadata is intended for. i really wish there was more of a discussion about what purposes this serves, particularly at the FAQ https://reuse.software/faq/
Frequently Asked Questions | REUSE