Re: [Gendispatch] New Version Notification for draft-ecahc-moderation-00.txt

["Salz, Rich" <[e-mail]>]

I am posting to the gendispatch list because that is where the document says discussion should happen.

In Section 3, Motivation, the MODML reference doesn’t really give guidance to chairs for this general case being discussed by this document. It describes how WG chairs should act if they make their WG list moderated, which is different.

The term PR-Action should be defined when first used, I think.

In section 4.1, Scope, the sentence “If is not expected that the moderator team will be monitoring every IETF channel…” should appear much earlier in the document.

In Section 4.3, Appeals, this sentence confuses me: Disagreements with a decision by the IETF Chair can be brought to their attention.  Does “their” refer to the IETF Chair? And if so, is it reasonable to expect that the IETF Chair having decided will change their mind? Isn’t disagreements with IETF Chair decisions can be appealed?

Have you considered having some subset of the organizational bodies and ISOC appoint members or liaisons?

From: Lars Eggert <[e-mail]>
Date: Thursday, July 6, 2023 at 1:48 PM
To: 'WG Chairs' <[e-mail]>
Cc: Alissa Cooper <[e-mail]>, Brian Carpenter <[e-mail]>, Jari Arkko <[e-mail]>
Subject: Fwd: New Version Notification for draft-ecahc-moderation-00.txt

Hi,

FYI, we've just submitted a proposal for a new approach to moderating the IETF's various contribution channels. It borrows a lot from the current moderation approach for the IETF discussion list, but applies the idea to all the IETF's contribution channels.

One open question is if WG chairs should retain the task (or at least ability) to moderator their WG lists. We'd be interested in your thoughts here, and of course on anything else related to the document.

Please do note that it's a -00 and has some known omissions, but we wanted to float the idea at this time so we can discuss at IETF 117.

Thanks,
Lars

PS: Note that I will be on vacation until July 17, but (most) of the co-authors should be around.


Begin forwarded message:

From: [e-mail]
Subject: New Version Notification for draft-ecahc-moderation-00.txt
Date: July 6, 2023 at 20:41:29 GMT+3
To: "Brian E. Carpenter" <[e-mail]>, "Alissa Cooper" <[e-mail]>, "Brian Carpenter" <[e-mail]>, "Jari Arkko" <[e-mail]>, "Lars Eggert" <[e-mail]>, "Russ Housley" <[e-mail]>


A new version of I-D, draft-ecahc-moderation-00.txt
has been successfully submitted by Lars Eggert and posted to the
IETF repository.

Name:                   draft-ecahc-moderation
Revision:              00
Title:                      IETF Community Moderation
Document date:                2023-07-06
Group:                  Individual Submission
Pages:                   9
URL:            https://www.ietf.org/archive/id/draft-ecahc-moderation-00.txt
Status:         https://datatracker.ietf.org/doc/draft-ecahc-moderation/
Html:           https://www.ietf.org/archive/id/draft-ecahc-moderation-00.html
Htmlized:       https://datatracker.ietf.org/doc/html/draft-ecahc-moderation


Abstract:
  This document describes the creation of a moderator team for all of
  the IETF's various contribution channels.  Without removing existing
  responsibilities for working group management, this team enables a
  uniform approach to moderation of disruptive participation across all
  mailing lists and other methods of IETF collaboration.




The IETF Secretariat