From nobody Mon Oct 1 06:26:54 2018 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 61605130DFA for ; Mon, 1 Oct 2018 06:26:52 -0700 (PDT) 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, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=rtfm-com.20150623.gappssmtp.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 BIOzChGhMwuq for ; Mon, 1 Oct 2018 06:26:49 -0700 (PDT) Received: from mail-lj1-x235.google.com (mail-lj1-x235.google.com [IPv6:2a00:1450:4864:20::235]) (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 986AB130DDC for ; Mon, 1 Oct 2018 06:26:48 -0700 (PDT) Received: by mail-lj1-x235.google.com with SMTP id 5-v6so12115372lju.6 for ; Mon, 01 Oct 2018 06:26:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=avObQeq535g+9jxQlOH/ssz6M2qPaAkgggUadLgAwD4=; b=ruLKZj9oGxi6RatUtnJlPqlJRoo8FntuxMOE82eLl5EfQQoq6f+GLJzh1OLh1gnxy0 ij7PKl6xy271DiNsHOS5XHAgYY7pYRvwgcPeEGhEazZ29iMWRRCBsGv+liAD25ceRTj4 NHsg/TNw++nKEm3HUDzKRYc7yuJSkHDt/hxIR+tFvIzdWDrPnlHbRxV4b8opnb2n8fDJ wUSzHW+QbuELnSkoG9D5Ab6pXXyJlqWTD6B47c6nWIGxlkF8G6sD8hyDV32eOYJ2GWFt bIWpffoZ73jnIzO3+d427hstGXOnoqCZJXhR6HuRQdr0SPdiV0fJ1q3pSnQQWgh5Zo75 2ddQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=avObQeq535g+9jxQlOH/ssz6M2qPaAkgggUadLgAwD4=; b=tS+Q+e/z3qQD049css9jaK03RgXVDDg4BDGtt5MbWIfmqkemOkS1bbluKScwv+s8IK vuMwC6M43fHndyqe6zoRF8yfPPy1f7PGGrLy9mYKFRcFgCzGEX8fX8509TeE0njGAJGE Mrx6oy8RNRN50wPoyD4c4BF2gd6XSt7FJ7DZo9/4EcCEFlCzWTNw56DlJJQmBsbOfhVr xrcy9XRptQaz1QNK0Rrh7hdOsJLktsmEdVhv7YMPejepydCuIM6XoGSQRXws6o8wqIqX 8r+Ex3HhWOuQvOamTNNz5gZ0HfcwDoLWMoMxZJ5vTBNQ1BJPh3thtEjNFZ1dy7Zd+gBr 2m6A== X-Gm-Message-State: ABuFfohAUABoPw1q/WMRaSgChcjuk373v0WKN66eyPy1+hP+QNmKnMKm +CAvqIyFUT9GydF6DkqG89gRq15RKSkb6HFBomiTPw== X-Google-Smtp-Source: ACcGV60g0QRuTwXFJEKI1v8iNlwXS/sbdNRIKYodY/yf7ZyYT1B12g36UwKzylbRVSzxFOVQhSn9IrYiNoZwMQ6Ld9w= X-Received: by 2002:a2e:544f:: with SMTP id y15-v6mr7064657ljd.51.1538400406758; Mon, 01 Oct 2018 06:26:46 -0700 (PDT) MIME-Version: 1.0 References: <974A500B-0BC8-4FE9-8A99-FAC23C139F95@vigilsec.com> In-Reply-To: <974A500B-0BC8-4FE9-8A99-FAC23C139F95@vigilsec.com> From: Eric Rescorla Date: Mon, 1 Oct 2018 06:26:09 -0700 Message-ID: To: Russ Housley Cc: tools-development@ietf.org Content-Type: multipart/alternative; boundary="000000000000c4777e05772ac1bc" Archived-At: Subject: Re: [TOOLS-DEVELOPMENT] Projects for 2019 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, 01 Oct 2018 13:26:52 -0000 --000000000000c4777e05772ac1bc Content-Type: text/plain; charset="UTF-8" Hi Russ, Do you think you could describe some of these in more detail? I've marked below the ones i don't recognize or wasn't able to infer... -Ekr On Sun, Sep 30, 2018 at 9:42 AM Russ Housley wrote: > This is the list of projects that came from a brainstorm session between > Robert and myself. Basically, we went through our notes and collected the > projects that were delayed since the RFC Format efforts consumed all of > this year's budget. Then, we divided the list into things that would best > be done by volunteers and things that would best be contracted. > > Volunteer Projects: > > 1 Improve GitHub tools for authors > 2 WG tracking of reviews > 3 Allow non-chairs to upload slides > 4 WG chair agenda support > > Contract Projects: > > 1 Rework the meeting scheduler > 2 Improvements to mail archive tool > 3 Wagtail and IETF website maintenance > 4 IANA expert review tracking *** > 5 Security review of RFC Editor toolsprior to open source > 6 EDU team materials *** > > 7 IRSG agenda and ballots > 8 Meetecho customization for IETF > *** > 9 Requirement for document review assistance > *** 10 Automatic agenda builder > *** > 11 Transition yangcatalog.org > > Thanks, > Russ > > _______________________________________________ > TOOLS-DEVELOPMENT mailing list > TOOLS-DEVELOPMENT@ietf.org > https://www.ietf.org/mailman/listinfo/tools-development > --000000000000c4777e05772ac1bc Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi Russ,

Do you think you co= uld describe some of these in more detail? I've marked below the ones i= don't recognize or wasn't able to infer...

-Ekr


= On Sun, Sep 30, 2018 at 9:42 AM Russ Housley <housley@vigilsec.com> wrote:
This is the list of projects that came from a brainstorm ses= sion between Robert and myself.=C2=A0 Basically, we went through our notes = and collected the projects that were delayed since the RFC Format efforts c= onsumed all of this year's budget.=C2=A0 Then, we divided the list into= things that would best be done by volunteers and things that would best be= contracted.

Volunteer Projects:

1=C2=A0 =C2=A0 =C2=A0 =C2=A0Improve GitHub tools for authors
2=C2=A0 =C2=A0 =C2=A0 =C2=A0WG tracking of reviews
3=C2=A0 =C2=A0 =C2=A0 =C2=A0Allow non-chairs to upload slides
4=C2=A0 =C2=A0 =C2=A0 =C2=A0WG chair agenda support

Contract Projects:

1=C2=A0 =C2=A0 =C2=A0 =C2=A0Rework the meeting scheduler=C2=A0 =C2=A0
2=C2=A0 =C2=A0 =C2=A0 =C2=A0Improvements to mail archive tool=C2=A0 =C2=A0 = =C2=A0 =C2=A0
3=C2=A0 =C2=A0 =C2=A0 =C2=A0Wagtail and IETF website maintenance=C2=A0 =C2= =A0
4=C2=A0 =C2=A0 =C2=A0 =C2=A0IANA expert review tracking=C2=A0 =C2=A0 =C2=A0=

***
=C2=A0=C2=A0 =C2=A0=C2= =A0
5=C2=A0 =C2=A0 =C2=A0 =C2=A0Security review of RFC Editor toolsprior to ope= n source
6=C2=A0 =C2=A0 =C2=A0 =C2=A0EDU team materials=C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0
***
=C2=A0
7=C2=A0 =C2=A0 =C2=A0 =C2=A0IRSG agenda and ballots=C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0
8=C2=A0 =C2=A0 =C2=A0 =C2=A0Meetecho customization for IETF
***
9=C2=A0 =C2=A0 =C2=A0 =C2=A0Requirement for document review assistance
<= /blockquote>
***

10=C2=A0 =C2=A0 =C2=A0 Automatic agenda builder
***
11=C2=A0 =C2=A0 =C2=A0 Transition yangcatalog.org

Thanks,
=C2=A0 Russ

_______________________________________________
TOOLS-DEVELOPMENT mailing list
TOOLS-DEVEL= OPMENT@ietf.org
https://www.ietf.org/mailman/listinfo/tools-d= evelopment
--000000000000c4777e05772ac1bc-- From nobody Mon Oct 1 08:52:52 2018 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 307EA130DD0 for ; Mon, 1 Oct 2018 08:52:50 -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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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 cyuzt1ZoGGw6 for ; Mon, 1 Oct 2018 08:52:47 -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 69147130E66 for ; Mon, 1 Oct 2018 08:52:47 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id 046F5300AA8 for ; Mon, 1 Oct 2018 11:52:45 -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 mbEEPUkfQS0w for ; Mon, 1 Oct 2018 11:52:43 -0400 (EDT) Received: from [10.25.1.79] (unknown [193.180.218.196]) by mail.smeinc.net (Postfix) with ESMTPSA id D45AC300425; Mon, 1 Oct 2018 11:52:42 -0400 (EDT) From: Russ Housley Message-Id: <4A304097-D016-4C79-B843-57B0EEF42106@vigilsec.com> Content-Type: multipart/alternative; boundary="Apple-Mail=_2D128BAB-F935-4F85-B1A3-4B990A3728DB" Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\)) Date: Mon, 1 Oct 2018 11:52:41 -0400 In-Reply-To: Cc: IETF Tools Development To: Eric Rescorla References: <974A500B-0BC8-4FE9-8A99-FAC23C139F95@vigilsec.com> X-Mailer: Apple Mail (2.3445.9.1) Archived-At: Subject: Re: [TOOLS-DEVELOPMENT] Projects for 2019 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, 01 Oct 2018 15:52:51 -0000 --Apple-Mail=_2D128BAB-F935-4F85-B1A3-4B990A3728DB Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii I hope the few sentences help ... Russ > On Oct 1, 2018, at 9:26 AM, Eric Rescorla wrote: >=20 > Hi Russ, >=20 > Do you think you could describe some of these in more detail? I've = marked below the ones i don't recognize or wasn't able to infer... >=20 > -Ekr >=20 >=20 > On Sun, Sep 30, 2018 at 9:42 AM Russ Housley > wrote: > This is the list of projects that came from a brainstorm session = between Robert and myself. Basically, we went through our notes and = collected the projects that were delayed since the RFC Format efforts = consumed all of this year's budget. Then, we divided the list into = things that would best be done by volunteers and things that would best = be contracted. >=20 > Volunteer Projects: >=20 > 1 Improve GitHub tools for authors > 2 WG tracking of reviews > 3 Allow non-chairs to upload slides > 4 WG chair agenda support >=20 > Contract Projects: >=20 > 1 Rework the meeting scheduler =20 > 2 Improvements to mail archive tool =20 > 3 Wagtail and IETF website maintenance =20 > 4 IANA expert review tracking =20 >=20 > *** Add capability to the Datatracker to know when a document needs IANA = Expert Review for a codepoint assignment. > =20 > 5 Security review of RFC Editor toolsprior to open source > 6 EDU team materials =20 > ***=20 EDU team materials posted in the Datatracker like other IETF meeting = sessions. > =20 > 7 IRSG agenda and ballots =20 > 8 Meetecho customization for IETF=20 > ***=20 About two years ago, we asked WG chairs what needed to be done to run = the meeting more smoothly and integrate the recordings in the = proceedings. It is time to follow up. Based on hallway discussions, = there are some ideas. > 9 Requirement for document review assistance > *** This is a requirements effort. Want to help WG chairs track who has = agreed to review a document, and the follow up. >=20 > 10 Automatic agenda builder > ***=20 Build a strawman IETF meeting agenda from the WG chair requests. It is = too manual today. Your recent feature request would be part of this = effort. > 11 Transition yangcatalog.org >=20 > Thanks, > Russ >=20 > _______________________________________________ > TOOLS-DEVELOPMENT mailing list > TOOLS-DEVELOPMENT@ietf.org > https://www.ietf.org/mailman/listinfo/tools-development = --Apple-Mail=_2D128BAB-F935-4F85-B1A3-4B990A3728DB Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii I = hope the few sentences help ...

Russ


On Oct = 1, 2018, at 9:26 AM, Eric Rescorla <ekr@rtfm.com> wrote:

Hi Russ,

Do you think you could describe some of = these in more detail? I've marked below the ones i don't recognize or = wasn't able to infer...

-Ekr


On = Sun, Sep 30, 2018 at 9:42 AM Russ Housley <housley@vigilsec.com> wrote:
This is the list of = projects that came from a brainstorm session between Robert and = myself.  Basically, we went through our notes and collected the = projects that were delayed since the RFC Format efforts consumed all of = this year's budget.  Then, we divided the list into things that = would best be done by volunteers and things that would best be = contracted.

Volunteer Projects:

1       Improve GitHub tools for authors
2       WG tracking of reviews
3       Allow non-chairs to upload slides
4       WG chair agenda support

Contract Projects:

1       Rework the meeting scheduler    =
2       Improvements to mail archive tool  =      
3       Wagtail and IETF website maintenance  =  
4       IANA expert review tracking    =  

***
Add capability to the Datatracker to know when a = document needs IANA Expert Review for a codepoint = assignment.

     
5       Security review of RFC Editor toolsprior to = open source
6       EDU team materials      =      
***

EDU team materials posted in the Datatracker like = other IETF meeting sessions.

 
7       IRSG agenda and ballots      =    
8       Meetecho customization for IETF
***

About two years ago, we asked WG chairs what needed to = be done to run the meeting more smoothly and integrate the recordings in = the proceedings.  It is time to follow up.  Based on hallway = discussions, there are some ideas.

9       Requirement for document review = assistance
***

This is a requirements effort.  Want to help WG = chairs track who has agreed to review a document, and the follow = up.


10      Automatic agenda builder
***

Build a strawman IETF meeting agenda from the WG chair = requests.  It is too manual today.  Your recent feature = request would be part of this effort.

11      Transition yangcatalog.org

Thanks,
  Russ

_______________________________________________
TOOLS-DEVELOPMENT mailing list
TOOLS-DEVELOPMENT@ietf.org
https://www.ietf.org/mailman/listinfo/tools-development

