Committer Meeting 04.04.2025

Attendees

• Ege
• Cris
• Sergio
• Daniel
• (GSoC Applicants)

Agenda and Minutes

• GSoC:
  • Deadline: Unknown
  • Submission as issue to https://gitlab.eclipse.org/eclipsefdn/emo-team/gsoc-at-the-ef/-/issues/?sort=due_date&state=opened&first_page_size=100
  • Overall Plan: Meet 1h per week, committer call as well. Use Discord for more help.
  • Ideas:
    • Discovery -> Introduction and TDD mechanism.
    • Security -> Bootstrapping Mechanism. How the user can provide it in the runtime.
      • Refactor security to Thing-level, i.e. not part of servient config. node-wot
      • Prompt the user to provide credentials etc.
    • *1 UI Generation based on TD -> Supporting multiple TDs too. A bit like https://demo.home-assistant.io/?edit=1
      • Works on the client side only?
      • First drag-drop a TD, see the affordances and their values (generated UI), choose some to add to your homepage
      • Target Students -> Front End Enthusiast
    • *1 Build an UI library (preferably Tailwind based) of Thing Description aware components ( components useful to build WoT applications )
    • Home Assistant Integration -> Implies using python, we don't have python in Thingweb.
      • Target Students -> Python Enthusiast
    • Home Assistant TD Generation from REST API -> Not sure how it fits to Thingweb. New td-tools folder?
      • Target Students -> API Enthusiast
    • *2 Test Things -> Making it reliable -> Attract cloud infra interested students
    • Website and Documentation
      • Target Students -> Front-end, documentation
    • Examples of Thingweb Component Combinations
      • Target Students -> Polyglots, Interop
    • *2 Adding OpenTelemetry and Observability
      • Target Students -> Cloud Infra
    • *3 Experiment with Raspberry pico 2 (wifi) and Kalumajs
      • Target Students -> Embedded dev
    • *4 High level application framework (integrated with WAM ?)
      • Target Students -> Node.js
    • TD Code integration of td-tools
      • Target Students -> Node.js
    • Implementing Web Thing Protocol
      • Target Students -> Node.js and protocol knowledge
• Website:
  • Documentation: https://hackmd.io/@egekorkan/thingweb-docs
    • JSDoc comments to generate the documentation -> Also, improves the documentation within code.
  • Online Things PR: https://github.com/eclipse-thingweb/website/pull/121
    • Refactoring
• Adopters:
  • What we know of:
    • Ege asked SICK AG -> Asked again.
    • Ege asked LMOS and DT -> Not sure what is the status
    • 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

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