Closes #45 - Provide a synthetic version of post-programs Project and Standard governance

mindthegab commented 4 years ago

Following work on #45 as part of the post program deprecation work #39, we have created a new entry and centralized point for our governance. The intent was to minimize changes from our current governance while cleaning up inconstancies emerged from organic growth and our changes over time (the move to FINOS, the move to the LF, etc.)

This new version includes:

Most of the Foundation corporate governance in editable formats so the Community can propose changes
A simple template for project governance in the CONTRIBUTING.md which projects can amend
A simple template for standard governance in the CONTRIBUTING.md which projects can amend with Board approval
Introducing the concept of Special Interest Groups
Formalizing the concept of Quarterly Focus Projects
Introducing the (optional) Formation stage in the Project Lifecycle
Introduce Project Branding Guidelines
Bring over best practices for voting, meetings, etc and OSS principles from the Wiki.

Once this PR is merged, per #48 we will proceed with cleaning up deprecated content like the wiki Community Handbook and also align our website governance pages to point here as a main entry point.

For a clean copy see https://github.com/copiesofcopies/community and for details of decisions see #45 (which this PR will close once merged).

/cc @toshaellison @brooklynrob @mcleo-d @scooter99boston @copiesofcopies @maoo

agitana commented 4 years ago

@mindthegab @copiesofcopies Is there a mechanism to ensure there's a backup for the lead maintainer? In other words, is it possible for a project to have two lead maintainers, or to allow multiple GitHub team maintainers? / cc @maoo

mindthegab commented 4 years ago

Thanks everyone for the comments so far - just a reminder that, per the plan presented to the Board and Members, we are planning to merge this pull request in 2 days, by Friday 22nd of July., effectively making this the law of the land.

In parallel we'll clean up the current community governance in the wiki Community Handbook, which has been largely migrated here when relevant.

Thanks again everyone for your input!

mindthegab commented 4 years ago

@mindthegab @copiesofcopies Is there a mechanism to ensure there's a backup for the lead maintainer? In other words, is it possible for a project to have two lead maintainers, or to allow multiple GitHub team maintainers? / cc @maoo

Yes. Each project can change their governance by majority and introduce a "vice-lead" or any other concept that helps having continuity. And then we can manage the Github teams appropriately.

mindthegab commented 4 years ago

Thanks everyone for the reviews. All comments have been addressed so I'm proceeding with merging this pull request making this the law of the land.

We will continue with #48 to complete cleanup of wiki and website and then work with projects on #58 to get the project level governance adopted.

Thanks everyone involved in the process!

/cc @toshaellison @brooklynrob @mcleo-d @scooter99boston @copiesofcopies @maoo @aitana16

finos / community

Closes #45 - Provide a synthetic version of post-programs Project and Standard governance #51