Meeting minutes
meeting starts
Agenda
McCool: we have several PR and then we should discuss the F2F
and then we should talk about testing
Minutes
<McCool> https://
first, minutes from last meeting are review
<kaz> Agenda:
McCool: ...regarding QR code, "can't" should be change to 'don't have to'
<kaz> (fixed)
since no objections are presented, minutes are published
PRs
now PRs are going to be checked
PR 179
<kaz> PR 179 - Replace interaction affordances in directory TD with a single link to its API endpoint
first PR review is #179
McCool: ...this PR seems to not have consensus, although many of the things were addressed.
McCool: ...let's close this PR, although not right now so Ben can respond
PR 168
<kaz> PR 168 - Add alternative payload format
next PR is #168
mccool types in the issue the main points of discussion
McCool: let's leave this PR util the author, christian glomb, is present
PR 204
<kaz> PR 204
next PR is #204
this PR only renames ids, therefore, and since no objections are presented
PR is merged
next PR is #205
since no objection is presented, PR is merged
PR 206
<kaz> PR 206 - Revert to use UUID URN as system-generated TD identifier
next PR is #206
PR is closed
F2F
next Topic is F2F
McCool: ....we have to decide which day we will do discovery stuff
… first proposal would be mid-late jun
… we could have a discovery meeting during F2F
… so which day shall be the meeting?
… date could be 30th of June
… we can't use the 30th because is opening day
… 23 of June is the alternative date
… next meeting will be 21 of June, scribe: Farshid
mccool is drafting the agenda for next meeting
mccool updates the cancellations file
Testing
<FarshidT> https://
next topic is testing
particularly, reporting
<kaz> (Kaz asks McCool if the call on June 21 will be a 2-hour call or a 1-hour call. McCool clarifies it will be a 1-hour call.)
Farshid: ...in this report we have assertionID, and the status (tat can be passed or failed) and then a column with the percentage of success passing the test
McCool: how is assigned the pass, skip, or fail
Farshid: if 1 is passed it is marked as passed and then it depends on the rest of tests passed, in that way the percentage is computed
McCool: we could have two tables, one with all the assertions where things are passed, failed, or skyped
McCool: the last column should be a list of test ids
… the second column should contain a list of those test ids, and if it was passed or failed
Farshid: we could have them in just one table
McCool: ...yes that could be a solution also
… in that way if something fails you can track down what
McCool: we want to deal with the two major implementations for directories
<FarshidT> example github.io nested file serving: https://
<kaz> [adjourned]