Re: Nexus Indexer code donation
Just an update: I was waiting for the code to be released so I could grab a stable tag to put into the ip process. The Nexus 1.5 release contains the Nexus Indexer 2.0.4 release so that's the code I'll use to start the process this week. On Tue, Jan 12, 2010 at 10:24 PM, Brian Fox bri...@infinity.nu wrote: The Maven PMC has voted to move forward with the Indexer code donation. We will need to move next into the ip clearance phase. We have also voted to add Brian Demers, Damian Bradicich and Tamas Cservanak as Maven committers to help support the new code. --Brian Fox Maven PMC Char On Thu, Jan 7, 2010 at 9:55 AM, Brian Fox bri...@infinity.nu wrote: What is your proposal here - did you want to vote those 3 people in as committers on the basis of the contribution, or will the existing committers apply patches until the rest of us get to know them? (I don't know who they are, so we may already). Funnily enough these alternatives have been a current topic on gene...@incubator for other projects :) I was intentionally vague because I didn't want to imply any type of contingency on the committers coming with the code. The committers are Tamas Cservanak, Damian Bradicich and Brian Demers. They've all been around the periphery of Maven for a while now, on the lists and irc etc. It would certainly make maintenance easier if they had commit access, but we can judge that on merits separate from the code. I did review the incubator threads and it seemed to be the consensus that the incubator has it's hands full and that projects should incubate subproject code where applicable. I see no value in trying to bring this code in through the full incubator since any new committers are already familiar with the process and we have proper mentors available. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Nexus Indexer code donation
On 28/01/2010, at 8:58 AM, Brian Fox wrote: Just an update: I was waiting for the code to be released so I could grab a stable tag to put into the ip process. The Nexus 1.5 release contains the Nexus Indexer 2.0.4 release so that's the code I'll use to start the process this week. Thanks! Will the license and headers be changed over before the donation? Cheers, Brett -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Nexus Indexer code donation
Will the license and headers be changed over before the donation? Yes. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Nexus Indexer code donation
The Maven PMC has voted to move forward with the Indexer code donation. We will need to move next into the ip clearance phase. We have also voted to add Brian Demers, Damian Bradicich and Tamas Cservanak as Maven committers to help support the new code. --Brian Fox Maven PMC Char On Thu, Jan 7, 2010 at 9:55 AM, Brian Fox bri...@infinity.nu wrote: What is your proposal here - did you want to vote those 3 people in as committers on the basis of the contribution, or will the existing committers apply patches until the rest of us get to know them? (I don't know who they are, so we may already). Funnily enough these alternatives have been a current topic on gene...@incubator for other projects :) I was intentionally vague because I didn't want to imply any type of contingency on the committers coming with the code. The committers are Tamas Cservanak, Damian Bradicich and Brian Demers. They've all been around the periphery of Maven for a while now, on the lists and irc etc. It would certainly make maintenance easier if they had commit access, but we can judge that on merits separate from the code. I did review the incubator threads and it seemed to be the consensus that the incubator has it's hands full and that projects should incubate subproject code where applicable. I see no value in trying to bring this code in through the full incubator since any new committers are already familiar with the process and we have proper mentors available. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Nexus Indexer code donation
What is your proposal here - did you want to vote those 3 people in as committers on the basis of the contribution, or will the existing committers apply patches until the rest of us get to know them? (I don't know who they are, so we may already). Funnily enough these alternatives have been a current topic on gene...@incubator for other projects :) I was intentionally vague because I didn't want to imply any type of contingency on the committers coming with the code. The committers are Tamas Cservanak, Damian Bradicich and Brian Demers. They've all been around the periphery of Maven for a while now, on the lists and irc etc. It would certainly make maintenance easier if they had commit access, but we can judge that on merits separate from the code. I did review the incubator threads and it seemed to be the consensus that the incubator has it's hands full and that projects should incubate subproject code where applicable. I see no value in trying to bring this code in through the full incubator since any new committers are already familiar with the process and we have proper mentors available. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Nexus Indexer code donation
On 08/01/2010, at 1:55 AM, Brian Fox wrote: What is your proposal here - did you want to vote those 3 people in as committers on the basis of the contribution, or will the existing committers apply patches until the rest of us get to know them? (I don't know who they are, so we may already). Funnily enough these alternatives have been a current topic on gene...@incubator for other projects :) I was intentionally vague because I didn't want to imply any type of contingency on the committers coming with the code. The committers are Tamas Cservanak, Damian Bradicich and Brian Demers. They've all been around the periphery of Maven for a while now, on the lists and irc etc. It would certainly make maintenance easier if they had commit access, but we can judge that on merits separate from the code. Makes sense. I did review the incubator threads and it seemed to be the consensus that the incubator has it's hands full and that projects should incubate subproject code where applicable. I see no value in trying to bring this code in through the full incubator since any new committers are already familiar with the process and we have proper mentors available. Absolutely. I think there are times when incubating a subproject makes sense, but not necessary in this case. -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Nexus Indexer code donation
Since it was first published several years ago, the Nexus Maven Repository Index has become the defacto standard for gathering information about remote repositories and is currently in use by all the repository managers and IDE integrations. The Nexus index of Central is currently downloaded more than 2 million times a month, consisting of 12TB of data a month. The index as I see it consists of two things: 1) The binary format that is used for the transport and 2) the code that produces and consumes the binary format. This code has been exclusively developed at Sonatype and is currently EPL licensed. We feel that interoperability is a key driver of the Maven ecosystem and the index should be included. We would like to propose relicensing the code to ASL and donate it to the Maven project where it can become part of the official Maven repository standard. We have been gathering documentation about the Index here[1] In addition to that, we have created a metadata format that is used to convey key pieces of information about a repository. You can read more about it in my comments here[2]. We would like to contribute this code as well, since this will further aid interoperability. Once we get this completed, we will have a good start to being able to produce a TCK that can be used to test and certify interoperability of various clients. [1] https://docs.sonatype.com/display/NX/Nexus+Indexer [2] http://java.dzone.com/articles/tale-two-repository-managers All the Indexer IP is owned by Sonatype and there are only three active developers that aren't currently Maven Committers, so this should be pretty easy process wise. Assuming no one has concerns accepting this code into the project, I'll move forward with the various formal votes and paperwork. Brian Fox --- Chair, Apache Maven PMC VP Eng. Sonatype, Inc. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Nexus Indexer code donation
On 07/01/2010, at 1:04 PM, Brian Fox wrote: We would like to propose relicensing the code to ASL and donate it to the Maven project where it can become part of the official Maven repository standard. We have been gathering documentation about the Index here[1] A huge +1 - I've been in favour of at least standardising the format here for a couple of years and this is an even better step. That's great news. In addition to that, we have created a metadata format that is used to convey key pieces of information about a repository. You can read more about it in my comments here[2]. We would like to contribute this code as well, since this will further aid interoperability. Again +1, your comments today prompted me to ask this but you beat me to it. I think we had a long standing issue to create some root repository metadata so adopting this as a standard makes sense so that they don't diverge. It'd be great to get the mirroring support into the core of Maven as well. All the Indexer IP is owned by Sonatype and there are only three active developers that aren't currently Maven Committers, so this should be pretty easy process wise. Assuming no one has concerns accepting this code into the project, I'll move forward with the various formal votes and paperwork. What is your proposal here - did you want to vote those 3 people in as committers on the basis of the contribution, or will the existing committers apply patches until the rest of us get to know them? (I don't know who they are, so we may already). Funnily enough these alternatives have been a current topic on gene...@incubator for other projects :) Thanks, Brett -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
