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 <[email protected]> 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: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
