Meeting minutes
Agenda
Ege: given low participation, should work on simpler items
Kaz: we need to think about Testfest prep given it's planned to be held during the week of April 24
Lagally: to be added to the agenda for today
Minutes
approved
Issues
Issue 333
Lagally: Sebastian is not available for Profile these days
… Ege, can you work on this issue?
Ege: yes
… what's the main question here?
Lagally: (shows the mismatch between Profile and TD)
Ege: aligning all the tables. right?
Lagally: let's concentrate on this point now
… but aligning all the tables is a valid question
Kaz: if we want to follow the definition of the tables within the TD spec, that's fine and probably would be useful
… however, are we aware that would mean we need to update our own tables once the original tables within the TD spec are updated
… my point is just that we need to be aware of the dependency
Lagally: think we're aware of that dependency
… but don't want to consider all the tables
… so would suggest we concentrate on this table within "5.6 Links" section
Kaz: and we need to check with Sebastian. right?
Lagally: Ege should check with Sebastian
Ege: ok
Contributions
Lagally: would like to think about work assignments
Lagally: we have 6 Editors here
… would like to think about how to share the load
Kaz: we should clarify our procedure first
… who from the Editors to handle which issues
… which depends on who are still active
… then clarify who to generate concrete PRs
… I personally think the original issue raiser should generate it. of course the Editors can help, though.
Ege: don't think we need to clarify that kind of policy
… also not sure the original issue raiser need to generate a concrete PR
Lagally: that's a reasonable comment but we have problems now
Ege: it's a common problem with our specs in general
Lagally: maybe we should have a general policy discussion as well
Kaz: it seems we need some more time for this discussion on assignment
… do we want to postpone this discussion and talk about Testfest prep?
… or rather postpone the discussion on Testfest prep and think about assignment now?
Testfest prep
Lagally: let's talk about the policy how to handle the issue assignments a bit more
<mlagally> proposal 1: WG member who submitted an issue should be initial assignee, he should drive it, identify a contributor
<mlagally> proposal 2: round robin assignment of current editors to unassigned issues and ask them to drive the contributions
Lagally: there two proposals so far, so would record them now.
Testfest prep
Which specification parts are ready for testing?
Lagally: (goes through the Editor's Draft)
… think all the content from the Editor's Draft is ready
Kaz: meaning all the sections starting from section 1 till the Appendix?
Lagally: yes
Ege: which parts to be expected to be tested?
… CSV files to be updated
Lagally: people are contributing TDs
… why don't we ask them to do the same contribution
Kaz: we're diving into the second item already
… let's talk about the content first
… regarding the content itself, are we ready to extract normative assertions from all the sections?
Lagally: McCool is working on that
… we have tools generated by McCool and Toumura-san
Kaz: given the feedback from the TD, Arch and Discovery specs, we should make sure if all the assertions are comprehensive enough for the developers
Lagally: we've been getting feedback from developers at least from the WG participants
… but why do we need to clarify if the document is comprehensive enough?
Kaz: given the feedback we got so far for the other specs, i.g., TD, Architecture and Discovery
… unfortunately, the assertions from those specs were not clear enough for the external developers
… so now we're holding Dev Meeting to describe the assertions
(some more discussion)
Kaz: sorry but we're out of time
… so let's continue the discussion next time
Lagally: can't make the Testing call myself today
… but please have discussion there as well
[adjourned]