Re: GSoC 2014: Summary so far, discussion starter: how to improve?

2013-11-21 Thread Thomas Rast
Thomas Rast t...@thomasrast.ch writes: * Does libgit2 want to remain under the Git umbrella, or participate on its own? * Figure out the wiki situation. In previous years the project proposals and other important information were hosted at k.org [5] and github wikis [6]. Other

Re: GSoC 2014: Summary so far, discussion starter: how to improve?

2013-11-21 Thread Christian Couder
On Thu, Nov 21, 2013 at 9:36 AM, Thomas Rast t...@thomasrast.ch wrote: Thomas Rast t...@thomasrast.ch writes: * Find an org admin and backup. In previous years Shawn and Peff did this. Would you do it again? If Shawn and Peff don't answer, it probably means that you should volunteer :-)

Re: GSoC 2014: Summary so far, discussion starter: how to improve?

2013-11-21 Thread Jeff King
On Thu, Nov 21, 2013 at 09:36:37AM +0100, Thomas Rast wrote: Thomas Rast t...@thomasrast.ch writes: * Does libgit2 want to remain under the Git umbrella, or participate on its own? * Figure out the wiki situation. In previous years the project proposals and other important

Re: GSoC 2014: Summary so far, discussion starter: how to improve?

2013-10-26 Thread Thomas Rast
Junio C Hamano gits...@pobox.com writes: Thomas Rast t...@thomasrast.ch writes: Theories * Scope creep: projects tend to get blocked on some bigger refactoring/restructuring task that was not in the original proposal. (Full disclosure: I actually proposed this theory.) I

Re: GSoC 2014: Summary so far, discussion starter: how to improve?

2013-10-26 Thread Thomas Rast
Fredrik Gustafsson iv...@iveqy.com writes: * Break projects into smaller, easier tasks - They should individually be simple, quick things if the mentor did them. - Should be parallelizable so students don't have to block on reviews. I'd 5-6 smaller projects setup for the summer, I

Re: GSoC 2014: Summary so far, discussion starter: how to improve?

2013-10-22 Thread Junio C Hamano
Thomas Rast t...@thomasrast.ch writes: Theories These are the hypotheses that I have heard (mostly in [1] and [2]) as to what is bad about Git's prior GSoC participations. * Aiming far too high, focusing on cool/shiny projects with a large impact. This also affects the

Re: GSoC 2014: Summary so far, discussion starter: how to improve?

2013-10-20 Thread Thomas Gummerer
As participant in GSoC 2012 I'll mostly respond to this from a student point of view. Generally I had a great learning experience with my project. It was a great introduction into how the Git project and open source projects in general work and certainly lowered the barrier to start

Re: GSoC 2014: Summary so far, discussion starter: how to improve?

2013-10-19 Thread Christian Couder
Hi, On Sat, Oct 19, 2013 at 8:09 AM, Thomas Rast t...@thomasrast.ch wrote: Previous Episodes = Git participated in Google Summer of Code (GSoC) 2007-2012, but did not participate in 2013 based on discussion in February [1]. At Git-Merge in Berlin there was a discussion

RE: GSoC 2014: Summary so far, discussion starter: how to improve?

2013-10-19 Thread Felipe Contreras
Thomas Rast wrote: * Diminishing returns: Git is too mature, with little low-hanging fruit left, making such projects harder Too mature? Aren't there other projects that are too mature as well? In particular I'm thinking about the Linux kernel. I think it's not about maturity, but how they

Re: GSoC 2014: Summary so far, discussion starter: how to improve?

2013-10-19 Thread Fredrik Gustafsson
Hi, so I was a GSoC:er, I got some (most) of my code merged but didn't fully met my (personal) goals for the project. However I do passed in the eyes of Google. GSoC is _hard_. You end up feeling completely stupid over and over again. Git has hard standards. Beeing just a single programmer and/or