From nobody Mon Feb 3 07:28:24 2020 Return-Path: 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 61EEE120112 for ; Mon, 3 Feb 2020 07:28:23 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.7 X-Spam-Level: X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=cooperw.in header.b=Jy3PGurC; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=VuurspoM 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 Afo4WXfzPHys for ; Mon, 3 Feb 2020 07:28:21 -0800 (PST) Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F3141120961 for ; Mon, 3 Feb 2020 07:28:20 -0800 (PST) Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 54EB221B6A for ; Mon, 3 Feb 2020 10:28:20 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute7.internal (MEProxy); Mon, 03 Feb 2020 10:28:20 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cooperw.in; h= from:content-type:mime-version:subject:message-id:date:to; s= fm2; bh=nLUJv6Mpsqbkq2bGISp02kAxJy/7GuDp93IBgL1mEyA=; b=Jy3PGurC WT0qxILgtVVeYaOD40RDKnlwTYl8fm8iI6+ebW5Io8QN6xHunteJ1vrlxzyXBVf8 YgBFoMhw/d3pQbgPio2TMyiGXNAGQbTnMy8E902jDraajzJ0xBB0GlXJDVzZkZeG qa/df028emlHhtZZtpSH/2JemBchkfyGR7b/OuWza4EZSvsuuzfHjrEdRE4+1DNx oIEpcbnHVp7VgyZf9S1XrqbQM85d6ityJHX3Kz7T9f6YiYRSOUgm6Fp6O2DO23lz 8fTP9vcUqwQg+dfTczKGxYwX7H5/rJ9eGzJcXQR9+nLESY9Ma3/B92D0nEDTDasO rqhjZm88tRTzqg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:message-id :mime-version:subject:to:x-me-proxy:x-me-proxy:x-me-sender :x-me-sender:x-sasl-enc; s=fm1; bh=nLUJv6Mpsqbkq2bGISp02kAxJy/7G uDp93IBgL1mEyA=; b=VuurspoMW9j2EK92/WoxuDA2s3mzmmZBV3UPkG8BNxtcu McN6KkVhAJIplwlnI93ZrpPc29ceLw6tuWXuq3le5YAo824zenjzv6ZkVwhQT6Bl M9UGDEPi5semKL2Dif39KYP1BQfoE0tzaW690yXuNOTb+8RaQko2NRHwNrsr44mq +N2qlN+b/jBARvIfUJV22qD+lSOyTwPiDH7ox0C7vbzMrsGr/MibnNd8dEIyq7GU DOo5EAnfOFBnAB3JHuJz8fuuprqOdetOx2zqxEroOJw3DX0/Zu4OIRfHMnoKZIww sd8QN3Kh/8NeQosoxned4CwccCKyWhGb10/Qwbbag== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedugedrgeejgdejgecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefhtggguffkfffvofesrgdtmherhhdtjeenucfhrhhomheptehlihhsshgrucev ohhophgvrhcuoegrlhhishhsrgestghoohhpvghrfidrihhnqeenucffohhmrghinhepih gvthhfrdhorhhgpdhgihhthhhusgdrtghomhenucfkphepudejfedrfeekrdduudejrdej heenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpegrlh hishhsrgestghoohhpvghrfidrihhn X-ME-Proxy: Received: from rtp-alcoop-nitro2.cisco.com (unknown [173.38.117.75]) by mail.messagingengine.com (Postfix) with ESMTPA id ECBFA3280064 for ; Mon, 3 Feb 2020 10:28:19 -0500 (EST) From: Alissa Cooper Content-Type: multipart/alternative; boundary="Apple-Mail=_05E178BD-9322-4A08-BB24-B62AE5B28593" Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\)) Message-Id: <02C6478F-B5DB-467D-BE10-855C3067895F@cooperw.in> Date: Mon, 3 Feb 2020 10:28:24 -0500 To: IETF Tools Development X-Mailer: Apple Mail (2.3445.9.1) Archived-At: Subject: [TOOLS-DEVELOPMENT] Tools architecture and strategy team X-BeenThere: tools-development@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Tools Development list server List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Feb 2020 15:28:23 -0000 --Apple-Mail=_05E178BD-9322-4A08-BB24-B62AE5B28593 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 Hi all, As many of you are aware, I=E2=80=99ve been working on putting together = a new team in the General area, the Tools Architecture and Strategy = team. The announcement below is likely to go out within the next day or = two, so I wanted you to know it is coming. Jay and I have had a couple = of chats with Robert about operationalizing the liaison relationship = between the teams and they will be continuing to hammer out the details = as the TAS team spins up. Feel free to send questions my way. Thanks, Alissa ---- To: ietf-announce@ietf.org , = ietf@ietf.org Subject: IETF Tools Architecture and Strategy Team Body: Hi all, I'd like to introduce a new team that has been created in the General = area: the Tools Architecture and Strategy (TAS) team. The current set of tools supported by the IETF Tools Team, including = Datatracker, Postconfirm, Mail Archive, XML2RFC, RFCDiff, and = YANGCatalog, has been developed and maintained over many years by = committed volunteers and contractors. The current tools suite has been = developed with extensive input and contributions from the community, and = as a result many previously unmet needs are today being met with the = IETF tools. As with many community-driven software development efforts, IETF tools = implementations have seen contributions from multiple developers and the = tools footprint has spread organically over many years. While this has = been productive it has been in the absence of a well defined = architecture and strategy that unites them all together. Given the = breadth of functionality in the tools suite and advances in how software = is developed, guiding architectural principles to which IETF tools align = and an overall strategy that sets out general objectives and means of = achieving them are necessary, applicable across the full tools suite. The IETF Tools Architecture and Strategy (TAS) team is tasked with = developing this architectural and strategic guidance for IETF tools = development. Initial topics that the TAS team may wish to consider = include: =E2=80=A2 End-to-end coverage of the IETF participant workflow =E2=80=A2 Extensibility and maintainability =E2=80=A2 Operational scalability, performance, and security profiles of = tools =E2=80=A2 User experience design, testing, and analysis It is not the role of the TAS team to implement, maintain, or manage the = operation of individual tools. Those responsibilities remain with the = IETF tools team. Once TAS team guidance documents become available, the = IETF Tools Project Manager (Robert Sparks) will establish plans and = workflows to align ongoing and future tools development with the = guidance. The TAS team is expected to consult widely with the IETF community, to = draw on best practices from the software development industry and open = source communities, and to evolve its guidance over time as practices = change. The team's online presence resides at: Datatracker page: https://datatracker.ietf.org/group/tools-arch/about/ = Mailing list (open to members, with a public archive): = tools-arch@ietf.org Github organization: https://github.com/ietf-team-tools-arch = The TAS team members and team leaders are appointed by the General Area = Director. The composition of the team is meant to reflect understanding = of the IETF tools suite and its history as well as cloud software = development processes and deployments. Team leadership changes are = expected approximately every two years. Team membership will be assessed = and potentially refreshed annually. The initial team members are: Jari Arkko Silvia Botros Jay Daley (LLC liaison) Tony Hansen Tero Kivinen John Levine Mark Nottingham Rich Salz (co-lead) Jim Schaad David Schinazi Robert Sparks (tools team liaison) Martin Thomson (co-lead) If you have questions about the team, feel free to send them to me or = the co-leads, Rich Salz > and = Martin Thomson >. Best, Alissa Cooper IETF Chair --Apple-Mail=_05E178BD-9322-4A08-BB24-B62AE5B28593 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8
Hi all,

As many of you are aware, I=E2=80=99ve been working on = putting together a new team in the General area, the Tools Architecture = and Strategy team. The announcement below is likely to go out within the = next day or two, so I wanted you to know it is coming. Jay and I have = had a couple of chats with Robert about operationalizing the liaison = relationship between the teams and they will be continuing to hammer out = the details as the TAS team spins up.

Feel free to send questions my = way.

Thanks,
Alissa

----

To: ietf-announce@ietf.org, ietf@ietf.org
Subject: IETF Tools Architecture and Strategy Team
Body:

Hi all,

I'd like to introduce a new team that has been created in the = General area: the Tools Architecture and Strategy (TAS) team.

The current set of tools supported by the IETF = Tools Team, including Datatracker, Postconfirm, Mail Archive, XML2RFC, = RFCDiff, and YANGCatalog, has been developed and maintained over many = years by committed volunteers and contractors. The current tools suite = has been developed with extensive input and contributions from the = community, and as a result many previously unmet needs are today being = met with the IETF tools.

As with many = community-driven software development efforts, IETF tools = implementations have seen contributions from multiple developers and the = tools footprint has spread organically over many years. While this has = been productive it has been in the absence of a well defined = architecture and strategy that unites them all together. Given the = breadth of functionality in the tools suite and advances in how software = is developed, guiding architectural principles to which IETF tools align = and an overall strategy that sets out general objectives and means of = achieving them are necessary, applicable across the full tools suite.

The IETF Tools Architecture and Strategy (TAS) = team is tasked with developing this architectural and strategic guidance = for IETF tools development. Initial topics that the TAS team may wish to = consider include:

=E2=80=A2 End-to-end = coverage of the IETF participant workflow
=E2=80=A2 = Extensibility and maintainability
=E2=80=A2 Operational = scalability, performance, and security profiles of tools
=E2= =80=A2 User experience design, testing, and analysis

It is not the role of the TAS team to implement, maintain, or = manage the operation of individual tools. Those responsibilities remain = with the IETF tools team. Once TAS team guidance documents become = available, the IETF Tools Project Manager (Robert Sparks) will establish = plans and workflows to align ongoing and future tools development with = the guidance.

The TAS team is expected to = consult widely with the IETF community, to draw on best practices from = the software development industry and open source communities, and to = evolve its guidance over time as practices change. The team's online = presence resides at:

Datatracker = page: https://datatracker.ietf.org/group/tools-arch/about/
Mailing list (open to members, with a public = archive): tools-arch@ietf.org
Github = organization: https://github.com/ietf-team-tools-arch

The TAS team members and team leaders are appointed by the = General Area Director. The composition of the team is meant to reflect = understanding of the IETF tools suite and its history as well as cloud = software development processes and deployments. Team leadership changes = are expected approximately every two years. Team membership will be = assessed and potentially refreshed annually. The initial team members = are:

Jari Arkko
Silvia = Botros
Jay Daley (LLC liaison)
Tony = Hansen
Tero Kivinen
John Levine
Mark Nottingham
Rich Salz (co-lead)
Jim Schaad
David Schinazi
Robert = Sparks (tools team liaison)
Martin Thomson (co-lead)

If you have questions about the team, feel = free to send them to me or the co-leads, Rich Salz <rsalz@akamai.com> and = Martin Thomson <mt@lowentropy.net>.

Best,
Alissa Cooper
IETF = Chair


