Contrib bundles.

[Ian Boston <ie...@tfd.co.uk>]

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

Re: Contrib bundles.

[Felix Meschberger <fm...@gmail.com>]

Hi Ian,

Ian Boston schrieb:
> Bertrand,
> I will get some time dedicated to better unit tests. I suspect initially
> the lower lever modules like the ones you have mentioned are going to be
> better targets as they have fewer external bindings. I will let you know
> when bundles stabilize, and have > 90% test coverage. Personally I would
> be interested in a role within Sling, but only based on relevant merit
> and an ability to dedicate time to make a appropriate and continued
> contribution.

Personally, I think, if you (or others) could commit to maintain the
contributions, they need not be perfect at the time of contribution ;-)

And "a role within Sling" is generally a natural consequence of
maintaining the contributed stuff ;-)

Regards
Felix

> Ian
> On 17 Apr 2009, at 10:10, Bertrand Delacretaz wrote:
> 
>> Hi Ian,
>>
>> On Fri, Apr 17, 2009 at 10:10 AM, Ian Boston <ie...@tfd.co.uk> 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
> 
> 

Re: Contrib bundles.

[Ian Boston <ie...@tfd.co.uk>]

Bertrand,
I will get some time dedicated to better unit tests. I suspect  
initially the lower lever modules like the ones you have mentioned are  
going to be better targets as they have fewer external bindings. I  
will let you know when bundles stabilize, and have > 90% test  
coverage. Personally I would be interested in a role within Sling, but  
only based on relevant merit and an ability to dedicate time to make a  
appropriate and continued contribution.
Ian
On 17 Apr 2009, at 10:10, Bertrand Delacretaz wrote:

> Hi Ian,
>
> On Fri, Apr 17, 2009 at 10:10 AM, Ian Boston <ie...@tfd.co.uk> 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

Re: Contrib bundles.

[Bertrand Delacretaz <bd...@apache.org>]

Hi Ian,

On Fri, Apr 17, 2009 at 10:10 AM, Ian Boston <ie...@tfd.co.uk> 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

Re: Contrib bundles.

[Carl Hall <ca...@gmail.com>]

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 <ie...@tfd.co.uk> 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
>