[VOTE] Merge dev lists

[Rahul Akolkar]

[Suggestion is to please reply to the ***@jakarta list only]

This is a vote to consolidate the development lists at Jakarta into
one development and one notifications list. For background including
timing, anticipated benefits and some discussion, see proposal [1]
thread.

[ ] +1
[ ] -1

While not required, it'd be nice if anyone voting against could
briefly state the reason(s). And you're ofcourse welcome to vote +/-0
if you really want.

Vote will run atleast 72 hours and will close no sooner than Thursday 5 pm EST.

TIA.
-Rahul

[1] (long, possibly fragmented URL below)
http://mail-archives.apache.org/mod_mbox/jakarta-general/200910.mbox/%***@mail.gmail.com%3e

[Hanson Char]

-1

Too much noise to signal ratio - not everyone is interested in every Jakarta
projects. Notification list consolidation seems fine, but probably not dev.

Post by Rahul Akolkar
This is a vote to consolidate the development lists at Jakarta into
one development and one notifications list. For background including
timing, anticipated benefits and some discussion, see proposal [1]
thread.
[ ] +1
[ ] -1
While not required, it'd be nice if anyone voting against could
briefly state the reason(s). And you're ofcourse welcome to vote +/-0
if you really want.
Vote will run atleast 72 hours and will close no sooner than Thursday 5 pm
EST.
TIA.
-Rahul
[1] (long, possibly fragmented URL below)
---------------------------------------------------------------------

[Quasar]

-1

The reasons Rahul explained are certainly valid for developers
subscribed to more than one dev list.
In my case, being subscribed to only JMeter dev list, I don't see
advantages in having all prjs in the same list; on the contrary, I'll
get more "useless" messages.

But of course this is only my opinion. Whatever decision will be taken,
I'll be part of the dev list.

Giuseppe

Post by Rahul Akolkar
This is a vote to consolidate the development lists at Jakarta into
one development and one notifications list. For background including
timing, anticipated benefits and some discussion, see proposal [1]
thread.
[ ] +1
[ ] -1
While not required, it'd be nice if anyone voting against could
briefly state the reason(s). And you're ofcourse welcome to vote +/-0
if you really want.
Vote will run atleast 72 hours and will close no sooner than Thursday 5 pm EST.
TIA.
-Rahul
[1] (long, possibly fragmented URL below)
---------------------------------------------------------------------
.

[Rahul Akolkar]

[Relaying result to all lists]

The vote to merge dev lists at Jakarta has passed with the following
binding votes cast:

5 +1s:
Felipe Leme
Daniel Savarese
Vadim Gritsenko
Rahul Akolkar
Stephen Colebourne

2 +0s:
Sebastian Bazley
Rony Flatscher

2 -1s:
Thomas Vandahl
Torsten Curdt

I also count 4 non-binding +1s (Mark Murphy, Venkat Krishnamurthy,
Henri Yandell, Jörg Schaible) and 3 non-binding -1s (Hanson Char,
Giuseppe, Tim Cronin). Two non-binding +1s were cast by folks who
until recently were on the PMC (bayard, joehni) so perhaps not giving
their votes enough credit is getting too technical here.

We'll encourage simple conventions (as Commons was mentioned, for
example) to make filtering email, searching archives etc. as
convenient as we can on a shared list. Hope is that will alleviate to
some extent the primary concern of those who've voted against.

I will open an INFRA ticket for this merge in a week or so (after I
post another heads up note with more details, dev mailing list
conventions etc. to the lists).

Thanks to everyone who voted.

-Rahul

Post by Rahul Akolkar
This is a vote to consolidate the development lists at Jakarta into
one development and one notifications list. For background including
timing, anticipated benefits and some discussion, see proposal [1]
thread.
[ ] +1
[ ] -1
While not required, it'd be nice if anyone voting against could
briefly state the reason(s). And you're ofcourse welcome to vote +/-0
if you really want.
Vote will run atleast 72 hours and will close no sooner than Thursday 5 pm EST.
TIA.
-Rahul
[1] (long, possibly fragmented URL below)