-
Notifications
You must be signed in to change notification settings - Fork 58
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pick license(s) for this repo. #49
Comments
Would it make sense (and possible) to go with a modified version of the GnoPL? (basically more generic so we wouldn't be so tied to Gno) |
It is possible, but I believe Apache2 may be a better choice than GPLv3 as the base license for this case. For example, Tendermint2 will be under Apache2, while Gno.land and GnoVM will be under GPLv3 (GnoPL fork). In my opinion, Gno.land and GnoVM make more sense to enforce radical transparency and a radical FOSS ethos. I view AtomHub (and its modules) as similar to Tendermint2, providing increased flexibility while maintaining strong protections. I always rely on Jae's opinion for these topics because they are not widely known in this world, (ironically,) and he has more knowledge in this area. |
GnoNGPL is good: NewTendermint,LLC is better than GnuFoundation. Richard Stallman suggested that the unvaxxinated be herded up and sent to camps. I mean come on... More seriously, we made GnoNGPL (GNO Network General Public License) (which is basically a fork of AGPL) because we also needed two things: "strong attribution (e.g. linkback from website)", and to not rely on the GNU foundation if we ever need to create updates. But if you read the (A)GPLv3/GnoNGPL terms the rights of the GNU foundation or NewTendermint,LLC are limited. We can publish new versions but the programmer (if they specify the GnoNGPL version) or the user (if the programmer didn't specify the version) decides what version they want to use, so nobody can restrict your future rights. So in short, using the AGPLv3 (or GnoNGPLv3) or GPLv3 (or GnoGPLv3) doesn't make you depend on either the GNU Foundation, or NewTendermint,LLC. I'd like to think of NewTendermint,LLC as a tokenized foundation that can better adapt copyleft licensing needs for the blockchain.
It will remain copyleft, and differs to address new problems or concerns.
This gives the programmer (forker & contributors) and users more options; we can't restrict their existing rights. NOTE: We can still import any GPL or Apache2 or MIT or whatever licenses in here. Need for Strong attribution: In the very least, if you're (the figurative "you") going to fork this repo to create your chain, your chain had better link back to AtomOne and give proper attribution where users can see it, in the header or footer in the most prominent way. In the very least, when the website is regarding the genesis of your project, or that's the phase of the project you're in, or if it's in your whitepaper. Otherwise, you are just stealing from our collective ideas. This "strong attribution" term along with the GnoNGPL will help AtomOne and the greater ecosystem against frauds. With GnoNGPL we can also figure out appropriate strong attribution terms that require split/child chains to properly register themselves and better create common interfaces. Build the (genesis) rails and prescribe the course. I recommend everyone use GnoNGPL for now, and GnoNGPLv4 will be more complete, early next year. v3 is a work in progress. Also, Also, you know who benefits from Apache2? |
Okay, understood. Regarding Apache2, I fail to see who would benefit from it on Genesis alone. If this repository begins to receive code contributions, I recommend reconsidering whether this license is still the most suitable option. |
I suggest we make this entire repo GnoNGPL, so that any code contribution that goes in here is GnoNGPL, and this repo is a self-contained reproducing viral copyleft genesis toolkit. |
Perfect! |
Ok closing this. If there are any issues or objections or questions anyone can re-open. |
I generally support using Creative Commons or a similar license for no-code gems.
While I'm fond of the GnoPL for projects where we need to safeguard development time to create robust products, it's closely tied to Gno and the Gno Network, which may not suit all projects.
Therefore, my recommendation is to go with Apache2, potentially adding a term for X years of strong attribution to ensure credit is given where due.
Related with #46
The text was updated successfully, but these errors were encountered: