----- Original message ---------------------------------------->
From: "Geir Magnusson Jr." <[EMAIL PROTECTED]>
To: Jakarta General List <[EMAIL PROTECTED]>
Received: Sun, 28 Dec 2003 11:11:07 -0500
Subject: Re: [PROPOSAL] Proactively encourage TLP status

>On Dec 28, 2003, at 10:25 AM, Ted Husted wrote:

>> +1
>>
>> I agree that interested volunteers should:
>>
>> * setup a Wiki area describing the TLP process and rationales , AND

>Do you think we all should setup our own individual Wiki page, or work
>together?  I'm getting the feeling you don't want to work together on
>this.

Steve made a proposal I supported, so I demonstrated my support by pitching in.

AFAIK, there's no such thing as a "personal" wiki page (which Steve has already 
proven).


>> * give notice to each and every Jakarta DEV list that the area exists.
>>
>> My main beef is that we have not done due diligence in alerting ALL of
>> the subprojects of the latest developments.

>What 'developments'?  We are discussing things here on general@, and as
>far as I can see, we have no developments yet.  Ted, you seem to be in
>a terrible hurry to push this through.  Can you wait until people come
>back from the holiday break and read and catch up?  the point of doing
>things here is to *increase* participation, not reduce it by rushing
>something through during a generally world-wide western holiday.

I had some time over the holidays myself, so I put together a proposal that reflected 
how I believe we should proceed. Other people responded to that, so I made some 
changes and issued another draft. There were other threads that seemed related to that 
proposal, so I tried to draw them together to see if we could build a consensus.

All I've done is make a proposal for the community to review at its leisure. If a 
consensus were to develop, I'd volunteer to move it along. If not, the kids need shoes 
...


>> I've outlined a wiki page as described by this proposal
>> <http://nagoya.apache.org/wiki/apachewiki.cgi?
>> JakartaPMCTopLevelProjectApplication>, and setup a draft TLP 
>> resolution.
>>
>> I would also volunteer to subscribe to each of the DEV lists and post
>> a message pointing them to the archive of this thread. (Unless another
>> volunteer already has an account setup to do such things. )

>Instead of doing it yourself, why not try to work w/in the PMC 
>structure and get a message that we all agree on, and have one person
>from each project on the PMC send to their community.  It would be a
>good step in the direction you just were espousing in a different
>thread, namely increased participation.

Committers commit. I believe it's something that should be done, so I volunteered to 
do it.

I also mentioned if someone else were ready and willing to do it, I'd be happy to step 
aside.


>> Whether a subproject follows through or not can be totally up to each
>> subproject. The important thing is that we do the due diligence in
>> making sure *everyone* concerned has been apprised.

>LOL. There is no legal requirement that any arbitrary idea that a
>person has *must* be propagated directly to the dev list of each
>sub-project.  Let others join in this...

My point is that  there is a social and ethical requirement to inform the committers 
of the status quo. There are many ways in which the points covered on the 
<http://nagoya.apache.org/wiki/apachewiki.cgi?JakartaPMCPropsedChanges> wiki page 
conflict with the original guidelines.  The only way to ensure everyone is aware of 
the status quo is for a posting to be made to every DEV list. Since I've served on the 
PMC,  I feel jointly responsible for erroneous information. I don't discharge my 
responsibilities lightly.

I guess all that I'm really asking is that a posting be circulated to each DEV list 
regarding the "proposed changes".  As mentioned, I'd be happy to do this myself, or 
help someone else do it, so long as it was done.

-Ted.



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

Reply via email to