Skip to content
This repository has been archived by the owner on Nov 21, 2018. It is now read-only.

License to all contributors or Public Domain maybe #1

Closed
Fishrock123 opened this issue Dec 3, 2014 · 10 comments
Closed

License to all contributors or Public Domain maybe #1

Fishrock123 opened this issue Dec 3, 2014 · 10 comments

Comments

@Fishrock123
Copy link
Contributor

Not sure if the former is possible.

@bnoordhuis
Copy link
Member

Is this a spiritual continuation of nodejs/node#34? I think it was pointed out in that issue that not all jurisdictions allow individuals (or non-governmental actors in general) to put things in the public domain.

@Fishrock123
Copy link
Contributor Author

jurisdictions allow individuals (or non-governmental actors in general) to put things in the public domain.

Right. Also, no, it is not a (direct?) continuation. This is for the website only. :)

@ghostbar
Copy link

ghostbar commented Dec 6, 2014

One is not exclusive of the other.

In order to license it public domain there needs to be copyright holders the license it as public domain.

Honestly, I would suggest MIT for any code and CC-by for content. Public Domain is very cool and definitely the goal for most of us but it's just too hard to actually accomplish.

@rlidwka
Copy link

rlidwka commented Dec 6, 2014

Public Domain is very cool and definitely the goal for most of us but it's just too hard to actually accomplish.

CC0 should be essentially the same as public domain.

@ghostbar
Copy link

ghostbar commented Dec 6, 2014

No, actually if you read the CC0 you can find:

4.a. No trademark or patent rights held by Affirmer are waived, abandoned, surrendered, licensed or
otherwise affected by this document.

Which differs a lot of the concept of public domain.

@therebelrobot
Copy link
Contributor

Any consensus on this? Maybe CC0? I'm cool licensing any of my work on the site to CC0 or any other open license we want.

@mikeal
Copy link
Contributor

mikeal commented Jan 15, 2015

I'd stick with MIT to match the main project. We should adopt the DCO and CoC of the main project as well.

@Fishrock123
Copy link
Contributor Author

I'd stick with MIT to match the main project.

ISC is MIT without legacy nonsense.

We should adopt the DCO and CoC of the main project as well.

Agreed.

@therebelrobot
Copy link
Contributor

+1 to the above

@therebelrobot
Copy link
Contributor

I'm pretty sure @mikeal committed the new ISC license into the repo. I'm gonna close this for now, but if it still needs to be addressed feel free to reopen.

mikeal added a commit that referenced this issue Jan 20, 2015
mikeal added a commit that referenced this issue Feb 8, 2015
snostorm pushed a commit that referenced this issue Feb 25, 2015
Initial translation of faq.md
snostorm pushed a commit that referenced this issue Mar 12, 2015
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

6 participants