Project leads must also be committers

It is very rare for us to have a project lead who is not also a committer, so I do not expect this to be controversial.

It's not clear to me that it should be possible to attain project lead status without having developed merit as a committer. I'll defer for another time, the discussion of whether or not some period of time should pass between somebody gaining committer status and then subsequently gaining project lead status. It is currently possible to retire an individual's committer status while leaving their project lead status intact. It's also currently possible to successfully complete a project lead election for somebody who is not a committer.

Our current practices are that when new projects are proposed, anyone who is listed as a project lead must also be listed a committer.

Our privileges model on both GitHub and GitLab grants project leads committer-level privileges and more. That is, for repositories hosted on GitHub and GitLab, project leads are effectively "super committers". This leaves a potential hole: we don't require committer agreements for project leads; so there is at least some potential that somebody who holds project lead status but not committer status could push content that is not covered by an agreement into a project repository (which, as well all know, could lead to the total breakdown of civilization).

It makes more sense to me to accept that project leads really are some sort of "super committer" rather than jump through a bunch of hoops to try and force these roles to be entirely separate.