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

Small Licensing Question #28

Open
9 tasks done
Granock opened this issue Nov 14, 2024 · 10 comments
Open
9 tasks done

Small Licensing Question #28

Granock opened this issue Nov 14, 2024 · 10 comments
Assignees

Comments

@Granock
Copy link

Granock commented Nov 14, 2024

Netstone itself is AGPLv3 licensed which requires you to publish all your sourcecode, including your own application even across process boundaries, on request, when users can access it.
Other lodestoneparsers like nodestone or gostone are mit-licensed.

is there a specific reason that only netstone is licensed under a strong copy-left license and those other parsers are licensed in a less restrictive way?

Update:

List of contributors:

  • goaats
  • Koenari
  • karashiiro
  • Tawmy
  • WesselKuipers
  • corielljacob
  • ge7nic
  • istMiyo
  • twobe7
@goaaats
Copy link
Collaborator

goaaats commented Nov 14, 2024

It used to be my default license, I sadly didn't think too much about it when I set up this repo. I wouldn't mind relicensing to something more permissive whatsoever, probably MIT.

Most of the code is from @Koenari and me, we could probably reach out to the other people that have contributed and get their approval.

@Koenari Koenari self-assigned this Nov 15, 2024
@Koenari
Copy link
Collaborator

Koenari commented Nov 15, 2024

I do not mind switching the license to MIT. I personally default to MIT now.
I will reach out to all the contributors and get approval. Since I have a lot of work to do in my day job I can't really give an ETA though

@karashiiro
Copy link
Member

I approve of switching to MIT.

@Granock
Copy link
Author

Granock commented Nov 15, 2024

I updated the issue with a list of all contributors that github shows, so it is easier to track who has responded. Hope that helps

@twobe7
Copy link
Contributor

twobe7 commented Dec 21, 2024

I updated the issue with a list of all contributors that github shows, so it is easier to track who has responded. Hope that helps

I wasn't in the list but I am down as a contributor (super minor) so for what it's worth, I too approve of switching to MIT.

@Tawmy
Copy link
Contributor

Tawmy commented Dec 22, 2024

Hey, thank you for reaching out. I do not mind the switch either, MIT sounds good.

@ge7nic
Copy link
Contributor

ge7nic commented Dec 22, 2024

Sure, also approve of switching to MIT.

@corielljacob
Copy link
Contributor

I approve of the switch! Thanks for gathering input, even from tiny contributors like me.

@WesselKuipers
Copy link
Contributor

Sounds good to me! I approve of switching to MIT 👍

@itsMiyo
Copy link
Contributor

itsMiyo commented Dec 22, 2024

MIT is good with me too. Thanks for reaching out to confirm.

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

10 participants