[Scripting] minutes - 26 July 2021

available at:
  https://www.w3.org/2021/07/26-wot-script-minutes.html


also as text below.

Thanks,

Kazuyuki

---
   [1]W3C

      [1] https://www.w3.org/


                             – DRAFT –
                             WoT Scripting

26 July 2021

   [2]Agenda. [3]IRC log.

      [2] https://www.w3.org/WoT/IG/wiki/WG_WoT_Scripting_API_WebConf#Agenda

      [3] https://www.w3.org/2021/07/26-wot-script-irc


Attendees

   Present
          Cristiano_Aguzzi, Daniel_Peintner, Kaz_Ashimura,
          Tomoaki_Mizushima

   Regrets
          Zoltan

   Chair
          Daniel

   Scribe
          kaz

Contents

    1. [4]Minutes
    2. [5]Vacation plan
    3. [6]Publication plan
    4. [7]PRs

Meeting minutes

  Minutes

   [8]July-19

      [8] https://www.w3.org/2021/07/19-wot-script-minutes.html


   Daniel: don't see any issues
   … any objections?

   (none; approved)

  Vacation plan

   Daniel: planning to take off but not decided yet

   Cristiano: maybe I can tell more next week

  Publication plan

   Daniel: aiming September

   Kaz: we should maintain the schedule somewhere, e.g., a
   separate section within the agenda wiki

  PRs

   <dape> [9]feat: move thing-description types to a dedicated
   package

      [9] https://github.com/w3c/wot-scripting-api/pull/329


   <dape> [10]related Issue 327 - Publish Thing Description schema
   and Types in another npm package

     [10] https://github.com/w3c/wot-scripting-api/issues/327


   Cristiano: 2 directories about TypeScript definition
   … npm workspace is used

   [11]npm workspace

     [11] https://docs.npmjs.com/cli/v7/using-npm/workspaces


   Cristiano: we don't need to publish the whole mechanism
   … use git tag to mark the history (e.g. git tag
   thing-description@1.1.0-DATE)

   Daniel: make sense
   … but we'll get too many tags

   Cristiano: this is completely optional

   Daniel: we can ask Zoltan, etc., about opinions

   Kaz: why do we need this complicated mechanism?
   … do we need/want to maintain all the versions?

   Daniel: we can see the content of each version using the tags

   Kaz: it's just that we want to provide some specific version of
   Scriping API (and typescript-based definition for tha) with
   some specific version of TD
   … in that case, we can simply mention this version of Scripting
   API should be used with that version of TD, etc.
   … do we really need to maintain all the versions using this
   mechanism?

   Daniel: we just need some specific version. that's true
   … but evolution of the Scripting API spec should be also
   recorded

   Kaz: do we want to distribute Scripting API implementations
   using to people automatically?

   Daniel: probably we should ask Zoltan, etc., for opinions

   Cristiano: it's optional but might be confusing
   … let's stick with the current workflow for a while
   … btw, the current folder structure seems a bit strange
   … but changing the package name would not be good

   Daniel: "wot-typescript-definitions" vs
   "wot-typescript-thing-description" vs
   "wot-thing-description-types"

   Cristiano: need consistency

   Daniel: would like to change the version number from "1.0.0" to
   "0.0.1"
   … other than that point, would like to hear Zoltan's opinion as
   well
   … (adds a comment to issue 329: add "private" to package.json
   so that it cannot be published)
   … would like to stop here today

   Cristiano: ok

   [adjourned]


    Minutes manually created (not a transcript), formatted by
    [12]scribe.perl version 136 (Thu May 27 13:50:24 2021 UTC).

     [12] https://w3c.github.io/scribe2/scribedoc.html

Received on Monday, 20 September 2021 08:35:11 UTC