Skip to content
Snippets Groups Projects
Select Git revision
  • ulysses4ever-patch-3
  • master default
  • mergify/merge-queue/50e6b1b7a2
  • mergify/merge-queue/e7e4ac5687
  • dont-mention-builddir-in-default-config-t11050
  • mergify/merge-queue/aafe5ea185
  • 3.16
  • mergify/merge-queue/a769f78a1b
  • mergify/bp/3.16/pr-11061
  • mergify/merge-queue/2b04a36384
  • mergify/merge-queue/8372a86082
  • mergify/bp/3.16/pr-11032
  • mergify/bp/3.16/pr-11047
  • mergify/merge-queue/731e297395
  • mergify/bp/master/pr-11033
  • wip/cabal-proposals
  • wip/teo-precise-unit-id
  • mergify/merge-queue/b815383153
  • mergify/merge-queue/6ce3ccd864
  • mergify/bp/3.16/pr-11018
  • 3.16.0+0
  • cabal-head
  • cabal-install-v3.16.0.0
  • cabal-install-solver-v3.16.0.0
  • Cabal-v3.16.0.0
  • Cabal-syntax-v3.16.0.0
  • Cabal-hooks-v3.16
  • Cabal-hooks-v3.16.0.0
  • Cabal-syntax-v3.14.2.0
  • Cabal-v3.14.2.0
  • cabal-instal-solver-v3.14.2.0
  • cabal-install-v3.14.2.0
  • 3.14.2+0
  • 3.14.1.1+1
  • cabal-install-v3.14.1.1
  • Cabal-hooks-3.14.1.1
  • Cabal-v3.14.1.1
  • 3.14.1.1
  • 3.14.1.1+0
  • cabal-install-solver-v3.14.1.0
40 results
Blame Permalink
  • Matthew Pickering's avatar
    6f6b2c8a
    Add proposals.md document which explains the proposal process (#11006) · 6f6b2c8a
    Matthew Pickering authored 
    The cabal developers are interested to adopt a proposal process, the
details are found in the `proposals.md` file.

The process is designed to make developers feel empowered to make decisions.

* It is light-weight, a PR is opened and discussed on a repo with a fixed discussion period.
* It is developer-led, final decisions are made by developers at the Cabal developers meeting.
* It is flexible, there is no formal voting procedure, decisions are made by rough consensus.

Overall, we hope that this will allow developers to move the cabal project forward.
    Unverified
    6f6b2c8a
    History
    Add proposals.md document which explains the proposal process (#11006)
    Matthew Pickering authored 
    The cabal developers are interested to adopt a proposal process, the
details are found in the `proposals.md` file.

The process is designed to make developers feel empowered to make decisions.

* It is light-weight, a PR is opened and discussed on a repo with a fixed discussion period.
* It is developer-led, final decisions are made by developers at the Cabal developers meeting.
* It is flexible, there is no formal voting procedure, decisions are made by rough consensus.

Overall, we hope that this will allow developers to move the cabal project forward.
Code owners
Assign users and groups as approvers for specific file changes. Learn more.
After you've reviewed these contribution guidelines, you'll be all set to contribute to this project.