Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Jakarta Commons Developers List" <commons-dev@jakarta.apache.org>
Received-SPF: neutral (hermes.apache.org: local policy)
Subject: Re: [email] Someone on commons-email?
From: Simon Kitching <skitching@apache.org>
Reply-To: skitching@apache.org
To: Jakarta Commons Developers List <commons-dev@jakarta.apache.org>
In-Reply-To: <42AEDA70.1060006@yahoo.com.br>
References: <42AB1161.2030900@yahoo.com.br> <42ACFC75.2050709@spiegs.com>
	 <df308a980506130106452f13b7@mail.gmail.com>  <42AD87A9.30704@yahoo.com.br>
	 <1118700269.5084.14.camel@knossos.elmet>  <42AEDA70.1060006@yahoo.com.br>
Content-Type: text/plain
Date: Wed, 15 Jun 2005 16:26:34 +1200
Message-Id: <1118809594.3951.32.camel@localhost.localdomain>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit

On Tue, 2005-06-14 at 10:24 -0300, Ramiro Pereira de Magalhaes wrote:

> Well, that's quite bad... :(
> Isn't anyone with "managing powers" interested in "pushing email towards 
> a release"? I can checkout this project and start fixing anything by 
> myself as (if) needed but this way I'll be working alone and in a 
> "branch" that will probably be thrown away when the project start moving 
> again...

Unfortunately it looks like no committer here has the spare time or
interest in email to help you out. And unfortunately that includes me
too.

You are perfectly entitled to take a copy of the code and start a
project on sourceforge (or elsewhere) as long as the license is complied
with (the easiest way to do that is just continue to use the APL 2.0
license). If you do this, then I would be happy to see a note on the
email project wiki pointing to the sourceforge branch. 

If the sourceforge fork is successful (builds a community of a few
developers, has happy users) then there is every chance that the
maintainers of that project (esp. you) might be invited to become
commons committers and merge the code back in here -- if you wanted to.

Or as you say you could just maintain a private copy. That's still an
improvement over starting from nothing.

It's always a shame to see a commons project die because the original
committers went away when users actively want to become developers (not
to mention bad for jakarta's reputation). But unfortunately it also
takes some time and effort from existing commons committers to check
that potential contributors are actually people we do want to give
commit rights to and to allow to perform releases in Apache's name. And
unlike some open-source projects, there aren't any people paid to work
on commons AFAIK.

Regards,

Simon


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