Meeting minutes
Daniel: welcome
previous minutes
<kaz> Mar-13
Daniel: we missed two calls
… one for charter discussion
… and other for low people count
… last minutes to be approved are from march 13
… no issues
… mintues approved
Meeting cancellations
Daniel: next monday is Easter Monday
… public bank holiday
… I won't be available
Cristiano: me neither
Kaz: there is no specific holiday for Easter in Japan
… but you as editors can change the schedule
Daniel: ok cancelling next week call
Kaz: please update the main wiki too
Publication schedule
Daniel: current plan is that we are going to decide today about moving to draft review
… btw publication schedule is yet to be updated
… we have still pending issues
… but we can fix those later
PR 463
<kaz> PR 463 - Fix internal slot in event handlers
Cristiano: we can go on if we can merge PR about internal slots
Daniel: to me PR is good to go
… note that if we don't commit for today
… we will delay publication schedule
Zoltan: I would like to have the internal slot as list
… not a map
Daniel: would you hold back the PR ?
Zoltan: I would keep the old format as list
Zoltan: I am not sure if we need to merge the Pr
… I try to understand what we are fixing here
… map is complex
… is kind of a meta object
… lists are better (we can use map as implementation detailed)
Daniel: we have Map in other places as well.
… does this mean that we have to discuss this later?
Zoltan: this is not a proper way, is like to prescribing implementation
… we should give freedom to use whatever they want
… but since we have them in other places we can merge as consistency
Daniel: we should go public today
Zoltan: what is the difference with the current published version?
Daniel: it is pretty old
… we did also breaking changes
… we can fix everything later or redesign some parts
Zoltan: we can redisign the internal slots anytime
… ok since we have the map in other places we can merge this
… do we need to freeze for the review?
Daniel: for the next two weeks we will ask for review
… so merge this PR now and fix it with a quick PR before Wednesday
Zoltan: also there might be PR during the review period
… e.g. fixing and review feedback
Cristiano: ok
Timeline
<kaz> wot PR 1084 - Defer scripting API note publishing due to charter discussion
Daniel: ok I will update the group
… shall we make an email notification today or on wedsay
Cristiano: we can send an email today
… maybe just say that there might be a follow up PR
Zoltan: go ahead, I'm going to provide a fixing PR
proposal: We will send an email tomorrow asking the group to review Scripting API document. On Wednesday we will update the whole group in the main call.
RESOLUTION: We will send an email tomorrow asking the group to review Scripting API document. On Wednesday we will update the whole group in the main call.
Kaz: will you ask the whole wg group to do review within two weeks?
… keep in mind that the period starts from Wednesday
Daniel: yes
Kaz: we should be clear about the status
… if there is any delay we should update the resoltion
Daniel: we are intime
Zoltan: we've asked review to the group
Kaz: the publication timeline here is delayed for Easter holiday?
Daniel: not really just one day
… people should have time
Kaz: we should be more precise, which version and which dates (e.g. from, to)
<dape_> PROPOSAL: Clarification for Publication: The WoT group review will start on April 4, and will end April 17. The Scripting API note will be published April 24.
Cristiano: lgtm
Kaz: ok
RESOLUTION: Clarification for Publication: The WoT group review will start on April 4, and will end April 17. The Scripting API note will be published April 24.
Daniel: we can go on with next charter topics
… it took a little bit
Cristiano: PR 462 might be relevant
… for versioning
… but we can do it on parallel
Daniel: I agree we can do in parallel
Kaz: we're out of time anyway
[adjourned]