Last edit -> Aug 22 (JE) - added mtg notes/actions in light blue italic
Attendees
Mark T., Tim J., Laurent M., Christine B., James D., Carlos R., Marco M., Ada N., Steve G., Baptiste C., Tom D., Pierre L., Raffaele D., Giuliano T., Mark A., Pat D., Janet E.
Regrets
M. Demleitner, T. Dower, G. Lemson, K. Polsterer, A. Schaaf,
We reviewed the table of RFEs ... for the most part, reviews are on track
Groningen Update
PD gave a summary of the Gronigen meeting plans
2019A Roadmaps
2019A Roadmap - Reference leading to Groningen Meeting
Team walked thru Roadmaps by Group; WG & IG Roadmaps for 2019A are up to date; progress is mostly on track
TCG topics
Caproles (from M. Demleitner, P. Dowler lead)
PD gave an overview - we deffered further discussion for the Interop
TD briefed the next 2 topics that were well reveived for discussion. Since we were down to out last 5 minutes, we will add them to the TCG agenda for Groningen
Status of document process in github
I think the github presence is ready. Apps would like to start using it for our next round of standards updates. Is there a documented process that comes with the repo?
Is it OK to handle some of the discussions on github itself, say through pull request comments or by filing and commenting on issues, or does all discussion still need to happen on the mail list? I would understand if that’s the case, but it may also render less useful some of those built-in github features.
Tighter coupling of reference implementations to standards approval
So far, the requirement for reference implementations for standards has been useful, but in the RFC it’s mostly a matter of checking that box.
I’m curious how people feel about being more rigorous in accepting those implementations. I’m mainly thinking about having them be reviewed and tested to verify both interoperability and coverage for all the requirements of the standard.
AOB
None noted
Actions
NEW
ACTION-T0819-1: JE - Contact Groningen organizers about moving TCG meeting to Wed evening - NEW
JE sent email this afternoon (8/22) and is waiting for a response (cc'd Mark A/Pat D)
OPEN/WORKING
ACTION-T0219-5: PD/JE - kick off the Architecture doc effort and distribute tasks to team - WORKING
ACTION-F0518-4: Laurant - Produce documentation on how the models relate and how to get started with certain use cases. WORKING
ACTION-T2019 -6: PD/JE: Ask DOC to transfer links to new Publishing on the VO doc when time is right - OPEN