Repository hierarchy in Forgejo

I’ve been hinting over at Fediverse that I’m getting somewhere with deploying a Forgejo instance: Bart Piotrowski: "something may be happening" - Treehouse Mastodon

Ignoring the technical part of it (i.e. where it will be hosted, what about CI, etc), the area I would like to have some alignment on with The Community™ is the future repository setup, should we ever migrate.

It’s worth keeping in mind that contrary to GitLab, Forgejo does not allow “unbound” root-level repositories. Each repo has to belong to some user or organization.

In the current GitHub world, I would differentiate these spaces:

• flathub-infra org which would map directly to something like infrastructure/
• flathub/flathub which is a kitchen sink of general issue tracker and target repo of the submission PRs. This would likely be meta/, with separate projects for issue tracking and new apps. Also where flathub-infra/memberships should go.
• Actual applications. Probably apps/? Doesn’t fit exactly because there are also extensions and BaseApps over there.

Anyone with strong opinions is welcome to chime in!