Hi,
I knew that this would come out wrong / will be read wrong.
a) I'm aware that this is not Jakarta. It is Maven. So rules are
probably different (I'm not on the Maven PMC, so all I know are the
public pages on maven.apache.org which is not really much. So I
considered the main apache rules from apache.org to apply)
b) From a personal, scratch my itch, point of view: Great! Bugs fixed,
new plugin, cool.
My concerns are of a different nature: The ASF is a people driven
organization. It is about participation. About people swapping opinions,
discussing topics. Agreeing. Not agreeing. This means, there are a few
rules to which everyone and every project should try to hold up. One of
them is voting and voting periods.
If you run a vote which takes only a few hours and then stop it "because
half of the PMC has voted", then you don't have to run a public vote at
all. Just vote on the PMC list and then release. But if you want people
to react on the vote, maybe try out the code that is voted on and be
able to raise objections (look at the commons-email voting thread that
runs on [EMAIL PROTECTED] We were ready to release and then someone
not really involved with c-e before, raised a valid objection about
dependencies) or concerns, then you do have to take some time to allow
people to react.
If you don't want or care about these reactions, then a project is no
longer people and community driven. Which is _the_ _main_ _point_ of all
ASF projects. This is what I meant with 'just watching the big guys
doing their thing'. Apache and Apache projects is about "everyone can
participate".
The mail went to the users-list because the announcement was sent only
there (I couldn't find it on the dev list, but this can be due to my
personal mailing list setup, if this is the case then apologies). I
agree that -dev is the better choice.
Regards
Henning
On Tue, 2005-09-06 at 18:00 +1000, Brett Porter wrote:
> Wow.
>
> (moving to the dev list, as it is completely inappropriate for the
> users list)
>
> You jump on the list saying how urgent it is you have this released
> because it has been broken for a while. We act to release it as
> quickly as possible, and you complain that it was too quick. Make up
> your mind! :)
>
> Half of the PMC voted. The time that the vote would be open for was
> specified, and elapsed.
>
> As for forwarding a result to the PMC - this is not Jakarta. There are
> not multiple subprojects and a huge number of PMC members - the PMC is
> active in the dev list.
>
> If you are genuinely concerned, feel free to discuss it - but please
> tell me you actually think there was some reason this shouldn't have
> gone ahead.
>
> - Brett
>
> On 9/6/05, Henning P. Schmiedehausen <[EMAIL PROTECTED]> wrote:
> Arnaud HERITIER <[EMAIL PROTECTED]> writes:
>
> >We are pleased to announce the Maven XDoc Plug-in 1.9.2
> release!=20
>
> Folks,
>
> |Subject: [vote] maven-xdoc-plugin 1.9.2 for maven 1.X
> |Date: Sun, 4 Sep 2005 01:40:29 +0000 (UTC)
>
>
> |Subject: [ANN] Maven XDoc Plug-in 1.9.2 released
> |Date: Mon, 5 Sep 2005 21:16:24 +0000 (UTC)
>
> Sorry to bother you, but IMHO it must not work that way. Even
> if the
> maven PMC runs things a bit differently, a voting period of
> not even
> 48 hours isn't the way to go. Also, according to the voting
> rules
> stated on the apache pages and your own maven developer pages,
> you
> should at least post a result to the dev-list (and you
> probably have
> to run the result by the Maven PMC (At least it is like this
> in
> Jakarta land and I don't think it is much different in Maven
> land)).
>
> Running the show like this ("We decided to release. Poof. We
> release.") might be ok for your very own project hosted at
> sourceforge. Not for an Apache project.
>
> You might think about this for future releases. The ASF has
> not many
> rules and they are very flexible but there _are_ rules and the
> point
> is to allow people to participate. Not just to sit and watch
> "the big
> guys do their thing".
>
> Regards
> Henning
>
>
>
> --
> Dipl.-Inf. (Univ.) Henning P.
> Schmiedehausen INTERMETA GmbH
> [EMAIL PROTECTED] +49 9131 50 654 0
> http://www.intermeta.de/
>
> RedHat Certified Engineer -- Jakarta Turbine Development --
> hero for hire
> Linux, Java, perl, Solaris -- Consulting, Training,
> Development
>
> 4 - 8 - 15 - 16 - 23 - 42
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
--
Dipl.-Inf. (Univ.) Henning P. Schmiedehausen INTERMETA GmbH
[EMAIL PROTECTED] +49 9131 50 654 0 http://www.intermeta.de/
RedHat Certified Engineer -- Jakarta Turbine Development
Linux, Java, perl, Solaris -- Consulting, Training, Engineering
4 - 8 - 15 - 16 - 23 - 42
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
