Myself and my coworker work on Sakai and are also interested in contributing to Sling where needed. As things come up, we'll do our best to submit patches and such. As more of Sakai is ported to Sling, I'm sure our contributions will increase.
On Fri, Apr 17, 2009 at 04:10, 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) > > Current development tree is on github at > http://github.com/ieb/open-experiments/tree/master, its only been going a > few weeks. Most of the bundles of interest use the scr plugin. Some of the > Sling committers are lurking on our mailing list but I thought it would be > appropriate to mention it here to show real interest on our part. > > Ian >
