Committee/Project model refactoring and source of truth

[dave2wave]

We need refactoring to use the same source of truth as the Agenda Tool and Whimsy.

https://svn.apache.org/repos/private/committers/board/committee-info.txt

There is parsing code available:

https://github.com/apache/infrastructure-agenda/blob/master/app/parsers/ci_parser.py

[dave2wave]

Add attributes like startdate and enddate.

[sebbASF]

It would be good if there was a shared library script to process these files. This would make it much easier to update the file to a better syntax

[dave2wave]

It would be good if there was a shared library script to process these files.

I agree, but that is really a sub-project for the agenda tool and would need co-operative work with Whimsy.

[sebbASF]

The agenda tool and Tooling both use Python, which should make it trivial to share.
Maybe the code belongs in asfpy?

Whimsy uses Ruby. Not so easy to share.

[dave2wave]

The agenda tool needs to update this information while ATR only reads it.

We haven't made any decision about a roster tool. Eventually we may want that code in asfpy

[dave2wave]

Currently asfpy does not have any svn features.

[sebbASF]

I was referring to the parsing, not fetching the file.

[gstein]

Note that committee-info.txt is available (for ATR's read-only needs) via aiohttp. Subversion isn't required.

Would still need a (shared?) parser, but svn isn't a hard-stop for ATR here.

[dave2wave]

The plan will be a data pip service layer which will be used with the Agenda Tool first.