Committer Meeting ‐ 01.03.2024

Attendees

• Ege
• Daniel
• Jan
• Matthias
• Cristiano

Agenda and Minutes

• Short Updates:
  • Next meetings: Goal is to transition to biweekly and have more technical discussions. To be evaluated over time
• node-wot:
  • Branch Protection: https://github.com/eclipse-thingweb/.eclipsefdn/issues/16 -> DONE
• Node-RED:
  • publication
  • Adding to node-red community: https://flows.nodered.org/add/node
• TD Tools:
  • https://github.com/eclipse-thingweb/td-tools/pull/5 Merged
• Important PRs or Discussions in Thingweb Components
  • node-wot
  • (coming from test things discussion) We should review the examples pipeline.
  • Better Eventing for Browser (longpolling doesn't scale to multiple connections)
    • MQTT over WS
    • SSE -> We will do one SSE connection per thing where event name is affordanceType/affordanceName and then the data underneath. We will also add the id but we are not sure how it can be used on the Consumer side. The last part is up for discussion.
    • Plain WS
• Google Account issue: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/3995
  • Not clear how to use the account
  • If no access -> we can ask for forwarding and to be added to each service as admin/write access.
• Logo usage, is everything clear? Title or not discussion.
  • Usage clear. We need guidelines in general
  • TODO is listed at https://github.com/eclipse-thingweb/thingweb/issues/5

Action Items

• 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.
• Archive all repos at old thingweb, create a .github repo, put a profile readme and point to new thingweb
• Understanding the logo usage guidelines from eclipse (see https://github.com/eclipse-thingweb/thingweb/tree/main/brand/logos)
• Moving relevant tools to td-tools from playground and node-wot
• Ask for a blank slate for the server from Eclipse in next year. Should work before HMI

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.