Re: [TOOLS-DEVELOPMENT] Tools Call Agenda -- 14 April 2020 at 1:00 Eastern

[Robert Sparks <[e-mail]>]

My notes for next week's meeting:

On 4/8/20 8:39 AM, Russ Housley wrote:
 > ** TRYING A NEW OUTLINE FOR THE AGENDA **
 >
 >
 > Tools Call Agenda -- 14 April 2020 at 1:00 Eastern
 >
 >
 > JOIN WEBEX MEETING
 > https://ietf.webex.com/ietf/j.php?MTID=m440dd848726339c03e605b9956e38bac
 > Meeting number (access code): 640 103 570
 > Meeting password: tools
 >
 > JOIN BY PHONE
 > 1-877-668-4493 Call-in toll free number (US/Canada)
 > 1-650-479-3208 Call-in toll number (US/Canada)
 > Meeting number (access code): 640 103 570
 > Meeting password: tools
 >
 >
 > 1. Hot Topics
 >    - Are tools issues blocking any documents?
 >    - Are there any priority tool changes needed?

     - We made many changes to the datatracker to support the 
virtualized IETF107
       and the increased use of interims after it. The rate of requests 
for new
       features and tweaks to the datatracker support the interims has 
begun to
       slow.

     - We are in discussions with Meetecho about integrating Meetecho 
with the
       virtual meetings.

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


     - IOLA provided a first pass at a better meeting schedule editing
       interface. I've asked for some changes before we begin testing 
with the
       Secretariat. The implementation is such that the old and new 
interfaces
       are available at the same time.

     -  Dashcare has completed part 1 of the automated schedule builder. The
        results are in 6.126.0. Jay and I will work with Dashcare to start
        part 2.

     -  We had a kickoff call with ZX Security, and have provided the
        materials needed for the RPC Security code review. We currently
        expect work to start on this project either the last week of April
        or the first week of May.

     -  Work is underway on dropping Python 2 support in the datatracker
        codebase. The next steps will be moving to Django 2 and to 
PostgreSQL.

     -  I have completed the repairs to the website needed for snippets to
        display links correctly (see release 0.9.16). I have started work on
        converting the website to Django 2.0, and subsequently moving to the
        most recent version of wagtail. One item of note. We are removing a
        transcoder that was used to downconvert the custom javascript 
torchbox
        built for the site to something IE 11 (of the time) worked 
better with.

     -  We are talking with Pantheon about increasing their level of 
support for
        YangCatalog.org, including what it would take to deploy the 
containerized
        version of the application on a cloud service such as Amazon. We 
have begun
        working towards identifying the actions taken while operating 
yc.o (such as
        granting a new sdo access to the API) that can be performed by 
the Secretariat
        and building the right interfaces and training to transition 
those tasks.

     -  Rich Salz and I worked at the codesprint towards replacing the 
DocumentURL
        construct in the datatracker with a more generic 
ExternalResource, which
        would make it easier for chairs to provide github repository 
references and
        usernames to tooling that would be interested in such things. 
Work on this
        slowed just after the 107 week, but I expect to return to it soon.

 >
 > 3. Operations Projects
 >    - Projects progress update and immediate plans
 >
 > 4. Planning for upcoming projects
 >    - SoW under development

     - The Github Backup SoW is still pending. Martin put together 
something that
       appears to back up everything needed for a group, but only if the 
group is
       configured to use his continuous integration tooling. This needs more
       investigation.

     - Testing on fronting the websites with nginx is still planned, but 
no progress
       was made this month.

 >    - RFP progress update
 >    - Planning for sizable volunteer projects
 >
 > 5. Are there any unmet needs?
 >    - Open discussion

     - Do we need to provide tooling or data-research to support the 
conversations
       around eligibility for future NomComs?

     - Last month, we mentioned trialing CodiMD with some upcoming 
interims, but
       action has not started on this idea.
 >
 > 6. Is the new agenda outline an improvement?
 >    - Open discussion
 >
 > _______________________________________________
 > TOOLS-DEVELOPMENT mailing list
 > [e-mail]
 > https://www.ietf.org/mailman/listinfo/tools-development