Re: [PROPOSAL] Ivy
Upayavira wrote: Antoine Levy-Lambert wrote: If this is right, the software grant must be received and accepted before setting up the infrastructure (svn, mailing lists, ...). Software grant must be received before code can be imported into SVN. Other infra can be set up now (assuming a status page exists, which I think you've done). Agreed. You can even create the svn. Just hold off from import until you have an ack that the grant is received. Bill - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PROPOSAL] Ivy
Hi, I have updated the incubator web site. The changes should be visible within an hour. Ivy should then be visible in the Projects bar to the right of the site. Regards, Antoine Antoine Levy-Lambert wrote: Garrett Rooney wrote: Ahh, sorry, my bad. If you're already an ASF Member you should have write access to the appropriate places in the incubator tree. The web pages are all under /incubator/public, and the members group has write access there. True, I have added a file called ivy.xml, added ivy to site-author/stylesheets/project.xml, and regenerated the site, then committed my changes. This has generated surprisingly long diffs. I do not have incubator UNIX karma yet, it would be cool if someone with this karma could do a svn update under /www/incubator.apache.org. Regards, Antoine - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PROPOSAL] Ivy
On 10/30/06, Antoine Levy-Lambert [EMAIL PROTECTED] wrote: Hi, I have updated the incubator web site. The changes should be visible within an hour. Ivy should then be visible in the Projects bar to the right of the site. Great, I can see Ivy project page! I've tried to register to the mailing list but it isn't setup yet. I'll wait to send my first message :-) Xavier Regards, Antoine Antoine Levy-Lambert wrote: Garrett Rooney wrote: Ahh, sorry, my bad. If you're already an ASF Member you should have write access to the appropriate places in the incubator tree. The web pages are all under /incubator/public, and the members group has write access there. True, I have added a file called ivy.xml, added ivy to site-author/stylesheets/project.xml, and regenerated the site, then committed my changes. This has generated surprisingly long diffs. I do not have incubator UNIX karma yet, it would be cool if someone with this karma could do a svn update under /www/incubator.apache.org. Regards, Antoine - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PROPOSAL] Ivy
Hi, I am not familiar with the legal aspects of bringing an external codebase to the incubator. William Rowe wrote that jayasoft needs to fill in a software grant to the ASF. If this is right, the software grant must be received and accepted before setting up the infrastructure (svn, mailing lists, ...). Regards, Antoine Original-Nachricht Datum: Wed, 25 Oct 2006 05:48:26 -0500 Von: William A. Rowe, Jr. [EMAIL PROTECTED] An: general@incubator.apache.org Betreff: Re: [PROPOSAL] Ivy Xavier Hanin wrote: I've just sent both an individual and a corporate CLA by fax. I was not sure the corporate CLA was necessary, but since Jayasoft is the current copyright holder of Ivy, I thought it might be required. Probably a good idea; the point to a Corporate CLA is actually an agreement between your employer and yourself that what you do with the Foundation is with their blessing. The ICLA you signed claims you have that right already, but we all know how painful employment contracts and their covenants are :) Best to be safe for your benefit. There is a DIFFERENT form, a Software Grant, which would be needed for a wholesale import of a code base owned by another party. See http://www.apache.org/licenses/#grants (very bottom paragraph.) Bill - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PROPOSAL] Ivy
Antoine Levy-Lambert wrote: Hi, I am not familiar with the legal aspects of bringing an external codebase to the incubator. William Rowe wrote that jayasoft needs to fill in a software grant to the ASF. If this is right, the software grant must be received and accepted before setting up the infrastructure (svn, mailing lists, ...). Software grant must be received before code can be imported into SVN. Other infra can be set up now (assuming a status page exists, which I think you've done). Regards, Upayavira Original-Nachricht Datum: Wed, 25 Oct 2006 05:48:26 -0500 Von: William A. Rowe, Jr. [EMAIL PROTECTED] An: general@incubator.apache.org Betreff: Re: [PROPOSAL] Ivy Xavier Hanin wrote: I've just sent both an individual and a corporate CLA by fax. I was not sure the corporate CLA was necessary, but since Jayasoft is the current copyright holder of Ivy, I thought it might be required. Probably a good idea; the point to a Corporate CLA is actually an agreement between your employer and yourself that what you do with the Foundation is with their blessing. The ICLA you signed claims you have that right already, but we all know how painful employment contracts and their covenants are :) Best to be safe for your benefit. There is a DIFFERENT form, a Software Grant, which would be needed for a wholesale import of a code base owned by another party. See http://www.apache.org/licenses/#grants (very bottom paragraph.) Bill - 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]
Re: [PROPOSAL] Ivy
On 10/30/06, Antoine Levy-Lambert [EMAIL PROTECTED] wrote: Hi, I am not familiar with the legal aspects of bringing an external codebase to the incubator. William Rowe wrote that jayasoft needs to fill in a software grant to the ASF. Ok I'll fill and send a software grant tomorrow morning. Tell me if I need to do anything else. Xavier If this is right, the software grant must be received and accepted before setting up the infrastructure (svn, mailing lists, ...). Regards, Antoine Original-Nachricht Datum: Wed, 25 Oct 2006 05:48:26 -0500 Von: William A. Rowe, Jr. [EMAIL PROTECTED] An: general@incubator.apache.org Betreff: Re: [PROPOSAL] Ivy Xavier Hanin wrote: I've just sent both an individual and a corporate CLA by fax. I was not sure the corporate CLA was necessary, but since Jayasoft is the current copyright holder of Ivy, I thought it might be required. Probably a good idea; the point to a Corporate CLA is actually an agreement between your employer and yourself that what you do with the Foundation is with their blessing. The ICLA you signed claims you have that right already, but we all know how painful employment contracts and their covenants are :) Best to be safe for your benefit. There is a DIFFERENT form, a Software Grant, which would be needed for a wholesale import of a code base owned by another party. See http://www.apache.org/licenses/#grants (very bottom paragraph.) Bill - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: voting was Re: [PROPOSAL] Ivy
I wonder (out loud) if we might recommend to change the format of the [RESULT] [VOTE] tally to simply summarize the binding votes, just for completeness. Clearly, the people who need to know who the binding votes are already know it, and it doesn't strike folks quite in the face if they are not familiar. For example, +1: Sam Joe Charlie Wilson Megantreth Russell Phan (4 binding) +/-0: none -1: none The vote passes. Respectfully, Craig On Oct 23, 2006, at 5:59 PM, William A. Rowe, Jr. wrote: Geir Magnusson Jr. wrote: Might be nice to leave binding-ness as an accounting detail for the person running the vote, to get rid of the my vote counts, yours doesn't thing that David pointed out. After all, if you get consensus, and it's all +1s. Bingo. That was David's point - the chair knows if at least -3- of those +1's came from PMC. And other votes help advise us all of the entire communities' opinion. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Craig Russell Architect, Sun Java Enterprise System http://java.sun.com/products/jdo 408 276-5638 mailto:[EMAIL PROTECTED] P.S. A good JDO? O, Gasp! smime.p7s Description: S/MIME cryptographic signature
Re: [PROPOSAL] Ivy
Stephane Bailliez wrote: Xavier Hanin wrote: After several weeks of discussion with our user community [1] and with several Apache members, I am proud to present a proposal [2] for the open source project Ivy to join the Apache Incubator. I and all the Ivy team and user community hope you will consider this proposal carefully, and accept the project to join the foundation. +1 Likewise +1 Alex - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PROPOSAL] Ivy
On 10/23/06, Xavier Hanin [EMAIL PROTECTED] wrote: ...I and all the Ivy team and user community hope you will consider this proposal carefully, and accept the project to join the foundation... Late but warm +1 (assuming a +1 can be *warm* ;-) -Bertrand - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PROPOSAL] Ivy
Garrett Rooney wrote: Ahh, sorry, my bad. If you're already an ASF Member you should have write access to the appropriate places in the incubator tree. The web pages are all under /incubator/public, and the members group has write access there. True, I have added a file called ivy.xml, added ivy to site-author/stylesheets/project.xml, and regenerated the site, then committed my changes. This has generated surprisingly long diffs. I do not have incubator UNIX karma yet, it would be cool if someone with this karma could do a svn update under /www/incubator.apache.org. Regards, Antoine - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PROPOSAL] Ivy
On 10/25/06, Antoine Levy-Lambert [EMAIL PROTECTED] wrote: snip/ I suppose the Ivy committers need to send a CLA in any case ? Xavier, Maarten, maybe you should read this http://www.apache.org/dev/ and particularly this http://www.apache.org/dev/new-committers-guide.html. I've just sent both an individual and a corporate CLA by fax. I was not sure the corporate CLA was necessary, but since Jayasoft is the current copyright holder of Ivy, I thought it might be required. - Xavier
Re: [PROPOSAL] Ivy
Xavier Hanin wrote: I've just sent both an individual and a corporate CLA by fax. I was not sure the corporate CLA was necessary, but since Jayasoft is the current copyright holder of Ivy, I thought it might be required. Probably a good idea; the point to a Corporate CLA is actually an agreement between your employer and yourself that what you do with the Foundation is with their blessing. The ICLA you signed claims you have that right already, but we all know how painful employment contracts and their covenants are :) Best to be safe for your benefit. There is a DIFFERENT form, a Software Grant, which would be needed for a wholesale import of a code base owned by another party. See http://www.apache.org/licenses/#grants (very bottom paragraph.) Bill - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PROPOSAL] Ivy
On 10/25/06, William A. Rowe, Jr. [EMAIL PROTECTED] wrote: Xavier Hanin wrote: I've just sent both an individual and a corporate CLA by fax. I was not sure the corporate CLA was necessary, but since Jayasoft is the current copyright holder of Ivy, I thought it might be required. Probably a good idea; the point to a Corporate CLA is actually an agreement between your employer and yourself that what you do with the Foundation is with their blessing. The ICLA you signed claims you have that right already, but we all know how painful employment contracts and their covenants are :) Best to be safe for your benefit. In my case this is not really an issue, since Jayasoft is my company. Anyway, now that it's done it doesn't hurt. There is a DIFFERENT form, a Software Grant, which would be needed for a wholesale import of a code base owned by another party. See http://www.apache.org/licenses/#grants (very bottom paragraph.) OK, I think that's what will be needed if Ivy is accepted in the incubator. I will wait until someone ask me to fill this form. Thanks for your help, - Xavier Bill - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [PROPOSAL] Ivy
Antoine Levy-Lambert wrote: I have sent an email to [EMAIL PROTECTED] but no one has moderated me in yet. Instant Gratification much? No one else had gotten to it, but it got done by me this AM. Please note, that is NOT the same thing as requesting to join the Incubator PMC. --- Noel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: RE: [PROPOSAL] Ivy
Hello, Thanks very much Noel for moderating me in. Regards, Antoine Original-Nachricht Datum: Wed, 25 Oct 2006 11:29:44 -0400 Von: Noel J. Bergman [EMAIL PROTECTED] An: general@incubator.apache.org Betreff: RE: [PROPOSAL] Ivy Antoine Levy-Lambert wrote: I have sent an email to [EMAIL PROTECTED] but no one has moderated me in yet. Instant Gratification much? No one else had gotten to it, but it got done by me this AM. Please note, that is NOT the same thing as requesting to join the Incubator PMC. Understood. Actually, I do not need to become a member of the incubator PMC either, but I would very much like to have the svn and UNIX karma to edit and publish elements of the web site of ivy. --- Noel Regards, Antoine - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: RE: [PROPOSAL] Ivy
On 10/25/06, Antoine Levy-Lambert [EMAIL PROTECTED] wrote: Understood. Actually, I do not need to become a member of the incubator PMC either, but I would very much like to have the svn and UNIX karma to edit and publish elements of the web site of ivy. Ok, slow down a bit. I'm all for enthusiasm, but this stuff does take a little time. First we vote on accepting the project. Once that happens the initial committers send in their CLAs. Once the CLAs are in the project's mentors request accounts on the ASF infrastructure (unix machines, svn, etc). Once root@ creates the accounts the mentors (or someone else if the mentors don't have the right access) grants you the appropriate karma to make changes to this kind of thing in svn. You're on step 1, AFAICT, and you're all set to jump to step 6. It'll happen, it just takes a little time ;-) -garrett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: RE: [PROPOSAL] Ivy
Hello Garrett, I am not an Ivy contributor, but an ASF member and an ANT PMC member who has volunteered as champion and mentor for Ivy. I do not want to start checking in code, I just would like the possibility to start creating an ivy folder on the incubator web site. Leo wrote that the fact that the Ant PMC sponsors Ivy is already enough to start incubation. If this is true, we can start taking care of these issues. We will soon stumble on people.apache.org being dead which does not help to do web site updates. Regards, Antoine Original-Nachricht Datum: Wed, 25 Oct 2006 15:21:47 -0400 Von: Garrett Rooney [EMAIL PROTECTED] An: general@incubator.apache.org Betreff: Re: RE: [PROPOSAL] Ivy On 10/25/06, Antoine Levy-Lambert [EMAIL PROTECTED] wrote: Understood. Actually, I do not need to become a member of the incubator PMC either, but I would very much like to have the svn and UNIX karma to edit and publish elements of the web site of ivy. Ok, slow down a bit. I'm all for enthusiasm, but this stuff does take a little time. First we vote on accepting the project. Once that happens the initial committers send in their CLAs. Once the CLAs are in the project's mentors request accounts on the ASF infrastructure (unix machines, svn, etc). Once root@ creates the accounts the mentors (or someone else if the mentors don't have the right access) grants you the appropriate karma to make changes to this kind of thing in svn. You're on step 1, AFAICT, and you're all set to jump to step 6. It'll happen, it just takes a little time ;-) -garrett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: RE: [PROPOSAL] Ivy
On 10/25/06, Antoine Levy-Lambert [EMAIL PROTECTED] wrote: Hello Garrett, I am not an Ivy contributor, but an ASF member and an ANT PMC member who has volunteered as champion and mentor for Ivy. I do not want to start checking in code, I just would like the possibility to start creating an ivy folder on the incubator web site. Ahh, sorry, my bad. If you're already an ASF Member you should have write access to the appropriate places in the incubator tree. The web pages are all under /incubator/public, and the members group has write access there. Leo wrote that the fact that the Ant PMC sponsors Ivy is already enough to start incubation. If this is true, we can start taking care of these issues. We will soon stumble on people.apache.org being dead which does not help to do web site updates. Yeah, not much you can do about that other than wait. It should be back up later today. -garrett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PROPOSAL] Ivy
For your information, I've created a page for the proposal on the wiki: http://wiki.apache.org/incubator/IvyProposal The proposal right now is the same as the one posted in the initial mail, with Stefan Bodewig added as Nominated Mentor. - Xavier On 10/24/06, Stefan Bodewig [EMAIL PROTECTED] wrote: On Mon, 23 Oct 2006, Xavier Hanin [EMAIL PROTECTED] wrote: === Nominated Mentors === Antoine Levy-Lambert Stephane Baillez Steve Loughran Due to the mail system outage the past weekend my email accepting a mentor role came a bit late. The final vote should include my name as well. Stefan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PROPOSAL] Ivy
Xavier Hanin wrote: After several weeks of discussion with our user community [1] and with several Apache members, I am proud to present a proposal [2] for the open source project Ivy to join the Apache Incubator. I and all the Ivy team and user community hope you will consider this proposal carefully, and accept the project to join the foundation. +1 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PROPOSAL] Ivy
+1 Antoine Xavier Hanin wrote: Hi All, After several weeks of discussion with our user community [1] and with several Apache members, I am proud to present a proposal [2] for the open source project Ivy to join the Apache Incubator. I and all the Ivy team and user community hope you will consider this proposal carefully, and accept the project to join the foundation. Best regards, - Xavier Hanin [1] http://groups.google.com/group/ivy-future [2] = Ivy Proposal = - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PROPOSAL] Ivy
Mentors, make sure to prod and poke Noel (Alternatively, buy him a soft drink) until he gets you added to the incubator PMC. As ASF members, you can already (and should) subscribe to incubator-private@ in the meantime. Hi, I have sent an email to [EMAIL PROTECTED] but no one has moderated me in yet. I would gladly poke Noel if I could. === Sponsoring Entity === The Ant PMC has voted the following resolution: The Ant PMC sponsors Ivy moving to the Apache Incubator. If the Ivy community wishes to move Ivy to become an Ant subproject after successful incubation, and if the ASF board agrees to it, Ant will welcome Ivy as a subproject after the incubation period. Note that Sponsoring Entity == Sponsor in this case. The incubator PMC doesn't vote on this proposal seperately -- the fact that the Ant PMC voted to do this is enough to start incubation, and your mentors can go and start with helping you get infrastructural resources set up. But just for fun: I suppose the Ivy committers need to send a CLA in any case ? Xavier, Maarten, maybe you should read this http://www.apache.org/dev/ and particularly this http://www.apache.org/dev/new-committers-guide.html. +1. LSD Would everyone agree with Leo that it is OK to start asking for infrastructural resources ? I suppose this means requesting setting up svn under http://svn.apache.org/repos/asf/incubator/ , and dev, user, ppmc, and commits lists ? Regards, Antoine - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PROPOSAL] Ivy
Antoine Levy-Lambert wrote: Would everyone agree with Leo that it is OK to start asking for infrastructural resources ? Nope, first off with the server disruption, there's really been only a day since the proposal was floated. 3 days is typical to let folks raise objections before concluding the vote. And secondly... I suppose this means requesting setting up svn under http://svn.apache.org/repos/asf/incubator/ , and dev, user, ppmc, and commits lists ? ... all need to be defined in http://incubator.apache.org/projects/ivy.html status page (that's what you point the folks to create the resources at, for their reference of what's to be created.) 1. propose, wait 3 days (or whatever it takes) 2. add up the votes to 3 or more ipmc +1's and announce it 3. create a status page 4. get cla's to secretary, point at status + iclas for root to make accounts, point at status for apmail request, jira request etc. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PROPOSAL] Ivy
Bonsoir Bill, in this case, can you give me commit access in svn to http://svn.apache.org/repos/asf/incubator/public/trunk so that I can start writing an Ivy site ? Regards, Antoine William A. Rowe, Jr. wrote: Antoine Levy-Lambert wrote: Would everyone agree with Leo that it is OK to start asking for infrastructural resources ? Nope, first off with the server disruption, there's really been only a day since the proposal was floated. 3 days is typical to let folks raise objections before concluding the vote. And secondly... I suppose this means requesting setting up svn under http://svn.apache.org/repos/asf/incubator/ , and dev, user, ppmc, and commits lists ? ... all need to be defined in http://incubator.apache.org/projects/ivy.html status page (that's what you point the folks to create the resources at, for their reference of what's to be created.) 1. propose, wait 3 days (or whatever it takes) 2. add up the votes to 3 or more ipmc +1's and announce it 3. create a status page 4. get cla's to secretary, point at status + iclas for root to make accounts, point at status for apmail request, jira request etc. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PROPOSAL] Ivy
Antoine Levy-Lambert wrote: Bonsoir Bill, in this case, can you give me commit access in svn to http://svn.apache.org/repos/asf/incubator/public/trunk so that I can start writing an Ivy site ? That would be Noel - but don't let it stop you... http://svn.apache.org/repos/asf/incubator/public/trunk/ the file you want is... http://svn.apache.org/repos/asf/incubator/public/trunk/site-author/projects/incubation-status-template.xml - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[PROPOSAL] Ivy
Hi All, After several weeks of discussion with our user community [1] and with several Apache members, I am proud to present a proposal [2] for the open source project Ivy to join the Apache Incubator. I and all the Ivy team and user community hope you will consider this proposal carefully, and accept the project to join the foundation. Best regards, - Xavier Hanin [1] http://groups.google.com/group/ivy-future [2] = Ivy Proposal = The following presents the proposal for creating a new Ivy project within the Apache Software Foundation. == Abstract == Ivy (http://www.jayasoft.org/ivy) is a java based tool for tracking, resolving and managing project dependencies. == Proposal == Ivy is a tool for managing (recording, tracking, resolving and reporting) project dependencies. It is characterized by the following: 1) flexibility and configurability - Ivy is essentially process agnostic and is not tied to any methodology or structure. Instead it provides the necessary flexibility and configurability to be adapted to a broad range of dependency management and build processes. 2) tight integration with Apache Ant - while available as a standalone tool, Ivy works particularly well with Apache Ant providing a number of powerful Ant tasks ranging from dependency resolution to dependency reporting and publication. == Rationale == Software development is increasingly characterized by leveraging externally provided components/capabilities and by a rapid release cycle. As a result it is not unusual for a project to depend on numerous third-party components which themselves may be dependent on a multitude of third-party of different or identical third-party components. Managing these dependencies - determining what the dependencies are, how they are used, the impact of a change, conflicts among dependencies, etc. - is extremely difficult and absolutely necessary. Ivy is one of a handful of tools addressing this need. While often compared to Maven - which has similar Ant tasks - Ivy differs from Maven in both its focus and philosophy. Ivy is solely focused on dependency management and is designed from the ground up to adapt to a wide range of requirements and scenarios. Examples include multiple aritfacts per module, plugin resolvers, configurable repository configurations and conflict managers. The maintainers of Ivy are interested in joining the Apache Software Foundation for several reasons: * Ivy has been hosted since its beginning in 2004 by a private company, which make people feel like it's a corporate product, thus slowing the contribution by the community. We strongly believe in the open source movement, and would like to make Ivy independent from Jayasoft. * We'd like to enjoy the benefits of utilizing Apache's infrastructure and legal protection. * It might open the door for cooperation with other projects, such as Ant or Maven. * We strongly believe in Apache philosophy, especially Meritocracy. == Current status == === Meritocracy === Ivy was originally created by Xavier Hanin in September 2004. Since then more than 20 users have contributed patches, and one of them has been promoted to the status of committer based on his merit through patch contribution. === Community === Ivy already has a growing user community, with more than 10,000 downloads since its 1.0 version and more than 500 users registered on the forum. === Core Developers === Ivy has only two core developers for the moment, but we hope joining the ASF will help increase this number. Xavier Hanin is the creator of the project, is an independant consultant and co founder of Jayasoft. He has an experience of 9 years in Java software development, uses open source projects intensively, and started his real participation in open source development with Ivy. Maarten Coene has joined the committer team in may 2006. He has an experience of 9 years in java development, is co-administrator of dom4j, ex-committer for scarab, has contributed patches to several open-source projects and is a user of a lot of open-source projects. === Alignment === Ivy has no mandatory dependencies except java 1.4. However, it is strongly recommended to be used with Ant. Ivy uses also other Apache projects, especially from Jakarta Commons. == Known risks == === Orphaned products === Due to its small number of committers, there is a risk of being orphaned. The main knowledge of the codebase is still mainly owned by Xavier Hanin. Even if Xavier has no plan to leave Ivy development, this is a problem we are aware of and know that need to be worked on so that the project become less dependent on an individual. === Inexperience with Open Source === While distributed under an open source license, access to Ivy was initially limited with no public access to the issue tracking system or svn repository. While things have changed since then - the svn repository is publicly accessible, a JIRA instance has been setup since june 2005, many new features
Re: [PROPOSAL] Ivy
+1 (Binding) from me. -- dims On 10/23/06, Xavier Hanin [EMAIL PROTECTED] wrote: Hi All, After several weeks of discussion with our user community [1] and with several Apache members, I am proud to present a proposal [2] for the open source project Ivy to join the Apache Incubator. I and all the Ivy team and user community hope you will consider this proposal carefully, and accept the project to join the foundation. Best regards, - Xavier Hanin [1] http://groups.google.com/group/ivy-future [2] = Ivy Proposal = The following presents the proposal for creating a new Ivy project within the Apache Software Foundation. == Abstract == Ivy (http://www.jayasoft.org/ivy) is a java based tool for tracking, resolving and managing project dependencies. == Proposal == Ivy is a tool for managing (recording, tracking, resolving and reporting) project dependencies. It is characterized by the following: 1) flexibility and configurability - Ivy is essentially process agnostic and is not tied to any methodology or structure. Instead it provides the necessary flexibility and configurability to be adapted to a broad range of dependency management and build processes. 2) tight integration with Apache Ant - while available as a standalone tool, Ivy works particularly well with Apache Ant providing a number of powerful Ant tasks ranging from dependency resolution to dependency reporting and publication. == Rationale == Software development is increasingly characterized by leveraging externally provided components/capabilities and by a rapid release cycle. As a result it is not unusual for a project to depend on numerous third-party components which themselves may be dependent on a multitude of third-party of different or identical third-party components. Managing these dependencies - determining what the dependencies are, how they are used, the impact of a change, conflicts among dependencies, etc. - is extremely difficult and absolutely necessary. Ivy is one of a handful of tools addressing this need. While often compared to Maven - which has similar Ant tasks - Ivy differs from Maven in both its focus and philosophy. Ivy is solely focused on dependency management and is designed from the ground up to adapt to a wide range of requirements and scenarios. Examples include multiple aritfacts per module, plugin resolvers, configurable repository configurations and conflict managers. The maintainers of Ivy are interested in joining the Apache Software Foundation for several reasons: * Ivy has been hosted since its beginning in 2004 by a private company, which make people feel like it's a corporate product, thus slowing the contribution by the community. We strongly believe in the open source movement, and would like to make Ivy independent from Jayasoft. * We'd like to enjoy the benefits of utilizing Apache's infrastructure and legal protection. * It might open the door for cooperation with other projects, such as Ant or Maven. * We strongly believe in Apache philosophy, especially Meritocracy. == Current status == === Meritocracy === Ivy was originally created by Xavier Hanin in September 2004. Since then more than 20 users have contributed patches, and one of them has been promoted to the status of committer based on his merit through patch contribution. === Community === Ivy already has a growing user community, with more than 10,000 downloads since its 1.0 version and more than 500 users registered on the forum. === Core Developers === Ivy has only two core developers for the moment, but we hope joining the ASF will help increase this number. Xavier Hanin is the creator of the project, is an independant consultant and co founder of Jayasoft. He has an experience of 9 years in Java software development, uses open source projects intensively, and started his real participation in open source development with Ivy. Maarten Coene has joined the committer team in may 2006. He has an experience of 9 years in java development, is co-administrator of dom4j, ex-committer for scarab, has contributed patches to several open-source projects and is a user of a lot of open-source projects. === Alignment === Ivy has no mandatory dependencies except java 1.4. However, it is strongly recommended to be used with Ant. Ivy uses also other Apache projects, especially from Jakarta Commons. == Known risks == === Orphaned products === Due to its small number of committers, there is a risk of being orphaned. The main knowledge of the codebase is still mainly owned by Xavier Hanin. Even if Xavier has no plan to leave Ivy development, this is a problem we are aware of and know that need to be worked on so that the project become less dependent on an individual. === Inexperience with Open Source === While distributed under an open source license, access to Ivy was initially limited with no public access to the issue tracking system or svn repository. While things have changed since then - the svn repository
Re: [PROPOSAL] Ivy
On Oct 23, 2006, at 8:03 PM, Xavier Hanin wrote: After several weeks of discussion with our user community [1] and with several Apache members, I am proud to present a proposal [2] for the open source project Ivy to join the Apache Incubator. Cool. Ivy is cool. Actually, it's not *that* cool, it is useful. It is so useful, I say it is cool when I give presentations these days. The proposal looks good, too. Importing jira may be a little hard IIUC, but I guess that'll get figured out. snip/ == Sponsors == === Champion === Antoine Levy-Lambert Sylvain Wallez === Nominated Mentors === Antoine Levy-Lambert Stephane Baillez Steve Loughran Mentors, make sure to prod and poke Noel (Alternatively, buy him a soft drink) until he gets you added to the incubator PMC. As ASF members, you can already (and should) subscribe to incubator-private@ in the meantime. === Sponsoring Entity === The Ant PMC has voted the following resolution: The Ant PMC sponsors Ivy moving to the Apache Incubator. If the Ivy community wishes to move Ivy to become an Ant subproject after successful incubation, and if the ASF board agrees to it, Ant will welcome Ivy as a subproject after the incubation period. Note that Sponsoring Entity == Sponsor in this case. The incubator PMC doesn't vote on this proposal seperately -- the fact that the Ant PMC voted to do this is enough to start incubation, and your mentors can go and start with helping you get infrastructural resources set up. But just for fun: +1. LSD - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PROPOSAL] Ivy
+1 (binding) On Oct 23, 2006, at 2:03 PM, Xavier Hanin wrote: Hi All, After several weeks of discussion with our user community [1] and with several Apache members, I am proud to present a proposal [2] for the open source project Ivy to join the Apache Incubator. I and all the Ivy team and user community hope you will consider this proposal carefully, and accept the project to join the foundation. Best regards, - Xavier Hanin [1] http://groups.google.com/group/ivy-future [2] = Ivy Proposal = The following presents the proposal for creating a new Ivy project within the Apache Software Foundation. == Abstract == Ivy (http://www.jayasoft.org/ivy) is a java based tool for tracking, resolving and managing project dependencies. == Proposal == Ivy is a tool for managing (recording, tracking, resolving and reporting) project dependencies. It is characterized by the following: 1) flexibility and configurability - Ivy is essentially process agnostic and is not tied to any methodology or structure. Instead it provides the necessary flexibility and configurability to be adapted to a broad range of dependency management and build processes. 2) tight integration with Apache Ant - while available as a standalone tool, Ivy works particularly well with Apache Ant providing a number of powerful Ant tasks ranging from dependency resolution to dependency reporting and publication. == Rationale == Software development is increasingly characterized by leveraging externally provided components/capabilities and by a rapid release cycle. As a result it is not unusual for a project to depend on numerous third-party components which themselves may be dependent on a multitude of third-party of different or identical third-party components. Managing these dependencies - determining what the dependencies are, how they are used, the impact of a change, conflicts among dependencies, etc. - is extremely difficult and absolutely necessary. Ivy is one of a handful of tools addressing this need. While often compared to Maven - which has similar Ant tasks - Ivy differs from Maven in both its focus and philosophy. Ivy is solely focused on dependency management and is designed from the ground up to adapt to a wide range of requirements and scenarios. Examples include multiple aritfacts per module, plugin resolvers, configurable repository configurations and conflict managers. The maintainers of Ivy are interested in joining the Apache Software Foundation for several reasons: * Ivy has been hosted since its beginning in 2004 by a private company, which make people feel like it's a corporate product, thus slowing the contribution by the community. We strongly believe in the open source movement, and would like to make Ivy independent from Jayasoft. * We'd like to enjoy the benefits of utilizing Apache's infrastructure and legal protection. * It might open the door for cooperation with other projects, such as Ant or Maven. * We strongly believe in Apache philosophy, especially Meritocracy. == Current status == === Meritocracy === Ivy was originally created by Xavier Hanin in September 2004. Since then more than 20 users have contributed patches, and one of them has been promoted to the status of committer based on his merit through patch contribution. === Community === Ivy already has a growing user community, with more than 10,000 downloads since its 1.0 version and more than 500 users registered on the forum. === Core Developers === Ivy has only two core developers for the moment, but we hope joining the ASF will help increase this number. Xavier Hanin is the creator of the project, is an independant consultant and co founder of Jayasoft. He has an experience of 9 years in Java software development, uses open source projects intensively, and started his real participation in open source development with Ivy. Maarten Coene has joined the committer team in may 2006. He has an experience of 9 years in java development, is co-administrator of dom4j, ex-committer for scarab, has contributed patches to several open- source projects and is a user of a lot of open-source projects. === Alignment === Ivy has no mandatory dependencies except java 1.4. However, it is strongly recommended to be used with Ant. Ivy uses also other Apache projects, especially from Jakarta Commons. == Known risks == === Orphaned products === Due to its small number of committers, there is a risk of being orphaned. The main knowledge of the codebase is still mainly owned by Xavier Hanin. Even if Xavier has no plan to leave Ivy development, this is a problem we are aware of and know that need to be worked on so that the project become less dependent on an individual. === Inexperience with Open Source === While distributed under an open source license, access to Ivy was initially limited with no public access to the issue tracking system or svn repository
Re: [PROPOSAL] Ivy
It seems unclear to me whether this proposal is for a TLP or sub-project of ant? I'm also not sure whether that even matters or something thats usually considered at the Incubator proposal stage? Niall On 10/23/06, Xavier Hanin [EMAIL PROTECTED] wrote: Hi All, After several weeks of discussion with our user community [1] and with several Apache members, I am proud to present a proposal [2] for the open source project Ivy to join the Apache Incubator. I and all the Ivy team and user community hope you will consider this proposal carefully, and accept the project to join the foundation. Best regards, - Xavier Hanin [1] http://groups.google.com/group/ivy-future [2] = Ivy Proposal = The following presents the proposal for creating a new Ivy project within the Apache Software Foundation. == Abstract == Ivy (http://www.jayasoft.org/ivy) is a java based tool for tracking, resolving and managing project dependencies. == Proposal == Ivy is a tool for managing (recording, tracking, resolving and reporting) project dependencies. It is characterized by the following: 1) flexibility and configurability - Ivy is essentially process agnostic and is not tied to any methodology or structure. Instead it provides the necessary flexibility and configurability to be adapted to a broad range of dependency management and build processes. 2) tight integration with Apache Ant - while available as a standalone tool, Ivy works particularly well with Apache Ant providing a number of powerful Ant tasks ranging from dependency resolution to dependency reporting and publication. == Rationale == Software development is increasingly characterized by leveraging externally provided components/capabilities and by a rapid release cycle. As a result it is not unusual for a project to depend on numerous third-party components which themselves may be dependent on a multitude of third-party of different or identical third-party components. Managing these dependencies - determining what the dependencies are, how they are used, the impact of a change, conflicts among dependencies, etc. - is extremely difficult and absolutely necessary. Ivy is one of a handful of tools addressing this need. While often compared to Maven - which has similar Ant tasks - Ivy differs from Maven in both its focus and philosophy. Ivy is solely focused on dependency management and is designed from the ground up to adapt to a wide range of requirements and scenarios. Examples include multiple aritfacts per module, plugin resolvers, configurable repository configurations and conflict managers. The maintainers of Ivy are interested in joining the Apache Software Foundation for several reasons: * Ivy has been hosted since its beginning in 2004 by a private company, which make people feel like it's a corporate product, thus slowing the contribution by the community. We strongly believe in the open source movement, and would like to make Ivy independent from Jayasoft. * We'd like to enjoy the benefits of utilizing Apache's infrastructure and legal protection. * It might open the door for cooperation with other projects, such as Ant or Maven. * We strongly believe in Apache philosophy, especially Meritocracy. == Current status == === Meritocracy === Ivy was originally created by Xavier Hanin in September 2004. Since then more than 20 users have contributed patches, and one of them has been promoted to the status of committer based on his merit through patch contribution. === Community === Ivy already has a growing user community, with more than 10,000 downloads since its 1.0 version and more than 500 users registered on the forum. === Core Developers === Ivy has only two core developers for the moment, but we hope joining the ASF will help increase this number. Xavier Hanin is the creator of the project, is an independant consultant and co founder of Jayasoft. He has an experience of 9 years in Java software development, uses open source projects intensively, and started his real participation in open source development with Ivy. Maarten Coene has joined the committer team in may 2006. He has an experience of 9 years in java development, is co-administrator of dom4j, ex-committer for scarab, has contributed patches to several open-source projects and is a user of a lot of open-source projects. === Alignment === Ivy has no mandatory dependencies except java 1.4. However, it is strongly recommended to be used with Ant. Ivy uses also other Apache projects, especially from Jakarta Commons. == Known risks == === Orphaned products === Due to its small number of committers, there is a risk of being orphaned. The main knowledge of the codebase is still mainly owned by Xavier Hanin. Even if Xavier has no plan to leave Ivy development, this is a problem we are aware of and know that need to be worked on so that the project become less dependent on an individual. === Inexperience with Open Source === While distributed under an open source
Re: [PROPOSAL] Ivy
Erik Hatcher wrote: +1 (binding) Forgive my ignorance, but what does +1 (binding) mean? -- david http://feathercast.org/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PROPOSAL] Ivy
it's a hint that the voter is a pmc member. -- dims On 10/23/06, david reid [EMAIL PROTECTED] wrote: Erik Hatcher wrote: +1 (binding) Forgive my ignorance, but what does +1 (binding) mean? -- david http://feathercast.org/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PROPOSAL] Ivy
On 10/23/06, Erik Hatcher [EMAIL PROTECTED] wrote: On Oct 23, 2006, at 6:50 PM, david reid wrote: Erik Hatcher wrote: +1 (binding) Forgive my ignorance, but what does +1 (binding) mean? see here: http://www.apache.org/foundation/voting.html Right, but this is a proposal, not a vote. There is no concept of a binding +1 on a proposal. -- Martin Cooper - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
voting was Re: [PROPOSAL] Ivy
Davanum Srinivas wrote: it's a hint that the voter is a pmc member. *sigh* Really, no, seriously, you're telling me that the PMC can't be trusted to count votes from it's members and others it feels are qualified? Wow... Seriously, pointing out such differences just splits the community. Hey, my vote counts! Yours doesn't! After seeing the people involved in the incubator at AC US, I'm pretty sure they were all past the stage of being impressed by such things. We should get over ourselves. +1 (binding) Forgive my ignorance, but what does +1 (binding) mean? -- david http://feathercast.org/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- david Have you listened to FeatherCast yet? http://feathercast.org/ Bought the t-shirt? http://www.cafepress.com/feathercast/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: voting was Re: [PROPOSAL] Ivy
A thousand apologies.My bad. Am really sorry that i voted. Am really sorry that i added a word after my vote. is this grovelling enough or should i grovel a bit more? Get a life folks! -- dims On 10/23/06, david reid [EMAIL PROTECTED] wrote: Davanum Srinivas wrote: it's a hint that the voter is a pmc member. *sigh* Really, no, seriously, you're telling me that the PMC can't be trusted to count votes from it's members and others it feels are qualified? Wow... Seriously, pointing out such differences just splits the community. Hey, my vote counts! Yours doesn't! After seeing the people involved in the incubator at AC US, I'm pretty sure they were all past the stage of being impressed by such things. We should get over ourselves. +1 (binding) Forgive my ignorance, but what does +1 (binding) mean? -- david http://feathercast.org/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- david Have you listened to FeatherCast yet? http://feathercast.org/ Bought the t-shirt? http://www.cafepress.com/feathercast/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: voting was Re: [PROPOSAL] Ivy
David I think you are wrong. Before I saw that syntax I used to assume that I couldn't vote unless my vote was binding. I've seen this model encourage non-PMC members to vote (myself included). Paul On 10/24/06, david reid [EMAIL PROTECTED] wrote: Davanum Srinivas wrote: it's a hint that the voter is a pmc member. *sigh* Really, no, seriously, you're telling me that the PMC can't be trusted to count votes from it's members and others it feels are qualified? Wow... Seriously, pointing out such differences just splits the community. Hey, my vote counts! Yours doesn't! After seeing the people involved in the incubator at AC US, I'm pretty sure they were all past the stage of being impressed by such things. We should get over ourselves. +1 (binding) Forgive my ignorance, but what does +1 (binding) mean? -- david http://feathercast.org/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- david Have you listened to FeatherCast yet? http://feathercast.org/ Bought the t-shirt? http://www.cafepress.com/feathercast/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Paul Fremantle VP/Technology, WSO2 and OASIS WS-RX TC Co-chair http://bloglines.com/blog/paulfremantle [EMAIL PROTECTED] Oxygenating the Web Service Platform, www.wso2.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: voting was Re: [PROPOSAL] Ivy
Might be nice to leave binding-ness as an accounting detail for the person running the vote, to get rid of the my vote counts, yours doesn't thing that David pointed out. After all, if you get consensus, and it's all +1s. geir Paul Fremantle wrote: David I think you are wrong. Before I saw that syntax I used to assume that I couldn't vote unless my vote was binding. I've seen this model encourage non-PMC members to vote (myself included). Paul On 10/24/06, david reid [EMAIL PROTECTED] wrote: Davanum Srinivas wrote: it's a hint that the voter is a pmc member. *sigh* Really, no, seriously, you're telling me that the PMC can't be trusted to count votes from it's members and others it feels are qualified? Wow... Seriously, pointing out such differences just splits the community. Hey, my vote counts! Yours doesn't! After seeing the people involved in the incubator at AC US, I'm pretty sure they were all past the stage of being impressed by such things. We should get over ourselves. +1 (binding) Forgive my ignorance, but what does +1 (binding) mean? -- david http://feathercast.org/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- david Have you listened to FeatherCast yet? http://feathercast.org/ Bought the t-shirt? http://www.cafepress.com/feathercast/ - 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]
Re: voting was Re: [PROPOSAL] Ivy
Geir Magnusson Jr. wrote: Might be nice to leave binding-ness as an accounting detail for the person running the vote, to get rid of the my vote counts, yours doesn't thing that David pointed out. After all, if you get consensus, and it's all +1s. Bingo. That was David's point - the chair knows if at least -3- of those +1's came from PMC. And other votes help advise us all of the entire communities' opinion. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PROPOSAL] Ivy
Hello Niall, Niall Pemberton wrote: It seems unclear to me whether this proposal is for a TLP or sub-project of ant? The Ant PMC will welcome Ivy after incubation if they want to. But Ivy can also choose to graduate as a TLP if the Ivy community prefers. All this is of course dependent upon the Incubator PMC and the ASF board. I'm also not sure whether that even matters or something thats usually considered at the Incubator proposal stage? It means strong support from Ant for Ivy. Niall === Sponsoring Entity === The Ant PMC has voted the following resolution: The Ant PMC sponsors Ivy moving to the Apache Incubator. If the Ivy community wishes to move Ivy to become an Ant subproject after successful incubation, and if the ASF board agrees to it, Ant will welcome Ivy as a subproject after the incubation period. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PROPOSAL] Ivy
On Tuesday 24 October 2006 06:41, Niall Pemberton wrote: It seems unclear to me whether this proposal is for a TLP or sub-project of ant? I'm also not sure whether that even matters or something thats usually considered at the Incubator proposal stage? It has been pointed out in past proposals that knowing the destination pre-incubation is not a pre-requisite for incubation. Hence, Ivy has noted this and shows that there are options available now, which may be changed further down the line, if they so chooses (subject to consensus from involved parties). Cheers Niclas - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: voting was Re: [PROPOSAL] Ivy
On 10/23/06, david reid [EMAIL PROTECTED] wrote: Davanum Srinivas wrote: it's a hint that the voter is a pmc member. *sigh* Really, no, seriously, you're telling me that the PMC can't be trusted to count votes from it's members and others it feels are qualified? Wow... Seriously, pointing out such differences just splits the community. Hey, my vote counts! Yours doesn't! After seeing the people involved in the incubator at AC US, I'm pretty sure they were all past the stage of being impressed by such things. We should get over ourselves. There is another viewpoint here that had better be considered, though ... we invite the community to participate in these votes, and I can guarantee you that the majority of people who are reading the vote thread have never bothered to read the rules on what votes count (indeed, they are more likely than not to be unaware there IS such a thing as binding versus non-binding votes). Are you really preferring that we HIDE the fact that their (non-PMC members) vote doesn't officially count (although it does influence consensus), and have them go away pissed off because they thought they were misled? Craig
Re: [PROPOSAL] Ivy
On Mon, 23 Oct 2006, Xavier Hanin [EMAIL PROTECTED] wrote: === Nominated Mentors === Antoine Levy-Lambert Stephane Baillez Steve Loughran Due to the mail system outage the past weekend my email accepting a mentor role came a bit late. The final vote should include my name as well. Stefan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PROPOSAL] Ivy
+1 On 23 Oct 06, at 2:03 PM 23 Oct 06, Xavier Hanin wrote: Hi All, After several weeks of discussion with our user community [1] and with several Apache members, I am proud to present a proposal [2] for the open source project Ivy to join the Apache Incubator. I and all the Ivy team and user community hope you will consider this proposal carefully, and accept the project to join the foundation. Best regards, - Xavier Hanin [1] http://groups.google.com/group/ivy-future [2] = Ivy Proposal = The following presents the proposal for creating a new Ivy project within the Apache Software Foundation. == Abstract == Ivy (http://www.jayasoft.org/ivy) is a java based tool for tracking, resolving and managing project dependencies. == Proposal == Ivy is a tool for managing (recording, tracking, resolving and reporting) project dependencies. It is characterized by the following: 1) flexibility and configurability - Ivy is essentially process agnostic and is not tied to any methodology or structure. Instead it provides the necessary flexibility and configurability to be adapted to a broad range of dependency management and build processes. 2) tight integration with Apache Ant - while available as a standalone tool, Ivy works particularly well with Apache Ant providing a number of powerful Ant tasks ranging from dependency resolution to dependency reporting and publication. == Rationale == Software development is increasingly characterized by leveraging externally provided components/capabilities and by a rapid release cycle. As a result it is not unusual for a project to depend on numerous third-party components which themselves may be dependent on a multitude of third-party of different or identical third-party components. Managing these dependencies - determining what the dependencies are, how they are used, the impact of a change, conflicts among dependencies, etc. - is extremely difficult and absolutely necessary. Ivy is one of a handful of tools addressing this need. While often compared to Maven - which has similar Ant tasks - Ivy differs from Maven in both its focus and philosophy. Ivy is solely focused on dependency management and is designed from the ground up to adapt to a wide range of requirements and scenarios. Examples include multiple aritfacts per module, plugin resolvers, configurable repository configurations and conflict managers. The maintainers of Ivy are interested in joining the Apache Software Foundation for several reasons: * Ivy has been hosted since its beginning in 2004 by a private company, which make people feel like it's a corporate product, thus slowing the contribution by the community. We strongly believe in the open source movement, and would like to make Ivy independent from Jayasoft. * We'd like to enjoy the benefits of utilizing Apache's infrastructure and legal protection. * It might open the door for cooperation with other projects, such as Ant or Maven. * We strongly believe in Apache philosophy, especially Meritocracy. == Current status == === Meritocracy === Ivy was originally created by Xavier Hanin in September 2004. Since then more than 20 users have contributed patches, and one of them has been promoted to the status of committer based on his merit through patch contribution. === Community === Ivy already has a growing user community, with more than 10,000 downloads since its 1.0 version and more than 500 users registered on the forum. === Core Developers === Ivy has only two core developers for the moment, but we hope joining the ASF will help increase this number. Xavier Hanin is the creator of the project, is an independant consultant and co founder of Jayasoft. He has an experience of 9 years in Java software development, uses open source projects intensively, and started his real participation in open source development with Ivy. Maarten Coene has joined the committer team in may 2006. He has an experience of 9 years in java development, is co-administrator of dom4j, ex-committer for scarab, has contributed patches to several open- source projects and is a user of a lot of open-source projects. === Alignment === Ivy has no mandatory dependencies except java 1.4. However, it is strongly recommended to be used with Ant. Ivy uses also other Apache projects, especially from Jakarta Commons. == Known risks == === Orphaned products === Due to its small number of committers, there is a risk of being orphaned. The main knowledge of the codebase is still mainly owned by Xavier Hanin. Even if Xavier has no plan to leave Ivy development, this is a problem we are aware of and know that need to be worked on so that the project become less dependent on an individual. === Inexperience with Open Source === While distributed under an open source license, access to Ivy was initially limited with no public access to the issue tracking system or svn repository. While
