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

Auto-publish hediet.vscode-drawio #93

Merged
merged 1 commit into from
Sep 25, 2020
Merged

Auto-publish hediet.vscode-drawio #93

merged 1 commit into from
Sep 25, 2020

Conversation

mattburgess
Copy link
Contributor

No description provided.

@jankeromnes
Copy link
Collaborator

Hi @mattburgess, many thanks for this contribution!

Note that this extension was also requested in #51

Unfortunately, we cannot auto-publish it from this repository, because this extension is licensed under GPL-3.0, which is incompatible with the Eclipse Public License used by OpenVSX and associated tools: #49 (comment)

@mattburgess
Copy link
Contributor Author

Ah; I skimmed that issue and thought it was waiting on some API compatibility issue to be resolved, I didn't click that it had actually been rejected on licensing grounds.

Does the restriction just mean that it can't be auto-published, or is it a stronger restriction meaning that even the upstream authors can't publish it to open-vsx at all?

@jankeromnes
Copy link
Collaborator

Ah; I skimmed that issue and thought it was waiting on some API compatibility issue to be resolved, I didn't click that it had actually been rejected on licensing grounds.

That's likely our fault for not being super clear, because the questions around licenses were new to us as well.

Does the restriction just mean that it can't be auto-published, or is it a stronger restriction meaning that even the upstream authors can't publish it to open-vsx at all?

Good question. @spoenemann do you know what would happen if the author of a GPL-3.0 licensed extension wants to publish the extension to OpenVSX?

@spoenemann
Copy link
Collaborator

I think it doesn't matter who publishes the extension. The restriction is really about the license.

@spoenemann
Copy link
Collaborator

Closing due to incompatible license.

@spoenemann spoenemann closed this Aug 21, 2020
@jankeromnes
Copy link
Collaborator

@mattburgess Good news! The Eclipse board may soon allow all "standard" open-source licensed extensions onto OpenVSX. While no official final decision has been announced yet, we consider this to be very promising, and have decided to accept your contribution now. Many thanks!

@jankeromnes jankeromnes reopened this Sep 25, 2020
@jankeromnes jankeromnes merged commit f4a8b06 into EclipseFdn:master Sep 25, 2020
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

Successfully merging this pull request may close these issues.

3 participants