-
Notifications
You must be signed in to change notification settings - Fork 17
Meetings 2026
Micke Nordin edited this page Jan 20, 2026
·
4 revisions
- STA work status update
- Spec work
- Proposal: create a change log with all modifications so far and tag 1.3 + submit to data tracker. See https://github.com/cs3org/OCM-STA/issues/25
- CS3 workshop
- Record number of contributions => the Campfire session on Interoperability and OCM will have to be particularly effective. Giuseppe proposes to approach the 3 major vendors to give a one-slide statement on their plans to support OCM, and there are significant contributions from other actors. A draft schedule will be published soon.
- AOB
- Giuseppe Lo Presti
- Enrique P. Arnaud
- Micke Nordin
- Yul Bahat
- Julian Koberg
- Ron Trompert
- Antoon Prins
- Bo Nygaard Bai
- A few tests are still in need of fix for https://github.com/nextcloud/server/pull/57234 - probably done by end of week, for sure end of month.
- We will create a 1.3 version tag and a 01 version of the spec and ask OCM-WG chairs to start a call for adoption. Micke will tag a version and upload the xml to the data tracker.
We will hold a Campfire session in Oslo - all three major vendors will be there. European Commission may also be represented. Giuseppe will chair and Mahdi will present on the test suite.
Richard will be in Taiwan to present OCM and Micke will do the same in IETF125.
Should we keep a version field in the discovery? We need to talk about it in the Working group and decide, the options are: Prescribe a version with a point release, e.g. 1.4.1 OR prescribe version 1 without points, OR remove version completely.
Should we have a IANA register for protocols, now we have webdav, ssh and webapp, but we allow anything explicitly in the the spec, maybe they can be registered in a registry.