cabal-devel

Thread Start a new thread

Download

cabal-devel@haskell.org

July 2016

7 participants
2 discussions

Opening up Cabal development
by Edward Z. Yang 18 Jul '16

18 Jul '16

Hey all, Paolo Giarrusso suggested that the Cabal project might look into giving more people commit bits, ala http://felixge.de/2013/03/11/the-pull-request-hack.html I think we do need to give more commit bits. There's a sliding scale of how extreme we can go: 1. We can adopt this wholesale: you PR, your GitHub profile checks out, we give you bits. 2. If we accept your PR, we give you bits. 3. If we accept your PR for a new feature, we give you bits. For (2), I trawled the commit history for 2016 and here's what I think is all the commits from people without bits. I apologize if I missed anyone (I just went through the commit list by hand.) @thumphries https://github.com/haskell/cabal/commit/ce2ffb24902816ab02f6c6b50921fb3a9a8… @sjakobi https://github.com/haskell/cabal/commit/bb9501bc23914a50684f288bc88cf04747d… @accraze https://github.com/haskell/cabal/commit/11650b26ecf0ba95c3a7e747c0968735e90… @headprogrammingczar https://github.com/haskell/cabal/commit/e9883dced04e6a16e25752cc8513ce26325… https://github.com/haskell/cabal/commit/0252a0aed79e881d4f6210d9296216aef3c… @randen https://github.com/haskell/cabal/commits/master?author=randen @aisamanra https://github.com/haskell/cabal/commit/6e2fca4314a01f07d520bc7b7669e70f70a… @kolmodin https://github.com/haskell/cabal/commit/0122e821825b875447f3844b349fba582ff… @mightybyte https://github.com/haskell/cabal/commit/ea01974be888d25ef918e7808aa6cf6b8aa… @gbaz https://github.com/haskell/cabal/commit/c69dfb8209dc7bfd9abf2a7e494704db652… @garetxe https://github.com/haskell/cabal/commit/c72aa8dbb5a11fb4137bda62c9b7a99fb48… @komadori https://github.com/haskell/cabal/commit/1da9b3533e6a0fae8692fa0f4f532ea63d4… @mgsloan https://github.com/haskell/cabal/commit/c10a4ca8c50290efc0b0ea65b34116ae165… @lukexi https://github.com/haskell/cabal/commit/5efc6341643e7fd98b33aea5a6ab96873d5… @mpkh https://github.com/haskell/cabal/commit/fcaf5d02947c5fd853ff69e2326e08f0082… @pra85 https://github.com/haskell/cabal/commit/a69b0ea23b0f00be30933a1dbb63fbc4f13… @tvestelind https://github.com/haskell/cabal/commit/fe7b597542d57c74814620ed7a553e252b5… @corngood https://github.com/haskell/cabal/commit/4214572306205ad2c20943ef2b3aacbc912… @gelisam https://github.com/haskell/cabal/commit/6b3457de66772d958fd5fe96066b08e93d0… Why don't we give them all commit access! (If we want to do (1) also look at the current PR queue.) If people want, we could also formalize some more rules about the state of master, e.g., - The Travis build must always be green. We should prioritize adding more tests for things we care about. Look into regular Hackage tests. - PR all your changes (so that you can check that Travis is green), try to get approval for big changes but BE BOLD. Cheers, Edward

6 11

I reorged labels on Cabal's GitHub
by Edward Z. Yang 13 Jul '16

13 Jul '16

If you hate it I can change it back but give it a try for now. If the "component" prefix in "component: solver" is too long we could go for something like "C-solver" but I think that is less transparent. I also added some new labels, "paging: ezyang (...)". In the parenthetical should be a quick summary of the types of things you are interested in getting paged for. I tried to guess some but I am not perfect, please feel free to change your description / add a label for yourself (I didn't get everyone) / tell me how you want yours changed. Edward

4 11