Front page | perl.bootstrap |
Postings from July 2000
While the technical kinks are being ironed out, could the engineers keep
in mind, us folks that would like to keep an ear all around.
Either a list with a digest of messages from each group
Subject: [p6-syntax-3.1.4] Digest 24 Dec 2003
Subject: [p6-XS-3.1.4.1.5.9] Digest 1 Jun 2001
Or individual emails, or ....
<chaim>
>>>>> "TB" == Tim Bunce <Tim.Bunce@ig.co.uk> writes:
TB> On Tue, Jul 25, 2000 at 11:37:14AM -0400, Dan Sugalski wrote:
>> At 11:38 AM 7/25/00 -0400, mjd-list-bootstrap@plover.com wrote:
>> >I suggested to Nat that we could set up a web page or some other
>> >mechanism that would make it very easy to create a mailing list
>> >quickly and then to destroy it again later. (I would volunteer for
>> >this if necessary.) The technical issues are not difficult, because
>> >of EZMLM. The security issues also do not seem to be difficult.
>> >
>> >I would be interested in whether this seems to be a good idea.
>>
>> I'd go for this, especially if the lists had an automatic self-destruct
>> mechanism. ("This list will self destruct in 10 days. Beep!") They'd give a
>> sandbox to contain discussion on a particular topic for a while but keep
>> things from going on interminably.
TB> I agree in general.
TB> I suggest that sub-groups be setup in exactly the same manner as the
TB> parent working group.
TB> We're pretty much agreed that each working group has a chairperson,
TB> mailing list, charter/goals, lifespan (and whatever else) which are
TB> agreed in advance by the Perl6 project manager.
TB> These sub-groups can be defined recursively as mini working groups.
TB> They'd have a chairperson, mailing list, charter/goals, lifespan
TB> (and whatever else) which are agreed in advance with the chairperson of
TB> the parent working group.
TB> Seems kinda neat.
--
Chaim Frenkel Nonlinear Knowledge, Inc.
chaimf@pobox.com +1-718-236-0183
Thread Previous
|
Thread Next