👥 Teams

[juliusknorr]

Issues in scope

• Renaming circles to 'Teams' circles#1505
• Teams dashboard widget circles#1506
  • feat: Implement teams dashboard widget circles#1510
  • fix: Disable dashboard widget if no frontend is available circles#1519
  • fix(dashboard): Add icon-teams CSS class and fix path to app icon circles#1520
• Renaming contacts app to 'people' contacts#3816
• Team (circle) overview page contacts#3817
• API for teams #43683
  • Implement team provider api #43855
• Improve related resource listing for teams related_resources#360
  • feat: List team resources in related resources panel nextcloud-libraries/nextcloud-vue#5316
  • Release library
  • Bump in apps
• Overview page collectives#1121
• Team resource providers for apps that share with circles or own resources by a circle
  • feat: Implement a team resource provider deck#5625
  • feat: Implement a team resource provider collectives#1130
  • Files feat: Implement team resource provider for shared files circles#1525
  • Talk feat: Implement team resource provider spreed#11741
  • Calendar Implement a team resource provider calendar#5842
  • Groupfolders Implement a team resource provider  groupfolders#2845

Stretch goal

• Add a configurable emoji for each circle circles#1508

Polishing

• Dashboard API widget improvements #44087

Out of scope for now

• Generic way of sharing to a team (through overview page)

Previous discussions

Discussion

• Based on circles, a circle can be used to create a space for a team or project
  • We can reuse existing logic in apps
• Breaking this down to smaller workable tasks
• Competitors have similar concepts (Sharepoint, confluence, notion, Dropbox)
• Further input Ideas about Circles circles#1456

As discussed in the planning call we should aim for a cross app/team implementation of this, so the UI flow to create a new project can be reused.

• Clarify with design
  • How does the flow to create a new project look like for individual apps
  • How does the flow of adding a resource to a project look like
• Clarify technical architecture
  • As we aligned on making this based on circles, my suggestion would be to come up with a generic server API for listing, creating, updating, deleting projects and adding/removing ressources to it. Circles can hold the implementation of this API.
  • Another part can be providers for the resources which then can be implemented in the individual apps. I'll outline my idea there in more detail to discuss further in the team
• Split MVP in individual tasks
• Involve other teams where relevant

Unified entrypoint

• Allow users to create a team/project with required resources
• Give people an overview and quick navigation to all relevant resources
• Future idea, provide a customizable dashboard like entrypoint
• Using collectives
  • Collectives already has a shared ownership model, there is a circle automatically created for each collective
  • There are some things that we could nicely reuse for an iterative process of developing such features
  • Collective somehow matches in naming to also cover more then just wiki/knowledge base
  • Also matches the vision Jonas/Max had to be more then just a wiki
• Using contacts UI in circles
  • We got feedback that this is not discoverable (not where users expect it)
• Separate App / UI
  • Might be better from feature visibility perspective
  • Might give admins a better overview / management interface
  • Larger development effort then reusing existing parts for now
  • Introduces yet another concept

Suggestion of features to implement:

• Extend the collectives app to allow creating other resources
  • Those will be shared automatically with this circle
  • Find a generic approach / API to expose such providers
  • Decide on what apps should be supported and involve other teams
• We display the common resources in Collectives (e.g. navigation or landing page)
• This should be a reusable component so it can be added to other apps

Cross reference

• Reuse related resources
• Apps could allow creating other resources directly, e.g. when creating a talk room have a checkbox to also create a project with a corresponding collective and deck board

Suggestion of features to implement:

• Together with design team: Prioritize circle project relations and show them more prominent, grouped

Shared ownership

• We can start with sharing to the circle, for now ownership transfer is a workaround
• Later on we can extend individual apps to have a ownership model of a circle

Suggestion of features to implement:

• Together with the design team: Explore who this could work UI wise

Out of scope / for future iterations

• ⭕📑👥 Integration of Projects and Teams into Dashboard #22897

[pschopen]

Maybe this can serve as inspiration: #38615

[roberix]

Hi.

Incredible feature announcement and more than useful.

As enterprise customer I am looking forward to have this implemented.

I hope it will be build around a full featured project centric files store which might replace the neglectfully treated group folders app.

In the end files are still the core in NC I guess.

Crucial features we think should be considered.

• Quotas per project
• Versions for files (not like group folders half baked)
• Tags with scope of project/limited to project

Thank you.

Regards

Rob

[juliusknorr]

Notes from the design discussion:

• Key apps: files, deck, talk, calendar
• Mockup for create new project dialog from within circles
• Mockup for collective overview page for project resources
  • Landing page recent pages and members can move to this page
  • Needs to list resources
  • Needs to manage resources
• Mockup of related resources showing projects and its resources
  • Decided to just link to collectives for the first MVP for create new project/add to project
