Clean up and rename the GitHub teams
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 4
- Forks
- 33
- Avg merge
- 3d 54m
- Merged PRs (30d)
- 2
Description
Context
https://openedx.slack.com/archives/C03R320AFJP/p1665670166110739
Jeremy R:
Hi! I am really liking Backstage, but one thing that gets me is the lack of team name consistency (at least in 2U)… is there a way to have teams to have some sort of prefix to know where they come from? I find a name format like “2u-aperture” to be easy to sort on, if one wanted to understand the gamut of 2u ownership…
Kyle:
I believe the names come from GitHub teams, which would mean the question becomes "Can we rename all the GitHub teams using some convention?" Which is a strong yes from me but maybe there are some downstream consequences I'm not thinking of. I'll bring this up in tCRIL's standup today.
We talked in standup and agreed this was a good idea.
AC
Follow through on https://docs.google.com/spreadsheets/d/1nDWMTbmDHyrwWJsSsyr6d6Bx97IKAoKpm5mSVjRj108/edit#gid=0
Renaming is based on https://openedx.atlassian.net/wiki/spaces/COMM/pages/3555852316/GitHub+Team+Naming+Conventions
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the linked spreadsheet and the GitHub Team Naming Conventions page, then use the Slack context to understand the agreed naming approach. Done means following through on the spreadsheet and renaming the listed GitHub teams according to the convention.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- developer-experience
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 28/100