Vaadin lets you build secure, UX-first PWAs entirely in Java.
Free ebook & tutorial.
Contributing and commit access
Tomasz Przybysz: Speaking about contribution. Is there any specific condition to become commiter?
Good question and multiple answers.
1) Contributing back to official Vaadin projects (Vaadin Framework, Vaadin TestBench, ...)
Please send patches attached to tickets at dev.vaadin.com. In many cases, the patch is used as a reference and core development team rewrites the feature. For more sizable contributions that are integrated directly integrated you have to sign a contributors agreement moving the rights to the code to Vaadin Ltd to keep the IPR:s for Vaadin projects clear and safe everyone involved. If you become a regular contributor and several of your patches get integrated, you will be considered for a commit access to the project directly.
2) Contributing back to some other project in dev.vaadin.com/svn (incubator or contrib)
Contact the author of the project. If he accepts you as a committer, you can contact me to get commit access.
3) Contributing back to project outside *.vaadin.com (for example github or code.google.com)
Contact the author. He can also arrange you a commit access.
4) Creating a new project in dev.vaadin.com/svn (incubator or contrib)
As there are already tons of projects, it is better in most cases to use code.google.com, githug or something else. If you really really want to host your project at svn.vaadin.com, contact me.
5) Creating a new project outside *.vaadin.com (for example github or code.google.com)
Feel free to do so :)
Whenever you are creating a new project, please also consider the guidelines for name use. (cut-n-paste from the http://vaadin.com/terms-of-service):
You may not use Vaadin, Vaadin product names or any other trademarks or trade names, whether registered or not, of Vaadin, or any similar mark or name, as Software trademark or trade name or for Software's marketing or advertising purposes. However, you may refer to Vaadin and its products to indicate interoperability between your Software and Vaadin and/or Vaadin Framework. For example you may name your Software "XYZ for Vaadin" but not "VaadinXYZ" or "XYZVaadin". Only Vaadin Ltd. is allowed to use com.vaadin.* package names for application programming interfaces (Java package names). Vaadin community members are allowed, but not required, to use org.vaadin.* package names for application programming interfaces (Java package names) in Software distributed in the Service with an open source license.
Thanks for reply and even extending the subject :)
It seems that project of my interest is hosted here: http://plugins.grails.org/grails-vaadin so I was about to contact the author(s) directly not the Vaadin dev team (exactly like you specified at point 3).
The first place I found any contact possibility with authors was Vaadin forum though.
That's why I asked in reply to Daniel's post. He's among the plugin authors.
However he's probably not subscribed to the thread as I have no answer till now.
Maybe I try contact Les or look for contact option with them elsewhere.
Btw. doesn't mentioned plugin name violate 'Vaadin' word usage terms? ;)