<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Abusive behaviour on a mail list is not new. AtomPub had some interesting "personalities" involved.<div><br></div><div>I'm not proposing that abusive behaviour is acceptable.</div><div><br></div><div>I'm suggesting that abusive behaviour is subjective, and that education and guiding the conversation to constructive ends is preferred to ejecting someone from the community.</div><div><br></div><div>-- Dick</div><div><br></div><div><div><div><div>On 2009-11-29, at 8:25 PM, David Recordon wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">I don't know the specifics, but it sounds like the AtomPub working group dealt with similar issues. <a href="http://friendfeed.com/dewitt/818a5c22/question-how-much-name-calling-personal-slurs">http://friendfeed.com/dewitt/818a5c22/question-how-much-name-calling-personal-slurs</a><br>
<br><div class="gmail_quote">On Sun, Nov 29, 2009 at 10:19 PM, Dick Hardt <span dir="ltr"><<a href="mailto:dick.hardt@gmail.com">dick.hardt@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Dave<br>
<br>
In all your time on IETF lists, how many times have you seen a participant banned from a list?<br>
<font color="#888888"><br>
-- Dick<br>
</font><div><div></div><div class="h5"><br>
On 2009-11-29, at 8:09 PM, Dave CROCKER wrote:<br>
<br>
> The link I sent earlier:<br>
><br>
> <<a href="http://mipassoc.org/dkim/ietf-list-rules.html" target="_blank">http://mipassoc.org/dkim/ietf-list-rules.html</a>><br>
><br>
> points to the IETF's enforcements procedures.<br>
><br>
> d/<br>
><br>
> Chris Messina wrote:<br>
>> On Sun, Nov 29, 2009 at 9:06 PM, Dave CROCKER <<a href="mailto:dhc2@dcrocker.net">dhc2@dcrocker.net</a> <mailto:<a href="mailto:dhc2@dcrocker.net">dhc2@dcrocker.net</a>>> wrote:<br>
>> Chris Messina wrote:<br>
>> I've gone ahead and adapted the microformats policy to our own:<br>
>> It doesn't say anything about enforcement rules. What are the<br>
>> procedures for determining whether someone has violated the policy,<br>
>> and what are the consequences of such an assessment?<br>
>> Do you have proposals on what they should be?<br>
>> Generally I think it's up to the discretion of the list owners/admins to make such decisions. If any decisions made are deemed unreasonable, I think they'll have the community on their case about it (as is the present situation).<br>
>> I don't know of any suitable alternative, given that we're talking about a mailing list.<br>
>> Chris --<br>
>> Chris Messina<br>
>> Open Web Advocate<br>
>> Personal: <a href="http://factoryjoe.com/" target="_blank">http://factoryjoe.com</a><br>
>> Follow me on Twitter: <a href="http://twitter.com/chrismessina" target="_blank">http://twitter.com/chrismessina</a><br>
>> Citizen Agency: <a href="http://citizenagency.com/" target="_blank">http://citizenagency.com</a><br>
>> Diso Project: <a href="http://diso-project.org/" target="_blank">http://diso-project.org</a><br>
>> OpenID Foundation: <a href="http://openid.net/" target="_blank">http://openid.net</a><br>
>> This email is: [ ] shareable [X] ask first [ ] private<br>
><br>
> --<br>
><br>
> Dave Crocker<br>
> Brandenburg InternetWorking<br>
> <a href="http://bbiw.net/" target="_blank">bbiw.net</a><br>
> _______________________________________________<br>
> general mailing list<br>
> <a href="mailto:general@lists.openid.net">general@lists.openid.net</a><br>
> <a href="http://lists.openid.net/mailman/listinfo/openid-general" target="_blank">http://lists.openid.net/mailman/listinfo/openid-general</a><br>
<br>
_______________________________________________<br>
general mailing list<br>
<a href="mailto:general@lists.openid.net">general@lists.openid.net</a><br>
<a href="http://lists.openid.net/mailman/listinfo/openid-general" target="_blank">http://lists.openid.net/mailman/listinfo/openid-general</a><br>
</div></div></blockquote></div><br>
</blockquote></div><br></div></div></body></html>