IETF Logo Mail Archive

Re: [Ietf-and-github] Tools for GitHub backups

"Salz, Rich" <rsalz@akamai.com> Sat, 21 March 2020 13:48 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 70BE03A13D4; Sat, 21 Mar 2020 06:48:31 -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 gq__sk_Ypn61; Sat, 21 Mar 2020 06:48:30 -0700 (PDT)
Received: from mx0b-00190b01.pphosted.com (mx0b-00190b01.pphosted.com [IPv6:2620:100:9005:57f::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 1A0F43A13CF; Sat, 21 Mar 2020 06:48:29 -0700 (PDT)
Received: from pps.filterd (m0050102.ppops.net [127.0.0.1]) by m0050102.ppops.net-00190b01. (8.16.0.42/8.16.0.42) with SMTP id 02LDklAa000417; Sat, 21 Mar 2020 13:48:29 GMT
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=akamai.com; h=from : to : cc : subject : date : message-id : references : in-reply-to : content-type : content-id : content-transfer-encoding : mime-version; s=jan2016.eng; bh=fuoNfDjeuyxktk6Wbkw9LeNItNxI+tWcIgClxGwNAv8=; b=FFjQoWlO/AE2R0ZuF4XeeaTv97+KOr/nhTbBfPaHRBG/paxB+wfBteU/U5MyJt+iV2qA o8a6r5YF8qK7a+v9lvSS+lTyuawz/fK0+BjH0GLjCy+KB1dX5ZpcqLmEXsfcpr94MeLW VgAcHyOC3sslkGkqH51RayJdK1d+tJfmy7AC1kd98iRfCoKRSNQZy56J/CtH/EWsBa2P tR6C1c1vYUAvEeQ7PVi7ty7HWnfAtB23wu1g2klk+QjECQw8jb5f1L6O6rh6c5bOG4Ny xCsK4veorK+yAI6n6cmTJx0ln87KPWsqfaEuoiqblzfN+MQFT8k/D0vSmsBMI2RoR+2U 1g==
Received: from prod-mail-ppoint2 (prod-mail-ppoint2.akamai.com [184.51.33.19] (may be forged)) by m0050102.ppops.net-00190b01. with ESMTP id 2yw8vhhyqt-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Sat, 21 Mar 2020 13:48:29 +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 02LDlL7d026103; Sat, 21 Mar 2020 09:48:28 -0400
Received: from email.msg.corp.akamai.com ([172.27.123.31]) by prod-mail-ppoint2.akamai.com with ESMTP id 2ywe8u8jhf-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Sat, 21 Mar 2020 09:48:28 -0400
Received: from USMA1EX-DAG1MB3.msg.corp.akamai.com (172.27.123.103) by usma1ex-dag1mb1.msg.corp.akamai.com (172.27.123.101) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Sat, 21 Mar 2020 09:48:27 -0400
Received: from USMA1EX-DAG1MB3.msg.corp.akamai.com ([172.27.123.103]) by usma1ex-dag1mb3.msg.corp.akamai.com ([172.27.123.103]) with mapi id 15.00.1497.006; Sat, 21 Mar 2020 09:48:27 -0400
From: "Salz, Rich" <rsalz@akamai.com>
To: Martin Thomson <mt@lowentropy.net>
CC: "wgchairs@ietf.org" <wgchairs@ietf.org>, "ietf-and-github@ietf.org" <ietf-and-github@ietf.org>
Thread-Topic: [Ietf-and-github] Tools for GitHub backups
Thread-Index: AQHV/nNDEcNuTK7KeEmmieiunIfXXqhR0I+AgAEFCoCAADxKAA==
Date: Sat, 21 Mar 2020 13:48:26 +0000
Message-ID: <E72785B9-971D-4D44-93FB-2E249BCBDE84@akamai.com>
References: <6c820473-d7ab-47c5-885b-56ea519ebefc@www.fastmail.com> <FA5BB18F-1C1E-48DE-AF06-625255B93EA7@tzi.org> <b804a3c3-85b4-4d61-9717-3a0a56116d5f@www.fastmail.com>
In-Reply-To: <b804a3c3-85b4-4d61-9717-3a0a56116d5f@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.63]
Content-Type: text/plain; charset="utf-8"
Content-ID: <0F290F20840DB74680952E10CF1AC272@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.645 definitions=2020-03-21_05:2020-03-20, 2020-03-21 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=605 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-2002250000 definitions=main-2003210082
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.138, 18.0.645 definitions=2020-03-21_05:2020-03-20, 2020-03-21 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 malwarescore=0 adultscore=0 bulkscore=0 mlxlogscore=582 priorityscore=1501 clxscore=1015 impostorscore=0 lowpriorityscore=0 suspectscore=0 spamscore=0 mlxscore=0 phishscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2003020000 definitions=main-2003210082
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-and-github/_p3cdRQIlUEsCvTqZ79wjThcRL4>
Subject: Re: [Ietf-and-github] Tools for GitHub backups
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: Sat, 21 Mar 2020 13:48:32 -0000

> It saves this ... it saves that ...

So in order to do a backup if the WG uses your CI tooling to save data in the repo, then anyone can clone the repo and it's all set.  If they don't use this, then the secretariat will need to be an owner to use other tooling to do a backup.

v2.23.0 | Report a Bug | By Email