[infra] Merge technical challenges into one repository

[oliviertassinari]

Summary

Today, we have a couple of challenges that are spread into different repositories, one for each https://www.notion.so/mui-org/Technical-challenges-8f1ea65dbdbd42c39020d50188ee7887?pvs=4#a0e21209bde94c3891f1618762a5fbe4.

• https://github.com/mui/tech-challenge-react
• https://github.com/mui/tech-challenge-full-stack
• https://github.com/mui/tech-challenge-design-engineer
• https://github.com/mui/tech-challenge-pigment-css

However, this comes with a couple of problems:

• To hide forks, we have to turn the project public and then private, for as many repositories
• To update the submission instructions, or fix the writing style, we have to create as many PRs as a repository
• Issues type needs to be synced (bug, etc.)
• It gives a bird view of all the challenges already present
• Olivier has locked the ability to create new repositories to make the easy path to add new folders in existing ones. This is mostly for the codebase, challenges aren't really related. But still, GitHub doesn't allow to select names of repositories that are allowed. (could be disabled, but them people might not know about this policy)
• No new permissions to figure out when creating a new repository. By default, nobody in the org has access to new repositories created outside of its creator.
• GitHub default subscription setting for new repository is to subscribe to all activities. This spams everyone each time a new repository is created.

Now, the upsides of having a separate repository is that:

• It's easier to have different owners who subscribe to each repository for all its notifications.

But overall one repository seems a clear net positive?

Examples

No response

Motivation

No response

Search keywords: -