Return-Path: Delivered-To: apmail-incubator-general-archive@www.apache.org Received: (qmail 56123 invoked from network); 17 Jan 2011 21:31:59 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 17 Jan 2011 21:31:59 -0000 Received: (qmail 65546 invoked by uid 500); 17 Jan 2011 21:31:59 -0000 Delivered-To: apmail-incubator-general-archive@incubator.apache.org Received: (qmail 65353 invoked by uid 500); 17 Jan 2011 21:31:58 -0000 Mailing-List: contact general-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: general@incubator.apache.org Delivered-To: mailing list general@incubator.apache.org Received: (qmail 65345 invoked by uid 99); 17 Jan 2011 21:31:58 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 17 Jan 2011 21:31:58 +0000 X-ASF-Spam-Status: No, hits=0.7 required=10.0 tests=RCVD_IN_DNSWL_NONE,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [194.109.24.26] (HELO smtp-vbr6.xs4all.nl) (194.109.24.26) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 17 Jan 2011 21:31:50 +0000 Received: from macpro.fritz.box (planetmarrs.xs4all.nl [82.95.193.148]) (authenticated bits=0) by smtp-vbr6.xs4all.nl (8.13.8/8.13.8) with ESMTP id p0HLVSbB007069 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for ; Mon, 17 Jan 2011 22:31:29 +0100 (CET) (envelope-from marcel.offermans@luminis.nl) Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Apple Message framework v1082) Subject: Re: [PROPOSAL] accept Easyant for incubation From: Marcel Offermans In-Reply-To: <4D34B3B7.9030608@gmx.de> Date: Mon, 17 Jan 2011 22:31:28 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: <30B6DCFE-05A0-46CF-923F-4C2C21EAEE34@luminis.nl> References: <4D2C9358.9010604@gmx.de> <4D34B3B7.9030608@gmx.de> To: X-Mailer: Apple Mail (2.1082) X-Virus-Scanned: by XS4ALL Virus Scanner X-Virus-Checked: Checked by ClamAV on apache.org Hello Antoine, For me it's non-controversial. I'd love to see something like this, but = I'm probably not going to be able to spend a lot of time contributing to = it. Maybe some OSGi specific parts, especially if we can somehow = integrate them with Bnd and BndTools. Greetings, Marcel On Jan 17, 2011, at 22:25 , Antoine Levy-Lambert wrote: > Hi, >=20 > We got no answer concerning Easyant. >=20 > Does this mean that the proposal is non-controversial and that we = should move on to a vote ? >=20 > Regards, >=20 > Antoine >=20 >=20 > On 1/11/2011 12:28 PM, Antoine Levy-Lambert wrote: >> Hello all, >>=20 >> We'd like to propose Easyant for entry into the ASF incubator. >>=20 >> 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. >>=20 >> The draft proposal is available at : >> http://easyant.org/projects/easyant/wiki/ApacheProposal >>=20 >> The Ant project has voted to sponsor the entry of Easyant at the = Incubator [1]. >>=20 >> For your convenience I have pasted this proposal below the email. >>=20 >> Regards, >>=20 >> Antoine >>=20 >> [1] = http://mail-archives.apache.org/mod_mbox/ant-dev/201101.mbox/%3C3A73C5DA-E= 4A2-4CB6-8423-0A985246FA8E@hibnet.org%3E >>=20 >> h1. EasyAnt Proposal >>=20 >> The following presents the proposal for creating a new EasyAnt = project within the Apache Software Foundation. >>=20 >> h2. Abstract >>=20 >> Easyant is a build system based on Apache Ant and Apache Ivy. >>=20 >> h2. Proposal >>=20 >> EasyAnt goals are : >>=20 >> * 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. >>=20 >> To still remain adaptable, >>=20 >> * 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. >>=20 >> h2. Rationale >>=20 >> 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. >>=20 >> 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...). >>=20 >> 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! >>=20 >> h2. Current Status >>=20 >> h3. Meritocracy >>=20 >> 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. >>=20 >> h3. Community >>=20 >> 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. >>=20 >> h3. Core Developers >>=20 >> Xavier Hanin and Nicolas Lalev=99=E9e 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. >>=20 >> h3. Alignment >>=20 >> 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) >>=20 >> h2. Known risks >>=20 >> h3. Orphaned products >>=20 >> 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. >>=20 >> h3. Inexperience with Open Source >>=20 >> Many of the committers have experience working on open source = projects. Two of them have experience as committers on other Apache = projects. >>=20 >> h3. Homogenous Developers >>=20 >> The existing committers are spread over a number of countries and = employers. >>=20 >> h3. Reliance on Salaried Developers >>=20 >> None of the developers rely on EasyAnt for consulting work. >>=20 >> h3. Relationships with Other Apache Products >>=20 >> As already stated above, EasyAnt is intended to have a quite good = integration with both Apache Ant and Apache Ivy. >>=20 >> h3. A Excessive Fascination with the Apache Brand >>=20 >> As we're already based on many Apache project (Ant + Ivy), it seems = natural for us that Apache Software Foundation could be a good host for = this. >>=20 >> h2. Documentation >>=20 >> Further reading on EasyAnt can be found at: = http://www.easyant.org/doc/ >>=20 >> Mailing list is located at http://groups.google.com/group/easyant >>=20 >> h2. Initial Source >>=20 >> The initial code base can be found at: http://svn.easyant.org/ >>=20 >> h2. Source and Intellectual Property Submission Plan >>=20 >> Ever developer is willing to sign the proper papers to make EasyAnt = enter the ASF. >>=20 >> h2. External Dependencies >>=20 >> Easyant requires at compile/runtime : >>=20 >> * apache ant >> * apache ivy >> * ant contrib >>=20 >> h2. Required Resources >>=20 >> h3. Mailing lists >>=20 >> * easyant-private (with moderated subscriptions) >> * easyant-dev >>=20 >> h3. Subversion Directory >>=20 >> https://svn.apache.org/repos/asf/incubator/easyant >>=20 >> h3. Issue Tracking >>=20 >> JIRA EasyAnt (EASYANT) >>=20 >> h2. Initial Committers >>=20 >> * Xavier Hanin >> * J=99=E9r=99=F4me Benois >> * Jason Trump >> * Siddhartha Purkayastha >> * Nicolas Lalev=99=E9e >> * Jean-Louis Boudart >>=20 >> h2. Sponsors >>=20 >> h3. Champions >>=20 >> * Antoine L=99=E9vy-Lambert >>=20 >> h3. Nominated Mentors >>=20 >> * Antoine L=99=E9vy-Lambert >>=20 >> h3. Sponsoring Entity >>=20 >> * Apache Ant >>=20 >>=20 >=20 >=20 > --------------------------------------------------------------------- > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org > For additional commands, e-mail: general-help@incubator.apache.org >=20 --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org For additional commands, e-mail: general-help@incubator.apache.org