-
Notifications
You must be signed in to change notification settings - Fork 849
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
License Question #657
Comments
CC @adrianheine While I understand AGPL's uses, I second the request to change the official plugins to a license compatible with MIT which Acorn itself uses, like MIT. |
This is a reasonable request and I was expecting it to come up. As a side-note, I don't consider the plugins to be official, and as far as I know the (other) acorn maintainers neither endorsed nor reviewed them. However, they are under the acornjs organization, so they are not ›just some plugins‹, either. As for the license, I default to AGPL and figured I could switch once the need arises. I would prefer APL over MIT, but it probably makes sense to just follow acorn itself and use MIT. |
@adrianheine Ping. |
@TimothyGu As I added to all of the plugin's READMEs in the meantime: if the license of one of them is a problem for your use-case, please open an issue with the specific plugin describing your use-case. My understanding is that eslint is not actually interested in them currently. |
I'd like to ask Acorn team about the license of stage-3 plugins.
Context:
We have a discussion whether we add supports stage-3 syntactic features to ESLint or not: eslint/eslint#9804
In the discussion, I mentioned
acornjs
org and official stage-3 plugins.However, we don't seem to be able to use those because of license compatibility.
Question:
Is there a possibility to consider those license to change to the same as acorn core?
I'm sorry if I offended you.
Thank you.
The text was updated successfully, but these errors were encountered: