<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=UTF-8" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Actually, it seems most users like to send messages via their email
client, but like in another email i sent, they also resent their email
clients for lack of pretty graphics, colors, and the mailing list
restriction on annoying HTML markup (namely none allowed) which if you
look at it, is really pointless (would you like to get a email with a
black background and pink text that's bold and some weird, hard-to-read
font? I don't think so)<br>
<br>
Also, apology accepted :) <br>
<br>
James Trotter wrote:
<blockquote
cite="mid99031ea50604221509p50a9ba28u74ca4fe97f0453d@mail.gmail.com"
type="cite">On 4/22/06, <b class="gmail_sendername">Segin</b> <<a
href="mailto:segin2005@gmail.com" target="_blank"
onclick="return top.js.OpenExtLink(window,event,this)">
segin2005@gmail.com</a>> wrote:
<div><span class="gmail_quote"></span>
<blockquote class="gmail_quote"
style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div style="direction: ltr;"> Why aren't I offering suggestions? I
did offer one. The rest are beyond
our control. To attempt to fix those would be as intelligent as
sticking your hand into a boiling pot of water.</div>
</blockquote>
<blockquote class="gmail_quote"
style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div style="direction: ltr;">Let's look at that last one, the
sticky thing. This usually means to
have a email highlighted in a way that it gets the attention of the
user. Now, think about it. There is nothing that we can do to address
this ourselves. If you say we can, you are an idiot. That is something
that must be configured in whatever email client the user is using. <br>
<br>
Now let's look at the email client config thing... Well, we could try
to fix headers of incoming email, but that's not really a solution. In
fact, there is no real solution that we can provide ourselves, and
besides, a properly configued email client (to produce proper headers
and such) is just proper netiuqitte. There is, again, nothing we can do
legally about this (well, we can find a way to break into the users
system and configure his email client for him, but were not here to
hold hands or commit crimes)<br>
<br>
Well, it's pretty obvious you didn't read my comments, think about
them, read the problems i commented against, and thought about those,
and finally thought all of it together. You are just out to troll, and
your reply is just flamebait. Your time would probably best be spent on
USENET, as there are plenty of trolls there.<br>
<br>
And before anyone says I am trolling, you're almost right, except that
I explained why the problems i mention as unfixable by us are just
that. Can we configure the users email client for him? No. Therefore we
can't fix those problems.</div>
</blockquote>
<div><br>
I wasn't trolling, and I'm very sorry if it seemed that way. I didn't
mean to upset you either.<br>
<br>
I suppose you were offering a suggestion, but if I understood it
correctly, it seemed to be: "Let the user fix it." In this case, I
believe we can solve it otherwise and spare the user the trouble
dealing with such complex matters such as configuring mail clients and
dealing with mailing-list interfaces. That's what Mike Hearn's original
(re-)proposal suggested, that we set up a forum using phpBB or the
like. There wouldn't be need for any mail client whatsoever and the
interface is more familiar to the ordinary user. Yeah, call me an
idiot, but we could even have stickies!<br>
<br>
</div>
<br>
<blockquote class="gmail_quote"
style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div style="direction: ltr;"><span>James Trotter wrote:
<blockquote
cite="http://mid99031ea50604221407h2c842c14qfca90a5df781e307@mail.gmail.com"
type="cite">On 4/22/06, <b class="gmail_sendername">Segin</b> <<a
href="mailto:segin2005@gmail.com" target="_blank"
onclick="return top.js.OpenExtLink(window,event,this)">
segin2005@gmail.com</a>> wrote:
<div><span class="gmail_quote"></span>
<blockquote class="gmail_quote"
style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Hello,
I have noted below problems that we can take care of, and those<br>
that aren't our problem, never were, never will be, impossible to be our<br>
problem, (you get the picture), because they are PEBKAC errors :)<br>
<br>
For all of those that don't know: PEBKAC = Problem Exists Between<br>
Keyboard and Chair.</blockquote>
<div><br>
I find this a little crude. You're acknowledging the fact that they are
problems, but dismissing them and not really offering a solution. It
seems to me that a lot of the problems with the mailing list is that
the interface is complex, especially for joe user. The least we can do
is to make it easy for them, and a forum seems to solve many of the
complexity issues. <br>
Take for example 1) Cannot post without configured mail client. If
there was no need for a mail client, there would be no problem.<br>
<br>
</div>
<blockquote class="gmail_quote"
style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Molle
Bestefich wrote:<br>
<br>
>Hi<br>
><br>
>I've tried to sum up the problems with the wine-users mailing list<br>
>that are urging many people to call for a <a
href="http://forum.winehq.org" target="_blank"
onclick="return top.js.OpenExtLink(window,event,this)">forum.winehq.org</a>
.<br>
><br>
>I hope it's useful.<br>
><br>
><br>
>Problems<br>
>========<br>
><br>
> 1) Cannot post without configured mail client<br>
><br>
><br>
An unconfigued client causes hell for EVERYONE they email, not just the
<br>
list members. If that's a problem for people, well, paper and pens still<br>
exist. this is PEBKAC.<br>
<br>
> 2) Browsing old topics and replying/posting new ones happen in two<br>
>different places (web archive vs. mail client) <br>
><br>
><br>
There should be a "server" email address (like majordomo) that you san<br>
send email to for requesting old archived posts. It should be flexible.<br>
This would allow for this problem to be fixed, and the archives to be <br>
access via email (for us that remember email-ftp)<br>
<br>
> 3) Current archive web interface unwieldy (many clicks needed to<br>
>browse, always sorted by month)<br>
><br>
This should be sorted in a 2-pass manner, Each level of posting (the <br>
original post is level one, immedate replies are level 2, and all the<br>
immediate replies to the first replies would be the seveal level 3s)<br>
would be sorted chronologically, and then by level. That's pretty much<br>
how I see mailing lists do that. If you don't understand, email me and<br>
i'll try to explain better.<br>
<br>
> 4) Missing Googlish search function<br>
><br>
><br>
> 5) "Subscribe" wording and web pages suggest your inbox will fill
up <br>
<br>
>when doing so<br>
><br>
><br>
Well, that's not a real problem because it is truthful for some poor<br>
people that don't use Yahoo!/GMail/Hotmail/Excite/etc. (those services<br>
offer large email boxes)<br>
<br>
> 6) Subscribing will cause your inbox to fill up; it's not obvious
how<br>
>to change it; neither how to receive mail on specific topics you DO<br>
>want once you've changed it<br>
><br>
><br>
Solution: Teach users how to properly use their mailbox, or simply get
a <br>
bigger mailbox. If it helps, I'll give people GMail invites just to<br>
counteract this problem (and having to use a stupid web-based email<br>
client as well :) this one is partially our problem, partially PEBKAC,<br>
partially the email providers problem. <br>
<br>
> 7) Missing "forward all postings re this topic to my inbox" feature<br>
> 8) Very difficult to post under pseudonym<br>
><br>
><br>
Not true, just don't include your real name anywhere in your email <br>
setup. I don't. Purely PEBKAC.<br>
<br>
> 9) Missing 'sticky' feature (?)<br>
><br>
><br>
That's not our problem. it's impossible for that to be our problem,<br>
because on a mailing list, sticky stuff is client-side only, no matter <br>
what your client is, which also implies that it's impossible for us to<br>
do jack about it. Purely PEBKAC.<br>
<br>
><br>
>Solution 1: A forum, fx. phpBB<br>
>===============================<br>
><br>
> Pros: <br>
> ) Easy to set up.<br>
> We might even be able to sneak it in before AJ returns :-).<br>
> (Sorry big guy, couldn't resist pulling one on your expense
=)..)<br>
> ) Might attract away from wine-users a high quantity of dumb <br>
>questions that people ask when they can't be bothered to search the<br>
>archives.<br>
> ) Adds a structural approach by categorizing users' various<br>
>problems, which encourages searching instead of asking. <br>
><br>
> Cons:<br>
> ) Dillutes knowledge; some ends up in forum and some on
wine-users,<br>
>unless we nuke wine-users.<br>
> ) Need to hack the code to get visual integration with WineHQ
(menus etc).<br>
> ) To get single-sign-on, we need either a.) reverse proxy or b.)<br>
>something LDAPish and some amount of phpBB hacking<br>
><br>
><br>
>Solution 2: Point people at Gmane or Google Groups in a prominent
place <br>
>========================================================================<br>
><br>
> Pros:<br>
> ) We don't have to do anything :-).<br>
><br>
> Cons:<br>
> ) If it's not directly on <a href="http://winehq.org"
target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
winehq.org</a>, it's probably not official<br>
>enough that people are going to use it.<br>
> ) Not everyone has a Gmail account (required to post through
Groups)<br>
> ) Not everyone is adept to using Gmane<br>
><br>
><br>
>Solution 3: WebForum-on-top-of-List<br>
>====================================<br>
><br>
> Pros:<br>
> ) We concentrate people, allowing web and email users to
communicate.<br>
> ) We concentrate (archived) knowledge in one place. <br>
><br>
> Cons:<br>
> ) The reason that forums are often filled with spam might be that<br>
>it's too easy to post to them. We'd be duplicating that.<br>
> ) We need to code it all ourselves!<br>
><br>
><br>
>I think solution 1 is good, but I prefer the extra icing on the cake<br>
>that comes with solution 3.<br>
><br>
><br>
><br>
>Now, I'm not high on crystal meth or anything, but I'll just assume<br>
>for a moment that we all want better accessibility for the
newcomers <br>
>(even with the rise in volume that they bring), and that all agree
to<br>
>go with solution 3 :-). Thus I'll try to outline a battle plan:<br>
><br>
>Battle-plan for solution 3<br>
>========================== <br>
><br>
>We'd like non-Wine developers to be able to join in; so let's make<br>
>sure that this system is generically usable.<br>
>That means:<br>
> * Standard user authentication, fx. using LDAP.<br>
> * Componentize a bit, fx. keep the web interface itself separate
from <br>
>WineHQ menu structure and logo.<br>
><br>
>We'd need to:<br>
> * Prioritize features<br>
> * Setup a mailing list<br>
> * Setup a simple project web page<br>
> * Setup a winehq-like staging area for development (follows <br>
>HEAD/TIP/origin of web repository so everyone can see what the
others<br>
>are doing)<br>
> * Find developers/volunteers!<br>
> * Get started on the coding<br>
><br>
>When prioritizing features, we should take a look around and see if
<br>
>there are software components available that could be reused, fx.:<br>
> * PHP LDAP auth bindings<br>
> * Existing, good web interfaces for the wine archives (mailman?)<br>
> * ?...<br>
><br>
>Any holes or oversights in that plan? <br>
><br>
>If solution 3 ever takes off, I will gladly contribute with coding.<br>
>Realistically, though, i cannot implement something like this all by<br>
>myself, especially not in any kind of a timely fashion. <br>
><br>
><br>
><br>
><br>
><br>
<br>
<br>
<br>
</blockquote>
</div>
<br>
James D. Trotter<br>
</blockquote>
<br>
</span></div>
</blockquote>
</div>
James D. Trotter<br>
</blockquote>
<br>
</body>
</html>