Mailinglist Archive: opensuse-security (601 mails)

< Previous Next >
RFC: - moderation -
  • From: Roman Drahtmueller <draht@xxxxxxx>
  • Date: Wed, 9 Aug 2000 16:08:29 +0200 (MEST)
  • Message-id: <Pine.LNX.4.21.0008091518520.1283-100000@xxxxxxxxxxxx>
> From: Eduardo Carriles <eduardo.carriles@xxxxxxxxxxx>
> To: SuSE Security Mail List <suse-security@xxxxxxxx>
> Date: Wed, 09 Aug 2000 15:08:48 +0200
> Subject: Re: [suse-security] SuSE security reputation, etc.. [Thread STATS]
> Reply-To: sofronia@xxxxxxxxxxx
> Hi Friends,
> [FYI]
> I did just to inform you, and as a small exercise, some manual processing
> on posts to this _thread_ and those where the [STATS] found as of today.

Hi Eduardo,

We certainly appreciate your eagerness wrt to the statistics you posted,
as it is quite interesting to look at.

However, this is a rather administrative subject, and it doesn't belong
here, as much as questions about SuSE's support for packages where the
license has changed or things that are actually subject to reading an FAQ.

Subscribers might have noticed the increasing amount of non-security
related material in the list, as well as increasing volume every day or
the other. This brings up the question if the list should go moderated or

Taking the risk that the follow-ups will cause a considerable amount of
noise on the list, this question needs an answer. I'd like to hear your
thoughts about the idea as well as the list policy. It is designed to be
very open and targets the list to become more valuable as an information
source and discussion platform, with a small noise ratio and an acceptable

Please feel free to answer personally to me if you don't wish your name to
be published with your opinion.

* Spam gets blackholed.

* Postings that are not related to security will not pass.
Exception: Sometimes threads evolve and provide valuable information
around an issue that is not closely related to security.

* Postings with commercial nature such as announcements of new versions of
commercial software in the security field will pass but will be marked
as such with an addition in the Subject: line in the header.

* Postings with critical content, regardless of the critizism's target, be
it SuSE, another Linux vendor or even hardware manufacturers, _will_ be
posted. It is needless to say that the claim of being independent
requires this allegation.

* As usual, postings will _not_ be modified, authors are responsible for
the content. If you post something, be aware that something that has
been written and published can't be redrawn easily. Polite style almost
always provides the basis for productive critizism, harsh accusations
make people angry.

* I want to point out that moderation does _not_ equal to censorship!
In some (hopefully) rare (f.ex. when a thread becomes too far
off-topic or a flamewar blazes) cases it might be neccessary to kill a
thread, or to collect the last responses for a thread and post them in a
single mail.

* Meta-postings (concerning the list) will always be answered but might
not pass. If the posting addresses the list policy, it _must_ pass.

Postings would be chained into the list in the same sequence as they

- -
| Roman Drahtm├╝ller <draht@xxxxxxx> // "Caution: Cape does |
SuSE GmbH - Security Phone: // not enable user to fly."
| N├╝rnberg, Germany +49-911-740530 // (Batman Costume warning label) |
- -

< Previous Next >