Meeting minutes
minutes
Daniel: looks fine
<dape> --> Nov 6
Daniel: we merged
… PRs and look issues
… ok we can approved them
<dape> s/Nov 11/Nov 6
<kaz> (approved)
Next calls
Daniel: first of all, xmas is near. We should decide if there will be cancellations
… it seems that in other calls they already cancelled calls.
… is the plan ok?
… no call the 25th of december and first of January
… let us know if you don't agree
2 weeks slot call?
Daniel: 2 calls in a month?
Cristiano: 2 weeks slot make sense. We don't have that much topics to discuss
Daniel: agree
Jan: second that, we are corrently working mostly async anyway. We can still merge PR once every two weeks
… we can also always switch back
Daniel: suggestion keep weekly slot but use the wiki to cancel it
<dape> PROPOSAL: For the near future the Scripting task force is going to have a 2-week schedule. Ahead of time it will be made public the when the next call will take place. W3C calendar entries remain as is for now.
<cris> +1
Kaz: given we're not sure when to do what, it couldn't be a "resolution" but maybe we can still record our intention for that direction within these minutes
Daniel: changing to intention. Meanwhile we discuss the plan
…let's see if we can came up with a plan
… and cancel the next call if needed
Kaz: if you have a clear time span when you want to have a bi-weekly call you should say it in the text
… "near future" is vague. also if your intention is actually "for a while until the work on TD 2.0 and Discovery 1.1 starts", you should say so.
<dape> INTENTION: For a while the the Scripting API task force might want to have a bi-weekly schedule. Meeting cancellations will be made official ahead of time. W3C calendar entries remain as is for now.
PRs
Daniel: no updates
… one about improvements, we are stuck and we need time to look into it
… the next twos are about discovery
… and how to align
PR 513
<kaz> PR 513 - feat!(typescript): align TypeScript definitions with Discovery API
Cristiano: looks good to me
Daniel: merging PR
Daniel: we can now start working with node-wot
Jan: it was a blocker, great to merge
Daniel: thank you jan
PR 517
<kaz> PR 517 - feat!: remove constructor from ConsumedThing interface
Daniel: we are using constructors in the webIDL
… it wasn't in the TS definitions
… it is not what we intended
… we should also use the term creating instead of constructing
Zoltan: do we have the expose method still ?
Daniel: yes
Zoltan: consistent deciding
… it is a complication and it is misunderstanding
Daniel: it was there for hystorical reasons
Zoltan: ok to merge
Kaz: what is the intention? given the current sample code we can remove the constructor code but the text can still say construct
Daniel: we don't change anything else, but just align the text
Kaz: it sounds ok, who and when the object it self is created?
… was it a bug?
Daniel: it was a leftover from old days
… it was also in ExposeThing
Cristiano: two comments. It is true that creates confusion. In the CG we got feedback about how it was not clear the process to create a ConsumedThing. Second I recall that the constructor was there for facilitating testing, still we can remove it
Daniel: ok, merging
PR #518 and Issue #512
<kaz> PR 518 - refactor: add readme and perl script for publication/release
<kaz> Issue 512 - Add perl script (for fixing duplicate IDs) to master/release folder
Daniel: kaz created a script to handle duplicated ids created by a bug in respect
Daniel: added also readme
… similar to what other repos have
… is that ok to merge it?
Zoltan: ok
Kaz: ok too. if needed, we can modify the description later. thank you
Jan: ok too
<Mizushima> +1 me too
Jan: should we add a followup issue?
Cristiano: a little bit overkill but that's ok
Daniel: it already there
… Issue 480
PR 489
<kaz> PR 489 - Better types for Scripting API
Daniel: cristiano worked on better typings
… there were problems
Cristiano: there are tricky parts
Zoltan: we should take care to not make more restrictions
… than the one are in the algorithms
<JKRhb> I will also have another look into it :) I've not found a solution for the problem so far as well :/
<kaz> [adjourned]