Skip to content

Regularize all team names #100

Open
Open

Description

@Rabia2219

Overview

We need to revise the teams so that the names are consistent across all teams.

Details

We will be changing the team names to reflect the permissions given

  • project-team-name-admins becomes project-team-name-admin
  • project-team-name-maintainers becomes project-team-name-maintain
  • project-team-name-writers becomes project-team-name-write
  • project-team-name becomes project-team-name-read

Action Items

  • Add the teams to the spreadsheet by going to pages 2-5 and opening each team, then screenscraping the results into chatgpt with the prompt (resource 1.05)
  • go to resource 1.01 and change any team that is called maintainers to maintain
  • go to resource 1.02 and change any team that is called admins to admin
  • find all the project names teams and add read to it

Resources/Instructions

I am going to paste multiple screen scrapes of GitHub teams (starting with page 2).

Your task:
1. Convert the data into a clean markdown table.
2. Use these columns exactly:
   - Team Name
   - Parent
   - Description
   - Members
   - Roles
   - Teams

3. Infer the "Parent" column using naming conventions:
   - If a team name contains a suffix like:
     - -write
     - -admin / -admins
     - -maintain / -maintainer
     - -merge
     - -managers
   → Then the parent is the base team name before the suffix.

   Examples:
   - "ballotnav-write" → parent = "ballotnav"
   - "admin-admin" → parent = "admin"

4. If no suffix exists, set Parent = Team Name (top-level team).

5. Do NOT fix typos or rename anything.
   - Preserve names exactly as given.

6. If descriptions are missing, leave blank.

7. If data is ambiguous (e.g., truncated names with "..."):
   - Still include the row
   - Infer parent as best as possible based on visible text

8. Preserve the original order of rows.

9. Output ONLY the markdown table. No explanation.

Here is the screen scrape:
[paste data here]

Activity

  1. self-assigned this
    on Apr 6, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions