Skip to content

Conversation

@dekkagaijin
Copy link

@dekkagaijin dekkagaijin commented Feb 7, 2018

I've seen way too many unattributed, closed source copies of your work in the past few hours. Adding strong copyleft protections will help nocode impact a wider audience.

I've seen way too many unattributed, closed source copies of your work in the past few hours. Adding string copyleft protections will help nocode be adopted by a wider audience.
@softprops
Copy link

Should nocode actually use no licence instead?

@trivikr
Copy link

trivikr commented Feb 7, 2018

+1 for No License

@jacktuck
Copy link

jacktuck commented Feb 7, 2018

+1 No license pls

@melwil
Copy link

melwil commented Feb 7, 2018

I'm not sure this project supports "No License", read the first line of the license:

When you make a creative work (which includes code) …

@jacktuck
Copy link

jacktuck commented Feb 7, 2018

@melwil Oh dear

@LordZane
Copy link

LordZane commented Feb 7, 2018

I read that as a creative work, such as code, and not a creative work that has to include code. This should qualify as a creative project, so it should be fine

@melwil
Copy link

melwil commented Feb 7, 2018

I completely agree, @LordZane. It was funny wording, however.

The funny best part of No License is that once the project has this, we get some additional sugar:

nobody else can use, copy, distribute, or modify your work … Once the work has other contributors (each a copyright holder), “nobody” starts including you.

So not only does nocode deploy nowhere, it can also be used by nobody. A sound win for No License, I would say.

@namoen0301
Copy link

Why not WTFPL?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants