Meeting minutes
Agenda
McCool: minutes, dev meeting and finally testfest logistics
Minutes
<kaz> Feb-1
McCool: mentioned playground fixes and new features
… we talked about developer meeting for a lot of time
… created some directories
… we have some work to do
… no other comments
… just one minor thing: can you use mailing list instead of ML
… makes things clearer
… Takenak is spelled wrong
developer meeting
<kaz> 2023.03.DevMtg
McCool: do we have a doodle pool?
Kaz: not yet
McCool: any date in mind?
McCool: let start from a concrete proposal and then we can tune it
… Monday at 9-10 ? with an evening slot in US (which is morning slot in JP)
… testfests is more for active WoT members
… dev call is more about read manual assertions and get feedback
… 9-10 for west cost is not that great
… we can do at 10 AM on Thursday
… good for east-cost and europe but not that great for japan
… but we have a dedicated event for that
Kaz: are we ok with cancelling the ordinary calls during that week?
McCool: we can
… I'm worried for the low attendance from US
… maybe we should find better slots
Kaz: if we cancel regular calls we are flexible and generate two doodle pools
McCool: we can sacrifice discovery and security
McCool: do we people for china?
Ege: actually yes
McCool: let's keep the japan time slot resonable for Asia
McCool: any conflict for the week of 27th ?
Kaz: do we need testfest for profile?
McCool: we still need to resolve a bunch of at risk items
… I have some implementations that could fill some of the gaps
… testfest helps to focus people on the implementation work
Kaz: we really need to organize a test event for a whole week?
McCool: is the testfest the best way to cover the implementation report?
Kaz: we were very busy with checking the data itself during the testfest more than implementation
… and dubugging the tools
… maybe it is better to have an async phase where people prepare stuff for the testfest
McCool: the more work people do before the testfest the better
Ege: it should be clear how to submit data
… and also create deadlines
… maybe for the next charter I prefer doing less testfests
McCool: it could be a argument for not doing this one, but we need to cover the gaps
Ege: no I mean less testfests but more productive
Kaz: we should focus on how to better organize the work
McCool: I agree
… also for the next charter I won't have that much bandwidth
<Ege> +1 to find a dedicated person
<Ege> I would also volunteer but I will not have bandwidth in the next charter either
McCool: let's try to set the Developer meeting for the week of the 27th
Kaz: if possible it is better to have the Developer meeting first and then testfest
McCool: ok it's an alternative proposal but it would overlaps with the Japanese Developer meeting
… but it is only one day
Kaz: in any case let's propose it in the doodle pool
McCool: we got some contribution from Michael Lagally, just a draft but it needs clean up
… we have something from TD too
… no new results
… will create a folder for Discovery
Kaz: We can use the content of the DRAFT-atrisk-explanations.md file as the starting point
… but the goal of the developer meeting is to explain the intentions of each assertions. So we should concentrate on that clarification.
McCool: the result we are looking for is to resolve as many at risk items as possible
… we don't have implementers that are reporting to some of them
Ege: I can work on the Thing Description
AoB?
Ege: just a small thing we push a new version of the TD playground
… it should be stable for the upcoming testfests
McCool: I have a PR that I need to fix
… I see no new pr
… but you can add your results
Ege: small thing we added TM based validation to the playground
… you may see some errors if your using a fake TM
… in that case you should enable a flag
McCool: can you add some explanation in a readme?
<Ege> https://
<Ege> w3c/
<Ege> it is now applied to the batchValidation instead of a readme
<kaz> (McCool has added clarification as a comment to the batchValidation.sh)
<kaz> [adjourned]