Teams: Barebone support #106

Open
opened 2024-05-02 12:32:06 +02:00 by Dalai Felinto · 1 comment

Bugs

  • Any team member should be able to edit any of the extensions.

  • If a user is removed from a team, we need to sanitize the database so that no extension they "exclusively" maintain still has the old Team selected.

Dropdown

  • In the draft_finalise template, if the user is part of any Team, they must pick whether the extension should be part of any team.

The form dropdown:

[ Select ...   ⌄ ]
[ Dalai Felinto  ]
[ Blender Studio ]
[ My Other Team  ]

All this does is set (or not) the "Team" field for the extension.

  • A similar dropdown (minus the "Select ...") is available when Editing an extension. Only for maintainers (not team members).
[ Dalai Felinto  ]
[ Blender Studio ]
[ My Other Team  ]

All this does is set/unset the "Team" field for the extension.

Profile Settings

Future tasks

Writing these down for reference (and in case someone from the community wants to help until it becomes a bigger priority).

If teams proves to be a useful feature, we will still need a way to:

  • It should be possible to create new teams.
  • Team managers should be able to add/remove users.
  • Team managers should be able to grant manage status to other team members.
  • Team managers should be able to delete teams.
## Bugs * [ ] Any team member should be able to edit any of the extensions. * [ ] If a user is removed from a team, we need to sanitize the database so that no extension they "exclusively" maintain still has the old Team selected. ## Dropdown * [ ] In the `draft_finalise` template, if the user is part of any Team, they *must* pick whether the extension should be part of any team. The form dropdown: ``` [ Select ... ⌄ ] [ Dalai Felinto ] [ Blender Studio ] [ My Other Team ] ``` All this does is set (or not) the "Team" field for the extension. * [ ] A similar dropdown (minus the "Select ...") is available when Editing an extension. Only for maintainers (not team members). ``` [ Dalai Felinto ] [ Blender Studio ] [ My Other Team ] ``` All this does is set/unset the "Team" field for the extension. ## Profile Settings * Button to "Leave Team" on the same line as the info. * [x] Front-end * [ ] Back-end * Profile setting, show even when not part of a team. * [ ] Add note on getting in touch via https://projects.blender.org/infrastructure/extensions-website/issues. * [ ] Update the link to use a pre-filled gitea template. ## Future tasks _Writing these down for reference (and in case someone from the community wants to help until it becomes a bigger priority)._ If teams proves to be a useful feature, we will still need a way to: * It should be possible to create new teams. * Team managers should be able to add/remove users. * Team managers should be able to grant manage status to other team members. * Team managers should be able to delete teams.

Most front-end changes have been done or prepared from the tasklist on the new teams-support branch. As most tasks need back-end changes too to step further, I'm leaving the tasks unchecked for now.

Back-end tasks are prepared with TODO: @back-end prefixed todos in templates to make them easier to find.

Most front-end changes have been done or prepared from the tasklist on the new `teams-support` branch. As most tasks need back-end changes too to step further, I'm leaving the tasks unchecked for now. Back-end tasks are prepared with _TODO: @back-end_ prefixed todos in templates to make them easier to find.
Oleg-Komarov self-assigned this 2024-05-17 12:42:04 +02:00
Sign in to join this conversation.
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: infrastructure/extensions-website#106
No description provided.