Splitting comp.lang.python

Cameron Laird claird at starbase.neosoft.com
Wed Mar 1 07:15:58 EST 2000


In article <20000301105629.A4323 at nl.linux.org>,  <gerrit at nl.linux.org> wrote:
>Hello,
>
>Quoting Fredrik Lundh <effbot at telia.com>,
>> this month, comp.lang.python has seen nearly
>> 50% more posts than any month before:
>> 
>>     http://www.egroups.com/group/python-list/info.html
>>     http://starship.python.net/crew/just/FindMailStats/
>
>4000 messages in 29 days is a lot. it's 138 messages a day. Previous
>discussions on splitting c.l.py always ended up in jokes and just
>disappeared; I want to resurrect an informal discussion on wheter
>to split the newsgroup or not; an RFD should be posted, of course,
>but IANAL: does anyone have time to create an RFD?
>
>    I propose to split c.l.py in a technical part and a non-technical part.
			.
			.
			.
No, no one has time to create an RFD.

I speak from experience.  Newsgroup creation requires
more commitment, and even passion, than you'd expect.
Only someone not discouraged by my discouraging words
will have the perseverance required to endure the pro-
cess.

By the way, Gerritt, you and Fredrik and I seem to be
running into each other a lot.  The most typical pat-
tern is that you say something enthusiastic, and then
effbot and I grumble at you.  That's what I (and he?)
will do now:  I don't understand your proposal.  If
it's to spawn a comp.lang.python.advocacy, well, I
think that's worth discussing.  If the suggestion is
that speculations about timbot's ontology and book re-
views be labeled "non-technical" ... I just don't see
that as viable.

I've got loads of informed opinions about newsgroup
dynamics.  If people truly want to pursue this, and
none of the other old-timers jump in, I'll write up
some of what I've seen.
-- 

Cameron Laird <claird at NeoSoft.com>
Business:  http://www.Phaseit.net
Personal:  http://starbase.neosoft.com/~claird/home.html



More information about the Python-list mailing list