= --Apple-Mail=_2D128BAB-F935-4F85-B1A3-4B990A3728DB-- From nobody Mon Oct 1 10:10:33 2018 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 87329130E6C for ; Mon, 1 Oct 2018 10:10:31 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.377 X-Spam-Level: X-Spam-Status: No, score=-0.377 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, RCVD_IN_SORBS_WEB=1.5, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=no 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 Rl2VeVXRVxxD for ; Mon, 1 Oct 2018 10:10:29 -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 AEA09130DC2 for ; Mon, 1 Oct 2018 10:10:29 -0700 (PDT) Received: from [172.16.17.185] ([63.227.77.251]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id w91HASSq019149 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Mon, 1 Oct 2018 12:10:28 -0500 (CDT) (envelope-from rjsparks@nostrum.com) X-Authentication-Warning: raven.nostrum.com: Host [63.227.77.251] claimed to be [172.16.17.185] Content-Type: multipart/alternative; boundary=Apple-Mail-74CE851A-10C2-417D-B97A-362F684E6DCE Mime-Version: 1.0 (1.0) From: Robert Sparks X-Mailer: iPhone Mail (16A366) In-Reply-To: <4A304097-D016-4C79-B843-57B0EEF42106@vigilsec.com> Date: Mon, 1 Oct 2018 11:10:28 -0600 Cc: Eric Rescorla , IETF Tools Development Content-Transfer-Encoding: 7bit Message-Id: <2D75C378-6567-4641-B265-86F0CDFAFA83@nostrum.com> References: <974A500B-0BC8-4FE9-8A99-FAC23C139F95@vigilsec.com> <4A304097-D016-4C79-B843-57B0EEF42106@vigilsec.com> To: Russ Housley Archived-At: Subject: Re: [TOOLS-DEVELOPMENT] Projects for 2019 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, 01 Oct 2018 17:10:32 -0000 --Apple-Mail-74CE851A-10C2-417D-B97A-362F684E6DCE Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Sent from my iPhone > On Oct 1, 2018, at 9:52 AM, Russ Housley wrote: >=20 > I hope the few sentences help ... >=20 > Russ >=20 >=20 >> On Oct 1, 2018, at 9:26 AM, Eric Rescorla wrote: >>=20 >> Hi Russ, >>=20 >> Do you think you could describe some of these in more detail? I've marked= below the ones i don't recognize or wasn't able to infer... >>=20 >> -Ekr >>=20 >>=20 >>> On Sun, Sep 30, 2018 at 9:42 AM Russ Housley wrot= e: >>> This is the list of projects that came from a brainstorm session between= Robert and myself. Basically, we went through our notes and collected the p= rojects that were delayed since the RFC Format efforts consumed all of this y= ear's budget. Then, we divided the list into things that would best be done= by volunteers and things that would best be contracted. >>>=20 >>> Volunteer Projects: >>>=20 >>> 1 Improve GitHub tools for authors >>> 2 WG tracking of reviews >>> 3 Allow non-chairs to upload slides >>> 4 WG chair agenda support >>>=20 >>> Contract Projects: >>>=20 >>> 1 Rework the meeting scheduler =20 >>> 2 Improvements to mail archive tool =20 >>> 3 Wagtail and IETF website maintenance =20 >>> 4 IANA expert review tracking =20 >>=20 >> *** >=20 > Add capability to the Datatracker to know when a document needs IANA Exper= t Review for a codepoint assignment. And work with iana to determine how much they want to use the datatracker to= track/capture those reviews. There are some older tickets related to this. W= ill send links when i have more than my phone to work through.=20 >=20 >> =20 >>> 5 Security review of RFC Editor toolsprior to open source >>> 6 EDU team materials =20 >> ***=20 >=20 > EDU team materials posted in the Datatracker like other IETF meeting sessi= ons. We made an attempt a few years ago to build a single place for the edu team t= o store developed presentations and other materials. See https://datatracker= .ietf.org/group/edu. It hasnt been consistently used. It needs simplifying a= t least, and as Russ calls out, the workflow for ietf meetings probably need= s to closer match the wg workflow.=20 >=20 >>> =20 >>> 7 IRSG agenda and ballots =20 >>> 8 Meetecho customization for IETF=20 >> ***=20 >=20 > About two years ago, we asked WG chairs what needed to be done to run the m= eeting more smoothly and integrate the recordings in the proceedings. It is= time to follow up. Based on hallway discussions, there are some ideas. >=20 >>> 9 Requirement for document review assistance >> *** >=20 > This is a requirements effort. Want to help WG chairs track who has agree= d to review a document, and the follow up. >=20 >>=20 >>> 10 Automatic agenda builder >> ***=20 >=20 > Build a strawman IETF meeting agenda from the WG chair requests. It is to= o manual today. Your recent feature request would be part of this effort. >=20 >>> 11 Transition yangcatalog.org >>>=20 >>> Thanks, >>> Russ >>>=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-74CE851A-10C2-417D-B97A-362F684E6DCE Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable

Sent from my iPhone

On Oct 1, 2018, at 9:52 A= M, Russ Housley <housley@vigilsec= .com> wrote:

= = I hope the few sentences help ...

Russ


On Oct 1, 2018, at 9:26 AM, E= ric Rescorla <ekr@rtfm.com= > wrote:

Hi Russ,

Do you think you could describe some of thes= e in more detail? I've marked below the ones i don't recognize or wasn't abl= e to infer...

-Ekr=


On Sun, Sep 30, 2018 at 9:42 AM Russ Ho= usley <housley@vigilse= c.com> wrote:
This= is the list of projects that came from a brainstorm session between Robert a= nd myself.  Basically, we went through our notes and collected the proj= ects that were delayed since the RFC Format efforts consumed all of this yea= r's budget.  Then, we divided the list into things that would best be d= one by volunteers and things that would best be contracted.

Volunteer Projects:

1       Improve GitHub tools for authors
2       WG tracking of reviews
3       Allow non-chairs to upload slides
= 4       WG chair agenda support

Contract Projects:

1       Rework the meeting scheduler   
2       Improvements to mail archive tool    &= nbsp;  
3       Wagtail and IETF website maintenance   = ;
4       IANA expert review tracking      <= /blockquote>

***

Add ca= pability to the Datatracker to know when a document needs IANA Expert Review= for a codepoint assignment.And work with ian= a to determine how much they want to use the datatracker to track/capture th= ose reviews. There are some older tickets related to this. Will send links w= hen i have more than my phone to work through. 


     
=
5       Security review of RFC Editor toolsprior to open= source
6       EDU team materials        &n= bsp;  
***

EDU team materials posted= in the Datatracker like other IETF meeting sessions.

We made an attempt a few years ago to build a s= ingle place for the edu team to store developed presentations and other mate= rials. See https://datatr= acker.ietf.org/group/edu. It hasnt been consistently used. It needs simp= lifying at least, and as Russ calls out, the workflow for ietf meetings prob= ably needs to closer match the wg workflow. 

 
7       IRSG agenda and ballots      &nbs= p;  
8       Meetecho customization for IETF
<= /blockquote>
***

About two years ago, we asked WG chairs wh= at needed to be done to run the meeting more smoothly and integrate the reco= rdings in the proceedings.  It is time to follow up.  Based on hal= lway discussions, there are some ideas.

9       Requirement for document review assistance
***

This is a requirements effort.  Want to hel= p WG chairs track who has agreed to review a document, and the follow up.

=

10      Automatic agenda builder
<= div class=3D"">***
=
Build a strawman IETF meeting agenda from the WG chair r= equests.  It is too manual today.  Your recent feature request wou= ld be part of this effort.

11      Transition yangcatalog.org
=
Thanks,
  Russ

_______________________________________________
TOOLS-DEVELOPMENT mailing list
T= OOLS-DEVELOPMENT@ietf.org
https://www.ietf.org/mailman/listinf= o/tools-development

______________________________________= _________
TOOLS-DEVELOPMENT mailing list
TOOLS-DEVELOPMENT@ietf.org
https://www.ietf.org/mailman/listinfo/tools-development
<= /div>
= --Apple-Mail-74CE851A-10C2-417D-B97A-362F684E6DCE-- From nobody Sat Oct 6 10:37:34 2018 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 BBD35130E03 for ; Sat, 6 Oct 2018 10:37:32 -0700 (PDT) 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, RCVD_IN_DNSWL_NONE=-0.0001] 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 yEL9BPWbSmvV for ; Sat, 6 Oct 2018 10:37:30 -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 A2796130DEE for ; Sat, 6 Oct 2018 10:37:30 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id 6F27F300A51 for ; Sat, 6 Oct 2018 13:37:28 -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 ey38kl2Rw7SV for ; Sat, 6 Oct 2018 13:37:27 -0400 (EDT) Received: from new-host-2.home (pool-71-127-50-4.washdc.fios.verizon.net [71.127.50.4]) by mail.smeinc.net (Postfix) with ESMTPSA id 70EEA300425 for ; Sat, 6 Oct 2018 13:37:27 -0400 (EDT) From: Russ Housley Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\)) Message-Id: Date: Sat, 6 Oct 2018 13:37:28 -0400 To: IETF Tools Development X-Mailer: Apple Mail (2.3445.9.1) Archived-At: Subject: [TOOLS-DEVELOPMENT] Tools Call Agenda -- 9 October 2018 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: Sat, 06 Oct 2018 17:37:33 -0000 Tools Call Agenda -- 9 October 2018 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 -- http://trac.tools.ietf.org/tools/ietfdb/wiki/MergePlan - GDPR Compliance -- Robert and Henrik 2. Community & Other Projects - Discontinue MonArch email archives -- Robert and Ryan 3. RFC Services Projects - RFC Format Contracts -- Heather and Robert -- IDnits -- Publication Formatter -- Text Submission -- RFClint -- SVGcheck -- XMLdiff 4. Server Infrastructure - IESG discussions of DMARC -- Henrik and Alexey -- Is there any status on ARC? - Is the IESG ready for non-ASCII I-Ds? -- Alexey 5. YANG Catalog - Feature additions -- Eric 6. Parking Lot - Prepare the RFC Production Center code for publication 7. AOB From nobody Sun Oct 7 09:03:21 2018 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 991C3127133 for ; Sun, 7 Oct 2018 09:03:19 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -14.956 X-Spam-Level: X-Spam-Status: No, score=-14.956 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.456, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=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 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 PznVlGvJnNhO for ; Sun, 7 Oct 2018 09:03:17 -0700 (PDT) Received: from alln-iport-2.cisco.com (alln-iport-2.cisco.com [173.37.142.89]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7D7BE124C04 for ; Sun, 7 Oct 2018 09:03:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2730; q=dns/txt; s=iport; t=1538928197; x=1540137797; h=from:to:subject:date:message-id:references:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=DDIytt2l3zfbFPDkjj78GheqXhXRmaULA7Pb7f4XD3s=; b=CS9wzjopyIBgt+BXo7n83u4t+hZCUYuvcN6cXU42jQGCZdRBx1OeXVyD 6vms9r7Lm179C0L08ShII3h2491syHKV3gPD5YyWv07Ky+CZoq45tvhlW SzNGFFi9FSUKi6rZSjINZjd93HrJY1/omy7SbKcwLt55dS1w119eQ5gl1 s=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AUAADZLbpb/4kNJK1IFwMaAQEBAQE?= =?us-ascii?q?CAQEBAQcCAQEBAYFTAwEBAQELAYIFZn8oCoNqlD2BaJcOFIFmCwEBGA2ERwI?= =?us-ascii?q?XhBghNgsNAQMBAQIBAQJtHAyFOgIBAwEBIREyCBkCAgEIGgIQBAwGAgICGQw?= =?us-ascii?q?LFQ8BAgEDARIUgw0BggEPNKMtgS6DP4E4hRMFgQaKLheBQT+BEicME4IeLoF?= =?us-ascii?q?BgU8LAQECGIELBAUBEgEJByYKJgiCCycxggsbAoo+kzAJAoZMiXsXghmCJIs?= =?us-ascii?q?6gl2JS4kjAhEUgSUkATBkcXAVOyoBgkEJgh0MC4Engh+FFIU+bwGLDxWBCoE?= =?us-ascii?q?fAQE?= X-IronPort-AV: E=Sophos;i="5.54,353,1534809600"; d="scan'208";a="182410130" Received: from alln-core-4.cisco.com ([173.36.13.137]) by alln-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 07 Oct 2018 16:03:16 +0000 Received: from XCH-RTP-013.cisco.com (xch-rtp-013.cisco.com [64.101.220.153]) by alln-core-4.cisco.com (8.15.2/8.15.2) with ESMTPS id w97G3G2O013828 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Sun, 7 Oct 2018 16:03:16 GMT Received: from xch-rtp-015.cisco.com (64.101.220.155) by XCH-RTP-013.cisco.com (64.101.220.153) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Sun, 7 Oct 2018 12:03:15 -0400 Received: from xch-rtp-015.cisco.com ([64.101.220.155]) by XCH-RTP-015.cisco.com ([64.101.220.155]) with mapi id 15.00.1395.000; Sun, 7 Oct 2018 12:03:15 -0400 From: "Eric Vyncke (evyncke)" To: Russ Housley , IETF Tools Development Thread-Topic: [TOOLS-DEVELOPMENT] Tools Call Agenda -- 9 October 2018 at 1:00 Eastern Thread-Index: AQHUXZtGBqw/aYqm0UGzsFNvskmld6UUV98A Date: Sun, 7 Oct 2018 16:03:15 +0000 Message-ID: <9BA9069F-6CDE-4587-B015-7E088B23A18E@cisco.com> References: In-Reply-To: Accept-Language: fr-FR, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/10.e.1.180613 x-ms-exchange-messagesentrepresentingtype: 1 x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [10.55.56.4] Content-Type: text/plain; charset="utf-8" Content-ID: <2EAB90B4EF92C14384537D7303AABD5C@emea.cisco.com> Content-Transfer-Encoding: base64 MIME-Version: 1.0 X-Outbound-SMTP-Client: 64.101.220.153, xch-rtp-013.cisco.com X-Outbound-Node: alln-core-4.cisco.com Archived-At: Subject: Re: [TOOLS-DEVELOPMENT] Tools Call Agenda -- 9 October 2018 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: Sun, 07 Oct 2018 16:03:20 -0000 RGVhciBhbGwsDQoNCkkgYW0gYWZyYWlkIHRoYXQgZm9yIG15IGZpcnN0IHBhcnRpY2lwYXRpb24g aW4gdGhpcyBtb250aGx5IGNhbGwsIEkgd2lsbCBiZSBpbiBhIGhpZ2ggc3BlZWQgdHJhaW4gYmV0 d2VlbiBQYXJpcyAmIEJlbGdpdW0uIFNvbWV0aW1lcyBtb2JpbGUgY29tbXVuaWNhdGlvbiBhcmUg bm90IHRoYXQgZ29vZCA6LSggc28gZG8gbm90IGJlIHN1cnByaXNlZCBpZiBJIGFtIHNpbGVudC4N Cg0KVGFsayB0byB5b3UgbmV4dCB3ZWVrDQoNCi3DqXJpYw0KDQrvu79PbiAwNi8xMC8yMDE4LCAx OTozNywgIlRPT0xTLURFVkVMT1BNRU5UIG9uIGJlaGFsZiBvZiBSdXNzIEhvdXNsZXkiIDx0b29s cy1kZXZlbG9wbWVudC1ib3VuY2VzQGlldGYub3JnIG9uIGJlaGFsZiBvZiBob3VzbGV5QHZpZ2ls c2VjLmNvbT4gd3JvdGU6DQoNCiAgICBUb29scyBDYWxsIEFnZW5kYSAtLSA5IE9jdG9iZXIgMjAx OCBhdCAxOjAwIEVhc3Rlcm4NCiAgICANCiAgICANCiAgICBKT0lOIFdFQkVYIE1FRVRJTkcNCiAg ICBodHRwczovL2lldGYud2ViZXguY29tL2lldGYvai5waHA/TVRJRD1tNDQwZGQ4NDg3MjYzMzlj MDNlNjA1Yjk5NTZlMzhiYWMNCiAgICBNZWV0aW5nIG51bWJlciAoYWNjZXNzIGNvZGUpOiA2NDAg MTAzIDU3MA0KICAgIE1lZXRpbmcgcGFzc3dvcmQ6IHRvb2xzDQogICAgDQogICAgSk9JTiBCWSBQ SE9ORQ0KICAgIDEtODc3LTY2OC00NDkzIENhbGwtaW4gdG9sbCBmcmVlIG51bWJlciAoVVMvQ2Fu YWRhKSANCiAgICAxLTY1MC00NzktMzIwOCBDYWxsLWluIHRvbGwgbnVtYmVyIChVUy9DYW5hZGEp DQogICAgTWVldGluZyBudW1iZXIgKGFjY2VzcyBjb2RlKTogNjQwIDEwMyA1NzANCiAgICBNZWV0 aW5nIHBhc3N3b3JkOiB0b29scw0KICAgIA0KICAgIA0KICAgIDEuIERhdGF0cmFja2VyIFByb2pl Y3RzDQogICAgICAgLSBFeHBlY3RlZCBEYXRhdHJhY2tlciBSZWxlYXNlcyAtLSBSb2JlcnQgYW5k IEhlbnJpaw0KICAgICAgICAgLS0gaHR0cDovL3RyYWMudG9vbHMuaWV0Zi5vcmcvdG9vbHMvaWV0 ZmRiL3dpa2kvTWVyZ2VQbGFuDQogICAgICAgLSBHRFBSIENvbXBsaWFuY2UgLS0gUm9iZXJ0IGFu ZCBIZW5yaWsNCiAgICANCiAgICAyLiBDb21tdW5pdHkgJiBPdGhlciBQcm9qZWN0cw0KICAgICAg IC0gRGlzY29udGludWUgTW9uQXJjaCBlbWFpbCBhcmNoaXZlcyAtLSBSb2JlcnQgYW5kIFJ5YW4N CiAgICANCiAgICAzLiBSRkMgU2VydmljZXMgUHJvamVjdHMNCiAgICAgICAtIFJGQyBGb3JtYXQg Q29udHJhY3RzIC0tIEhlYXRoZXIgYW5kIFJvYmVydA0KICAgICAgICAgLS0gSURuaXRzDQogICAg ICAgICAtLSBQdWJsaWNhdGlvbiBGb3JtYXR0ZXINCiAgICAgICAgIC0tIFRleHQgU3VibWlzc2lv bg0KICAgICAgICAgLS0gUkZDbGludA0KICAgICAgICAgLS0gU1ZHY2hlY2sNCiAgICAgICAgIC0t IFhNTGRpZmYNCiAgICANCiAgICA0LiBTZXJ2ZXIgSW5mcmFzdHJ1Y3R1cmUNCiAgICAgICAtIElF U0cgZGlzY3Vzc2lvbnMgb2YgRE1BUkMgLS0gSGVucmlrIGFuZCBBbGV4ZXkNCiAgICAgICAgIC0t IElzIHRoZXJlIGFueSBzdGF0dXMgb24gQVJDPw0KICAgICAgIC0gSXMgdGhlIElFU0cgcmVhZHkg Zm9yIG5vbi1BU0NJSSBJLURzPyAtLSBBbGV4ZXkNCiAgICANCiAgICA1LiBZQU5HIENhdGFsb2cN CiAgICAgICAtIEZlYXR1cmUgYWRkaXRpb25zIC0tIEVyaWMNCiAgICANCiAgICA2LiBQYXJraW5n IExvdA0KICAgICAgIC0gUHJlcGFyZSB0aGUgUkZDIFByb2R1Y3Rpb24gQ2VudGVyIGNvZGUgZm9y IHB1YmxpY2F0aW9uDQogICAgDQogICAgNy4gQU9CDQogICAgDQogICAgX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCiAgICBUT09MUy1ERVZFTE9QTUVOVCBt YWlsaW5nIGxpc3QNCiAgICBUT09MUy1ERVZFTE9QTUVOVEBpZXRmLm9yZw0KICAgIGh0dHBzOi8v d3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vdG9vbHMtZGV2ZWxvcG1lbnQNCiAgICANCg0K From nobody Mon Oct 8 13:00:54 2018 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 40A8B130F67 for ; Mon, 8 Oct 2018 13:00:52 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.88 X-Spam-Level: X-Spam-Status: No, score=-1.88 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01] 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 NiOidRKKPtyU for ; Mon, 8 Oct 2018 13:00:50 -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 0E355130F5E for ; Mon, 8 Oct 2018 13:00:49 -0700 (PDT) Received: from unescapeable.local ([47.186.18.66]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id w98K0l5L006480 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for ; Mon, 8 Oct 2018 15:00:48 -0500 (CDT) (envelope-from rjsparks@nostrum.com) X-Authentication-Warning: raven.nostrum.com: Host [47.186.18.66] claimed to be unescapeable.local To: tools-development@ietf.org References: From: Robert Sparks Message-ID: <3450d120-f53c-1335-93a5-b7b550daf8d2@nostrum.com> Date: Mon, 8 Oct 2018 15:00:47 -0500 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 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] Tools Call Agenda -- 9 October 2018 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, 08 Oct 2018 20:00:53 -0000 Some notes. On 10/6/18 12:37 PM, Russ Housley wrote: > Tools Call Agenda -- 9 October 2018 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 > -- http://trac.tools.ietf.org/tools/ietfdb/wiki/MergePlan > - GDPR Compliance -- Robert and Henrik The Plan and MergePlan are updated. I don't believe we have anything upcoming that will be surprising or need extra coordination. > > 2. Community & Other Projects > - Discontinue MonArch email archives -- Robert and Ryan I sent the message we worked on here to the community last week. The responses so far have been positive,  and it generated a new feature request. Should we forward what went to ietf-announce to wg-chairs? > > 3. RFC Services Projects > - RFC Format Contracts -- Heather and Robert > -- IDnits > -- Publication Formatter > -- Text Submission > -- RFClint > -- SVGcheck > -- XMLdiff All on target - I don't think we have anything new to discuss here. > > 4. Server Infrastructure > - IESG discussions of DMARC -- Henrik and Alexey > -- Is there any status on ARC? > - Is the IESG ready for non-ASCII I-Ds? -- Alexey > > 5. YANG Catalog > - Feature additions -- Eric There are a few different things here we should track in our discussions: a) Development of new functionality (Feature additions as above). Eric is helping to gather the list of items we can turn into an SoW for that. b) Transitioning operation of the current yangcatalog to the secretariat.     - Eric hopes we could do this by the end of the year, but if we need to fund more development to facilitate the transition, it will have to wait for 2019 funds. c) Moving to a tools-team-driven maintenance model for the yangcatalog. > > 6. Parking Lot > - Prepare the RFC Production Center code for publication > > 7. AOB Could we, probably early in the call, talk briefly about the upcoming project list? > > _______________________________________________ > TOOLS-DEVELOPMENT mailing list > TOOLS-DEVELOPMENT@ietf.org > https://www.ietf.org/mailman/listinfo/tools-development From nobody Mon Oct 8 13:12:20 2018 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 3439E130FED for ; Mon, 8 Oct 2018 13:12:19 -0700 (PDT) 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 l3oABM7StrQ3 for ; Mon, 8 Oct 2018 13:12:17 -0700 (PDT) Received: from zinfandel.tools.ietf.org (zinfandel.tools.ietf.org [IPv6:2001:1890:126c::1:2a]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7E5AD130FCE for ; Mon, 8 Oct 2018 13:12:17 -0700 (PDT) Received: from h-37-140.a357.priv.bahnhof.se ([94.254.37.140]:52140 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 1g9bt2-0002Uu-Ma; Mon, 08 Oct 2018 13:12:17 -0700 To: Robert Sparks , tools-development@ietf.org References: <3450d120-f53c-1335-93a5-b7b550daf8d2@nostrum.com> From: Henrik Levkowetz Message-ID: Date: Mon, 8 Oct 2018 22:12:09 +0200 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: <3450d120-f53c-1335-93a5-b7b550daf8d2@nostrum.com> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="eiC7TQlIBoQTFsc416BouDbBSIXR9UqWv" X-SA-Exim-Connect-IP: 94.254.37.140 X-SA-Exim-Rcpt-To: tools-development@ietf.org, rjsparks@nostrum.com 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] Tools Call Agenda -- 9 October 2018 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, 08 Oct 2018 20:12:19 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --eiC7TQlIBoQTFsc416BouDbBSIXR9UqWv Content-Type: multipart/mixed; boundary="LgUgC8jWNbwiXnhG6HC4n85ugee7RqBJ5"; protected-headers="v1" From: Henrik Levkowetz To: Robert Sparks , tools-development@ietf.org Message-ID: Subject: Re: [TOOLS-DEVELOPMENT] Tools Call Agenda -- 9 October 2018 at 1:00 Eastern References: <3450d120-f53c-1335-93a5-b7b550daf8d2@nostrum.com> In-Reply-To: <3450d120-f53c-1335-93a5-b7b550daf8d2@nostrum.com> --LgUgC8jWNbwiXnhG6HC4n85ugee7RqBJ5 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable A few additional notes: On 2018-10-08 22:00, Robert Sparks wrote: > Some notes. >=20 >=20 > On 10/6/18 12:37 PM, Russ Housley wrote: >> Tools Call Agenda -- 9 October 2018 at 1:00 Eastern >> >> >> JOIN WEBEX MEETING >> https://ietf.webex.com/ietf/j.php?MTID=3Dm440dd848726339c03e605b9956e3= 8bac >> 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 >> -- http://trac.tools.ietf.org/tools/ietfdb/wiki/MergePlan >> - GDPR Compliance -- Robert and Henrik > The Plan and MergePlan are updated. I don't believe we have anything=20 > upcoming that will be surprising or need extra coordination. I concur. Some details: Some work has been done on the group features branch, but tweaks and bugfixes related to the GDPR mailings, Login handling, and NomCom tools have delayed this. A new tool to read email delivery messages and deactivate email addresses with permanent failures has been released and used to handle bounces from the GDPR consent request mailings. Consent request email requests have been sent out, initial round plus 2 reminders; the last one today (Monday). Data removal is scheduled for the 22nd. Henrik >> >> 2. Community & Other Projects >> - Discontinue MonArch email archives -- Robert and Ryan > I sent the message we worked on here to the community last week. The=20 > responses so far have been positive, and it generated a new feature=20 > request. >=20 > Should we forward what went to ietf-announce to wg-chairs? >> >> 3. RFC Services Projects >> - RFC Format Contracts -- Heather and Robert >> -- IDnits >> -- Publication Formatter >> -- Text Submission >> -- RFClint >> -- SVGcheck >> -- XMLdiff > All on target - I don't think we have anything new to discuss here. >> >> 4. Server Infrastructure >> - IESG discussions of DMARC -- Henrik and Alexey >> -- Is there any status on ARC? >> - Is the IESG ready for non-ASCII I-Ds? -- Alexey >> >> 5. YANG Catalog >> - Feature additions -- Eric > There are a few different things here we should track in our discussion= s: >=20 > a) Development of new functionality (Feature additions as above). Eric = > is helping to gather the list of items we can turn into an SoW for that= =2E >=20 > b) Transitioning operation of the current yangcatalog to the secretaria= t. > - Eric hopes we could do this by the end of the year, but if we=20 > need to fund more development to facilitate the transition, it will hav= e=20 > to wait for 2019 funds. >=20 > c) Moving to a tools-team-driven maintenance model for the yangcatalog.= >=20 >> >> 6. Parking Lot >> - Prepare the RFC Production Center code for publication >> >> 7. AOB > Could we, probably early in the call, talk briefly about the upcoming=20 > project list? >> >> _______________________________________________ >> 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 >=20 --LgUgC8jWNbwiXnhG6HC4n85ugee7RqBJ5-- --eiC7TQlIBoQTFsc416BouDbBSIXR9UqWv Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEifjc5+rnL1MJBcZSTptXS4+7FxoFAlu7uhkACgkQTptXS4+7 FxqgjBAAxpFJ/QBr6XfIW3mt8YXPG7n291cMbCeL1IB4oh3AcCIpYllJj2HXASq/ AGmVctvJjimNaNlAnREk4hKJaPqSB8bt7kfmNKyzE6WZ/TwOPjHBBw2btEggBAlt JOxPbEECX1XYR/NwQmsDWF3G38g3AiT6pRhLcIr204b7gV5eNONGzaKZr98FDvRC tPBhBo8GVQCHgJyRe1FXL2kuaHjdLK6fKfJ+tRlueZM/8SUk2IF4mUBTiMISZkYF FVgv1J5I4JN3yQxFwft1vt8IHb3BiJ13XBJmNdYEMskSZzxzabGod0DnFMx9d6xe RZodnMC88IbETAWtZVwjj4uKRiOHl10mt4O190pH1N2VOeQuwAGToG2jU8oEZr9e oYGLO8m09+g9CLSwUAl35GIbvu/L+xdW+AiyaoTt8Afbse+84KApPRTHbWFKsGuq M8DGvJzON7LgYXUlITBxxsHmSp4tVnXR8aFhn6r1WYFnB6gRKfQPE8rThJiHbeZI EogxuReUjpOxQUAoEXl2+5PTbx+QahQkz26eIvm0/hVoXVZae0aYSmoBlPq5Yt4G chOWzF+ezLAK2eYZddeLfwhS1zkJw2xu+dmb0fo8VzbszVW8+DMmRfuE58SFgkUO /RmzdGaRv6GFOAKYajTOyz9Q9b0RBA47dk7QdyVsqqzPmIEYdS0= =J7Eh -----END PGP SIGNATURE----- --eiC7TQlIBoQTFsc416BouDbBSIXR9UqWv-- From nobody Mon Oct 8 23:39:04 2018 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 2596B1311AD for ; Mon, 8 Oct 2018 23:39:03 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -14.956 X-Spam-Level: X-Spam-Status: No, score=-14.956 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.456, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=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 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 u87Avhxzkb5m for ; Mon, 8 Oct 2018 23:39:00 -0700 (PDT) Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7246513118E for ; Mon, 8 Oct 2018 23:38:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4382; q=dns/txt; s=iport; t=1539067137; x=1540276737; h=from:to:subject:date:message-id:references:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=1h4WwFn62v0cVAbryZ7x0ACrJFs3UMq63jHch6Oft5M=; b=VIgA356Lzic3HV+DdTU3pw1D5Injd8wiipAfz+4gMhZq7H+N6biUDVWb kNvWAehB1aFTVpyg2uUyn+s8xmSvlAmX3xwms/0yv2bZWBkpZ+vf3p0Ce /5rgXJ54i1ciZH/bq5P22XWut2419m9solR/DX+53EFbX/7ICe3ZxzKD6 4=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AGAAC5TLxb/5RdJa1jGQEBAQEBAQE?= =?us-ascii?q?BAQEBAQcBAQEBAQGBUgMBAQEBAQsBggVmfygKg2uURoINlmkUgWYLAQEYC4R?= =?us-ascii?q?JAheELiE1DA0BAwEBAgEBAm0cDIU5AQEBAQIBAQEhES0NGwIBCA4KAgIRFQI?= =?us-ascii?q?CAiULFRACBAESgyEBgXkID6I3EYEigS6Ed4UdBYELii4XgUE/gTkfgh4ugUG?= =?us-ascii?q?BWgEBgRwvFhcogkIxgiYCiQOBO5MyCQKGTYl7F497gl6JS4klAhEUgSUfATW?= =?us-ascii?q?BVXAVOyoBgkGCMoNRhRSFPm+LSoEfAQE?= X-IronPort-AV: E=Sophos;i="5.54,359,1534809600"; d="scan'208";a="463556108" Received: from rcdn-core-12.cisco.com ([173.37.93.148]) by rcdn-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 09 Oct 2018 06:38:34 +0000 Received: from XCH-RTP-012.cisco.com (xch-rtp-012.cisco.com [64.101.220.152]) by rcdn-core-12.cisco.com (8.15.2/8.15.2) with ESMTPS id w996cYfJ024613 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 9 Oct 2018 06:38:34 GMT Received: from xch-rtp-015.cisco.com (64.101.220.155) by XCH-RTP-012.cisco.com (64.101.220.152) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Tue, 9 Oct 2018 02:38:33 -0400 Received: from xch-rtp-015.cisco.com ([64.101.220.155]) by XCH-RTP-015.cisco.com ([64.101.220.155]) with mapi id 15.00.1395.000; Tue, 9 Oct 2018 02:38:33 -0400 From: "Eric Vyncke (evyncke)" To: Robert Sparks , "tools-development@ietf.org" Thread-Topic: [TOOLS-DEVELOPMENT] Tools Call Agenda -- 9 October 2018 at 1:00 Eastern Thread-Index: AQHUXZtGBqw/aYqm0UGzsFNvskmld6UWCwyAgADTtYA= Date: Tue, 9 Oct 2018 06:38:33 +0000 Message-ID: References: <3450d120-f53c-1335-93a5-b7b550daf8d2@nostrum.com> In-Reply-To: <3450d120-f53c-1335-93a5-b7b550daf8d2@nostrum.com> Accept-Language: fr-FR, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/10.e.1.180613 x-ms-exchange-messagesentrepresentingtype: 1 x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [10.61.66.84] Content-Type: text/plain; charset="utf-8" Content-ID: <1BB1D43A8D2E4947AC2BD67EEED49A7A@emea.cisco.com> Content-Transfer-Encoding: base64 MIME-Version: 1.0 X-Outbound-SMTP-Client: 64.101.220.152, xch-rtp-012.cisco.com X-Outbound-Node: rcdn-core-12.cisco.com Archived-At: Subject: Re: [TOOLS-DEVELOPMENT] Tools Call Agenda -- 9 October 2018 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, 09 Oct 2018 06:39:03 -0000 QXMgSSB3aWxsIGJlIGluIHRoZSBUaGFseXMgdHJhaW4gZHVyaW5nIHRoZSBjYWxsOiBubyBndWFy YW50ZWUgdG8gaGF2ZSBhIGRlY2VudCBwaG9uZSBjYWxsIGV2ZW4gaWYgSSB3aWxsIHRyeS4NCg0K U29tZSBub3RlcyBwcmVmaXhlZCB3aXRoIEVWPg0KDQrvu79PbiAwOC8xMC8yMDE4LCAyMjowMSwg IlRPT0xTLURFVkVMT1BNRU5UIG9uIGJlaGFsZiBvZiBSb2JlcnQgU3BhcmtzIiA8dG9vbHMtZGV2 ZWxvcG1lbnQtYm91bmNlc0BpZXRmLm9yZyBvbiBiZWhhbGYgb2YgcmpzcGFya3NAbm9zdHJ1bS5j b20+IHdyb3RlOg0KICAgID4gNS4gWUFORyBDYXRhbG9nDQoNCkVWPiBTdGF0dXMgb2YgaHR0cHM6 Ly93d3cueWFuZ2NhdGFsb2cub3JnIG5vdyBvdmVyIElQdjYgOy0pIGJ1dCBtb3JlIGltcG9ydGFu dCBubyBtb3JlIFNRTGl0ZSBvciBQSFAgKGV4Y2VwdCBvbmUgcmVtYWluaW5nIHBhZ2UpLCBldmVy eXRoaW5nIGlzIFB5dGhvbiAmIE15U1FMICYgRGphbmdvICYgVVdTR0kuIFN0YXJ0LXVwIHByb2Nl ZHVyZXMgYXJlIGF1dG9tYXRpYywgc28sIHRoZSBzZXJ2ZXIgaGFzIGJlY29tZSAnZWFzeSB0byBv cGVyYXRlJy4gQWxsIGNvZGUgaXMgYXQ6IGh0dHBzOi8vZ2l0aHViLmNvbS9ZYW5nQ2F0YWxvZyB3 aXRoIEFwYWNoZSAyIGxpY2Vuc2UuIFRoZXJlIGFyZSBzdGlsbCBvbmUgb3IgdHdvIGJ1Z3MgYmVp bmcgaXJvbmVkIG91dCBieSB0aGUgY29udHJhY3RvciBQYW50aGVvbi4NCg0KRVY+IFRoZXJlIGFy ZSB0d28gYXBwbGljYXRpb25zIGZyb20gQ2lzY28gd2hpY2ggYXJlIG5vdCBvcGVuIHNvdXJjZToN Ci0gQ29uZkQgKGV4IHRhaWwtZikgUHJlbWl1bSB3aGljaCBpcyBjcml0aWNhbCBhcyBhbGwgdGhl IGRhdGEgaXMgc3RvcmVkIGluIGl0cyBlbmdpbmUgYW5kIE5FVENPTkYgaXMgdXNlZCBieSBzb21l IFNETyB0byB1cGxvYWQvbW9kaWZ5IFlBTkcgbW9kZWxzLiBUaGUgUHJvZHVjdCBNYW5hZ2VyIG9m IHRoaXMgdG9vbCBoYXMgYWdyZWVkIHRvIGdyYW50IElFVEYgYSBmcmVlIGV2YWx1YXRpb24gbGlj ZW5zZSBvZiBvbmUgeWVhciB3aXRoIGltcGxpY2l0IGFuZCBhdXRvbWF0aWMgcmVuZXdhbC4NCi0g WWFuZ1N1aXRlIHdoaWNoIGlzIGEgdXNlZnVsIGJ1dCBub3QgY3JpdGljYWwgYWRkaXRpb24gdG8g eWFuZ2NhdGFsb2csIGl0IGlzIGF0IGh0dHBzOi8veXMueWFuZ2NhdGFsb2cub3JnIEkgYW0gc3Rp bGwgaW4gZGlzY3Vzc2lvbiB3aXRoIHRoZSB0ZWFtIHRvIGhhdmUgaXQgZWl0aGVyIG9wZW4gc291 cmNlZCBvciBoYXZlIGEgZnJlZSBsaWNlbnNlIGZvciB0aGUgSUVURi4NCg0KRVY+IFRoZSBzZXJ2 ZXIgYWxzbyB1c2VzIFl1bWF3b3JrcyB0b29sIHlhbmdkdW1wLXBybyB0byBjaGVjayB0aGUgdmFs aWRpdHkgb2YgYWxsIHVwbG9hZGVkIFlBTkcgbW9kZWxzIChpbiBhZGRpdGlvbiB0byBvdGhlciBj b21waWxlcnMgc3VjaCBhcyB0aGUgb3BlbiBzb3VyY2UgcHlhbmcgb2YgbGlieWFuZykuIFRoaXMg U3VtbWVyLCBZdW1hd29ya3MgaGFzIGFncmVlZCB0byBoYXZlIGEgZnJlZSBkb3dubG9hZCBhY2Nv dW50IGZvciBJRVRGIChvZiBjb3Vyc2Ugd2Ugd2lsbCBuZWVkIHRvIHB1dCB5b3UgaW4gZGlyZWN0 IHRvdWNoIHdpdGggdGhlbSkNCg0KICAgID4gICAgIC0gRmVhdHVyZSBhZGRpdGlvbnMgLS0gRXJp Yw0KICAgIFRoZXJlIGFyZSBhIGZldyBkaWZmZXJlbnQgdGhpbmdzIGhlcmUgd2Ugc2hvdWxkIHRy YWNrIGluIG91ciBkaXNjdXNzaW9uczoNCiAgICANCiAgICBhKSBEZXZlbG9wbWVudCBvZiBuZXcg ZnVuY3Rpb25hbGl0eSAoRmVhdHVyZSBhZGRpdGlvbnMgYXMgYWJvdmUpLiBFcmljIA0KICAgIGlz IGhlbHBpbmcgdG8gZ2F0aGVyIHRoZSBsaXN0IG9mIGl0ZW1zIHdlIGNhbiB0dXJuIGludG8gYW4g U29XIGZvciB0aGF0Lg0KDQpFVj4gYWdyZWVkDQogICAgDQogICAgYikgVHJhbnNpdGlvbmluZyBv cGVyYXRpb24gb2YgdGhlIGN1cnJlbnQgeWFuZ2NhdGFsb2cgdG8gdGhlIHNlY3JldGFyaWF0Lg0K ICAgICAgICAgLSBFcmljIGhvcGVzIHdlIGNvdWxkIGRvIHRoaXMgYnkgdGhlIGVuZCBvZiB0aGUg eWVhciwgYnV0IGlmIHdlIA0KICAgIG5lZWQgdG8gZnVuZCBtb3JlIGRldmVsb3BtZW50IHRvIGZh Y2lsaXRhdGUgdGhlIHRyYW5zaXRpb24sIGl0IHdpbGwgaGF2ZSANCiAgICB0byB3YWl0IGZvciAy MDE5IGZ1bmRzLg0KDQpFVj4gdGhlcmUgc2hvdWxkIGJlIG5vIG1vcmUgZGV2ZWxvcG1lbnQgdG8g bWFrZSB0aGUgdHJhbnNpdGlvbiBidXQgaXQgd2lsbCB0YWtlIHNvbWUgaG91cnMgb2YgbXlzZWxm IGFuZCBzb21lb25lIGZyb20gdGhlIHNlY3JldGFyaWF0IEkgYW0gYWZyYWlkLg0KDQogICAgYykg TW92aW5nIHRvIGEgdG9vbHMtdGVhbS1kcml2ZW4gbWFpbnRlbmFuY2UgbW9kZWwgZm9yIHRoZSB5 YW5nY2F0YWxvZy4NCg0KRVY+IGl0IHdvdWxkIGJlIG5pY2UgaW5kZWVkLiBJdCBjdXJyZW50bHkg cnVucyBvbiBVYnVudHUgMTguMDQsIDMwIEdCIFJBTSAodHlwaWNhbCB1c2UgMjUgR0IpLCAyMDAg R0IgU1NEICh1c2VkIGF0IDE3JSksIDggY29yZXMgKHVzZWQgYXQgMjAlIHBlZWsgYW5kIHdlIGFy ZSBkb2luZyBtaWdyYXRpb24vdGVzdCkNCiAgDQogICAgPg0KICAgID4gNi4gUGFya2luZyBMb3QN CiAgICA+ICAgICAtIFByZXBhcmUgdGhlIFJGQyBQcm9kdWN0aW9uIENlbnRlciBjb2RlIGZvciBw dWJsaWNhdGlvbg0KICAgID4NCiAgICA+IDcuIEFPQg0KICAgIENvdWxkIHdlLCBwcm9iYWJseSBl YXJseSBpbiB0aGUgY2FsbCwgdGFsayBicmllZmx5IGFib3V0IHRoZSB1cGNvbWluZyANCiAgICBw cm9qZWN0IGxpc3Q/DQogICAgPg0KICAgID4gX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX18NCiAgICA+IFRPT0xTLURFVkVMT1BNRU5UIG1haWxpbmcgbGlzdA0K ICAgID4gVE9PTFMtREVWRUxPUE1FTlRAaWV0Zi5vcmcNCiAgICA+IGh0dHBzOi8vd3d3LmlldGYu b3JnL21haWxtYW4vbGlzdGluZm8vdG9vbHMtZGV2ZWxvcG1lbnQNCiAgICANCiAgICBfX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KICAgIFRPT0xTLURFVkVM T1BNRU5UIG1haWxpbmcgbGlzdA0KICAgIFRPT0xTLURFVkVMT1BNRU5UQGlldGYub3JnDQogICAg aHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby90b29scy1kZXZlbG9wbWVudA0K ICAgIA0KDQo= From nobody Fri Oct 12 07:47:21 2018 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 C3C5D130E22 for ; Fri, 12 Oct 2018 07:47:19 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.88 X-Spam-Level: X-Spam-Status: No, score=-1.88 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01] 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 Q4pC95qgmtPT for ; Fri, 12 Oct 2018 07:47:17 -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 8444C130DCB for ; Fri, 12 Oct 2018 07:47:17 -0700 (PDT) Received: from unescapeable.local ([47.186.18.66]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id w9CElGTs003178 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for ; Fri, 12 Oct 2018 09:47:17 -0500 (CDT) (envelope-from rjsparks@nostrum.com) X-Authentication-Warning: raven.nostrum.com: Host [47.186.18.66] claimed to be unescapeable.local To: tools-development@ietf.org References: <974A500B-0BC8-4FE9-8A99-FAC23C139F95@vigilsec.com> <4A304097-D016-4C79-B843-57B0EEF42106@vigilsec.com> <2D75C378-6567-4641-B265-86F0CDFAFA83@nostrum.com> From: Robert Sparks Message-ID: <06b06cb7-d2e8-b978-0b3f-01a8093ab854@nostrum.com> Date: Fri, 12 Oct 2018 09:47:16 -0500 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: <2D75C378-6567-4641-B265-86F0CDFAFA83@nostrum.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US Archived-At: Subject: Re: [TOOLS-DEVELOPMENT] Projects for 2019 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, 12 Oct 2018 14:47:20 -0000 As discussed on this weeks call, here is a version of the list we've been discussing with a short description for each contract project. The descriptions are informational, and intended only to assist with early prioritization. They are not comprehensive. Each project will begin with the development of a statement of work that would define the project more precisely. These are listed in priority order in each section (the contract and volunteer sections are independent). ====================== - Contract Projects:     - Rework the meeting scheduler         The agenda editing tool will benefit from updates to improve         the appearance and efficiency of the editor. Options for         scheduling need to be more flexible than the current grid         allows.     - Transition operation of yangcatalog.org       to the secretariat         The recent push has the yangcatalog in a state that is easy to         deploy. This project will initially identify and execute any         additional development needed to allow the secretariat to take         over operations. (At this time, little to no additional         development is anticipated, though options about deployment         technologies need to be considered).     - Develop yangcatalog.org features         Develop features have been deferred while working to get the         catalog into a state that can be operated by the secretariat.         Éric and Benoit are gathering a list of those features.     - Improvements to mail archive tool         This will focus initially on addressing any issues we have         related to discontinuing Mhonarc, and then address requested         enhancements.     - Wagtail and IETF website maintenance         There are shortcomings with the functionality of the website         at the moment (such as allowing plain text files to be served         easily), and with installation of updates.     - IANA expert review tracking         Work with IANA to determine what datatracker features would         help identify which drafts have content needing expert review,         and how the datatracker could help with tracking the progress         of those reviews.     - Security review of RFC Editor toolsprior to open source         We plan to move the RFC Editor’s tools source to an open         repository. Before doing so, we need to review the code for         security vulnerabilities and adjust as necessary.     - EDU team materials         The Edu team manages materials used at, and sometimes between,         IETF meetings, such as the Newcomer’s training decks. The         “Materials” tab added to the datatracker view of the edu team         (https://datatracker.ietf.org/group/edu/materials/) was added         to help manage these materials, but has proven difficult for         the team to use. This project will work with the team to         identify a better mechanism (in the datatracker, or         elsewhere).     - IRSG agenda and ballots         The IRSG would like to have a balloting system similar to the         IESGs, and views to manage documents currently under ballot.         See     - Meetecho customization for IETF         We have a backlog of features WG chairs have requested to run         the meeting more smoothly. We have identified items needed to         integrate the recordings in the proceedings.     - Build requirements for document review assistance         There have been periodic requests to build or find a system         that would allow in-place markup of a draft for review, and to         track resolution of comments made in that markup. This project         would work with the community to develop a set of requirements         for one or more ways to provide that functionality.     - Automatic agenda builder         The initial agenda used going into the conflict-resolution         call is currently generated by hand. We started an effort with         the last major improvement to the scheduling system to compute         one or more good starting places. This project would revisit         that idea. - Volunteer Projects:     - Transition ongoing maintenance of yangcatalog.org to the Tools team     - Improve GitHub tools for authors     - Allow non-chairs to upload slides     - Allow Working Groups to track volunteer and assigned reviews, possibly      reusing the tooling created for the directorates.     - Provide tools to help working groups build meeting agendas (such as       tracking agenda time requests, assisting with materials links, and       building initial agenda text). From nobody Mon Oct 15 08:08:02 2018 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 D4552128BAC for ; Mon, 15 Oct 2018 08:08:00 -0700 (PDT) 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, RCVD_IN_DNSWL_NONE=-0.0001] 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 6hA34A-43pxF for ; Mon, 15 Oct 2018 08:07:59 -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 B97CC130E7E for ; Mon, 15 Oct 2018 08:07:59 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id 735CA300A91 for ; Mon, 15 Oct 2018 11:07:57 -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 EYwB1ln-h63l for ; Mon, 15 Oct 2018 11:07:56 -0400 (EDT) Received: from a860b60074bd.home (pool-71-127-50-4.washdc.fios.verizon.net [71.127.50.4]) by mail.smeinc.net (Postfix) with ESMTPSA id C42DE300580 for ; Mon, 15 Oct 2018 11:07:56 -0400 (EDT) From: Russ Housley Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\)) Message-Id: <8678E40F-F846-48E5-A927-7AE513155572@vigilsec.com> Date: Mon, 15 Oct 2018 11:07:57 -0400 To: IETF Tools Development X-Mailer: Apple Mail (2.3445.9.1) Archived-At: Subject: [TOOLS-DEVELOPMENT] Calendar Server 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, 15 Oct 2018 15:08:01 -0000 We did a calendar server experiment a few years ago. I recall that we = set up a calendar for a few WGs, and then we found that they were not = used enough to set up one for each WG. I think the server is still in = place for leadership groups. The IoT Directorate has need for a = calendar. Would it be hard to add a calendar for them? Russ From nobody Mon Oct 15 08:13:38 2018 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 B4418130EB8 for ; Mon, 15 Oct 2018 08:13:30 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.2 X-Spam-Level: X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-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 AiUxwgQBQhcL for ; Mon, 15 Oct 2018 08:13:29 -0700 (PDT) Received: from mail.amsl.com (c8a.amsl.com [4.31.198.40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7B412130E84 for ; Mon, 15 Oct 2018 08:13:29 -0700 (PDT) Received: from mail.amsl.com (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTPS id A9E771D06DE for ; Mon, 15 Oct 2018 08:12:58 -0700 (PDT) Received: from mail-io1-f50.google.com (mail-io1-f50.google.com [209.85.166.50]) by c8a.amsl.com (Postfix) with ESMTPSA id 875911D06DB for ; Mon, 15 Oct 2018 08:12:58 -0700 (PDT) Received: by mail-io1-f50.google.com with SMTP id n18-v6so14484452ioa.9 for ; Mon, 15 Oct 2018 08:13:29 -0700 (PDT) X-Gm-Message-State: ABuFfojxhuyAjQZhyDOi+YhFiqgdJXBbaTiQOItCfhqijNL6Rlt3mMYa 6PHE2OJQWW47TyfHUP7m+17D5+65qIdGX/SADkg= X-Google-Smtp-Source: ACcGV60qsZFAdpmjVtCe6X1IgSftDmCXdHE76yXvmnitcf6Lg5Bz8RepUrb5mJIrn5fAz9NBZol15r9gWtsrj9NCGeM= X-Received: by 2002:a6b:254:: with SMTP id 81-v6mr11101103ioc.183.1539616408573; Mon, 15 Oct 2018 08:13:28 -0700 (PDT) MIME-Version: 1.0 References: <8678E40F-F846-48E5-A927-7AE513155572@vigilsec.com> In-Reply-To: <8678E40F-F846-48E5-A927-7AE513155572@vigilsec.com> From: Glen Date: Mon, 15 Oct 2018 08:13:15 -0700 X-Gmail-Original-Message-ID: Message-ID: To: tools-development@ietf.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Archived-At: Subject: Re: [TOOLS-DEVELOPMENT] Calendar Server 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, 15 Oct 2018 15:13:38 -0000 Hi Russ - On Mon, Oct 15, 2018 at 8:08 AM Russ Housley wrote: > We did a calendar server experiment a few years ago. I recall that we se= t up a calendar for a few WGs, and then we found that they were not used en= ough to set up one for each WG. I think the server is still in place for l= eadership groups. The IoT Directorate has need for a calendar. Would it b= e hard to add a calendar for them? The old actual "calendar server" died a painful and well-deserved death some time ago. What we have now is a webdav-based scenario where an individual manager can publish a calendar from their Mac to the IETF web server in such a way that others can subscribe to it as though it were a calendar feed. There can be only one manager, the primary calendar must live on their Mac, the IETF server acts only as a reflector feed. If this will suit, then please have the IOT director contact Matt Larson , copying Alexa Morris and they will get it set up for the individual caretaker. Glen From nobody Mon Oct 15 08:16:37 2018 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 6CF4A130E84 for ; Mon, 15 Oct 2018 08:16:35 -0700 (PDT) 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, RCVD_IN_DNSWL_NONE=-0.0001, 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 ZS-2PFg2gG1o for ; Mon, 15 Oct 2018 08:16:32 -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 72DDF130E5D for ; Mon, 15 Oct 2018 08:16:32 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id 5BC0A300A98 for ; Mon, 15 Oct 2018 11:16:30 -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 LNuBuYvcJJ2w for ; Mon, 15 Oct 2018 11:16:29 -0400 (EDT) Received: from a860b60074bd.home (pool-71-127-50-4.washdc.fios.verizon.net [71.127.50.4]) by mail.smeinc.net (Postfix) with ESMTPSA id 0FC7F300580; Mon, 15 Oct 2018 11:16:28 -0400 (EDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\)) From: Russ Housley In-Reply-To: Date: Mon, 15 Oct 2018 11:16:29 -0400 Cc: IETF Tools Development Content-Transfer-Encoding: quoted-printable Message-Id: <0B0D013C-D015-4C03-8471-555F13A5772A@vigilsec.com> References: <8678E40F-F846-48E5-A927-7AE513155572@vigilsec.com> To: Glen Barney X-Mailer: Apple Mail (2.3445.9.1) Archived-At: Subject: Re: [TOOLS-DEVELOPMENT] Calendar Server 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, 15 Oct 2018 15:16:35 -0000 > On Oct 15, 2018, at 11:13 AM, Glen wrote: >=20 > Hi Russ - >=20 > On Mon, Oct 15, 2018 at 8:08 AM Russ Housley = wrote: >> We did a calendar server experiment a few years ago. I recall that = we set up a calendar for a few WGs, and then we found that they were not = used enough to set up one for each WG. I think the server is still in = place for leadership groups. The IoT Directorate has need for a = calendar. Would it be hard to add a calendar for them? >=20 > The old actual "calendar server" died a painful and well-deserved > death some time ago. What we have now is a webdav-based scenario > where an individual manager can publish a calendar from their Mac to > the IETF web server in such a way that others can subscribe to it as > though it were a calendar feed. There can be only one manager, the > primary calendar must live on their Mac, the IETF server acts only as > a reflector feed. >=20 > If this will suit, then please have the IOT director contact Matt > Larson , copying Alexa Morris and > they will get it set up for the individual caretaker. Thanks. I'll find out if this will work. Russ From nobody Mon Oct 15 16:35:13 2018 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 69A5B120072 for ; Mon, 15 Oct 2018 16:35:11 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.2 X-Spam-Level: X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-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 w9KQUHqPSf6h for ; Mon, 15 Oct 2018 16:35:09 -0700 (PDT) Received: from mail.amsl.com (c8a.amsl.com [4.31.198.40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DA7D1130E23 for ; Mon, 15 Oct 2018 16:35:09 -0700 (PDT) Received: from mail.amsl.com (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTPS id 811B61D06DD for ; Mon, 15 Oct 2018 16:34:38 -0700 (PDT) Received: from mail-it1-f173.google.com (mail-it1-f173.google.com [209.85.166.173]) by c8a.amsl.com (Postfix) with ESMTPSA id 5BB8E1D06DB for ; Mon, 15 Oct 2018 16:34:38 -0700 (PDT) Received: by mail-it1-f173.google.com with SMTP id c85-v6so7717955itd.1 for ; Mon, 15 Oct 2018 16:35:09 -0700 (PDT) X-Gm-Message-State: ABuFfogbDDsS5Cr4xYgddlKAjBqZzlNvmxMHHrXVPVk8SV8E0HrF7suu WqRMEfULqIFTlHBsnTVqewHv894A07K+UUFVtgQ= X-Google-Smtp-Source: ACcGV60aHgrspDP3ObGxMMC5XHGGuT4HkRh77XwNGtSxZ30/fE7TBGjm3Lu9WVpraEu8mtkMhgke33dQhVowK1ouSLE= X-Received: by 2002:a24:94d:: with SMTP id 74-v6mr13682707itm.178.1539646508956; Mon, 15 Oct 2018 16:35:08 -0700 (PDT) MIME-Version: 1.0 From: Glen Date: Mon, 15 Oct 2018 16:34:54 -0700 X-Gmail-Original-Message-ID: Message-ID: To: tools-development@ietf.org Content-Type: text/plain; charset="UTF-8" Archived-At: Subject: [TOOLS-DEVELOPMENT] The latest round of spam 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, 15 Oct 2018 23:35:11 -0000 Hi Tools Team - So the latest round of IETF spam consists of a bot which forges email from an @ietf.org address, to that same @ietf.org address, claiming that the "account has been hacked", that the user has been video recorded, and demanding a bribe of bitcoin to make the video go away rather than being shown to all of the user's relatives. I'm sure that "Mr. Copyright-questions@ietf.org" would be horrified. Needless to say, it's just junk spam. I added some rules to filter on bitcoin phrases, in the hope that that would solve the issue. Of course, at AMS, I have all legitimate AMS addresses blocked, so that only their users (with authentication) can send from those addresses. But, in the IETF, because of the way some of our legacy tools work, and some of our interconnections between lists and tools, some of these send-from addresses are not only not blocked, but actually whitelisted in spam tables, making such forgeries easy. I can of course block sending from these addresses, and/or unwhitelist them, but when I've done so in the past it has caused legitimate email from tools and systems to be blocked and/or to fail. So - low priority - but perhaps at some point in the near future we should inventory all of our tools, and review how each one sends email, and determine if we really even still need some of them (*cough* *coughANNOUNCEMENTTOOLcough*), and figure out how better to allow people and tools to send email while more effectively blocking forgeries from the outside world. And two postscripts to the above: #1. I sent this email on Saturday, just after adding the rules. My email at the time listed the specific phrases I had added to the blacklist. Because there were multiple phrases, spamassassin scored up my own email so high that it got rejected and never made it to the list. Ha ha! I am now resending this email to you two days later. #2. Improbably, a thread on the MLS list talking about a certain technique said that the technique was used in "Bitcoin Wallets" - which caused a couple of replies sent after my rules were added to also get rejected. I've removed that particular rule from the collection, and asked list members to resend any additional email. Don't even get me started on cryptocurrency. All of my savings are in Dogecoin. Glen -- Glen Barney IT Director AMS (IETF Secretariat) From nobody Wed Oct 24 09:06:46 2018 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 7637E130F5E for ; Wed, 24 Oct 2018 09:06:41 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.88 X-Spam-Level: X-Spam-Status: No, score=-1.88 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01] 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 IlGLGJQCx2gN for ; Wed, 24 Oct 2018 09:06:38 -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 47AEA130EE0 for ; Wed, 24 Oct 2018 09:06:38 -0700 (PDT) Received: from unescapeable.local ([47.186.18.66]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id w9OG6bqo023947 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for ; Wed, 24 Oct 2018 11:06:37 -0500 (CDT) (envelope-from rjsparks@nostrum.com) X-Authentication-Warning: raven.nostrum.com: Host [47.186.18.66] claimed to be unescapeable.local To: IETF Tools Development From: Robert Sparks Message-ID: Date: Wed, 24 Oct 2018 11:06:36 -0500 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US Archived-At: Subject: [TOOLS-DEVELOPMENT] Outline of tasks for improving the meeting scheduling tool. 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, 24 Oct 2018 16:06:45 -0000 All - Below is an outline of the things that need to improve with the meeting scheduling tool. Please skim and let me know if there are any big items that you think are missing. Please comment where I call out open questions. The primary TODO below is to identify and name the types of things we are currently lumping in as "non-session sessions". I hope to use a few brainstorming sessions in Bangkok to build that set of things. This is not, of course, in the form we would use for an SoW - prose needs to be created. But before building that, I want to make sure we're targeting the right things. ---- - Improve scheduling working/research group sessions     - Working with an individual schedule         - Use bootstrap to display the agenda edit page             - Remove the broken “show/hide” navigation mechanic (see the [>] button in the upper left).             - Reduce the real-estate taken by the “You must save” and “Save as” dialogs (#1429)             - Open Question: Remove the ability to slide days around? The secretariat is not using it.             - Consider removing the ability to hide a room or a day (and the [show all] button with it. The secretariat is not using it.             - Rendered HTML is currently invalid - result should pass HTML validator checks.             - Javascript is currently putting a lot of debugging information on the browser console                 - Logging should either be removed or make the log levels selectable         - Restructure the communication with between the browser and the server to be more efficient.             - The current implementation makes several hundred requests for information about individual sessions, groups, their needed resources, and their conflicts. A single combined request would be more efficient.         - Make it easier to see AD conflicts on the grid - the secretariat has to do this manually right now.         - Must-be-present doesn’t show on the grid at all. The secretariat feels the data is not well groomed enough for it to be useful if it showed (there is concern about knot knowing who these people are well enough to make judgement calls on whether the declared conflict is really reasonable).         - Make it possible to swap two entire columns on the drag-drop view (e.g. switch Wed and Tue morning). The secretariat does this frequently while building a schedule, sometimes while on the conflict-resolution call. It currently requires many drag-drop options to the unscheduled field, and is error prone.         - Make groups that are in slots that don’t match their requested time more visually distinct (#1428)         - Greying out sessions by area should work whether you own an agenda or not (#1584)         - If a session is moved after the agenda is finalized, the agenda view should show something in the old time slot pointing to the new time slot.             - Add a SessionStatusName of ‘rescheduled’. When a session is moved after the agenda is finalized, create a new session with the original SchedTimeSessAssignment, and place it in status 'rescheduled'.             - Open Question: Is this WG/RG session specific? Should this happen to private meetings that are rescheduled?     - Working with the set of schedules         - Add a way to track changes to a schedule. Needs to be easier to remember what’s different between two versions             - The typical workflow is to copy a schedule and make a few changes             - Add a history that captures changes to a given schedule.                 - If this uses events, it will be different from SchedulingEvents. These need to be aware of changes to SchedTimeSessAssignment for a given schedule.             - Open Question: Should we provide a diff between two schedules?         - Add notes describing a version.             - The name field isn’t big enough to be descriptive, and it is created before the description is really known.             - Saving a new copy with a shorter descriptive name just makes clutter.         - Page at /meeting/103/agendas/list can be made more useful             - Consider grouping by (visible, public)             - The Edit button does not take the user to a place to edit the schedule - the resulting form is for changing the name of the schedule, deleting it, making it official, or changing it’s (visible, public) status. The presentation should be more self-documenting.             - The notes describing versions should be available here (at least in summary). These notes should be searchable. - Improve setting up a new meeting     - Setting up a new meeting is currently inefficient - normally repeating things are scheduled on the wrong day (probably a bug introduced when we started starting meetings on Saturday). Copying things forward from previous meetings is not working as expected. Currently the secretariat has to do a lot of deletes/adds when setting up the new schedule.     - The current workflow is to add things that should be the same across all agendas (like breaks and registrations sessions) to the “Empty” agenda. Concrete proposed schedules start by making a copy of the “Empty” agenda. Unfortunately, if the breaks or registration sessions need to change after some concrete schedules have been started, those changes have to be manually made to each copy.     - Create a base schedule that all schedules inherit from         -  Things like breaks and registration would live in the base schedule         - Changes to this base schedule would affect all schedules immediately.         - Make sessions from the base schedule visually distinct wherever such sessions are shown graphically, such as /meeting/103/room-view - Improve the ability to schedule meetings that are not WG meetings     - The non-session concept is overused, and talking about non-session sessions is counterintuitive. A redesign of the objects to give the non-session things usefully conceptual names is needed. Views that talk about “non-session” need to be updated to speak in terms of what they are actually working with.         - Some of these things have materials, like ANRW and hotrfc         - TODO: Describe each of the things and give them names     - Improve the flexibility of the grid         - Allow rooms to have different grids         - It’s currently expected that WG/RG session rooms would all share the same grid, and sessions of other types would be scheduled in rooms with a different grid. Thus, the drag-drop views don’t need to support mixed grids at the moment, but care should be taken with the code anticipating that we would need to support them in the future.         - /meeting/timeslots/edit, in particular, will need adjustment to handle rooms having different grids.             - Possibly group rooms that share a common grid structure.     - Make it easy to control what types of sessions do and dont appear on the official agenda page.     - Allow graphical scheduling of non-wg sessions         - Open Question: Choose between these options         - Option 1             - Create a separate page similar to the WG/RG drag and drop.         - Option 2             - Allow graphical scheduling and rescheduling of non rg/wg sessions directly on /meeting/room-view             - Consider helper links from /by-type and /by-room to assist with finding and moving sessions.     - Consider adding views that show “Isoc meetings” or “Private meetings” where we have room-view etc now, or perhaps leverage the customized agenda view - letting the secretariat select whether they see things on that view. - Improve session request handling     - There were three groups at 103 that listed themselves as first order conflicts. The form needs stricter validation.         - Groups can’t list themselves as conflicts         - Closed WGs or Bofs can’t be listed as conflicts     - Lots of requests list groups that are closed, or bofs that have passed.     - The secretariat expresses concern about the quality of the group conflict data and the must-be-present data. Should we change the tooling to make it more likely the lists get maintained? (The IESG would need to make this decision). - Improve meeting statistics     - There is currently a manually created report for the IESG that summarizes the number of sessions requested per area, and the number of requests of each length (per area). This can be automated.     - Add a view reachable from the session-request pages (e.g. meeting/requests) that produces that summary.     - Add graphs. Allow showing one meeting or a comparison against recent/all meetings.     - Allow the user to view the reports/graphs showing what was “requested” and what “actually met”. - Improve testing     - All the javascript needs automated testing - Improve the community’s view of the agenda     - Modify the week-view in the agenda to allow selection/deselection of the ‘non-wg’ events (codesprint, systers lunch, etc).     - Modify the week-view custom urls to use a query string rather than a fragment list. (Apps use fragments for other things too). Calendar subscriptions should still work. Consider having a browser cookie available to store preferences between meetings (see #1991)     - Add an “All Bofs” customization button (#2314). Consider also an “All newcomers” or “running code” groups.     - Add an important date ics feed.  There is a manually created important dates calendar on the ietf website currently.         - Possibly include important dates in the upcoming meeting calendar.     - Reduce the granularity of IETF meetings in the “Upcoming meetings” ics.         - Possibly allow selectors to only show IETF meetings where group “foo” has a session         - See #2605 and #2216 - Improve materials handling for interims     - Allow uploading of recordings for interims (#2471, #2467) - Code-base cleanup     - Code has a mix of “schedule” and “agenda” in it. Picking one and converting would be better.     - A session object currently has a ‘scheduled’ datetime attribute that records the time that the object first enters the ‘sched’ state. This should be replaced with a relation to a new event class: SchedulingEvent, that records all status transitions. - New Bugs     - Inactive address chosen when saving an agenda - 2611     - When creating non-session items, setting location often doesn’t stick. Sometimes it takes multiple saves to get it to work.     - Groups populate incorrectly on an empty schedule - the non-session screen display is broken. Stephanie will show Ryan and develop a more detailed report. From nobody Thu Oct 25 11:31:46 2018 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 5593C130E3A for ; Thu, 25 Oct 2018 11:31:45 -0700 (PDT) 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, RCVD_IN_DNSWL_NONE=-0.0001, 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 3KmCQvhLSiYk for ; Thu, 25 Oct 2018 11:31:42 -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 6BF54128A6E for ; Thu, 25 Oct 2018 11:31:42 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id C2746300AB0 for ; Thu, 25 Oct 2018 14:25:43 -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 Pby_Hapxe0FL for ; Thu, 25 Oct 2018 14:25:41 -0400 (EDT) Received: from [5.5.33.36] (vpn.snozzages.com [204.42.252.17]) by mail.smeinc.net (Postfix) with ESMTPSA id E8661300A48; Thu, 25 Oct 2018 14:25:40 -0400 (EDT) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\)) From: Russ Housley In-Reply-To: Date: Thu, 25 Oct 2018 14:25:34 -0400 Cc: IETF Tools Development Content-Transfer-Encoding: quoted-printable Message-Id: References: To: Robert Sparks X-Mailer: Apple Mail (2.3445.9.1) Archived-At: Subject: Re: [TOOLS-DEVELOPMENT] Outline of tasks for improving the meeting scheduling tool. 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, 25 Oct 2018 18:31:45 -0000 We used to have the concept of a meeting template. Templates had names. = In this write-up, you talk about a "base schedule". I cannot tell if = they are the same. Russ > On Oct 24, 2018, at 12:06 PM, Robert Sparks = wrote: >=20 > All - >=20 > Below is an outline of the things that need to improve with the = meeting scheduling tool. Please skim and let me know if there are any = big items that you think are missing. Please comment where I call out = open questions. The primary TODO below is to identify and name the types = of things we are currently lumping in as "non-session sessions". I hope = to use a few brainstorming sessions in Bangkok to build that set of = things. This is not, of course, in the form we would use for an SoW - = prose needs to be created. But before building that, I want to make sure = we're targeting the right things. >=20 > ---- >=20 >=20 > - Improve scheduling working/research group sessions > - Working with an individual schedule > - Use bootstrap to display the agenda edit page > - Remove the broken =E2=80=9Cshow/hide=E2=80=9D navigation = mechanic (see the [>] button in the upper left). > - Reduce the real-estate taken by the =E2=80=9CYou must = save=E2=80=9D and =E2=80=9CSave as=E2=80=9D dialogs (#1429) > - Open Question: Remove the ability to slide days around? = The secretariat is not using it. > - Consider removing the ability to hide a room or a day = (and the [show all] button with it. The secretariat is not using it. > - Rendered HTML is currently invalid - result should pass = HTML validator checks. > - Javascript is currently putting a lot of debugging = information on the browser console > - Logging should either be removed or make the log = levels selectable > - Restructure the communication with between the browser and = the server to be more efficient. > - The current implementation makes several hundred requests = for information about individual sessions, groups, their needed = resources, and their conflicts. A single combined request would be more = efficient. > - Make it easier to see AD conflicts on the grid - the = secretariat has to do this manually right now. > - Must-be-present doesn=E2=80=99t show on the grid at all. The = secretariat feels the data is not well groomed enough for it to be = useful if it showed (there is concern about knot knowing who these = people are well enough to make judgement calls on whether the declared = conflict is really reasonable). > - Make it possible to swap two entire columns on the drag-drop = view (e.g. switch Wed and Tue morning). The secretariat does this = frequently while building a schedule, sometimes while on the = conflict-resolution call. It currently requires many drag-drop options = to the unscheduled field, and is error prone. > - Make groups that are in slots that don=E2=80=99t match their = requested time more visually distinct (#1428) > - Greying out sessions by area should work whether you own an = agenda or not (#1584) > - If a session is moved after the agenda is finalized, the = agenda view should show something in the old time slot pointing to the = new time slot. > - Add a SessionStatusName of =E2=80=98rescheduled=E2=80=99. = When a session is moved after the agenda is finalized, create a new = session with the original SchedTimeSessAssignment, and place it in = status 'rescheduled'. > - Open Question: Is this WG/RG session specific? Should = this happen to private meetings that are rescheduled? > - Working with the set of schedules > - Add a way to track changes to a schedule. Needs to be easier = to remember what=E2=80=99s different between two versions > - The typical workflow is to copy a schedule and make a few = changes > - Add a history that captures changes to a given schedule. > - If this uses events, it will be different from = SchedulingEvents. These need to be aware of changes to = SchedTimeSessAssignment for a given schedule. > - Open Question: Should we provide a diff between two = schedules? > - Add notes describing a version. > - The name field isn=E2=80=99t big enough to be = descriptive, and it is created before the description is really known. > - Saving a new copy with a shorter descriptive name just = makes clutter. > - Page at /meeting/103/agendas/list can be made more useful > - Consider grouping by (visible, public) > - The Edit button does not take the user to a place to edit = the schedule - the resulting form is for changing the name of the = schedule, deleting it, making it official, or changing it=E2=80=99s = (visible, public) status. The presentation should be more = self-documenting. > - The notes describing versions should be available here = (at least in summary). These notes should be searchable. > - Improve setting up a new meeting > - Setting up a new meeting is currently inefficient - normally = repeating things are scheduled on the wrong day (probably a bug = introduced when we started starting meetings on Saturday). Copying = things forward from previous meetings is not working as expected. = Currently the secretariat has to do a lot of deletes/adds when setting = up the new schedule. > - The current workflow is to add things that should be the same = across all agendas (like breaks and registrations sessions) to the = =E2=80=9CEmpty=E2=80=9D agenda. Concrete proposed schedules start by = making a copy of the =E2=80=9CEmpty=E2=80=9D agenda. Unfortunately, if = the breaks or registration sessions need to change after some concrete = schedules have been started, those changes have to be manually made to = each copy. > - Create a base schedule that all schedules inherit from > - Things like breaks and registration would live in the base = schedule > - Changes to this base schedule would affect all schedules = immediately. > - Make sessions from the base schedule visually distinct = wherever such sessions are shown graphically, such as = /meeting/103/room-view > - Improve the ability to schedule meetings that are not WG meetings > - The non-session concept is overused, and talking about = non-session sessions is counterintuitive. A redesign of the objects to = give the non-session things usefully conceptual names is needed. Views = that talk about =E2=80=9Cnon-session=E2=80=9D need to be updated to = speak in terms of what they are actually working with. > - Some of these things have materials, like ANRW and hotrfc > - TODO: Describe each of the things and give them names > - Improve the flexibility of the grid > - Allow rooms to have different grids > - It=E2=80=99s currently expected that WG/RG session rooms = would all share the same grid, and sessions of other types would be = scheduled in rooms with a different grid. Thus, the drag-drop views = don=E2=80=99t need to support mixed grids at the moment, but care should = be taken with the code anticipating that we would need to support them = in the future. > - /meeting/timeslots/edit, in particular, will need adjustment = to handle rooms having different grids. > - Possibly group rooms that share a common grid structure. > - Make it easy to control what types of sessions do and dont appear = on the official agenda page. > - Allow graphical scheduling of non-wg sessions > - Open Question: Choose between these options > - Option 1 > - Create a separate page similar to the WG/RG drag and = drop. > - Option 2 > - Allow graphical scheduling and rescheduling of non rg/wg = sessions directly on /meeting/room-view > - Consider helper links from /by-type and /by-room to = assist with finding and moving sessions. > - Consider adding views that show =E2=80=9CIsoc meetings=E2=80=9D = or =E2=80=9CPrivate meetings=E2=80=9D where we have room-view etc now, = or perhaps leverage the customized agenda view - letting the secretariat = select whether they see things on that view. > - Improve session request handling > - There were three groups at 103 that listed themselves as first = order conflicts. The form needs stricter validation. > - Groups can=E2=80=99t list themselves as conflicts > - Closed WGs or Bofs can=E2=80=99t be listed as conflicts > - Lots of requests list groups that are closed, or bofs that have = passed. > - The secretariat expresses concern about the quality of the group = conflict data and the must-be-present data. Should we change the tooling = to make it more likely the lists get maintained? (The IESG would need to = make this decision). > - Improve meeting statistics > - There is currently a manually created report for the IESG that = summarizes the number of sessions requested per area, and the number of = requests of each length (per area). This can be automated. > - Add a view reachable from the session-request pages (e.g. = meeting/requests) that produces that summary. > - Add graphs. Allow showing one meeting or a comparison against = recent/all meetings. > - Allow the user to view the reports/graphs showing what was = =E2=80=9Crequested=E2=80=9D and what =E2=80=9Cactually met=E2=80=9D. > - Improve testing > - All the javascript needs automated testing > - Improve the community=E2=80=99s view of the agenda > - Modify the week-view in the agenda to allow selection/deselection = of the =E2=80=98non-wg=E2=80=99 events (codesprint, systers lunch, etc). > - Modify the week-view custom urls to use a query string rather = than a fragment list. (Apps use fragments for other things too). = Calendar subscriptions should still work. Consider having a browser = cookie available to store preferences between meetings (see #1991) > - Add an =E2=80=9CAll Bofs=E2=80=9D customization button (#2314). = Consider also an =E2=80=9CAll newcomers=E2=80=9D or =E2=80=9Crunning = code=E2=80=9D groups. > - Add an important date ics feed. There is a manually created = important dates calendar on the ietf website currently. > - Possibly include important dates in the upcoming meeting = calendar. > - Reduce the granularity of IETF meetings in the =E2=80=9CUpcoming = meetings=E2=80=9D ics. > - Possibly allow selectors to only show IETF meetings where = group =E2=80=9Cfoo=E2=80=9D has a session > - See #2605 and #2216 > - Improve materials handling for interims > - Allow uploading of recordings for interims (#2471, #2467) > - Code-base cleanup > - Code has a mix of =E2=80=9Cschedule=E2=80=9D and =E2=80=9Cagenda=E2= =80=9D in it. Picking one and converting would be better. > - A session object currently has a =E2=80=98scheduled=E2=80=99 = datetime attribute that records the time that the object first enters = the =E2=80=98sched=E2=80=99 state. This should be replaced with a = relation to a new event class: SchedulingEvent, that records all status = transitions. > - New Bugs > - Inactive address chosen when saving an agenda - 2611 > - When creating non-session items, setting location often doesn=E2=80= =99t stick. Sometimes it takes multiple saves to get it to work. > - Groups populate incorrectly on an empty schedule - the = non-session screen display is broken. Stephanie will show Ryan and = develop a more detailed report. >=20 > _______________________________________________ > TOOLS-DEVELOPMENT mailing list > TOOLS-DEVELOPMENT@ietf.org > https://www.ietf.org/mailman/listinfo/tools-development From nobody Thu Oct 25 11:34:00 2018 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 E3EB3128A6E for ; Thu, 25 Oct 2018 11:33:58 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.879 X-Spam-Level: X-Spam-Status: No, score=-1.879 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, 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 69DxUU9aMLf8 for ; Thu, 25 Oct 2018 11:33:56 -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 65FB3130E3A for ; Thu, 25 Oct 2018 11:33:56 -0700 (PDT) Received: from unescapeable.local ([47.186.18.66]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id w9PIXsIf086175 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Thu, 25 Oct 2018 13:33:55 -0500 (CDT) (envelope-from rjsparks@nostrum.com) X-Authentication-Warning: raven.nostrum.com: Host [47.186.18.66] claimed to be unescapeable.local To: Russ Housley Cc: IETF Tools Development References: From: Robert Sparks Message-ID: Date: Thu, 25 Oct 2018 13:33:54 -0500 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 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] Outline of tasks for improving the meeting scheduling tool. 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, 25 Oct 2018 18:33:59 -0000 On 10/25/18 1:25 PM, Russ Housley wrote: > We used to have the concept of a meeting template. Templates had names. In this write-up, you talk about a "base schedule". I cannot tell if they are the same. Can you say more? I don't believe the datatracker has ever had a formal template concept. When a new meeting is created an "Empty" schedule is built. That can be edited to have things like breaks in it, and then that can be copied to build a particular proposed agenda in. Are you remembering something else? The "base schedule" concept I talk about below is new, and doesn't currently exist in the code. The fundamental idea here is that any changes to that base schedule would be inherited (appear immediately) by all other schedules for that meeting. > > Russ > >> On Oct 24, 2018, at 12:06 PM, Robert Sparks wrote: >> >> All - >> >> Below is an outline of the things that need to improve with the meeting scheduling tool. Please skim and let me know if there are any big items that you think are missing. Please comment where I call out open questions. The primary TODO below is to identify and name the types of things we are currently lumping in as "non-session sessions". I hope to use a few brainstorming sessions in Bangkok to build that set of things. This is not, of course, in the form we would use for an SoW - prose needs to be created. But before building that, I want to make sure we're targeting the right things. >> >> ---- >> >> >> - Improve scheduling working/research group sessions >> - Working with an individual schedule >> - Use bootstrap to display the agenda edit page >> - Remove the broken “show/hide” navigation mechanic (see the [>] button in the upper left). >> - Reduce the real-estate taken by the “You must save” and “Save as” dialogs (#1429) >> - Open Question: Remove the ability to slide days around? The secretariat is not using it. >> - Consider removing the ability to hide a room or a day (and the [show all] button with it. The secretariat is not using it. >> - Rendered HTML is currently invalid - result should pass HTML validator checks. >> - Javascript is currently putting a lot of debugging information on the browser console >> - Logging should either be removed or make the log levels selectable >> - Restructure the communication with between the browser and the server to be more efficient. >> - The current implementation makes several hundred requests for information about individual sessions, groups, their needed resources, and their conflicts. A single combined request would be more efficient. >> - Make it easier to see AD conflicts on the grid - the secretariat has to do this manually right now. >> - Must-be-present doesn’t show on the grid at all. The secretariat feels the data is not well groomed enough for it to be useful if it showed (there is concern about knot knowing who these people are well enough to make judgement calls on whether the declared conflict is really reasonable). >> - Make it possible to swap two entire columns on the drag-drop view (e.g. switch Wed and Tue morning). The secretariat does this frequently while building a schedule, sometimes while on the conflict-resolution call. It currently requires many drag-drop options to the unscheduled field, and is error prone. >> - Make groups that are in slots that don’t match their requested time more visually distinct (#1428) >> - Greying out sessions by area should work whether you own an agenda or not (#1584) >> - If a session is moved after the agenda is finalized, the agenda view should show something in the old time slot pointing to the new time slot. >> - Add a SessionStatusName of ‘rescheduled’. When a session is moved after the agenda is finalized, create a new session with the original SchedTimeSessAssignment, and place it in status 'rescheduled'. >> - Open Question: Is this WG/RG session specific? Should this happen to private meetings that are rescheduled? >> - Working with the set of schedules >> - Add a way to track changes to a schedule. Needs to be easier to remember what’s different between two versions >> - The typical workflow is to copy a schedule and make a few changes >> - Add a history that captures changes to a given schedule. >> - If this uses events, it will be different from SchedulingEvents. These need to be aware of changes to SchedTimeSessAssignment for a given schedule. >> - Open Question: Should we provide a diff between two schedules? >> - Add notes describing a version. >> - The name field isn’t big enough to be descriptive, and it is created before the description is really known. >> - Saving a new copy with a shorter descriptive name just makes clutter. >> - Page at /meeting/103/agendas/list can be made more useful >> - Consider grouping by (visible, public) >> - The Edit button does not take the user to a place to edit the schedule - the resulting form is for changing the name of the schedule, deleting it, making it official, or changing it’s (visible, public) status. The presentation should be more self-documenting. >> - The notes describing versions should be available here (at least in summary). These notes should be searchable. >> - Improve setting up a new meeting >> - Setting up a new meeting is currently inefficient - normally repeating things are scheduled on the wrong day (probably a bug introduced when we started starting meetings on Saturday). Copying things forward from previous meetings is not working as expected. Currently the secretariat has to do a lot of deletes/adds when setting up the new schedule. >> - The current workflow is to add things that should be the same across all agendas (like breaks and registrations sessions) to the “Empty” agenda. Concrete proposed schedules start by making a copy of the “Empty” agenda. Unfortunately, if the breaks or registration sessions need to change after some concrete schedules have been started, those changes have to be manually made to each copy. >> - Create a base schedule that all schedules inherit from >> - Things like breaks and registration would live in the base schedule >> - Changes to this base schedule would affect all schedules immediately. >> - Make sessions from the base schedule visually distinct wherever such sessions are shown graphically, such as /meeting/103/room-view >> - Improve the ability to schedule meetings that are not WG meetings >> - The non-session concept is overused, and talking about non-session sessions is counterintuitive. A redesign of the objects to give the non-session things usefully conceptual names is needed. Views that talk about “non-session” need to be updated to speak in terms of what they are actually working with. >> - Some of these things have materials, like ANRW and hotrfc >> - TODO: Describe each of the things and give them names >> - Improve the flexibility of the grid >> - Allow rooms to have different grids >> - It’s currently expected that WG/RG session rooms would all share the same grid, and sessions of other types would be scheduled in rooms with a different grid. Thus, the drag-drop views don’t need to support mixed grids at the moment, but care should be taken with the code anticipating that we would need to support them in the future. >> - /meeting/timeslots/edit, in particular, will need adjustment to handle rooms having different grids. >> - Possibly group rooms that share a common grid structure. >> - Make it easy to control what types of sessions do and dont appear on the official agenda page. >> - Allow graphical scheduling of non-wg sessions >> - Open Question: Choose between these options >> - Option 1 >> - Create a separate page similar to the WG/RG drag and drop. >> - Option 2 >> - Allow graphical scheduling and rescheduling of non rg/wg sessions directly on /meeting/room-view >> - Consider helper links from /by-type and /by-room to assist with finding and moving sessions. >> - Consider adding views that show “Isoc meetings” or “Private meetings” where we have room-view etc now, or perhaps leverage the customized agenda view - letting the secretariat select whether they see things on that view. >> - Improve session request handling >> - There were three groups at 103 that listed themselves as first order conflicts. The form needs stricter validation. >> - Groups can’t list themselves as conflicts >> - Closed WGs or Bofs can’t be listed as conflicts >> - Lots of requests list groups that are closed, or bofs that have passed. >> - The secretariat expresses concern about the quality of the group conflict data and the must-be-present data. Should we change the tooling to make it more likely the lists get maintained? (The IESG would need to make this decision). >> - Improve meeting statistics >> - There is currently a manually created report for the IESG that summarizes the number of sessions requested per area, and the number of requests of each length (per area). This can be automated. >> - Add a view reachable from the session-request pages (e.g. meeting/requests) that produces that summary. >> - Add graphs. Allow showing one meeting or a comparison against recent/all meetings. >> - Allow the user to view the reports/graphs showing what was “requested” and what “actually met”. >> - Improve testing >> - All the javascript needs automated testing >> - Improve the community’s view of the agenda >> - Modify the week-view in the agenda to allow selection/deselection of the ‘non-wg’ events (codesprint, systers lunch, etc). >> - Modify the week-view custom urls to use a query string rather than a fragment list. (Apps use fragments for other things too). Calendar subscriptions should still work. Consider having a browser cookie available to store preferences between meetings (see #1991) >> - Add an “All Bofs” customization button (#2314). Consider also an “All newcomers” or “running code” groups. >> - Add an important date ics feed. There is a manually created important dates calendar on the ietf website currently. >> - Possibly include important dates in the upcoming meeting calendar. >> - Reduce the granularity of IETF meetings in the “Upcoming meetings” ics. >> - Possibly allow selectors to only show IETF meetings where group “foo” has a session >> - See #2605 and #2216 >> - Improve materials handling for interims >> - Allow uploading of recordings for interims (#2471, #2467) >> - Code-base cleanup >> - Code has a mix of “schedule” and “agenda” in it. Picking one and converting would be better. >> - A session object currently has a ‘scheduled’ datetime attribute that records the time that the object first enters the ‘sched’ state. This should be replaced with a relation to a new event class: SchedulingEvent, that records all status transitions. >> - New Bugs >> - Inactive address chosen when saving an agenda - 2611 >> - When creating non-session items, setting location often doesn’t stick. Sometimes it takes multiple saves to get it to work. >> - Groups populate incorrectly on an empty schedule - the non-session screen display is broken. Stephanie will show Ryan and develop a more detailed report. >> >> _______________________________________________ >> TOOLS-DEVELOPMENT mailing list >> TOOLS-DEVELOPMENT@ietf.org >> https://www.ietf.org/mailman/listinfo/tools-development From nobody Thu Oct 25 12:36:07 2018 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 B0852130E41 for ; Thu, 25 Oct 2018 12:36:05 -0700 (PDT) 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, RCVD_IN_DNSWL_NONE=-0.0001, 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 8QbrvQsPCFmB for ; Thu, 25 Oct 2018 12:36:03 -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 A83141274D0 for ; Thu, 25 Oct 2018 12:36:03 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id 85C3C300A40 for ; Thu, 25 Oct 2018 15:36:01 -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 bhIXFozUGkCV for ; Thu, 25 Oct 2018 15:36:00 -0400 (EDT) Received: from a860b60074bd.fios-router.home (pool-71-178-45-35.washdc.fios.verizon.net [71.178.45.35]) by mail.smeinc.net (Postfix) with ESMTPSA id 6E4B0300538; Thu, 25 Oct 2018 15:36:00 -0400 (EDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\)) From: Russ Housley In-Reply-To: Date: Thu, 25 Oct 2018 15:36:00 -0400 Cc: IETF Tools Development Content-Transfer-Encoding: quoted-printable Message-Id: <7E6636D2-BA3A-47D7-94DA-01BA506A02E4@vigilsec.com> References: To: Robert Sparks X-Mailer: Apple Mail (2.3445.9.1) Archived-At: Subject: Re: [TOOLS-DEVELOPMENT] Outline of tasks for improving the meeting scheduling tool. 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, 25 Oct 2018 19:36:06 -0000 > On Oct 25, 2018, at 2:33 PM, Robert Sparks = wrote: >=20 > On 10/25/18 1:25 PM, Russ Housley wrote: >> We used to have the concept of a meeting template. Templates had = names. In this write-up, you talk about a "base schedule". I cannot = tell if they are the same. > Can you say more? I don't believe the datatracker has ever had a = formal template concept. When a new meeting is created an "Empty" = schedule is built. That can be edited to have things like breaks in it, = and then that can be copied to build a particular proposed agenda in. = Are you remembering something else? See = https://iaoc.ietf.org/documents/Agenda-Scheduling-Tool-RFP-2012-05-24-Fina= l.pdf. It talks about meeting agenda templates. > The "base schedule" concept I talk about below is new, and doesn't = currently exist in the code. The fundamental idea here is that any = changes to that base schedule would be inherited (appear immediately) by = all other schedules for that meeting. I think this is what was envisioned by meeting agenda templates. The = grid comes from the template, but different WG/RG assignments to the = slots will be made for a meeting that uses a particular template. Russ From nobody Thu Oct 25 12:43:03 2018 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 7C3171274D0 for ; Thu, 25 Oct 2018 12:43:02 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.879 X-Spam-Level: X-Spam-Status: No, score=-1.879 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, 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 i4vr4VFbEeKA for ; Thu, 25 Oct 2018 12:43:01 -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 1EF63130E6E for ; Thu, 25 Oct 2018 12:43:01 -0700 (PDT) Received: from unescapeable.local ([47.186.18.66]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id w9PJgxKA098265 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Thu, 25 Oct 2018 14:43:00 -0500 (CDT) (envelope-from rjsparks@nostrum.com) X-Authentication-Warning: raven.nostrum.com: Host [47.186.18.66] claimed to be unescapeable.local To: Russ Housley Cc: IETF Tools Development References: <7E6636D2-BA3A-47D7-94DA-01BA506A02E4@vigilsec.com> From: Robert Sparks Message-ID: <0a98698f-e986-cb87-d70e-a80e0493bf66@nostrum.com> Date: Thu, 25 Oct 2018 14:42:59 -0500 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: <7E6636D2-BA3A-47D7-94DA-01BA506A02E4@vigilsec.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US Archived-At: Subject: Re: [TOOLS-DEVELOPMENT] Outline of tasks for improving the meeting scheduling tool. 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, 25 Oct 2018 19:43:03 -0000 On 10/25/18 2:36 PM, Russ Housley wrote: >> On Oct 25, 2018, at 2:33 PM, Robert Sparks wrote: >> >> On 10/25/18 1:25 PM, Russ Housley wrote: >>> We used to have the concept of a meeting template. Templates had names. In this write-up, you talk about a "base schedule". I cannot tell if they are the same. >> Can you say more? I don't believe the datatracker has ever had a formal template concept. When a new meeting is created an "Empty" schedule is built. That can be edited to have things like breaks in it, and then that can be copied to build a particular proposed agenda in. Are you remembering something else? > See https://iaoc.ietf.org/documents/Agenda-Scheduling-Tool-RFP-2012-05-24-Final.pdf. It talks about meeting agenda templates. > >> The "base schedule" concept I talk about below is new, and doesn't currently exist in the code. The fundamental idea here is that any changes to that base schedule would be inherited (appear immediately) by all other schedules for that meeting. > I think this is what was envisioned by meeting agenda templates. The grid comes from the template, but different WG/RG assignments to the slots will be made for a meeting that uses a particular template. So, I think you are agreeing with what the outline proposes this project should do. Am I missing anything? > > Russ > From nobody Thu Oct 25 12:48:21 2018 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 38C9E130EC2 for ; Thu, 25 Oct 2018 12:48:20 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.879 X-Spam-Level: X-Spam-Status: No, score=-1.879 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, 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 7Gfbjqmjp33c for ; Thu, 25 Oct 2018 12:48:18 -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 D4274130EA3 for ; Thu, 25 Oct 2018 12:48:18 -0700 (PDT) Received: from unescapeable.local ([47.186.18.66]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id w9PJmIts099160 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Thu, 25 Oct 2018 14:48:18 -0500 (CDT) (envelope-from rjsparks@nostrum.com) X-Authentication-Warning: raven.nostrum.com: Host [47.186.18.66] claimed to be unescapeable.local To: Russ Housley Cc: IETF Tools Development References: <7E6636D2-BA3A-47D7-94DA-01BA506A02E4@vigilsec.com> From: Robert Sparks Message-ID: <406488a5-5dbf-dd4b-5d9d-b88bc47f5601@nostrum.com> Date: Thu, 25 Oct 2018 14:48:17 -0500 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: <7E6636D2-BA3A-47D7-94DA-01BA506A02E4@vigilsec.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US Archived-At: Subject: Re: [TOOLS-DEVELOPMENT] Outline of tasks for improving the meeting scheduling tool. 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, 25 Oct 2018 19:48:20 -0000 And to be complete On 10/25/18 2:36 PM, Russ Housley wrote: >> On Oct 25, 2018, at 2:33 PM, Robert Sparks wrote: >> >> On 10/25/18 1:25 PM, Russ Housley wrote: >>> We used to have the concept of a meeting template. Templates had names. In this write-up, you talk about a "base schedule". I cannot tell if they are the same. >> Can you say more? I don't believe the datatracker has ever had a formal template concept. When a new meeting is created an "Empty" schedule is built. That can be edited to have things like breaks in it, and then that can be copied to build a particular proposed agenda in. Are you remembering something else? > See https://iaoc.ietf.org/documents/Agenda-Scheduling-Tool-RFP-2012-05-24-Final.pdf. It talks about meeting agenda templates. And this was realized in code as I describe. The notion of template is the collection TimeSlot objects for the meeting, and is made available through the default "Empty" schedule that can be copied. > >> The "base schedule" concept I talk about below is new, and doesn't currently exist in the code. The fundamental idea here is that any changes to that base schedule would be inherited (appear immediately) by all other schedules for that meeting. > I think this is what was envisioned by meeting agenda templates. The grid comes from the template, but different WG/RG assignments to the slots will be made for a meeting that uses a particular template. > > Russ > From nobody Thu Oct 25 13:49:06 2018 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 CC7AF1276D0 for ; Thu, 25 Oct 2018 13:49:04 -0700 (PDT) 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, RCVD_IN_DNSWL_NONE=-0.0001, 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 T9Cc1L7bw6ju for ; Thu, 25 Oct 2018 13:49:03 -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 F001F124BAA for ; Thu, 25 Oct 2018 13:49:02 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id C670D300AA2 for ; Thu, 25 Oct 2018 16:49:00 -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 80KIFxwMX7zU for ; Thu, 25 Oct 2018 16:48:59 -0400 (EDT) Received: from a860b60074bd.fios-router.home (pool-71-178-45-35.washdc.fios.verizon.net [71.178.45.35]) by mail.smeinc.net (Postfix) with ESMTPSA id 6A41930056B; Thu, 25 Oct 2018 16:48:59 -0400 (EDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\)) From: Russ Housley In-Reply-To: <0a98698f-e986-cb87-d70e-a80e0493bf66@nostrum.com> Date: Thu, 25 Oct 2018 16:48:59 -0400 Cc: IETF Tools Development Content-Transfer-Encoding: quoted-printable Message-Id: References: <7E6636D2-BA3A-47D7-94DA-01BA506A02E4@vigilsec.com> <0a98698f-e986-cb87-d70e-a80e0493bf66@nostrum.com> To: Robert Sparks X-Mailer: Apple Mail (2.3445.9.1) Archived-At: Subject: Re: [TOOLS-DEVELOPMENT] Outline of tasks for improving the meeting scheduling tool. 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, 25 Oct 2018 20:49:05 -0000 > On Oct 25, 2018, at 3:42 PM, Robert Sparks = wrote: >=20 > On 10/25/18 2:36 PM, Russ Housley wrote: >>> On Oct 25, 2018, at 2:33 PM, Robert Sparks = wrote: >>>=20 >>> On 10/25/18 1:25 PM, Russ Housley wrote: >>>> We used to have the concept of a meeting template. Templates had = names. In this write-up, you talk about a "base schedule". I cannot = tell if they are the same. >>> Can you say more? I don't believe the datatracker has ever had a = formal template concept. When a new meeting is created an "Empty" = schedule is built. That can be edited to have things like breaks in it, = and then that can be copied to build a particular proposed agenda in. = Are you remembering something else? >> See = https://iaoc.ietf.org/documents/Agenda-Scheduling-Tool-RFP-2012-05-24-Fina= l.pdf. It talks about meeting agenda templates. >>=20 >>> The "base schedule" concept I talk about below is new, and doesn't = currently exist in the code. The fundamental idea here is that any = changes to that base schedule would be inherited (appear immediately) by = all other schedules for that meeting. >> I think this is what was envisioned by meeting agenda templates. The = grid comes from the template, but different WG/RG assignments to the = slots will be made for a meeting that uses a particular template. > So, I think you are agreeing with what the outline proposes this = project should do. Am I missing anything? No. I am just advocating consistent terminology. Russ From nobody Thu Oct 25 14:31:57 2018 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 88CD8130DFF for ; Thu, 25 Oct 2018 14:31:55 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.879 X-Spam-Level: X-Spam-Status: No, score=-1.879 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, 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 1K_PW0QapsYk for ; Thu, 25 Oct 2018 14:31:53 -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 AC66D130DFB for ; Thu, 25 Oct 2018 14:31:53 -0700 (PDT) Received: from unescapeable.local ([47.186.18.66]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id w9PLVqUm016309 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Thu, 25 Oct 2018 16:31:53 -0500 (CDT) (envelope-from rjsparks@nostrum.com) X-Authentication-Warning: raven.nostrum.com: Host [47.186.18.66] claimed to be unescapeable.local To: Russ Housley Cc: IETF Tools Development References: <7E6636D2-BA3A-47D7-94DA-01BA506A02E4@vigilsec.com> <0a98698f-e986-cb87-d70e-a80e0493bf66@nostrum.com> From: Robert Sparks Message-ID: <680b29b6-d38b-88e3-f96e-1065043bc4fa@nostrum.com> Date: Thu, 25 Oct 2018 16:31:51 -0500 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US Archived-At: Subject: Re: [TOOLS-DEVELOPMENT] Outline of tasks for improving the meeting scheduling tool. 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, 25 Oct 2018 21:31:56 -0000 On 10/25/18 3:48 PM, Russ Housley wrote: >> On Oct 25, 2018, at 3:42 PM, Robert Sparks wrote: >> >> On 10/25/18 2:36 PM, Russ Housley wrote: >>>> On Oct 25, 2018, at 2:33 PM, Robert Sparks wrote: >>>> >>>> On 10/25/18 1:25 PM, Russ Housley wrote: >>>>> We used to have the concept of a meeting template. Templates had names. In this write-up, you talk about a "base schedule". I cannot tell if they are the same. >>>> Can you say more? I don't believe the datatracker has ever had a formal template concept. When a new meeting is created an "Empty" schedule is built. That can be edited to have things like breaks in it, and then that can be copied to build a particular proposed agenda in. Are you remembering something else? >>> See https://iaoc.ietf.org/documents/Agenda-Scheduling-Tool-RFP-2012-05-24-Final.pdf. It talks about meeting agenda templates. >>> >>>> The "base schedule" concept I talk about below is new, and doesn't currently exist in the code. The fundamental idea here is that any changes to that base schedule would be inherited (appear immediately) by all other schedules for that meeting. >>> I think this is what was envisioned by meeting agenda templates. The grid comes from the template, but different WG/RG assignments to the slots will be made for a meeting that uses a particular template. >> So, I think you are agreeing with what the outline proposes this project should do. Am I missing anything? > No. I am just advocating consistent terminology. I agree. There are also lots of other places in the meeting code we should put this pressure on. > > Russ > From nobody Tue Oct 30 09:08:19 2018 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 2E5D712D4EA for ; Tue, 30 Oct 2018 09:08:17 -0700 (PDT) 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, RCVD_IN_DNSWL_NONE=-0.0001] 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 kgWeBcKtPOuU for ; Tue, 30 Oct 2018 09:08:14 -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 C88A812D4F2 for ; Tue, 30 Oct 2018 09:08:13 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id 620C6300AB0 for ; Tue, 30 Oct 2018 12:08:11 -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 GJVVzXutzmSz for ; Tue, 30 Oct 2018 12:08:09 -0400 (EDT) Received: from a860b60074bd.fios-router.home (pool-71-178-45-35.washdc.fios.verizon.net [71.178.45.35]) by mail.smeinc.net (Postfix) with ESMTPSA id 691CA3002C1; Tue, 30 Oct 2018 12:08:09 -0400 (EDT) From: Russ Housley Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\)) Message-Id: Date: Tue, 30 Oct 2018 12:08:09 -0400 Cc: IESG , IETF Tools Development To: IETF Chair X-Mailer: Apple Mail (2.3445.9.1) Archived-At: Subject: [TOOLS-DEVELOPMENT] Tools Team Report -- 30 October 2018 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, 30 Oct 2018 16:08:17 -0000 Tools Team Report -- 30 October 2018 1. Datatracker Projects - The merge plan was recently updated. -- See http://trac.tools.ietf.org/tools/ietfdb/wiki/MergePlan -- None of the upcoming activities are surprising or need extra coordination. - GDPR Compliance -- Two email messages for people to give consent for information in the datatracker went out, as planned. Deletion of Datatracker accounts that have not provided opt-in is still pending, and it is expected to happen in early November. 2. Community & Other Projects - The Tools Team is working to discontinue MonArch email archives. This will allow all of the mail-related tools to work from one copy of the archives in maildir format. So far, the responses from the community have been positive. The distribution was expanded to include the IRSG. Planning will begin shortly after IETF 103. 3. RFC Services Projects - RFC Format contracts are on schedule: -- IDnits -- Publication Formatter -- Text Submission -- RFClint -- SVGcheck -- XMLdiff - Release of xml2rfc 2.12.0 introduces the HTML formatter and the new v3 vocabulary. 4. Server Infrastructure - The custom DMARC-handling software was deployed for all mail lists in June. We received very positive feedback from the community. - There is a desire to move away from the custom software to ARC, but the ARC software cannot be configured to handle just a few of our mail lists. Henrik provided requirements to the ARC developers, but so far, they have not offered a release date. Alexey offered to help get a response. - There are three updates to www.ietf.org underway with Torchbox. First, upgrade the version of Wagtail from 1.12.1 to 2.2.2 was expected in October, but it is delayed until November. Second, changes to the home page display based on feedback received from the IETF community, which includes adding email archive search to the page, is complete. Third, the addition of an RSS feed for the IETF Blog is expected to be complete by the end of October. 5. YANG Catalog - Final deliverables for the recent project to improve the YANG catalog are being completed. - Once those are finished, the operation of the yangcatalog.org will be transferred to the IETF Secretariat. The current expectation is that will happen at the end of the year. However, if we learn that more development is needed to facilitate the transition, it will wait for 2019, where the budget includes some funds for the YANG catalog. - Moving to a tools-team-driven model for maintenance of the YANG catalog in 2019. - Requirements for new features are being gathered by Eric and Benoit for future development efforts. 6. Other Business - The IESG decided to allow I-Ds with non-ascii characters in places other than names to be posted. -- Release of IDnits 2.16.0 implemented this policy change. - The IMAP server code that is provided by ISODE does not handle changed usernames well. When a person changed their username, the IMAP server noticed the change, but all saved IMAP state was lost. Changing the username back recovered the state. Alexey has written a fix, but it has not been released yet. 6. Parking Lot - Prepare the RFC Production Center code for publication. -- Maybe this can get some attention when the six RFC Format tools are posted in an open source repository.