commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Craig R. McClanahan" <craig...@apache.org>
Subject Re: A new VOTE list commoons-vote
Date Mon, 03 Feb 2003 19:10:03 GMT

-1 on a voting list separate from the DEV list for a given project.

There are two main reasons for my view on this:

* People who search the DEV mailing list archives should be
  able to see both the discussions around design decisions
  and the votes with a single search; making them look two
  places is painful.

* People who vote should not have the option to do so without
  subscribing to the DEV list and at least seeing the discussions
  about what they are voting on (much better, of course, if
  they actually *participate* in those discussions as well).

Commons is a little funny because we've got multiple (somewhat overlapping
but basically independent) development groups sharing a single mailing
list.  However, there is already a mechanism to deal with that -- separate
DEV list for a particular component, if the developers of that component
so choose (like [ttpclient] did.  IMHO, votes on [httpclient] issues
should be done where the developers are, which is commons-httpclient-dev,
rather than on commons-dev itself.  If you've got a separate developers
list, it should be used for everything that would otherwise happen on
commons-dev.

Craig


On Mon, 3 Feb 2003, Jeffrey Dever wrote:

> Date: Mon, 03 Feb 2003 13:12:32 -0500
> From: Jeffrey Dever <jsdever@sympatico.ca>
> Reply-To: Jakarta Commons Developers List <commons-dev@jakarta.apache.org>
> To: Jakarta Commons Developers List <commons-dev@jakarta.apache.org>
> Subject: A new VOTE list commoons-vote
>
> The most recent dicsussion of having a commons-vote list had pretty good
> support but the thread died away.
>
> Not having a dedicated place to vote is a continuous problem for
> HttpClient, and would be for any other project that is looking towards
> its own list.  When we vote, we have to decide:
>
>     1) to post on the commons-httpclient-dev list where people most
> interested in httpclient hang out (about 130 subscribers)
>     2) post to the commons-dev list where most of the commons committers
> are subscribed
>     3) cross post and risk getting flamed and fragmenting the results to
> make the result difficult to veryify
>
> A dedicated list would completely solve our voting problem.
>
> Recently we have seen a number of poorly formed votes on commons.  That
> is just expected in the current framework.  The dev list is so casual,
> that it is natural to expect casual votes.  A dedicated vote list would
> give us well defined location to look to for examples, not 350 messages
> ago in the archives or somewhere on the website but right there, on the
> list.
>
> I'm not going to propose a vote on this issue myself: I'm just happy
> being the release prime for HttpClient. I'm certainly willing to help,
> but this is somthing that should be driven at a higher level.  I would
> be very impressed if someone on the PMC would take up this cause and at
> least present a proposal here that we can vote on and bring this issue
> to a close one way or another.
>
> -jsd
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


Mime
View raw message