Document project governance

[mfisher87]

Chatting with @JessicaS11 over the last week, I think we've identified a need to explicitly document how governance works for this project.

• How are decisions made? By whom?
• What rises to the level of a "big decision" that requires buy-in, and what is a "small decision" that can be decided by any community members?
• Where and how do we record big decisions (i.e. decision records / decision log)?
• Who should review before a PR is merged?
• What leadership roles does this project have and who performs them?
• What is the pathway for someone to taking on a leadership role like "maintainer"?
• What do we want/expect to see change about governance in our future?

opensource.guide has an excellent page on governance: https://opensource.guide/leadership-and-governance/

Finally, should we consider review and adoption by an org like pyopensci to help us with governance and other long-term aspects of project maintenance? @JessicaS11 based on what we've discussed so far, I think this would be an excellent strategic move to make the work more sustainable. Perhaps we should break this off into another issue.