incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rolf Kulemann <>
Subject Re: [OT] How to prevent abusing Apache priviliges
Date Sun, 17 Oct 2004 14:10:16 GMT
On Sun, 2004-10-17 at 15:14, Steven Noels wrote:
> Speak freely 
> and your voice will be heard. We're all here to learn.

That is maybe why the thread was started, dunno, and I really already
learned from it, since I'm not very ASF experienced, yet. If Thorsten
would have known better, he wouldn't have started the thread.

I guess speaking freely about such a _possible_ happening is the main
problem here, since private mails are involved, but maybe privacy of
emails and netikette do not matter to everybody, but to me. 

Of course your idea of "speaking freely" would be an option (see below).
I like very much more the approach to send private mail to the source,
too, because maybe the first (or following related) private mails were
misunderstood and talking about that freely would make unnecessary noise
and would invlove people, which again misinterpret it. 

Don't you like the idea?

> (and imagine yourself being an outsider reading this thread: how would 
> you read it? what would you think of the incubator, or the ASF as a 
> whole?)

I guess this thread isn't damaging anything, because it's as you say
"blue skying" (I prefer the word abstract here). I for myself could
imagine that's interesting to outsiders, too, since it shows that we
care about such things.

To summarize the ideas up to now:

1.) send back a private mail to clarify maybe with another ASF veteran
(or another appropriate person) on cc -> good idea :)

2.) Just talk freely about such a matter on a closed list like *pmc*@ ->
depends on the concrete facts

3.) Just talk freely about such a matter on open not backed up lists
like incubator@ -> depends on the concrete facts

4.) Just talk freely about such a matter on open backed up lists like
community@ or *-(dev|users)@ -> obviously a really bad idea

Additional to the above items:

5.) Engrave sense making options from above somewhere appropriate that
we do not need to discuss it again. This is maybe an incubator task, if
at all.

I really do not like number 3.) and 4.). I think number 5.) is a must,
but that's maybe only my opinion. Number 1,2, depending on the facts,
are my personal favorites.

I think it is absolutely ok to clarify what is the best way to
communicate and clarify such sensitive problems and I can not understand
this pressure making related to "come and say whats happened dude".

I hope my contributions to this thread are not misinterpreted.

My one Euro :)

Rolf Kulemann

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message