Committer Meeting 06.12.2024

Attendees

• Ege
• Cris
• Sergio
• Daniel
• Jan

Agenda and Minutes

• Next meetings:
  • 27.12.2024 and 03.01.2025 cancelled
• Website:
  • Documentation: https://hackmd.io/@egekorkan/thingweb-docs
    • JSDoc comments to generate the documentation -> Also, improves the documentation within code.
  • WoT vs Thingweb
• Adopters:
  • What we know of:
    • Ege asked SICK AG -> Asked. Under discussion internally.
    • Lorenzo started UniBo -> The process is underway.
    • Ege asked OPCF -> Asked. Under discussion internally.
    • Lorenzo asked Uni Pisa. No answer yet.
    • Cris and Ege asked Michael Freund from Fraunhofer. -> Ege needs to do some stuff
    • Cris did Vaimee -> They will do an issue
  • Add such a pointer to each readme (if you are using Thingweb Component X, please show support by getting into the adopters list). See https://eclipse.dev/ditto/ for the usage of the Eclipse API.
    • We will add a badge next to the others and link to a section below that explains the process (just a logo and link, need to be part of the org)
• node-wot:
  • Testing the automated release pipeline from dart_wot
  • Counter Example: Duplicate the code in test-things and host as others.
• Important PRs or Discussions in Thingweb Components
  • https://github.com/orgs/eclipse-thingweb/projects/1/views/1
• Big Milestones:
  • WoT F2F Plugfest in November: Interop testing of all Thingweb components and documenting the results.
    • How go with implementing new TD features? Release organization: Should we have a beta channel or keep adding stuff until there is something not backwards compatible?
      • Go for 1.0 release for the plugfest where 1.0 (and main branch) has new features of TD. 0.8.x or maybe 0.9 versions stay with old td features. They can still get updates in their gh branch and new npm releases.
    • What to do for Thingweb?
      • OCX mashup scenario with multiple components. Siemens Sentron PAC <-> node-wot modbus client <-> node-wot mqtt <-> MQTT Broker <-> dart_wot based smartphone app
      • Test plan for interop with bindings and operations. Sort of like a benchmark to be improved upon.
      • 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)
      • Fixing the known bugs: Browser PR, Modbus Binding Timeout, CLI big warning due to outdated dependencies, MQTT implementation following old binding.
      • Manageable Actions Feature Test

Action Items

• 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