Repo Ownership and Location

While I agree that setting up separate repos for subprojects is a good idea, I don't see any need to leave them out in the BDFL's GitHub account. Not only might not someone stay in that role for life, but having related repos under the org makes them easier for outsiders to find.

But there's no need to pre-approve such projects: let the initial BDFL set it up under his account and, when it's reached the point where it should clearly be an "official" part of the project, move the repo from the user's account to the org. This won't break people using the old remote because GitHub is clever enough to leave the old one working so long as no new repo is created under that name. (Web access gets redirected, too.) The permissions also come along so everybody who had whatever access to the repo when it was in the account maintains that when the repo is moved to the org, even if they don't have permissions in the org.

The issue proposes a policy for repository ownership and moving subprojects into the organization, but names no files, tests, or entry points. Start by checking whether the repository already documents ownership and repository transfers; done would mean the policy is agreed and recorded in the relevant project guidance, or the proposal is explicitly closed.