Re: [TOOLS-DEVELOPMENT] Tools Call Agenda -- 10 September 2019 at 1:00 Eastern

Russ Housley <housley@vigilsec.com> Mon, 09 September 2019 16:26 UTC

Return-Path: <housley@vigilsec.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 0E1C212007A for <tools-development@ietfa.amsl.com>; Mon, 9 Sep 2019 09:26:52 -0700 (PDT)
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=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 uEzMscKxxLa7 for <tools-development@ietfa.amsl.com>; Mon, 9 Sep 2019 09:26:50 -0700 (PDT)
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 65931120041 for <tools-development@ietf.org>; Mon, 9 Sep 2019 09:26:50 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id AF736300AED for <tools-development@ietf.org>; Mon, 9 Sep 2019 12:26:48 -0400 (EDT)
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 6XZtpx-mORQO for <tools-development@ietf.org>; Mon, 9 Sep 2019 12:26:47 -0400 (EDT)
Received: from a860b60074bd.fios-router.home (unknown [138.88.156.37]) by mail.smeinc.net (Postfix) with ESMTPSA id D894A300470; Mon, 9 Sep 2019 12:26:46 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <4b712824-1ce0-6a47-d512-685c11aac67b@nostrum.com>
Date: Mon, 9 Sep 2019 12:26:46 -0400
Cc: IETF Tools Development <tools-development@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <A63D4999-58D9-4FC2-990F-F5B0828C9379@vigilsec.com>
References: <57225470-D9D0-4066-91D8-26BCF66C67D6@vigilsec.com> <4b712824-1ce0-6a47-d512-685c11aac67b@nostrum.com>
To: Robert Sparks <rjsparks@nostrum.com>
X-Mailer: Apple Mail (2.3445.104.11)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-development/5JTQQDE7qS1QjRMQWQ_U42x40_Q>
Subject: Re: [TOOLS-DEVELOPMENT] Tools Call Agenda -- 10 September 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, 09 Sep 2019 16:26:52 -0000

Robert:

>> 2. Community & Other Projects
>>    - WWW search to provide additional pointers -- Greg
>>      -- Give pointers to datatracker and mailarchive
> 
> The www project got a lot of attention from me this month, with a release (v0.9.7) that moved the IESG statement to live under the IESG pages instead of with the blog pages.
> 
> The site also had some significant performance issues that took time to diagnose and address. While diagnosing, we identified several major changes that need to be made to the way the website currently serves blog pages. These are being tracked at https://github.com/ietf-tools/wagtail_website/issues (in particular issues 10 and 11) and will be addressed in upcoming releases. Greg will be entering several other requests (including analytics integration) as issues soon.

Re: Issue #11

I assume there are two sides to this.  First, the Wagtail side needs to stop making the queries, and second, the now extraneous APIs can be removed from the datatracker.  Is that right?

Russ