Mailing-List: contact dev-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Jakarta Commons Developers List" <dev@commons.apache.org>
Received-SPF: pass (athena.apache.org: domain of brett.porter@gmail.com
 designates 209.85.198.187 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=YrOuQB5P6da9ZAzLo6c8QnuCb2wAPjvCHN/uH0EoBeMa27G+ksj+Ct+Ujr0SWAr/TFbqagERdpsx2tCouq9KA2L5goybcr2yPHYUY0QcoSROCgI43R5xC1VBW1b6vRugBPDsOh2HbPGRzDVjr0gD4dWCP2MRh64lylXDl75YbTE=
Message-ID: <9e3862d80801031749q2d7ff44fh1a640cdfe8e0fb94@mail.gmail.com>
Date: Fri, 4 Jan 2008 12:49:45 +1100
From: "Brett Porter" <brett.porter@gmail.com>
To: "Jakarta Commons Developers List" <dev@commons.apache.org>
Subject: Re: [all] releasing a nearly dormant project (was Re: [exec] how to
 proceed for a nearly dormant project)
In-Reply-To: <55afdc850801031742r36aa6f08w95b1f9bc670e87bb@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <477BDEAF.5040100@it20one.at>
	 <536737FD-3D93-4FFF-A49E-9C936AB0C55F@apache.org>
	 <477CA03C.3070907@it20one.at>
	 <887457FE-C0B2-4FF5-97BD-E37A3051667C@apache.org>
	 <55afdc850801031742r36aa6f08w95b1f9bc670e87bb@mail.gmail.com>

I'm always interested, but it's always been somewhere down my list of
priorities :(

If Siegfried is able to drive it to release quality, I can likely
start using it in a number of places which will increase my
involvement.

Thanks!

Cheers,
Brett

On 04/01/2008, Niall Pemberton <niall.pemberton@gmail.com> wrote:
> On Jan 3, 2008 9:00 AM, Torsten Curdt <tcurdt@apache.org> wrote:
> > >>> Exec would need to migrate to proper first.
> > >>
> > > According to the website moving to proper requires an "active group
> > > of committers" - I hardly qualifiy for that so I'm sort of stuck
> >
> > That was my concern
> >
> > > Therefore I see two options
> > >
> > > +) one existing committer teams up with me (preferred but rather
> > > unlikely looking at the recent activity)
> > > +) I leave commons-exec at it is in the sandbox  and push out a
> > > SNAPSHOT release
> >
> > IMO a SNAPSHOT release is not really what we want. But I guess we (as
> > a community) need to discuss situations like these. The definition of
> > active committers is rather vague in this context. After all we have
> > quite some "one man shows" where other committers just help out. But
> > not releasing "exec" does not sounds like a better option either.
>
> I agree the only option is really to propose promoting exec to become
> a proper component and then release. For me the question is how likely
> is Siegfried to stick around to support it? I would hate to see it
> promoted and then it go inactive again shortly after. I know
> circumstances change and there are no binding commitments here - but
> stating an intention to stick around and look after it when proposing
> promotion would make me more likely to vote for it (plus yours and
> Luc's semi-interest helps). Looking at the commit logs, the people to
> last work on actual code were Niklas Gustavsson (July 2006), Trygve
> Laugstoul (Sept 2005) and Brett Porter (August 2005) - perhaps it
> would be also worth pinging them to see if their interest can be
> revived.
>
> Niall
>
> > Thoughts?
> >
> > cheers
> > --
> > Torsten
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>


-- 
Brett Porter
Blog: http://www.devzuz.org/blogs/bporter/

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org