Mailing-List: contact general-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: general@incubator.apache.org
Message-ID: <3F0A90DA.3010506@wyona.org>
Date: Tue, 08 Jul 2003 11:37:30 +0200
From: Michael Wechner <michael.wechner@wyona.org>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4b) Gecko/20030507
MIME-Version: 1.0
To: general@incubator.apache.org
Subject: Re: Some sparse nots about changes to the incubation process
References: <3F0A8B31.6070906@apache.org>
In-Reply-To: <3F0A8B31.6070906@apache.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Nicola Ken Barozzi wrote:
> 
> Looking at how Lenya is now incubating, here are some notes, that aim to 
> resolve some problems that have arised in incubation.
> 
> 1. Appointing someone from this PMC to look over a project is a good 
> idea. If I weren't on that list (via gmane in case anyone checks ;-) 
> this PMC would not know how it's going.
> 
> 2. What about having the incubated project send the incubator PMC 
> monthly status reports of what has happened, and more important, of the 
> things done in the incubation process?

I think this is a good idea, because it helps the incubated project to 
refocus on its status. I would also send the same report to
the "Parent PMC", in our case the Cocoon PMC.

Thanks

Michael

> 
> 3. We need to make a boilerplate doco for the new incubating projects 
> that clearly states what they have to do for incubation. We have some 
> docs, but a clear mail wil only the things pertaining to them would be 
> nice.
> 
> 4. Making the incubating project have it's own CVS module is a terrible 
> idea. It gives the incubating project and the new users the idea that 
> the project is already a full-apache project. This is the same problem 
> that had arised on Avalon, where projects that were really sandbox code 
> started appearing in the main excalibur CVS, making users use them as 
> they were properly released, which was not true.
> 
> All incubating projects therefore should reside in the incubator module.
> I'd also propose that all committers of the sponsoring PMC can have 
> access to it, as well as all the committers from other incubating 
> projects (so they can eventually lend a hand in need).
> 
> 5. The PMC that has asked for that projects has to cater for it too. 
> There needs to be at least one from that PMC that co-works with the 
> incubator advisor on the project list.
> 
> 6. Making a separate mailing list right from the start that is in the 
> final destination address is again IMHO not a good idea. I would propose 
> that all incubating projects start de-facto on the 
> projects@incubator.apache.org ML, and eventually migrate to 
> nameoftheproject@incubator.apache.org.
> 
> 7. The webpage of teh incubatong project should have the incubator logo 
> and the project one. The final PMC may link to it, and have their logo 
> somewhere else on the page, but not as part of the header.
> 


-- 
Michael Wechner
Wyona Ltd.  -   Open Source Content Management   -   Apache Lenya
http://www.wyona.com              http://cocoon.apache.org/lenya/
michael.wechner@wyona.com                        michi@apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org