Better integration of contacts, users and groups #4493
Labels
1. to develop
Accepted and waiting to be taken care of
design
Design, UI, UX, etc.
enhancement
feature: federation
feature: sharing
feature: users and groups
spec
With there being more sharing, federation etc the proper integration of how we handle users and groups becomes very important.
Now before we develop more into three different directions with the user management, Contacts app and now even Circles, we should see where we can consolidate.
I had a call with @daita of the Circles app and we talked about a few things. The best course of action seems to make Circles a backend-only app and have everything which you could do via the interface be integrated into existing parts of Nextcloud. And also some additional thoughts.
Example
In my Contacts app I have a few people, among them:
Now if I create a Group with all of these people and share something with that Group, it should be shared in the most ideal way with everyone:
Tasks
Connect own Contacts entry and Personal settings info: You should be able to set a Contacts entry as »Yourself« like in Android and iOS too. That contacts entry should be connected to your personal profile.
Connect Contacts entries with other people’s personal settings info, basically like a federated phonebook / Facebook.
Suggest Contacts from sharing
Different visibility / levels of Contact groups: Just like Circles has different levels of visibility, we could have that in Contacts. It could be implemented by using the 3-dot-menu for each group, and having a selector »Local«, »Contacts«, »Public« (or other options) much like the Personal settings.
Users should only see one term for »Groups« – not »Circles« or »Teams« or something like that. That’s confusing.
In the Mail app, enable people to send mails to entire Contact groups. Ref Sending to groups [$150 awarded] mail#41
more ideas?
cc @nextcloud/sharing @nextcloud/contacts @daita @schiessle @ChristophWurst @irgendwie @Henni @LukasReschke @oparoz
The text was updated successfully, but these errors were encountered: