Skip to content

Committer Meeting ‐ 25.10.2024

Jump to bottom
Ege Korkan edited this page Oct 25, 2024 · 4 revisions

Attendees

  • Ege
  • Cris
  • Jan
  • Sergio

Agenda and Minutes

  • OCX Report:
    • Good attendance: 300-400 people reported. Talks had 10-15 people in the main track. Might be different for Java, Automotive.
    • Fun event: Some games and prizes, nice food, cool people.
    • Other WoT projects: Eclipse Sensinact -> Smart Cities relevance. https://gitlab.eclipse.org/eclipse-research-labs/nephele-project/opencall-1/vofactory/sensinact-environment is soon coming to https://eclipse-sensinact.readthedocs.io/en/latest/. They treat WoT as a southbound and northbound connector. Ege to paste pics in the chat.
    • EU Cyber Resiliency Act. Auditing of node-wot, "death" of github.com/siemens
    • Open Regulatory Compliance WG, T SSP interest etc.
    • Software Defined Vehicle
    • Financial Situation of Eclipse. ThreadX implications. Types of OSS foundations.
    • Apache PLC4X.
    • Security becoming more important
    • Next year Brussels
  • Account Management: We should notify Eclipse about the accounts we have.
    • npm
    • Dockerhub
    • Netlify
    • python
    • VS Code Marketplace
    • Algolia
    • NuGet
    • pub.dev
    • Google Analytics (already done)
    • Google Search Console (already done)
  • Website:
    • Ben Francis Feedback
    • Philipp Blum Adopters Feedback
    • To Dos: CD, Algolia, Documentation
  • 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 DID CampusOS subproject Maverick
      • Ege asked SICK AG -> Asked. Under discussion internally.
      • Lorenzo started UniBo -> The process is underway.
      • Cris will ask Vaimee
      • Ege will ask OPCF -> Asked. Under discussion internally.
      • Lorenzo asked Uni Pisa. No answer yet.
      • Cris and Ege asked Michael Freund from Fraunhofer. -> Under discussion internally.
      • Ege asked Vignesh for CALA or LMU (not xor) -> He got denied by LMU legal people...
      • Ege will ask Farshid from Canonical -> Not possible due to lack of adoption
      • Jan is asking University Emden-Leer -> First idea is ok, needs confirmation.
    • 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
  • 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?
        • 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)

Action Items

Decisions and Resolutions

Clone this wiki locally