Re: [Ietf-and-github] Archiving a repository?

"Salz, Rich" <rsalz@akamai.com> Tue, 21 April 2020 22:58 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 C16D63A0D52; Tue, 21 Apr 2020 15:58:46 -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 eNBcuJbhNWyx; Tue, 21 Apr 2020 15:58:44 -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 678513A0D57; Tue, 21 Apr 2020 15:58:43 -0700 (PDT)
Received: from pps.filterd (m0122330.ppops.net [127.0.0.1]) by mx0b-00190b01.pphosted.com (8.16.0.42/8.16.0.42) with SMTP id 03LMvKWd032462; Tue, 21 Apr 2020 23:58:43 +0100
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=cEXeSlhamBHKjxApDyLr7CXQaOpxy6nH7TByaec+/Qs=; b=h8hEdILKZ4anEuFMLSZjowbnx3zdj4KAJHeEVtS/xHlG73pnmhQMI3DtCYcImF8Qhuj1 0yS1tKv2GvOwUyDdnKB9P4YYJiG1jSV9Rrap9BDblNLkd4Gg8E0p7F9UCb09b4htS222 xHxKq9iRhMny/ILgrZelmAXCtM/4umpxJKN9+2NeZ3Ebrggoz+k7bX/LCyehy7ATXnso Waujd3S7VdUbsjiF49Zh81wcHZTkBc2VmaYGyjuDYZTvoAHfB6JxzR6H8UPWQ4OZFYD0 h0A2jzkucyiG5cnCZp208DoE4kNBmM4VqOzq2+rAGuY8FMX9wo199AdPBcfKUQCuVQYp GQ==
Received: from prod-mail-ppoint2 (prod-mail-ppoint2.akamai.com [184.51.33.19] (may be forged)) by mx0b-00190b01.pphosted.com with ESMTP id 30fs6wdft9-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 21 Apr 2020 23:58:43 +0100
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 03LMln1S010407; Tue, 21 Apr 2020 18:58:42 -0400
Received: from email.msg.corp.akamai.com ([172.27.165.116]) by prod-mail-ppoint2.akamai.com with ESMTP id 30fvvv0qpu-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Tue, 21 Apr 2020 18:58:42 -0400
Received: from USTX2EX-DAG1MB1.msg.corp.akamai.com (172.27.165.119) by ustx2ex-dag1mb5.msg.corp.akamai.com (172.27.165.123) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Tue, 21 Apr 2020 17:58:29 -0500
Received: from USTX2EX-DAG1MB1.msg.corp.akamai.com ([172.27.165.119]) by ustx2ex-dag1mb1.msg.corp.akamai.com ([172.27.165.119]) with mapi id 15.00.1497.006; Tue, 21 Apr 2020 17:58:27 -0500
From: "Salz, Rich" <rsalz@akamai.com>
To: Jacob Hoffman-Andrews <jsha@letsencrypt.org>, "ietf-and-github@ietf.org" <ietf-and-github@ietf.org>
CC: "<acme-chairs@ietf. org>" <acme-chairs@ietf.org>
Thread-Topic: Archiving a repository?
Thread-Index: AQHWGCqCdv7z3136QU6HyvOLkTHEEKiEe60A///FjQA=
Date: Tue, 21 Apr 2020 22:58:27 +0000
Message-ID: <6B9CB5C2-BBFF-48ED-A724-99E4B171FE03@akamai.com>
References: <7A0F05FE-819B-431E-9069-BCD233C0AAED@akamai.com> <CAN3x4Q=pcy4RHXjymF2W86TdTFN0uO4sL_PdrfNqxB6ScsGXvQ@mail.gmail.com>
In-Reply-To: <CAN3x4Q=pcy4RHXjymF2W86TdTFN0uO4sL_PdrfNqxB6ScsGXvQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/16.36.20041300
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [172.19.37.158]
Content-Type: text/plain; charset="utf-8"
Content-ID: <582F4A2A7AEDFF4183BCF9B3934A79BB@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.676 definitions=2020-04-21_10:2020-04-21, 2020-04-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=947 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-2002250000 definitions=main-2004210167
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.138, 18.0.676 definitions=2020-04-21_10:2020-04-21, 2020-04-21 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 impostorscore=0 malwarescore=0 mlxlogscore=933 suspectscore=0 priorityscore=1501 adultscore=0 lowpriorityscore=0 mlxscore=0 spamscore=0 clxscore=1015 phishscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2003020000 definitions=main-2004210167
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-and-github/SY3BOZReA6TY0ofyuL7thiXoyzE>
Subject: Re: [Ietf-and-github] Archiving a repository?
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: Tue, 21 Apr 2020 22:58:47 -0000

Resending with fixed mailing address.


On 4/21/20, 6:28 PM, "Jacob Hoffman-Andrews" <jsha@letsencrypt.org> wrote:

    The motivating event is that we recently had an issue filed on the
    repo that was more of a support request for an ACME implementer. In
    the long run, an unused repo can attract such requests, as well as
    spam, and comments that are better directed towards the WG mailing
    list.

    On Tue, Apr 21, 2020 at 3:16 PM Salz, Rich <rsalz@akamai.com> wrote:
    >
    > This came up in ACME, where someone suggested we archive the main ACME repo.  I don’t recall this ever coming up in our docs here.  Thoughts?