#13037 [Forgejo] New Organization and Teams Request: Flock
Closed: Migrated to Fedora Forge by ryanlerch. Opened by jflory7.

Hello Fedora Infra Team,

I would like to request the creation of a new organization and associated teams in Fedora Forge.

1. New Organization Details:

Desired Organization Name (Short Name):
flock

Full Name of Organization:
Flock to Fedora Organizers Team

Description of Organization's Purpose:
This organization will host repositories and manage collaboration for the Flock to Fedora Organizers Team, focusing on event planning, documentation, and coordination for our annual contributor conference.

Website URL (Optional):
https://fedoraproject.org/flock/

Avatar/Logo (Optional):
Flock logo or any fun Colúr-based mascot image (FYI @ekidney @madelinepeck)

Fedora Accounts Group for Organization Owners:
forge-flock-owners

Fedora Accounts for Organization Owners Group:
@amoloney, @dvolavko, @jasonbrooks, @jflory7, @jonatoni, @jspaleta, @shaunm

2. New Team Details (within 'flock' organization):

Team 1: Core

  • Target Organization Name: flock
  • Team Name: core
  • Description of Team's Purpose: Flock core staff members accountable for end-to-end event success.
  • Desired Permission Level in Forgejo: Write
  • Fedora Accounts Group to Map to Team: forge-flock-owners
  • Include all repositories?: Yes, this team should have write access to all current and future repositories in 'flock'.

Team 2: Members

  • Target Organization Name: flock
  • Team Name: members
  • Description of Team's Purpose: All team members involved with Flock.
  • Desired Permission Level in Forgejo: Write
  • Fedora Accounts Group to Map to Team: flock-team (see #13036)
  • Include all repositories?: Yes, this team should have write access to all current and future repositories in 'flock'.

Team 3: Communications

  • Target Organization Name: flock
  • Team Name: comms
  • Description of Team's Purpose: Communications team responsible for outreach, messaging, blogging, and social media.
  • Desired Permission Level in Forgejo: Write
  • Fedora Accounts Group to Map to Team: Can we manage team membership dynamically from Forgejo? Or must all teams be defined in FAS? Ideally, here we can delegate different roles to different people involved with parts of Flock organizing. The visual distinction of the teams is what is helpful for me.
  • Include all repositories?: Yes, this team should have write access to all current and future repositories in 'flock'.

Please let me know if any further information is required.


Metadata Update from @zlopez:
- Issue priority set to: Waiting on Assignee (was: Needs Review)
- Issue tagged with: forgejo_migration, low-trouble, medium-gain

Metadata Update from @ryanlerch:
- Issue assigned to ryanlerch

@jflory7 a bit confused by this one -- teams in forgejo are used for managing access to repos -- if the permissions are the same for members v communications, then there is no need for communications to be a seperate team.

This issue has been migrated to Fedora Forge:
https://forge.fedoraproject.org/infra/tickets/issues/13037

Please continue any further discussion there.

Metadata Update from @ryanlerch:
- Issue close_status updated to: Migrated to Fedora Forge
- Issue status updated to: Closed (was: Open)

Metadata