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

Re: Initial Structure

Thread Previous
From:
Tom Hughes
Date:
July 26, 2000 11:54
Subject:
Re: Initial Structure
Message ID:
4cb543e449.tom@compton.compton.nu
In message <20000726173950.I14669@ig.co.uk>
          Tim Bunce <Tim.Bunce@ig.co.uk> wrote:

> On Wed, Jul 26, 2000 at 10:04:04AM -0600, Nathan Torkington wrote:
>
> > The chairs can spin off
> > sub-groups to tackle particular issues, each with goals, a chair, and
> > so on.  The chair's responsibility includes weekly summaries a-la
> > mjd's p6p reduxes, but the chair may delegate to someone else.  The
> > summaries are sent to the parent list.  Summaries of language and
> > internals are sent to the announce list.
>
> Sounds good.

So where do reduxes for the top level lists (internals, language et al) go?

> > The mailing list chairs have access to a web page on perl.org that
> > makes it easy to create or destroy mailing lists.  Once a mailing list
> > is destroyed, its archives are put onto the webiste.
>
> There's the question of whether sub-groups initially inherit the
> subscription list of the parent. I.e., members opt-out or opt-in.
> Perhaps that's a choice for the chair when a sub-group is spawned.

Definately not. We should either do one or the other but lets be
consistent or local administration and filtering will be a nightmare
for me at least.

Tom

-- 
Tom Hughes (tom@compton.nu)
http://www.compton.nu/
...Necessity is a mother.


Thread Previous


nntp.perl.org: Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at ask@perl.org | Group listing | About