Committer Meeting ‐ 26.04.2024

Attendees

Short Updates:
- WoT F2F Plugfest postponed but still an online F2F
- Google Analytics
PyPi account
Node-red PR: https://github.com/eclipse-thingweb/node-red/pull/16
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.
  - Submission link: https://www.ocxconf.org/event/778b82cc-6834-48a4-a58e-f883c5a7b8c9/websitePage:a02bf80e-a155-43e6-bb46-0f3b94b69c42
  - Need to understand pricing
Important PRs or Discussions in Thingweb Components
- https://github.com/orgs/eclipse-thingweb/projects/1/views/1
TD Tools:
- CI Pipeline

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
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
- TODO is listed at https://github.com/eclipse-thingweb/thingweb/issues/5
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.

Quickly spinning up node-wot things -> JS -> Counter.
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
Using node-wot in another project -> JS and TS -> This is basically documentation
Advanced Usage of node-wot -> Also documentation
Adding bindings and codecs
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.