Re: [TOOLS-DEVELOPMENT] Tools Call Agenda -- 12 May 2020 at 2:00 Eastern

My notes for tomorrow's call;

 > 1. Hot Topics
 >   - Are tools issues blocking any documents?
 >   - Are there any priority tool changes needed?

* Building a good user experience with Meetecho for future interims
   and online full meetings.
    - We are still working through what a user will hand to webex to
      "log in". Testing/evaluation of the experience with Oauth2
      depends on Django 2. We have two fallbacks ready - one that
      utilizes personal api tokens from the datatracker, and one
      that uses the old concept of providing a registration number.
      Ryan is working towards an API endpoint in the datatracker that
      will accept registration information as the registration system
      gathers it.

* There were several requests to change the behavior of ics calendar
   for meeting/upcoming. We are still reviewing how to best respond to
   some of them.

 > 2. Development Projects
 >    - Contracted projects progress update and immediate plans

We held a review session with the secretariat focusing on the new
meeting schedule editor. Liz asked for many improvements. A recording
of the session was sent to IOLA.

Dashcare has started work on the actual automatic schedule generator.

ZX Security has started the security review of the RPC code, and have
sent an initial set of comments.

We've made several changes to the datatracker at the IESGs request
focusing on interim meetings. These are already deployed (See
https://datatracker.ietf.org/release/). We have a request from the
IAB to allow programs to request meetings and manage materials similar
to working groups/research groups. This is implemented and will be
part of an upcoming release.

Work on converting the datatracker to Django 2 is nearing completion.

The wagtail portion of the website has been upgraded to Django 2 and
a recent release of wagtail. To do so, we removed the use and local
extensions to the deprecated Hallo editor. We should look at reimplementing
some of those extensions in the newer drafttail framework. It is now simpler
to keep the project aligned with new releases of wagtail as they come out.

We deployed an instance of CodiMD on Heroku and notified the chairs list.
It has not seen much use, and we haven't received any feedback past a few
initial positive responses. I will push for more feedback from the chairs.

We supplied a tool to help advance the NomCom eligibility discussions.

 >    - Volunteer projects progress update and immediate plans

We have scheduled an online sprint for 19May.

 >
 > 3. Operations Projects
 >    - Projects progress update and immediate plans

We will be experimenting with fronting some of the proxied applications
with nginx in the next couple of weeks

 > 4. Planning for upcoming projects
 >    - SoW under development
 >    - RFP progress update

We have not issued the RFP for github backups for two reasons:
It's not clear there is anyone with a product that could bid, and
Martin Thomson and Mike Bishop have created most of a (bespoke)
solution that will likely serve our needs.

Henrik will be the tools team advisor for the upcoming NomCom.

There have been several suggestions made in the last couple of
months around requirements for a revision of the errata verification
system. I am collecting those as input into a possible upcoming
project.

The Tools Architecture and Strategy Team held their first real-time
meeting. The agenda was organization and obtaining some initial
background.

 >    - Planning for sizable volunteer projects
 >
 > 5. Are there any unmet needs?
 >    - Open discussion
 >
 > 6. Any Other Business

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