Open ZeroNetTickBot opened 5 years ago
GPLv3-only and Lax
GPLv3 and Lax
GPLv3+ and Lax
GPLv3+ and Lax
Making sure the second-half of the list of contributors get properly mentioned:
@xfq @6543 @ajmeese7 @AceLewis @megfault @zasei @artemmolotov @Nephos @Austin-Williams @bencevans @valkheim @d14na @thesoftwarejedi @Derson5 @dldx @EdenSG @camponez @Erkan-Yilmaz @Fil @gyulaweber @shakna-israel @flibustier @justinwiley @kseistrup @MRoci @sexybiggetje @BoboTiG @medimatrix @Nodeswitch @Ornataweaver @adrelanos @quasiyoke @Radtoo @RedbHawk @rcmorano @rubo77 @SuperSandro2000 @Thunder33345 @anonym @beigexperience @blurHY @dqwyy @eduaddad @goofy-mdn @krikmo @leycec @mnlg @mymage @probonopd @saber28
@rwv @sinkuu @zwgshr
GPLv3+ and Lax
GPLv3+ and Lax
GPLv3+
GPLv3+ and Lax
Just some useful information for people:
Sometimes open-source software projects get stuck in a license incompatibility situation. Often the only feasible way to resolve this situation is re-licensing of all participating software parts. For successful relicensing the agreement of all involved copyright holders, typically the developers, to a changed license is required. While in the free and open-source domain achieving 100% coverage of all authors is often impossible due to the many contributors involved, often it is assumed that a great majority is sufficient. For instance, Mozilla assumed an author coverage of 95% to be sufficient.[4] Others in the FOSS domain, as Eric S. Raymond, came to different conclusions regarding the requirements for relicensing of a whole code base.
Additionally, if you want to find out more about different licenses, http://tldrlegal.com seems to be a decent resource.
GPLv3+ and Lax
GPLv3+
GPLv3 and Lax
GPLv3+
GPLv3+ and Lax
Fewer choices was far better for achieving consensus.
Maybe.. but we shouldn't be dictating completely what people can choose from, because they have to choose it for themselves (legally). Also, I didn't really add that many more choices.
Basically, what I'm saying is if people naturally fall into a consensus regarding what they actutally want, then more choices doesn't matter. But if we are getting a consensus with less options but not a consensus with more options, then that just means we're kinda shoehorning people into a consensus when that's not what they really want.
The more important change in this update though was to clarify any ambiguity (this is important for legal reasons, along with understandability reasons), so I replaced "Apache" and "Apache-compatible" with "Lax" and was explicit about "Lax" not including the Public Domain.
GPLv3+ and Lax
Btw, polite discussion on licenses are welcome and you can change your vote at any time by posting another comment.
GPLv3 and Lax
@sirMackk @ysc3839 @mkg20001 @xfq @6543 @d14na @camponez @kseistrup @eduaddad @probonopd @skwerlman
I have just noticed that you voted for GPLv3+ . I want to make sure that the GPL options were clear enough, so let me explain it again:
GPLv3 and Lax
GPLv3-only and Lax
Relicensing as GPLv3 and Lax would be needed in case we make ZeroNet more modularized (#2063) in the future. In this case, ZeroNet libraries (protocol handling and other more low-level things) would then be licensed as Lax license (MIT/BSD). Complete ZeroNet program would then be licensed as GPLv3.
This could help making ZeroNet more popular as developers would have already-created modular libraries for extending/building with ZeroNet. Lax license would be needed as such licenses (MIT/BSD) have the ability to be used in most other licenses, so developers won't have to worry about license compatibility so much.
Lax
@goofy-mdn Just to make sure: choosing Lax means that we'll have to rewrite all libraries and make others support Lax as well, or remove your contributions. Are you fine with that?
Lax
Lax
Are you all sure guys?
GPLv3-only and Lax
Apache2
whatever the project decides is fine with me
GPLv3+ and Lax
whatever the project decides is fine with me
+1
GPLv3 and Lax
GPLv3+ and Lax
Choose what is best for you, I really have no issue with that ;)
Lax
GPLv3+
Here's another thought: whoever is licensing their work under lax licenses (i'm really just skipping through possible legal implications of formulating it like that, but oh well) gives anyone ability to license whole work under GPL (v3 in case of apache), however that would require some work on proper licensing every bit (if anyone cares, that is). In a similar vein, licensing a piece of code under GPLv3+ allows others to use/distribute/modify it under GPLv3 only.
@sirMackk @ysc3839 @mkg20001 @xfq @6543 @d14na @camponez @kseistrup @eduaddad @probonopd @skwerlman
I have just noticed that you voted for GPLv3+ . I want to make sure that the GPL options were clear enough, so let me explain it again:
- GPLv3-only allows us to license the project under the standard GPLv3 license
- GPLv3+ allows us to license the project under "GPLv3 or later" but not the standard GPLv3 license
- GPLv3 allows us to use either "GPLv3 or later" or the standard GPLv3 license, whatever we find better or more compatible
I'm not sure why that needed explanation.... but my vote is the same.
I only did 1 trivial commit so I don't think I should have a say. I am just commenting so you can cross me off.
GPLv3 and Lax
I only did 1 trivial commit so I don't think I should have a say. I am just commenting so you can cross me off.
+1
GPLv3+
GPLv3+
GPLv3+
Whatever @HelloZeroNet wants.
Hello to all previous ZeroNet contributors.
ZeroNet project has recently been informed of some license incompatibilities. Namely, we are using some Apache 2.0 and GPLv3 dependencies, whilst the current ZeroNet license is GPLv2. Thus, I would now ask the contributors to support GPLv3 switch.
A bot is listening on this thread. Please post exactly one of the following 13 comments:
Accepting the first case is recommended: GPLv3 ("and later" or "-only") would be used for ZeroNet core and Lax/Permissive licenses would be used for libraries.
Switching to a Lax/Permissive would require all GPL dependencies to be replaced. Not allowing the switch to a different license (therefore keeping GPLv2) would also require all GPLv3 dependencies, as well as Apache dependencies, to be replaced.
Notice: The term "Lax/Permissive license" used here does not include Public Domain licenses. They do, however, include BSD 2/3, MIT, ISC, and Apache-2.0
Statistics
Contributor list
@shortcutme: Doesn't care@imachug: GPLv3 and Lax@rllola: Doesn't care@tangdou1: GPLv3+@TheNain38: GPLv3-only and Lax@jerry-wolf: GPLv3 and Lax@radfish: Doesn't care@matthewrobertbell: Doesn't care@sirMackk: GPLv3+@Idealcoder: GPLv3@ysc3839: GPLv3+@filips123: GPLv3 and Lax@cclauss: GPLv3+@DaniellMesquita: GPLv3@n3r0-ch: Doesn't care@OliverCole: GPLv3 and Lax@geekless: GPLv3+@cxgreat2014: GPLv3+ and Lax@erqan: Doesn't care@iShift: Doesn't care@mkg20001: GPLv3+ and Lax@krixano: GPLv3 and Lax@Emeraude: Doesn't care@reezer: GPLv3 and Lax@danielquinn: GPLv3+@HostFat: GPLv3@JeremyRand: GPLv3+@volker48: Doesn't care@ppsfassa: Doesn't care@brunogarciavaz: Doesn't care@caryoscelus: GPLv3+@vitorio: GPLv3 and Lax@xfq: GPLv3+ and Lax@6543: GPLv3+ and Lax@ajmeese7: Doesn't care@AceLewis: Doesn't care@megfault: GPLv3 and Lax@zasei: Doesn't care@artemmolotov: Doesn't care@Nephos: Doesn't care@bencevans: GPLv3+@valkheim: GPLv3+@d14na: GPLv3+ and Lax@thesoftwarejedi: Doesn't care@dldx: Doesn't care@camponez: GPLv3+ and Lax@Fil: Doesn't care@gyulaweber: GPLv3+@shakna-israel: Blocking@flibustier: GPLv3 and Lax@kseistrup: GPLv3+@MRoci: GPLv3+@sexybiggetje: GPLv3+ and Lax@BoboTiG: Doesn't care@adrelanos: Doesn't care@quasiyoke: GPLv3 and Lax@Radtoo: GPLv3 and Lax@rubo77: GPLv3 and Lax@SuperSandro2000: Doesn't care@Thunder33345: Lax@anonym: Doesn't care@beigexperience: GPLv3 and Lax@blurHY: GPLv3+@dqwyy: Doesn't care@eduaddad: GPLv3+@goofy-mdn: Lax@mnlg: Doesn't care@mymage: GPLv3 and Lax@probonopd: GPLv3+ and Lax@saber28: GPLv3 and Lax@rwv: Doesn't care@sinkuu: GPLv3 and LaxPassing people
If you're not a contributor but you still want to support this or that option, you can post a comment as well. These comments will appear below.
@skwerlman: GPLv3+ and Lax@0x6a73: GPLv3-only and Lax@CatTheHacker: Lax@blazercrypter: GPLv3-only and Lax@alopexc0de: GPLv3-only and Lax@zeronettimemachine: GPLv3+@ghost: GPLv3+@CyberSecurityEngineer: GPLv3+@USAhas8000PlusNuclearBombForSelfDefense: GPLv3+@George-Soros: GPLv3+@Lambeosaurus: GPLv3+@Kusoneko: GPLv3 and Lax@decentralizedauthority: GPLv3+@canewsin: MIT/BSD2@russianagent: GPLv3+