Skip to content
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

Change license to Creative Commons Zero #34

Closed
7 tasks done
Tracked by #61
Freso opened this issue Jul 6, 2017 · 10 comments
Closed
7 tasks done
Tracked by #61

Change license to Creative Commons Zero #34

Freso opened this issue Jul 6, 2017 · 10 comments

Comments

@Freso
Copy link
Member

Freso commented Jul 6, 2017

I would like to relicense the LOOT masterlists/repositories to be under the Creative Commons Zero license (effectively submit them to the public domain). See loot/loot.github.io#61 for more thoughts on this.

@MaddBomber83, @Sharlikran, @WrinklyNinja, @flatwhatson, @ExE-Boss, @Kinaga, @Arthmoor if you agree with moving to this much more free license, please write a comment confirming this.

@Ortham
Copy link
Member

Ortham commented Jul 7, 2017

I'm okay with this.

@ExE-Boss
Copy link
Contributor

ExE-Boss commented Jul 7, 2017

I’m also OK with this.

@flatwhatson
Copy link
Contributor

👍

@Sharlikran
Copy link
Member

Fine with me

@Arthmoor
Copy link
Contributor

Arthmoor commented Jul 7, 2017

I have no problem with this.

@Spu00Key
Copy link

Spu00Key commented Jul 8, 2017

I'll just have to echo @WrinklyNinja and question changing something on semantics. Does this change let us do something we can't do now, that we want to do now?

It's cool if it allows us to do more in the future, just question why now when we have nothing to balance against it.

Not important enough to me to be a thorn though. I'm ok with the change and appreciate the opportunity to provide input.

@Freso
Copy link
Member Author

Freso commented Jul 8, 2017

@MaddBomber83 I'll reply to you on the loot/loot issue.

@ExE-Boss
Copy link
Contributor

ExE-Boss commented Jul 13, 2017

It might be easier to contact @Kinaga on Nexus at Carriage and Ferry Travel Overhaul by Kinaga, which was added to the masterlist in PR #26.

@Kinaga
Copy link
Contributor

Kinaga commented Jul 27, 2017

I'm ok with this. Thank you for pming me on Nexus. Sorry if I held you up.

@Freso
Copy link
Member Author

Freso commented Jul 27, 2017

Thanks @Kinaga, and I assume @ExE-Boss for reaching out to them. :) (It was on me to-do list, but my to-do list is very long. >_<)

I have made a pull request now which I will merge in ~2 days if no objections are made by then: #38

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

No branches or pull requests

8 participants