-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Description
Problem to solve
The new Teams & projects feature allows users to create teams and invite team members. Team members ca add repositories as projects that can be part of only one team. There are use cases where users with proper permissions1 are trying to add projects but are not able to add the repository in a new team.
Currently, we inform the user when the project is already part of the proejct but it's not clear a) which user has added that project or b) which team currently owns the project, see also #5119 and #5128.
Commonly, the user who added a project in a team and the user who is tryng to add the project to a team are already collaborators for the same repository with proper permissions to add the repository as project. However, there's no way
Proposal
Eventually, we could need a way to allow users to request access to a team which owns a shared project for which users contribute to. This can be used when
The following will probably need to become separate issues:
- A good first MVC (minimum viable change) could be to allow to request access to a team when a user is trying to add a project that is already part of another team. This would also require to provide team owners a way to see pending requests and approve or reject.
- Next steps could include a) introducing public team pages where users could request access to a team and b) team owners can approve or reject requests.
- Other improvements could include suggesting teams top join that a) include projects from GitHub orgs or GitLab groups you are a member of or b) teams created from users using the same domain name with you.
- ...
Footnotes
-
Proper permissions include the ability to install the GitHub app or add repository webhooks for GitLab, etc. ↩
Metadata
Metadata
Assignees
Labels
Type
Projects
Status