-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Introducing new share type #29
Comments
Hey all, it might be helpful to distinguish between the federated group share in a general sense and the implementation of said share type as a Virtual Organisation (VO) group share I am currently working on. Can we treat this as one and the same @schiessle? The VO groups are managed outside of Nextcloud and users might already be familiar with existing icons in this context. I will check and report back on that. Thanks for the suggestions @tobiasKaminsky! I like the regular group icon as shown for "group". Maybe we can use a variation of that to highlight that we are dealing with a special type of group. |
@nextcloud/designers as also Björn mentioned in first post, federated group shares should have a different icon. |
The icon can/should be the same as the group icon you mentioned @tobiasKaminsky. That it’s a federated share is communicated in the sidebar, nothing we need to press into the icon. :) |
@schiessle @smesterheide once you have a PR on server ready to test, I am happy to give it a try on Android |
We are in the process of developing federated group sharing in a way that for example in a Global Scale setup every member of a group gets access to the share, no matter on which Nextcloud server the user is located.
If you are interested you can find all the documents and the detailed description here: https://cloud.nextcloud.com/index.php/f/6222227
Therefore we need the clients to know the new share type and handle it properly:
The main developer on the server side will be @smesterheide supported by @come-nc
cc @tobiasKaminsky for your reference, as discussed
The text was updated successfully, but these errors were encountered: