The rest of this entry will explain why Ruby on Netbeans is important and how the community can support this effort. Hopefully, by the time you are done reading this, you will want to help out!
Why is NetBeans Ruby support important?
The truth is virtually every Java programmer on the planet is using one of a small handful of IDEs. The big ones are NetBeans, Eclipse, and Intellij. When a Java programmer decides to look at new language one of the first questions they ask is: Is there an IDE for it? Or...Does that run on NetBeans? JRuby (and Ruby) has quite a bit of motivation for Ruby support in Java IDEs because we see it as one less hurdle for a Java programmer who wants to try out Ruby.
This last paragraph may explain part of the motivation from the perspective of a Ruby evangelist... but it says nothing about the usefulness of Ruby on NetBeans. The editor is great. It has many conveniences like snippets, context sensitive navigation, live debugging, Rails support (2.x), and so much more. As a tool, it would be a great loss for all this work to disappear. As a programmer who spends most of his day in NetBeans, losing Ruby support would be a tragic loss.
A plea for contributors
I work on JRuby full-time. For me, hacking on NetBeans will be an OSS project where I contribute during my spare time. Several other JRuby folks will also volunteer some time under the same conditions: Yoko Harada, Charles Nutter, and Nick Sieger. Don’t be fooled though...you do not have to be a JRuby hacker to work on this project....in fact in the not-so-distant future you might not even need to to know any Java (more on this later).
Another treasure trove of expertise will come from Erno Mononen. Erno was one of the Ruby NetBeans engineers until his departure from Oracle. He makes no promises in how much time he can provide since he will also be contributing in his free time, but he should be an invaluable resource. Even if we only get to occasionally ask him questions.
Also Geertjan Wielenga, who has been helping answering questions about undertaking this community support and also pointing me towards NetBeans training resources has also offered his help.
So we have a few people who are offering to help make this a reality, but we can use all the help we can get. If you are interested in helping you should join the dev mailing list dev AT ruby.netbeans.org (instructions on how to access mailing: http://wiki.netbeans.org/RubyCommunityInformation). Introduce yourself and your interests in helping out.
We are going to continue to leverage as much of NetBeans infrastructure as we can. I mentioned continuing to use their mailing lists. We can continue to use their issue tracker. The hg repo will still remain the normative source for what gets released. However, in an attempt to make things easier to develop, we plan on mirroring the hg repo on github.com. Rubyists are huge git fans. Adding a git repository will lend a lot more visibility to the project. The git mirror has not been set up yet because we haven’t figured out how much of NetBeans should be mirrored.
By staying on NetBeans infrastructure it will be an easier path to get free continuous integration support on http://deadlock.netbeans.org/hudson and it will also make it simpler to integrate into NetBeans AutoUpdate process.
Stay tuned for announcements about the upcoming github mirror. At the same time we announce the mirror we should have a simplified document on how to build Ruby NetBeans.
0. Simplify the Build process so it is trivial to get started
Let's face it...cloning 1.2Gb to compile a module is a barrier to entry. It is possible to compile without cloning all of NB source, but specifying the 10+ Ruby-related projects you need to clone is a little confusing (to me at least :) ).
1. Restart continuous integration testing on http://deadlock.netbeans.org/hudson
2. Mirror hg source on github.com
This will be easy once we nail down simplifying the build process.
3. Unbundle JRuby source
Currently, a full version of JRuby’s source gets checked into the repository and then it gets patched. The delta of things patched is very small and we should be able to eliminate the need for patching.
We will still depend on JRuby as a jar (see next step).
4. Use JRuby embedding support to write portions of Ruby NetBeans in the Ruby language
All people interested in Ruby NetBeans support already know Ruby. Not all of them know Java. Having strategic portions written in Ruby will help improve the amount of contributions we get.
We shouldn’t go hog wild about replacing things which work already, but this is a good opportunity to implement new things in a way which will allow Ruby hackers to contribute to Ruby NB.
5. Re-prioritize issues and get volunteers to work on them
There are currently 600 open issues. Many of these will need to be re-prioritized based on the level of support we can provide.
Here are the some of the important ones:
- Rails 3 support (only Rails 2.3 current supported)
- Bundler support
- 1.9 syntax
People can come on the dev mailing list and talk about what they want to work on.
Ruby on NetBeans is already an impressive project, but like any OSS project it needs maintenance and care. If you think Ruby on NetBeans is important and you’re thinking about helping...please do. Even if you know nothing about NetBeans internals or you have never contributed to an OSS project before: Jump in head first! Getting involved in OSS is always a great learning experience and you will be a better person for it.