On Dec 17, 2011, at 9:58 AM, Thomas Schilling wrote:
> Weeeell... I've gotten a little bit of a different perspective on this
> since working at a company with very high code quality standards (at
> least for new code). There is practically no observable code review
> happening. I'm sure Dimitrios and Simon PJ review most of each
> other's code every now and then, but overall there is very little code
> review happening (and no formal, recorded code review whatsoever).
> Cleaning up the GHC code base is a huge task -- it uses lots of dirty
> tricks (global variables, hash tables, unique generation is
> non-deterministic, ...) which often complicate efforts tremendously (I
> tried). The lack of a unit tests doesn't help (just rewriting code so
> that it can be tested would help quite a bit).
So in other words, would it be helpful it we recruited GHC janitors? That is,
similar to how we have the Trac which gives people bug reports to pick out and
work on, would it make sense to have a Trac or some other process which gives
people chunks of code to clean up and/or make easier to test?
(I am of course inspired in suggesting this by the Linux kernel janitors,
though it doesn't look like the project has survived, and maybe that portends
ill for trying to do the same for GHC...)
Cheers,
Greg
_______________________________________________
Haskell-Cafe mailing list
Haskell-Cafe@haskell.org
http://www.haskell.org/mailman/listinfo/haskell-cafe
