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

Permission to wrap & distribute as a COM library under GPLv3? #910

Closed
retailcoder opened this issue Aug 29, 2019 · 3 comments
Closed

Permission to wrap & distribute as a COM library under GPLv3? #910

retailcoder opened this issue Aug 29, 2019 · 3 comments

Comments

@retailcoder
Copy link

Hi,

First of all, huge props to all Moq contributors - this package has changed my life!

I manage an OSS project licensed under GPLv3; Rubberduck is a COM add-in for the VBIDE (VB6/VBA6/VBA7 x86/x64) that aims to bring the legacy editor into this century with features that every modern IDE has - including navigational enhancements, static code analysis, refactorings... and a unit testing framework, to name a few.

There's a pull request that's been WIP for a while, that's solved all the hard parts and is now nearing completion; this pull request would give Rubberduck a full-blown mocking framework, by wrapping Moq into a COM-visible API that VBA/VB6 code can consume. This is a complete revolution in the VBA landscape, and I'd really want Moq to get all the praise it deserves from users of this future Rubberduck feature: there's no way that PR could have existed without Moq.

Now, I should probably have done this a couple of months ago, but I would like to ask for your permission to distribute this wrapper API (with proper attribution) as a Rubberduck feature, branded as a "Moq wrapper" - similar to how we ported the original Smart Indenter code (which was kindly offered to the Rubberduck project... under GPLv3) and now publicly brand it as a "Smart Indenter port".

Can we use the name "Moq" in "Moq wrapper API", or we should just call it some "Mocking API" that users would only know it's Moq under the hood if they looked at the project's attributions? Is the GPLv3 license a problem? If so, how can we make it work?

Thank you for your time!
Mathieu

@retailcoder
Copy link
Author

Linking #887

@stakx
Copy link
Contributor

stakx commented Aug 29, 2019

/cc @kzu

@kzu
Copy link
Member

kzu commented Aug 29, 2019

I don't have a problem at all. The conditions sound fair (attribution).

Thanks for asking and good luck with that cool new feature!

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