Closed nfitzen closed 2 years ago
@SeanDaBlack thoughts?
Current contributors:
@SeanDaBlack @andria-dev @steph-query @ChrisBremseth @ramblingjordan @erikedlund @jacobmovingfwd
I for one would very much support an open source license.
I fully agree
100%
Let's do it.
Agreed
I think we have a quorum on this. @jacobmovingfwd is the only one not to reply so far, but his contribution is a (very helpful) data set, but not any logic.
I'll look into setting this up!
Any preferences on license? I've used Apache, GNU 3.0, and MIT in a few different cases. Couldn't tell you the differences off the top of my head.
I like Creative Commons, but just from an aesthetic pov, I don't know about the legal differences at all.
@jacobmovingfwd Creative Commons shouldn't be used for software.
Any preferences on license? I've used Apache, GNU 3.0, and MIT in a few different cases. Couldn't tell you the differences off the top of my head.
@ramblingjordan GPL-3.0-or-later
is good unless there might be an issue of nonfree dependencies, or if the program is too short to warrant it. Edit: It's a copyleft license. Expat/MIT
is a simple all-permissive license that has a warranty disclaimer and a copyright notice. Apache-2.0
most notably includes a patent grant.
Sounds like MIT might be the best option, lets us use any dependencies we might need if I understand that correctly?
Any objections? (Will give some time to let people reply)
Sounds like MIT might be the best option, lets us use any dependencies we might need if I understand that correctly?
Any objections? (Will give some time to let people reply)
The LGPL will let you use non-free dependencies! That way your code can still remain free.
The LGPL will let you use non-free dependencies! That way your code can still remain free.
@FOSSilizedDaemon not true. The LGPL allows the code to be used as a dependency to nonfree code. We're considering the opposite; namely, that this code accidentally linked against a nonfree library.
Either way, the code is simple enough (< 300 lines) that Expat is a perfectly fine choice.
Any objections? (Will give some time to let people reply)
@ramblingjordan By the way - I wouldn't accept more contributions until this gets sorted. Copyright licensing is an opt-in system, and each new contributor has to explicitly agree until you specify a license in the repo (and then GitHub's ToS does the rest of the work).
I'm going to make a PR if everyone's decided on Expat/MIT
that indicates licenses according to the REUSE guidelines. That way, it can be as simple as assigning the PR to every contributor.
Good call. Can you hold off just for a bit. We're going to move the repository to my account so we can manage things better and give @SeanDaBlack a break from the monster he's unleashed.
fyi i have reported that user spamming the issues to github for abuse. since, this shit is just insane.
The LGPL will let you use non-free dependencies! That way your code can still remain free.
@FOSSilizedDaemon not true. The LGPL allows the code to be used as a dependency to nonfree code. We're considering the opposite; namely, that this code accidentally linked against a nonfree library.
Either way, the code is simple enough (< 300 lines) that Expat is a perfectly fine choice.
Ahhh my bad, I am still learning about liscening myself so I will stay tuned to this thread in hopes of learning more.
We split the work into multiple repos all with licenses. Thanks!
Would it be possible to add a free software license to this code, such as Expat/
MIT
,Apache-2.0
, orGPL-3.0-or-later
? (See also the GNU Project's license recs and FSFE'S REUSE guidelines.)Also, all significant contributors (what that means will be up to your lawyer) will need to approve these changes, because copyright law.
(Obligatory "IANAL, this is not legal advice" statement here. I just think it's mildly ironic that this tool isn't free.)