Optimization of member organization #5
Labels
No labels
effort
high
effort
low
effort
medium
good first issue
help wanted
meeting topic
needs changes
needs reporter feedback
needs review
priority
high
priority
low
priority
medium
type/content
type/misc
No milestone
No project
No assignees
3 participants
Notifications
Due date
Dependencies
No dependencies set.
Reference
docs/tickets#5
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Currently, we have at least two groups:
While we're at it, we should also define a process for adding new members to our group(s). The current basic idea is something along the lines of:
@pbokoc wrote in #5 (comment):
This is sensible to me! This is how the Community Ops Team does it too. We have a Forgejo issue form that we use for this here. Feel free to fork/copy it into something useful for the Docs Team!
I opened an infra ticket to request a new FAS group for Quick Docs here: infra/tickets#13260
FAS group has been created, now we just need to add a new team and map the FAS group to it (see forge/forge#501), and to add people from the old Quick Docs repo in pagure to the group.
Users from https://pagure.io/group/quick-docs-committers have been added to the new group.
forge/forge#501 is done, so we now have a group under the Docs org called Quick-Docs-Committers with membership controlled by the forge-docs-quickdocs FAS group.
I believe that's all for this ticket.