Skip to content

docs(ocm): clarify contact removal semantics - #426

Merged
glpatcern merged 10 commits into
developfrom
ocm-spec-recipient-removal
Nov 12, 2026
Merged

glpatcern merged 10 commits into
developfrom
ocm-spec-recipient-removal

Conversation

@MahdiBaghbani

@MahdiBaghbani MahdiBaghbani commented Nov 10, 2026 •

Copy link
Copy Markdown
Member

This PR is part of cs3org/OCM-STA#57.

Summary

Keep contact removal limited to the two users involved and preserve existing shares unless separately withdrawn or declined. Distinguish it from user and group departure, and add CONTACT_REMOVED to the notification registry.

Signed-off-by: Mahdi Baghbani <mahdi-baghbani@azadehafzar.io>
Signed-off-by: Mahdi Baghbani <mahdi-baghbani@azadehafzar.io>
Signed-off-by: Mahdi Baghbani <mahdi-baghbani@azadehafzar.io>
Signed-off-by: Mahdi Baghbani <mahdi-baghbani@azadehafzar.io>
Signed-off-by: Mahdi Baghbani <mahdi-baghbani@azadehafzar.io>
Signed-off-by: Mahdi Baghbani <mahdi-baghbani@azadehafzar.io>
Signed-off-by: Mahdi Baghbani <mahdi-baghbani@azadehafzar.io>
Signed-off-by: Mahdi Baghbani <mahdi-baghbani@azadehafzar.io>
Signed-off-by: Mahdi Baghbani <mahdi-baghbani@azadehafzar.io>
Signed-off-by: Mahdi Baghbani <mahdi-baghbani@azadehafzar.io>
@MahdiBaghbani
MahdiBaghbani force-pushed the ocm-spec-recipient-removal branch from e0a3810 to 3a2b594 Compare November 10, 2026 05:44
@MahdiBaghbani MahdiBaghbani self-assigned this Nov 10, 2026
@glpatcern

Copy link
Copy Markdown
Member

To be honest I'm a bit lost with this PR: there are parts that surely are missing and should be merged, but quite many rewritten sections appear to me not very useful, as they make the text longer and more verbose without adding any content - which is typical of LLM-generated text.

I'll try and go for a detailed review soon, not today though!

@MahdiBaghbani

Copy link
Copy Markdown
Member Author

@glpatcern yes true, I wanted to open the PR so Micke and you can see it before working on it more since I almost started working on it from 3rd Nov, and then rebased it a couple time, now I can clean it up and make it properly ready.

The idea I had was written and merged by you in the previous PR and this one is here to address the rest of it.

@glpatcern glpatcern left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, I see the intent and you were right to push it out. I've added comments to many sections, the general comment I have is this needs to be split, and the specific contact removal IMHO can be greatly simplified.

Comment thread IETF-OCM.md Resolved
Comment thread IETF-OCM.md Resolved
Comment thread IETF-OCM.md Resolved
Comment thread spec.yaml Resolved
Comment thread spec.yaml Resolved
Comment thread spec.yaml Resolved
Comment thread spec.yaml Resolved
Comment thread IETF-OCM.md Resolved
Comment thread IETF-OCM.md Resolved
Comment thread spec.yaml Resolved
@MahdiBaghbani
MahdiBaghbani force-pushed the ocm-spec-recipient-removal branch from 3a2b594 to 4e1cef7 Compare November 12, 2026 09:32
@MahdiBaghbani

Copy link
Copy Markdown
Member Author

I have fixed this pr to be in scope of its title

Will open new ones soon to address the other parts of the specification

@glpatcern glpatcern left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

@glpatcern
glpatcern merged commit 691302e into develop Nov 12, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants