[irtf-discuss] Re: Last call: IRTF Code of Conduct
Wes Hardaker <wjhns1@hardakers.net> Wed, 11 September 2024 22:28 UTC
Return-Path: <wjhns1@hardakers.net>
X-Original-To: irtf-discuss@ietfa.amsl.com
Delivered-To: irtf-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BC936C16943D; Wed, 11 Sep 2024 15:28:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.107
X-Spam-Level:
X-Spam-Status: No, score=-7.107 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=hardakers.net
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6j9lYA6i79al; Wed, 11 Sep 2024 15:28:39 -0700 (PDT)
Received: from mail.hardakers.net (mail.hardakers.net [107.220.113.177]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AD80DC139C65; Wed, 11 Sep 2024 15:28:39 -0700 (PDT)
Received: from localhost (unknown [10.0.0.9]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mail.hardakers.net (Postfix) with ESMTPSA id 143EE2066F; Wed, 11 Sep 2024 15:28:39 -0700 (PDT)
DKIM-Filter: OpenDKIM Filter v2.11.0 mail.hardakers.net 143EE2066F
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hardakers.net; s=default; t=1726093719; bh=w85nOpgY5n49+IWC98LVMmvCA4izA/2EVpxMakeMEc0=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=kUtvZRnoUOX3c7hIIrrICTQhc/NWnTLRTHRQJ7SGup0rqS+Fd7ovxI3zdHkjg0dCd 5uFU6v8SpukbE58etkaueaw0TLjJL1cunY/IfRGQeu+KF6Yota0KL6Hav4HPg4Yg7U dngMQjKJZifYPRhFHAaPnOIIkI3w/SRcCXDRTajo=
From: Wes Hardaker <wjhns1@hardakers.net>
To: Colin Perkins <csp@csperkins.org>
In-Reply-To: <52E73F49-5145-44FB-928F-9F513A55755B@csperkins.org> (Colin Perkins's message of "Wed, 28 Aug 2024 11:47:21 +0100")
References: <52E73F49-5145-44FB-928F-9F513A55755B@csperkins.org>
Date: Wed, 11 Sep 2024 15:28:38 -0700
Message-ID: <yblwmjh7rl5.fsf@wd.hardakers.net>
User-Agent: Gnus/5.13 (Gnus v5.13)
MIME-Version: 1.0
Content-Type: text/plain
Message-ID-Hash: VW4LAZ52YHDIDZZLCSOB7JP5DD7VH25X
X-Message-ID-Hash: VW4LAZ52YHDIDZZLCSOB7JP5DD7VH25X
X-MailFrom: wjhns1@hardakers.net
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-irtf-discuss.irtf.org-0; header-match-irtf-discuss.irtf.org-1; header-match-irtf-discuss.irtf.org-2; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: irtf-discuss@irtf.org, The IRSG <irsg@irtf.org>
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [irtf-discuss] Re: Last call: IRTF Code of Conduct
List-Id: IRTF general and new-work discussion list <irtf-discuss.irtf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/irtf-discuss/SNwAAlY1p8SagE6okgcHP4Uu-UE>
List-Archive: <https://mailarchive.ietf.org/arch/browse/irtf-discuss>
List-Help: <mailto:irtf-discuss-request@irtf.org?subject=help>
List-Owner: <mailto:irtf-discuss-owner@irtf.org>
List-Post: <mailto:irtf-discuss@irtf.org>
List-Subscribe: <mailto:irtf-discuss-join@irtf.org>
List-Unsubscribe: <mailto:irtf-discuss-leave@irtf.org>
Colin Perkins <csp@csperkins.org> writes: > The IRSG is proposing that the IRTF adopt the code of conduct > described in draft-perkins-irtf-code-of-conduct. Thanks for both writing this document and posting it (and to everyone else that has helped contribute toward it). I think it's important to spell out these concerns/topics and look forward to it being published. Having said that (you knew it was coming), some thoughts/issues/nits are below. Note that I have not read any of the other comments, as I always try to do a full independent review in advance of reading other people's discussion topics. [abstract and section 1] - I understand the point behind putting "continue" in "the IRTF will continue to strive", but I'm not sure it's needed. If it's just continuing, then it could be argued the document isn't needed. How about something along the lines of "this document formally codifies the code of conduct that has made the IRTF successful in encourages broad participation, ..." [section 2] - For "Harassment is unwelcome, hostile, or intimidating behaviour..."" I would suggest adding "Harassment *is defined* as unwelcome, hostile or ..." - It would be good to explicitly list virtual meetings: "... other events, mailing lists, *virtual meetings*, or other online forums" - For "Participants must follow the IETF anti-harassment policy..." I struggled a bit with this statement. Obviously, we want it. But it makes the document a little bit less clear as to why it's needed. I'd actually suggest moving this sentence up to the introduction and then specifically referring to section 7 for where differences are spelled out. TL;DR: it's important to clearly state that both the IETF code and this code and that the differences are spelled out in 7. - "Research Group Chair or the IRTF Chair, or with the Ombudsteam" -> "Research Group Chair, the IRTF Chair, or with the Ombudsteam" (suggest dropping the first or) - "... or after consultation with the IRTF Chair by permanently suspending ..." It is not clear from the sentence who is making the final call. Is the IRTF Chair's approval required, or "I just talked with them and they disagreed but I'm banning you anyway". I'd suggest that it should explicit require IRTF chair approval for a permanent ban. - "be raised with the Chair of the [IAB]" - This seems also slightly under-specified. I'd think the IAB chair should also consult with the full IAB to make appeal decisions. [section 3] - "Participants are reminded that reading, writing, and conversing in a language where one is not a native speaker may be difficult, and to treat those doing so with grace if they do so imperfectly." Suggest: Reading, writing, and conversing in a language where one is not a native speaker may be difficult, and IRTP participants should treat those doing so with grace and understanding. - For makeing "other materials accessible to those with impaired vision or disabilities", it would be good to have a reference to a resource here. Supposedly a new one may be published soon that you can point to, though I'm sure there are others that could be used as well. - suggest: "what was meant" -> "when necessary" [section 4] - "...the IRTF may take action against authors..." I'm not sure what to do here. I agree that, obviously, plagiarism [etc] would be bad. But I'm not sure what actions the IRTF can do other than to unpublish works, etc? The IRTF is not a formal body that can "sue" or other external actions. So we should probably list the specific actions that can be taken by the IRTF, such as unpublishing presentations, drafts, and banning participants from future participation? - A new thought for the end of the section: When IRTF document authors are republishing portions of other works of theirs, they must request and receive permission from their co-authors before publishing similar works through the IRTF. (not a perfect sentence, but the point I'm trying to make is that if I write an ID based on work from 3 past published papers with 9 other authors, I'd better get their permission to republish elements). This is slightly different than citing (IMHO). - It might be good to define what "IRTF systems" are. Sorry for the long list. Note that I don't think any of these are absolute show-stoppers IMHO, so I leave these thoughts to the consensus of the wider group(s). -- Wes Hardaker USC/ISI
- [irtf-discuss] Last call: IRTF Code of Conduct Colin Perkins
- [irtf-discuss] Re: [gaia] Last call: IRTF Code of… patrick
- [irtf-discuss] Re: [CFRG] Last call: IRTF Code of… Salz, Rich
- [irtf-discuss] Re: Last call: IRTF Code of Conduct Toerless Eckert
- [irtf-discuss] Re: [nmrg] Last call: IRTF Code of… Bob Natale
- [irtf-discuss] Re: [irsg] Last call: IRTF Code of… Colin Perkins
- [irtf-discuss] Re: [irsg] Last call: IRTF Code of… Toerless Eckert
- [irtf-discuss] Re: [irsg] [nmrg] Last call: IRTF … Colin Perkins
- [irtf-discuss] Re: [IRTF-Announce] Last call: IRT… Colin Perkins
- [irtf-discuss] Re: [irsg] Last call: IRTF Code of… Colin Perkins
- [irtf-discuss] Re: [irsg] Last call: IRTF Code of… Toerless Eckert
- [irtf-discuss] Re: [irsg] Last call: IRTF Code of… Colin Perkins
- [irtf-discuss] Re: [irsg] Last call: IRTF Code of… Toerless Eckert
- [irtf-discuss] Re: [irsg] Last call: IRTF Code of… Colin Perkins
- [irtf-discuss] Re: [irsg] [hrpc] Last call: IRTF … Colin Perkins
- [irtf-discuss] Re: [irsg] Last call: IRTF Code of… Toerless Eckert
- [irtf-discuss] Re: [hrpc] Last call: IRTF Code of… Timothy Holborn
- [irtf-discuss] Re: [irsg] Last call: IRTF Code of… Pete Resnick
- [irtf-discuss] Re: Last call: IRTF Code of Conduct Wes Hardaker
- [irtf-discuss] Re: Last call: IRTF Code of Conduct Colin Perkins
- [irtf-discuss] Re: [IRTF-Announce] Last call: IRT… Colin Perkins