This forum is now a read-only archive. All commenting, posting, registration services have been turned off. Those needing community support and/or wanting to ask questions should refer to the Tag/Forum map, and to http://spring.io/questions for a curated list of stackoverflow tags that Pivotal engineers, and the community, monitor.
No announcement yet.
How can one contribute to Add-ons Development & EnhancementPage Title Module
As a community member i try to contribute with feedback and sugestions on Roo present and future features and use cases, there are a lot of community driven (directly or indirectly) jira issues.
Another contribution oportunity is the forum, i see a lot of basic questions being asked again and again, so it's easy to answer it and (hopefully) help a little.
About technical contributions, you can allways report bugs and requests for enhancements to Jira, in my experience they are allways wellcome by Roo's team. You can contribute patches as well (a first class technical contribution).
About addon development, well, all of us are anxious to develop addons , but until the API is stable (Roo is still in RC3) it's dangerous, you may well end with a lot of unusable code in your hands!
Re the Roo add-on API, I don't expect to be making any material changes to it going forward - at least not in the 1.x.x series. So it should be safe to write add-ons at this time. We're coming up for 1.0.0.RC4 shortly, so it's largely frozen what the add-on related APIs will look like at this time.
Anujk, you can register in Jira very easily, you don't need nothing special, once you have an account you can submit issues and patches.
But if you want to develop addons i recomend use a code hosting project like sourceforge, kenai or google code and host there (in svn) your code and files, the roo addon install facilities can easily pick the addon from that URL and install it, see the cloud foundry post for an example of such installation, once you have your addon a forum post could be a good way of anouncing it, as you can see Ben and Stefan are allways monitoring it.