Skip to content

License #3

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

Open
Watchful1 opened this issue Nov 28, 2014 · 4 comments
Open

License #3

Watchful1 opened this issue Nov 28, 2014 · 4 comments

Comments

@Watchful1
Copy link

This is mostly a formality, but RedGearCore is technically listed as all rights reserved on curse and has no license here. I haven't been able to find a statement from you anywhere else officially saying it's okay to include in modpacks.

Would you mind adding a license?

@DillonJettCallis
Copy link
Member

In order to add a license I'd first have to ..... care. I picked the all rights reserved because the number of options is long, confusing, and full of legal-sounding mumbo-jumbo I couldn't be bothered to read or care about.

@Watchful1
Copy link
Author

Well, as it happens, I'm the head of the FTB 3rd party pack system. So I spend a lot of time check packs for distributions permissions. Since there are a number of mod authors that do care, I try to be very strict about letting people add mods to their packs unless there's a specific statement from the author saying they have permission.

@lly11-01
Copy link

As a pack developer it is very unnerving for a mod, especially a coremod, to have such a reluctant stand on permissions. It gives me a bad first impression on your team, and I have debated on whether to keep it in my pack or to leave it out.
However, I do see a proper license set in place for your other mods Brewcraft and Geocraft. So on behalf of many pack developers, I ask whether RedGearCore would share the same license as Brewcraft and Geocraft. All we need is a simple answer and my doubts would be put to rest.

Thank you.

@MagmaBro123
Copy link

In order to add a license I'd first have to ..... care. I picked the all rights reserved because the number of options is long, confusing, and full of legal-sounding mumbo-jumbo I couldn't be bothered to read or care about.

Then simply don't make mods if your too lazy to do anything.

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

4 participants