Skip to content

Group-owned shares and invites to/from groups #53

Description

@michielbdejong

OCM assumes the sender of a share is a specific user. But in some situations it would be useful to think of shares as owned by a group.

This would mirror the concept of "Group Folders" which exists in some EFSS systems, but across multiple sites.

Activity

  1. michielbdejong commented on Feb 14, 2023

    @michielbdejong
    ContributorAuthor

    Also, share-to-group is possible in the share-with flow of OCM but not in the invite-first flow. We need to think more about this.

    One blocking factor in working on this is that the invite-first flow is so far only implemented in Reva, and I think Reva's groups support is not very extensive yet (at least in the master branch).

  2. changed the title [-]Group-owned shares[/-] [+]Group-owned shares and invites to/from groups[/+] on Feb 14, 2023
  3. smesterheide commented on Mar 9, 2023

    @smesterheide
    Contributor

    Are group owned shares any different from re-shares? Consider a resource (file or folder) owned by a particular user that is being shared with a group. Any member can request to re-share the resource with other users or groups (local or remote) given the necessary permissions. The resource gains more independent shares during the process. In Nextcloud re-shares are handled by the instance that the owner user is home to (notification type REQUEST_RESHARE).

  4. michielbdejong commented on Mar 10, 2023

    @michielbdejong
    ContributorAuthor

    Yes, I think there is a difference. It removes the need to assign a particular group member as the "owner".
    So something like https://apps.nextcloud.com/apps/groupfolders / https://www.youtube.com/watch?v=LaTd-TTj41Q but cross-server! :)

  5. locked and limited conversation to collaborators on Oct 17, 2024
  6. converted this issue into a discussion #152 on Oct 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions