IETF Logo Mail Archive

Re: [Ietf-and-github] Rules regarding ownership of orgs

"Salz, Rich" <rsalz@akamai.com> Mon, 16 March 2020 14:05 UTC

Return-Path: <rsalz@akamai.com>
X-Original-To: ietf-and-github@ietfa.amsl.com
Delivered-To: ietf-and-github@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C0D923A08C5 for <ietf-and-github@ietfa.amsl.com>; Mon, 16 Mar 2020 07:05:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level:
X-Spam-Status: No, score=-2.1 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=akamai.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2v0zi0cTf7WQ for <ietf-and-github@ietfa.amsl.com>; Mon, 16 Mar 2020 07:05:02 -0700 (PDT)
Received: from mx0a-00190b01.pphosted.com (mx0a-00190b01.pphosted.com [IPv6:2620:100:9001:583::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9FBF03A08BD for <ietf-and-github@ietf.org>; Mon, 16 Mar 2020 07:05:02 -0700 (PDT)
Received: from pps.filterd (m0122333.ppops.net [127.0.0.1]) by mx0a-00190b01.pphosted.com (8.16.0.42/8.16.0.42) with SMTP id 02GDhPDU018618; Mon, 16 Mar 2020 14:05:02 GMT
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=akamai.com; h=from : to : subject : date : message-id : references : in-reply-to : content-type : content-id : content-transfer-encoding : mime-version; s=jan2016.eng; bh=6CrWoSCZXaDcF9yb3I+unMqe4AkyfUyOfluu3hFXR0A=; b=L9DBLfeyMBRbJPe25YBNoZ9tznwXli1V72GKXwfW/LRHlAuQAyov9Lb3emRCEgMmzhcI K0AFZvjCW6sSUGlclKL5LtGycamYxJwe8NqbThdvjTWkkQjmFdNNMLbhIxn7ILxMz5Lr dXZFmNkMSb1XU94SXnXg9GWgRIGxAxphsfc81rwjRW2J0t9vZrsPPSralkkwBTUdpCsi tYXOEwup8mFpevKvEGsAcYiYonSr0JA52PHCr+NeqtXpUgN37YFRNSU2mNeiGDNuzk5h 73PCQTkhu4mFtVU7TS+ZMzdbPiCLtRiOq0UIWriMChdcIN/QpHkezhsjQmYwNKzm+0Di fg==
Received: from prod-mail-ppoint2 (prod-mail-ppoint2.akamai.com [184.51.33.19] (may be forged)) by mx0a-00190b01.pphosted.com with ESMTP id 2yrva5ye9p-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Mon, 16 Mar 2020 14:05:02 +0000
Received: from pps.filterd (prod-mail-ppoint2.akamai.com [127.0.0.1]) by prod-mail-ppoint2.akamai.com (8.16.0.27/8.16.0.27) with SMTP id 02GDlRA1019137; Mon, 16 Mar 2020 10:05:01 -0400
Received: from email.msg.corp.akamai.com ([172.27.123.34]) by prod-mail-ppoint2.akamai.com with ESMTP id 2yrtkvcyhg-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Mon, 16 Mar 2020 10:05:00 -0400
Received: from USMA1EX-DAG1MB1.msg.corp.akamai.com (172.27.123.101) by usma1ex-dag1mb4.msg.corp.akamai.com (172.27.123.104) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Mon, 16 Mar 2020 10:05:00 -0400
Received: from USMA1EX-DAG1MB1.msg.corp.akamai.com ([172.27.123.101]) by usma1ex-dag1mb1.msg.corp.akamai.com ([172.27.123.101]) with mapi id 15.00.1497.006; Mon, 16 Mar 2020 10:04:59 -0400
From: "Salz, Rich" <rsalz@akamai.com>
To: Martin Thomson <mt@lowentropy.net>, "ietf-and-github@ietf.org" <ietf-and-github@ietf.org>
Thread-Topic: [Ietf-and-github] Rules regarding ownership of orgs
Thread-Index: AQHV+0fLpgVLWAg4aEiFanXBcfrtZKhLQTKA
Date: Mon, 16 Mar 2020 14:04:59 +0000
Message-ID: <E4B2E3EC-5338-4C4A-B404-A64E308D9A10@akamai.com>
References: <26230b6d-d241-40d9-9290-0c91fdb8e88e@www.fastmail.com>
In-Reply-To: <26230b6d-d241-40d9-9290-0c91fdb8e88e@www.fastmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/16.35.20030802
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [172.19.118.20]
Content-Type: text/plain; charset="utf-8"
Content-ID: <0E5C7B370DCEE84EB6E8E364D62BCB5E@akamai.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.138, 18.0.572 definitions=2020-03-16_03:2020-03-12, 2020-03-16 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 suspectscore=0 malwarescore=0 phishscore=0 bulkscore=0 spamscore=0 mlxscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-2002250000 definitions=main-2003160068
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.138, 18.0.572 definitions=2020-03-16_03:2020-03-12, 2020-03-16 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 suspectscore=0 bulkscore=0 mlxlogscore=990 lowpriorityscore=0 malwarescore=0 impostorscore=0 mlxscore=0 phishscore=0 priorityscore=1501 clxscore=1015 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2003020000 definitions=main-2003160068
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-and-github/DNXBpiayhHXlMhxMMxbKHT02Z_w>
Subject: Re: [Ietf-and-github] Rules regarding ownership of orgs
X-BeenThere: ietf-and-github@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Discussion of using GitHub in IETF activities, particularly for Working Groups" <ietf-and-github.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-and-github>, <mailto:ietf-and-github-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-and-github/>
List-Post: <mailto:ietf-and-github@ietf.org>
List-Help: <mailto:ietf-and-github-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-and-github>, <mailto:ietf-and-github-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Mar 2020 14:05:05 -0000

In the cases I'm familiar with, we have 2+ AD's and 2 WG chairs.  I think that's enough redundancy.

How about saying "four or more people should be admin's of the organization"  And if the secretariat would create a "role" account (not tied to any user, just available for any secretariat staff who need it), that could be a backup.

v2.35.0 | Report a Bug | By Email | System Status