Re: Incubating with Apache Commons as champion?

2015-01-20 Thread Rob Vesse
Stian If a community made predominantly of existing Apache committers (or containing a strong core of) already exists and this would be a small self contained module as part of Apache Commons then why does the Incubator need be involved at all? Why can this not just be submitted directly to

Incubating with Apache Commons as champion?

2015-01-20 Thread Stian Soiland-Reyes
The discussion on dev@commons about coming-to-Apache Commons-RDF (https://github.com/commons-rdf/commons-rdf/) seems to be rejecting a temporary mailing list like rdf@commons as it is seen t be splitting Apache Commons as a project - the ideal committer on Apache Commons is caring about all its

Re: Incubating with Apache Commons as champion?

2015-01-20 Thread Niclas Hedhman
I agree that incoming codebase can go through the IP Clearance, and if the committers are already Commons folks (predominantly), and the only actual issue is the number of mails on the dev@, then I think that separate mailing list is fine, perhaps with the exception of not having a name related to

Re: Incubating with Apache Commons as champion?

2015-01-20 Thread Rob Vesse
Agreed The point that I was trying to make is that if those involved already understand the Apache Way going through Incubation for the sake of it seems a pointless exercise especially when the legal/IP aspects of things can be handled in other fashions. If you are in a position to simply

RE: Incubating with Apache Commons as champion?

2015-01-20 Thread Ross Gardler (MS OPEN TECH)
@incubator.apache.orgmailto:general@incubator.apache.org Subject: Re: Incubating with Apache Commons as champion? I agree that incoming codebase can go through the IP Clearance, and if the committers are already Commons folks (predominantly), and the only actual issue is the number of mails on the dev@, then I think

Re: Incubating with Apache Commons as champion?

2015-01-20 Thread Sergio Fernández
On 20/01/15 16:08, Rob Vesse wrote: On the other hand does Commons-RDF necessarily need to come to the ASF at all? If it is a small self-contained interface module that will remain stable what does it gain (other than brand association) by coming to the ASF? Well, this question eventually

Re: Incubating with Apache Commons as champion?

2015-01-20 Thread Stian Soiland-Reyes
Just because a lot of Apache committers are involved and could put things right into another project (or even propose a new TLP directly) doesn't mean it happens. https://wiki.apache.org/incubator/BeanShellProposal was voted -1 in the incubator because it had many Apache folks already and didn't

RE: Incubating with Apache Commons as champion?

2015-01-20 Thread Ross Gardler (MS OPEN TECH)
@incubator.apache.orgmailto:general@incubator.apache.org Subject: Re: Incubating with Apache Commons as champion? Stian If a community made predominantly of existing Apache committers (or containing a strong core of) already exists and this would be a small self contained module as part of Apache Commons then why does

Re: Incubating with Apache Commons as champion?

2015-01-20 Thread Sergio Fernández
On 20/01/15 15:28, Stian Soiland-Reyes wrote: The suggestion is that Commons-RDF could be a incubator project, but with a projected path to become part of the Apache Commons instead of a TLP. (I believe this path has not happened before) It did happened before:

Re: Incubating with Apache Commons as champion?

2015-01-20 Thread Andrea Pescetti
Stian Soiland-Reyes wrote: https://wiki.apache.org/incubator/BeanShellProposal was voted -1 in the incubator because it had many Apache folks already and didn't need to learn anything. Yet the project didn't move into Apache - perhaps because it didn't have any pressure or framework to go