Mailing-List: contact general-help@incubator.apache.org; run by ezmlm
Message-ID: <3E6F4E22.5050706@apache.org>
Date: Wed, 12 Mar 2003 16:11:30 +0100
From: Nicola Ken Barozzi <nicolaken@apache.org>
Reply-To: nicolaken@apache.org
Organization: Apache Software Foundation
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
 rv:1.3b) Gecko/20030210
MIME-Version: 1.0
To: general@incubator.apache.org
Subject: Incubator - where do we go from here
References: 
 <OF2E331EF6.556E21C6-ONCA256CE6.00822561-CA256CE7.00031621@multitask.com.au>
 <200303121207.12360.conor@cortexebusiness.com.au>
 <20030311235402.A23383@lyra.org>
In-Reply-To: <20030311235402.A23383@lyra.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit


Geez, a night and half a day, and I get loooads of mails and rants on 
the list. Ok, let's see to get some order in it, and be constructive.


First of all:

Roy T. Fielding wrote, On 12/03/2003 3.26:
 >
 > -1.  I see no evidence that the task has been accomplished.
 > Accomplish
 > the task and then the Tapestry committers and Jakarta committers can
 > choose to house Tapestry wherever they like.  The point of incubator
 > is to make sure such self-governing committer groups exist in order
 > for them to make the decision, not for us to make the decision for
 > them.

 From what I read on the other mails, I agree too.
What should we do? Here it comes:

Greg Stein wrote, On 12/03/2003 8.54:
...
 > Constructive criticism of the day:
 > establish the checklist, get projects signed off, and move 'em along.
 > Very objective, and very satisfying to those involved.
...
 >
 > There is a definite need for the Incubator, but I think the people who
 > advocated it as a "community builder" need to reassess that concept.

Ok, I start to see the light here. And what has happened to Tapestry is 
a very clear indication that the above is exactly the point.

So we need a checklist to perform... here goes a version:


Roy T. Fielding wrote, On 12/03/2003 4.18:

 > The same ones you have been saying all along.  Copyright, verification
 > of IP rights (meaning the ASF can distribute the code), establishment
 > of a list of active committers, documented decisions by those
 > committers to do things (like release code, move to Jakarta, etc.),
 > and organizational acceptance of responsibility for the project
 > (i.e., a vote by the destination PMC or creation of a new PMC by
 > the board).


So, what we need now is to decide on this list and get it done.
I also need help here from Dion, Andy and others to see the point we 
have come to WRT these items.
We will define them and asses them in parallel for Tapestry.

* Copyright

  - Have the papers that transfer the rights to the ASF been recieved?
  - Is fax sufficient?
  - Who sent what?

* verification of IP rights (meaning the ASF can distribute the code)

  - What does this exactly mean WRT the previous item?

* establishment of a list of active committers

  - Are all active committers in the STATUS file?
  - Do they have access to CVS?
  - Did they all send the signed paper?
  - Is fax sufficient?

* infrastructure aspects

  - Are mailing lists set up?
  - Are they archived?
  - Is Bugzilla set up?
  - Is the site migrated to our infrastructure?

* documented decisions by those  committers to do things
   (like release code, move to Jakarta, etc.)

  - What does this mean?
  - Who is the release manager?
  - Are releases being properly signed, mirrored and accepted by the PMC?

* organizational acceptance of responsibility for the project  (i.e., a 
vote by the destination PMC or creation of a new PMC by the board).

  - Has the Jakarta PMC accepted it with a vote?

* Responsibility

  - Who is responsibly to this PMC for Tapestry?
  - Who tracks down things in the status file?
       incubator/projects/tapestry/STATUS

As Incubator

  - We need more helpers. If someone wants to become part of this PMC, 
please start helping in any way possible, and we'll vote him in in case.

  - We need to have projects discuss things *here*. I see thiungs being 
done outside, and rants happen here. Not good.

  - We need incubators responsible for projects. I'd propose to be 
responsible for Tapestry ATM.

  - Let's get here the docs that Dion talked about from the tapestry work.

-- 
Nicola Ken Barozzi                   nicolaken@apache.org
             - verba volant, scripta manent -
    (discussions get forgotten, just code remains)
---------------------------------------------------------------------