Mailing-List: contact dev-help@ant.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Ant Developers List" <dev@ant.apache.org>
Received-SPF: pass (nike.apache.org: domain of jeanlouis.boudart@gmail.com
 designates 209.85.217.173 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <2BDB7542-C5D7-40DC-B91C-9B030D330257@hibnet.org>
References: <2BDB7542-C5D7-40DC-B91C-9B030D330257@hibnet.org>
Date: Sat, 14 Jul 2012 01:27:11 +0200
Message-ID: 
 <CA+e2WO4Vk_gFJjU=8mgS1bUNnp1Wyw0JN8_SFSaxxAgmByd2mw@mail.gmail.com>
Subject: Re: [VOTE] Accept EasyAnt as a subproject
From: Jean-Louis Boudart <jeanlouis.boudart@gmail.com>
To: Ant Developers List <dev@ant.apache.org>
Content-Type: multipart/alternative; boundary=bcaec552398065d1bb04c4be6b2c

--bcaec552398065d1bb04c4be6b2c
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

I was watching the original discussion on incubator mailing list few days
ago, and like Nicolas i misunderstood the sponsoring of Ant project to
EasyAnt.

I don't see any advantage to build an independent PMC.

EasyAnt is build on top of ant and ivy, and it doesn't mean we just want to
use the library under the hood. EasyAnt is here also to promote those
powerful tools and bring fresh ideas, we already contributed features to
both project, and i'm pretty sure we will continue in this way. As we
depend on those project and really plan to contribute to them i would feel
more confortable if Ant PMC is aware about easyant release and vice et
versa.

EasyAnt will try to be always using upstream version of both project, and
particular needs for us could probably "stimulate" ant or ivy release
frequency.

If one day, some of us becomes part of Ant PMC,  we could also help on
releasing Ant + Ivy.

Cheers,

2012/7/11 Nicolas Lalev=E9e <nicolas.lalevee@hibnet.org>

> EasyAnt is a project based on Ant and Ivy which is in incubation under ou=
r
> "sponsoring".
>
> I kind of misunderstood the "sponsoring". I was thinking that it was
> implying that EasyAnt will become part of the Ant project. It doesn't
> bylaw. We just cleared it out with the EasyAnt community. So let's clear =
it
> out with this vote for the Ant PMC.
> I also thought that EasyAnt should have a classical incubation period,
> doing release and growing a community. But it has no sense since if EasyA=
nt
> is accepted as a subproject of Ant, the Ant PMC will be responsible for
> EasyAnt code and releases.
>
> So if we accept EasyAnt, the code will be imported, committers added. But
> releases should be voted by us. I'm the only active EasyAnt committer whi=
ch
> is also an Ant PMC member. This means that other Ant PMC member should be
> involved so that things can roll. We have been managing that with Ivy and
> IvyDE, but this is something that should have in mind while voting. Also
> note that it would somehow resolve itself it some EasyAnt developer becom=
e
> part of the Ant PMC, some of them have already wrote some nice patches on
> Ant and Ivy :)
>
> So, should we accept EasyAnt as a subproject ?
>
>
> Nicolas
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
> For additional commands, e-mail: dev-help@ant.apache.org
>
>


--=20
Jean Louis Boudart
Independent consultant
Apache EasyAnt commiter http://incubator.apache.org/easyant/

--bcaec552398065d1bb04c4be6b2c--