Follow

It's okay to publish code under a free software / open source license without starting a "project". Not every act of sharing code for others to use and/or build on is a "project". Which is something that studies about how many "projects" are "maintained" should keep in mind.

@johns Years ago there was a prominent person in the community who wanted to make these 'project' attributes a requirement for something to be labeled as 'open source'.

I just could not seem to get them to understand these are different (but related) concepts, but their ideas didn't get any traction with the rest of the community either so the problem solved itself.

This person literally told me that if I published my own code in a public repository with a GPLv3 (for example) license, they would not have considered that 'open source' on its own.

@kevin @johns
No, you obviously need a "Foundation" to manage the "Project" that maintains the code.

@johns @bodil Yea, I provide almost all the code I write as open source/free license as a courtesy.

In general, I promise no level of support. But if someone needs "My Silly Specific-Purpose Tool #527", I should at least give them the opportunity to modify it as they see fit :D.

Sign in to participate in the conversation
Librem Social

Librem Social is an opt-in public network. Messages are shared under Creative Commons BY-SA 4.0 license terms. Policy.

Stay safe. Please abide by our code of conduct.

(Source code)

image/svg+xml Librem Chat image/svg+xml