People fight about licensing all the time. I try not to get involved, it's up the maintainer and their vision for the project. Everyone's going to make the wrong choice according to others. I generally work with GNU copy-left licenses. My vision is to preserve the project and protect the users of my project. My ideals for my projects are my own expectations. When you give me your source code, you shouldn't have control over what I get to do with it on my machine. Meaning I care that I protect my user's rights to use my software however they see fit, while preserving the project's existence. Make money off of it, but you have to give credit to the project, and you have to allow user's access to the source that built your app.
This changes heavily depending on the project though. Libraries lgpl is my go to. Apps are gpl2, and server stuff is AGPL. I want minimum "this is how you must use my project" but maximum "you must respect the project and user's freedom if you choose to use this"
I think MIT, BSD and Public Domain all have their place too though. Some devs just don't care and that's cool too, use it however you want. But just know that going into your project.
ChipTuner
npub1qd…3fqm7
2025-05-01 18:04:14
in reply to nevent1q…5zy3
Author Public Key
npub1qdjn8j4gwgmkj3k5un775nq6q3q7mguv5tvajstmkdsqdja2havq03fqm7Published at
2025-05-01 18:04:14Event JSON
{
"id": "412865bf55a811f96816c58018cef5ce03a322a79affb2479f568b199725c5ae",
"pubkey": "036533caa872376946d4e4fdea4c1a0441eda38ca2d9d9417bb36006cbaabf58",
"created_at": 1746122654,
"kind": 1,
"tags": [
[
"e",
"26fe9639298650a63cc2db24ff5400de380870c0a0df85ad195dc1fa923429d2",
"wss://theforest.nostr1.com/",
"root",
"ee9d979e7e1418a9f7472baf82dc96082a0d4251b77bcb170a6ecec93fadff64"
],
[
"e",
"26fe9639298650a63cc2db24ff5400de380870c0a0df85ad195dc1fa923429d2",
"wss://theforest.nostr1.com/",
"reply",
"ee9d979e7e1418a9f7472baf82dc96082a0d4251b77bcb170a6ecec93fadff64"
],
[
"p",
"ee9d979e7e1418a9f7472baf82dc96082a0d4251b77bcb170a6ecec93fadff64"
]
],
"content": "People fight about licensing all the time. I try not to get involved, it's up the maintainer and their vision for the project. Everyone's going to make the wrong choice according to others. I generally work with GNU copy-left licenses. My vision is to preserve the project and protect the users of my project. My ideals for my projects are my own expectations. When you give me your source code, you shouldn't have control over what I get to do with it on my machine. Meaning I care that I protect my user's rights to use my software however they see fit, while preserving the project's existence. Make money off of it, but you have to give credit to the project, and you have to allow user's access to the source that built your app. \n\nThis changes heavily depending on the project though. Libraries lgpl is my go to. Apps are gpl2, and server stuff is AGPL. I want minimum \"this is how you must use my project\" but maximum \"you must respect the project and user's freedom if you choose to use this\"\n\nI think MIT, BSD and Public Domain all have their place too though. Some devs just don't care and that's cool too, use it however you want. But just know that going into your project. ",
"sig": "f12d5e6e5b43425102b6f9036b14c596a5d522f2f0147aa09fb70bd55ae49f66df6eeb81d6adfb0a21fec72fbad9cb438f5d70b0ebcb4235a64e33067c41d38c"
}