Committer Meeting ‐ 14.06.2024

Attendees

• Jan
• Daniel
• Ege

Agenda and Minutes

• OCX Submitted
• Big Milestones:
  • 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.
    • Helm chart or compose file which starts components and does a test.
    • We should discuss whether this can be a generic way to do interop tests in WoT. We can involve other open source projects (e.g. Ditto to avoid https://github.com/eclipse-ditto/ditto/issues/1959)
• TD Tools:
  • CI Pipeline
• Dart_wot:
  • Release process (and how to generalize it)
    • In dart_wot, a process inspired by release-plz was added
    • For node-wot, maybe we can adapt Google's release-please
  • Discovery
• Important PRs or Discussions in Thingweb Components
  • https://github.com/orgs/eclipse-thingweb/projects/1/views/1

Action Items

• Moving thing-model-helpers to td-tools
• Trying to remove https://github.com/eclipse-thingweb/node-wot/blob/master/packages/td-tools/src/thing-description.ts and https://github.com/eclipse-thingweb/node-wot/blob/master/packages/td-tools/src/resolver-interface.ts
• 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
  • https://github.com/eclipse-thingweb/node-wot/issues/1267
• 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
• 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.