develooper Front page | perl.bootstrap | Postings from July 2000

Re: HERESY: *ONE* mailing list

Benoit Beausejour
July 26, 2000 11:03
Re: HERESY: *ONE* mailing list
Message ID:

Just to bring another idea on the table and continue the discussion...

I think we also should inspire ourselves a little from the organisation of
a "not-so-away" cousin of Perl, Apache!

The Apache Project has guidelines about development/developers relations,
conflicts resolution and patch's a system that works and
that has proven very efficient over the years. 

I think we could take some parts of what the years have given to Apache
and integrate them in the Perl6 development process...

(Guidelines @

Benoit Beausejour - ( - (SaKa@Quake)
SmartWorker Project (
460 St-Catherine Ouest, Suite 210
Montreal, Quebec H3P 1A7 

On Wed, 26 Jul 2000, Tim Bunce wrote:

> On Tue, Jul 25, 2000 at 08:35:04PM -0400, Adam Turoff wrote:
> > DISCLAIMER: This is just an idea.  It isn't necessarily a good one.
> It seems to me that we're all pretty much agreed on the general
> "spin-off little short term mailing lists as needed" concept.
> And we're also pretty much agreed on the "working groups have goals
> and limited lifespan" concept.
> That makes the working groups and sub groups sound very similar.
> Given that, the issue of "one list" vs "many lists" has a fairly
> natural solution: Let them all come and go as needed.
> The ``Root List'' exists first and "spawns" (charters) working groups
> as needed (determined by the project manager).  The working groups can
> themselves spawn sub groups as needed (determined by the wg chair).
> Picture:
>             Root List
>              /  |  \
>             /   |   \
>            WG  WG   WG
>                / \   \
>               /   \   \
>              SG   SG   SG
> Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at | Group listing | About