Subject: [TOOLS-DEVELOPMENT] Ray's rough notes for Tools Call

From: Russ Housley <[email-masked]>
Date: Tue, 18 Mar 2014 14:32:06 -0400

Tools Call 18 Mar 14

Attendees

Russ
Robert
Glen
Tony
Henrik
Greg
Matt
Alice
Alexa
Karen
Ryan
Scott
Heather

1. Datatracker Projects
 - Expected Datatracker Releases -- Robert and Henrik

Next few weeks:
* pyflakes-clean
  - First of several new test tools added to the test suite and
     the corrections to the code that it uncovered.
* schema changes
  - updates to table column names and data types including
     * renaming meeting.ScheduledSession
     * increasing 8 character slugs to 16 characters
     * changing the document consensus field to allow setting it back to unknown
* django authentication
  - shifting to django's internal authentication framework,
     will allow people to log out.
* agenda
  - merge in the outstanding new functionality and bugfixes
     from the agenda project

* IRTF rg tracking
* improved audio/video link handling in proceedings
* generalized group pages (including edu-team pages)

 - Agenda Scheduling Development -- Robert

Likely to be in the May/June timeframe:

* agenda
  - corrections to any issues found during April testing
  - automated testing of the javascript components
  - tests for the automated placement code

Investigations started - intent is to have a release before Toronto,
but uncertainty is still high

 - Agenda Display -- Robert
	Robert to get more details; a few problems still remaining; expect some that affect the Proceedings; need to chase them down; 
	Alexa - this is -not- impacting production of the Proceedings

 - Improved test environment -- Henrik
	Henrik - now have clean in the branch; test suite taking more than a minute to run; started to look at another test, more challenging than pyflakes; priorities - focus on django before working on Vulture

	Robert - bringing in automatic tests for javascripts; frustrated with Firefox tool; hoping to test second data tracker release mid-May; looking for compatible Firefox version

 - IPR Tool improvements -- Robert
	Robert - v4 SOW out last week, no comments; 
	Scott - I think we can move forward with no further 
	Ray - ready to go to RFB with a locked down SOW then take proposals to IAOC
	Russ - take to TMC

 - Liaison Tool improvements -- Robert
	Robert - no outstanding requests for change; had Eliot look at it.
	Does have to go to community?  Yes
	Most recent is Feb 7th- Robert to review
	Then send to community
	Review online tracker

 - Transition to Django authorization model -- Robert
	Release before Toronto

 - Sandbox Datatracker for WG chairs -- Robert
	Russ - WG Chairs would like a place to try stuff
	Alexa - WG Chairs would like someplace to play with tools without touching live data
	Robert - when provide sandbox?  Just before meetings, or standing?  Takes a lot of CPUs; how often to refresh?; try to run for each person? “crazy talk”  Not enough horse power to support that effort; Experience when presenting to IESG and get feedback - everyone time someone has done something in the sandbox thinking they were doing something in Production system; get very confused;  How avoid that pitfall?  How was it marked to distinguish it from the Production?  How did people access it?  What was URL?
	Henrik - right direction at all?  Maybe try things on the data tracker itself?
	Russ - because produce emails and request for Secretariat to do work.
	Russ - Summary - improve documentation and make sandbox available only during the meeting.	

	example of a sandboxed tracker: http://tracker.tools.ietf.org/

2. Community & Other Projects
 - Pre-MHonArc Messages from mbox files for Mail Search & Archive Tool -- AMS
	Russ - need to go through mailbox files older than MHonArc files; Ryan was going to do one to get a feel for level of effort
	Ryan - picked ietf mailing list and found that the process was taking a long time; scanning for spam not bad; but indexing one by one was taking a long time;  Plan B - take reports of old archives and import them; this will be to be loaded more efficiently; 
	Robert - new way we found messages with errors in parsing; much improved; side effect of proposed path, will have a copy and will make maintenance more painless going forward; some possibility that some bits of spam will sneak through.  We will still use the MHonArc filters.  
	Ryan - this is a bit complex, there are some old messages in MHonArc that will overlap.
	Robert - don’t think we risk the manual part of pulling out spam
	Scott - assumes Spam Assassin captures everything the Secretariat did	
	Ryan - for the reimport - use MHonArc filter as we did the first time; step 2, for the lists that we have reports on, will take all of them, pass through Spam Assassin to the new archive;  Plan is for mid-April

 - IETF Website Makeover
	Robert - lot of discussion on the list;  What are next steps?
		right thing to do is take list discussion back to committee to prepare a revision 
	Ray - take what we have so far back to the committee since conversation has waned
	Russ - we may use some amount of javascript, such as Agenda tools
	Greg - are there parts today that use Javascript
	Russ - Secretariat
	Greg - so, non-public facing views; what is the main entry view of the website?  
	Russ - next step - design team do a rev based on feedback from call
	Robert - related to this; what we do or don’t do with PiWik at this point? Recommendation right now is that we don’t try to use it; potentiality very privacy invasive
	Alexa - if consensus we can leave off; survey?; service  uses 
	Matt - can restrict info in PiWik; apache logs have full IP addresses;
	Robert - collects a whole lot more info than Apache; we should remove javascript built into all of this pages

3. RFC Services Projects
 - xml2rfc bug fixes -- Alice and Henrik
	Henrik - no changes since last time; have other things in queue, hopefully before next call, but not next couple of weeks
	Alice - bugs are just trickling in, not preventing us from using tool

 - RSE Design Team -- Heather
	Heather - as for when SOWs coming to this group; originally in next 6 weeks or so then out to community by Toronto
	Robert - discussion on the list; more details coming out; answers will come out of the discussion
	Russ - should discussion be there, or somewhere else?
	Heather - not rfc-interest, but open to suggestions for other lists.

4. Transition of Mission Critical Tools
 - Moving mail aliases to ietf.org and link them to datatracker database
	Henrik - I had hoped to take care of the remaining coding in London, didn’t happen; 
			He wasn’t at the Sprint
	Henrik - either Toronto Sprint or I’ll take on the code
	Russ - on your list and if not done by Toronto, then at the Sprint

 - Internet-Draft dependencies
	Robert - works been done; next release will remove the link to the older pages 
	Russ - marked as done

5. Server Infrastructure
 - Automatic failover from Sunnyvale to Orlando -- AMS
	Matt - failover is still in progress, in the queue; have a couple of server changes that need to be made; talk about in April

 - Support from a Content Distribution Network -- AMS
	Matt - doing research; 4 players are v6 capable; all support SSL; waiting on rates for 3 out of 4; 
	Scott - https for all quotes?
	Matt - getting both rates, SSL and non-SSL.
	Matt - list of criteria, SSL, v6, rates, Google is setting up a CDN, no fee structure as yet, but I’ve been focused on the 4 where there is hard data.  Audio archives are 560GB.  Will send something out once data obtained.

6. Parking Lot:
 - Moving issue trackers and wikis for IETF WGs on ietf.org

7. AOB