search

kelseyhightower / nocode

The best way to write secure and reliable applications. Write nothing; deploy nowhere.
Apache License 2.0
61.01k stars 4.72k forks source link

Can nocode be licensed under MIT License? #137

Closed trivikr closed 6 years ago

trivikr commented 6 years ago

It's shorter, simpler, less-restrictive than Apache 2.0

pbnj commented 6 years ago

If we've learned anything from React's licensing shenanigans is that having licenses is bad. No License seems fitting here.

asciifaceman commented 6 years ago

I recommend the implementation of an UNLICENSED.md file.

trivikr commented 6 years ago

How about WTFPL? Looks like it has also been requested in the past #94

akashmishra23 commented 6 years ago

How about NoLicense.md

asciifaceman commented 6 years ago

Isn't any license the implementation of esoteric legal code?

MarHoff commented 6 years ago

Guys this is serious I just had a confirmation of prior art in comments of another issue I opened

208 (Not sure if you can deploy nocode to yesterday)

I think it would be highly advisable and safer to switch project to nolicence as you are already starting to suggest. I really don't wan't that a legal battle based on prior art get in the way of this beautiful framework that is nocode.

Here's a draft I'm suggesting.

racerpeter commented 6 years ago

May I suggest NCL-1.0? https://github.com/kelseyhightower/nocode/pull/335

pbnj commented 6 years ago

@MarHoff - someone wrote a blog article about how NoLicense puts you in more risk of legal battle.

MarHoff commented 6 years ago

@petermbenjamin I really don’t no if old schemes applied to nocode seems like the most groundbreaking revolution since blockchain.

Unlike other solution nocode is offline self-repairing, self-deleting in case of security breach and consistently non existing event in when scaling up.

Nolicence text at all should then be more appropriate to handle no risk at all that come with implementing Nothing. Contrary to traditional licence the sole present of any text in the licence file seems to exponentially increase the risk of semantic misunderstanding of the licence text.

I grant you however that some confusion can arise for developers that come from a loosely typed language and might eventually confuse an empty string with nil or null.

westonal commented 6 years ago

This is a big concern to me, now I've seen this repo, are all my future works are now bound by the terms of the current license as derivative works?