Add issue templates for common operations

[zimbatm]

Last week I discovered that it's possible to create issue templates with form fields:

https://github.com/NixOS/foundation/blob/master/.github/ISSUE_TEMPLATE/funding_form.yml

We could create issue templates for common operations and help clarify our workflows.

For example:

• move a repo
• create a new repo
• deploy a service
• ...

What do you think?

[zowoq]

• move a repo
• create a new repo

I wouldn't bother with templates for this unless we're going to restrict permissions for creating and moving repos.

Restricting permissions as crossed my mind a couple of times, e.g. for forks of repos it would be good to have a record of who and why without having to dig around for it.

[zimbatm]

Whenever we onboard new members, there is always a bit of back and forth to add them to the org; then they can move the repo; once the repo is there, fix the maintainer field, create the related team, get them to know about the settings app to configure the repo. Documenting and keeping track of all of those steps would be nice.

For new repos, potentially, we want to disable it as some members use it for fresh repos. Ideally, the org holds projects that are more than MVPs, although we didn't really discuss what standards we want to hold here. The issue with too many MVP repos is that it creates a graveyard of unmaintained projects.

[zowoq]

For new repos, potentially, we want to disable it as some members use it for fresh repos.

Just had another new project created here so I've gone ahead and disabled it.

[zowoq]

For new repos, potentially, we want to disable it as some members use it for fresh repos.

Just had another new project created here so I've gone ahead and disabled it.

As this is kind of inconvenient to flip on and off and keep track if it I'll leave it enabled until we figure out what we want to do and document it. I have an idea that my allow us to keep it disabled and still transfer repos into the org but need to test it first.