2011/4/5 Christopher Done :

On 5 April 2011 15:17, Marco Túlio Gontijo e Silva wrote:

...

I plan to apply to the Google Summer of Code, to work on the parallelization of Cabal Install.  As stated in some comments, this project may be too small for three months, so I included some other things in my proposal.  The first is to work on making GHC parallel while building different modules.

I'm sure everyone is eager to have a parallel GHC and parallel Cabal. I am. Waiting for 67 modules to build in order every time I change my types file is not fun.

You should parallelize yourself instead; while one thread is stuck waiting for GHC or Cabal, the other ones can have fun.

Hi Marco On Tue, Apr 5, 2011 at 3:17 PM, Marco Túlio Gontijo e Silva wrote:

I've writed a draft of the proposal at http://www2.dcc.ufmg.br/laboratorios/llp/wiki/doku.php?id=marco_soc2011 .  If you have any comments, I'll be glad to receive them.

Thanks for taking the time to put together such a well-written proposals. I have two comments at this point: "If not all of the dependencies were build yet, the dependencies are included in the queue, and also the package or module, after them." Minor nit: note that several packages can share a dependency so naively adding a dependency to the queue could cause unnecessary rebuilds. "I'll work on a released version of GHC, to avoid having to rebuild it whenever the git is updated, and to avoid handling with changed on the git tree during my development." I would strongly recommend against this as you might end up with an impossible merge towards the end of the project, putting the whole project in jeopardy. I'd suggest getting patches in early and frequently. By submitting patches (at least for review) early and often you'll benefit from feedback and buy-in from the maintainer(s) and make it easier for him/her/they to merge your work. Johan