= --Apple-Mail=_05E178BD-9322-4A08-BB24-B62AE5B28593-- From nobody Tue Feb 4 13:01:08 2020 Return-Path: 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 79FF012012E for ; Tue, 4 Feb 2020 13:01:07 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.897 X-Spam-Level: X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no 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 2H42IKUs5gEs for ; Tue, 4 Feb 2020 13:01:05 -0800 (PST) Received: from mail.smeinc.net (mail.smeinc.net [209.135.209.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8D268120170 for ; Tue, 4 Feb 2020 13:01:05 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id DCBA4300B0D for ; Tue, 4 Feb 2020 15:34:23 -0500 (EST) X-Virus-Scanned: amavisd-new at mail.smeinc.net Received: from mail.smeinc.net ([127.0.0.1]) by localhost (mail.smeinc.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id 3TBvMRHfmGxo for ; Tue, 4 Feb 2020 15:34:22 -0500 (EST) Received: from a860b60074bd.fios-router.home (pool-108-51-198-163.washdc.fios.verizon.net [108.51.198.163]) by mail.smeinc.net (Postfix) with ESMTPSA id 8FA16300512 for ; Tue, 4 Feb 2020 15:34:22 -0500 (EST) From: Russ Housley Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\)) Message-Id: <9FC93267-3A7A-4727-B115-6E823B688221@vigilsec.com> Date: Tue, 4 Feb 2020 16:01:03 -0500 To: IETF Tools Development X-Mailer: Apple Mail (2.3445.104.11) Archived-At: Subject: [TOOLS-DEVELOPMENT] Tools Call Agenda -- 11 February 2020 at 1:00 Eastern X-BeenThere: tools-development@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Tools Development list server List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Feb 2020 21:01:07 -0000 Tools Call Agenda -- 11 February 2020 at 1:00 Eastern JOIN WEBEX MEETING https://ietf.webex.com/ietf/j.php?MTID=m440dd848726339c03e605b9956e38bac Meeting number (access code): 640 103 570 Meeting password: tools JOIN BY PHONE 1-877-668-4493 Call-in toll free number (US/Canada) 1-650-479-3208 Call-in toll number (US/Canada) Meeting number (access code): 640 103 570 Meeting password: tools 1. Datatracker Projects - Expected Datatracker Releases -- Robert and Henrik -- https://trac.tools.ietf.org/tools/ietfdb/browser/trunk/PLAN - Meeting application improvements by IOLA -- Robert - Automated schedule builder by DashCare -- Robert - Minor Tools Enhancements by Painless Security -- Robert 2. Community & Other Projects - WWW search to provide additional pointers -- Greg - Host third-party subresources on mailarchive -- Ryan 3. RFC Services Projects - Are tools issues blocking any documents? -- John and Henrik - Security Review of RPC Tools -- Robert and Jay 4. Server Infrastructure - Deployment of Python3 -- Robert - Expected Website Releases -- Robert - DMARC support for email aliases -- Henrik and Alexey 5. YANG Catalog - Tasks in Priority order: -- Posting YANG modules by other SDOs -- Eric and Robert -- Putting yangcatalog.org in a Docker container -- Robert -- Upgrade the operating system on the server -- Robert 6. Parking Lot - Search over www, datatracker, and mailarchive - Transition Datatracker to Django2 and then Django3 - Transition Mailarchive to Django2 and then Django3 - Transition Wagtail for IETF website to Django2 and then Django3 7. AOB From nobody Tue Feb 4 16:42:26 2020 Return-Path: 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 7BAF1120127 for ; Tue, 4 Feb 2020 16:42:24 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham autolearn_force=no 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 oT7B_P9idNft for ; Tue, 4 Feb 2020 16:42:23 -0800 (PST) Received: from macbook-pro.localdomain (unknown [158.140.230.105]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPSA id DBFF2120072 for ; Tue, 4 Feb 2020 16:42:22 -0800 (PST) From: Jay Daley Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3608.40.2.2.4\)) Message-Id: <60B5A7B1-DE03-4A94-A301-58B52385B049@ietf.org> Date: Wed, 5 Feb 2020 13:42:20 +1300 To: IETF Tools Development X-Mailer: Apple Mail (2.3608.40.2.2.4) Archived-At: Subject: [TOOLS-DEVELOPMENT] RFP for Security Review and Remediation of the RFC Production Center Web Accessible Code - issued X-BeenThere: tools-development@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Tools Development list server List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Feb 2020 00:42:25 -0000 In case you missed the announcement, this RFP has been reissued. It has = changed a bit since the original as the documented RFP process has been = tidied up and the language made clearer. The RFP is = https://ietf.org/media/documents/IETF_RPC_Tools_Security_Review_RFP_05Feb2= 0.pdf Jay --=20 Jay Daley IETF Executive Director jay@ietf.org +64 21 678840 From nobody Wed Feb 5 09:37:52 2020 Return-Path: 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 017801200B2 for ; Wed, 5 Feb 2020 09:37:51 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -14.499 X-Spam-Level: X-Spam-Status: No, score=-14.499 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com header.b=K/U7rw78; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=HAo7ICMl 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 8rrxBpfZoxaJ for ; Wed, 5 Feb 2020 09:37:48 -0800 (PST) Received: from rcdn-iport-7.cisco.com (rcdn-iport-7.cisco.com [173.37.86.78]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5888D120077 for ; Wed, 5 Feb 2020 09:37:48 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3216; q=dns/txt; s=iport; t=1580924268; x=1582133868; h=from:to:subject:date:message-id:references:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=CKlsfDVnLTTU0nTbpfiRaPvKTPK2JP07kjH9lMnX4CI=; b=K/U7rw78DCMSJG+v+p7xj27by6COLWo0JTCMNmPe9GAKNReHaDcE42HX GYzrFVl6F/vt+yGUags9NE2KcT74La/6oxwzVy2CtAwPzhuRngZ/aPHRJ Qdaf6M3+h0G9wRJWf7gqHVhFyiJ55W83CKHLA+31d7UXq0PFavJwVMhWQ E=; IronPort-PHdr: =?us-ascii?q?9a23=3An73lYBTt3hyaiaqWFL2H5NJLgNpsv++ubAcI9p?= =?us-ascii?q?oqja5Pea2//pPkeVbS/uhpkESXBdfA8/wRje3QvuigQmEG7Zub+FE6OJ1XH1?= =?us-ascii?q?5g640NmhA4RsuMCEn1NvnvOiEkDcJJV1JN9HCgOk8TE8H7NBXf?= X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AiAQAV/Tpe/4sNJK1LFwMcAQEBAQE?= =?us-ascii?q?HAQERAQQEAQGBaQUBAQsBgVNQBWxYIAQLKgqEC4NGA4p7TpojgS4UgRADVAk?= =?us-ascii?q?BAQEMAQEYDQgCAQGEQAIXgiMkNgcOAgMNAQEEAQEBAgEFBG2FNwyFZwIBAwE?= =?us-ascii?q?BEBERDAEBJAgMDQICAQgaAhAEDAYCAgIZDAsVDwECAQMBEhQOgwQBgkoDLgE?= =?us-ascii?q?DCzyhNAKBOYhidYEygn8BAQVFgX+CXBiCDAkFgQkqAYV/hiIagUE/gREnIII?= =?us-ascii?q?eLj6BBIFgAQECGoEPBQESAQkHERcKJgiCFisyghEbjWgqggVAnxMKgjqHSoV?= =?us-ascii?q?GgiaHDRuCSHiHF5AyhESKHohqkjUCBAIEBQIOAQEFgVgBMmdxcBU7KgGCQQl?= =?us-ascii?q?HGA2OHQwMC4EwgiCFFIU/dAKBJ4p0FYENAYEPAQE?= X-IronPort-AV: E=Sophos;i="5.70,406,1574121600"; d="scan'208";a="710082338" Received: from alln-core-6.cisco.com ([173.36.13.139]) by rcdn-iport-7.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 05 Feb 2020 17:37:46 +0000 Received: from XCH-RCD-009.cisco.com (xch-rcd-009.cisco.com [173.37.102.19]) by alln-core-6.cisco.com (8.15.2/8.15.2) with ESMTPS id 015HbkSX023356 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 5 Feb 2020 17:37:46 GMT Received: from xhs-rtp-003.cisco.com (64.101.210.230) by XCH-RCD-009.cisco.com (173.37.102.19) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Wed, 5 Feb 2020 11:37:45 -0600 Received: from xhs-rcd-003.cisco.com (173.37.227.248) by xhs-rtp-003.cisco.com (64.101.210.230) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Wed, 5 Feb 2020 12:37:44 -0500 Received: from NAM11-CO1-obe.outbound.protection.outlook.com (72.163.14.9) by xhs-rcd-003.cisco.com (173.37.227.248) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Wed, 5 Feb 2020 11:37:44 -0600 ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=IHk8X7eEKWgip896mk+dQU4yE62ZeOP/9HYrx6IhqJsMhS5Hjt0uhcpJ40ojT/yMvoZn7rcg/U4kVmrHq+IwZ/bXusAkBg+EeHyqV9h2w8rcjv7nLYJoh+E++HJZ5TUu73ej/+WoJQ29sbY1IlqhHbQy5SWw3vaJl/KY3HTpL9gG1CglfoTUnA1x1xY9pFd/wXQqP5DBz6D0bylxT6nsGX8wfEN7EanQvzf3kW+qVbjbEXgeiw4hvDOwFHURIBLSTc2OoNM6RRCV6p97de4eXbYN3tVxbjw7EWnBf1tyy5QXQUn/OHHhVaWvV3JKCFvaHfHHYIM3bA9hnM/9BJv3OQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=CKlsfDVnLTTU0nTbpfiRaPvKTPK2JP07kjH9lMnX4CI=; b=WY5V0M09hondGn2/Bn0Lv2S4ksOiF+ocK2TzPaYb5cAF2iSW/6FgwCx8NOeLPsXy1SZQhuKBqRL6BHo1YhF3g2q/YKi5TKxnCeerlzDQjM+a4QjpvfL3GcVHfFd7HcSSDyj0EJwsVG6yJG323mc5iZI8Y5Or07RLjCnuABE+TGhuMeEt5bynIKBFd3rZqmT81uTLLCc/hAZCuxa8F0GZZCpG10ceSYFIzwOGwH7t7abb1sT8wO79SSM7kYXfnMLK553zNKOVMrr887fAOJvVAhwXTyB1HN8++6Rwc9tsvaaWn6LZBK4G2sQDk6uUCy9IXhT8N8FUb3U6sXlTR81WZQ== ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=cisco.com; dmarc=pass action=none header.from=cisco.com; dkim=pass header.d=cisco.com; arc=none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector2-cisco-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=CKlsfDVnLTTU0nTbpfiRaPvKTPK2JP07kjH9lMnX4CI=; b=HAo7ICMlnZ+fEYYb5XXoIFtU1lpj1g/2VfOqc1HQyknmlWKDHUEZR6v5Xm89PQImiDNYVesFmzRi7nNFrMGdR82/ivfb6DRAQO2ROPlqfrlCYKcDzIRnkc5q3sXYmBbOlcHTgCXcxtOQZrcK/oJx1tJE/yCQ34ZpFXu1JxT6SQU= Received: from DM5PR11MB1753.namprd11.prod.outlook.com (10.175.88.141) by DM5PR11MB1963.namprd11.prod.outlook.com (10.175.89.8) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2686.27; Wed, 5 Feb 2020 17:37:42 +0000 Received: from DM5PR11MB1753.namprd11.prod.outlook.com ([fe80::680d:e22e:72d5:67ca]) by DM5PR11MB1753.namprd11.prod.outlook.com ([fe80::680d:e22e:72d5:67ca%3]) with mapi id 15.20.2707.020; Wed, 5 Feb 2020 17:37:42 +0000 From: "Eric Vyncke (evyncke)" To: Russ Housley , IETF Tools Development Thread-Topic: [TOOLS-DEVELOPMENT] Tools Call Agenda -- 11 February 2020 at 1:00 Eastern Thread-Index: AQHV255Sb2xmj5SURUCBpDXZglCcEagM71aA Date: Wed, 5 Feb 2020 17:37:42 +0000 Message-ID: References: <9FC93267-3A7A-4727-B115-6E823B688221@vigilsec.com> In-Reply-To: <9FC93267-3A7A-4727-B115-6E823B688221@vigilsec.com> Accept-Language: fr-BE, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/10.21.0.200113 authentication-results: spf=none (sender IP is ) smtp.mailfrom=evyncke@cisco.com; x-originating-ip: [92.184.105.239] x-ms-publictraffictype: Email x-ms-office365-filtering-correlation-id: d7990b05-f0a6-496e-6fce-08d7aa621ab8 x-ms-traffictypediagnostic: DM5PR11MB1963: x-microsoft-antispam-prvs: x-ms-oob-tlc-oobclassifiers: OLM:8882; x-forefront-prvs: 0304E36CA3 x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(376002)(136003)(366004)(396003)(346002)(39860400002)(199004)(189003)(81156014)(33656002)(36756003)(8936002)(86362001)(2906002)(5660300002)(64756008)(66556008)(66946007)(66476007)(91956017)(76116006)(66574012)(26005)(66446008)(8676002)(71200400001)(16799955002)(316002)(6512007)(186003)(81166006)(6486002)(2616005)(110136005)(6506007)(966005)(478600001); DIR:OUT; SFP:1101; SCL:1; SRVR:DM5PR11MB1963; H:DM5PR11MB1753.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1; received-spf: None (protection.outlook.com: cisco.com does not designate permitted sender hosts) x-ms-exchange-senderadcheck: 1 x-microsoft-antispam: BCL:0; x-microsoft-antispam-message-info: LE+c7rLwTrFGVFJ95nxludCo9RuRbx8Jh6dP3kTxubwQMkXQTG/w+C7WRvNT5fwO9q6sPbjVizpr7qz56tFTAgc1vFTj5tYyAdDzaKuBjoyMPyjPtE986lvzcS1uqA1C8tn3hJBQSefjB0ZUF0T82sbv11mm100huU4Nnlbp+t3jbPCS8w2gCrdIh/SaAJYAxLQN+6TshMH6trd3+ps1K7DPe2tlH9iHSggOZxmDaMlVPZKLM+kftG1PuucIta39sIdciEYHyYxgVhVv5aZzW2v+gHt+PcBSUEQJUHTn6YENebERiXl0+me9j7XuB5+/1xK1YqJW8rcXDTfBP1ZuXJkwo7mdq2rl7xql43Pbab1n37QefovtSezCYlEAYp6x1iEK3uNFidGGQAXW0S1/2rXP6oFQTliZU+c686IqF7vYmR9uJSKU9RfgV1Eg7naNUIZhiC22/npbJQEomXX5go+1H25xi5SmC0OGoUjRjbXrZfY9PrPG/opyhih9JavGcreCOx+VBHYfxYQuRmcIZw== x-ms-exchange-antispam-messagedata: AIVZzZKeR4npK02jC01r42VlyVuUxzsKI7IPVs4jccG9kxbQrFAoxGVnsMZOr0djyUrYMZEhSqLnIX+3ow4pz19dskaO5QwNDJZTE9PonROETKx2RuE7issUawUTmsXSgepzNPV4/AmVIYKbbafJYA== x-ms-exchange-transport-forked: True Content-Type: text/plain; charset="utf-8" Content-ID: <004099AD21DF8947A8C95BD3887C2CA2@namprd11.prod.outlook.com> Content-Transfer-Encoding: base64 MIME-Version: 1.0 X-MS-Exchange-CrossTenant-Network-Message-Id: d7990b05-f0a6-496e-6fce-08d7aa621ab8 X-MS-Exchange-CrossTenant-originalarrivaltime: 05 Feb 2020 17:37:42.7056 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e X-MS-Exchange-CrossTenant-mailboxtype: HOSTED X-MS-Exchange-CrossTenant-userprincipalname: DQdUvPsNbe9MxxMuPQeMh7xu7H9WT+BDlXjd0RB2WrfJnPfp2q2yaXHrMgVJxHoMy2s9SwimdASTXVaRuyXWRw== X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM5PR11MB1963 X-OriginatorOrg: cisco.com X-Outbound-SMTP-Client: 173.37.102.19, xch-rcd-009.cisco.com X-Outbound-Node: alln-core-6.cisco.com Archived-At: Subject: Re: [TOOLS-DEVELOPMENT] Tools Call Agenda -- 11 February 2020 at 1:00 Eastern X-BeenThere: tools-development@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Tools Development list server List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Feb 2020 17:37:51 -0000 RGVhciBhbGwsDQoNCkkgd2lsbCBiZSBhYnJvYWQgb24gdmFjYXRpb25zLCBzbywgcGxlYXNlIGFj Y2VwdCBteSBhcG9sb2dpZXMgZm9yIG5vdCBqb2luaW5nDQoNCi3DqXJpYw0KDQrvu79PbiAwNC8w Mi8yMDIwLCAyMjowMSwgIlRPT0xTLURFVkVMT1BNRU5UIG9uIGJlaGFsZiBvZiBSdXNzIEhvdXNs ZXkiIDx0b29scy1kZXZlbG9wbWVudC1ib3VuY2VzQGlldGYub3JnIG9uIGJlaGFsZiBvZiBob3Vz bGV5QHZpZ2lsc2VjLmNvbT4gd3JvdGU6DQoNCiAgICBUb29scyBDYWxsIEFnZW5kYSAtLSAxMSBG ZWJydWFyeSAyMDIwIGF0IDE6MDAgRWFzdGVybg0KICAgIA0KICAgIA0KICAgIEpPSU4gV0VCRVgg TUVFVElORw0KICAgIGh0dHBzOi8vaWV0Zi53ZWJleC5jb20vaWV0Zi9qLnBocD9NVElEPW00NDBk ZDg0ODcyNjMzOWMwM2U2MDViOTk1NmUzOGJhYw0KICAgIE1lZXRpbmcgbnVtYmVyIChhY2Nlc3Mg Y29kZSk6IDY0MCAxMDMgNTcwDQogICAgTWVldGluZyBwYXNzd29yZDogdG9vbHMNCiAgICANCiAg ICBKT0lOIEJZIFBIT05FDQogICAgMS04NzctNjY4LTQ0OTMgQ2FsbC1pbiB0b2xsIGZyZWUgbnVt YmVyIChVUy9DYW5hZGEpIA0KICAgIDEtNjUwLTQ3OS0zMjA4IENhbGwtaW4gdG9sbCBudW1iZXIg KFVTL0NhbmFkYSkNCiAgICBNZWV0aW5nIG51bWJlciAoYWNjZXNzIGNvZGUpOiA2NDAgMTAzIDU3 MA0KICAgIE1lZXRpbmcgcGFzc3dvcmQ6IHRvb2xzDQogICAgDQogICAgDQogICAgMS4gRGF0YXRy YWNrZXIgUHJvamVjdHMNCiAgICAgICAtIEV4cGVjdGVkIERhdGF0cmFja2VyIFJlbGVhc2VzIC0t IFJvYmVydCBhbmQgSGVucmlrDQogICAgICAgICAtLSBodHRwczovL3RyYWMudG9vbHMuaWV0Zi5v cmcvdG9vbHMvaWV0ZmRiL2Jyb3dzZXIvdHJ1bmsvUExBTg0KICAgICAgIC0gTWVldGluZyBhcHBs aWNhdGlvbiBpbXByb3ZlbWVudHMgYnkgSU9MQSAtLSBSb2JlcnQNCiAgICAgICAtIEF1dG9tYXRl ZCBzY2hlZHVsZSBidWlsZGVyIGJ5IERhc2hDYXJlIC0tIFJvYmVydA0KICAgICAgIC0gTWlub3Ig VG9vbHMgRW5oYW5jZW1lbnRzIGJ5IFBhaW5sZXNzIFNlY3VyaXR5IC0tIFJvYmVydA0KICAgIA0K ICAgIDIuIENvbW11bml0eSAmIE90aGVyIFByb2plY3RzDQogICAgICAgLSBXV1cgc2VhcmNoIHRv IHByb3ZpZGUgYWRkaXRpb25hbCBwb2ludGVycyAtLSBHcmVnDQogICAgICAgLSBIb3N0IHRoaXJk LXBhcnR5IHN1YnJlc291cmNlcyBvbiBtYWlsYXJjaGl2ZSAtLSBSeWFuDQogICAgDQogICAgMy4g UkZDIFNlcnZpY2VzIFByb2plY3RzDQogICAgICAgLSBBcmUgdG9vbHMgaXNzdWVzIGJsb2NraW5n IGFueSBkb2N1bWVudHM/IC0tIEpvaG4gYW5kIEhlbnJpaw0KICAgICAgIC0gU2VjdXJpdHkgUmV2 aWV3IG9mIFJQQyBUb29scyAtLSBSb2JlcnQgYW5kIEpheQ0KICAgIA0KICAgIDQuIFNlcnZlciBJ bmZyYXN0cnVjdHVyZQ0KICAgICAgIC0gRGVwbG95bWVudCBvZiBQeXRob24zIC0tIFJvYmVydA0K ICAgICAgIC0gRXhwZWN0ZWQgV2Vic2l0ZSBSZWxlYXNlcyAtLSBSb2JlcnQNCiAgICAgICAtIERN QVJDIHN1cHBvcnQgZm9yIGVtYWlsIGFsaWFzZXMgLS0gSGVucmlrIGFuZCBBbGV4ZXkNCiAgICAN CiAgICA1LiBZQU5HIENhdGFsb2cNCiAgICAgICAtIFRhc2tzIGluIFByaW9yaXR5IG9yZGVyOg0K ICAgICAgICAgLS0gUG9zdGluZyBZQU5HIG1vZHVsZXMgYnkgb3RoZXIgU0RPcyAtLSBFcmljIGFu ZCBSb2JlcnQNCiAgICAgICAgIC0tIFB1dHRpbmcgeWFuZ2NhdGFsb2cub3JnIGluIGEgRG9ja2Vy IGNvbnRhaW5lciAtLSBSb2JlcnQNCiAgICAgICAgIC0tIFVwZ3JhZGUgdGhlIG9wZXJhdGluZyBz eXN0ZW0gb24gdGhlIHNlcnZlciAtLSBSb2JlcnQNCiAgICANCiAgICA2LiBQYXJraW5nIExvdA0K ICAgICAgIC0gU2VhcmNoIG92ZXIgd3d3LCBkYXRhdHJhY2tlciwgYW5kIG1haWxhcmNoaXZlDQog ICAgICAgLSBUcmFuc2l0aW9uIERhdGF0cmFja2VyIHRvIERqYW5nbzIgYW5kIHRoZW4gRGphbmdv Mw0KICAgICAgIC0gVHJhbnNpdGlvbiBNYWlsYXJjaGl2ZSB0byBEamFuZ28yIGFuZCB0aGVuIERq YW5nbzMNCiAgICAgICAtIFRyYW5zaXRpb24gV2FndGFpbCBmb3IgSUVURiB3ZWJzaXRlIHRvIERq YW5nbzIgYW5kIHRoZW4gRGphbmdvMw0KICAgIA0KICAgIDcuIEFPQg0KICAgIA0KICAgIF9fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQogICAgVE9PTFMtREVW RUxPUE1FTlQgbWFpbGluZyBsaXN0DQogICAgVE9PTFMtREVWRUxPUE1FTlRAaWV0Zi5vcmcNCiAg ICBodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3Rvb2xzLWRldmVsb3BtZW50 DQogICAgDQoNCg== From nobody Mon Feb 10 08:10:23 2020 Return-Path: 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 7C388120232 for ; Mon, 10 Feb 2020 07:35:43 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.979 X-Spam-Level: X-Spam-Status: No, score=-1.979 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nostrum.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 fzT7phH3ceHY for ; Mon, 10 Feb 2020 07:35:41 -0800 (PST) Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AF96E120255 for ; Mon, 10 Feb 2020 07:35:41 -0800 (PST) Received: from unescapeable.local ([47.186.30.41]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id 01AFZelj012593 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for ; Mon, 10 Feb 2020 09:35:40 -0600 (CST) (envelope-from rjsparks@nostrum.com) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1581348941; bh=Sc+3m8V2WAycAkHYF05XbOkONNJDCa+CgepAVfTcHpc=; h=Subject:To:References:From:Date:In-Reply-To; b=Bm8Ojr7y2q1EwhJ/y195qhJWbIoPLwMx8Juh6UaHFHgcJ+pN9zB2WvDw2ni2WRugp 1QAwi7amUlhvNWE7CpfapEOV43HXY6V2JpFPkYv7B6U5p3F7qLYY7Ad552jmJ8O12s PKwRjYG6X99upwx/bRh2vgu1G8hG5XAos9DRhS68= X-Authentication-Warning: raven.nostrum.com: Host [47.186.30.41] claimed to be unescapeable.local To: tools-development@ietf.org References: <9FC93267-3A7A-4727-B115-6E823B688221@vigilsec.com> From: Robert Sparks Message-ID: <3af13579-de59-4e2a-85c4-279bea760ad8@nostrum.com> Date: Mon, 10 Feb 2020 09:35:39 -0600 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:68.0) Gecko/20100101 Thunderbird/68.4.2 MIME-Version: 1.0 In-Reply-To: <9FC93267-3A7A-4727-B115-6E823B688221@vigilsec.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US Archived-At: Subject: Re: [TOOLS-DEVELOPMENT] Tools Call Agenda -- 11 February 2020 at 1:00 Eastern X-BeenThere: tools-development@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Tools Development list server List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Feb 2020 15:35:44 -0000 Agenda bash: We should talk about the migration to the new server in section 4. Notes inline for tomorrow's call: On 2/4/20 3:01 PM, Russ Housley wrote: > Tools Call Agenda -- 11 February 2020 at 1:00 Eastern > > > JOIN WEBEX MEETING > https://ietf.webex.com/ietf/j.php?MTID=m440dd848726339c03e605b9956e38bac > Meeting number (access code): 640 103 570 > Meeting password: tools > > JOIN BY PHONE > 1-877-668-4493 Call-in toll free number (US/Canada) > 1-650-479-3208 Call-in toll number (US/Canada) > Meeting number (access code): 640 103 570 > Meeting password: tools > > > 1. Datatracker Projects > - Expected Datatracker Releases -- Robert and Henrik > -- https://trac.tools.ietf.org/tools/ietfdb/browser/trunk/PLAN The PLAN was updated to raise the priority order of  capturing when the datatracker sends email (to facilitate re-sending messages when needed) and transitioning to Django 2. > - Meeting application improvements by IOLA -- Robert On track as of mid-Jan. I'm awaiting a more recent update from IOLA. > - Automated schedule builder by DashCare -- Robert Part one is expected to be complete by the end of Feb. > - Minor Tools Enhancements by Painless Security -- Robert This team has completed 2 of the 3 planned initial datatracker enhancements. The plan is to familiarize them with working on as many of the tools as possible. The next tool I will ask them to do minor enhancements to is the main website. > > 2. Community & Other Projects > - WWW search to provide additional pointers -- Greg > - Host third-party subresources on mailarchive -- Ryan > > 3. RFC Services Projects > - Are tools issues blocking any documents? -- John and Henrik > - Security Review of RPC Tools -- Robert and Jay This RFP has been issued - see . Bids are due 4Mar. > > 4. Server Infrastructure > - Deployment of Python3 -- Robert > - Expected Website Releases -- Robert I plan to do either a minor release or a patch to fix an issue with previewing pages in the authoring admin early this week. I should have a major revision ready for review on wwwstaging in a few days. This revision removes the broken datatracker integration attempt, and simplifies many of the models in preparation for moving the website to a current revision of wagtail. > - DMARC support for email aliases -- Henrik and Alexey > > 5. YANG Catalog > - Tasks in Priority order: > -- Posting YANG modules by other SDOs -- Eric and Robert > -- Putting yangcatalog.org in a Docker container -- Robert > -- Upgrade the operating system on the server -- Robert > > 6. Parking Lot > - Search over www, datatracker, and mailarchive > - Transition Datatracker to Django2 and then Django3 > - Transition Mailarchive to Django2 and then Django3 > - Transition Wagtail for IETF website to Django2 and then Django3 > > 7. AOB > > _______________________________________________ > TOOLS-DEVELOPMENT mailing list > TOOLS-DEVELOPMENT@ietf.org > https://www.ietf.org/mailman/listinfo/tools-development From nobody Mon Feb 10 11:08:37 2020 Return-Path: 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 CFA3912081E for ; Mon, 10 Feb 2020 11:08:35 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.998 X-Spam-Level: X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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=gmail.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 JECIF4LLm-qo for ; Mon, 10 Feb 2020 11:08:33 -0800 (PST) Received: from mail-wm1-x333.google.com (mail-wm1-x333.google.com [IPv6:2a00:1450:4864:20::333]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D7632120820 for ; Mon, 10 Feb 2020 11:08:32 -0800 (PST) Received: by mail-wm1-x333.google.com with SMTP id g1so426236wmh.4 for ; Mon, 10 Feb 2020 11:08:32 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=g6lcXL+D/MlVeDalvpPKbu9LaDVjA/i0ia8tk1bF0b0=; b=qfAeJw+TdFyzJd68M0maysLguSTQkwgKpFCNauhqBUywOWp5TxJzaPv54U+puLecPu FEVn266403fU8DkuStgw0MRj/ppMgsvtCa71eJe/XN8CVxEYs8iY0PRHAiHDYN/m11gQ jKDaZx5hKvTlFYxnXqAj4F5vvcBalXT5ryFvJqIWS9BzNQXorgh+o+XMCmjhDyvl9yvU W7Jx0iOOH1uESigNBP3dSvQqZhknWJCaNYbjukyWpjWtYcTaAYarfHb84AawSXtCYTY3 IxBuhuQg35ClYEYvIB+xSeQRqFyaIsuIp7xhHLxmQjgq538s18da9fp0DH9hc7Ywi+d7 eELw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=g6lcXL+D/MlVeDalvpPKbu9LaDVjA/i0ia8tk1bF0b0=; b=hkpM51PRI6YtwN0YYPfzcsDn0JGo2PcZJO+Zb9g0xntt9xEpy9EzWAGMYrvxDv5uBm Wy7E9wBRzwTORzVZNF0Hxw/zy9df9K27qf/40Y2Ii8gEym1+3wKG0sUoDfIyEEt0bKPx MfBfNJwmht/amfK9c0wq3TdRJj7m0+4DTybXi7fZbhl9QbsLYu9TwY6+MIjtPvazymf8 Db/zAzp5qWvUJsYSuC0y9wJ2CxeZcQ4Q4iPtVnLEs91A+MiMXraZjHmFS3YuSaVqDLic RaGd/evYaO44zwI6qLgkrWqY5DoD8EBHcT5/zftMC5oyQFpNmJ7nUAQ/0vO330GEwCRz GqeA== X-Gm-Message-State: APjAAAWlpqhGzqNQ3R9flArXA8QB3mQ/dXsC+t99gywi6hUdZm9e0z6C 2aGpI4YBuM8Zrz5Qm8kC1+s= X-Google-Smtp-Source: APXvYqyV57ln/VaWOKdg+u+aAqo+C70bPgVjXV2+whLKXqvTuVwD9zVTaPWm52lM+/PhyZfQnPh/uA== X-Received: by 2002:a7b:c0c7:: with SMTP id s7mr434047wmh.129.1581361711276; Mon, 10 Feb 2020 11:08:31 -0800 (PST) Received: from ?IPv6:2601:647:5a00:ef0b:f04e:1c5b:d367:7db0? ([2601:647:5a00:ef0b:f04e:1c5b:d367:7db0]) by smtp.gmail.com with ESMTPSA id u4sm1803575wrt.37.2020.02.10.11.08.29 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 10 Feb 2020 11:08:30 -0800 (PST) From: Bob Hinden Message-Id: <10D7A3E8-E3BC-4F73-AD63-AACC96B85797@gmail.com> Content-Type: multipart/signed; boundary="Apple-Mail=_F5385D67-47A8-4E24-8B74-2EF14F35C5C3"; protocol="application/pgp-signature"; micalg=pgp-sha512 Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\)) Date: Mon, 10 Feb 2020 11:08:26 -0800 In-Reply-To: <3af13579-de59-4e2a-85c4-279bea760ad8@nostrum.com> Cc: Bob Hinden , IETF Tools Development To: Robert Sparks References: <9FC93267-3A7A-4727-B115-6E823B688221@vigilsec.com> <3af13579-de59-4e2a-85c4-279bea760ad8@nostrum.com> X-Mailer: Apple Mail (2.3445.104.11) Archived-At: Subject: Re: [TOOLS-DEVELOPMENT] Tools Call Agenda -- 11 February 2020 at 1:00 Eastern X-BeenThere: tools-development@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Tools Development list server List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Feb 2020 19:08:36 -0000 --Apple-Mail=_F5385D67-47A8-4E24-8B74-2EF14F35C5C3 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 Regrets, I can=E2=80=99t make the call. Bob > On Feb 10, 2020, at 7:35 AM, Robert Sparks = wrote: >=20 > Agenda bash: >=20 > We should talk about the migration to the new server in section 4. >=20 > Notes inline for tomorrow's call: >=20 > On 2/4/20 3:01 PM, Russ Housley wrote: >> Tools Call Agenda -- 11 February 2020 at 1:00 Eastern >>=20 >>=20 >> JOIN WEBEX MEETING >> = https://ietf.webex.com/ietf/j.php?MTID=3Dm440dd848726339c03e605b9956e38bac= >> Meeting number (access code): 640 103 570 >> Meeting password: tools >>=20 >> JOIN BY PHONE >> 1-877-668-4493 Call-in toll free number (US/Canada) >> 1-650-479-3208 Call-in toll number (US/Canada) >> Meeting number (access code): 640 103 570 >> Meeting password: tools >>=20 >>=20 >> 1. Datatracker Projects >> - Expected Datatracker Releases -- Robert and Henrik >> -- https://trac.tools.ietf.org/tools/ietfdb/browser/trunk/PLAN > The PLAN was updated to raise the priority order of capturing when = the datatracker sends email (to facilitate re-sending messages when = needed) and transitioning to Django 2. >> - Meeting application improvements by IOLA -- Robert > On track as of mid-Jan. I'm awaiting a more recent update from IOLA. >> - Automated schedule builder by DashCare -- Robert > Part one is expected to be complete by the end of Feb. >> - Minor Tools Enhancements by Painless Security -- Robert > This team has completed 2 of the 3 planned initial datatracker = enhancements. The plan is to familiarize them with working on as many of = the tools as possible. The next tool I will ask them to do minor = enhancements to is the main website. >>=20 >> 2. Community & Other Projects >> - WWW search to provide additional pointers -- Greg >> - Host third-party subresources on mailarchive -- Ryan >>=20 >> 3. RFC Services Projects >> - Are tools issues blocking any documents? -- John and Henrik >> - Security Review of RPC Tools -- Robert and Jay > This RFP has been issued - see = . Bids are due 4Mar. >>=20 >> 4. Server Infrastructure >> - Deployment of Python3 -- Robert >> - Expected Website Releases -- Robert >=20 > I plan to do either a minor release or a patch to fix an issue with = previewing pages in the authoring admin early this week. >=20 > I should have a major revision ready for review on wwwstaging in a few = days. This revision removes the broken datatracker integration attempt, = and simplifies many of the models in preparation for moving the website = to a current revision of wagtail. >=20 >> - DMARC support for email aliases -- Henrik and Alexey >>=20 >> 5. YANG Catalog >> - Tasks in Priority order: >> -- Posting YANG modules by other SDOs -- Eric and Robert >> -- Putting yangcatalog.org in a Docker container -- Robert >> -- Upgrade the operating system on the server -- Robert >>=20 >> 6. Parking Lot >> - Search over www, datatracker, and mailarchive >> - Transition Datatracker to Django2 and then Django3 >> - Transition Mailarchive to Django2 and then Django3 >> - Transition Wagtail for IETF website to Django2 and then Django3 >>=20 >> 7. AOB >>=20 >> _______________________________________________ >> TOOLS-DEVELOPMENT mailing list >> TOOLS-DEVELOPMENT@ietf.org >> https://www.ietf.org/mailman/listinfo/tools-development >=20 > _______________________________________________ > TOOLS-DEVELOPMENT mailing list > TOOLS-DEVELOPMENT@ietf.org > https://www.ietf.org/mailman/listinfo/tools-development --Apple-Mail=_F5385D67-47A8-4E24-8B74-2EF14F35C5C3 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP -----BEGIN PGP SIGNATURE----- iQEzBAEBCgAdFiEEm0rfRsOCoyamPexGrut0EXfnu6gFAl5BqioACgkQrut0EXfn u6hXpwgAupRsPAvOiaSnXHJFmBlGpWER82W15Q/uKQpdB0SxHS9FPzoi70dVAwRV DcnXKXJ+EdSyUl2KGEor47sFWoivDer40Xo32PhOCdp+B7TQ4mb88z786gd1R+2w mTJhb9VU4zewLy+5uEOL6F7YLDtUR/W9VIyOlkv7/dsiLC8dNq59nlsOp3pLY2AM 2rQJq/2riv4yR2+3dhYMpOT/C2vh/iM8Y2ObNyg4oHr0onCyqPJ+WQ8GrqZT1zoW VFQZlHj5XML1Qe7LUrGGsWQI+6WwK3DG+24bdpMOCh+Gr0kasPGPm7Tp/fYJf3dp 8QSAuTxS0TalYbzPaPEMKPOSz8LzZw== =gYGp -----END PGP SIGNATURE----- --Apple-Mail=_F5385D67-47A8-4E24-8B74-2EF14F35C5C3-- From nobody Mon Feb 10 19:04:14 2020 Return-Path: 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 7D645120089 for ; Mon, 10 Feb 2020 19:04:12 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -14.501 X-Spam-Level: X-Spam-Status: No, score=-14.501 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com header.b=FyL9tJnQ; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=HAcY85fN 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 9Isz2u9v2jql for ; Mon, 10 Feb 2020 19:04:10 -0800 (PST) Received: from alln-iport-7.cisco.com (alln-iport-7.cisco.com [173.37.142.94]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 410F7120058 for ; Mon, 10 Feb 2020 19:04:10 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5432; q=dns/txt; s=iport; t=1581390250; x=1582599850; h=from:to:subject:date:message-id:references:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=QUWPFqJluTTU5hhHkOSnYzE5CKDymt98kQwzgOXNaVU=; b=FyL9tJnQT1VH+rdHEAxTaMQtUgEGe5kqYfMZ6ISuOwKS1L2nq7RQn4LQ EKIrQrg6f/qiAZGn3hbsMEbTE/Wat2g7yFumGTjHqubQK4CWXpoI7w6+I 75NMS3jP8wOUzSyC4tve0NAs44LpSniBXJek8NYMRV8eD0kCdqoB4bkNx I=; IronPort-PHdr: =?us-ascii?q?9a23=3AVOMCpx8D0rc14f9uRHGN82YQeigqvan1NQcJ65?= =?us-ascii?q?0hzqhDabmn44+8ZB7E/fs4iljPUM2b8P9Ch+fM+4HYEW0bqdfk0jgZdYBUER?= =?us-ascii?q?oMiMEYhQslVcObGEvwL/PCZC0hF8MEX1hgrDm2?= X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0DMAQACGUJe/4sNJK1MFwMcAQEBAQE?= =?us-ascii?q?HAQERAQQEAQGBaAYBAQsBAYFSKScFbFggBAsqCoQLg0YDiwJOgWwlmBKBLhS?= =?us-ascii?q?BEANUCQEBAQwBARgNCAIBAYRAAheCLyQ1CA4CAw0BAQQBAQECAQUEbYU3DEI?= =?us-ascii?q?BAQEDBwSFFAEBAgIBARAREQwBASQIDA0CAgEIDgoCAhAEDAYCAgIZDAsVDwE?= =?us-ascii?q?CAQMBEhQOgwQBgkoDLgEBDTyeGgKBOYhidYEygn8BAQVFfkFAgj4YggwJBYE?= =?us-ascii?q?JKgGGAIYiGoFBP4ERJwwUgh4uPoEEgWABAQEBGoEUARIBCQcRFwomCIIWKzK?= =?us-ascii?q?CERuNbCcDggVAnxsKgjqHTIVIiTgbgkh5l06ERooegUuHIZI5AgQCBAUCDgE?= =?us-ascii?q?BBYFUATZncXAVOyoBgkEJRxgNjh0MDAuBBAEHJIIghRSFP3QCC4EcggWEQoR?= =?us-ascii?q?GFYENAYEPAQE?= X-IronPort-AV: E=Sophos;i="5.70,427,1574121600"; d="scan'208";a="425986390" Received: from alln-core-6.cisco.com ([173.36.13.139]) by alln-iport-7.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 11 Feb 2020 03:04:09 +0000 Received: from XCH-RCD-003.cisco.com (xch-rcd-003.cisco.com [173.37.102.13]) by alln-core-6.cisco.com (8.15.2/8.15.2) with ESMTPS id 01B348Gu004197 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 11 Feb 2020 03:04:08 GMT Received: from xhs-rcd-003.cisco.com (173.37.227.248) by XCH-RCD-003.cisco.com (173.37.102.13) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Mon, 10 Feb 2020 21:04:08 -0600 Received: from xhs-rcd-001.cisco.com (173.37.227.246) by xhs-rcd-003.cisco.com (173.37.227.248) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Mon, 10 Feb 2020 21:04:07 -0600 Received: from NAM11-DM6-obe.outbound.protection.outlook.com (72.163.14.9) by xhs-rcd-001.cisco.com (173.37.227.246) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Mon, 10 Feb 2020 21:04:07 -0600 ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=gNa2xINAsbsFDxZx0MqgaIpHK++mJm8AbZzHVmXvalYtrGhIGUIPNmcWs41yDYQLb9Bet0oDYA/m5uDtDHlycWr649viE6uHK1DdEXHXicwBVkuKHAOfaOUN3MD2qohlVr0IxHBBsCZ/txwyv2SJt7ZSLJRplsVCW4E4NgY8IJZX/qsp2pvN7zkqfdAUy1MzsTzPpWq9H/jt7itY5T8CB/8/VMS4pQqq/fpYDZAztvmrwuxCNWt4N8xtG6Ev5lVEBeiYTCz0/PJklHrn+zXRfj5f27xkvOOESd8PtLe2s/o0O38ETSQhoq6iasjt4N1ntS2b4z3mMKwK0QyUiYVBdA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=QUWPFqJluTTU5hhHkOSnYzE5CKDymt98kQwzgOXNaVU=; b=Z8D+f0ZHia3AQZyRrSM6FE/MLYYFWKmdPPs+kPP5WG0VQtSbNO6YimQUTg8kCpAi8xOLRGd/KAT16J74h8O/z6awnkNx+jguqfiEwycLm3sNP6wB9l3/zM50OEfhfgc8s789PORnURBKbHSCE9g3/6h4ZfcSGLraufsefyAvYOecxFl5FJDSsc9hFbJ5ftVpULlPXbLIxgqV0zJl/VYRfFoxXnSEN7c8Mc2hKBfLg+uTqbpK3Cl3jrikq4mwRs4kSD00mQjOojiKSTq9hIv614oEhcmMMXQrsZAcSdsGeQSHpN0oThv/zi3O5PpHNG7hgknmwVbURu6jhdSySp+3Dg== ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=cisco.com; dmarc=pass action=none header.from=cisco.com; dkim=pass header.d=cisco.com; arc=none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector2-cisco-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=QUWPFqJluTTU5hhHkOSnYzE5CKDymt98kQwzgOXNaVU=; b=HAcY85fN/18YxAD9QOO0iAWkaWbqCco5hV0SeXhczukMKjNqg5zOzOFM99bajFH0T6yk2660on0IH2UUCOaPzMFVlsvGChT2lnebTFxDDKCKbHJcouVqy3Dkk58E8yxuELM0SBUbEQ/iumsNZZnxemxo7lS3k+ol7QJlqvtKw6U= Received: from DM5PR11MB1753.namprd11.prod.outlook.com (10.175.88.141) by DM5PR11MB1371.namprd11.prod.outlook.com (10.168.101.145) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2707.21; Tue, 11 Feb 2020 03:04:06 +0000 Received: from DM5PR11MB1753.namprd11.prod.outlook.com ([fe80::680d:e22e:72d5:67ca]) by DM5PR11MB1753.namprd11.prod.outlook.com ([fe80::680d:e22e:72d5:67ca%3]) with mapi id 15.20.2707.030; Tue, 11 Feb 2020 03:04:06 +0000 From: "Eric Vyncke (evyncke)" To: Robert Sparks , "tools-development@ietf.org" Thread-Topic: [TOOLS-DEVELOPMENT] Tools Call Agenda -- 11 February 2020 at 1:00 Eastern Thread-Index: AQHV4Ce+b2xmj5SURUCBpDXZglCcEagVYE2A Date: Tue, 11 Feb 2020 03:04:06 +0000 Message-ID: <3055CFF0-D1C0-4831-BD7A-6CC51361973C@cisco.com> References: <9FC93267-3A7A-4727-B115-6E823B688221@vigilsec.com> <3af13579-de59-4e2a-85c4-279bea760ad8@nostrum.com> In-Reply-To: <3af13579-de59-4e2a-85c4-279bea760ad8@nostrum.com> Accept-Language: fr-BE, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/10.21.0.200113 authentication-results: spf=none (sender IP is ) smtp.mailfrom=evyncke@cisco.com; x-originating-ip: [190.166.236.188] x-ms-publictraffictype: Email x-ms-office365-filtering-correlation-id: 54292595-e53d-411e-aa75-08d7ae9f0ec1 x-ms-traffictypediagnostic: DM5PR11MB1371: x-microsoft-antispam-prvs: x-ms-oob-tlc-oobclassifiers: OLM:9508; x-forefront-prvs: 0310C78181 x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(136003)(346002)(396003)(376002)(366004)(39860400002)(189003)(199004)(53546011)(6506007)(110136005)(316002)(8676002)(6486002)(16799955002)(36756003)(81166006)(8936002)(81156014)(71200400001)(86362001)(66574012)(5660300002)(66946007)(66556008)(66476007)(33656002)(6512007)(478600001)(186003)(26005)(2616005)(966005)(91956017)(2906002)(64756008)(66446008)(76116006); DIR:OUT; SFP:1101; SCL:1; SRVR:DM5PR11MB1371; H:DM5PR11MB1753.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1; received-spf: None (protection.outlook.com: cisco.com does not designate permitted sender hosts) x-ms-exchange-senderadcheck: 1 x-microsoft-antispam: BCL:0; x-microsoft-antispam-message-info: h8MERb6Joo18EXJABen7R9wrU7aP3P8qm4s45i7f6fbiMQyHgVqEiAXz3jTDePHwW7ifB5repfiXFxSNfEDW09Vh5i1/5feL5C0GXYQ/AFyyzd5n1K/30ga2DqBxGFNU7Q1w0AWbEreeTEe1aWT9ddYY9XOquhEOOED4n5Hq3ZRowRD1I6lI7XwJZy6PGiX7sC59a6gZsK19NN8mpeZvrtSbgKttNi0hZUPC1/HJFPMitpyTuXFIJkPMBF2AGtJn6UTaqD0yL3i4PhnND2FUA1cwoWCBuUWVx4Q8NP9cmN3eXqsKXfaMCLo8h/scL/068IZrb/1yyUyQTbuBkMPde5aNbDqIvokYCROUN6FwGuatrEgJmf1OSyJKVfuMeAb9abj7I20I94Qp3SVlSeNeI/UDsHO5XUlEFaVPoAiu5oED3w+TCUo/XClyM7V7zTrn9L167y8PrjCfPixhwZxysLt4XoXOn5j8VkcbdThgGdgEBqnLdKL2DXJJvTaQBsuEQnXl2y22tXgzbQIUZvFiXQ== x-ms-exchange-antispam-messagedata: WVj3W5JOGiZ509Q+NOTXRro4la4+K2U5bJDKU/XNL1XIlWuFC8+RmSLqH5ythRYfnhXSwa/BLAXAfdFFWJEHqbkBHsv5SuTxrR+XnwIOuwO2NT8sy2XggTRepIfngtTnAJlpEjTOhjnerMzpEzoFNg== x-ms-exchange-transport-forked: True Content-Type: text/plain; charset="utf-8" Content-ID: Content-Transfer-Encoding: base64 MIME-Version: 1.0 X-MS-Exchange-CrossTenant-Network-Message-Id: 54292595-e53d-411e-aa75-08d7ae9f0ec1 X-MS-Exchange-CrossTenant-originalarrivaltime: 11 Feb 2020 03:04:06.5481 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e X-MS-Exchange-CrossTenant-mailboxtype: HOSTED X-MS-Exchange-CrossTenant-userprincipalname: NvglDghdCo96MZ64fWfbgAdm6p8bMtDkDxeCFQACfCqqNGeNaJ7m7zm1zXsYU8aFVT7Ls2me069OGYKZIsosPQ== X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM5PR11MB1371 X-OriginatorOrg: cisco.com X-Outbound-SMTP-Client: 173.37.102.13, xch-rcd-003.cisco.com X-Outbound-Node: alln-core-6.cisco.com Archived-At: Subject: Re: [TOOLS-DEVELOPMENT] Tools Call Agenda -- 11 February 2020 at 1:00 Eastern X-BeenThere: tools-development@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Tools Development list server List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Feb 2020 03:04:13 -0000 QXMgSSBhbSBhYnJvYWQgb24gdmFjYXRpb25zLCBJIHdvbid0IG1ha2UgdGhlIGNhbGwgDQoNCi3D qXJpYw0KDQrvu79PbiAxMC8wMi8yMDIwLCAxMjoxMiwgIlRPT0xTLURFVkVMT1BNRU5UIG9uIGJl aGFsZiBvZiBSb2JlcnQgU3BhcmtzIiA8dG9vbHMtZGV2ZWxvcG1lbnQtYm91bmNlc0BpZXRmLm9y ZyBvbiBiZWhhbGYgb2YgcmpzcGFya3NAbm9zdHJ1bS5jb20+IHdyb3RlOg0KDQogICAgQWdlbmRh IGJhc2g6DQogICAgDQogICAgV2Ugc2hvdWxkIHRhbGsgYWJvdXQgdGhlIG1pZ3JhdGlvbiB0byB0 aGUgbmV3IHNlcnZlciBpbiBzZWN0aW9uIDQuDQogICAgDQogICAgTm90ZXMgaW5saW5lIGZvciB0 b21vcnJvdydzIGNhbGw6DQogICAgDQogICAgT24gMi80LzIwIDM6MDEgUE0sIFJ1c3MgSG91c2xl eSB3cm90ZToNCiAgICA+IFRvb2xzIENhbGwgQWdlbmRhIC0tIDExIEZlYnJ1YXJ5IDIwMjAgYXQg MTowMCBFYXN0ZXJuDQogICAgPg0KICAgID4NCiAgICA+IEpPSU4gV0VCRVggTUVFVElORw0KICAg ID4gaHR0cHM6Ly9pZXRmLndlYmV4LmNvbS9pZXRmL2oucGhwP01USUQ9bTQ0MGRkODQ4NzI2MzM5 YzAzZTYwNWI5OTU2ZTM4YmFjDQogICAgPiBNZWV0aW5nIG51bWJlciAoYWNjZXNzIGNvZGUpOiA2 NDAgMTAzIDU3MA0KICAgID4gTWVldGluZyBwYXNzd29yZDogdG9vbHMNCiAgICA+DQogICAgPiBK T0lOIEJZIFBIT05FDQogICAgPiAxLTg3Ny02NjgtNDQ5MyBDYWxsLWluIHRvbGwgZnJlZSBudW1i ZXIgKFVTL0NhbmFkYSkNCiAgICA+IDEtNjUwLTQ3OS0zMjA4IENhbGwtaW4gdG9sbCBudW1iZXIg KFVTL0NhbmFkYSkNCiAgICA+IE1lZXRpbmcgbnVtYmVyIChhY2Nlc3MgY29kZSk6IDY0MCAxMDMg NTcwDQogICAgPiBNZWV0aW5nIHBhc3N3b3JkOiB0b29scw0KICAgID4NCiAgICA+DQogICAgPiAx LiBEYXRhdHJhY2tlciBQcm9qZWN0cw0KICAgID4gICAgIC0gRXhwZWN0ZWQgRGF0YXRyYWNrZXIg UmVsZWFzZXMgLS0gUm9iZXJ0IGFuZCBIZW5yaWsNCiAgICA+ICAgICAgIC0tIGh0dHBzOi8vdHJh Yy50b29scy5pZXRmLm9yZy90b29scy9pZXRmZGIvYnJvd3Nlci90cnVuay9QTEFODQogICAgVGhl IFBMQU4gd2FzIHVwZGF0ZWQgdG8gcmFpc2UgdGhlIHByaW9yaXR5IG9yZGVyIG9mICBjYXB0dXJp bmcgd2hlbiB0aGUgDQogICAgZGF0YXRyYWNrZXIgc2VuZHMgZW1haWwgKHRvIGZhY2lsaXRhdGUg cmUtc2VuZGluZyBtZXNzYWdlcyB3aGVuIG5lZWRlZCkgDQogICAgYW5kIHRyYW5zaXRpb25pbmcg dG8gRGphbmdvIDIuDQogICAgPiAgICAgLSBNZWV0aW5nIGFwcGxpY2F0aW9uIGltcHJvdmVtZW50 cyBieSBJT0xBIC0tIFJvYmVydA0KICAgIE9uIHRyYWNrIGFzIG9mIG1pZC1KYW4uIEknbSBhd2Fp dGluZyBhIG1vcmUgcmVjZW50IHVwZGF0ZSBmcm9tIElPTEEuDQogICAgPiAgICAgLSBBdXRvbWF0 ZWQgc2NoZWR1bGUgYnVpbGRlciBieSBEYXNoQ2FyZSAtLSBSb2JlcnQNCiAgICBQYXJ0IG9uZSBp cyBleHBlY3RlZCB0byBiZSBjb21wbGV0ZSBieSB0aGUgZW5kIG9mIEZlYi4NCiAgICA+ICAgICAt IE1pbm9yIFRvb2xzIEVuaGFuY2VtZW50cyBieSBQYWlubGVzcyBTZWN1cml0eSAtLSBSb2JlcnQN CiAgICBUaGlzIHRlYW0gaGFzIGNvbXBsZXRlZCAyIG9mIHRoZSAzIHBsYW5uZWQgaW5pdGlhbCBk YXRhdHJhY2tlciANCiAgICBlbmhhbmNlbWVudHMuIFRoZSBwbGFuIGlzIHRvIGZhbWlsaWFyaXpl IHRoZW0gd2l0aCB3b3JraW5nIG9uIGFzIG1hbnkgb2YgDQogICAgdGhlIHRvb2xzIGFzIHBvc3Np YmxlLiBUaGUgbmV4dCB0b29sIEkgd2lsbCBhc2sgdGhlbSB0byBkbyBtaW5vciANCiAgICBlbmhh bmNlbWVudHMgdG8gaXMgdGhlIG1haW4gd2Vic2l0ZS4NCiAgICA+DQogICAgPiAyLiBDb21tdW5p dHkgJiBPdGhlciBQcm9qZWN0cw0KICAgID4gICAgIC0gV1dXIHNlYXJjaCB0byBwcm92aWRlIGFk ZGl0aW9uYWwgcG9pbnRlcnMgLS0gR3JlZw0KICAgID4gICAgIC0gSG9zdCB0aGlyZC1wYXJ0eSBz dWJyZXNvdXJjZXMgb24gbWFpbGFyY2hpdmUgLS0gUnlhbg0KICAgID4NCiAgICA+IDMuIFJGQyBT ZXJ2aWNlcyBQcm9qZWN0cw0KICAgID4gICAgIC0gQXJlIHRvb2xzIGlzc3VlcyBibG9ja2luZyBh bnkgZG9jdW1lbnRzPyAtLSBKb2huIGFuZCBIZW5yaWsNCiAgICA+ICAgICAtIFNlY3VyaXR5IFJl dmlldyBvZiBSUEMgVG9vbHMgLS0gUm9iZXJ0IGFuZCBKYXkNCiAgICBUaGlzIFJGUCBoYXMgYmVl biBpc3N1ZWQgLSBzZWUgDQogICAgPGh0dHBzOi8vd3d3LmlldGYub3JnL21lZGlhL2RvY3VtZW50 cy9JRVRGX1JQQ19Ub29sc19TZWN1cml0eV9SZXZpZXdfUkZQXzA1RmViMjAucGRmPi4gDQogICAg QmlkcyBhcmUgZHVlIDRNYXIuDQogICAgPg0KICAgID4gNC4gU2VydmVyIEluZnJhc3RydWN0dXJl DQogICAgPiAgICAgLSBEZXBsb3ltZW50IG9mIFB5dGhvbjMgLS0gUm9iZXJ0DQogICAgPiAgICAg LSBFeHBlY3RlZCBXZWJzaXRlIFJlbGVhc2VzIC0tIFJvYmVydA0KICAgIA0KICAgIEkgcGxhbiB0 byBkbyBlaXRoZXIgYSBtaW5vciByZWxlYXNlIG9yIGEgcGF0Y2ggdG8gZml4IGFuIGlzc3VlIHdp dGggDQogICAgcHJldmlld2luZyBwYWdlcyBpbiB0aGUgYXV0aG9yaW5nIGFkbWluIGVhcmx5IHRo aXMgd2Vlay4NCiAgICANCiAgICBJIHNob3VsZCBoYXZlIGEgbWFqb3IgcmV2aXNpb24gcmVhZHkg Zm9yIHJldmlldyBvbiB3d3dzdGFnaW5nIGluIGEgZmV3IA0KICAgIGRheXMuIFRoaXMgcmV2aXNp b24gcmVtb3ZlcyB0aGUgYnJva2VuIGRhdGF0cmFja2VyIGludGVncmF0aW9uIGF0dGVtcHQsIA0K ICAgIGFuZCBzaW1wbGlmaWVzIG1hbnkgb2YgdGhlIG1vZGVscyBpbiBwcmVwYXJhdGlvbiBmb3Ig bW92aW5nIHRoZSB3ZWJzaXRlIA0KICAgIHRvIGEgY3VycmVudCByZXZpc2lvbiBvZiB3YWd0YWls Lg0KICAgIA0KICAgID4gICAgIC0gRE1BUkMgc3VwcG9ydCBmb3IgZW1haWwgYWxpYXNlcyAtLSBI ZW5yaWsgYW5kIEFsZXhleQ0KICAgID4NCiAgICA+IDUuIFlBTkcgQ2F0YWxvZw0KICAgID4gICAg IC0gVGFza3MgaW4gUHJpb3JpdHkgb3JkZXI6DQogICAgPiAgICAgICAtLSBQb3N0aW5nIFlBTkcg bW9kdWxlcyBieSBvdGhlciBTRE9zIC0tIEVyaWMgYW5kIFJvYmVydA0KICAgID4gICAgICAgLS0g UHV0dGluZyB5YW5nY2F0YWxvZy5vcmcgaW4gYSBEb2NrZXIgY29udGFpbmVyIC0tIFJvYmVydA0K ICAgID4gICAgICAgLS0gVXBncmFkZSB0aGUgb3BlcmF0aW5nIHN5c3RlbSBvbiB0aGUgc2VydmVy IC0tIFJvYmVydA0KICAgID4NCiAgICA+IDYuIFBhcmtpbmcgTG90DQogICAgPiAgICAgLSBTZWFy Y2ggb3ZlciB3d3csIGRhdGF0cmFja2VyLCBhbmQgbWFpbGFyY2hpdmUNCiAgICA+ICAgICAtIFRy YW5zaXRpb24gRGF0YXRyYWNrZXIgdG8gRGphbmdvMiBhbmQgdGhlbiBEamFuZ28zDQogICAgPiAg ICAgLSBUcmFuc2l0aW9uIE1haWxhcmNoaXZlIHRvIERqYW5nbzIgYW5kIHRoZW4gRGphbmdvMw0K ICAgID4gICAgIC0gVHJhbnNpdGlvbiBXYWd0YWlsIGZvciBJRVRGIHdlYnNpdGUgdG8gRGphbmdv MiBhbmQgdGhlbiBEamFuZ28zDQogICAgPg0KICAgID4gNy4gQU9CDQogICAgPg0KICAgID4gX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCiAgICA+IFRPT0xT LURFVkVMT1BNRU5UIG1haWxpbmcgbGlzdA0KICAgID4gVE9PTFMtREVWRUxPUE1FTlRAaWV0Zi5v cmcNCiAgICA+IGh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vdG9vbHMtZGV2 ZWxvcG1lbnQNCiAgICANCiAgICBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fXw0KICAgIFRPT0xTLURFVkVMT1BNRU5UIG1haWxpbmcgbGlzdA0KICAgIFRPT0xT LURFVkVMT1BNRU5UQGlldGYub3JnDQogICAgaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9s aXN0aW5mby90b29scy1kZXZlbG9wbWVudA0KICAgIA0KDQo= From nobody Tue Feb 11 12:49:59 2020 Return-Path: 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 8C177120132 for ; Tue, 11 Feb 2020 12:49:57 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.898 X-Spam-Level: X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=unavailable autolearn_force=no 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 2CjbJ64QVF5Q for ; Tue, 11 Feb 2020 12:49:56 -0800 (PST) Received: from mail.smeinc.net (mail.smeinc.net [209.135.209.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3170412006F for ; Tue, 11 Feb 2020 12:49:56 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id 7FAAE300B41 for ; Tue, 11 Feb 2020 15:16:06 -0500 (EST) X-Virus-Scanned: amavisd-new at mail.smeinc.net Received: from mail.smeinc.net ([127.0.0.1]) by localhost (mail.smeinc.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id TBXoIhWcis2D for ; Tue, 11 Feb 2020 15:16:04 -0500 (EST) Received: from [192.168.0.166] (wsip-72-194-193-110.dc.dc.cox.net [72.194.193.110]) by mail.smeinc.net (Postfix) with ESMTPSA id 8487F300595; Tue, 11 Feb 2020 15:16:04 -0500 (EST) From: Russ Housley Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\)) Message-Id: <0C2D1C1C-6031-4187-AB88-B0CDE3199C76@vigilsec.com> Date: Tue, 11 Feb 2020 15:42:44 -0500 Cc: IESG , IETF Tools Development To: IETF Chair X-Mailer: Apple Mail (2.3445.104.11) Archived-At: Subject: [TOOLS-DEVELOPMENT] Tools Team Report -- 11 February 2020 X-BeenThere: tools-development@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Tools Development list server List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Feb 2020 20:49:58 -0000 Tools Team Report -- 11 February 2020 1. Datatracker Projects - The plan has seen a few significant updates in the last week: -- https://trac.tools.ietf.org/tools/ietfdb/browser/trunk/PLAN -- Increased the priority of capturing a record of all email sent from the Datatracker. -- Raised the priority for the transition to Django 2.0. - A contract for Meeting Application Improvements was awarded to IOLA. The work related to the database models is complete and deployed; the works related to the user interface is underway, and it is expected to complete in the next few weeks. - A contract for the first part of the automated meeting schedule generation was awarded to DashCare, and work is underway. This is the first part of a bigger project; this part will provide better models for conflicts that have previously been captured as lore or text comments. This part of the project is expected to complete in the by the end of February 2020. - Contracts for Tools Maintenance and Minor Tools Enhancements were awarded to Elf Tools and Painless Security, respectively. In both cases, work is underway. Painless Security was give three initial tasks to familiarize them with the Datatracker code, and two have been completed. Painless Security will also be learning the code for other tools; they have begun a minor enhancement to the IETF website. 2. Community & Other Projects - Matomo has been integrated with the IETF Wagtail website, and it is collecting the desired analytics. 3. RFC Services Projects - One document is blocked on a bug in xml2rfc; the fix will be posted this week. - The Tools Team developed a Statement of Work for a security review of the tools used by the RFC Production Center, and the IETF LLC released the RFP in the first week of February 2020. The Tools Team will assist with the evaluation of bids, which a due on 4 March 2020. 4. Server Infrastructure - We plan to transition all IETF services to a new virtual server group on 24 February 2020, which was previously attempted on 27 January 2020. The reasons for the failed transition have been found in the Datatracker scripts, and they have been resolved. This transition will move us to the latest releases for the operating system, Python, and other software. - A minor release is planned this week to the IETF Wagtail website to fix an issue with previewing pages by authors. - A major revision to the IETF Wagtail website is planned for later this month to remove a previous broken attempt at Datatracker integration and simplify many of the models in preparation for transition to the current version of Wagtail. - The custom DMARC-handling software was deployed for all mail lists in June 2018. This custom software seems to be a better fit for the IETF than OpenARC. However, the custom software does not support the Internet-Draft and leadership email aliases. Once the virtual server upgrade is complete, we will investigate how to handle these email aliases. 5. YANG Catalog - Current focus is to better support the posting of YANG modules by other SDOs. - A sandbox of the YANGcatalog.org is running in a container. We expect deployment of the containerized version later this year. - A contract for YANG Catalog Maintenance by PANTHEON.tech is underway. From nobody Tue Feb 11 12:57:47 2020 Return-Path: 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 CE3BA12083A for ; Tue, 11 Feb 2020 12:57:45 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham autolearn_force=no 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 vje2WflWrzgC for ; Tue, 11 Feb 2020 12:57:42 -0800 (PST) Received: from macbook-pro.localdomain (unknown [158.140.230.105]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPSA id C727712006F for ; Tue, 11 Feb 2020 12:57:41 -0800 (PST) From: Jay Daley Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3608.40.2.2.4\)) Message-Id: <8973A94E-1169-4A5A-ADFA-ACCADA3A4949@ietf.org> Date: Wed, 12 Feb 2020 09:57:39 +1300 To: IETF Tools Development X-Mailer: Apple Mail (2.3608.40.2.2.4) Archived-At: Subject: [TOOLS-DEVELOPMENT] Trac - instances and issues X-BeenThere: tools-development@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Tools Development list server List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Feb 2020 20:57:46 -0000 Here=E2=80=99s my analysis of the trac situation so far. Any = corrections/additions most welcome. There are multiple trac =E2=80=99sites=E2=80=99 (for want of a better = word) 1. https://trac.ietf.org - This is the trac that the secretariat maintains - Every new WG automatically gets a trac instance created for it here = (343 current instances) but not all concluded WGs have one - As far as Robert knows, the only thing used here is the wiki pages not = the rest of the trac functionality - This has a tools trac instance which is not used 2. https://tools.ietf.org and https://trac.tools.ietf.org - This is the site that is maintained by Henrik - Some (All?) WGs are listed here (117 current and 515 concluded) with = each having a set of status pages and one of the headings of the status = page being a pointer to the wiki for 1. above - The two URLs work interchangeably (which is what confused me about two = instances per WG, when in fact there is only one) 3. https://trac.tools.ietf.org/tools/ietfdb/ - Same site as 2. above - This is the datatracker trac instance - The wiki and tickets functionality is used - This connects to a subversion repository with the datatracker source = enabling the browse source functionality - The roadmap functionality is not used, instead the roadmap is kept in = a source document = https://trac.tools.ietf.org/tools/ietfdb/browser/trunk/PLAN - Not all of the work items identified on the plan have a ticket = associated with them 4. https://trac.tools.ietf.org/tools/xml2rfc/trac/ - Same site as 2. above - This is the trac instance for xml2rfc - The tickets functionality is used - The wiki functionality is not used and instead there are static HTML = pages at https://tools.ietf.org/tools/xml2rfc/ (also accessed through = https://trac.tools.ietf.org/tools/xml2rfc/) - This connects to a subversion repository with the xml2rfc source = enabling the browse source functionality - The roadmap functionality is not used and I do not know if a separate = plan exists I=E2=80=99m still thinking this through, but the immediate issues that = concern me are a. Using the wrong tool for the job - i.e. using trac in places we = really just need a wiki tool. b. Multiple blind alleys of unused functionality (mainly caused by a. = above) c. Extremely difficult for a newcomer to find out what is current, what = is old and what was never used. d. Inconsistencies such that if a newcomer does work something out they = can't use that to help them understand the next part e. Not getting the most from trac (e.g. use of the roadmap feature) Thanks to much patient explanation by Russ, Robert and Henrik I = understand how we=E2=80=99ve got to where we=E2=80=99ve got and I = don=E2=80=99t want this to go over old ground - we are where we are - my = concern is how we improve the current situation in the best way possible = for everyone. Just to be clear, I=E2=80=99m not asking for anything to be done now, = I=E2=80=99m just sharing my analysis so far for info with a view to = starting a conversation about where to take this. cheers Jay --=20 Jay Daley IETF Executive Director jay@ietf.org +64 21 678840 From nobody Tue Feb 11 13:47:49 2020 Return-Path: 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 BD94C12081F; Tue, 11 Feb 2020 13:47:46 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.9 X-Spam-Level: X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no 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 utZ0kdhcv1Kz; Tue, 11 Feb 2020 13:47:44 -0800 (PST) Received: from zinfandel.tools.ietf.org (zinfandel.tools.ietf.org [64.170.98.42]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DFB8F120018; Tue, 11 Feb 2020 13:47:44 -0800 (PST) Received: from h-202-242.a357.priv.bahnhof.se ([158.174.202.242]:60272 helo=tannat.localdomain) by zinfandel.tools.ietf.org with esmtpsa (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from ) id 1j1dNK-00030i-DR; Tue, 11 Feb 2020 13:47:44 -0800 To: Jay Daley , IETF Tools Development References: <8973A94E-1169-4A5A-ADFA-ACCADA3A4949@ietf.org> From: Henrik Levkowetz Message-ID: <5c02a922-15de-baa0-a0c5-920b0254b493@levkowetz.com> Date: Tue, 11 Feb 2020 22:47:13 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 In-Reply-To: <8973A94E-1169-4A5A-ADFA-ACCADA3A4949@ietf.org> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="vTL5W1xtLBG9Ew8iPhtwsm823uEjxR1b8" X-SA-Exim-Connect-IP: 158.174.202.242 X-SA-Exim-Rcpt-To: tools-development@ietf.org, jay@ietf.org X-SA-Exim-Mail-From: henrik@levkowetz.com X-SA-Exim-Version: 4.2.1 (built Mon, 26 Dec 2011 16:24:06 +0000) X-SA-Exim-Scanned: Yes (on zinfandel.tools.ietf.org) X-Clacks-Overhead: GNU Terry Pratchett Archived-At: Subject: Re: [TOOLS-DEVELOPMENT] Trac - instances and issues X-BeenThere: tools-development@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Tools Development list server List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Feb 2020 21:47:47 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --vTL5W1xtLBG9Ew8iPhtwsm823uEjxR1b8 Content-Type: multipart/mixed; boundary="erpsF4q9p4v0fn6hPnCLNiJpojDGFFOmc"; protected-headers="v1" From: Henrik Levkowetz To: Jay Daley , IETF Tools Development Message-ID: <5c02a922-15de-baa0-a0c5-920b0254b493@levkowetz.com> Subject: Re: [TOOLS-DEVELOPMENT] Trac - instances and issues References: <8973A94E-1169-4A5A-ADFA-ACCADA3A4949@ietf.org> In-Reply-To: <8973A94E-1169-4A5A-ADFA-ACCADA3A4949@ietf.org> --erpsF4q9p4v0fn6hPnCLNiJpojDGFFOmc Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hi Jay, One point, inline below: On 2020-02-11 21:57, Jay Daley wrote: > Here=E2=80=99s my analysis of the trac situation so far. Any correctio= ns/additions most welcome. >=20 > There are multiple trac =E2=80=99sites=E2=80=99 (for want of a better w= ord) >=20 > 1. https://trac.ietf.org > - This is the trac that the secretariat maintains > - Every new WG automatically gets a trac instance created for it here (= 343 current instances) but not all concluded WGs have one > - As far as Robert knows, the only thing used here is the wiki pages no= t the rest of the trac functionality > - This has a tools trac instance which is not used >=20 > 2. https://tools.ietf.org and https://trac.tools.ietf.org > - This is the site that is maintained by Henrik > - Some (All?) WGs are listed here (117 current and 515 concluded) with = each having a set of status pages and one of the headings of the status p= age being a pointer to the wiki for 1. above > - The two URLs work interchangeably (which is what confused me about tw= o instances per WG, when in fact there is only one) These are not trac instances at all; they are the old WG pages I built before the datatracker had any resources for the WGs. These pages provid= ed the impetus for starting to build WG pages in the datatracker. Their functionality has gradually been duplicated (and in many cases now exceeded) in the datatracker, but there are still people who prefer the more compact representation provided on the tools.ietf.org pages. All data here is derived from the datatracker. > 3. https://trac.tools.ietf.org/tools/ietfdb/ > - Same site as 2. above > - This is the datatracker trac instance > - The wiki and tickets functionality is used > - This connects to a subversion repository with the datatracker source = enabling the browse source functionality > - The roadmap functionality is not used, instead the roadmap is kept in= a source document https://trac.tools.ietf.org/tools/ietfdb/browser/trunk= /PLAN > - Not all of the work items identified on the plan have a ticket associ= ated with them >=20 > 4. https://trac.tools.ietf.org/tools/xml2rfc/trac/ > - Same site as 2. above > - This is the trac instance for xml2rfc > - The tickets functionality is used > - The wiki functionality is not used and instead there are static HTML = pages at https://tools.ietf.org/tools/xml2rfc/ (also accessed through htt= ps://trac.tools.ietf.org/tools/xml2rfc/) > - This connects to a subversion repository with the xml2rfc source enab= ling the browse source functionality > - The roadmap functionality is not used and I do not know if a separate= plan exists >=20 >=20 > I=E2=80=99m still thinking this through, but the immediate issues that = concern me are >=20 > a. Using the wrong tool for the job - i.e. using trac in places we rea= lly just need a wiki tool. >=20 > b. Multiple blind alleys of unused functionality (mainly caused by a. = above) >=20 > c. Extremely difficult for a newcomer to find out what is current, wha= t is old and what was never used. >=20 > d. Inconsistencies such that if a newcomer does work something out the= y can't use that to help them understand the next part >=20 > e. Not getting the most from trac (e.g. use of the roadmap feature) >=20 >=20 > Thanks to much patient explanation by Russ, Robert and Henrik I > understand how we=E2=80=99ve got to where we=E2=80=99ve got and I don=E2= =80=99t want this to > go over old ground - we are where we are - my concern is how we > improve the current situation in the best way possible for everyone. >=20 > Just to be clear, I=E2=80=99m not asking for anything to be done now, I= =E2=80=99m > just sharing my analysis so far for info with a view to starting a > conversation about where to take this. Understood. Best, Henrik --erpsF4q9p4v0fn6hPnCLNiJpojDGFFOmc-- --vTL5W1xtLBG9Ew8iPhtwsm823uEjxR1b8 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEifjc5+rnL1MJBcZSTptXS4+7FxoFAl5DIOIACgkQTptXS4+7 FxrFmBAAxWfETDGe2Dl0nCv0oFoKSi2YX+ZxKbwx+e/GgpqZN8Gl58qkSxX+IyJA oZtD7wsiGPJoA+M282ObuqExAPORLZr0jcgal+FrlgFUVPpmY8xRfgFUE/TDjyxo GreIEFidrIRk8eZCcjcHNdUfY/wJVnu8kGYjG0uIVSPCbGBYhRXoZae01KWZ2/sp tekvWefk7OPCy7lJTQO857HlZ7dfg4eCzh6alwk+QO+gErMSzJ7dCMLFmUDARe8v wz33cNV/ex82cNTK4+zxFuAGMt8KZg/ZgsNw915P2m/CX818+xYXtOsKe8N8h1yU K+BNFUAX5JJg/QkzLGnRQlpo3E+dw4pc8oiXV9JvuY4oCwec6LukIq+cMnYA0MCp 47Ox6P14tajtxuP9QvWgcfs8Q2Fh8G0uWHYpCJMm/Q5PDnDlGBkMK9oIxih7d4QS GlN6zdcbLeSzuZ11MLW9I9ZZMyjyZ5eqHHLZXiGsYOnurO6Ugkc7x2Qz3ODuKt40 HUtfXgYZixsJYl8cbtQu7wRGKadzRESFktkdbN+KLEe3o6Mbv/+UJ5j1/djFG0us 2IEKMx6LLmzek1LBD4Ftt+kM05QaHSJL+zfMcbiFbHO4ZKI1l33XraQ81ku3UPNm SCDPUSIyor01nG+XpVboeXszhy8i678qDroiJ8QtaKGBXfqsbxI= =cF8R -----END PGP SIGNATURE----- --vTL5W1xtLBG9Ew8iPhtwsm823uEjxR1b8-- From nobody Tue Feb 11 13:50:42 2020 Return-Path: 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 70E04120A49 for ; Tue, 11 Feb 2020 13:50:38 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.899 X-Spam-Level: X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001] autolearn=ham autolearn_force=no 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 ZvI_2MPQzadz; Tue, 11 Feb 2020 13:50:36 -0800 (PST) Received: from macbook-pro.localdomain (unknown [158.140.230.105]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPSA id 0C1261209EF; Tue, 11 Feb 2020 13:50:35 -0800 (PST) From: Jay Daley Message-Id: <51EA5819-147D-45F1-A01F-9659D791B328@ietf.org> Content-Type: multipart/alternative; boundary="Apple-Mail=_5680AADE-E861-4113-8D24-F286805CDDCE" Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3608.40.2.2.4\)) Date: Wed, 12 Feb 2020 10:50:33 +1300 In-Reply-To: <5c02a922-15de-baa0-a0c5-920b0254b493@levkowetz.com> Cc: IETF Tools Development To: Henrik Levkowetz References: <8973A94E-1169-4A5A-ADFA-ACCADA3A4949@ietf.org> <5c02a922-15de-baa0-a0c5-920b0254b493@levkowetz.com> X-Mailer: Apple Mail (2.3608.40.2.2.4) Archived-At: Subject: Re: [TOOLS-DEVELOPMENT] Trac - instances and issues X-BeenThere: tools-development@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Tools Development list server List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Feb 2020 21:50:42 -0000 --Apple-Mail=_5680AADE-E861-4113-8D24-F286805CDDCE Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 > On 12/02/2020, at 10:47 AM, Henrik Levkowetz = wrote: >=20 > Hi Jay, >=20 > One point, inline below: >=20 > On 2020-02-11 21:57, Jay Daley wrote: >> Here=E2=80=99s my analysis of the trac situation so far. Any = corrections/additions most welcome. >>=20 >> There are multiple trac =E2=80=99sites=E2=80=99 (for want of a better = word) >>=20 >> 1. https://trac.ietf.org >> - This is the trac that the secretariat maintains >> - Every new WG automatically gets a trac instance created for it here = (343 current instances) but not all concluded WGs have one >> - As far as Robert knows, the only thing used here is the wiki pages = not the rest of the trac functionality >> - This has a tools trac instance which is not used >>=20 >> 2. https://tools.ietf.org and https://trac.tools.ietf.org >> - This is the site that is maintained by Henrik >> - Some (All?) WGs are listed here (117 current and 515 concluded) = with each having a set of status pages and one of the headings of the = status page being a pointer to the wiki for 1. above >> - The two URLs work interchangeably (which is what confused me about = two instances per WG, when in fact there is only one) >=20 > These are not trac instances at all; they are the old WG pages I built > before the datatracker had any resources for the WGs. These pages = provided > the impetus for starting to build WG pages in the datatracker. >=20 > Their functionality has gradually been duplicated (and in many cases = now > exceeded) in the datatracker, but there are still people who prefer = the > more compact representation provided on the tools.ietf.org = pages. Thanks Henrik - I understand now. Jay --=20 Jay Daley IETF Executive Director jay@ietf.org +64 21 678840 --Apple-Mail=_5680AADE-E861-4113-8D24-F286805CDDCE Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8

On 12/02/2020, at 10:47 AM, Henrik Levkowetz <henrik@levkowetz.com> wrote:

Hi Jay,

One point, inline = below:

On 2020-02-11 = 21:57, Jay Daley wrote:
Here=E2=80=99s my analysis of the = trac situation so far.  Any corrections/additions most welcome.

There are multiple trac =E2=80=99sites=E2=80=99 = (for want of a better word)

1.  https://trac.ietf.org
- This is the trac that the secretariat maintains
- Every new WG automatically gets a trac instance created for = it here (343 current instances) but not all concluded WGs have one
- As far as Robert knows, the only thing used here is the = wiki pages not the rest of the trac functionality
- This = has a tools trac instance which is not used

2.  https://tools.ietf.org and https://trac.tools.ietf.org
- This is the = site that is maintained by Henrik
- Some (All?) WGs are = listed here (117 current and 515 concluded) with each having a set of = status pages and one of the headings of the status page being a pointer = to the wiki for 1. above
- The two URLs work = interchangeably (which is what confused me about two instances per WG, = when in fact there is only one)

These are not trac instances at = all; they are the old WG pages I built
before the datatracker had any resources for the WGs. =  These pages provided
the impetus for starting to build WG pages in the = datatracker.

Their = functionality has gradually been duplicated (and in many cases = now
exceeded) in = the datatracker, but there are still people who prefer the
more compact representation = provided on the tools.ietf.org pages.

Thanks = Henrik - I understand now.

Jay


-- 
Jay Daley
IETF = Executive Director
jay@ietf.org
+64 21 678840

= --Apple-Mail=_5680AADE-E861-4113-8D24-F286805CDDCE-- From nobody Wed Feb 12 08:50:37 2020 Return-Path: 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 E32FA1208AB for ; Wed, 12 Feb 2020 08:50:35 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -104.2 X-Spam-Level: X-Spam-Status: No, score=-104.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham autolearn_force=no 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 0a5QjT7Ug7LA for ; Wed, 12 Feb 2020 08:50:35 -0800 (PST) Received: from mail.amsl.com (c8a.amsl.com [4.31.198.40]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 15E07120899 for ; Wed, 12 Feb 2020 08:50:35 -0800 (PST) Received: from mail.amsl.com (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTPS id 14410203788 for ; Wed, 12 Feb 2020 08:47:12 -0800 (PST) Received: from mail-ot1-f49.google.com (mail-ot1-f49.google.com [209.85.210.49]) by c8a.amsl.com (Postfix) with ESMTPSA id ECDCB203830 for ; Wed, 12 Feb 2020 08:47:11 -0800 (PST) Received: by mail-ot1-f49.google.com with SMTP id 77so2581737oty.6 for ; Wed, 12 Feb 2020 08:50:34 -0800 (PST) X-Gm-Message-State: APjAAAXuF8+21iKZaoav68hwbbFnnHMzZTJjBNVdjbxIkWb2SXyHaYed T9x2DyCzuDrfanBhEN50jpIctyUFreNPWKJajz0= X-Google-Smtp-Source: APXvYqz95l+ZkJ2nlKvIe5Iy1NUS2OvXwyesSjKDSeETxKD5ap274r2WZ2tgvWi0MnpRY/jrkdXadqcY4bpPLybtDfo= X-Received: by 2002:a9d:784b:: with SMTP id c11mr9546827otm.246.1581526234333; Wed, 12 Feb 2020 08:50:34 -0800 (PST) MIME-Version: 1.0 From: Glen Date: Wed, 12 Feb 2020 08:50:22 -0800 X-Gmail-Original-Message-ID: Message-ID: To: IETF Tools Development Content-Type: text/plain; charset="UTF-8" Archived-At: Subject: [TOOLS-DEVELOPMENT] Server cutover rescheduled X-BeenThere: tools-development@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Tools Development list server List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Feb 2020 16:50:36 -0000 Dear Tools Team: I just wanted to write informally to let this group know that, overnight, we've elected to move the server cutover forward from Monday the 24th to this Saturday the 15th. Nothing has changed; however, it's clear that there is no good reason to wait, and with the old server still struggling, I really feel like we need to get this done ASAP. By doing this on a weekend, we can be slightly less stressed about it, have more flexibility in handling any emergencies, and keep our community (and ourselves!) much happier. My thanks to Henrik, Robert, Russ and Ryan who have given up their weekend to work with me on this and monitor things post-cutover. I mention this here now because I'm going to send an announcement out to the Announce list tomorrow, and I didn't want anyone in this group to be confused about the date change given our conversations on the Tools Call yesterday. As always, any questions, let me know. Thanks, Glen -- Glen Barney IT Director AMS (IETF Secretariat) From nobody Thu Feb 13 15:22:08 2020 Return-Path: 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 54DD0120289 for ; Thu, 13 Feb 2020 15:22:07 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -104.2 X-Spam-Level: X-Spam-Status: No, score=-104.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham autolearn_force=no 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 PUi2RVfcQQXL for ; Thu, 13 Feb 2020 15:22:05 -0800 (PST) Received: from mail.amsl.com (c8a.amsl.com [4.31.198.40]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EA6391202A0 for ; Thu, 13 Feb 2020 15:22:05 -0800 (PST) Received: from mail.amsl.com (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTPS id 433F7203C38 for ; Thu, 13 Feb 2020 15:18:28 -0800 (PST) Received: from mail-oi1-f178.google.com (mail-oi1-f178.google.com [209.85.167.178]) by c8a.amsl.com (Postfix) with ESMTPSA id 27A80203C37 for ; Thu, 13 Feb 2020 15:18:28 -0800 (PST) Received: by mail-oi1-f178.google.com with SMTP id i1so7614533oie.8 for ; Thu, 13 Feb 2020 15:22:05 -0800 (PST) X-Gm-Message-State: APjAAAVPFYFXbtaZb5lU1npuOYFQwwjpJM9GpEreoK5QDQT413HcpH6e aERwhS/HFUx0fMReeV3IUp30Z+nkTXVdcJQqJlI= X-Google-Smtp-Source: APXvYqwuKUIf9fhv2qVynxO50j2QkfX1tEOKmWP+1zjmPxBMNKF7U9yXJ19h6YfvajVfNuGx8LQhPhPdc+rnPv/gLk0= X-Received: by 2002:a05:6808:8ee:: with SMTP id d14mr15600oic.138.1581636125213; Thu, 13 Feb 2020 15:22:05 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Glen Date: Thu, 13 Feb 2020 15:21:53 -0800 X-Gmail-Original-Message-ID: Message-ID: To: IETF Tools Development Content-Type: text/plain; charset="UTF-8" Archived-At: Subject: Re: [TOOLS-DEVELOPMENT] Server cutover rescheduled X-BeenThere: tools-development@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Tools Development list server List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Feb 2020 23:22:07 -0000 Dear Tools Team: On Wed, Feb 12, 2020 at 8:50 AM Glen wrote: > I just wanted to write informally to let this group know that, > overnight, we've elected to move the server cutover forward from > Monday the 24th to this Saturday the 15th. Follow-up for this group. Both of these dates are now out. We will reschedule for another Saturday as soon as we work out some additional details. I won't post any more noise to this list about this; we will send a general announcement out, as before, once we're ready to proceed. Thank you, Glen -- Glen Barney IT Director AMS (IETF Secretariat) From nobody Mon Feb 24 15:13:19 2020 Return-Path: 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 C1F8E3A151B for ; Mon, 24 Feb 2020 15:13:16 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.079 X-Spam-Level: X-Spam-Status: No, score=-2.079 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, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nostrum.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 ClsSS8L9IVgb for ; Mon, 24 Feb 2020 15:13:15 -0800 (PST) Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 991483A151D for ; Mon, 24 Feb 2020 15:13:15 -0800 (PST) Received: from unescapeable.local ([47.186.30.41]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id 01ONDDcB067502 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Mon, 24 Feb 2020 17:13:14 -0600 (CST) (envelope-from rjsparks@nostrum.com) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1582585994; bh=CCYgZvCqtyMzw00VZmTXtDCZuM85pb/w4cgRzxiNA/s=; h=To:Cc:From:Subject:Date; b=bSPc2yyCbOVfMGhfXe2E2FUKOxUooMc9rP7hbrO00+702T/0ZswXxJKJ6IfvtfX2n O6KOMmzQHB5xBnoblT8CAJCR/E6OCU+GB6wOQ8ci+CpBVL5wpX/Az+brI6mGE4RoCP jR0wnlYgs5aDDfTO9lyIRm+4G7vUNuB47CyklG8A= X-Authentication-Warning: raven.nostrum.com: Host [47.186.30.41] claimed to be unescapeable.local To: IETF Tools Development Cc: Martin Thomson From: Robert Sparks Message-ID: <9de49701-4477-291a-9a98-a39feb819a44@nostrum.com> Date: Mon, 24 Feb 2020 17:13:13 -0600 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:68.0) Gecko/20100101 Thunderbird/68.5.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US Archived-At: Subject: [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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Feb 2020 23:13:17 -0000 All - Here is a bare bones start at an SoW for building the backup infrastructure for github WG repositories as discussed in the git wg documents: Please comment or suggest changes where things need to change. Don't worry about the normal SoW framing for now, but focus on whether this is asking for the right thing. RjS From nobody Tue Feb 25 12:32:57 2020 Return-Path: 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 4FF9A3A154B for ; Tue, 25 Feb 2020 12:32:55 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.897 X-Spam-Level: X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no 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 2U5JTwidfPKH for ; Tue, 25 Feb 2020 12:32:53 -0800 (PST) Received: from mail.smeinc.net (mail.smeinc.net [209.135.209.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ADA583A154C for ; Tue, 25 Feb 2020 12:32:53 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id 378D7300B83 for ; Tue, 25 Feb 2020 15:32:51 -0500 (EST) X-Virus-Scanned: amavisd-new at mail.smeinc.net Received: from mail.smeinc.net ([127.0.0.1]) by localhost (mail.smeinc.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id 1KJ0T4mBDTCY for ; Tue, 25 Feb 2020 15:32:49 -0500 (EST) Received: from a860b60074bd.fios-router.home (pool-108-51-198-163.washdc.fios.verizon.net [108.51.198.163]) by mail.smeinc.net (Postfix) with ESMTPSA id C7E73300232; Tue, 25 Feb 2020 15:32:49 -0500 (EST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\)) From: Russ Housley In-Reply-To: <9de49701-4477-291a-9a98-a39feb819a44@nostrum.com> Date: Tue, 25 Feb 2020 15:32:51 -0500 Cc: IETF Tools Development , Martin Thomson Content-Transfer-Encoding: quoted-printable Message-Id: <0AEE469F-F140-45E4-B553-1B03A7B4DC45@vigilsec.com> References: <9de49701-4477-291a-9a98-a39feb819a44@nostrum.com> To: Robert Sparks X-Mailer: Apple Mail (2.3445.104.11) Archived-At: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Feb 2020 20:32:55 -0000 This looks fine to me. I am not sure, but should item number 3 also = allow restore to a local git repository? Russ > On Feb 24, 2020, at 6:13 PM, Robert Sparks = wrote: >=20 > All - >=20 > Here is a bare bones start at an SoW for building the backup = infrastructure for github WG repositories as discussed in the git wg = documents: >=20 > >=20 > Please comment or suggest changes where things need to change. Don't = worry about the normal SoW framing for now, but focus on whether this is = asking for the right thing. >=20 > RjS From nobody Tue Feb 25 12:43:05 2020 Return-Path: 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 B153E3A156F for ; Tue, 25 Feb 2020 12:43:03 -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 (1536-bit key) header.d=iecc.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 TG1cBP67VgBs for ; Tue, 25 Feb 2020 12:43:02 -0800 (PST) Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (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 CE8933A156E for ; Tue, 25 Feb 2020 12:43:01 -0800 (PST) Received: (qmail 2586 invoked from network); 25 Feb 2020 20:43:00 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent; s=a0c.5e5586d4.k2002; i=johnl-iecc.com@submit.iecc.com; bh=sfjLhUij3l5aW5liDZeVis2ZLGgLO8eRwZIhIVOVDgg=; b=eqt0ea4C8Yd7fnr0JY3yOHrb4MY5xRa0XV6iasmnpn9TAh5I6qxysyac8x5C2ptg1vXkcHE0xD2LbFQGhjYU3ifOIVB27xpPPreHqdCCFQPk1v42yQ2ZgHTAKVH8G3RLVHWuxq/+RAkzYt6UDyLazJieoyduO+m5rKl4crfeLrmkLAidvoMiJ9RIMTK9sTdGawc/mNp54XtktnOSkGFf05oRKSwhSrP/igtDZtppDClfAIMve5HU/yPrPhKn794J Received: from localhost ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPSA (TLS1.3 ECDHE-RSA AES-256-GCM AEAD, johnl@iecc.com) via TCP6; 25 Feb 2020 20:42:59 -0000 Date: 25 Feb 2020 15:42:59 -0500 Message-ID: From: "John R. Levine" To: "Russ Housley" , "Robert Sparks" Cc: "IETF Tools Development" , "Martin Thomson" In-Reply-To: <0AEE469F-F140-45E4-B553-1B03A7B4DC45@vigilsec.com> References: <9de49701-4477-291a-9a98-a39feb819a44@nostrum.com> <0AEE469F-F140-45E4-B553-1B03A7B4DC45@vigilsec.com> User-Agent: Alpine 2.22 (OSX 407 2020-02-09) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Archived-At: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Feb 2020 20:43:04 -0000 > This looks fine to me. I am not sure, but should item number 3 also allow restore to a local git repository? I'd think it'd be a good idea to provide some idea of how many repos, how large they're likely to be, and how often they're backed up. A lot of thongs that work fine on 100MB die painfully on multiple gigabytes. Regards, John Levine, johnl@taugh.com, Primary Perpetrator of "The Internet for Dummies", Please consider the environment before reading this e-mail. https://jl.ly From nobody Wed Feb 26 08:43:17 2020 Return-Path: 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 71FC53A0B9E for ; Wed, 26 Feb 2020 08:43:15 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.403 X-Spam-Level: X-Spam-Status: No, score=-1.403 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, KHOP_HELO_FCRDNS=0.276, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=nostrum.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 LMFUBLFjDyvt for ; Wed, 26 Feb 2020 08:43:10 -0800 (PST) Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DEBE03A0B92 for ; Wed, 26 Feb 2020 08:43:10 -0800 (PST) Received: from unescapeable.local ([47.186.30.41]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id 01QGh4Bi037593 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Wed, 26 Feb 2020 10:43:05 -0600 (CST) (envelope-from rjsparks@nostrum.com) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1582735386; bh=IMcvSQwg7uhuI6qhpVZcRYp9w15R9LgovlPCTwCu4vw=; h=Subject:To:Cc:References:From:Date:In-Reply-To; b=KPo0iMkfulKFndwm2NRZOBerVPdi5Yde4n65VAdRi2d4qytXeCyhaS6mK71dw4oa3 ipeI9wSTw5XXiIUPmta9+zUdV05rUiCNtsx1kc245axzngP2FLedYOacpK2Uyg3kui OZi91AHDgJPhhPQPfzrhhNU2z2z4Chww2Hio1SRo= X-Authentication-Warning: raven.nostrum.com: Host [47.186.30.41] claimed to be unescapeable.local To: "John R. Levine" , Russ Housley Cc: IETF Tools Development , Martin Thomson References: <9de49701-4477-291a-9a98-a39feb819a44@nostrum.com> <0AEE469F-F140-45E4-B553-1B03A7B4DC45@vigilsec.com> From: Robert Sparks Message-ID: Date: Wed, 26 Feb 2020 10:43:04 -0600 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:68.0) Gecko/20100101 Thunderbird/68.5.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US Archived-At: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Feb 2020 16:43:16 -0000 On 2/25/20 2:42 PM, John R. Levine wrote: >> This looks fine to me.  I am not sure, but should item number 3 also >> allow restore to a local git repository? > > I'd think it'd be a good idea to provide some idea of how many repos, > how large they're likely to be, and how often they're backed up.  A > lot of thongs that work fine on 100MB die painfully on multiple > gigabytes. The frequency will start out as hourly, as specified in draft-ietf-git-github-wg-configuration. At the moment, we can only thumbnail the expected initial number of repositories. We can put a theoretical upper bound on it using the total number of active WG/RG drafts. Getting the size of what the backup of a repository will be is going to be something the project will have to discover. We could get some anecdotal points with help from one of the larger WG users perhaps. The difficulty will be in exercising the API (or things built on it) that gets the entire project (issues, pull-requests, etc), not just the git repository itself. Martin - have you tried that with any of the repositories you have they keys for? RjS > > > Regards, > John Levine, johnl@taugh.com, Primary Perpetrator of "The Internet for > Dummies", > Please consider the environment before reading this e-mail. https://jl.ly From nobody Wed Feb 26 10:54:36 2020 Return-Path: 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 C99743A10F9 for ; Wed, 26 Feb 2020 10:54:34 -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=sCFO3n4M; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=G8fKYyJZ 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 eROKmabL8nCc for ; Wed, 26 Feb 2020 10:54:27 -0800 (PST) Received: from wout1-smtp.messagingengine.com (wout1-smtp.messagingengine.com [64.147.123.24]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 27C983A10E2 for ; Wed, 26 Feb 2020 10:54:26 -0800 (PST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.west.internal (Postfix) with ESMTP id 8FD435EE; Wed, 26 Feb 2020 13:54:25 -0500 (EST) Received: from imap2 ([10.202.2.52]) by compute1.internal (MEProxy); Wed, 26 Feb 2020 13:54:25 -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=sOxRsMdXRSojnFfUL9eJDvwpBCTRMJ1 LTW+gmSUp1qU=; b=sCFO3n4M0A8NHe7rQAcLi7nghzdIwuL3jdN1LWvDJaJ3Xf3 B++2eZaE+NaRV4P9qq5zcQW14Twq0ENNJzQYadDpO1cV9KWTVvDoh/S3MnFOfGbE R8JgDnB1KLfpzrYzLbE3IUaXa9e/zlpVy/P/dVgqfH30c2ZfqWkl7bVv4GeJ0ggR PjBeE1b3Ov5PJPOi4ScRfnbpEh4TyU1IKw5FvLeXxn+EIC/Nq7f8xgYz1ush2tf6 Jg8ilwhlO8wXdudE02WVKyzNl3niA5UZt1lOF9n8PLi2eUPqTjSnUGVwZmQ4TpXg 98YtwcS67DmZ3Yhc2vBRXTdMrQxK4iVyvedd7/w== 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=sOxRsM dXRSojnFfUL9eJDvwpBCTRMJ1LTW+gmSUp1qU=; b=G8fKYyJZh2GP1ZL8NjYoP6 NkUk7jqNEvyQ/DO60/Ezga62HEjJzJCYuWa1HWgBDdi2Lofg0sR9fCWQFMt/YewA srAu+2R8KDNW2fKZF2Ji/aalSCj1uoCONZGvcKu6IvEuKQGFaKt3Vz11SZ10BU9i vb9CcS3EmjAE9g0kGmYZlEoQ1otp2RRhipRyayMfsUSucxH1/TBKNst3qwBc5Xht FE2KCAR/ri/glXAJovt5CG2ufY9yhwceJ5v7F+3mHhDXAT70snJxSWKfMZ1HgJTM QP5Bixnnc0W8DHQSEwfCf0qeNs7ulCoemDW2KMmDzL+gBvHOijrAM3/nbkRplnxg == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedugedrleeggdduudelucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepofgfggfkjghffffhvffutgesthdtredtreertdenucfhrhhomhepfdforghr thhinhcuvfhhohhmshhonhdfuceomhhtsehlohifvghnthhrohhphidrnhgvtheqnecuff homhgrihhnpehquhhitgifghdrohhrghdpghhithhhuhgsrdgtohhmnecuvehluhhsthgv rhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepmhhtsehlohifvghnthhroh hphidrnhgvth X-ME-Proxy: Received: by mailuser.nyi.internal (Postfix, from userid 501) id A32B8E00AC; Wed, 26 Feb 2020 13:54:24 -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: <66380131-5b4e-4fa4-860c-08b240929e7f@www.fastmail.com> In-Reply-To: <9de49701-4477-291a-9a98-a39feb819a44@nostrum.com> References: <9de49701-4477-291a-9a98-a39feb819a44@nostrum.com> Date: Wed, 26 Feb 2020 11:54:03 -0700 From: "Martin Thomson" To: "Robert Sparks" , "IETF Tools Development" Content-Type: text/plain Archived-At: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Feb 2020 18:54:35 -0000 A few things to consider. This should include labels in the things that are backed up. Saving labels should be relatively trivial. This should include comments on issues and pull requests. A record of conversations can be critical to understanding how decisions were made. This can get a little complicated. I would be OK if comments on code (which can be on commits or on specific lines in pull requests) are not backed up. Any restore operation will necessarily be limited. Any tool that restores a repository will be unable to associate restored pull requests, issues, and comments with the original users who created them. It should be possible to have the tool generate issues and pull requests with "From @foo at $datetime" annotations, but those will be attributed to the robot account that is used for this process. In order to backup pull requests you will need to pull git commits from forks. Attempting to save the code from a pull request in any other form would be far more complicated. It would be good to specify this in a little more detail. The approach I have seen work here is just to fetch the commits and apply branch labels to them. It will not be possible for the original author of a pull request who created it from a fork to make additional changes, but they will be able to make a new pull request if they need to do anything. A related question there is whether you want to save code only for open pull requests or whether you want to record where the pull request was merged. Given that we will have git history, I don't think that we need to worry so much about old pull requests, aside from any commentary. FWIW, I have some limited backup capability for pull requests and issues, which you can see here: https://quicwg.org/base-drafts/issues.html With the 3k+ issues on that repo, it's very inefficient, but it does operate entirely offline. It doesn't capture comments either. I would like to have an alternative to this, because the method I use writes a very badly packed file to the repository, which is hugely inefficient. On Mon, Feb 24, 2020, at 16:13, Robert Sparks wrote: > All - > > Here is a bare bones start at an SoW for building the backup > infrastructure for github WG repositories as discussed in the git wg > documents: > > > > Please comment or suggest changes where things need to change. Don't > worry about the normal SoW framing for now, but focus on whether this is > asking for the right thing. > > RjS > > From nobody Wed Feb 26 11:00:12 2020 Return-Path: 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 5C9CC3A11AD for ; Wed, 26 Feb 2020 11:00:06 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.403 X-Spam-Level: X-Spam-Status: No, score=-1.403 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, KHOP_HELO_FCRDNS=0.276, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=nostrum.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 LbFEcEVOma0M for ; Wed, 26 Feb 2020 11:00:04 -0800 (PST) Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7F6E23A1190 for ; Wed, 26 Feb 2020 11:00:04 -0800 (PST) Received: from unescapeable.local ([47.186.30.41]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id 01QJ02Jp060930 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Wed, 26 Feb 2020 13:00:03 -0600 (CST) (envelope-from rjsparks@nostrum.com) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1582743603; bh=/5646QB29GfQrJgQBWBke4P9kTHccnXzaQbMAZC7eps=; h=Subject:To:References:From:Date:In-Reply-To; b=DW8MkUjM1Hmdc2/c639/5ES6PaYKzeMABmzK1ykAcuXPdJi1GXSuJU2GpH+9sWrFT yQZO+wqqhdQPuhqxq3luIe/c2Ojuk+X0gxKlRFr+wyFB4ukqWy7FrVxQOQlPDhtT65 jPxzSSocD4bCo1jeVS2BRh5II9KgThJcGH1eDz2c= X-Authentication-Warning: raven.nostrum.com: Host [47.186.30.41] claimed to be unescapeable.local To: Martin Thomson , IETF Tools Development References: <9de49701-4477-291a-9a98-a39feb819a44@nostrum.com> <66380131-5b4e-4fa4-860c-08b240929e7f@www.fastmail.com> From: Robert Sparks Message-ID: <2acd5e5e-0a1e-7658-964f-ca8d881b76f2@nostrum.com> Date: Wed, 26 Feb 2020 13:00:02 -0600 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:68.0) Gecko/20100101 Thunderbird/68.5.0 MIME-Version: 1.0 In-Reply-To: <66380131-5b4e-4fa4-860c-08b240929e7f@www.fastmail.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US Archived-At: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Feb 2020 19:00:11 -0000 Hi Martin - Have you tried using the organization migration api ( or something like against one or more of the repositories you have the owner role for? It would be good to know if either of those capture labels or comments. RjS On 2/26/20 12:54 PM, Martin Thomson wrote: > A few things to consider. > > This should include labels in the things that are backed up. Saving labels should be relatively trivial. > > This should include comments on issues and pull requests. A record of conversations can be critical to understanding how decisions were made. This can get a little complicated. I would be OK if comments on code (which can be on commits or on specific lines in pull requests) are not backed up. > > Any restore operation will necessarily be limited. Any tool that restores a repository will be unable to associate restored pull requests, issues, and comments with the original users who created them. It should be possible to have the tool generate issues and pull requests with "From @foo at $datetime" annotations, but those will be attributed to the robot account that is used for this process. > > In order to backup pull requests you will need to pull git commits from forks. Attempting to save the code from a pull request in any other form would be far more complicated. It would be good to specify this in a little more detail. The approach I have seen work here is just to fetch the commits and apply branch labels to them. It will not be possible for the original author of a pull request who created it from a fork to make additional changes, but they will be able to make a new pull request if they need to do anything. > > A related question there is whether you want to save code only for open pull requests or whether you want to record where the pull request was merged. Given that we will have git history, I don't think that we need to worry so much about old pull requests, aside from any commentary. > > FWIW, I have some limited backup capability for pull requests and issues, which you can see here: https://quicwg.org/base-drafts/issues.html With the 3k+ issues on that repo, it's very inefficient, but it does operate entirely offline. It doesn't capture comments either. I would like to have an alternative to this, because the method I use writes a very badly packed file to the repository, which is hugely inefficient. > > On Mon, Feb 24, 2020, at 16:13, Robert Sparks wrote: >> All - >> >> Here is a bare bones start at an SoW for building the backup >> infrastructure for github WG repositories as discussed in the git wg >> documents: >> >> >> >> Please comment or suggest changes where things need to change. Don't >> worry about the normal SoW framing for now, but focus on whether this is >> asking for the right thing. >> >> RjS >> >> From nobody Wed Feb 26 11:43:15 2020 Return-Path: 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 6CFF93A1294 for ; Wed, 26 Feb 2020 11:43:12 -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=dEKnfYwt; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=ZxpMAKWT 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 n2dTMDKPAULh for ; Wed, 26 Feb 2020 11:43:10 -0800 (PST) Received: from wout1-smtp.messagingengine.com (wout1-smtp.messagingengine.com [64.147.123.24]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 78D9A3A1291 for ; Wed, 26 Feb 2020 11:43:10 -0800 (PST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.west.internal (Postfix) with ESMTP id D19A76DE; Wed, 26 Feb 2020 14:43:08 -0500 (EST) Received: from imap2 ([10.202.2.52]) by compute1.internal (MEProxy); Wed, 26 Feb 2020 14:43:09 -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=6IwCJcSb93sYauMKjahd7mzq7WU5tSt dovQisED/Eek=; b=dEKnfYwtNBJAcqzhXZQDdngtbkUpAj/RXpgf/biZcMXfXa9 Z+jcHEDh4rT8ebw6lCvRMJ54tJJFheryL7gGAe4rbaYJnNIjQ9W6jUbeypuvazVj 2S97B9LNaxOykDUIV4cUV9fahvf6TXsP1FG6AYRHWsN3U9aRuCoXD9PsldAZnVmw TFn4pFR1FdftD0nCbEKyTLxYJS6mE6CT5AB4iNr2GxCgrA4r/tC14HgnCdA9sIb2 utQ/sBN3FAebSUb9PGPqmLSQUFycD2+8m2xC2EAFpQMsmHgxAYYj0mHb0xx2rbYz IauZYoPwWIOo1in9+i8+NrveGChYx4SbsFQWH4g== 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=6IwCJc Sb93sYauMKjahd7mzq7WU5tStdovQisED/Eek=; b=ZxpMAKWTHqY6Z2KsirRUlP oEFbJXp3iyZRP/QQeas08nz5CTJlCycq+CUdf8WRzdXOLWpUsBdtpisAY9bTeFpV NKJXloJ3GBd1UZMClM5LTMenysmP/MEeWytag0Y3wT6Ei3GwVFjjlD/+DR5wqB0g kpjp/CnSCk5BNv/5T16ZUNlvYZ1jNJmoKCmGxy/yUK6Xm0lDNpFDu9RSiHRLtezh II0UIaCnJGnTIbr4gGpf6O1i32wL51Od4geHUy5cadTBoeFxSAFqTXQVXAmgKr/+ i+bHyhKuWW0L+ERRBHFc/7s0wBamLJctxLTwyLr4ctIZcaXnQa6h8MQXeVclhGTQ == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedugedrleeggdduvdelucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepofgfggfkjghffffhvffutgesthdtredtreertdenucfhrhhomhepfdforghr thhinhcuvfhhohhmshhonhdfuceomhhtsehlohifvghnthhrohhphidrnhgvtheqnecuff homhgrihhnpehgihhthhhusgdrtghomhenucevlhhushhtvghrufhiiigvpedtnecurfgr rhgrmhepmhgrihhlfhhrohhmpehmtheslhhofigvnhhtrhhophihrdhnvght X-ME-Proxy: Received: by mailuser.nyi.internal (Postfix, from userid 501) id EDAFCE00AC; Wed, 26 Feb 2020 14:43:07 -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: In-Reply-To: <2acd5e5e-0a1e-7658-964f-ca8d881b76f2@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> Date: Wed, 26 Feb 2020 12:42:46 -0700 From: "Martin Thomson" To: "Robert Sparks" , "IETF Tools Development" Content-Type: text/plain Archived-At: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Feb 2020 19:43:13 -0000 On Wed, Feb 26, 2020, at 12:00, Robert Sparks wrote: > Hi Martin - > > Have you tried using the organization migration api > ( or something like > against one or > more of the repositories you have the owner role for? It would be good > to know if either of those capture labels or comments. So I have used the v3 "REST" API, which does offer the ability to capture comments. (I think that is what you mean by the first reference there; the organization migration option isn't really relevant here, by my understanding.) I just didn't use that capability, mostly because the API already requires a massive amount of data. There is a graphql API (https://developer.github.com/v4/) that is better in that regard, but I haven't had time to play with it. The API has information about labels. I have used that successfully. The python tool appears to capture labels and comments, but I haven't tried it. I don't know what format it stores data in. That might be critical to determining its suitability for this project. From nobody Wed Feb 26 13:32:59 2020 Return-Path: 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 52F6B3A0785 for ; Wed, 26 Feb 2020 13:32:58 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.402 X-Spam-Level: X-Spam-Status: No, score=-1.402 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, HTML_MESSAGE=0.001, KHOP_HELO_FCRDNS=0.276, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=nostrum.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 60ZtniHbwhFF for ; Wed, 26 Feb 2020 13:32:57 -0800 (PST) Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E4CB83A0787 for ; Wed, 26 Feb 2020 13:32:56 -0800 (PST) Received: from unescapeable.local ([47.186.30.41]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id 01QLWtxL086982 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Wed, 26 Feb 2020 15:32:56 -0600 (CST) (envelope-from rjsparks@nostrum.com) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1582752776; bh=WFqSFWkIjFJDEYp87Qfk5rDMb7UGT2bQLmsZob9RUJw=; h=Subject:To:References:From:Date:In-Reply-To; b=RGSekRJiMsqSuLKPckf6eH8G447HLh3L0wnqZRo2IUFhJuZTCua8kl2VOda8u10Of ixvw3YZ+/iJvPn45ZCygFTogtXXyIa0u7usIiJwp41lnycsqcax6Wckvleb/rudcHF rgeVxcnAncNmMI4i/4P8+bFjkIIycw+7olgqt6R8= X-Authentication-Warning: raven.nostrum.com: Host [47.186.30.41] claimed to be unescapeable.local To: Martin Thomson , IETF Tools Development References: <9de49701-4477-291a-9a98-a39feb819a44@nostrum.com> <66380131-5b4e-4fa4-860c-08b240929e7f@www.fastmail.com> <2acd5e5e-0a1e-7658-964f-ca8d881b76f2@nostrum.com> From: Robert Sparks Message-ID: <9eaed56c-6fb8-6037-3bcf-14776ac2f328@nostrum.com> Date: Wed, 26 Feb 2020 15:32:55 -0600 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:68.0) Gecko/20100101 Thunderbird/68.5.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/alternative; boundary="------------45194835A31BD590022F5BFB" Content-Language: en-US Archived-At: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Feb 2020 21:32:58 -0000 This is a multi-part message in MIME format. --------------45194835A31BD590022F5BFB Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit On 2/26/20 1:42 PM, Martin Thomson wrote: > On Wed, Feb 26, 2020, at 12:00, Robert Sparks wrote: >> Hi Martin - >> >> Have you tried using the organization migration api >> ( or something like >> against one or >> more of the repositories you have the owner role for? It would be good >> to know if either of those capture labels or comments. > So I have used the v3 "REST" API, which does offer the ability to capture comments. (I think that is what you mean by the first reference there; the organization migration option isn't really relevant here, by my understanding.) I think it is spot-on relevant. That is the current API github recommends for backing up organization repositories. See where it says > To download an archive of your repository, you can use the API for > user or organization migrations. For more information, see "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? > I just didn't use that capability, mostly because the API already requires a massive amount of data. There is a graphql API (https://developer.github.com/v4/) that is better in that regard, but I haven't had time to play with it. > > The API has information about labels. I have used that successfully. > > The python tool appears to capture labels and comments, but I haven't tried it. I don't know what format it stores data in. That might be critical to determining its suitability for this project. 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. --------------45194835A31BD590022F5BFB Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 7bit


On 2/26/20 1:42 PM, Martin Thomson wrote:
On Wed, Feb 26, 2020, at 12:00, Robert Sparks wrote:

Hi Martin -

Have you tried using the organization migration api 
(<https://developer.github.com/v3/migrations/orgs/> or something like 
<https://github.com/josegonzalez/python-github-backup> against one or 
more of the repositories you have the owner role for? It would be good 
to know if either of those capture labels or comments.

So I have used the v3 "REST" API, which does offer the ability to capture comments.  (I think that is what you mean by the first reference there; the organization migration option isn't really relevant here, by my understanding.)

I think it is spot-on relevant. That is the current API github recommends for backing up organization repositories.

See <https://help.github.com/en/github/creating-cloning-and-archiving-repositories/backing-up-a-repository> where it says

To download an archive of your repository, you can use the API for user or organization migrations. For more information, see "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?


 I just didn't use that capability, mostly because the API already requires a massive amount of data.  There is a graphql API (https://developer.github.com/v4/) that is better in that regard, but I haven't had time to play with it.

The API has information about labels. I have used that successfully.

The python tool appears to capture labels and comments, but I haven't tried it.  I don't know what format it stores data in. That might be critical to determining its suitability for this project.
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.

    

  


--------------45194835A31BD590022F5BFB--


From nobody Wed Feb 26 15:57:01 2020
Return-Path: 
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 ; 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 ; 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 ; 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: 
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedugedrleehgddukecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefofgggkfgjfhffhffvufgtsehttdertderredtnecuhfhrohhmpedfofgrrhht ihhnucfvhhhomhhsohhnfdcuoehmtheslhhofigvnhhtrhhophihrdhnvghtqeenucffoh hmrghinhepghhithhhuhgsrdgtohhmnecuvehluhhsthgvrhfuihiivgeptdenucfrrghr rghmpehmrghilhhfrhhomhepmhhtsehlohifvghnthhrohhphidrnhgvth
X-ME-Proxy:    
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>  <9eaed56c-6fb8-6037-3bcf-14776ac2f328@nostrum.com>
Date: Wed, 26 Feb 2020 16:56:35 -0700
From: "Martin Thomson" 
To: "Robert Sparks" , "IETF Tools Development" 
Content-Type: text/plain
Archived-At: 
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 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-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 " 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.


From nobody Thu Feb 27 08:11:16 2020
Return-Path: 
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 13B843A0BD6 for ; Thu, 27 Feb 2020 08:11:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level: 
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 ANFt5hkQnYGA for ; Thu, 27 Feb 2020 08:11:12 -0800 (PST)
Received: from mail.smeinc.net (mail.smeinc.net [209.135.209.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C887C3A0BD5 for ; Thu, 27 Feb 2020 08:11:12 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id 4814B300A27 for ; Thu, 27 Feb 2020 11:11:10 -0500 (EST)
X-Virus-Scanned: amavisd-new at mail.smeinc.net
Received: from mail.smeinc.net ([127.0.0.1]) by localhost (mail.smeinc.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id e5z3lGGheJeE for ; Thu, 27 Feb 2020 11:11:08 -0500 (EST)
Received: from a860b60074bd.fios-router.home (pool-108-51-198-163.washdc.fios.verizon.net [108.51.198.163]) by mail.smeinc.net (Postfix) with ESMTPSA id 4088F300A20; Thu, 27 Feb 2020 11:11:08 -0500 (EST)
From: Russ Housley 
Content-Type: multipart/mixed; boundary="Apple-Mail=_57C25238-FA8A-4048-8952-9A9E9D182B99"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Message-Id: <3729CE09-D13F-436D-A917-0DEF91348E31@vigilsec.com>
Date: Thu, 27 Feb 2020 11:11:09 -0500
Cc: IETF Tools Development 
To: Tools Team Discussion 
X-Mailer: Apple Mail (2.3445.104.11)
Archived-At: 
Subject: [TOOLS-DEVELOPMENT] Server Transition Briefing
X-BeenThere: tools-development@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Tools Development list server 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Thu, 27 Feb 2020 16:11:14 -0000

--Apple-Mail=_57C25238-FA8A-4048-8952-9A9E9D182B99
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=us-ascii

The IETF Tools Team will hold a one-hour WebEx session (see invite below)
on the recent server transition.  The goal is to share information about
the changes in the server architecture over the last decade and the most
recent upgrade that took place on 22 Feb 2020.  With this context in mind,
there will be time for discussion.  Some things we hope to hear about
include:

- how can the approach to monitoring/alerting be more transparent
- how to ensure monitoring/alerting covers the end user experience
- how to improve the infrastructure for testing
- next steps toward separation of services to reduce fragility and increase
  flexibility

I hope you are able to attend.

For the IETF Tools Team,
  Russ


= = = = = = = =

Meeting number (access code): 643 457 472
Meeting password: 2tgKWY8VUU8
 
Wednesday, March 11, 2020
8:00 pm UTC for 1 hour
 
Join by phone
Tap to call in from a mobile device (attendees only)
1-650-479-3208 Call-in toll number (US/Canada)
 
Join from a video system or application
Dial 643457472@ietf.webex.com
You can also dial 173.243.2.68 and enter your meeting number.
 
Join using Microsoft Lync or Microsoft Skype for Business
Dial 643457472.ietf@lync.webex.com
 
Need help? Go to http://help.webex.com


--Apple-Mail=_57C25238-FA8A-4048-8952-9A9E9D182B99
Content-Disposition: attachment;
	filename=Webex_Meeting.ics
Content-Type: text/calendar;
	x-unix-mode=0644;
	name="Webex_Meeting.ics"
Content-Transfer-Encoding: quoted-printable

BEGIN:VCALENDAR=0APRODID:-//Microsoft=20Corporation//Outlook=2010.0=20=
MIMEDIR//EN=0AVERSION:2.0=0AMETHOD:REQUEST=0ABEGIN:VEVENT=0A=
ATTENDEE;CN=3D"IETF=20Tools=20Team":MAILTO:tools-discuss@ietf.org=0A=
ORGANIZER;CN=3D"Cisco=20Webex":MAILTO:messenger@webex.com=0A=
DTSTART:20200311T200000Z=0ADTEND:20200311T210000Z=0A=
LOCATION:https://ietf.webex.com/ietf/j.php?MTID=3Dm00937c87933d32f8f66e20a=
62dd8e0a1=0ATRANSP:OPAQUE=0ASEQUENCE:1582818075=0A=
UID:74196a3d-1b5a-4065-a2a1-942d4f8157bf=0ADTSTAMP:20200311T200000Z=0A=
DESCRIPTION:\n\nJOIN=20WEBEX=20=
MEETING\nhttps://ietf.webex.com/ietf/j.php?MTID=3Dm00937c87933d32f8f66e20a=
62dd8e0a1\nMeeting=20number=20(access=20code):=20643=20457=20472\n\nHost=20=
key:=20889085\n\nMeeting=20password:=202tgKWY8VUU8\n\n\n\nJOIN=20BY=20=
PHONE\n1-650-479-3208=20Call-in=20toll=20number=20(US/Canada)=20\nTap=20=
here=20to=20call=20(mobile=20phones=20only,=20hosts=20not=20supported):=20=
tel:%2B1-650-479-3208,,*01*643457472%23%23*01*\n\n\nJOIN=20FROM=20A=20=
VIDEO=20SYSTEM=20OR=20APPLICATION\nDial=20=
sip:643457472@ietf.webex.com\nYou=20can=20also=20dial=20173.243.2.68=20=
and=20enter=20your=20meeting=20number.\n\n\nJoin=20using=20Microsoft=20=
Lync=20or=20Microsoft=20Skype=20for=20Business\nDial=20=
sip:643457472.ietf@lync.webex.com\n\n\n\nCan't=20join=20the=20meeting?=20=
Contact=20support=20here:\nhttps://ietf.webex.com/ietf/mc\n\n\nIMPORTANT=20=
NOTICE:=20Please=20note=20that=20this=20Webex=20service=20allows=20audio=20=
and=20other=20information=20sent=20during=20the=20session=20to=20be=20=
recorded,=20which=20may=20be=20discoverable=20in=20a=20legal=20matter.=20=
You=20should=20inform=20all=20meeting=20attendees=20prior=20to=20=
recording=20if=20you=20intend=20to=20record=20the=20meeting.\n=0A=
X-ALT-DESC;FMTTYPE=3Dtext/html:*=20{=20=20=20=20=
padding:=200;=20=20=20=20margin:=200;}table=20{=09border-collapse:=20=
separate;=20width=20=3D100%;=09border:=200;=09border-spacing:=200;}tr=20=
{=09line-height:=2018px;}a,=20td=20{=09font-size:=2014px;=09font-family:=20=
Arial;=09color:=20#333;=09word-wrap:=20break-word;=09word-break:=20=
normal;=09padding:=200;}.title=20{=09font-size:=2028px;}.image=20{=09=
width:=20auto;=09max-width:=20auto;}.footer=20{=09width:=20604px;}.main=20=
{}@media=20screen=20and=20(max-device-width:=20800px)=20{=09.title=20{=09=
=09font-size:=2022px=20!important;=09}=09.image=20{=09=09width:=20auto=20=
!important;=09=09max-width:=20100%=20!important;=09}=09.footer=20{=09=09=
width:=20100%=20!important;=09=09max-width:=20604px=20!important=09}=09=
.main=20{=09=09width:=20100%=20!important;=09=09max-width:=20604px=20=
!important=09}}=09=
 =09=09=09=09=09=09=
=09=09=09=09=09=09=09=09=09=09=09=09=09=09=09=09=09=09=09=09 =09=09=09=09=09=09=
=09=09=09=09=09=09=09=09=09=09
=09=09=09=09=
=09=09When=20=
it's=20time,=20join=20the=20Webex=20meeting=20here.=09=09=09=09=09=

=09=09=09=09=09=09Meeting=20number=20(access=20code):=20643=20457=20=
472=09=09=09=09=09
=09=09=09=
=09=09=09=09=09=09=09=09=09=09=09=09=09=09=09=09
=09=09=09=09=09=09Host=20key:=20=
889085=09=09=09=09=09
=09=09=
=09
Meeting=20password:2tgKWY8VUU8
=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=09 =09=09=09=09=09=09=09=09=09=09=09=09=09=09=09=09=09=09=09=09=09=09=09=09=09=
Join=20meeting=09=09=09=09=09=09=09=09=
=09=09=09
=09=09=09=09=09=09=09=09=09=20 
 
Join=20by=20phone =20=

Tap=20to=20=
call=20in=20from=20a=20mobile=20device=20(attendees=20only) =20=

1-650-479-3208 Call-in=20toll=20number=20=
(US/Canada) =20

 
Join=20from=20a=20video=20system=20or=20=
application
Dial=20643457472@ietf.webex.com =20
You=20can=20=
also=20dial=20173.243.2.68=20and=20enter=20your=20meeting=20=
number.=20 =20
 =20
 =20=

Join=20using=20Microsoft=20Lync=20or=20Microsoft=20Skype=20for=20=
BusinessDial=20643457472.ietf@lync.webex.com=

=09=09=09=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20 =09=09=09=09=
=09=09=09=09=09Need=20=
help?=20Go=20to=20http://help.webex.com=09=09=09=09=09=09=09=
=09=09=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20 =09=09=09=09=09=
=09=0ASUMMARY:Server=20Transition=20Briefing=0A=
PRIORITY:5=0ACLASS:PUBLIC=0AEND:VEVENT=0AEND:VCALENDAR=0A=

--Apple-Mail=_57C25238-FA8A-4048-8952-9A9E9D182B99--


From nobody Thu Feb 27 12:55:44 2020
Return-Path: 
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 A9F983A0C1D for ; Thu, 27 Feb 2020 12:55:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.403
X-Spam-Level: 
X-Spam-Status: No, score=-1.403 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, KHOP_HELO_FCRDNS=0.276, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=nostrum.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 ts6fmPOcIHDQ for ; Thu, 27 Feb 2020 12:55:34 -0800 (PST)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 648613A0BF7 for ; Thu, 27 Feb 2020 12:55:34 -0800 (PST)
Received: from unescapeable.local ([47.186.30.41]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id 01RKtWuY097324 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Thu, 27 Feb 2020 14:55:33 -0600 (CST) (envelope-from rjsparks@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1582836933; bh=RLvpnJ3u+HktjuGWxHxcweT3NwSr1snCZKoqlt0p3qs=; h=Subject:To:References:From:Date:In-Reply-To; b=uFq4+RMg9OFEYymkLDb6OUGhF7TVuIziUEhYwRugw347g1Nbd/dctYJpi2r/KIBu3 kz4LexTAbBit59Fh7nMeoq6I+9n3TfH/cQf1sm5yHgLr/ehfuluBP23TfeUPI4iGeC fLdbuq/rOEy+R+HPEYv6k9L8hUaf46KxQFDBS2K4=
X-Authentication-Warning: raven.nostrum.com: Host [47.186.30.41] claimed to be unescapeable.local
To: Martin Thomson , IETF Tools Development 
References: <9de49701-4477-291a-9a98-a39feb819a44@nostrum.com> <66380131-5b4e-4fa4-860c-08b240929e7f@www.fastmail.com> <2acd5e5e-0a1e-7658-964f-ca8d881b76f2@nostrum.com>  <9eaed56c-6fb8-6037-3bcf-14776ac2f328@nostrum.com> <7d0e1230-7fab-4aed-bc64-55a4ca8438ad@www.fastmail.com>
From: Robert Sparks 
Message-ID: 
Date: Thu, 27 Feb 2020 14:55:31 -0600
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:68.0) Gecko/20100101 Thunderbird/68.5.0
MIME-Version: 1.0
In-Reply-To: <7d0e1230-7fab-4aed-bc64-55a4ca8438ad@www.fastmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Archived-At: 
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 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Thu, 27 Feb 2020 20:55:42 -0000

On 2/26/20 5:56 PM, Martin Thomson wrote:
> 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 " 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.

You have to do the steps before it on that page before there's anything 
to download.

Specifically: 
https://developer.github.com/v3/migrations/users/#start-a-user-migration 
will have had to have succeeded (it's where you get :migration_id, and 
https://developer.github.com/v3/migrations/users/#start-a-user-migration 
will have to have been checked to see that the migration has finished 
successfully.

And one more thing to consider: This whole API requires providing the 
credentials of an _owner_ of the repository being backed up. I suspect 
that means we'll have an identity that we ask WG draft repositories to 
add as an owner. Does that match your expectations?

>
>> 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.


From nobody Fri Feb 28 01:26:49 2020
Return-Path: 
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 026173A13E9 for ; Fri, 28 Feb 2020 01:26:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level: 
X-Spam-Status: No, score=-2.098 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_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=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=lowentropy.net header.b=GWsoJnlL; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=y4nsx4RE
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 ueruelcCc9TM for ; Fri, 28 Feb 2020 01:26:45 -0800 (PST)
Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AD08D3A13E7 for ; Fri, 28 Feb 2020 01:26:45 -0800 (PST)
Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.nyi.internal (Postfix) with ESMTP id 85ADC21910; Fri, 28 Feb 2020 04:26:44 -0500 (EST)
Received: from imap2 ([10.202.2.52]) by compute2.internal (MEProxy); Fri, 28 Feb 2020 04:26:44 -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=mwvhHU3+wclvpBv7oNcI1Y8cQ/5O/Gf +m7q35oW1bf0=; b=GWsoJnlLH84Ex2O/qkI2Pcna0kEa4KEEdKJFfbjAb9KSqC3 svG9MpeQUxsGHKUUlFekSwRvT7I6dYnV/33MvKljxZd7JuhE1ggMyqgp9II7AI8v 8gxVUh23Qp9wYc8qs+WPw0HH3BlsJ5wnyjouy0irYIUeI6EPVriJ302WzIefUOmL qGydTjCHicw4owhvPUEblKpR3NB+be7pnSjiBt8Ov2JouaVMUjZkdjkcH3qkE5BF W59MQjnNsOPiR4hUHxffLh9ZiyJhMcbhK4AH3VS79k7Zqi2592X+4VhCFps58tTz 4NKCwWR+PwJlf07vImaP96MYsimcdGxOzSK+k+A==
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=mwvhHU 3+wclvpBv7oNcI1Y8cQ/5O/Gf+m7q35oW1bf0=; b=y4nsx4REEcV3r+kgMGGdWx 5iHjzPGOvhpq2tyJumnI63tmD98azc5yOHBYI6NA7ir3cDrGcyGjlFUjM6WqMFKs fgUToqTdvIRsIU3uwGkQhB5YWIVDnCCc12aekVxPZ93XHt1kvr/C/iWzS9yM2KRN 5sKM8XxKLnXMw26MNF+MAyhr4kWteqf7+J4/wlJP9abQbfVmMouOT2DtsYKVOq4e ARcKEKCjvcFw9sMarRdhBaqIGLqF/Dj1IxBQaD79FUzArfl8M67nVQrFoPfyjJuX qJMU85oLzKaw937v3KThOWzQMci7LS+MOPJ6wkLciVoTxvfCBpxmLSZCRT2d8nLg ==
X-ME-Sender: 
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedugedrleekgddtvdcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefofgggkfgjfhffhffvufgtsehttdertderredtnecuhfhrohhmpedfofgrrhht ihhnucfvhhhomhhsohhnfdcuoehmtheslhhofigvnhhtrhhophihrdhnvghtqeenucevlh hushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehmtheslhhofigv nhhtrhhophihrdhnvght
X-ME-Proxy:    
Received: by mailuser.nyi.internal (Postfix, from userid 501) id EE233E00B9; Fri, 28 Feb 2020 04:26:43 -0500 (EST)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.1.7-967-g014f925-fmstable-20200226v1
Mime-Version: 1.0
Message-Id: <91d83c87-3a20-4b01-aee4-9535196b3427@www.fastmail.com>
In-Reply-To: 
References: <9de49701-4477-291a-9a98-a39feb819a44@nostrum.com> <66380131-5b4e-4fa4-860c-08b240929e7f@www.fastmail.com> <2acd5e5e-0a1e-7658-964f-ca8d881b76f2@nostrum.com>  <9eaed56c-6fb8-6037-3bcf-14776ac2f328@nostrum.com> <7d0e1230-7fab-4aed-bc64-55a4ca8438ad@www.fastmail.com> 
Date: Fri, 28 Feb 2020 02:26:22 -0700
From: "Martin Thomson" 
To: "Robert Sparks" , "IETF Tools Development" 
Content-Type: text/plain
Archived-At: 
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 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Fri, 28 Feb 2020 09:26:47 -0000

(Travel might delay more responses...)

On Thu, Feb 27, 2020, at 13:55, Robert Sparks wrote:
> And one more thing to consider: This whole API requires providing the 
> credentials of an _owner_ of the repository being backed up. I suspect 
> that means we'll have an identity that we ask WG draft repositories to 
> add as an owner. Does that match your expectations?

Now that I understand this more, that is just one of the problems: locking the repo every hour is likely to be too disruptive.  I don't particularly like the idea that we have this tool as an owner, but that's less of a problem.


From nobody Fri Feb 28 06:14:29 2020
Return-Path: 
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 0954B3A18D3 for ; Fri, 28 Feb 2020 06:14:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.403
X-Spam-Level: 
X-Spam-Status: No, score=-1.403 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, KHOP_HELO_FCRDNS=0.276, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=nostrum.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 LL0b5L6k-DUJ for ; Fri, 28 Feb 2020 06:14:17 -0800 (PST)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F07C23A18CD for ; Fri, 28 Feb 2020 06:14:16 -0800 (PST)
Received: from unescapeable.local ([47.186.30.41]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id 01SEEEPe029900 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Fri, 28 Feb 2020 08:14:16 -0600 (CST) (envelope-from rjsparks@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1582899256; bh=rvBay0qGgttvDGkHunsiyTNHbofKo/jG1K9fyQaXICE=; h=Subject:To:References:From:Date:In-Reply-To; b=Hk+PHgcR25/7TGP3hUFmhr/7fpLtHwhRXqciRO3Y5e8j+VXCLB5vtdTHd1pG5rdVI 0vPKecUXCr7CYf1/8Lyxg8X7SNwRBYireW88+tFZZyZKnz1lhoiBbMtSnFOMYC8X9A KoQHGheFUpduAmIjJzYIcQEnJLPovNSjqLulmxeY=
X-Authentication-Warning: raven.nostrum.com: Host [47.186.30.41] claimed to be unescapeable.local
To: Martin Thomson , IETF Tools Development 
References: <9de49701-4477-291a-9a98-a39feb819a44@nostrum.com> <66380131-5b4e-4fa4-860c-08b240929e7f@www.fastmail.com> <2acd5e5e-0a1e-7658-964f-ca8d881b76f2@nostrum.com>  <9eaed56c-6fb8-6037-3bcf-14776ac2f328@nostrum.com> <7d0e1230-7fab-4aed-bc64-55a4ca8438ad@www.fastmail.com>  <91d83c87-3a20-4b01-aee4-9535196b3427@www.fastmail.com>
From: Robert Sparks 
Message-ID: <784fca0c-de95-f40d-0cba-bfeec28a4224@nostrum.com>
Date: Fri, 28 Feb 2020 08:14:14 -0600
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:68.0) Gecko/20100101 Thunderbird/68.5.0
MIME-Version: 1.0
In-Reply-To: <91d83c87-3a20-4b01-aee4-9535196b3427@www.fastmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Archived-At: 
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 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Fri, 28 Feb 2020 14:14:27 -0000

On 2/28/20 3:26 AM, Martin Thomson wrote:
> (Travel might delay more responses...)
>
> On Thu, Feb 27, 2020, at 13:55, Robert Sparks wrote:
>> And one more thing to consider: This whole API requires providing the
>> credentials of an _owner_ of the repository being backed up. I suspect
>> that means we'll have an identity that we ask WG draft repositories to
>> add as an owner. Does that match your expectations?
> Now that I understand this more, that is just one of the problems: locking the repo every hour is likely to be too disruptive.

locking is an option, not a requirement, and it's turned off by default. 
I didn't see anything that indicated it would break things if you didn't 
lock the repository.

I think that option was there only to make it easier for people who were 
really _migrating_ a repository to a different place to avoid confusion 
or losing information during transition.

>    I don't particularly like the idea that we have this tool as an owner, but that's less of a problem.