I can't join you either, as I'm currently winding an ODD workshop here in Paris... more than 15 minutes notice might have been helpful I tend to agree with James' comment below. Another good idea would be to address inconsistently/incorrectly specified actions as per MSM's recent tickets ... On 02/03/17 13:54, James Cummings wrote:

I'll be in a meeting for the first part of it so will try to join you later if someone reminds me of the hangout url.

Joel''s warning about starting from scratch is good. Another approach is slowly and systematically updating portions of the code in place. Eg in our case moving some of the recursively called templates into functions or similar.

Back in awhile, James

-- Dr James Cummings, Academic IT Services, University of Oxford

On 2 Mar 2017 13:46, Syd Bauman <s.bauman@northeastern.edu> wrote: We are planning to meet again (on Google Hangouts -- will someone volunteer to set up the Hangout, please?) at 14:00Z, i.e., in ~15 mins.

The only things (I know of) for the agenda are:

1) trying to work out the rest of the ODD processing table[1], which IIRC Martin & I were supposed to work on prior to the call, but we didn't get to; and

2) tackling a ticket. Martin & I chatted and thought that ticket #206 might be something that we could handle as a group in < 1 hour.[2]

Also worth mentioning that I mentioned the goal of a complete re-write to MSMcQ, who pointed me to an article by Joel Spolsky.[3] (Joel is one of the guys who started both Trello and StackOverflow; he is *very* smart, and I think usually right on target. It is certainly worth reading.)

Notes ----- [1] https://wiki.tei-c.org/index.php/Mapping_ODD_processing [2] https://github.com/TEIC/Stylesheets/issues/206 [3] https://www.joelonsoftware.com/2000/04/06/things-you-should-never-do-part-i/ -- tei-council mailing list tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council

PLEASE NOTE: postings to this list are publicly archived