We've just applied as a mentoring organization for the Google Summer of Code 2011. Here a couple of project ideas students could pick from / expand upon. Feel free to suggest more in comments.
Whether we're accepted or not will be known by March 18th.
Most projects Projects will require a decent knowledge of Java and various libraries, as well as a good understand of web applications.
Necessary Magnolia introduction/training can be provided by the mentor.
Subversion and Maven experience a plus, but shouldn't be too much of a burden.
Unless otherwise stated, students will be mentored by Greg.
In no particular order:
| Table of Contents |
|---|
...
Our current module mechanism relies on discovering modules (Magnolia plug-ins, i.e jar or zip files) on the classpath. We'd like to be able to host those outside the web application, and be able to download, install and start them without having to restart the container. This might or might not involve OSGi. This will involve close-to-core work within Magnolia, its module mechanism and version handling mechanism.
It is also related to the store project described above.
...