Hi Dhruv & Dominque, Please may I ask if you collect any data, e.g., over the last couple of years, on the moderation actions that you need to take at all? E.g., - number of times that you needed to moderate (at each of the various levels) - the number of specific participants that you have needed to send moderation requests to (perhaps per year, and in total). My instinct, that may be wrong, is that you only need to do moderation infrequently and it is only necessary to send these moderation requests to very few individuals. I think that collecting and making this data publicly available might be helpful for the community to have visibility on what level of moderation happens on the IETF list. Regards, Rob > -----Original Message----- > From: ietf <ietf-bounces@xxxxxxxx> On Behalf Of IETF Moderators > Sent: 25 August 2022 10:53 > To: Scott Bradner <sob@xxxxxxxxx>; John C Klensin <john-ietf@xxxxxxx> > Cc: ietf@xxxxxxxx > Subject: Re: Notification to list from the IETF Moderators team > > Hi John & Scott, > > The process that we followed is listed at > https://github.com/ietf/Moderators/blob/main/sop.md > > - We sent an initial suggestion off-list only, with an offer of > assistance with re-framing and listing the consequences for continued > inappropriate postings. > > - We made another request to take a voluntary 5-day "cooling off" > period, with an offer of assistance with re-framing and listing the > consequences for continued inappropriate postings. > > - When the request was ignored and the inappropriate posting continued, > we took the action to temporarily restrict posting rights for 14 days. > Before taking this action, we took an approval from the IETF Chair. > > Apart from the recent instance, the moderators team has sent initial > requests in 2021 and 2020 as well. > > = > > Community is free to discuss what is appropriate/acceptable as well as > comment on the process moderators team follow. And as Lars said the > procedures can change based on the community consensus, but until then > we are charged to act as per them. > > Thanks! > Dhruv & Dominque > The Moderators team for ietf@xxxxxxxx > > > > On 8/25/22 00:30, Scott Bradner wrote: > > agreeing with John - seems to me that this is a case of the cure causing > significantly more problems than the > > original issue. > > > > many of us over the years have been the targets of Masataka Ohta's > pointed comments - sometimes the comments > > stung more than a bit but there was always a reason that he was > commenting and ignoring the underlying reason > > to focus on the delivery misses a clear contribution to the discussion at > hand. > > > > I also join John in asking for an explanation of what specific triggers > contributes should avoid so as to not > > be subject to your censorship? > > > > thanks > > > > Scott > > > > > >> On Aug 24, 2022, at 1:18 PM, IETF Moderators <moderators@xxxxxxxx> > wrote: > >> > >> Hi all, > >> > >> We wanted to let the list know that the Moderators team for > ietf@xxxxxxxx (described in more detail at [1]) has determined that Masataka > Ohta has engaged in a pattern of abuse based on their recent messages to > this list [2][3]. Their posting rights to the ietf@xxxxxxxx mailing list have been > restricted for the next 14 days. We encourage everyone to review the IETF > discussion list charter [4] and avoid postings that include uncivil commentary > [5]. > >> > >> Thanks, > >> Dhruv Dhody on behalf of the Moderators team for ietf@xxxxxxxx > >> > >> [1] https://www.ietf.org/how/lists/discussion/ > >> [2] https://mailarchive.ietf.org/arch/msg/ietf/bOI2y4p8AnyEGzOe- > 4C4wpBhTpo/ > >> [3] https://mailarchive.ietf.org/arch/msg/ietf/mg6pT8Po- > QcsB8g6N1z2aFSbqLw/ > >> [4] https://www.rfc-editor.org/rfc/rfc9245.html > >> [5] https://github.com/ietf/Moderators/blob/main/unprofessional- > commentary.md > >>
