Optimization of member organization #5

Closed
opened 2026-01-27 11:45:19 +00:00 by pboy · 6 comments
Owner

Currently, we have at least two groups:

  • The (core) docs team
  • The Quickdocs team
Currently, we have at least two groups: - The (core) docs team - The Quickdocs team
pboy added this to the (deleted) project 2026-01-27 11:45:50 +00:00
pboy modified the project from (deleted) to (deleted) 2026-01-27 11:46:01 +00:00
pboy modified the project from (deleted) to (deleted) 2026-01-27 11:46:10 +00:00
Owner

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:

  • Open a nomination ticket, something along the lines of #20
  • Ticket should be open for at least a week and requires 3 +1s and no -1s from current group members
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: * Open a nomination ticket, something along the lines of https://forge.fedoraproject.org/docs/tickets/issues/20 * Ticket should be open for at least a week and requires 3 +1s and no -1s from current group members
Owner

@pbokoc wrote in #5 (comment):

  • Open a nomination ticket, something along the lines of #20
  • Ticket should be open for at least a week and requires 3 +1s and no -1s from current group members

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!

@pbokoc wrote in https://forge.fedoraproject.org/docs/tickets/issues/5#issuecomment-596998: > * Open a nomination ticket, something along the lines of #20 > * Ticket should be open for at least a week and requires 3 +1s and no -1s from current group members 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](https://forge.fedoraproject.org/commops/tickets/src/branch/main/.forgejo/issue_template/new-member.yml). Feel free to fork/copy it into something useful for the Docs Team!
jflory7 added the due date 2026-04-07 2026-04-01 13:16:02 +00:00
jflory7 modified the project from (deleted) to (deleted) 2026-04-01 13:18:37 +00:00
Owner

I opened an infra ticket to request a new FAS group for Quick Docs here: infra/tickets#13260

I opened an infra ticket to request a new FAS group for Quick Docs here: https://forge.fedoraproject.org/infra/tickets/issues/13260
Owner

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.

FAS group has been created, now we just need to add a new team and map the FAS group to it (see https://forge.fedoraproject.org/forge/forge/issues/501), and to add people from the old Quick Docs repo in pagure to the group.
Owner

Users from https://pagure.io/group/quick-docs-committers have been added to the new group.

Users from https://pagure.io/group/quick-docs-committers have been added to the new group.
Owner

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.

https://forge.fedoraproject.org/forge/forge/issues/501 is done, so we now have a group under the Docs org called [Quick-Docs-Committers](https://forge.fedoraproject.org/org/docs/teams/quickdocs) with membership controlled by the [forge-docs-quickdocs](https://accounts.fedoraproject.org/user/pbokoc/) FAS group. I believe that's all for this ticket.
Sign in to join this conversation.
No description provided.