<br><br><div class="gmail_quote">On Tue, Mar 3, 2009 at 6:25 PM, Lydia Pintscher <span dir="ltr"><<a href="mailto:lydia@kde.org">lydia@kde.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Heya folks,<br>
<br>
I have been thinking about what we can improve this year wrt to the<br>
code that gets written during GSoC. As last year was the first year we<br>
had a lot of newcomers as students I think there are some things we<br>
can improve this year on the coding side.<br>
One big problem last year was that some students commited huge chunks<br>
of code that only very few people or even no-one reviewed post commit.<br>
So I guess we should make it very very clear that we want to see<br>
smaller commits on a more regular basis.<br>
Is there anything else that could be useful? What is your opinion on a<br>
more formal code review pre or post commit?<br>
Also for the former students: Is there anything on the coding side we<br>
could have done that you think would have helped you?<br>
<br>
Let's make GSoC 2009 rock at least as much as last year's!</blockquote></div><br>Switching to Git will make all this a lot easier. We could even start students off with the pull request' model on github.<br><br>
So you're just making me guilty for not working on scripty. :D<br><br>ian<br>