Mailman List Policy for Fedora Hosted

[Mike McGrath]

On Tue, 19 Feb 2008, Jeffrey Ollie wrote:

> Well, I believe that I have most of the technical bits in place for
> Mailman for Fedora Hosted.  Now we just need to figure out a few
> policy items...
>
> 1) Who can request lists? My proposal: anyone that is listed as an
> administrator in the project's group in FAS.
>

anyone can request a list, the filter will be for the admin team to create
it.

> 2) What sorts of lists can be requested?  My proposal: Lists may be
> reqested for discussing the use of, development of, or disseminating
> other useful information about (e.g. announcement or commit lists)
> projects hosted with Fedora.  Lists about non-F/OSS topics or F/OSS
> projects not hosted with Fedora would not be acceptable.


I think thats fine, most common requests $project-users $project-devel
will be easy to just let through.  Questionable ones can always be dealt
with as they come.

> 3) What should the policy on list names be?  My proposal:
>
> A) All list names must be prefixed with "<projectname>-".
> B) All list names must be suffixed with "-list".
> C) Lists may optionally have something between the prefix and suffix,
> as long as it's not obviously vulgar or obscene.
>
> For example, the following would be acceptable list names:
>
> smolt-list
> smolt-dev-list
> smolt-commits-list

We've had requests about this by the individuals to remove "-list" I'm
fine with it as the standard though.  We can add it to the faq.

> The exceptions to this rule would be the default "mailman" site list
> and possibly a list dedicated to discussing the Fedora Hosted service
> itself (name to be determined later).  FESCo or the Fedora Board could
> approve other exceptions.
>
> 4) What should the policy on archives be? My proposal:
>
> A) All lists must have public archives.  The exception would be the
> default "mailman" list.

+1

> B) Requests to remove a post from the archives will be denied unless
> it can be shown that by *not* removing the post RedHat and/or Fedora
> face a credible threat of civil or criminal liability.  We'll likely
> require the assistance of RH Legal to make these sorts of
> determinations (hopefully they will never happen).

I think this might already be covered by our privacy policy.  Either way
we generally don't take stuff down unless there's some technical or other
reason.  Its easy for us to say "no we won't take that down" because
people can escalate to the board.. who will then say no, we won't take
that down :)

Side note: Are the scripts ready?  Do we have an SOP for it yet?

	-Mike