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

Willing to migrate license to Apache 2.0? #19

Closed
tballison opened this issue Sep 5, 2017 · 10 comments
Closed

Willing to migrate license to Apache 2.0? #19

tballison opened this issue Sep 5, 2017 · 10 comments
Assignees

Comments

@tballison
Copy link
Contributor

I'm a committer on Apache Tika. It would be great to include parso to handle sas7bdat files. However, we can't include it with a GPL license. Is there any chance you'd be willing to migrate to Apache 2.0? Thank you!

@printsev printsev self-assigned this Sep 6, 2017
@printsev
Copy link
Contributor

printsev commented Sep 7, 2017

Hi Tim,

Thanks for your interest in parso. We will let you know as soon as we know more. By the way, would it work for you if parso is based on Java 8?

Igor

@tballison
Copy link
Contributor Author

Great. Thank you! We'll be migrating to Java 8 over the next month or so.

@printsev
Copy link
Contributor

OK, so we have the approval and desire to migrate to ALv2, I'm not sure when though.. We will try to finish it this year.

@tballison
Copy link
Contributor Author

tballison commented Sep 12, 2017

What fantastic news! There's no rush on our part, but this will be a great added capability. Let me know if a PR would be welcomed, or if it would be faster for you to handle it on your side. Thank you!

@chrismattmann
Copy link

awesome thank you!

@printsev
Copy link
Contributor

Thanks guys, we will do it on our side. Also we need to check what else should be included into this new version.

@tballison
Copy link
Contributor Author

W00t! THANK YOU!!! We're just about to migrate to Java 8 so we're ready to go. Thank you!!!

@printsev
Copy link
Contributor

This version is Java 6 compatible so you can use it - we were pretty short in time so 2.0.8 differs from 2.0.7 only in terms of the license unfortunately. We will try to fix #24 soon - stay tuned :)

@tballison
Copy link
Contributor Author

Got it. Thank you! And thank you @Gagravarr for being one step ahead of me. :)

@chrismattmann
Copy link

thank you! @printsev

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

3 participants