• All collectives are a project but showing up as such once some other resource is added
• Potential "rebranding" based on new scopes (icon, maybe still call collectives, marketing)

[juliusknorr]

• ocs
  • list resource providers
  • create new resource for project (create and share with circle or make the circle the owner)
  • remove resource from project (deletes)
  • list resources for project
  • optional: list projects for user (or entity, see open questions)
• ocp
  • register resource provider
  • provider interface with
    • provider name (e.g. deck)
    • provider entity (e.g deck board)
    • icon as svg
    • create new resource for project
    • remove resource from project
• apps implementing the provider interface
• open questions:
  • one resource in multiple projects
    • how to handle this? Sharing would still allow to share a deck board to multiple circles but it would conflict with the goal of the shared ownership concept for a project and its resources

[marcoambrosini]

Here are the final mockups:

Collectives
prototype
dev link

Other apps proectj picker flow
prototype
dev link

[juliusknorr]

After the discussion we had, I have tried to summarize the outcome and separated this into the following individual tasks, to be filed as individual issues once confirmed:

Teams dashboard widget

• Should list all teams (circles) a user is part of
• Should allow to expand a team to list all items that are shared with this specific team
• Should offer a button to navigate to the team management within contacts
• Requires mockup

Renaming circles to 'Teams'

• Rename any user facing parts that mention Circle to Team and Circles to Teams

Renaming contacts app to 'people'

• Rename the contacts app to People

Improvements to contacts app team view (circles management)

• Simplify UI to hide advanced settings
• Add a related resource list to list all resources that are shared with a team

Related resources for listing teams and the related resources of it in individual apps

• Should list teams that this item is part of
• Should provide other resources that are part of the same team
• Prioritize larger entities (e.g. folders) over small ones (e.g. files) (The related 'files' are less important then related Talk rooms, Group-folders, Calendars,... So the files should be on the bottom. You can see the problem in our Engineering room)
• Requires mockup based on existing related resources

Related resources on Collective page

• Based on the current overview mockups and releated resources

---

Not in scope for now

• New mechanism of adding existing resources to teams (sharing will be used) and we don't want to introduce another concept
• Create a new team from other places (e.g. dashboard widget, collectives), we guide users to the contacts app for now

[karlitschek]

looks good. Missing is an example 'Team' that exists by default. And the Teams widget should be one of the default widgets.

[karlitschek]

Another thing related to 'related ressources'. The related 'files' are less important then related Talk rooms, Group-folders, Calendars,... So the files should be on the bottom. You can see the problem in our Engineering room.

[AndyScherzinger]

Improvements to contacts app team view (circles management)

Simplify UI to hide advanced settings

Fine as long as hiding means the functionality is still available since circles is heavily used by some of our customers

[maximelehericy]

I like this, it looks promising :)

[sunjam]

Rename the contacts app to People

Quick thought: contacts is the term used by Android, iOS, Windows, email clients, etc. 🤷
Contacts reads as very clear and to the point, but use people if that makes more sense. ❤️

[strugee]

@juliushaertl fyi you missed the README of nextcloud/deck - not sure if docs are in scope for this ticket

[juliusknorr]

Most relevant parts are in, closing as the rest is tracked in follow up issues.

[CoreyBurger]

I added this comment on the Circles issue, but thought I would put it here too:

Can I add a comment here - Teams is a truly terrible name for this project. Assuming it survives trademark issues with MS, I strongly suggest you rename it back to Circles. Why?

There are three groups looking for information under the term "Nextcloud Teams"

People looking to integrate Nextcloud with Teams (the MS one that everybody just calls teams)
People looking to compare Teams (the MS one) to Nextcloud
People looking for information on Nextcloud Teams

All 3 are going to be tripping all over each other and be massively confused.

Circles was unique. Nobody used it, why it worked so well.

Please rename this back

[marcoambrosini]

@CoreyBurger the word "teams" is ubiquitous and used in all kinds of collaboration software. It expresses the concept of a group of people working together in a much clearer way to our users. There are no trademark issues here :)
We won't diminish our user experience and avoid using an effective word simply because a competitor uses it for one of their products.

[CoreyBurger]

The word teams might be used by lots of people, but when it comes to collaboration software, if you say teams, most people mean Teams (the MS one). This is just needless confusion when an existing name (circles) existing and was unique

[sunjam]

Circles name is taken directly from Google+ Circles. It was never unique, by design. Either way, it is the company's choice. Points have been shared, so no need to continue saying the same thing.

https://duckduckgo.com/?q=google%2B+circles&t=fpas&ia=web

[jakobroehrl]

What about adding the tables app to this?

[jancborchardt]

@jakobroehrl @pschopen yep, there is an issue open for this at nextcloud/tables#142 :)