[FR] Team calendars, Team addressbooks
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 36.9k
- Forks
- 5.2k
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 713
Description
How to use GitHub
- Please use the 👍 reaction to show that you are interested into the same feature.
- Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
- Subscribe to receive notifications on status change and new comments.
Feature description
There should be a basic concept called "Team resources" not only for Team folders but for any type of resource intended to be shared
Is your feature request related to a problem? Please describe.
Some scenarios are based in equal users and not in "superaccounts" with resources to be shared to others. All the sense of working with "Team folders" is applicable to other resources because it's the team and not a casual user who owns resources, quotas, etc.
Describe the solution you'd like
Extend "Team" concept to be able to create "Team folders", "Team calendars", "Team addresbooks" and other team shareable objects. Each object with its sharing options.
Describe alternatives you've considered
Abstract "Team" concept to create teams with their names, and link them folders, calendars, etc.
This could make simpler to a user have access to whole team resources only by belonging to a group that receives shares.
Additional context
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing how the existing Team folders concept and sharing options are represented. Define what shared team calendars and addressbooks should support, including team membership and per-object sharing, and confirm that the broader Team resources model covers the requested objects.
Written by the indexing model from the issue text.
Assessment
- Domain
- full-stack
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100