Re: [TOOLS-DEVELOPMENT] Tools Call Agenda -- 8 October 2019 at 1:00 Eastern

Robert Sparks <rjsparks@nostrum.com> Mon, 07 October 2019 15:50 UTC

Return-Path: <rjsparks@nostrum.com>
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 4FF6A120110 for <tools-development@ietfa.amsl.com>; Mon, 7 Oct 2019 08:50:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.98
X-Spam-Level:
X-Spam-Status: No, score=-1.98 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] 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 e2fXliU1Etcb for <tools-development@ietfa.amsl.com>; Mon, 7 Oct 2019 08:50:00 -0700 (PDT)
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 F137B120041 for <tools-development@ietf.org>; Mon, 7 Oct 2019 08:49:59 -0700 (PDT)
Received: from unescapeable.local ([47.186.30.41]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id x97FnvIS055736 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for <tools-development@ietf.org>; Mon, 7 Oct 2019 10:49:59 -0500 (CDT) (envelope-from rjsparks@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1570463399; bh=cued+qW+ZSzZJ5S6mfUVH5OVVpJn7DQ62HsSyh2c6i0=; h=Subject:From:To:References:Date:In-Reply-To; b=IdaPJwCCKphbrffopT0Co3GV3B03IrNyOkxJQSEtR3YmIR8MPgNI9gZCRm+FjjrHe IH9Mcj0iLL5I3L5rU3bAr1xwdK0Fq9EoEkC22xylG1PUj8lD7UQunbzWCSEHrrWPy/ FRw+dDi+GpOTkFDm+KX6xjTmNW4nQMaZfJ6lDY9I=
X-Authentication-Warning: raven.nostrum.com: Host [47.186.30.41] claimed to be unescapeable.local
From: Robert Sparks <rjsparks@nostrum.com>
To: tools-development@ietf.org
References: <DBEBAE12-4D81-44EA-A6C7-839909C943CE@vigilsec.com> <74e88b05-9993-c932-47de-928bbafb1951@nostrum.com>
Message-ID: <020c56b3-8d6d-6e37-1edd-c315a5c40d73@nostrum.com>
Date: Mon, 7 Oct 2019 10:49:57 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:60.0) Gecko/20100101 Thunderbird/60.9.0
MIME-Version: 1.0
In-Reply-To: <74e88b05-9993-c932-47de-928bbafb1951@nostrum.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-development/CtorIb6tiKC3Y_hlQNoLOOcsww0>
Subject: Re: [TOOLS-DEVELOPMENT] Tools Call Agenda -- 8 October 2019 at 1:00 Eastern
X-BeenThere: tools-development@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Tools Development list server <tools-development.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tools-development>, <mailto:tools-development-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tools-development/>
List-Post: <mailto:tools-development@ietf.org>
List-Help: <mailto:tools-development-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tools-development>, <mailto:tools-development-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Oct 2019 15:50:03 -0000

On 10/4/19 10:37 AM, Robert Sparks wrote:
> Some notes for the call.
>
> On 10/3/19 1:09 PM, Russ Housley wrote:
>> Tools Call Agenda -- 8 October 2019 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 priorities in the plan have been tuned. Please look and see that 
> they still meet expectations.
>
>
>>     - Implementation of last-call@ietf.org -- Robert
>
> Most of the work for this (other than creating the new list) is in the 
> datatracker.
>
> We plan to have this as a release ready to deploy on Oct 18.
>
>>     - Meeting Application Improvements by IOLA -- Robert
> IOLA began work this week. They are significantly off their originally 
> expected start date. I think it is still reasonable for them to finish 
> this project this year.
>>     - Datatracker maintenance by DashCare -- Robert
> The improvements to the review tool project continues to go well. The 
> recent 6.104.0 release contained much of this work, and the next 
> several will continue to include improvements.
>>     - IRSG balloting -- Robert
> On track for completion before IETF106.
>>     - Deployment of Python3 datatracker -- Robert
>
> We are going to have to separate and containerize trac, which isn't 
> likely to become python3 enabled until sometime next year.
>
> We are currently planning to deploy the conversion to python 3 when 
> the main ietf server is upgraded.
>
>>       -- Impacts on related applications
> The mailarchive app will need to deploy on python 3 at the same time 
> as the datatracker.
>>
>> 2. Community & Other Projects
>>     - WWW search to provide additional pointers -- Greg
>>       -- Give pointers to datatracker and mailarchive
> This is on my queue to implement.
>>     - Host third-party subresources on mailarchive -- Ryan
>>
>> 3. RFC Services Projects
>>     - RPC use of new RFC format tools -- Heather and Henrik
>>     - Deploying in-line errata on rfc-editor.org? -- Alice
>>     - Security Review of RPC Tools -- Robert and Heather
> We are in the period where we are gathering proposals. The deadline is 
> 14Oct. We have received a few clarifying questions and have answers 
> ready for the 7Oct question response deadline.
>>
>> 4. Server Infrastructure
>>     - Expected Website Releases -- Robert
>
> I released a significant to the website behavior today (affecting blog 
> page performance). It should be in production before we get to 
> Tuesday's meeting.
>
> See <https://github.com/ietf-tools/wagtail_website/releases>;.
>
> There will be several releases in the next couple of weeks that change 
> database internals without changing the public's view of the website. 
> The names of fields that editors use will be improved.
>
> After that, the major work items are to
>
> * Remove the current datatracker integration attempt
>
> * Migrate to Django 2 so that we can move to more recent wagtail releases
>
> * Investigate reimplementation of the Area and Topic templates
>
> We'll be making smaller improvements with regular releases from now on.
>
> We're discovering that the CSS framework used by the current system is 
> undocumented, and hard to work with. We are beginning to discuss a 
> project to rebase the site on Bootstrap4 while maintaining the look 
> and feel of the site.
>
>>     - IESG discussions of DMARC -- Henrik and Alexey
>>       -- When do we expect the next release of OpenARC? Ever?
>>
>> 5. YANG Catalog
>>     - Putting yangcatalog.org in a Docker container -- Robert
> As noted in the last meeting, this is prioritized behind major 
> functionality issues in the yangcatalog project, but it is getting 
> cycles. I am currently to the point where most of the containers come 
> up the way they should in my development environment , but the confd 
> and api_recovery containers are not reaching the expected steady 
> run-state. I am keeping pressure on this, but I don't expect that 
> we'll switch production to the containerized version in the near 
> future. Certainly not before IETF106.
>>
>> 6. Parking Lot
>>     - Search over www, datatracker, and mailarchive
>>     - Transition Datatracker to Django2
>>     - Transition Website to Django2
>>
>> 7. AOB
I think we should talk briefly about the state of supporting markdown 
for minutes/agendas (and eventually other documents), and how we should 
prioritize improving it.
>>
>> _______________________________________________
>> TOOLS-DEVELOPMENT mailing list
>> TOOLS-DEVELOPMENT@ietf.org
>> https://www.ietf.org/mailman/listinfo/tools-development