| 1 |
On 03/20/2018 08:08 PM, Rich Freeman wrote: |
| 2 |
> On Tue, Mar 20, 2018 at 7:54 PM, Benda Xu <heroxbd@g.o> wrote: |
| 3 |
>> William Hubbs <williamh@g.o> writes: |
| 4 |
>> |
| 5 |
>>> I do feel that this decision reflects badly on us as a community and |
| 6 |
>>> should be reversed immediately. The proper way to deal with people who |
| 7 |
>>> have bad behavior is to deal with them individually and not put a |
| 8 |
>>> restriction on the community that is not necessary. |
| 9 |
>> |
| 10 |
>> I agree with William. Dealing with individuals makes more sense. |
| 11 |
>> |
| 12 |
>> It boils down to an attitude of assuming outsiders are good (blacklist |
| 13 |
>> to ML) or bad (whitelist to ML) by default. |
| 14 |
> |
| 15 |
> Actually, I think it is more of a technical constraint. It is |
| 16 |
> basically impossible to blacklist somebody on a mailing list, since |
| 17 |
> all they need to do is roll up a new email address. |
| 18 |
> |
| 19 |
> I can think of various arguments for whitelisting or not whitelisting, |
| 20 |
> but it seems silly to blacklist. |
| 21 |
> |
| 22 |
|
| 23 |
require active stewardship (moderation, blacklisting, etc.) |
| 24 |
|
| 25 |
entry barriers to participation (default deny / require whitelist) |
| 26 |
|
| 27 |
if there are limitations on free speech, someone has to bear the burden. |
| 28 |
for gentoo to have list moderation (blacklist approach) which isn't |
| 29 |
dysfunctional, the main barrier to resources will be the human resources |
| 30 |
end of things, not technical constraints. The tools themselves are easy |
| 31 |
enough to use, but people who are willing and able to use them, and with |
| 32 |
a clear guideline for how it needs done is a comrel issue which the |
| 33 |
foundation needs to sort out. |
Archives