On Tue, Oct 16, 2012 at 8:34 PM, Clint Priest <cpri...@zerocue.com> wrote:

> I was thinking more along the lines of a collaborative wiki with
> inline-threaded comments...
>
> > -----Original Message-----
> > From: Jan Ehrhardt [mailto:php...@ehrhardt.nl]
> > Sent: Tuesday, October 16, 2012 8:00 PM
> > To: internals@lists.php.net
> > Subject: Re: [PHP-DEV] Alternatives to mailing list?
> >
> > Yahav Gindi Bar in php.internals (Wed, 17 Oct 2012 03:18:12 +0300):
> > >I may sound old fashioned, but what about a forum?
>
>
I agree that having a forum would have some definite benefits and should be
explored further.  The only caveat I'd add is that it should not be used as
a replacement for the listserv.  The problem with forums is that most
registered users don't check it regularly.  This can lead to obvious
communication problems.  A listserv, on the other hand, rarely suffers from
this because people are far more likely to check their email inbox
frequently and consistently.  The convenience factor with regard to
replies/etc is also apparent.

That said, I do believe we have a bit of a problem with threads getting
scattered due to slight changes in the subject text.  The Property
Accessors thread, in particular, is a bit of a nightmare to navigate.

Perhaps what we need is a listserv with smarter digest options and a full,
forum-like UI.  For example, when you subscribe to a list, you can have the
option of receiving only the first x number of messages via email, after
which you'll just get a one-shot link to the forum thread for further
reading.  Another useful feature could be the creation of user-created
temporary lists.  For example, if there's an RFC thread that's extremely
active but only of interest to the few people who are participating in it,
they could move the discussion to a new list that would only exist for some
defined period of time (preset, while active, etc).

Of course, those would all have to be custom solutions most likely.  But in
an ideal world at least, that's how it would look I think.

---Kris

Reply via email to