{"thread":{"id":"13204","subject":"Welcome to Git's GSoC 2008!","startedAt":"2008-04-22T01:32:01Z","lastAt":"2008-04-26T18:59:43Z","messageCount":8,"participants":["Shawn O. Pearce","Jakub Narebski"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"74896","messageId":"20080422013201.GA4828@spearce.org","threadId":"13204","inReplyTo":null,"subject":"Welcome to Git's GSoC 2008!","fromName":"Shawn O. Pearce","fromEmail":"spearce@spearce.org","sentAt":"2008-04-22T01:32:01Z","receivedAt":"2008-04-22T01:32:01Z","isPatch":false,"sender":{"key":"spearce@spearce.org","avatar":"https://avatars.githubusercontent.com/u/34844?v=4"},"body":"Congratulations, and welcome to the Git community!\n\nBy now I hope you are aware that your project proposal has been\nselected by the Git community, and will be funded thanks to the\nextremely generous folks at Google.\n\nThis year Git was fortunate enough to receive funding for 6 students,\nand we are looking forward to the successful completion of the\nfollowing interesting projects:\n\n  GitTorrent\n      Student: Joshua Roys\n      Mentor:  Sam Vilain\n\n      Josh and Sam will be working to implement native git object\n      transport via a peer-to-peer system, potentially allowing\n      popular projects such as the linux kernel to be available\n      via more servers than just git.kernel.org.\n\n  git-statistics\n      Student: Sverre Rabbelier\n      Mentor:  David Symonds\n\n      Sverre and David are looking to mine the commit history of\n      a project and identify \"good\" changes from \"bad\" changes.\n      Such information may help maintainers to better judge the\n      risk associated with new changes, and help new contributers\n      to more quickly locate individuals who are experienced in\n      a particular section of code (e.g. automatically identify\n      module maintainers).\n    \n  Gitweb caching\n      Student: Lea Wiemann\n      Mentor:  John 'warthog' Hawley\n\n      Lea and John will be working to port the caching gitweb fork\n      that runs on kernel.org back into the main tree, as well as\n      implementing even more improved caching for really large sites\n      like kernel.org, repo.or.cz, or anyone else using gitweb for\n      a large number of repositories and users.\n    \n  Eclipse plugin push support\n      Student: Marek Zawirski\n      Mentor:  Shawn O. Pearce\n\n      Marek and myself will be working to implement pack generation\n      in jgit, allowing the 100% native Java implementation of Git\n      to create pack files locally, as well as upload pack files to\n      a remote repository over the native Git transport.  Marek is\n      also looking forward to improving some of the user interface\n      aspects of the Eclipse Git team provider plugin.\n    \n  git-merge builtin\n      Student: Miklos Vajna\n      Mentor:  Johannes Schindelin\n\n      Miklos and Dscho will be porting the git-merge shell script\n      to C, permitting it to make use of builtin functions like\n      merge base computation, and making the program overall more\n      portable to non-POSIX systems.  Porting some of the popular\n      merge strategies (e.g. git-merge-ours) will also be done as\n      time permits.\n    \n  git-sequencer\n      Student: Stephan Beyer\n      Mentor:  Christian Couder, Daniel Barkalow\n\n      Stephan, Christian and Daniel will be working to port the\n      current \"git rebase --interactive\" to C, as well as create\n      a general \"commit sequencer\" that can be used as the backing\n      implementation for \"git-am\", all three forms of \"git-rebase\",\n      and possibly implement an \"interactive rebase GUI\" within\n      git-gui and/or gitk.\n\n\nStudent projects will be worked on roughly full time (~40 hours/week)\nbetween May 26th and August 18th.\n\nRight now you should spend some time talking to your mentor(s),\nso you can both get to know each other better.  Here's a rough\nidea of some of the things you should be trying to work on with\nyour mentor over the next several weeks:\n\n - Get a copy of Git installed, and become familiar enough with\n   it that you can make changes and commit them.\n\n - Clone the project you will be working to improve.\n\n   - Can you compile it?\n   - Can you run your compiled version?\n   - Can you make a silly modification (make it say \"hello world!\")\n     and see that modification when you test it?\n\n - Discuss where you will be publishing your work.  Publish the\n   base (unmodified) code to make sure you can publish your own\n   work later.\n\n   I highly recommend creating a repository on repo.or.cz.  It is\n   free, and for many of you the upstream project (git.git or\n   egit.git) is already hosted there, so you just create a fork\n   from it.\n\n - Start dicussing with your mentor your timeline and goals.\n\n   Yes, you covered this in your proposal.  But now that its actually\n   something you will be working on this summer it will really help\n   both you and your mentor if you can work out a more detailed\n   plan of the tasks ahead of you.\n\n - Discuss your personal schedule(s) with your mentor(s)/student(s).\n\n   Will you be planning to be offline for any period of time?\n   Taking a summer vacation/holiday for a week?  Now would be a\n   good time to share this information, so everyone knows what to\n   expect this summer.\n\n - Consider reviewing the GPL if you have not read it.\n\n   Nearly all Git related code is covered by the GNU Public License.\n   Individual authors (that's you) retain the copyright on works\n   they create.  (egit/jgit is a special case, I'll take it up with\n   Marek on another thread.)\n\n - Ask you mentor to introduce you around.\n\n   You and your mentor are not working in a vacuum.  Hundreds of\n   people have contributed to Git over the years and there is\n   a wealth of knowledge in the community that you can leverage\n   to your benefit.  Work with your mentor to develop additional\n   contacts with other contributors who are knowledgable in the\n   area of your project.  Don't hesistate to ask these folks for\n   help when you get stuck, especially if your mentor is unable to\n   answer you immediately.\n\nWe realize you are still taking classes, and have project deadlines,\nhomework and exams to still worry about.  But now that you are\naccepted into GSoC its also time to start setting aside a few\nhours a week to plan out your summer, so you can make the most of\nthis opportunity.\n\nWe are excited to have you join us, and are really looking forward\nto these projects!\n\nFinal note: I am your friendly organization administrator.  If you\nhave any questions that your mentor can't answer, etc., please\nemail me.  I'm here to help both the student and the mentor make\nthe most of this summer.\n\n-- \nShawn.\n"},{"id":"74897","messageId":"20080422015933.GB4828@spearce.org","threadId":"13204","inReplyTo":"20080422013201.GA4828@spearce.org","subject":"GSoC 2008 application summary","fromName":"Shawn O. Pearce","fromEmail":"spearce@spearce.org","sentAt":"2008-04-22T01:59:33Z","receivedAt":"2008-04-22T01:59:33Z","isPatch":false,"sender":{"key":"spearce@spearce.org","avatar":"https://avatars.githubusercontent.com/u/34844?v=4"},"body":"This year Google Summer of Code really grew as a program.  Over 7,100\napplications were submitted, almost 1,000 more than last year.\nStudents applied from more than 1300 colleges and universities,\nin more than 98 countries[*1*].\n\nThis year Google offered funding for 1125 students.  This is more\nthan $5.6 million USD given freely to 177 open source projects and\ninterested college students.  Last year Google funded 900 students,\nso we have seen an increase in funding for an additional 225 students\nover last year's program.  Amazing.  Thank you Google!\n\n\nNow more specifically to Git.  We received 36 student applications\nfrom almost that many students (a couple submitted more than one\nproject idea).  That works out to be .5% of the applications.\nGoogle graciously offered Git 6 student slots, which is .5% of the\ntotal number of slots Google funded this year.  One of the criteria\nused by Google to allocate slots to organizations is the percentage\nof overall applications received.\n\nThis year we had a difficult time selecting students.  There were\nmany worthy applicants and applications, and just not enough slots\nto go around.  I wish we had more slots to give, as there were even\nmore students that we wanted to fund.\n\nStudent stipends for Google Summer of Code run at $4500 USD.  If you\nwork for a company with deep enough pockets to be able to make such\na donation to a \"Git summer intern\", we'd love to talk to you.\n\n\nIf you are a student who wasn't selected, you should be receiving\na more detailed message from me in the next few days regarding\nyour proposal.  I really want to let everyone know what happened\nwith their proposal, including the general reasoning behind why\nthe project wasn't selected.  In many cases it simply was a lack of\nresouces, both in terms of mentors and in terms of limited slots.\nDue to the relatively large number of students it will probably\ntake me a couple of days to write everyone.  Please be patient.\n\n\n*1*: http://google-opensource.blogspot.com/2008/04/announcing-accepted-student-proposals.html\n\n-- \nShawn.\n"},{"id":"74908","messageId":"20080422060313.GD29771@spearce.org","threadId":"13204","inReplyTo":"bd6139dc0804212235p250b7335ide5359b43937869b@mail.gmail.com","subject":"Re: Welcome to Git's GSoC 2008!","fromName":"Shawn O. Pearce","fromEmail":"spearce@spearce.org","sentAt":"2008-04-22T06:03:13Z","receivedAt":"2008-04-22T06:03:13Z","isPatch":false,"sender":{"key":"spearce@spearce.org","avatar":"https://avatars.githubusercontent.com/u/34844?v=4"},"body":"Sverre Rabbelier <alturin@gmail.com> wrote:\n> I'm wondering if you other students and mentors are interested in\n> setting up something like a mailing list/forum/IM/whatever to keep\n> each other posted of progress during the summer without spamming the\n> other resources too much. Maybe we can all help each other out with\n> any problems we encounter and just keep in touch in general?\n\nI have been considering it.  But haven't proposed the idea myself\nquite yet.\n\nWe are all working on very different projects.  But I see roughly\nthree classes of discussions that are likely to occur:\n\n  * seemingly stupid questions (aka read the manual or faq)\n\n  There's no such thing as a stupid question, only stupid answers.\n  But one reason we have these wonderful mentors is they can be a\n  safe place for you to bounce ideas off without inciting a flame\n  war on the mailing list.\n\n  * fine grained project specific details\n\n  These are maybe too specific to your project to really spam close\n  to 900 people on the main git mailing list, but are still worth\n  discussion.  Often these sorts of discussions happen off-list\n  among a few interested contributors anyway, even in non-GSoC git\n  related projects.\n\n  These probably should happen between you, your mentor(s) and a\n  handful of others who your mentor has introduced you to as being\n  interested in your work, and as a resource for you to go to for\n  assistance (see the first class of discussion).\n\n  * more project wide discussions\n\n  These really should happen on the git mailing list.  You really\n  want feedback from potential users, and you really want to get a\n  wider audience for your work.  As your project evolves and takes\n  shape your mentor should be encouring you to start posting bits\n  of it for more general discussion.\n\n\nThat said, if the students want to set up a mailing list to help\neach other out, go ahead.  And feel free to invite your mentors,\nor not.  ;-)\n\nFor the record, the best way to reach me is this email address, or\nas \"spearce\" on irc.freenode.net in #git and/or #gsoc.  I'm never\non an IM network, and I really don't like to visit web forums.\nIf it doesn't email to this address where I can read and reply,\nits not something I am interested in.\n\n-- \nShawn.\n"},{"id":"75029","messageId":"20080423042122.GL29771@spearce.org","threadId":"13204","inReplyTo":"20080422015933.GB4828@spearce.org","subject":"Re: GSoC 2008 application summary","fromName":"Shawn O. Pearce","fromEmail":"spearce@spearce.org","sentAt":"2008-04-23T04:21:22Z","receivedAt":"2008-04-23T04:21:22Z","isPatch":false,"sender":{"key":"spearce@spearce.org","avatar":"https://avatars.githubusercontent.com/u/34844?v=4"},"body":"\"Shawn O. Pearce\" <spearce@spearce.org> wrote:\n> \n> If you are a student who wasn't selected, you should be receiving\n> a more detailed message from me in the next few days regarding\n> your proposal.  I really want to let everyone know what happened\n> with their proposal, including the general reasoning behind why\n> the project wasn't selected.\n\nThese notes have now all been individually emailed to students.\n\nAs GSoC applications are considered private unless accepted into\nthe program I have specifically avoided CC'ing these messages to the\nmailing list.  Every message obviously contained the student's email\naddress, but each also addressed specific parts of the student's\nnon-public project proposal.\n\nThe way we selected our 6 students was driven by a number of factors:\n\n - availability of mentors\n\n   As org admin I was trying to balance one student per mentor,\n   so that each individual mentor could focus their available time\n   to a single student's benefit.  Most mentors were willing to\n   mentor only 1 or 2 specific project ideas.  To maximize our\n   accepted students we had to accept a diverse range of projects.\n\n - limited slots\n\n   With only 6 slots available to us in the end we had to make\n   some tough decisions about which projects should be selected,\n   and which wouldn't.  It would be nice if there were more slots\n   then students (and we could take them all), but that is not the\n   way such things work.\n\n - community interest\n\n   We tried to select projects that will have a visible impact on\n   the overall Git user community.\n\n - proposal quality\n\n   We looked for well defined proposals that had measurable criteria\n   for success, and a clear direction for reaching that goal within\n   the time allotted by the GSoC calendar.\n\n - community interaction and student enthusiasm\n\n   We looked for applications where the student was active on our\n   IRC channel, or discussed their project on the mailing list, or\n   significantly via private email with a potential mentor.\n\n   In all such cases the students showed enthusiasm for the project\n   idea and a genuine interest in making Git even better for everone.\n   This was not required, but it certainly made the mentors feel\n   that the student was more likely to be successful this summer.\n\nIf anyone has any questions, or would like further information\nabout our selection process this year, please feel free to ask.\n\n\nOh, and last but not least, I _really_ want to thank our crew of\n2008 mentors for helping with the evaluation process.  They spent\nsome pretty considerable time over the last few weeks talking to\nprospective students on IRC, this mailing list, and private email,\nas well as reviewing applications through the official GSoC web\napplication portal thingy (which as it turns out is a lot less\ncool of a web application than it sounds).  Their efforts were very\nmuch appreciated.\n\n-- \nShawn.\n"},{"id":"75185","messageId":"m3d4odq3w1.fsf@localhost.localdomain","threadId":"13204","inReplyTo":"20080422013201.GA4828@spearce.org","subject":"Re: Welcome to Git's GSoC 2008!","fromName":"Jakub Narebski","fromEmail":"jnareb@gmail.com","sentAt":"2008-04-25T16:46:19Z","receivedAt":"2008-04-25T16:46:19Z","isPatch":false,"sender":{"key":"jnareb@gmail.com","avatar":"https://avatars.githubusercontent.com/u/2706?v=4"},"body":"\"Shawn O. Pearce\" <spearce@spearce.org> writes:\n\n> This year Git was fortunate enough to receive funding for 6 students,\n> and we are looking forward to the successful completion of the\n> following interesting projects:\n\n>   GitTorrent\n>   git-statistics\n>   Gitweb caching\n>   Eclipse plugin push support\n>   git-merge builtin\n>   git-sequencer\n\nI have found three another Git-related Google Summer of Code 2008\nprojects by other organizations:\n\n    Git plugin for Anjuta IDE  (GNOME)\n    KDevelop DVCS support      (KDE)\n    Git# implementation        (Mono Project)\n\nInfo from Shawn message, and above info can be found on git wiki at\nhttp://git.or.cz/gitwiki/SoC2008Projects\n\n-- \nJakub Narebski\nPoland\nShadeHawk on #git\n"},{"id":"75227","messageId":"20080426172945.GD29771@spearce.org","threadId":"13204","inReplyTo":"m3d4odq3w1.fsf@localhost.localdomain","subject":"Re: Welcome to Git's GSoC 2008!","fromName":"Shawn O. Pearce","fromEmail":"spearce@spearce.org","sentAt":"2008-04-26T17:29:45Z","receivedAt":"2008-04-26T17:29:45Z","isPatch":false,"sender":{"key":"spearce@spearce.org","avatar":"https://avatars.githubusercontent.com/u/34844?v=4"},"body":"Jakub Narebski <jnareb@gmail.com> wrote:\n> I have found three another Git-related Google Summer of Code 2008\n> projects by other organizations:\n> \n>     Git plugin for Anjuta IDE  (GNOME)\n\nThis project was new to me; prior to your message I did not know\nabout it.  Thanks.\n\n>     KDevelop DVCS support      (KDE)\n\nI contacted this student/mentor pair and offered them our mailing\nlist address if they have questions.  Apparently the project is\ntrying to create some common DVCS abstractions but wants to use\nGit as the first supported tool.\n\n>     Git# implementation        (Mono Project)\n\nI was talking to one of the two students on #git the other day.\nRobin and I both think they are probably better off just taking jgit\nand compiling it with ikvm so it runs on the Mono CLR.  From there\nthey can build their interface in C#.  Excluding the copyright header\nin every source file, jgit is about 24,300 lines of code right now.\nThat's a lot to write in a summer, especially if you don't know\nGit as well as say I do.\n\nThere is some concern from people who are close to the summer of code\nprogram that two students working on the same project this summer may\nresult in one's success being dependent upon the other's success.\nThis sort of dependency is not permitted under the Summer of Code\nrules, as it can be quite unfair to an otherwise successful student.\n\nIt will be interesting to see how everyone's project turns out at\nthe end of the summer.\n\n-- \nShawn.\n"},{"id":"75229","messageId":"200804262028.09746.jnareb@gmail.com","threadId":"13204","inReplyTo":"20080426172945.GD29771@spearce.org","subject":"Re: Welcome to Git's GSoC 2008!","fromName":"Jakub Narebski","fromEmail":"jnareb@gmail.com","sentAt":"2008-04-26T18:28:08Z","receivedAt":"2008-04-26T18:28:08Z","isPatch":false,"sender":{"key":"jnareb@gmail.com","avatar":"https://avatars.githubusercontent.com/u/2706?v=4"},"body":"On Sat, 26 Apr 2008, Shawn O. Pearce wrote:\n> Jakub Narebski <jnareb@gmail.com> wrote:\n>>\n>> I have found three another Git-related Google Summer of Code 2008\n>> projects by other organizations:\n\nBy the way, it is a bit strange that Google Summer of Code 2008 pages \nare not fully indexed.  Currently searching for \"git soc 2008\" from \n\"Search Google Code:\" search form finds only organization info for Git \nCommunity, \"Git plugin for Anjuta IDE\" project, SoC2008Template \n(Note, this template is blatantly plagiarized from Git's SoC \ntemplate ;-), and netconf project for Debian which uses Git repository \nbut is not about git in any way; none of other were found.\n \n>>     Git plugin for Anjuta IDE  (GNOME)\n> \n> This project was new to me; prior to your message I did not know\n> about it.  Thanks.\n\nHave they contacted Git Community (IRC channel, mailing list, individual \ndevelopers) for help, or did you contacted them, as with \"KDevelop DVCS \nsupport\"?\n\n>>     KDevelop DVCS support      (KDE)\n\nWith these two projects, and egit/jgit for Eclipse, and also planned Git \nsupport in NetBeans IDE, there would be Git support in I think most \nused IDEs... What's left is something akin to AnkhSVN, i.e. support for \nGit in Visual Studio; perhaps Git# projects would help with it...\n \n> I contacted this student/mentor pair and offered them our mailing\n> list address if they have questions.  Apparently the project is\n> trying to create some common DVCS abstractions but wants to use\n> Git as the first supported tool.\n\nI think it is a very good idea, because in my (certainly biased) opinion \nGit has best design and best model of DVCS.  It also has many \ninteresting features: working with multiple branches in single \nrepository, bisect to find where bug was introduced, blame/annotate \nworking across code movement and possibly ignoring whitespace changes \n(although I guess that it would be nice to have interface to pickaxe \nsearch instead/in addition).\n\nI wonder how much will be done; I guess it can borrow at least a bit \nfrom QGit (history viewer) and KGit (commit tool).\n \n>>     Git# implementation        (Mono Project)\n>\n> There is some concern from people who are close to the summer of code\n> program that two students working on the same project this summer may\n> result in one's success being dependent upon the other's success.\n> This sort of dependency is not permitted under the Summer of Code\n> rules, as it can be quite unfair to an otherwise successful student.\n\nI was wondering how this have passed GSoC projects screening...\n\n> It will be interesting to see how everyone's project turns out at\n> the end of the summer.\n\n-- \nJakub Narebski\nPoland\n"},{"id":"75231","messageId":"20080426185943.GF29771@spearce.org","threadId":"13204","inReplyTo":"200804262028.09746.jnareb@gmail.com","subject":"Re: Welcome to Git's GSoC 2008!","fromName":"Shawn O. Pearce","fromEmail":"spearce@spearce.org","sentAt":"2008-04-26T18:59:43Z","receivedAt":"2008-04-26T18:59:43Z","isPatch":false,"sender":{"key":"spearce@spearce.org","avatar":"https://avatars.githubusercontent.com/u/34844?v=4"},"body":"Jakub Narebski <jnareb@gmail.com> wrote:\n> On Sat, 26 Apr 2008, Shawn O. Pearce wrote:\n> > Jakub Narebski <jnareb@gmail.com> wrote:\n> >>\n> >> I have found three another Git-related Google Summer of Code 2008\n> >> projects by other organizations:\n> \n> By the way, it is a bit strange that Google Summer of Code 2008 pages \n> are not fully indexed.\n\nIt is strange.  But I'm sure its something like the site is indexed\nby Google itself, and the page rank algorithm is classifying most\nof the pages as too low to be worth returning due to the low number\nof hyperlinks going in.\n\n> Currently searching for \"git soc 2008\" from \n> \"Search Google Code:\" search form finds only organization info for Git \n> Community, \"Git plugin for Anjuta IDE\" project, SoC2008Template \n> (Note, this template is blatantly plagiarized from Git's SoC \n> template ;-)\n\nApparently our GSoC work has been useful to others outside of Git.\nExcellent.  GSoC has started to become even more of a pet project\nof mine, so I'm glad to see people outside of our community have\nfound our work useful.\n  \n> >>     Git plugin for Anjuta IDE  (GNOME)\n> > \n> > This project was new to me; prior to your message I did not know\n> > about it.  Thanks.\n> \n> Have they contacted Git Community (IRC channel, mailing list, individual \n> developers) for help, or did you contacted them, as with \"KDevelop DVCS \n> support\"?\n\nThey haven't contacted me or anyone I know.  I looked up an email\naddress for the mentor (couldn't locate one for the student)\nand sent them an email, as I did for KDevelop.  Except I wrote it\nafter my reply to you so I didn't mention it in my reply to you.\nOk, so now I have mentioned it.  ;-)\n\n> >>     KDevelop DVCS support      (KDE)\n> \n> With these two projects, and egit/jgit for Eclipse, and also planned Git \n> support in NetBeans IDE, there would be Git support in I think most \n> used IDEs... What's left is something akin to AnkhSVN, i.e. support for \n> Git in Visual Studio; perhaps Git# projects would help with it...\n\nI haven't heard anything about Git in NetBeans lately.  I'm hoping\nthat one day a devoted NetBeans user will come along and pester\nus to break jgit out of the egit repository, so that they can\nuse it within NetBeans without lugging around Eclipse code they\ndon't need.  The code is already built with that in mind, it just\nhas the unfortunate fate of being mingled in the same repository\nas the egit code.\n  \n> I wonder how much will be done; I guess it can borrow at least a bit \n> from QGit (history viewer) and KGit (commit tool).\n>  \n> >>     Git# implementation        (Mono Project)\n> >\n> > There is some concern from people who are close to the summer of code\n> > program that two students working on the same project this summer may\n> > result in one's success being dependent upon the other's success.\n> > This sort of dependency is not permitted under the Summer of Code\n> > rules, as it can be quite unfair to an otherwise successful student.\n> \n> I was wondering how this have passed GSoC projects screening...\n\nMarek Zawirski (the Git GSoC student adding push support to jgit)\nmentioned something about this to me earlier this week.  I made a\nremark about it on #gsoc, and the Google folks who do most of the\nwork for GSoC had not heard about it before my comment.  With so\nmany students and projects I am not surprised that they cannot\nscreen everything.\n\nMost of the screening is left up to the mentors themselves.  So in\nthis case the Mono mentors must have felt that this project was\nlarge enough and important enough to justify using two student\nslots, and that either they didn't know about the rule, were going\nto ignore the rule, or would be able to structure the projects to\navoid this dependency.\n\nI hadn't realized Git was so important to the Mono folks.  I thought\nthey were still on SVN.  In any event, it is interesting that they\nare building IDE support.  Its depressing that Microsoft managed to\nfracture the development communities into Java vs. C# and that they\nuse different VMs, resulting in it being more likely that code will\nbe rewritten rather than reused.\n\n-- \nShawn.\n"}]}