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

BIDS Governance Discussion Resources #245

jdkent opened this issue Jun 19, 2019 · 1 comment


None yet
3 participants
Copy link

commented Jun 19, 2019

A followup from @arokem at the OHBM BIDS discussion suggesting we can look towards the python transition from BDFL to their current steering counsel for inspiration on selecting/modifying the BIDS governance structure. The python community put a decent amount of work aggregating/summarizing governance structures from other open source projects.

PEP 8000 gives an overview of the relevant PEPs for selecting how do we vote for a new governance structure, what options do we select from, what other governance structures are out there (Rust is included).

If you want a more personal account of their process, Brett Cannon (A python core developer and current member of the steering counsel), talked on a couple podcasts about the process.

For where we are currently, #104 should be an essential read, with @KirstieJane's excellent comment outlining considerations for the decision making process.

What are other people's good reads/resources on governance/decision-making topics?


This comment has been minimized.

Copy link

commented Jun 19, 2019

Hi @jdkent

Thank you for raising this and sharing these resources! This is an important discussion to be had and after the OHBM BIDS community meeting the need is there for more organized structure. I think an important aspect will be having this conversation in the open to allow all thoughts and concerns to be aired so we can create the best governance structure for us (taking inspiration from projects like Python, Rust, W3C, etc; and others identified by Kirstie)

A potential proposal is being generated and distributed for community feedback (could be kicked back and a broader conversation be needed). I will open another issue to keep it separate from this one (I think it is great to have a record of governance resources if others in the community want to crowdsource these resources).

WIll be fantastic to have all thoughts on it. WIll be a google document to allow more fluid conversations and enable easier contribution.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.