[Twisted-Python] Forum vs. mailing list

[Clark C. Evans]

Matthew,

A forum does not solve the core issue of organizing information
into a clear hierarchy of topics, filtering relevant questions
and answers, and a whole host of other items.  While a Wiki or
a Forum could be useful, it will only work if there are several
people who care about its structure, moderate it, and work
hard to make the information useful.   Other than that, threaded
email works just as well.  

IMHO, an AutoFAQ would be more appropriate, in particular, if you
or someone else dedicates significant _time_ to make sure that it
stays orderly and useful.   Sort of a AutoFAQ, you could simply
implement or edit a FAQ.  I'm sure if you kept one up-to-date 
it would glady find its way into the source code.

Probably a more "helpful" item would be a "Weekly Report" 
like the Python Developer's list has.  Some dutiful individual
there scans all of the things discussed, lists the topics
discussed, summarizes them into a single paragaraph and 
provides links to particularly insighful emails.  In my 
opinion, this would be far more useful..

Clark

On Thu, Nov 13, 2003 at 05:39:42PM -0600, Hegedus, Matthew S wrote:
| Philippe Lafoucri?re mentions his favoring of a forum over a mailing list. A
| forum sounds much better to me. Topics can be nicely separated, past
| knowledge can be easily searched, and email inboxes can be freed from much
| clutter (or at least make room for spam). Is it not too late to implement a
| forum?
| 
| Matthew Hegedus
| 
| -----Original Message-----
| From: Philippe Lafoucri?re [mailto:lafou at wanadoo.fr] 
| Sent: Thursday, November 13, 2003 3:14 PM
| To: Twisted
| Subject: Re: [Twisted-Python] Deferred model
| 
| 
| 
| > I'm sure this has been answered a million times before, but here 
| > goes...
| 
| I'm sure too. But I proposed a long time ago (and several times) to use a
| forum instead of a mailing list... 
| 
| > Deferreds do not magically turn blocking code into non-blocking code. 
| > If you place blocking code in a wmfactory_ method, it will still 
| > interfere with the event loop.
| > 
| > If you have blocking code, you can either rewrite it in a non-blocking 
| > manner, or you can use a separate thread to run it. 
| > <http://twistedmatrix.com/documents/howto/threading>
| > 
| > If you give more detail about what you're trying to do, I'm sure one 
| > of the Twisted gurus can explain what the best approach(es) might be.
| 
| I thought of using the setUp method of page. I can start the calculation
| when the page loads, but I don't know what to call (in the callback) when
| it's done (a wmfactory_xxx ?). I'll check the threading part you gave me.
| Thank you !
| 
| -- 
| Philippe
| 
| 
| _______________________________________________
| Twisted-Python mailing list
| Twisted-Python at twistedmatrix.com
| http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python
| 
| _______________________________________________
| Twisted-Python mailing list
| Twisted-Python at twistedmatrix.com
| http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python
|