Re: [TOOLS-DEVELOPMENT] Tools Call Notes -- 10 September

[Liz Flynn <[e-mail]>]

Hi everyone,

Below are my notes from yesterday’s tools call. 

Liz Flynn
Project Manager / IETF
[e-mail]


=============


Tools Call Notes -- 10 September 2019 at 1:00 Eastern


1. Datatracker Projects
  - Expected Datatracker Releases -- Robert and Henrik
    -- https://trac.tools.ietf.org/tools/ietfdb/browser/trunk/PLAN
  - Python2 to Python3 transition – Henrik

Henrik: The next step will be taken when we have transitioned to the next version OS on the servers and when we have everything containerized or running under Python 3. The main waiting point is Trac, which we still don’t know if it will be released under 3 in time for us. Most likely the next work item is to containerize Trac. 

  - Meeting Application Improvements by IOLA – Robert

Robert: IOLA is still planning to complete the project by the date they had bid but they have been short on time.

  - Datatracker maintenance by DashCare – Robert

The developer is in a good place and they expect to have the project completed on time.

  - IRSG balloting -- Robert

Akayla has been working on this and had a slow start. We’ve turned the bend and started with a reasonable pace of progress. We’ve updated the delivery time to be right around the time of IETF 106. 




2. Community & Other Projects
  - WWW search to provide additional pointers -- Greg
    -- Give pointers to datatracker and mailarchive

Russ: Last time we talked about doing search over WWW, the datatracker, and the mail archive. That has been moved to the parking lot. Now, when you do a search on WWW you’ll get pointers to additional information in the datatracker and mail archive. This was fairly quick and the other thing is a tougher project. It will be implemented very shortly if it hasn’t been already. 

Robert: It will be in the next release or two of the website. 


3. RFC Services Projects
  - RPC testing of new RFC format tools -- Heather and Robert

Heather: There is only one outstanding piece to test, re the metadata when a document has been obsoleted. Next week we’ll be ready to publish in v3. XML to RFC output is so close that we’re still on target for next week. 

Russ: Idea is that starting with documents approved by a stream next week, those will be v3 through the whole process? The ones already approved will be v2?

Alice: Documentss that are in auth48 will go into an auth48 round 2 and move to v3.  There are less than a handful of docs that will be published in v2. 
https://mailarchive.ietf.org/arch/msg/rfc-interest/yEsDj8BR6AwtLi6UduKOPVc9SIo) points to transition details (https://www.rfc-editor.org/rse/wiki/doku.php?id=v3implementation)


  - Security Review of RPC Tools -- Robert and Heather

Robert: The directory structure in the details of the SOW needs to be updated. I will talk with Priyanka and re-circulate the SOW.


  - Rendering errata in more useful way -- Robert
    -- How will it be deployed on rfc-editor.org?

The beta of rfc-editor.org now includes errata. They can be linked from the Datatracker soon. Heather will talk to Alice and Sandy about the format of the errata and the URL; if “beta” should stay in the URL, which will require redirects later, or if the URL should be changed now. The errata pages can always be regenerated if people have a lot of suggestions for feature requests.




4. Server Infrastructure
  - IESG discussions of DMARC -- Henrik and Alexey
    -- When do we expect the next release of OpenARC? Ever?

Henrik: We will probably see OpenARC but maybe not soon. During the last IETF the code we need was written. It’s maybe being tested and it’s maybe been committed, but there’s no release. I will poke them again.


5. YANG Catalog
  - Putting yangcatalog.org in a Docker container – Robert

The main developer does not have more time available for us but is making progress. See https://github.com/orgs/YangCatalog/projects/1 for progress. Containerization is in the middle of the list of priorities.

  - Adding features from the yangvalidator project – Eric

Eric: We have someone committed for .5 day a week to build unit tests. Work is underway.
I’ve done nothing regarding yang validator yet. 

6. SustainIETF.org
  - It redirects to ietf.org

Right now this is just being redirected to ietf.org. It’s up to the LLC to decide if they want to do something else with it. This will be taken off the agenda for future calls unless there is something new to do with it. 



7. Parking Lot
  - Search over www, datatracker, and mailarchive

8. AOB



> On Sep 10, 2019, at 7:13 AM, Greg Wood <[e-mail]> wrote:
> 
> I may not make the call today, so some further update on these items:
> 
>> On Sep 9, 2019, at 11:33 AM, Robert Sparks <[e-mail]> wrote:
>> 
>>> 
>>> 2. Community & Other Projects
>>>   - WWW search to provide additional pointers -- Greg
>>>     -- Give pointers to datatracker and mailarchive
> 
> Robert and Russ and I discussed an approach. This Google Doc provides additional details:
> 
> https://docs.google.com/document/d/1jE0GnaIsfasTggr3DymJkbDzFKU1VLxTj36PO-uGhq4/edit?usp=sharing
> 
>> 
>> The www project got a lot of attention from me this month, with a release (v0.9.7) that moved the IESG statement to live under the IESG pages instead of with the blog pages.
>> 
>> The site also had some significant performance issues that took time to diagnose and address. While diagnosing, we identified several major changes that need to be made to the way the website currently serves blog pages. These are being tracked at https://github.com/ietf-tools/wagtail_website/issues (in particular issues 10 and 11) and will be addressed in upcoming releases. Greg will be entering several other requests (including analytics integration) as issues soon.
> 
> I’ve added several items. Once the analytics proposal has finished up community review, I’ll add that, too.
> 
> Let me know if more info would be helpful.
> 
> -Greg
> 
> _______________________________________________
> TOOLS-DEVELOPMENT mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/tools-development