Consider streamlining committer paperwork for folks who use their corporate email address
I'm thinking that we have an opportunity to streamline the committer paperwork process when the individual uses a corporate email address.
We know, for example, that somebody with an @redhat.com email address works for Red Hat, and we know that Red Hat has an MCCA, so there's no need for any human intervention in getting the committer paperwork squared away.
The committer paperwork bits are relatively straightforward and require very little effort, but requiring human intervention means that we need a human to be paying attention and engaged. If that human is on vacation, then we could end up with a days-long unnecessary delay. While we do have backups for the humans engaged in this process, we are unable to provide unbroken coverage. These sorts of days are compounded in cases where human intervention is required further downstream from the process (I believe that most of the process of enabling a committer is automated after approval by EMO Records, but there are corner cases where some manual intervention is required).
AFAIK, we do not explicitly track email email domain associations with member companies. This would have to be addressed as part of this effort.