I am following both mailings lists.
I like the distinction between developer and user. Especially, since we have SCM
messages coming into developer.
As a regular user I really don't want to see those, but as a developer I do.
However, if we do decide to merge them. Then merge them into something neutral,
like xmlrpc-general.
My 0.02 Euro,
Jimisola
----- Original Message -----
From: "Henri Gomez" <[EMAIL PROTECTED]>
To: <xmlrpc-dev@ws.apache.org>
Sent: Thursday, February 23, 2006 1:37 PM
Subject: Re: Do we need xmlrpc-dev and xmlrpc-user?
May be a good idea since the traffic is low
2006/2/23, Jochen Wiedmann <[EMAIL PROTECTED]>:
Hi,
the distinction between a mailing list of developers and a different
mailing list of users is typically driven by increasing traffic.
Either of developers or users do not want to accept too many mails,
which aren't of any interest to them. That's fine.
On the other hand, the separation has also a disadvantage: It splits
an existing community into two subcommunities. In the case of xmlrpc-*
this means splitting an already small and weak community into two
smaller and weaker. Additionally, I have the feeling that there isn't
too much contact between these two lists. Upon recently, John Wilson
was the only one I was aware on both lists.
Wouldn't it be good to merge these lists? For example, one could move
all subscribers of xml-rpc-user to xmlrpc-dev and leave xmlrpc-user as
an alias?
Jochen
--
Whenever you find yourself on the side of the
majority, it is time to pause and reflect.
(Mark Twain)
