Comments (7)
Thanks for a kind reminder. It's one of the many things that I need to sort out before I can upload the plugin to Maven Central (and that's why I am keeping it here for now).
In summary, the situation is follows (if I myself understand the long history behind in correctly):
- The original plugin was deleloped by Gregory Kick from Google and was available on a branch of protobuf project. As such, it must have been covered by "New BSD License", link:
http://code.google.com/p/protobuf/source/browse/trunk/COPYING.txt - The branch was never merged into trunk for some reason. It was then taken over by David Trott and uploaded to GitHub 2 years ago: dtrott@dcf8f4e
- A few other people contributed through pull requests.
- Then I took over it on my fork, because our project needed my changes/fixes and David was too busy to merge my pull request.
IANAL, by my understanding is that if I am going to keep the project on GitHub, I can stick to the above liberal BSD licence, only extending "Copyright 2008, Google Inc." with an additional community copyright for the code that was added after taking the project over from Google. If I am going to promote the project to e.g. CodeHaus Mojo, I may need to relicense it under a dual Apache/BSD licence -- but that's something that needs to be clarified. If it comes to a legal deadlock, there's always an option to write a clean-room implementation.
from maven-protoc-plugin.
Would it make sense to go ahead now and stick to the BSD license? If you later decide to additionally license it under Apache, that should still be an option.
I can see changes I'd like to contribute (e.g. it would be nice to have the option to output generated python), but I'm hesitating because I don't know if I could then legally use the code. It makes me wonder if I might be best off forking the 2008 plugin that has clear license terms...I'd really rather do that though because as far as I can see, the changes since then have been good changes that I would rather not lose.
from maven-protoc-plugin.
Frankly speaking, I am more and more inclined to kick off a clean room implementation on clear licence terms. All the currently planned changes will require a pretty major refactoring of the entire plugin, and I think I can just as well start it afresh, retaining what's been done by me and Rob so far, and rewriting the rest. I reckon that "the rest" will amount to a very small portion of the current plugin's code.
from maven-protoc-plugin.
Hi @sergei-ivanov,
I would like to use this plugin in our project, but as there is no Licence we can't. Has anything changed in the last 3 years?
Thanks,
Nerses
from maven-protoc-plugin.
I am sorry to disappoint you, but unfortunately nothing really changed in that time: I haven't got resources for a clean rewrite, Google people haven't shown a commitment to adopt the project, CodeHaus dev community was not interested in it either.
from maven-protoc-plugin.
hiya - quick ping wrt to license. ping me on twitter @saturnism and let's chat.
from maven-protoc-plugin.
Hello all,
We managed to amicably resolve licensing issues with Google. The plugin has been licensed under Apache 2.0 licence, and it has a new home now:
https://github.com/xolstice/protobuf-maven-plugin
This repository will be locked down shortly. Please submit issues and pull requests to the new repository.
Thank you for your patience.
Kind regards,
Sergei
from maven-protoc-plugin.
Related Issues (20)
- Command line too long HOT 2
- Make clearing out of the output directory optional
- URL is no longer working HOT 3
- Add an option to attach descriptor set to the build
- Any in src/test/proto cause all protos defined in /src/main/proto to be generated in generated-test-sources HOT 10
- URL specified in pluginRepository goes to 404 location HOT 5
- Maven 3.2.5 breaks the toolchain support in the plugin
- Require at least java6 for running the plugin HOT 1
- Drop support for Maven2 and make Maven 3.0.0 the minimum required version HOT 2
- Clean up javadocs in order to appease doclint in java 8
- Plugin repository is busted HOT 2
- Add support for custom native plugins HOT 4
- Plugin location in README does not work HOT 3
- Proto file source in android APK file HOT 2
- Protoc is now available in the central repository HOT 1
- Preserve dependency ordering for protobuf imports HOT 1
- allow compiling dependent files HOT 1
- Configure .proto files path HOT 3
- push to maven central HOT 1
- Does this plugin have the option to generate C# code as well? HOT 3
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from maven-protoc-plugin.