Skip to content

Committer Meeting ‐ 19.04.2024

Jump to bottom
Ege Korkan edited this page Apr 19, 2024 · 6 revisions

Attendees

  • Ege
  • Cris
  • Daniel

Agenda and Minutes

  • Short Updates:

    • WoT F2F Plugfest postponed but still an online F2F

  • Big Milestones:

    • Online WoT F2F in June:
    • WoT F2F Plugfest in November: Interop testing of all Thingweb components and documenting the results.
      • A mashup scenario with multiple components. E.g. node-wot exposes a TD of a physical Thing, registers to TDD, dart_wot consumes it and does something with it. This can become a presentable showcase in the open day
      • Test plan for interop with bindings and operations. Sort of like a benchmark to be improved upon
    • Open Code Experience (previously known as EclipseCon): Any ideas? Future plans and roadmap. Results of F2F. Showing usage of Thingweb: SICK AG, MagentaZuhause with Matter and node-wot as consumer.

  • Dockerhub account: https://hub.docker.com/orgs/thingweb

  • Important PRs or Discussions in Thingweb Components

  • TD Tools:

    • CI Pipeline

Action Items

  • node-wot: We will try Node.js ES2021 and if it doesn't work, we can go for older versions. We will bump minor version, i.e. going to 0.9.0
  • Create dockerhub account for Thingweb
  • Move anything but counter example to test-things and integrate to the docker compose. node-wot should have one-shot examples of how to use it for the ones who clone the repo.
  • Understanding the logo usage guidelines from eclipse (see https://github.com/eclipse-thingweb/thingweb/tree/main/brand/logos). We need guidelines in general
  • Moving relevant tools to td-tools from playground and node-wot
  • Ask for a blank slate for the server from Eclipse before HMI.
  • Playground Integration:
    • Binary usage: So that a non-JS person uses it like a Linux command-line script. Not necessarily as a package manager binary but first installing node and then using it from the binary path.
    • Default behavior of CLI: It should not validate its own examples directory.

Decisions and Resolutions

Examples Discussion

  1. Quickly spinning up node-wot things -> JS -> Counter.
  2. We lose compile time bug detection but vs code will show a visual error (implies that it should be doable in tsconfig somehow) -> This can be fixed by end-to-end testing
  3. Using node-wot in another project -> JS and TS -> This is basically documentation
  4. Advanced Usage of node-wot -> Also documentation
  5. Adding bindings and codecs
  6. Creating a custom servient

Note: Hosting Things for helping with understanding of WoT -> Source code is irrelevant in that case

Some other points:

  • JS examples need beautification
  • JS code can be copy-pasted to TS code so it makes sense to provide examples in JS.
Clone this wiki locally