On Thu, Jan 01, 2009 at 10:52:29AM -0800, Istvan Albert wrote: -> On Dec 31 2008, 1:10?pm, "C. Titus Brown" <[email protected]> wrote: -> -> > OK -- that sounds like a good idea, if we want to go with a code review -> > system. ?Any thoughts on the process outline? -> -> Happy New Year to Everyone! -> -> One of the links you have on your blog link to Alex Martelli's post on -> code review where he emphasizes the social aspects of code review. It -> rings very true to me, but that also means that I also have some -> doubts that open source and code review can be integrated (the -> priorities for participants in an open source project can be very -> different). For example see slides 15, and 16 how would that work if -> someone would drop out for a month, etc? -> -> http://assets.en.oreilly.com/1/event/12/Code%20Reviews%20for%20Fun%20and%20Profit%20Paper.pdf
Hi Istvan, Happy New Year! You seem talking about new code going in... I think this is only partially aligned with the goal of going over existing code. But for new code, right now I think Chris is doing informal code reviews of everyone else's code before checking it in. So we should just think about having someone look over Chris's code before it goes in. Marek seems like a good choice, and I'm happy to pitch in. Right now new development on pygr is relatively slow so I don't know how big a workload it will be in practice...? cheers, --titus -- C. Titus Brown, [email protected] --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pygr-dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/pygr-dev?hl=en -~----------~----~----~----~------~----~------~--~---
