Thorsten Scherler wrote:
El lun, 10-07-2006 a las 23:41 +0200, Michael Wechner escribió:
Thorsten Scherler wrote:
Discussion seems to have settled down on this topic,
so it must be time for a Vote.
This concerns everyone on the dev mailing list,
so please all vote, not just PMC committers.
Review the current draft at http://lenya.zones.apache.org/docu/guidelines.html
for the latest version.
Apart from possible minor tweaks, are you happy with the
current content?
As a preamble I would like to note, that I am currently on paternity
leave and will not be able to be very responsive until next week, but
nevertheless I will try to give some feedback:
I wish you have done this in the feedback time prior to this vote (like
everyone else). Doing it in the vote is very deconstructive
I voted -1 and explained why.
and it seems
that you have not read the proposal when we ask for it.
what else should I do if we never really discussed it?
- I think the mission of Apache Lenya needs be more detailed, e.g.
framework with out of the box samples, scalable, performant, backwards
compatible, ... I think we really need to define our goals resp. link
to a document which is defining the goals explicitely, otherwise I am
afraid this whole thing is pointless.
If you feel that we should redefine the mission statement (like you
hinted in many threads) then please raise it in a separate thread, maybe
present a proposal and we can discuss on it.
ok, will do so
- Re emeritus: What means "not contributing in any form"?
no mail, no commit to the code base, no nothing.
if that's the meaning that we should add this definition, otherwise
discussions will happen
again and again ....
- Re the PMC chair: What means "the chair has the power to establish rules
and procedures"? Isn't that the role of the PMC itself?! And what means
"including of the PMC itself"? Hmm?
The chair is the ASF officer in charge (like a chairman of a board of a
company). She has the last word and can overrule the pmc.
I am -1 on this. What would be agreeable to me is that if the PMC is
undecisive which
means for instance 3 versus 3 then the PMC chair can decide.
Please see
http://www.apache.org/foundation/how-it-works.html#pmc for more detailed
explanation.
- I think the Quartely reports need to be approved by the PMC before sending
to the board
Yes I think this is a good idea, but why didn't you raised before.
I raised it several times on the PMC mailing list
Now
it will have to wait till after the vote
- Electing PMC members: I think the general rule should be that
committers are not PMC members from the very beginning when they become
committers.
You can raise this later.
I also raised this several times in discussion before
- Voting: Conensus means to me that everyone agrees or do I
misunderstand consesus?
No, if you really mean *everyone* (like in all active committer have to
vote), that is "Unanimous consensus".
- Voting: Why the term lazy majority and not just majority?
This points out that not all pmc member have to vote.
- Veto: why does the pmc chair has the power to decide if a veto is
valid or not
it comes with the role. see above link:
"...has the power to establish rules and procedures for the day to day
management of the communities for which the PMC is responsible..."
again, I am -1 on this, because I do not understand why the PMC chair should
have so much power in this type of community as Lenya is
- voting procedure: i guess not all votes will be done on the dev list?!
¿?
http://lenya.zones.apache.org/docu/guidelines.html
"...Where necessary, PMC voting may take place on the private PMC
mailing list..."
I guess I have missed this sentence
- code management: why are old branches unmaintained?!
Why maintain them when they are old?
old doesn't mean these are useless and often a lot of people
still use them and send it patches.
as a result of my questions and remarks I am -1 re the content of
these guidelines
You had the change to comment on this guidelines a long time. You
decided to wait till it came to the vote.
was the vote announced resp. discussion closed?
Why?
see above
Without being negative, but generally speaking I think people haven't really
read this document closely and hence just say +1. I hope I am wrong.
Interesting now all +1's are uninformed and have not read the
guidelines.
let them speak for themselves
Nevertheless I still believe that we should start with a white sheet of
paper
and vote on every "paragraph" and also attach a reasoning for each
paragraph.
See the thread from Michael Ralston regarding this point.
so I assume you have the same opinion as Michael Ralston.
Michi
salu2
--
Michael Wechner
Wyona - Open Source Content Management - Apache Lenya
http://www.wyona.com http://lenya.apache.org
[EMAIL PROTECTED] [EMAIL PROTECTED]
+41 44 272 91 61
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
