Hi Henri,
- A CLA on file from the revival candidate. (resurrector)
The mentor should guide them through a few patches to show they are
committed, then we can make them a committer. I don't think there's
any reason to do CLAs without also making them committers.
I'm not sure we need to
Hi Julius,
If someone is interested in taking over a truly inactive project,
maybe they should fork and start their own SVN repository from their
own domain. The person should make it clear that their fork is in no
way sanctioned by Apache.
That would be OK for projects that are, as you
On 2/14/07, Roland Weber [EMAIL PROTECTED] wrote:
Here is my take on a revival procedure...
Pre-precondition.
We need to define what is inactive and place it in such a state.
Dormant seems a favourite word.
In the recent board report for the Commons components, we've gone with
Inactive to
After reading the followups, -1 to my original idea! :-)
One funny thought:
I love having inactive jars in my classpath. It's the active jars
that give me all the headaches!
--
yours,
Julius Davies
416-652-0183
http://juliusdavies.ca/
Hi Julius (learning here :),
Thanx for the comprehensive and well thought out mail..
Julius Davies wrote:
Thanks for your reply, Martin!
To reiterate (hopefully more clearly this time), I see two dilemmas
and two problems:
Dilemma #1:
--
You can't stop
Hi everyone,
Moving this from the private list to general (this is actually a spin of from a
thread about adding
a committer to an inactive project, hence that it was on private).
Definition list :
Inactive project = a project that has no *developer* community.
The Apache Way :
To become
Hi, Martin, and Everyone,
If someone is interested in taking over a truly inactive project,
maybe they should fork and start their own SVN repository from their
own domain. The person should make it clear that their fork is in no
way sanctioned by Apache.
The only responsibility Apache might
Hi Julies,
Julius Davies wrote:
Hi, Martin, and Everyone,
If someone is interested in taking over a truly inactive project,
maybe they should fork and start their own SVN repository from their
own domain. The person should make it clear that their fork is in no
way sanctioned by Apache.
Thanks for your reply, Martin!
To reiterate (hopefully more clearly this time), I see two dilemmas
and two problems:
Dilemma #1:
--
You can't stop people from forking. Forking is the lowest barrier
way for a committer-less community to revive an inactive project.
