Yes, it's typical. The same thing happened with Scripting.

All technical decisions regarding code are made on the dev list, and always 
will be.

We sometimes choose to make non-technical decisions on the PMC list.

-Ted.

On Sun, 23 Jan 2005 13:13:15 -0800, Dakota Jack wrote:
>�At the risk of being flamed, might I ask if this debate, vote,
>�whatever was public or limited to the PMC? �And, might I ask if
>�this was sub rosa (so to speak), is that typical? �I do not mean to
>�suggest anything but merely to gather information about the
>�processes, since these processes impact my use of Struts and my
>�business decisions. Thanks.
>
>�Jack
>
>�<snip>
>�On Sun, 23 Jan 2005 13:03:02 -0800 (PST), Martin Cooper
>�<[EMAIL PROTECTED]>�wrote:
>>�The Apache Struts team is pleased to announce the adoption of its
>>�latest subproject, Struts Shale, a JSF-based framework.
>>
>�</snip>
>
>�--
>�------------------------------
>
>�"You can lead a horse to water but you cannot make it float on its
>�back."
>
>�~Dakota Jack~
>
>�"You can't wake a person who is pretending to be asleep."
>
>�~Native Proverb~
>
>�"Each man is good in His sight. It is not necessary for eagles to
>�be crows."
>
>�~Hunkesni (Sitting Bull), Hunkpapa Sioux~
>
>�-----------------------------------------------
>
>�"This message may contain confidential and/or privileged
>�information. If you are not the addressee or authorized to receive
>�this for the addressee, you must not use, copy, disclose, or take
>�any action based on this message or any information herein. If you
>�have received this message in error, please advise the sender
>�immediately by reply e-mail and delete this message. Thank you for
>�your cooperation."
>
>�--------------------------------------------------------------------
>�- To unsubscribe, e-mail: [EMAIL PROTECTED] For
>�additional commands, e-mail: [EMAIL PROTECTED]




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

Reply via email to