Scott Eade <[EMAIL PROTECTED]> writes:

Hi,

I'm a bit late to the show but I hope that I have caught up with the
various messages sent here.

[ For those of you who do not follow the Velocity lists: I helped
moving Velocity out of Jakarta and into TLP status and was the last
one on the tree when it came to calling for a PMC chair, so I am
currently serving in that function. ]

First things first: No worries! Becoming a TLP is an easy thing, as
long as there are enough developers devoted to keeping the project
running. That is the most important thing. The TLP normally puts next
to no overhead onto the project, except that once per quarter, a board
report has to be written and sent to the ASF board. Normally this
report can be prepared on the Wiki and is no big deal.

Becoming a TLP means that the project forms its own Project Management
committee (PMC). This means a few things legal-wise, because the PMC
and the PMC chair are actually responsible for all software released
by the project. There is a longer explanation about the
responsibilities of the PMC at
http://www.apache.org/foundation/how-it-works.html#pmc

Especially this means that a project like Turbine can no longer hide
below the (pretty large and somewhat paralyzed) Jakarta PMC. On our
own, we report directly to the board and one of the board members will
watch the progress of the project closer (currently mainly the Jakarta
chair and a few interested PMC members are watching. Hello Martin!).

What is needed to form a PMC is a number of people willing to provide
oversight. A few of them should be ASF members but not all need
to. Not all need to be active Turbine committers; some familiarity
with the code is appreciated but not required. All PMC members must be
committers, though. Oversight is more important. The PMC is a
legal/organisatorial thing, not a code controlling tool.

Off my head, I can think of 
 * seade
 * sgoeschl
 * tv
 * hoffmann
 * wglass,
 * henning
 * brekke

which are four active and three somewhat 'alumni' committers. This is
more than Velocity had at inception and it should work fine. Will,
Scott and I are members, so that should be no problem, too.  (Actively
serving on a PMC also is a step towards membership BTW, see
http://www.apache.org/foundation/how-it-works.html#roles :-) )

(Yes, that means that I would be willing to serve on the PMC for
oversight. However, my current day job does not allow me to
participate in more than one project as a developer, so my programming
time is currently geared towards Velocity. Sorry 'bout that).

Next thing would be to steal^Wcreate a TLP proposal. There are a
number of proposal examples in the board minutes. Adapting one to
Turbine is not a hard thing. The proposal should contain a list of
people serving on the PMC and a PMC chair. I would like to propose
Scott for PMC chair, BTW (he is the intersection between the committer
and members, which makes him the logical candidate).

Once the proposal passes the board, there is at first some
infrastructure work to do: Moving the web site, changing links and
mailing list addresses etc. (to get some idea, look at
http://issues.apache.org/jira/browse/VELOCITY-470).

This mainly needs constant prodding of infra to get things done. Not a
hard thing, but it is important to be persistent. Also, in the first
three months, montly reports are expected by the board, so this is the
time where the new PMC shows that it works.

>Let's discuss this here before I go to the trouble of putting a proposal 
>together.

I'm very +1 on leaving Jakarta before the ship sinks. With the current
commons TLP proposal, the holes became bigger.

I know that Juergen and Thomas will be at ApacheCon EU; we can team up
there and maybe set up an IRC channel for further discussion and
collaboration on getting the TLP off the ground. Will and I surely can
provide guidance as we already went through the process once with
Velocity. So let's do it.

        Best regards
                Henning


-- 
Henning P. Schmiedehausen  -- [EMAIL PROTECTED] | J2EE, Linux,               
|gls
91054 Buckenhof, Germany   -- +49 9131 506540  | Apache person              |eau
Open Source Consulting, Development, Design    | Velocity - Turbine guy     |rwc
                                                                            |m k
INTERMETA - Gesellschaft fuer Mehrwertdienste mbH - RG Fuerth, HRB 7350     |a s
Sitz der Gesellschaft: Buckenhof. Geschaeftsfuehrer: Henning Schmiedehausen |n

               "Save the cheerleader. Save the world."

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to