commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Matt Benson <>
Subject Re: [ALL] Commons JMS Project
Date Mon, 09 Jul 2012 21:08:39 GMT
I am still thinking this through... Commons policy permits any Apache
committer to start a sandbox component, but IMO it is tacitly implied
that the associated code come directly from the committer/s, or from
another Apache project.  This implies that this development would

- take place in the Incubator, probably sponsored by the Camel PMC,
with the stated hope of graduating as a Commons subproject, OR
- be created as a Camel subproject, with the Camel PMC handling the IP
clearance, THEN Camel developers copying the code to the Commons
sandbox (this feels a little unwieldy, though, TBH)

Alternatively, it's possible that the Commons PMC would decide that
having other Apache committers (e.g. Camel, CXF, etc.) manage
*contributed* IP in the sandbox is okay.  If existing Commons
developers are interested, then we have precedent to handle this type
of contribution in the sandbox (CSV) without further worry.  The other
TLPs' committers would still be encouraged to participate, of course.
Any comments from the rest of Commons on either point?

>From the IP perspective, the letter of foundation law requires that
the contribution be made via the IP clearance (sofware grant) process



On Mon, Jul 9, 2012 at 3:29 PM, Scott England-Sullivan
<> wrote:
> Matt is correct. I will ping my coworkers and see who would be available to help out
and we will go from there.
> Thanks,
> Scott ES
> On Jul 9, 2012, at 2:19 PM, Matt Benson <> wrote:
>> If Scott were an Apache committer (he is not), that would be true.  ;)
>> Instead, the situation is more complicated.  Is this component part
>> of the current Camel codebase?  If so (or even if not?), perhaps one
>> or more of the Camel committers would care to manage the code in the
>> Commons sandbox, from which point you, Scott, could participate as a
>> contributor (if the key one).
>> Matt
>> On Mon, Jul 9, 2012 at 3:15 PM, Luc Maisonobe <> wrote:
>>> On 09/07/2012 22:12, Scott England-Sullivan wrote:
>>>> Hello,
>>> Hi Scott,
>>>> I have developed a new component for the Apache Camel project written using
>>>> pure Java JMS APIs (the current component is a Spring JMS wrapper).  There
>>>> have been requests made to make the API pulled out of the Camel component
>>>> and to place them in a commons project for use by other projects (CXF) that
>>>> are looking to move away from the Spring JMS API.
>>>> As such I am looking for guidance on where to start.  The guides reference
>>>> contributing to current standing projects but not on how to create a
>>>> submission for a new commons project, namely, commons-jms.
>>>> Any help or pointers would be appreciated.
>>> You should probably start the component in the commons sandbox and from
>>> them gather a small community before being promoted to commons proper.
>>> best regards,
>>> Luc
>>>> Thanks in advance,
>>>> Scott ES
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail:
>>> For additional commands, e-mail:
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail:
>> For additional commands, e-mail:
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message