Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

first draft governance model (bfdl) #565

Open
wants to merge 1 commit into
base: develop
Choose a base branch
from

Conversation

shahzebsiddiqui
Copy link
Contributor

first draft Governance Model

@boegel
Copy link
Member

boegel commented Nov 28, 2019

@shahzebsiddiqui Thank you for looking into this!

There's a couple of things I don't like here, like the BDFL part, and the fact that we have maintainers listed in two different places.

This document should just point to https://easybuild.readthedocs.io/en/latest/Maintainers.html imho... The corresponding file is also in this repo btw, see https://github.com/easybuilders/easybuild/blob/develop/docs/Maintainers.rst

@shahzebsiddiqui
Copy link
Contributor Author

@boegel Yes i understand the file https://github.com/easybuilders/easybuild/blob/develop/docs/Maintainers.rst was part of documentation and I wrote the GOVERNANCE file with assumption that this would reside outside of documentation build. Generally it should be easily found in the top level repo.

The governance file should address how the easybuild project is governed taking into account the three repos (easybuild-framework, easybuild-easyblocks, easybuild-easyconfigs). That way you can have one governance file for the entire project instead of three separate governance file per repo.

Eventually you may want to consider removing the Maintainers.rst from documentation once the Governance File is finalized so dont worry if it is documented in two locations for time being.

It would be worth breaking down the role for Easybuild Maintainers to sub-committees so roles are defined clearly and new users can address questions to appropriate committee when requesting for support assistance. For instance you may want to have core-maintainers for each repo depending on contribution and experience level. Also there needs to be section on how frequent contributors can transition to core-contributors. It is a gray-line but you may want to decide at some point to give more power to the contributors to be part of the community and maintain the project and maybe require them to attend Easybuild Conf Call on regular basis.

The BFDL section was added but certainly this could be changed if Easybuild is not maintained as a BFDL model. The other models are Liberal Contribution or Meritocracy. See https://opensource.guide/leadership-and-governance/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants