Skip to content

Latest commit

 

History

History
148 lines (124 loc) · 8.19 KB

DECISION-MAKING.md

File metadata and controls

148 lines (124 loc) · 8.19 KB
Raw

Decision-making rules

Introduction

In October 2019, the BIDS community voted to ratify a governance structure and to elect five members as a Steering Group to oversee the development and adoption of the standard.

The document outlining our governance structure is hosted on the BIDS website: https://bids.neuroimaging.io/governance.html

In the following, we list the current members of subgroups detailed in the BIDS governance.

Steering Group

Name
Guiomar Niso (@guiomar)
Melanie Ganz (@melanieganz)
Robert Oostenveld (@robertoostenveld)
Russel Poldrack (@poldrack)
Kristie Whitaker (@KristieJane)

Maintainers Group

Name Time commitment Scope
Stefan Appelhoff (@sappelhoff) 5h/week
Chris Markiewicz (@effigies) 5h/week
Franklin Feingold (@franklin-feingold) 5h/week Community development

In addition to the BIDS Governance classification of a maintainer, maintainers may declare a limited scope of responsibility. Such a scope can range from maintaining a modality supported in the specification to nurturing a welcoming BIDS community. One or more scopes can be chosen by the maintainer and agreed upon by the Maintainers Group. A maintainer is primarily responsible for issues within their chosen scope(s), although contributions elsewhere are welcome, as well.

BEP Leads Group

Leaders of BIDS Extension Proposals are listed in the table of BEPs.

Contributors Group

Contributors are listed in Appendix I of the BIDS specification. Contributors who have not yet entered their name into this list are encouraged to edit the Contributors WIKI page with their name, using the emojis listed in the WIKI to indicate their contributions.

Other groups

The following groups not listed in detail. Please learn more about these groups from the governance document.

  • BEP working groups
  • Advisory Group
  • BIDS Community

GitHub Workflow

For the day-to-day work on the BIDS specification, we currently abide by the following rules with the intention to:

  • Strive for consensus.
  • Promote open discussions.
  • Minimize the administrative burden.
  • Provide a path for when consensus cannot be made.
  • Grow the community.
  • Maximize the bus factor of the project.

The rules outlined below are inspired by the lazy consensus system used in the Apache Foundation and heavily depends on GitHub Pull Request Review system.

Rules

  1. Every modification of the specification (including a correction of a typo, adding a new Contributor, an extension adding support for a new data type, or others) or proposal to release a new version needs to be done via a Pull Request (PR) to the Repository.
  2. Anyone can open a PR (this action is not limited to Contributors).
  3. PRs adding new Contributors must also add their GitHub names to the CODEOWNERS file.
  4. A PR is eligible to be merged if and only if these conditions are met:
    1. The last commit is at least 5 working days old to allow the community to evaluate it.
    2. The PR features at least two Reviews that Approve the PR from Contributors of which neither is the author of the PR. The reviews need to be made after the last commit in the PR (equivalent to Stale review dismissal option on GitHub).
    3. Does not feature any Reviews that Request changes.
    4. Does not feature "WIP" in the title (Work in Progress).
    5. Passes all automated tests.
    6. Is not proposing a new release or has been approved by at least one Maintainer (i.e., PRs proposing new releases need to be approved by at least one Maintainer).
  5. A Maintainer can merge any PR - even if it's not eligible to merge according to Rule 4.
  6. Any Contributor can Review a PR and Request changes. If a Contributor Request changes they need to provide an explanation what changes should be added and justification of their importance. Reviews requesting changes can also be used to request more time to review a PR.
  7. A Contributor that Requested changes can Dismiss their own review or Approve changes added by the Contributor who opened the PR.
  8. If the author of a PR and Contributor who provided Review that Requests changes cannot find a solution that would lead to the Contributor dismissing their review or accepting the changes the Review can be Dismissed with a vote or by a Maintainer. Rules governing voting:
    1. A Vote can be triggered by any Contributor, but only after 5 working days from the time a Review Requesting Changes has been raised and in case a Vote has been triggered previously no sooner than 15 working days since its conclusion.
    2. Only Contributors can vote, each contributor gets one vote.
    3. A Vote ends after 5 working days or when all Contributors have voted (whichever comes first).
    4. A Vote freezes the PR - no new commits or Reviews Requesting changes can be added to it while a vote is ongoing. If a commit is accidentally made during that period it should be reverted.
    5. The quorum for a Vote is 30% of all Contributors.
    6. The outcome of the vote is decided based on a simple majority.

Comments

  1. Researchers preparing academic manuscripts describing work that has been merged into this repository are strongly encouraged to invite all Maintainers as co-authors as a form of appreciation for their work.
  2. There are no restrictions on how the content of the PR is prepared. For example it is perfectly fine for a PR to consist of content developed by a group of experts over an extended period of time via in person meetings and online collaborations using a Google Document.
  3. To facilitate triage of incoming PR you can subscribe to notifications for new PRs proposing changes to specific files. To do this add your GitHub name next to the file you want to subscribe to in the CODEOWNERS. This way you will be ask to review each relevant PR. Please mind that lack of your review will not prevent the PR from being merged so if you think the PR needs your attention, please review it promptly or request more time via Request changes.
  4. Releases are triggered the same way as any other change - via a PR.
  5. PRs MUST be merged using the "Create a merge commit" option in GitHub (i.e., the "merge pull request" option). This is necessary for our automatic changelog generator to do its work reliably. See the GitHub help page for information on merge methods. See the changelog generator implementation in our circleci configuration file.