<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/3.30.3">
</HEAD>
<BODY>
On Wed, 2011-01-12 at 07:15 +0800, Ng Oon-Ee wrote:
<BLOCKQUOTE TYPE=CITE>
<PRE>
On Tue, 2011-01-11 at 18:42 +0100, Nicolas Sebrecht wrote:
> On Mon, Jan 10, 2011 at 05:17:09PM -0500, Philippe LeCavalier wrote:
> >
> > As a user, 90% of what's posted here makes no sense to me and is of
> > little value. Do we need to separate users from devs? If I take my
> > own posts as an example I get about a 50/50 chance of being replied
> > to. I attribute that in part by the abundance of dev posts.
> >
> > This isn't a complaint by any means. I love seeing so much work on
> > this project but at the same time we must maintain an efficient
> > method for resolving end-user problems and concerns.
>
> Then, you could safely filter out threads having the tag PATCH in the
> subject. Another option is to not subscribe to the mailing list.
> Subscription is not a prerequisite to post here.
>
> This mailing list is primaly meant for the development work. I'd like to
> avoid a seperated users mailing list to keep users and developers as
> near as possible, each other.
>
Filtering is the best option I think. Perhaps an additional line at the
bottom of the list footer saying:-
Please filter for the tag [PATCH] if you do not want to receive
code-in-progress
would help?
</PRE>
</BLOCKQUOTE>
I think we're missing the point I was trying to make. The reason I<BR>
suggested this wasn't for my or any ones convenience of reading the<BR>
list . My concern with so much coding mail is that it seems to be burying<BR>
user requests for help. Shouldn't this type of chatter be better documented<BR>
/ more appropriate in a bug tracking system anyway? Pardon my ignorance<BR>
here -I'm getting pretty far off my comfort zone as I don't know much<BR>
about the process of coding especially the communication thereof...<BR>
<BR>
Phil
</BODY>
</HTML>