During FOSDEM, I was approach by Martin Skurla (CC-ed on this e-mail), a
student, who said he'd love to see us apply for Google Summer of Code
(GSoC) as a mentoring organization, because he wants to work with us in
the program. He was specifically interested in working on the NetBeans
integration.
I thought this was a great idea. At the time I suggested that one
project idea is to enable NetBeans to see the static code analysis
results produced on the server, but later he found out that that's
already on the roadmap for NetBeans 7.2.
So I'm trying to solicit ideas for the possible project ideas for GSoC.
I'd like to come up with some ideas for Martin around NetBeans
integration, but any other ideas are also welcome.
As a rule of thumb, I believe GSoC projects need to be:
- moderately scoped so that someone can achieve it in a limited time
frame.
- ideally shouldn't require deep understanding of the existing stuff.
- open-ended problem that fosters creativity.
As for NetBeans, one possibility is the "pre-tested commit" feature
based on diff files --- we'll have NetBeans send us diff, then when we
build a job, we'd apply it on the source tree after checkout. It's got
some work on NB side and some work on Jenkins side, a nice mix.
For broader project ideas, I think some of the UI work we discussed in
FOSDEM would fit in nicely. Other ideas include:
- Gradle integration, similar to what we have for Ivy/Maven.
Probe what Gradle is doing, and auto archive stuff.
- Plugin development with Python via Jython
- Ruby plugin work. Code generators, wrappers, etc.
- Code generators for Java (like "jpi generate builder FooBuilder")
[1] http://wiki.netbeans.org/NewAndNoteworthyNB71#Hudson
--
Kohsuke Kawaguchi http://kohsuke.org/
