Hi Ian, On Fri, Apr 17, 2009 at 10:10 AM, Ian Boston <[email protected]> wrote: > We (Sakai Kernel Development Team), are starting to create a number of OSGi > bundles and services as extensions to Sling. They are all A2 licensed (why > would you choose anything else :)). Without wanting to bloat the Sling code > base unnecessarily, is there interest in code contributions to Sling?, or at > least co-ordination to avoid duplication. (and stupid mistakes on our part)...
I think we're particularly interested in contributions that are of general interest - JAX-RS, Guice integration, XML-related tools, those things stand out after having a quick look at your github stuff. Such contributions should be sustainable for the Sling project. Simple enough modules that we're confident we can maintain ourselves can be fine, and good automated tests also help a lot in making code sustainable. I think the best would be sustained contributions from the Sakai people, that might lead us to make some of the Sakai committers Sling committers as well, following the usual merit-driven procedure of course. Given that you are already a committer on Shindig, I won't need months before pushing to make you a committer once I see good stuff here...but the final decision is in the hands of the Sling PPMC and Incubator PMC of course. We are willing to expand the Sling community, and having more ties between Sakai and Sling makes a lot of sense IMHO, as we discussed at ApacheCon (FYI Sling folks, some people from the Sakai team were around and we had good informal discussions about possible synergies). Right now, the best might be for you guys to suggest some modules that could be contributed to Sling, and we can take if from there. -Bertrand
