As the chair of this project I should probably know it better but I wonder
whether we have a project policy that contains guidelines about vote resulting.
Does the -1 of Jörg mean that the Java 5 proposal is rejected?
Quoting http://www.apache.org/foundation/how-it-works.html#management:
"The rules require that a negative vote includes an alternative proposal or a
detailed explanation of the reasons for the negative vote.
The community then tries to gather consensus on an alternative proposal that
resolves the issue. In the great majority of cases, the concerns leading to the
negative vote can be addressed.
This process is called 'consensus gathering' and we consider it a very important
indication of a healthy community."
According to these paragraphs I'd say yes because a) Jörg gave some good reasons
not to switch and b) there are no majority votes but we always need consensus.
Hence we have to find a way to gather consensus. Right?
(Please don't use this thread to discuss the specific problem of whether we
should make Java 5 the minimum JDK requirement. Thanks!)
--
Reinhard Pötz Independent Consultant, Trainer & (IT)-Coach
{Software Engineering, Open Source, Web Applications, Apache Cocoon}
web(log): http://www.poetz.cc
--------------------------------------------------------------------
___________________________________________________________
Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de
