Re: [TOOLS-DEVELOPMENT] Backing up Github WG repositories

"Martin Thomson" <mt@lowentropy.net> Wed, 26 February 2020 23:56 UTC

Return-Path: <mt@lowentropy.net>
X-Original-To: tools-development@ietfa.amsl.com
Delivered-To: tools-development@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6533D3A0BBC for <tools-development@ietfa.amsl.com>; Wed, 26 Feb 2020 15:56:59 -0800 (PST)
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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, 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=lowentropy.net header.b=Q8y2UJ5d; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=XjdHpMnm
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 t7iATckBu3w4 for <tools-development@ietfa.amsl.com>; Wed, 26 Feb 2020 15:56:57 -0800 (PST)
Received: from wout2-smtp.messagingengine.com (wout2-smtp.messagingengine.com [64.147.123.25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9CA9C3A0BB9 for <tools-development@ietf.org>; Wed, 26 Feb 2020 15:56:57 -0800 (PST)
Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.west.internal (Postfix) with ESMTP id A571F65B; Wed, 26 Feb 2020 18:56:56 -0500 (EST)
Received: from imap2 ([10.202.2.52]) by compute2.internal (MEProxy); Wed, 26 Feb 2020 18:56:56 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lowentropy.net; h=mime-version:message-id:in-reply-to:references:date:from:to :subject:content-type; s=fm1; bh=Nn8DhH+aV0Jj5IOnFRs/k8F43duQgaV BYbwkLOjdWiM=; b=Q8y2UJ5dW7Goc2Wctk5n7z0nMJQHX2Q38Byp0g1vEFmgne1 rpTGBC9m/WtW0vThp6nN5K2U5N8/3ikiF4U3jZ7zb2FIXONG2I/VrbxHz1tQpeat hJJSeq6Y35+9vDX3HXuIE7b9jgmimd3BoVZsrMdV//P03bbJ+2kdi0AUWGGTaV59 /kXSMRuf4RGxgA95qrDkEjGamSfxbx/rlzd5R86Q9mDpnUdX3Ipq6fdrvNslfAC9 3A+evCvHLrRzWhTzLQ51cwz+uPFVCoh9O/71ZSiGNB3ZnH6cc1DoOCiXR1oheBbw LD+cBLswkjOmtSaHzqqkT7pIWoHCIambEoya7qA==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=Nn8DhH +aV0Jj5IOnFRs/k8F43duQgaVBYbwkLOjdWiM=; b=XjdHpMnmy7GFREG053VkNu 3sQjtgRpjar38IrY9C6pCr6SImT95AZfCBT/rQNgHJ7qlFptIeDwco8fs5fKiG5Z YSXPaMVGZvj7pH6Y3kPB+JoShpf2g+PkuV6/Zph0P9CmJAxMpwm6mB+Ds34uiSQc moZ+RQUM5wUNe05EcbRiuNGxO2Zst35v4fyJ7AVoM4BrzcEguYcm3llaKLAMLB9r yUW5Nu63InE2mvphE1+Gh/5v6Ox8siD/gil8KfZdxfS5XqW9JgnRymvFaN0iYqDJ QGnp2X9xHSD5vnCDw4CN/xZRorjFZnfZigJqJkBhUzwkG/emcHiVdZ4OZ99zlKTA ==
X-ME-Sender: <xms:xwVXXl5yokcTHzQEZ8g60IbCsfjPT1GqjowN2EgiEumysND2he8C6A>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedugedrleehgddukecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefofgggkfgjfhffhffvufgtsehttdertderredtnecuhfhrohhmpedfofgrrhht ihhnucfvhhhomhhsohhnfdcuoehmtheslhhofigvnhhtrhhophihrdhnvghtqeenucffoh hmrghinhepghhithhhuhgsrdgtohhmnecuvehluhhsthgvrhfuihiivgeptdenucfrrghr rghmpehmrghilhhfrhhomhepmhhtsehlohifvghnthhrohhphidrnhgvth
X-ME-Proxy: <xmx:xwVXXvmAdTUEzWdS1rvgx42hF9M_E0Vf6es7U8Xst1iKy6kHvUI6tw> <xmx:xwVXXlj13oQhTk-zqOssAnDc1KKQIxowkNWmjngAqkhnRrDy3H21JQ> <xmx:xwVXXjK0s8IA4uH7-rRs3S714826Ntf7HSkR5QPE5o_b2ummaVKSDw> <xmx:yAVXXuwqPPtZ81S6FpNjdGJ4OGVQzi5zT-xT13Bk5_vFd2yjhzZwKw>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id D93B7E00AC; Wed, 26 Feb 2020 18:56:55 -0500 (EST)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.1.7-947-gbed3ff6-fmstable-20200220v2
Mime-Version: 1.0
Message-Id: <7d0e1230-7fab-4aed-bc64-55a4ca8438ad@www.fastmail.com>
In-Reply-To: <9eaed56c-6fb8-6037-3bcf-14776ac2f328@nostrum.com>
References: <9de49701-4477-291a-9a98-a39feb819a44@nostrum.com> <66380131-5b4e-4fa4-860c-08b240929e7f@www.fastmail.com> <2acd5e5e-0a1e-7658-964f-ca8d881b76f2@nostrum.com> <a3b33093-03d4-4c78-b5d4-8709f60b9fd6@www.fastmail.com> <9eaed56c-6fb8-6037-3bcf-14776ac2f328@nostrum.com>
Date: Wed, 26 Feb 2020 16:56:35 -0700
From: Martin Thomson <mt@lowentropy.net>
To: Robert Sparks <rjsparks@nostrum.com>, IETF Tools Development <tools-development@ietf.org>
Content-Type: text/plain
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-development/uGToKtpCF7YskLf3_s6yBJgoRk4>
Subject: Re: [TOOLS-DEVELOPMENT] Backing up Github WG repositories
X-BeenThere: tools-development@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Tools Development list server <tools-development.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tools-development>, <mailto:tools-development-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tools-development/>
List-Post: <mailto:tools-development@ietf.org>
List-Help: <mailto:tools-development-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tools-development>, <mailto:tools-development-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Feb 2020 23:56:59 -0000

On Wed, Feb 26, 2020, at 14:32, Robert Sparks wrote:
> > To download an archive of your repository, you can use the API for user or organization migrations. For more information, see "Migrations <https://developer.github.com/v3/migrations/>" in the GitHub Developer documentation. 
>
> Now, it's clear from the warnings about the API changing without 
> advance notice during the preview period that this is not yet stable, 
> but it is what they aim people at right now. 
> 
> Do you read their documentation differently?

https://developer.github.com/v3/migrations/users/#download-a-user-migration-archive is a more targeted link.  I don't know about the format of the dump you get.

> So, we 
> clearly specify that we have a requirement to capture labels and 
> comments, and leave it to the bidders to propose tools that will do 
> that, yes? We can make sure the language where we point to potential 
> solutions doesn't imply they are fit, or preferred.

Sounds good.  Thanks.