Committer Meeting ‐ 22.12.2023

Attendees

• Ege

Agenda and Minutes

• Short Updates:
  • domus-directory: Python and Triplestore-based, SPARQL support (name still under discussion).
    • Christian will start internal clearing in January.
  • IoT WG Update: ThreadX, Sparkplug, Other groups
  • Next meetings
    • 29.12 and 5.01 cancelled
    • 12.01 with new timing at 11am CET.
      • Biweekly? -> Let's reevaluate when we have more technical discussions.
      • More technical discussions.
• New npm org: Who has stolen thingweb ? npm cli finds no owner. I can create a name dispute at https://support.github.com/contact/npm-name-disputes

  Resolution: New npm organization called thingweb looking like https://www.npmjs.com/org/node-wot. Package names will be @thingweb/MY_TOOL

  • We also need to create a new user who owns the org? Otherwise project leads own the org?
• Google Account issue (no updates): https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/3995
  • Should we just create a new email address and account? Project leads can share the email address password.
• Discussing test-things
  • Positive feedback on this from others in EclipseCon (not necessarily the repo, the general concept)
  • Looking at the initial state, explaining the goal
  • Reviewing Modbus Thing
  • Last time we decided to go for docker containers and later install portainer, and Ege agrees. Green light?
  • How about hosting other services (small APIs) in the same server? E.g. aid conversion and validation as a REST API.
• td-tools: Moving tools there after new releases in respective repos? (naming agreed already: https://github.com/eclipse-thingweb/td-tools/issues/3)
• Important PRs or Discussions in Thingweb Components
  • Anything to add?

Action Items

• Jan to check whether pub.dev accepts dual-license setup.
• Cristiano to update readmes with links. The logo files go to this repository.

Decisions and Resolutions

• Logo: We will have a placeholder for individual components. See example below: