Committer Meeting ‐ 20.09.2024

Attendees

• Ege
• Daniel
• Cristiano
• Jan
• Sergio
• Lorenzo

Agenda and Minutes

• Adopters: We start with Siemens, create the category and then ask companies.
  • An issue and corresponding PR is live
  • 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.
    • Asked SICK AG and it is being checked
  • 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.
• Test Things:
  • Multiple stuff in flight. Going to show PR.
• 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/
• 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)
• 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

Action Items

• OCX Presentation Prep
• 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

Examples Reorg Order

1. Move test-thing, coffee machine to test-things
2. Make sure docker-compose/swarm works -> Update all links pointing to the "services"
3. JS example counter in node-wot with beautification and explanations
4. Remove all duplicate and redundant examples from node-wot
5. Start integration tests in node-wot: move https://github.com/eclipse-thingweb/node-wot/tree/master/packages/examples/src/bindings and start end-to-end tests
6. Incorporate "some" examples' code into the documentation website by injecting their code to write twice
   1. Using node-wot in other projects as dependency
   2. Adding bindings and codecs
   3. Creating a custom servient