Skip to content

Committer Meeting 06.12.2024

Jump to bottom
Ege Korkan edited this page Dec 6, 2024 · 2 revisions

Attendees

  • Ege
  • Cris
  • Sergio
  • Daniel
  • Jan

Agenda and Minutes

  • Next meetings:
    • 27.12.2024 and 03.01.2025 cancelled
  • Website:
    • Documentation
      • ToC
        • Thingweb Introduction and pointing to tools
        • Quick WoT Introduction
        • node-wot
          • Quick Start
            • Installing
            • Counter Example: Getting it to work (CLI commands and seeing something running), how to extend it
            • Going forward: Understand the architecture, how to contribute
          • Architecture
            • Basics for the Users: What node-wot has in the core, what are bindings -> Direct to the Bindings Section.
            • Technical Architecture: Reuse from presentations. Architectural documentation for developer introduction
          • Bindings Documentation
            • Examples in each binding readme -> Integrating readme automatically
      • JSDoc comments to generate the documentation -> Also, improves the documentation within code.
    • WoT vs Thingweb
  • Adopters:
    • What we know of: Siemens, University of Bologna, University of Pisa, SICK AG, Fraunhofer ISA, TU Munich, Archeion, Vaimee, CampusOS, University Emden-Leer, LMU (CALA), Microsoft, Canonical.
      • Jan is asking University Emden-Leer -> First idea is ok, needs confirmation.
      • 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 some stuff
      • Cris did Vaimee -> They will do an issue
      • Ege will ask Farshid from Canonical -> Not possible due to lack of adoption
      • Ege asked Vignesh for CALA or LMU (not xor) -> He got denied by LMU legal people...
    • Add such a pointer to our website and 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
  • 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

Decisions and Resolutions

Clone this wiki locally