Re: [VOTE] Release of EasyAnt 0.9-incubating
+1 Antoine On Feb 19, 2013, at 2:23 AM, ant elder wrote: I've already voted +1 for this on the easyant list but +1 again to bring the vote up again. Still need one more vote please anyone... ...ant On Thu, Feb 14, 2013 at 9:14 PM, Nicolas Lalevée nicolas.lale...@hibnet.org wrote: This is a call for a vote of the release of EasyAnt 0.9-incubating. We are releasing the plugins, the buildtypes, the skeletons and the core (the main distribution). The first vote happened on the dev mailing list there: http://mail-archives.apache.org/mod_mbox/incubator-easyant-dev/201302.mbox/%3C21AB5F29-A4AF-4886-B640-DC0E32D294A0%40hibnet.org%3E We've got 4 +1 from the PPMC, 2 +1 from the mentors. The svn tags are there: http://svn.apache.org/repos/asf/incubator/easyant/plugins/tags/0.9-incubating/ http://svn.apache.org/repos/asf/incubator/easyant/buildtypes/tags/0.9-incubating/ http://svn.apache.org/repos/asf/incubator/easyant/skeletons/tags/0.9-incubating/ http://svn.apache.org/repos/asf/incubator/easyant/core/tags/0.9-incubating/ The released artifacts are there: http://people.apache.org/~hibou/easyant-0.9-incubating/ The KEYS file is there: http://svn.apache.org/repos/asf/incubator/easyant/KEYS Please, cast your votes: [ ] +1, I accept the release [ ] +0, OK, but…. [ ] -1, I disapprove, because…. Nicolas - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Please add me to the ContributorsGroup on wiki.apache.org/incubator
Hi, please add me to the ContributorsGroup on wiki.apache.org/incubator. I need to sign off a report for EasyAnt. Regards, Antoine - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] MRUnit entry into the incubator
On 3/1/11 8:16 PM, Eric Sammer wrote: All: Discussions from the [PROPOSAL] thread seem to have tapered off so I'd like to call a vote on accepting MRUnit into the incubator. I'm re-pasting the proposal for simplicity. We'll leave the vote open for 72 hours. Thanks! +1 Antoine - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept Rave into the Incubator
[ ] +1 Accept Rave into the incubator - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Propose Howl as an Apache Incubator project
+1 Antoine On 2/10/11 3:37 PM, Alan Gates wrote: I would like to propose Howl as an Apache Incubator project. Howl is a table and storage management service for data created using Apache Hadoop. The proposal is on the Incubator wiki at http://wiki.apache.org/incubator/HowlProposal and is pasted below. Thanks. Alan. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[VOTE][RESULTS] [PROPOSAL] EasyAnt incubator
Hi, The proposal to have EasyAnt join the ASF Incubator has been adopted with 11 binding +1s Regards, Antoine On 1/24/2011 12:14 PM, Antoine Levy-Lambert wrote: I would like to present for a vote the following proposal to be sponsored by the Ant PMC for a new EasyAnt podling. The proposal is available on the wiki at and included below: http://wiki.apache.org/incubator/EasyAntProposal - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE][PROPOSAL] EasyAnt incubator
Hello Ant, On 1/26/2011 7:25 AM, ant elder wrote: +1 You only have two mentors, if you need a third i would help out. Welcome. Please feel free to add your name on the proposal on the wiki under http://wiki.apache.org/incubator/EasyAntProposal ...ant Regards, Antoine - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[VOTE][PROPOSAL] EasyAnt incubator
I would like to present for a vote the following proposal to be sponsored by the Ant PMC for a new EasyAnt podling. The proposal is available on the wiki at and included below: http://wiki.apache.org/incubator/EasyAntProposal [] +1 to accept EasyAnt into the Incubator [] 0 don't care [] -1 object and reason why. Thanks, Antoine Levy-Lambert --- Proposal text from the wiki --- EasyAnt Proposal The following presents the proposal for creating a new EasyAnt project within the Apache Software Foundation. = Abstract = Easyant is a build system based on Apache Ant and Apache Ivy. = Proposal = EasyAnt goals are : * to leverage popularity and flexibility of Ant. * to integrate Apache Ivy, such that the build system combines a ready-to-use dependency manager. * to simplify standard build types, such as building web applications, JARs etc, by providing ready to use builds. * to provide conventions and guidelines. * to make plugging-in of fresh functionalities easy as writing simple Ant scripts as Easyant plugins. To still remain adaptable, * Though Easyant comes with a lot of conventions, we never lock you in. * Easyant allows you to easily extend existing modules or create and use your own modules. * Easyant makes migration from Ant very simple. Your legacy Ant scripts could still be leveraged with Easyant. = Rationale = On the Ivy and Ant mailing list, an often asked question is Why Ivy is not shipped with Ant ?. Ant users (and some opponents) complains also about the bootstrapping of an Ant based build system: it is mainly about copying an existing one. EasyAnt is intended to response to both of these requirements: a prepackaged Ant + Ivy solution with standard build script ready to be used. Also taking inspiration from the success of Apache Maven, EasyAnt is adopting the convention over configuration principle. Then it could be easy to build standard project at least for all commons steps (no more need to reinvent the wheel between each projects). The common part should be easy enough to tune parameters without having deep ant knowledge (example changing the default directory of sources, force compilation to be java 1.4 compatible, etc...). Last but not least, EasyAnt is intended to provide a plugin based architecture to make it easy to contribute on a specific step of the build. Build plugins are pieces of functionality that can be plugged into or removed from a project. Plugins could actually perform a piece of your regular build, e.g. compile java classes during build of a complete war. Or, do a utility action, e.g. deploy your built web application onto a packaged Jetty server! = Current Status = == Meritocracy == Some of the core developers are already committers and members of the Apache Ant PMC, so they understand what it means to have a process based on meritocracy. == Community == EasyAnt have a really small community (around 100 downloads per release). It is not a problem as the team is currently making restructuring changes. The team plans to make more promotion after those changes and strongly believe that community is the priority as the tool is designed to be easy to use. == Core Developers == Xavier Hanin and Nicolas Lalev�¡�ée are members of the PMC of Apache Ant. Jerome Benois is an Acceleo committer, he was a committer in Eclipse MDT Papyrus for two years and he's an active contributor in Eclipse Modeling and Model Driven community. He's a committer on Bushel project now contribute to the Ivy code base. He leads the EasyAnt for Eclipse plugin development. Jason Trump is leading Beet project on sourceforge (http://beet.sourceforge.net/). Jean-Louis Boudart is Hudson committer. == Alignment == EasyAnt is based on Apache Ant and Ivy. Being part of Apache could help for a closer collaboration between projects. The team plans to reinject as much as possible stuff into Ant or Ivy like they've done in the past on : * extensionPoint : kind of IoC for targets (Ant) * import/include mechanism (Ant) * module inheritance (Ivy) = Known risks = == Orphaned products == Jean-Louis Boudart is the main developer of EasyAnt. Other developers got interested in this project and are now touching to every aspect of EasyAnt. Thus the risk of being orphaned is quite limited. == Inexperience with Open Source == Many of the committers have experience working on open source projects. Two of them have experience as committers on other Apache projects. == Homogenous Developers == The existing committers are spread over a number of countries and employers. == Reliance on Salaried Developers == None of the developers rely on EasyAnt for consulting work. == Relationships with Other Apache Products == As already stated above, EasyAnt is intended to have a quite good integration with both Apache Ant and Apache Ivy. == A Excessive Fascination with the Apache Brand == As we're already based on many Apache project (Ant + Ivy
Re: [PROPOSAL] accept Easyant for incubation
On 1/20/2011 5:58 AM, Stefan Bodewig wrote: Count me in. I've added my name to the proposal page on the Wiki as well. Thanks, this is great news. Regards, Antoine Stefan - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] accept Easyant for incubation
On 1/17/2011 5:21 PM, Bertrand Delacretaz wrote: Hi Antoine, You'll need more than one mentor for that, and please move the proposal to http://wiki.apache.org/incubator as well. Proposal in the incubator wiki now. It is here now http://wiki.apache.org/incubator/EasyAntProposal Working with Nicolas on the mentors issue. -Bertrand Antoine - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] accept Easyant for incubation
Hi, I am going to be a mentor of EasyAnt. I am looking for other people willing to volunteer for that too. I am sure it is going to be interesting. Regards, Antoine On 1/17/2011 5:21 PM, Bertrand Delacretaz wrote: Hi Antoine, On Mon, Jan 17, 2011 at 10:25 PM, Antoine Levy-Lambertanto...@gmx.de wrote: We got no answer concerning Easyant. Does this mean that the proposal is non-controversial and that we should move on to a vote ? You'll need more than one mentor for that, and please move the proposal to http://wiki.apache.org/incubator as well. I cannot help with mentoring ATM unfortunately. -Bertrand - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] accept Easyant for incubation
Hi, We got no answer concerning Easyant. Does this mean that the proposal is non-controversial and that we should move on to a vote ? Regards, Antoine On 1/11/2011 12:28 PM, Antoine Levy-Lambert wrote: Hello all, We'd like to propose Easyant for entry into the ASF incubator. Easyant is providing a solution for projects who want to use Ant and Ivy with a lot of ready-made templates, with the option to customize. The draft proposal is available at : http://easyant.org/projects/easyant/wiki/ApacheProposal The Ant project has voted to sponsor the entry of Easyant at the Incubator [1]. For your convenience I have pasted this proposal below the email. Regards, Antoine [1] http://mail-archives.apache.org/mod_mbox/ant-dev/201101.mbox/%3c3a73c5da-e4a2-4cb6-8423-0a985246f...@hibnet.org%3E h1. EasyAnt Proposal The following presents the proposal for creating a new EasyAnt project within the Apache Software Foundation. h2. Abstract Easyant is a build system based on Apache Ant and Apache Ivy. h2. Proposal EasyAnt goals are : * to leverage popularity and flexibility of Ant. * to integrate Apache Ivy, such that the build system combines a ready-to-use dependency manager. * to simplify standard build types, such as building web applications, JARs etc, by providing ready to use builds. * to provide conventions and guidelines. * to make plugging-in of fresh functionalities easy as writing simple Ant scripts as Easyant plugins. To still remain adaptable, * Though Easyant comes with a lot of conventions, we never lock you in. * Easyant allows you to easily extend existing modules or create and use your own modules. * Easyant makes migration from Ant very simple. Your legacy Ant scripts could still be leveraged with Easyant. h2. Rationale On the Ivy and Ant mailing list, an often asked question is Why Ivy is not shipped with Ant ?. Ant users (and some opponents) complains also about the bootstrapping of an Ant based build system: it is mainly about copying an existing one. EasyAnt is intended to response to both of these requirements: a prepackaged Ant + Ivy solution with standard build script ready to be used. Also taking inspiration from the success of Apache Maven, EasyAnt is adopting the convention over configuration principle. Then it could be easy to build standard project at least for all commons steps (no more need to reinvent the wheel between each projects). The common part should be easy enough to tune parameters without having deep ant knowledge (example changing the default directory of sources, force compilation to be java 1.4 compatible, etc...). Last but not least, EasyAnt is intended to provide a plugin based architecture to make it easy to contribute on a specific step of the build. Build plugins are pieces of functionality that can be plugged into or removed from a project. Plugins could actually perform a piece of your regular build, e.g. compile java classes during build of a complete war. Or, do a utility action, e.g. deploy your built web application onto a packaged Jetty server! h2. Current Status h3. Meritocracy Some of the core developers are already committers and members of the Apache Ant PMC, so they understand what it means to have a process based on meritocracy. h3. Community EasyAnt have a really small community (around 100 downloads per release). It is not a problem as the team is currently making restructuring changes. The team plans to make more promotion after those changes and strongly believe that community is the priority as the tool is designed to be easy to use. h3. Core Developers Xavier Hanin and Nicolas Lalev�ée are members of the PMC of Apache Ant. Jerome Benois is an Acceleo committer, he was a committer in Eclipse MDT Papyrus for two years and he's an active contributor in Eclipse Modeling and Model Driven community. He's a committer on Bushel project now contribute to the Ivy code base. He leads the EasyAnt for Eclipse plugin development. Jason Trump is leading Beet project on sourceforge (http://beet.sourceforge.net/). Jean-Louis Boudart is Hudson committer. h3. Alignment EasyAnt is based on Apache Ant and Ivy. Being part of Apache could help for a closer collaboration between projects. The team plans to reinject as much as possible stuff into Ant or Ivy like they've done in the past on : * extensionPoint : kind of IoC for targets (Ant) * import/include mechanism (Ant) * module inheritance (Ivy) h2. Known risks h3. Orphaned products Jean-Louis Boudart is the main developer of EasyAnt. Other developers got interested in this project and are now touching to every aspect of EasyAnt. Thus the risk of being orphaned is quite limited. h3. Inexperience with Open Source Many of the committers have experience working on open source projects. Two of them have experience as committers on other Apache projects. h3. Homogenous Developers The existing
Re: [PROPOSAL] accept Easyant for incubation
On 1/17/2011 5:21 PM, Bertrand Delacretaz wrote: Hi Antoine, You'll need more than one mentor for that, and please move the proposal to http://wiki.apache.org/incubator as well. Thanks Bertrand. There will be two mentors, myself and Nicolas Lalevée. Nicolas is a member of the Ant PMC , and a committer of ivy and committer and release manager of IvyDE. I cannot help with mentoring ATM unfortunately. -Bertrand Regards, Antoine - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[PROPOSAL] accept Easyant for incubation
Hello all, We'd like to propose Easyant for entry into the ASF incubator. Easyant is providing a solution for projects who want to use Ant and Ivy with a lot of ready-made templates, with the option to customize. The draft proposal is available at : http://easyant.org/projects/easyant/wiki/ApacheProposal The Ant project has voted to sponsor the entry of Easyant at the Incubator [1]. For your convenience I have pasted this proposal below the email. Regards, Antoine [1] http://mail-archives.apache.org/mod_mbox/ant-dev/201101.mbox/%3c3a73c5da-e4a2-4cb6-8423-0a985246f...@hibnet.org%3e h1. EasyAnt Proposal The following presents the proposal for creating a new EasyAnt project within the Apache Software Foundation. h2. Abstract Easyant is a build system based on Apache Ant and Apache Ivy. h2. Proposal EasyAnt goals are : * to leverage popularity and flexibility of Ant. * to integrate Apache Ivy, such that the build system combines a ready-to-use dependency manager. * to simplify standard build types, such as building web applications, JARs etc, by providing ready to use builds. * to provide conventions and guidelines. * to make plugging-in of fresh functionalities easy as writing simple Ant scripts as Easyant plugins. To still remain adaptable, * Though Easyant comes with a lot of conventions, we never lock you in. * Easyant allows you to easily extend existing modules or create and use your own modules. * Easyant makes migration from Ant very simple. Your legacy Ant scripts could still be leveraged with Easyant. h2. Rationale On the Ivy and Ant mailing list, an often asked question is Why Ivy is not shipped with Ant ?. Ant users (and some opponents) complains also about the bootstrapping of an Ant based build system: it is mainly about copying an existing one. EasyAnt is intended to response to both of these requirements: a prepackaged Ant + Ivy solution with standard build script ready to be used. Also taking inspiration from the success of Apache Maven, EasyAnt is adopting the convention over configuration principle. Then it could be easy to build standard project at least for all commons steps (no more need to reinvent the wheel between each projects). The common part should be easy enough to tune parameters without having deep ant knowledge (example changing the default directory of sources, force compilation to be java 1.4 compatible, etc...). Last but not least, EasyAnt is intended to provide a plugin based architecture to make it easy to contribute on a specific step of the build. Build plugins are pieces of functionality that can be plugged into or removed from a project. Plugins could actually perform a piece of your regular build, e.g. compile java classes during build of a complete war. Or, do a utility action, e.g. deploy your built web application onto a packaged Jetty server! h2. Current Status h3. Meritocracy Some of the core developers are already committers and members of the Apache Ant PMC, so they understand what it means to have a process based on meritocracy. h3. Community EasyAnt have a really small community (around 100 downloads per release). It is not a problem as the team is currently making restructuring changes. The team plans to make more promotion after those changes and strongly believe that community is the priority as the tool is designed to be easy to use. h3. Core Developers Xavier Hanin and Nicolas Lalev�ée are members of the PMC of Apache Ant. Jerome Benois is an Acceleo committer, he was a committer in Eclipse MDT Papyrus for two years and he's an active contributor in Eclipse Modeling and Model Driven community. He's a committer on Bushel project now contribute to the Ivy code base. He leads the EasyAnt for Eclipse plugin development. Jason Trump is leading Beet project on sourceforge (http://beet.sourceforge.net/). Jean-Louis Boudart is Hudson committer. h3. Alignment EasyAnt is based on Apache Ant and Ivy. Being part of Apache could help for a closer collaboration between projects. The team plans to reinject as much as possible stuff into Ant or Ivy like they've done in the past on : * extensionPoint : kind of IoC for targets (Ant) * import/include mechanism (Ant) * module inheritance (Ivy) h2. Known risks h3. Orphaned products Jean-Louis Boudart is the main developer of EasyAnt. Other developers got interested in this project and are now touching to every aspect of EasyAnt. Thus the risk of being orphaned is quite limited. h3. Inexperience with Open Source Many of the committers have experience working on open source projects. Two of them have experience as committers on other Apache projects. h3. Homogenous Developers The existing committers are spread over a number of countries and employers. h3. Reliance on Salaried Developers None of the developers rely on EasyAnt for consulting work. h3. Relationships with Other Apache Products As already stated above,
Re: [VOTE] Let Ivy Graduate as an Ant Subproject
yes, +1 and congratulations too. Regards, Antoine Original-Nachricht Datum: Mon, 08 Oct 2007 09:05:08 -0700 Von: Jean T. Anderson [EMAIL PROTECTED] An: general@incubator.apache.org Betreff: Re: [VOTE] Let Ivy Graduate as an Ant Subproject Stefan Bodewig wrote: Should Ivy be allowed to graduate as an Ant Subproject? [x] Yes [ ] No yes, +1, and congratulations! -jean - 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: REMINDER: BOARD REPORTS
Hi, Thanks Xavier for the report. Regards, Antoine Original-Nachricht Datum: Thu, 15 Feb 2007 19:19:43 +0100 Von: Xavier Hanin [EMAIL PROTECTED] An: general@incubator.apache.org CC: Betreff: Re: REMINDER: BOARD REPORTS On 2/14/07, Yoav Shapira [EMAIL PROTECTED] wrote: Hi, OK, we're almost there ;) Lokahi, stdcxx, TSIK, WSRP4J, y'all still have a few hours. I was also hoping to see the Ivy report (originally expected last month) on http://wiki.apache.org/incubator/February2007 by now... Hi, I'm still not used to the reporting process, so I think I've updated Ivy's report on the wiki page a bit late... that is, only a few hours ago, but I think it was still the 14th somewhere in the world :-) Sorry for the delay, next time we'll be on time! Xavier Yoav - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
board report format
Hi, what is the board report format. Justin left a remark that we did not follow the template for Ivy. Regards, Antoine - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
import of ivy's code in SVN
Hello, Xavier Hanin has created this issue on 23/Nov/06 12:15 AM. https://issues.apache.org/jira/browse/INFRA-1047 This is currently the limiting factor to start working on ivy here at the incubator. Can someone of infrastructure take care of it ? Regards, Antoine - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [IVY] setup of infrastructure
Hello Stefan, will you also contact infrastructure concerning mailing lists and JIRA on behalf of Ivy ? Regards, Antoine Stefan Bodewig wrote: On Mon, 30 Oct 2006, Antoine Levy-Lambert [EMAIL PROTECTED] wrote: Also, can I request the creation of the svn directory for ivy before the grant is received, or shall I wait for this one ? No, we just must not import any code before the grant is recorded. You don't need to bother infrastructure with svn issues, BTW, I should be able to handle that. Stefan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [IVY] setup of infrastructure
Hi Xavier, I have added this commits list to the page about ivy. http://incubator.apache.org/projects/ivy.html The update should be visible on the web in one hour. I have seen that Stefan also did an update to this page, removing a date which was filled by mistake. :-) Also he has added ivy to http://incubator.apache.org/projects/index.html (will also be visible soon) Regards, Antoine Xavier Hanin wrote: On 10/30/06, Brett Porter [EMAIL PROTECTED] wrote: On 31/10/06, Xavier Hanin [EMAIL PROTECTED] wrote: Personnally I don't mind, What I like with only one list is that you can easily reply to a commit and discuss it if required. Having two separate lists is more scalable. If any other one has a preference, it's ok for me. We set the reply-to so that discussions on commits should come back to the dev@ list, so you get the advantage of uncluttering the archives and the list being less intimidating to new developers, while avoiding fracturing the discussion. This seems to be a good solution. I would go with it if others are ok. Xavier - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [IVY] setup of infrastructure
Hi, I have contacted infrastructure for the mailing lists and for JIRA. Regards, Antoine Original-Nachricht Datum: Tue, 31 Oct 2006 20:06:02 +0100 Von: Stefan Bodewig [EMAIL PROTECTED] An: general@incubator.apache.org Betreff: Re: [IVY] setup of infrastructure On Tue, 31 Oct 2006, Antoine Levy-Lambert [EMAIL PROTECTED] wrote: will you also contact infrastructure concerning mailing lists and JIRA on behalf of Ivy ? Please go ahead yourself, you can volunteer me as moderator for all lists but another moderator - preferably in a different time zone than Central Europe - would be good. Stefan - 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]
[IVY] maillists moderator needed
Hi, infrastructure actually needs 3 moderators for the emails. Stefan Bodewig and myself are volunteers. We need a third. Regards, Antoine Original-Nachricht Datum: Tue, 31 Oct 2006 20:06:02 +0100 Von: Stefan Bodewig [EMAIL PROTECTED] An: general@incubator.apache.org Betreff: Re: [IVY] setup of infrastructure Please go ahead yourself, you can volunteer me as moderator for all lists but another moderator - preferably in a different time zone than Central Europe - would be good. Stefan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [IVY] maillists moderator needed
Hello Xavier, this is certainly something that you are allowed to do. So I will let infrastructure know that we have the 3 people needed. Will you do this with your gmail mail address ? Regards, Antoine Xavier Hanin wrote: On 11/1/06, Antoine Levy-Lambert [EMAIL PROTECTED] wrote: Hi, infrastructure actually needs 3 moderators for the emails. Stefan Bodewig and myself are volunteers. We need a third. I don't know if this is something I'm allowed to do, but if I can I volunteer. Xavier Regards, Antoine Original-Nachricht Datum: Tue, 31 Oct 2006 20:06:02 +0100 Von: Stefan Bodewig [EMAIL PROTECTED] An: general@incubator.apache.org Betreff: Re: [IVY] setup of infrastructure Please go ahead yourself, you can volunteer me as moderator for all lists but another moderator - preferably in a different time zone than Central Europe - would be good. Stefan - 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
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]
[IVY] setup of infrastructure
Hello Upayavira, thanks a lot for your email. The status page exists at this location : http://incubator.apache.org/projects/ivy.html Xavier already answered that he is working on the software grant. Can all the interested parties (champions, mentors, and of course Xavier and Maarten) check that the data on the status page reflects what we want to have for ivy. One detail, which I copied from the Wiki page : no separate distribution list for the commit messages. This will mean that the commit messages when changes are done in svn will go to the ivy-dev list (like ant-dev). Xavier, Maarten, do you want to have it that way ? Some projects have a [project name]-commits separate list. Also, can I request the creation of the svn directory for ivy before the grant is received, or shall I wait for this one ? If involved parties are OK with the name of the mailing lists (ivy-ppmc, ivy-dev, ivy-user), can I go ahead to ask the mailing lists to be setup ? Some projects call their ppmc list private (for instance would be ivy-private). Do we have to obey to this convention ? Regards, Antoine Original-Nachricht Datum: Mon, 30 Oct 2006 14:37:47 + Von: Upayavira [EMAIL PROTECTED] An: general@incubator.apache.org Betreff: 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]
Re: [IVY] setup of infrastructure
Thanks Garrett, this is fixed in Subversion, and the change will be soon visible on the web. Regards, Antoine Original-Nachricht Datum: Mon, 30 Oct 2006 11:50:42 -0500 Von: Garrett Rooney [EMAIL PROTECTED] An: general@incubator.apache.org Betreff: Re: [IVY] setup of infrastructure On 10/30/06, Antoine Levy-Lambert [EMAIL PROTECTED] wrote: Some projects call their ppmc list private (for instance would be ivy-private). Do we have to obey to this convention ? All the PMC and PPMC mailing lists are now known as -private, to stress the fact that they're supposed to be used just for conversations that can't be held in public. It was a global ASF wide change, for older lists there are aliases in place so the old -pmc version works, but the cannonical list name is now -private. -garrett - 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: [IVY] setup of infrastructure
Hello Xavier, we need to check with infrastructure whether they accept new products in JIRA at this time. I understood that infrastructure has more trouble supporting JIRA than Bugzilla. I will ask infrastructure in a separate email. Regards, Antoine Original-Nachricht Datum: Mon, 30 Oct 2006 18:24:20 +0100 Von: Xavier Hanin [EMAIL PROTECTED] An: general@incubator.apache.org Betreff: Re: [IVY] setup of infrastructure For bugtracking I would prefer jira than bugzilla. The rest seems ok for me. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Fwd: Re: Fwd: Re: [IVY] setup of infrastructure]
FYI Original Message Subject:Re: Fwd: Re: [IVY] setup of infrastructure Date: Tue, 31 Oct 2006 13:35:58 +1100 From: Jeff Turner [EMAIL PROTECTED] To: Antoine Levy-Lambert [EMAIL PROTECTED] CC: [EMAIL PROTECTED], [EMAIL PROTECTED] References: [EMAIL PROTECTED] On Mon, Oct 30, 2006 at 07:48:46PM +0100, Antoine Levy-Lambert wrote: Hi, I am champion and mentor of Ivy, a new project which is entering the incubator. Is it possible to create new products in JIRA ? Or do you prefer newcomers to use bugzilla ? Whichever you prefer. Ivy is using already jira. http://jira.jayasoft.org/secure/Dashboard.jspa is their URL. If we choose JIRA for Ivy, can we import the existing bug reports into the new database ? With a bit of effort, and not-100% fidelity, yes. Jason Dillon wrote a tool to generate a script recreating JIRA data: http://swizzle.codehaus.org/Jira+Migration --Jeff - 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: 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
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: [VOTE] REVISED Policy on Initial Committer and PPMC members
Hello Noel, sorry to ask a basic question. What does PPMC mean ? Is it the sub PMC of a particular incubator project ? Regards, Antoine Original-Nachricht Datum: Wed, 25 Oct 2006 16:12:19 -0400 Von: Noel J. Bergman [EMAIL PROTECTED] An: general@incubator.apache.org Betreff: [VOTE] REVISED Policy on Initial Committer and PPMC members The Champion shall work with the incoming community identify the initial PPMC members*. The Champion shall review each with the incoming community - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] REVISED Policy on Initial Committer and PPMC members
Thanks Martijn. Regards, Antoine Martijn Dashorst wrote: PPMC = Podling project management committee IPMC = Incubator project management committee if I'm not mistaken. Martijn - 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
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
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]
