Skip to content

Committer Meeting ‐ 22.12.2023

Jump to bottom
Ege Korkan edited this page Dec 22, 2023 · 10 revisions

Attendees

  • Ege
  • Sebastian
  • Matthias
  • Cristiano

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
      • 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: thingweb is retrieved from Matthias. There is quite a bit of configuration possiblility. Ege to show screen.
    • Should we grab all names in possible platforms? Might get messy soon?
      • pud.dev, pip, maven (java is more decentralized?), cargo, nuget
  • 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.
    • Traefik can do proxying for non HTTP as well but it has to be TLS. -> Use it for HTTP at least and try same for non-HTTP.
    • Ask for a blank slate for the server
    • 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
    • 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: MicrosoftTeams-image
  • Get Thingweb at pud.dev, pip, maven, cargo, nuget
    • 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
  • Ask for a blank slate for the server from Eclipse in next year. Should work before HMI
Clone this wiki locally