-
Notifications
You must be signed in to change notification settings - Fork 1
Committer Meeting ‐ 20.10.2023
Ege Korkan edited this page Oct 20, 2023
·
6 revisions
- Ege Korkan
- Matthias Kovatsch
- Jan Romann
- Daniel Peintner
- Cristiano Aguzzi
- Pedram Hadjian
- EclipseCon: Reporting on the Event
- Short Update on New Components:
- domus-directory: Python and Triplestore-based, SPARQL support. Namedomus-directory (name still under discussion). Status
- dart_wot: Approved at https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/3767
- Zion from VAIMEE: Under discussion internally
- Logo Discussion
- Documented under decisions
- Hosting Playground at Netlify? -> moving plugfest landing page to /plugfest kind of location?
- td-tools
- One language or not?
- We start with one language now. Once we figure out the binary distribution, we can accept other languages if they accept to follow the distribution mechanism to provide binaries
- Distributing binaries or not?
- npx (npm cli): Already works with node-wot if you provide at least one argument (e.g. npx @node-wot/cli --help)
- Platform-specific package manager (later on)
- npm pipeline (npm install, npm build, link to root)
- See: https://github.com/eclipse-thingweb/node-wot/issues/1033 and https://github.com/eclipse-thingweb/td-tools/pull/1
- Last week's opinions
- Cris: It would be better to have different packages. We can start by moving them and then splitting them into different packages.
- Ege: I think also too. We have to name the packages.
- Matthias: I would expect something like the node-wot, one repo but multiple module packages.
- Cris: We can use
@thingweb/node-wot/core
. - Matthias: It would create too much work for us and users too. We can go for
@td-tools
- Jan: We can regroup for 1.0 release.
- One language or not?
- Readme alignment in general
- Header can be "Eclipse Thingweb - component name"
- How to align all the readmes? Will be the next meeting discussion
- Discussing test-things
- Positive feedback on this from others in EclipseCon (not necessarily the repo, the general concept)
- Next week screen share to understand where to place the component name in the logo.
- Thingweb Logo stays the same as a generic one. The SVG of the logo will have a placeholder to put the name of the component.
- Hosting Playground at Netlify, moving plugfest.thingweb.io to /plugfest and then asking Eclipse to redirect.
- TD Tools will accept any tool that outputs or takes a TD/TM. All tools need to offer at least a basic CLI experience. First only Node.js but we will accept others later on.
- Home
- Organizational Documentation
-
Meetings
- Committer Meeting 28.02.2025
- Committer Meeting 14.02.2025
- Committer Meeting 31.01.2025
- Committer Meeting 13.12.2024
- Committer Meeting 06.12.2024
- Committer Meeting 15.11.2024
- Committer Meeting 25.10.2024
- Committer Meeting 18.10.2024
- Committer Meeting 11.10.2024
- Committer Meeting 04.10.2024
- Committer Meeting 27.09.2024
- Committer Meeting 20.09.2024
- Committer Meeting 02.08.2024
- Committer Meeting 26.07.2024
- Committer Meeting 12.07.2024
- Committer Meeting 05.07.2024
- Committer Meeting 28.06.2024
- Committer Meeting 14.06.2024
- Committer Meeting 07.06.2024
- Committer Meeting 31.05.2024
- Committer Meeting 17.05.2024
- Committer Meeting 03.05.2024
- Committer Meeting 26.04.2024
- Committer Meeting 19.04.2024
- Committer Meeting 12.04.2024
- Committer Meeting 05.04.2024
- Committer Meeting 15.03.2024
- Committer Meeting 08.03.2024
- Committer Meeting 01.03.2024
- Committer Meeting 23.02.2024
- Committer Meeting 16.02.2024
- Committer Meeting 02.02.2024
- Committer Meeting 26.01.2024
- Committer Meeting 19.01.2024
- Committer Meeting 12.01.2024
- Committer Meeting 22.12.2023
- Committer Meeting 01.12.2023
- Committer Meeting 24.11.2023
- Committer Meeting 17.11.2023
- Committer Meeting 03.11.2023
- Committer Meeting 27.10.2023
- Committer Meeting 20.10.2023
- Committer Meeting 13.10.2023
- Committer Meeting 06.10.2023
- Committer Meeting 29.09.2023
- Committer Meeting 22.09.2023