Committer Meeting ‐ 12.01.2024

Attendees

• Ege
• Christian
• Matthias
• Jan
• Cristiano
• Daniel

Agenda and Minutes

• Short Updates:
  • domus-directory: Python and Triplestore-based, SPARQL support (name still under discussion).
    • Christian will start internal clearing in January.
  • Next meetings: Goal is to transition to biweekly and have more technical discussions. To be evaluated over time
• Orgs in pub.dev, npm, nuget, pypi
  • cargo: when someone publishes a package, they can add github:org:team (e.g. github:rust-lang:owners) to that crate. No need to hunt thingweb, just agreeing on the naming scheme at that point would be needed.
  • pypi: request sent.
  • nuget: https://www.nuget.org/profiles/thingweb
• 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
  • Traefik proxy PR: https://github.com/eclipse-thingweb/test-things/pull/18
    • Ege to test in home setup with opening ports as well
    • Vaimee uses it for their setups
    • Can work with Modbus with TLS (Vaimee explored it)
    • Portainer can also use multiple compose files (more logical grouping)
  • Asking for a blank slate for the server once docker compose is set?
    • At the same time, removing playground
  • node-wot Things: counter etc. should stay there since they are used for starters
    • One option:Push node-wot examples docker images to dockerhub with each release. This means maintaining Dockerfiles in node-wot. It makes it easier for newcomers to test.
    • We should review the examples pipeline. Keep the simple examples in node-wot but move the "complex" ones to test-things. This means differentiating tutorial things and protocol testing things in test-things.
• 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
  • Discoverer Consumer Architecture in node-wot

Action Items

• Jan to check whether pub.dev accepts dual-license setup.
  • It is possible (no AND or OR relationship but at least possible)
• Cristiano to update readmes with links of the logo. The logo files go to this repository.
• Ask for a blank slate for the server from Eclipse in next year. Should work before HMI

Decisions and Resolutions

• Move anything but counter example to test-things and integrate to the docker compose. node-wot should have one-shot examples of how to use it for the ones who clone the repo.