Committer Meeting ‐ 18.10.2024

Jump to bottom

Ege Korkan edited this page Oct 18, 2024 · 3 revisions

Attendees

Ege
Cris
Jan
Sergio
Lorenzo
Daniel

Agenda and Minutes

OCX Updates: Short Slides for Tuesday done. Thursday slides are 50% done. Demo video preparation is underway.
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.
  - Cris DID Archeion
  - Erich DID Microsoft
  - Michael Freund did FAU Chair
  - Fady DID TU Munich
  - 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 will ask Vignesh for CALA or LMU (not xor) -> Asked. He will do that.
  - 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.
  - Jan is asking CampusOS subproject Maverick -> Project leads are ok.
- 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)
Website Redesign:
- Figma: https://www.figma.com/design/34hWJ41EcLFFhT0aItnvuM/Thing-Web-New-Design?node-id=63-1063&node-type=canvas
- Google Slides: https://docs.google.com/presentation/d/1xTqbdlIfiltY3AD4gk0YPh0vfIse_N-LPy11Odqe-Xc/edit?usp=sharing
- Draft Netlify Page: https://thingweb.netlify.app/
- Where to give feedback: PR
Test Things:
- Server refreshed, ports opened. Ege will do the installation
TD Code and WAM: Moved
node-wot:
- Testing the automated release pipeline from dart_wot
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?
    - 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

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