Open Cloud Mesh Community Group - Activity in 2024
No matches.
Past meetings
GitHub
cs3org/OCM-API
-
1 issue closed.
-
Milestone 5 "spec text development" cs3org/OCM-API#99.
-
-
1 issue received 1 new comment.
-
1 pull request opened.
-
1 pull request merged.
Past meetings
GitHub
cs3org/OCM-API
-
6 issues closed.
-
Note multiple API endpoint base paths in spec.yaml cs3org/OCM-API#118.
-
Make the spec more modular and backwards compatible? cs3org/OCM-API#106.
-
TODOs in the protocol specification cs3org/OCM-API#159.
-
Discovery caps - Aka is the /mfa-capable endpoint really necessary? cs3org/OCM-API#121.
-
Did we introduce protocol.[webdav|options].URI accidentally cs3org/OCM-API#127.
-
Rethink capability name `/mfa-capable` cs3org/OCM-API#133.
-
-
2 issues received 2 new comments.
-
1 pull request opened.
-
Mark reshare notification as out of scope cs3org/OCM-API#160, by @michielbdejong.
-
-
5 pull requests merged.
-
Prepare v1.2.0 cs3org/OCM-API#89.
-
Openapi 3 cs3org/OCM-API#83.
-
use-code as new requirement + cleaned up superseded references to mfa-capable cs3org/OCM-API#156.
-
Mark reshare notification as out of scope cs3org/OCM-API#160.
-
Caps Disco cs3org/OCM-API#136.
-
-
4 pull requests received 10 new comments.
-
use-code as new requirement + cleaned up superseded references to mfa-capable cs3org/OCM-API#156 (4 comments by @glpatcern, @michielbdejong)
-
Past meetings
GitHub
cs3org/OCM-API
-
3 issues opened.
-
TODOs in the protocol specification cs3org/OCM-API#159, by @glpatcern.
-
Path-to-resource examples in Share endpoint cs3org/OCM-API#157, by @glpatcern.
-
OCM does not cover revoking invitations cs3org/OCM-API#147, by @butonic.
-
-
8 issues closed.
-
Path-to-resource examples in Share endpoint cs3org/OCM-API#157.
-
Possible (other) vendors cs3org/OCM-API#145.
-
Why are email address and name required in Invite Acceptance Request/Response? cs3org/OCM-API#117.
-
OCM does not cover revoking invitations cs3org/OCM-API#147.
-
Are `()` illegal in http header names? cs3org/OCM-API#137.
-
Group-owned shares and invites to/from groups cs3org/OCM-API#53.
-
support sub-shares? cs3org/OCM-API#75.
-
Email field in the invite flow cs3org/OCM-API#142.
-
-
4 issues received 10 new comments.
-
Path-to-resource examples in Share endpoint cs3org/OCM-API#157 (4 comments by @glpatcern, @michielbdejong, @mickenordin)
-
Why are email address and name required in Invite Acceptance Request/Response? cs3org/OCM-API#117 (4 comments by @glpatcern, @MahdiBaghbani, @redblom)
-
-
5 pull requests opened.
-
Improve share access process and share examples cs3org/OCM-API#158, by @glpatcern.
-
use-code as new requirement + cleaned up superseded references to mfa-capable cs3org/OCM-API#156, by @glpatcern.
-
Fixed summary for invite-accepted cs3org/OCM-API#149, by @glpatcern.
-
Explicitly mark invite flow attributes as required cs3org/OCM-API#148, by @MahdiBaghbani.
-
maintenance: fixed URLs to point back to main branch cs3org/OCM-API#146, by @glpatcern.
-
-
5 pull requests merged.
-
Improve share access process and share examples cs3org/OCM-API#158.
-
Explicitly mark invite flow attributes as required cs3org/OCM-API#148.
-
Fixed summary for invite-accepted cs3org/OCM-API#149.
-
Small fix for code spec cs3org/OCM-API#144.
-
maintenance: fixed URLs to point back to main branch cs3org/OCM-API#146.
-
-
1 pull request closed.
-
Explicitly mark invite flow attributes as required cs3org/OCM-API#143.
-
-
4 pull requests received 21 new comments.
-
Explicitly mark invite flow attributes as required cs3org/OCM-API#143 (4 comments by @glpatcern, @MahdiBaghbani, @michielbdejong)
-
use-code as new requirement + cleaned up superseded references to mfa-capable cs3org/OCM-API#156 (2 comments by @glpatcern)
-
Improve share access process and share examples cs3org/OCM-API#158 (2 comments by @glpatcern, @michielbdejong)
Past meetings
Participants
-
1 participant joined.
-
Liz Prescott joined.
-
GitHub
cs3org/OCM-API
-
19 issues opened.
-
Possible (other) vendors cs3org/OCM-API#145, by @MahdiBaghbani.
-
Email field in the invite flow cs3org/OCM-API#142, by @MahdiBaghbani.
-
RFE: DNS-based discovery via TXT records cs3org/OCM-API#141, by @glpatcern.
-
[Maintenance] Shall we restore a short README that points to the I-D document? cs3org/OCM-API#138, by @glpatcern.
-
Are `()` illegal in http header names? cs3org/OCM-API#137, by @michielbdejong.
-
Rethink capability name `/mfa-capable` cs3org/OCM-API#133, by @michielbdejong.
-
Invite Flow improvements cs3org/OCM-API#128, by @michielbdejong.
-
Did we introduce protocol.[webdav|options].URI accidentally cs3org/OCM-API#127, by @michielbdejong.
-
Calling `mfa-enforced` a permission feels weird cs3org/OCM-API#126, by @michielbdejong.
-
Can we drop `singleProtocolNew`? cs3org/OCM-API#125, by @michielbdejong.
-
Discovery caps - Aka is the /mfa-capable endpoint really necessary? cs3org/OCM-API#121, by @michielbdejong.
-
switch content-type from application/hal+json to application/json cs3org/OCM-API#120, by @michielbdejong.
-
SRV DNS record + keyId = a bit of a mess cs3org/OCM-API#119, by @michielbdejong.
-
Note multiple API endpoint base paths in spec.yaml cs3org/OCM-API#118, by @michielbdejong.
-
Why are email address and name required in Invite Acceptance Request/Response? cs3org/OCM-API#117, by @michielbdejong.
-
RFE: list-shares endpoint cs3org/OCM-API#107, by @michielbdejong.
-
Make the spec more modular and backwards compatible? cs3org/OCM-API#106, by @michielbdejong.
-
Discuss `resourceTypes[i].protocols` cs3org/OCM-API#105, by @michielbdejong.
-
Remove `protocol.name` cs3org/OCM-API#104, by @michielbdejong.
-
-
21 issues closed.
-
SRV DNS record + keyId = a bit of a mess cs3org/OCM-API#119.
-
Calling `mfa-enforced` a permission feels weird cs3org/OCM-API#126.
-
[Maintenance] Shall we restore a short README that points to the I-D document? cs3org/OCM-API#138.
-
Invite Flow improvements cs3org/OCM-API#128.
-
invite section first sentence is derailed cs3org/OCM-API#97.
-
Can we drop `singleProtocolNew`? cs3org/OCM-API#125.
-
switch content-type from application/hal+json to application/json cs3org/OCM-API#120.
-
updating shares cs3org/OCM-API#36.
-
Send a notification to a trusted service: enumerate legal values for "type" cs3org/OCM-API#35.
-
create new share: add permission specification cs3org/OCM-API#34.
-
create new share: name vs opaque resource id cs3org/OCM-API#32.
-
Notifications endpoint might also return a 202 accepted cs3org/OCM-API#31.
-
Security proposal: trusted services and shared secrets / request signing cs3org/OCM-API#23.
-
Consolidation of federated sharing and sharing modules cs3org/OCM-API#22.
-
Existing standards cs3org/OCM-API#21.
-
subfiles parameter when getting shares cs3org/OCM-API#16.
-
Provide more specific media type cs3org/OCM-API#12.
-
Discuss `resourceTypes[i].protocols` cs3org/OCM-API#105.
-
Three security concerns I think we can improve on cs3org/OCM-API#100.
-
Framing in terms of GNAP cs3org/OCM-API#80.
-
-
28 issues received 45 new comments.
-
Did we introduce protocol.[webdav|options].URI accidentally cs3org/OCM-API#127 (4 comments by @glpatcern, @michielbdejong)
-
Why are email address and name required in Invite Acceptance Request/Response? cs3org/OCM-API#117 (3 comments by @glpatcern, @MahdiBaghbani, @michielbdejong)
-
Discovery caps - Aka is the /mfa-capable endpoint really necessary? cs3org/OCM-API#121 (3 comments by @glpatcern, @michielbdejong, @mickenordin)
-
SRV DNS record + keyId = a bit of a mess cs3org/OCM-API#119 (2 comments by @glpatcern, @michielbdejong)
-
Make the spec more modular and backwards compatible? cs3org/OCM-API#106 (2 comments by @michielbdejong)
-
cs3org/OCM-API#31 (2 comments by @michielbdejong)
-
cs3org/OCM-API#75 (1 comment by @glpatcern)
-
switch content-type from application/hal+json to application/json cs3org/OCM-API#120 (1 comment by @glpatcern)
-
cs3org/OCM-API#36 (1 comment by @michielbdejong)
-
cs3org/OCM-API#35 (1 comment by @michielbdejong)
-
cs3org/OCM-API#34 (1 comment by @michielbdejong)
-
cs3org/OCM-API#32 (1 comment by @michielbdejong)
-
cs3org/OCM-API#23 (1 comment by @michielbdejong)
-
cs3org/OCM-API#22 (1 comment by @michielbdejong)
-
cs3org/OCM-API#21 (1 comment by @michielbdejong)
-
cs3org/OCM-API#16 (1 comment by @michielbdejong)
-
cs3org/OCM-API#12 (1 comment by @michielbdejong)
-
Security Considerations, from OSW session about RAP and comparing with CIBA-PUSH cs3org/OCM-API#84 (1 comment by @michielbdejong)
-
-
24 pull requests opened.
-
Small fix for code spec cs3org/OCM-API#144, by @MahdiBaghbani.
-
Explicitly mark invite flow attributes as required cs3org/OCM-API#143, by @MahdiBaghbani.
-
Update README.md cs3org/OCM-API#140, by @mickenordin.
-
Restore cover cs3org/OCM-API#139, by @glpatcern.
-
Caps Disco cs3org/OCM-API#136, by @michielbdejong.
-
Internet draft format cs3org/OCM-API#135, by @michielbdejong.
-
Drop DNS-based discovery (and vanity addresses) cs3org/OCM-API#134, by @michielbdejong.
-
MFA: Change from permission to a new concept `requirement` cs3org/OCM-API#132, by @mickenordin.
-
Reworded the protocols section of a new share cs3org/OCM-API#131, by @glpatcern.
-
Update email for internet-draft-format cs3org/OCM-API#130, by @mickenordin.
-
Use pseudo-code for the signature creation and verification examples cs3org/OCM-API#129, by @glpatcern.
-
Get ready for first I-D version cs3org/OCM-API#124, by @michielbdejong.
-
Change response type cs3org/OCM-API#123, by @MahdiBaghbani.
-
Discovery in internet draft cs3org/OCM-API#122, by @michielbdejong.
-
Introduction and Invite Acceptance Request/Response in Internet Draft cs3org/OCM-API#116, by @michielbdejong.
-
Consolidate scope and assumptions section cs3org/OCM-API#115, by @michielbdejong.
-
Slight section rewrite: Accessing the Resource cs3org/OCM-API#114, by @michielbdejong.
-
Slight rewrite of the Share Creation and Share Acceptance sections cs3org/OCM-API#113, by @michielbdejong.
-
Server discovery section cs3org/OCM-API#112, by @michielbdejong.
-
Establishing Contact section cs3org/OCM-API#111, by @michielbdejong.
-
recipientProvider should be an FQDN cs3org/OCM-API#110, by @michielbdejong.
-
Add intro section and terms cs3org/OCM-API#109, by @michielbdejong.
-
Remove required but not existing properties from NewShare? cs3org/OCM-API#108, by @michielbdejong.
-
Spec rewrite cs3org/OCM-API#103, by @michielbdejong.
-
-
24 pull requests merged.
-
Restore cover cs3org/OCM-API#139.
-
Drop DNS-based discovery (and vanity addresses) cs3org/OCM-API#134.
-
Update README.md cs3org/OCM-API#140.
-
MFA: Change from permission to a new concept `requirement` cs3org/OCM-API#132.
-
Reworded the protocols section of a new share cs3org/OCM-API#131.
-
Internet draft format cs3org/OCM-API#135.
-
Use pseudo-code for the signature creation and verification examples cs3org/OCM-API#129.
-
Update email for internet-draft-format cs3org/OCM-API#130.
-
Get ready for first I-D version cs3org/OCM-API#124.
-
Discovery in internet draft cs3org/OCM-API#122.
-
Introduction and Invite Acceptance Request/Response in Internet Draft cs3org/OCM-API#116.
-
Consolidate scope and assumptions section cs3org/OCM-API#115.
-
Slight section rewrite: Accessing the Resource cs3org/OCM-API#114.
-
Slight rewrite of the Share Creation and Share Acceptance sections cs3org/OCM-API#113.
-
Server discovery section cs3org/OCM-API#112.
-
Establishing Contact section cs3org/OCM-API#111.
-
Change response type cs3org/OCM-API#123.
-
recipientProvider should be an FQDN cs3org/OCM-API#110.
-
Add intro section and terms cs3org/OCM-API#109.
-
Remove required but not existing properties from NewShare? cs3org/OCM-API#108.
-
Signing request cs3org/OCM-API#92.
-
Advertise any other protocol in the discovery endpoint cs3org/OCM-API#93.
-
httpsig and short-lived bearer tokens as alternative to sharedSecret cs3org/OCM-API#98.
-
Add sharedSecret back in multipleProtocols example cs3org/OCM-API#101.
-
-
4 pull requests closed.
-
Federation type information at discovery endpoint cs3org/OCM-API#94.
-
Federated contacts public key exchange and signing cs3org/OCM-API#95.
-
Use federatedCloudId instead of email for user identification between servers cs3org/OCM-API#102.
-
Spec rewrite cs3org/OCM-API#103.
-
-
25 pull requests received 124 new comments.
-
Signing request cs3org/OCM-API#92 (17 comments by @ArtificialOwl, @glpatcern, @MahdiBaghbani, @michielbdejong)
-
MFA: Change from permission to a new concept `requirement` cs3org/OCM-API#132 (12 comments by @glpatcern, @michielbdejong, @mickenordin)
-
Reworded the protocols section of a new share cs3org/OCM-API#131 (9 comments by @glpatcern, @michielbdejong, @mickenordin)
-
Drop DNS-based discovery (and vanity addresses) cs3org/OCM-API#134 (8 comments by @glpatcern, @labkode, @michielbdejong)
-
Server discovery section cs3org/OCM-API#112 (8 comments by @glpatcern, @MahdiBaghbani, @michielbdejong, @mickenordin)
-
Use federatedCloudId instead of email for user identification between servers cs3org/OCM-API#102 (8 comments by @MahdiBaghbani, @michielbdejong)
-
Federation type information at discovery endpoint cs3org/OCM-API#94 (7 comments by @glpatcern, @MahdiBaghbani, @michielbdejong)
-
Use pseudo-code for the signature creation and verification examples cs3org/OCM-API#129 (6 comments by @glpatcern, @michielbdejong)
-
Slight section rewrite: Accessing the Resource cs3org/OCM-API#114 (5 comments by @glpatcern, @michielbdejong, @mickenordin)
-
Establishing Contact section cs3org/OCM-API#111 (5 comments by @glpatcern, @michielbdejong, @mickenordin)
-
Slight rewrite of the Share Creation and Share Acceptance sections cs3org/OCM-API#113 (4 comments by @glpatcern, @michielbdejong, @mickenordin)
-
httpsig and short-lived bearer tokens as alternative to sharedSecret cs3org/OCM-API#98 (4 comments by @glpatcern, @michielbdejong)
-
Introduction and Invite Acceptance Request/Response in Internet Draft cs3org/OCM-API#116 (3 comments by @glpatcern, @michielbdejong)
-
Explicitly mark invite flow attributes as required cs3org/OCM-API#143 (2 comments by @glpatcern, @MahdiBaghbani)
-
Federated contacts public key exchange and signing cs3org/OCM-API#95 (2 comments by @MahdiBaghbani, @michielbdejong)
-
Remove required but not existing properties from NewShare? cs3org/OCM-API#108 (2 comments by @MahdiBaghbani, @michielbdejong)
-
Past meetings
Participants
-
1 participant joined.
-
Maxence Lange (Nextcloud Gmbh) joined.
-
GitHub
cs3org/OCM-API
-
3 issues opened.
-
Three security concerns I think we can improve on cs3org/OCM-API#100, by @michielbdejong.
-
Milestone 5 "spec text development" cs3org/OCM-API#99, by @michielbdejong.
-
invite section first sentence is derailed cs3org/OCM-API#97, by @michielbdejong.
-
-
1 issue closed.
-
Why use refresh tokens? cs3org/OCM-API#88.
-
-
4 issues received 10 new comments.
-
10 pull requests opened.
-
Use federatedCloudId instead of email for user identification between servers cs3org/OCM-API#102, by @MahdiBaghbani.
-
Add sharedSecret back in multipleProtocols example cs3org/OCM-API#101, by @michielbdejong.
-
httpsig and short-lived bearer tokens as alternative to sharedSecret cs3org/OCM-API#98, by @michielbdejong.
-
Make DNS-based discovery optional cs3org/OCM-API#96, by @michielbdejong.
-
Federated contacts public key exchange and signing cs3org/OCM-API#95, by @MahdiBaghbani.
-
Federation type information at discovery endpoint cs3org/OCM-API#94, by @MahdiBaghbani.
-
Advertise any other protocol in the discovery endpoint cs3org/OCM-API#93, by @glpatcern.
-
Signing request cs3org/OCM-API#92, by @ArtificialOwl.
-
/invitation-accepted remove 404 status cs3org/OCM-API#91, by @mickenordin.
-
/invitation-accepted Reword description cs3org/OCM-API#90, by @mickenordin.
-
-
3 pull requests merged.
-
Make DNS-based discovery optional cs3org/OCM-API#96.
-
/invitation-accepted Reword description cs3org/OCM-API#90.
-
/invitation-accepted remove 404 status cs3org/OCM-API#91.
-
-
6 pull requests received 23 new comments.
-
Advertise any other protocol in the discovery endpoint cs3org/OCM-API#93 (3 comments by @glpatcern, @MahdiBaghbani)
-
httpsig and short-lived bearer tokens as alternative to sharedSecret cs3org/OCM-API#98 (2 comments by @michielbdejong)
Past meetings
Past meetings
Participants
-
2 participants joined.
-
Björn Schießle (Nextcloud Gmbh) joined.
-
Andreas Klotz (Helmholtz-Zentrum Berlin) joined.
-
-
2 organizations joined.
-
Nextcloud Gmbh joined.
-
Helmholtz-Zentrum Berlin joined.
-
GitHub
cs3org/OCM-API
-
1 issue opened.
-
Why use refresh tokens? cs3org/OCM-API#88, by @michielbdejong.
-
-
1 issue closed.
-
Server alias cs3org/OCM-API#38.
-
-
1 issue received 1 new comment.
-
cs3org/OCM-API#38 (1 comment by @glpatcern)
-
-
1 pull request opened.
-
Clarify access methods cs3org/OCM-API#87, by @glpatcern.
-
-
3 pull requests merged.
-
Introduce a .well-known discovery endpoint and DNS SRV records cs3org/OCM-API#82.
-
Clarify access methods cs3org/OCM-API#87.
-
clarify sharedSecret usage cs3org/OCM-API#86.
-
-
1 pull request closed.
-
Convert to OpenAPI 3.0 cs3org/OCM-API#64.
-
-
5 pull requests received 15 new comments.
-
Introduce a .well-known discovery endpoint and DNS SRV records cs3org/OCM-API#82 (8 comments by @DanScharon, @glpatcern, @mickenordin)
-
cs3org/OCM-API#64 (1 comment by @glpatcern)
-
Past meetings
Participants
-
2 chairs appointed.
-
Michiel de Jong became a chair.
-
Giuseppe Lo Presti became a chair.
-
-
1 participant joined.
-
Andreas Klotz (Helmholtz-Zentrum Berlin) joined.
-
-
1 participant left.
-
Andreas Klotz (Helmholtz-Zentrum Berlin) left.
-
-
1 organization joined.
-
Helmholtz-Zentrum Berlin joined.
-
-
1 organization left.
-
Helmholtz-Zentrum Berlin left.
-
GitHub
cs3org/OCM-API
-
2 issues opened.
-
Sequence Diagrams cs3org/OCM-API#85, by @michielbdejong.
-
Security Considerations, from OSW session about RAP and comparing with CIBA-PUSH cs3org/OCM-API#84, by @michielbdejong.
-
-
1 issue closed.
-
Trade in shared secret for an OAuth-grade refresh/access token? cs3org/OCM-API#81.
-
-
3 issues received 5 new comments.
-
Trade in shared secret for an OAuth-grade refresh/access token? cs3org/OCM-API#81 (2 comments by @butonic, @michielbdejong)
-
Security Considerations, from OSW session about RAP and comparing with CIBA-PUSH cs3org/OCM-API#84 (1 comment by @michielbdejong)
-
-
2 pull requests opened.
-
clarify sharedSecret usage cs3org/OCM-API#86, by @butonic.
-
-
2 pull requests received 2 new comments.
Participants
-
3 participants joined.
-
Magnus Andersson (SUNET) joined.
-
Richard Freitag (SUNET) joined.
-
Jonathan Xu (Seafile Ltd.) joined.
-
-
1 organization joined.
-
Seafile Ltd. joined.
-
GitHub
cs3org/OCM-API
-
1 issue opened.
-
Trade in shared secret for an OAuth-grade refresh/access token? cs3org/OCM-API#81, by @michielbdejong.
-
-
1 issue received 2 new comments.
-
Trade in shared secret for an OAuth-grade refresh/access token? cs3org/OCM-API#81 (2 comments by @michielbdejong)
-
-
1 pull request opened.
-
Introduce a .well-known discovery endpoint and DNS SRV records cs3org/OCM-API#82, by @glpatcern.
-
-
2 pull requests merged.
-
Add MFA capability and permission cs3org/OCM-API#79.
-
Add notification when a trusted user is removed cs3org/OCM-API#78.
-
-
1 pull request received 5 new comments.
GitHub
cs3org/OCM-API
-
1 issue opened.
-
Framing in terms of GNAP cs3org/OCM-API#80, by @michielbdejong.
-
-
1 issue received 2 new comments.
Participants
-
1 participant joined.
-
Mikael Nordin (SUNET) joined.
-
-
1 organization joined.
-
SUNET joined.
-
GitHub
cs3org/OCM-API
-
1 issue closed.
-
Are notifications allowed to have side-effects? cs3org/OCM-API#46.
-
-
1 pull request opened.
-
Add MFA capability and permission cs3org/OCM-API#79, by @mickenordin.
-
-
1 pull request merged.
-
Improved spec for notifications cs3org/OCM-API#77.
-
-
2 pull requests received 5 new comments.
-
cs3org/OCM-API#77 (1 comment by @glpatcern)