Meeting minutes
agenda
<kaz> agenda
Cristiano: agenda
approving the previous minutes
<dape> Feb-20
Cristiano: charter discussions may include discussion about Scripting API Rec track
Minutes approved.
PRs
PR #456
<cris__> PR 456 - Use bib references in text instead of URLs
Daniel: updated to use biblio references than links every time
Daniel: xref cannot include URL fragments
Cristiano: it's ok to use "data-cite" links
https://
https://
PR approved
Cristiano: merging now
Daniel: we have the same issue with other specs as well, maybe we should share the best practices
Zoltan: agreed, we have several issues with spec improvement label, and we can share the best practices
Kaz: please raise the issue up in the main call
Zoltan: we should summarize the best practices in a place (issue) we can refer to
Kaz: please explain the latest nice features of ReSpec in the main call, then we need to figure out the references Daniel mentioned. maybe we can look into the other W3C specs to see how to deal with the, e.g., the ones from WebApps WG.
Cristiano: how to cite for instance TD
… didn't find that through xref
<cris__> w3c/
Zoltan: note to self: add links to Web IDL and Infra spec
Issues
issue 224
<cris__> Issue 224 - Scripting API versioning
Cristiano: about scripting API versioning
… some of the text in the issue is not in the meeting minutes
Cristiano: it would be nice to ship node-wot with the right version of the Scripting API linked
Cristiano: we can do label categories wrt how do they affect the implementation
Cristiano: using github tags should be fine
Zoltan: can we render a given tag/ git hash?
Cristiano: we can
<cris__> https://
Zoltan: then we can do that, but it's a nice practice to also tag
Cristiano: TypeScript types should also be in sync
Daniel: wrt we could try to publish more often: I see this impractical, at least not feasible on a weekly basis
… which is why we decided that when we make a change on TypeScript / spec, we create a tag
Cristiano: we can use a special tag to node-wot
Daniel: node-wot uses 3 versions
… Thing Model, Thing Description, Scripting API
Zoltan: the node-wot package.json dependency tag is empty, it should be used
Cristiano: right, it might need some changes
Cristiano: the correct way would be to tag the whole Scripting repo with the tag when the TypeScript is changed
Daniel: agreed
Cristiano: capturing the discussion in an issue
Zoltan: we can make a tag after each PR that changes the TypeScript
Daniel: but limited to one tag per day, so may comprise multiple PRs
Cristiano: major algorithms changes might trigger a new tag as well
Cristiano: and publish the TypeScript with a new tag, even though no changes in the interface itself
Cristiano: should we update the readme with this?
Zoltan: right, good idea
Cristiano: capturing that in an issue as well
<cris__> Issue 458 - Explain the new tagging mechanism for experimental features
Zoltan: let's assign a few issues for the next meeting
Daniel: will check the optional arg null initialization
Zoltan: will check as well
Cristiano: AOB?
(none)
[adjourned]