{"thread":{"id":"12450","subject":"GSoC 2008 Application - Help Wanted!","startedAt":"2008-03-03T05:06:24Z","lastAt":"2008-03-05T05:10:44Z","messageCount":8,"participants":["Shawn O. Pearce","Johannes Schindelin","Wincent Colaiuta","Jonas Fonseca"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"70740","messageId":"20080303050624.GF8410@spearce.org","threadId":"12450","inReplyTo":null,"subject":"GSoC 2008 Application - Help Wanted!","fromName":"Shawn O. Pearce","fromEmail":"spearce@spearce.org","sentAt":"2008-03-03T05:06:24Z","receivedAt":"2008-03-03T05:06:24Z","isPatch":false,"sender":{"key":"spearce@spearce.org","avatar":"https://avatars.githubusercontent.com/u/34844?v=4"},"body":"I am starting to prepare our application to Google Summer of\nCode 2008 and would greatly appreciate editing help from everyone\ninterested.  The page on the Wiki is here\n\n  http://git.or.cz/gitwiki/SoC2008Application\n\nand has mostly been created by copying the 2007 page and updating\nthe content to reflect last year's involvement.  To make it easier I\nam including the Wiki markup below so you can read and reply inline\nif that is your preferred approach.\n\nThe deadline is March 12 (12 noon PDT/19:00 UTC).\n\n--8<--\nGit's application to Google's Summer of Code 2008.\n\nThe application questions can be found on\n[http://code.google.com/soc/2008/faqs.html#0.1_org_app code.google.com].\n\nShawn Pearce has volunteered to submit the application and serve\nas our group's primary contact.\n\n''' What is your Organization's Name? '''\n\nGit Development Community\n\n''' What is your Organization's Homepage? '''\n\n[http://git.or.cz/]\n\n''' Describe your organization. '''\n\nAs Git approaches its third anniversary, it is now the revision\ncontrol system of choice for many of the largest and most successful\nopen source projects, including the Linux kernel and at least eight\nGoogle Summer of Code 2007 projects: ikiwiki, One Laptop Per Child,\nSamba, Thousand Parsec, The Wine Project, VideoLAN, XMMS2, and X.org.\n\nThis achievement is the product of the Git development community,\na loose-knit team of developers, technical writers, and end users\nwith a passion for high quality open-source development.\n\n''sp>'' Is this really a good description of us?\n\n''' Why is your organization applying to participate in GSoC 2008? What\ndo you hope to gain by participating? '''\n\nDuring GSoC 2007 Git had two successful student projects.  Although\nboth students contributed useful code to the community, the biggest\nbenefit we received was the increased visibility and the addition of\nnew long-term contributors.\n\nBy participating in GSoC 2008 the Git community hopes to attract\nmore new talent to our community, and convert that talent into\nlong-term contributors.\n\n''' Did your organization participate in past GSoCs? If so, please\nsummarize your involvement and the successes and challenges of your\nparticipation. '''\n\nDuring GSoC 2007 we had two student projects (\"GIT library project\",\n\"Replace most core scripts with C versions\") mentored by two of our\nactive developers.\n\nThe first project produced a Python binding to the internal Git\nAPIs, showing it is possible to embed our private library in a\ndeveloper friendly interface.  This work has not yet been merged\ninto a release tree as it still requires additional effort to\nresolve memory management issues in the underlying private library.\n\nThe second project ported two core Git functions from Bourne shell\nto C, as well as cleaned up the implementation to follow our current\nbest practices.  The student involved with this project is still\nan active contributor almost one year later.\n\n''sp>'' Talk about our challenges.\n\n''' If your organization has not previously participated in GSoC,\nhave you applied in the past? If so, for what year(s)? '''\n\nYes, 2007 (applied and accepted).\n\n''' Who will your organization administrator be? Please include Google\nAccount information. '''\n\nShawn O. Pearce (have Google Account)\n\n''' What license does your project use? '''\n\nGPL (GNU Public License)\n\n''' What is the URL for your ideas page? '''\n\n[http://git.or.cz/gitwiki/SoC2008Ideas]\n\n''' What is the main development mailing list for your organization? '''\n\ngit@vger.kernel.org\n\n''' What is the main IRC channel for your organization? '''\n\n#git on irc.freenode.org.\n\n''' Does your organization have an application template you would like\nto see students use? If so, please provide it now. '''\n\n[[SoC2008Template]]\n\n''' Who will be your backup organization administrator? Please include\nGoogle Account information. '''\n\nJohannes Schindelin (have Google Account)\n\n''' Who will your mentors be? Please include Google Account\nInformation. '''\n\n * Shawn O. Pearce (have Google Account)\n * Johannes Schindelin (have Google Account)\n\n''' What criteria did you use to select these individuals as\nmentors? Please be as specific as possible. '''\n\nAll mentors volunteered for the specific project(s) that they could\ncontribute the most to.  All mentors are active contributers within\nthe Git development community.\n\nActive contributers are defined to be those who have submitted and\nhave had accepted into a shipped release a substantial amount of\nnew code or fixes within the last 4 months (Nov 2007 - Mar 2008).\nSubstantial amount of code is defined to be equal in size (or\nlarger) to what might be reasonably expected of a student working\non a Google Summer of Code project.\n\nAll mentors are well known within the Git development community\nfor their accomplishments and contributions.\n\n''' What is your plan for dealing with disappearing students? '''\n\nEvery reasonable effort will be made to maintain contact with\nstudents and ensure they are making progress throughout the summer.\n\nIn the unfortunate event that a student abandons and does not\ncomplete his/her GSoC project, the Git community will try to pick up\nand continue the work without the student.  This is one reason why we\nwill require frequent publishing of project materials to repo.or.cz.\n\nStudents will also be strongly encouraged by our mentors to work\nthrough their project by completing several small milestones\nthroughout the summer.  This strategy of project organization will\nhelp students to feel like they have accomplished something useful\nsooner, as well as making it easier for the Git community to pick\nup an abandoned project.\n\n''' What is your plan for dealing with disappearing mentors? '''\n\nMost of our suggested projects have more than one mentor available.\nAs a community we plan on making sure all of the active projects have\nat least two mentors willing and available to work with the student,\nreducing the likelihood that the project becomes mentor-less during\nGSoC '08.\n\nIn the unlikely event that a mentor disappears during the summer\nanother mentor will be arranged to step in.  The Git community\nhas plenty of good people within that would be more than happy to\nhelp a student finish their project.  It is very probable that the\nreplacement mentor would already be familiar with the student and\nthe project, as many community members routinely review code and\ndiscussions on the mailing list.\n\n''' What steps will you take to encourage students to interact with\nyour project's community before, during and after the program? '''\n\nStudents will be required to join the main development mailing\nlist, and post their patches for discussion to same.  All current\ncontributors already do this, so students will see the experienced\nhands performing the same tasks, and will therefore be able to learn\nby example.  We feel that the list based discussions will help the\nstudents to become, and stay, a member of the community.\n\nMailing list traffic is currently around 80-100 messages per day,\nand is focused on Git feature development.  Keeping current by\nat least skimming list messages is an important part of the Git\ndevelopment process.\n\nStudents will be required to post their work as a Git repository on\nrepo.or.cz (an open community hosting server), or on another publicly\navailable server, so that their work is immediately available for\neveryone to review, experiment with, and make use of.  Nearly all\nmembers of the Git community post their active work to repo.or.cz\nor similar servers.\n\nMentors will also exchange email with students on at least a\nweekly basis, if not more frequently.  Students will be required\nto provide weekly progress reports back to their mentors, so that\nthe mentors are aware of the tasks that a student might be stuck on\nor are having difficulty with.  The intent of the progress reports\nis to give the mentors a chance to provide suggestions for problem\nresolution back to the student.\n\nFrequent email and IRC interaction with mentors and other developers\nwill be strongly encouraged by suggesting students post their\nquestions and ideas to the mailing list, and to discuss them on #git.\nMost developers either already hold \"office-hours\" on IRC, or have\nagreed to do so during GSoC '08.\n\n''' What will you do to ensure that your accepted students stick with\nthe project after GSoC concludes? '''\n\nGSoC will be a good introduction to Git (both the technology and the\ncommunity) for the students.  Once they know Git and are \"hooked\",\nwe are confident they won't easily leave the arena, for a number\nof reasons.\n\nThe interaction between community members has always been very\nfriendly, and new people are have always been warmly welcomed;\nespecially those with interesting new ideas and viewpoints.\nJovial working friendships have been easily formed between the\ncommunity members, and students will most certainly also be warmly\nwelcomed into that environment.\n\nHacking on Git is an excellent way to hone one's development skills,\nas the community is filled with a wide range of very experienced\nprogrammers who are ready and willing to help a contributor improve\nthe quality of their work.  We hope that students will realize this\nunique opportunity during GSoC and continue staying active within\nthe community even after GSoC '08 completes.\n\n-- \nShawn.\n"},{"id":"70771","messageId":"alpine.LSU.1.00.0803031130210.22527@racer.site","threadId":"12450","inReplyTo":"20080303050624.GF8410@spearce.org","subject":"Re: GSoC 2008 Application - Help Wanted!","fromName":"Johannes Schindelin","fromEmail":"johannes.schindelin@gmx.de","sentAt":"2008-03-03T11:39:23Z","receivedAt":"2008-03-03T11:39:23Z","isPatch":false,"sender":{"key":"johannes.schindelin@gmx.de","avatar":"https://avatars.githubusercontent.com/u/127790?v=4"},"body":"Hi,\n\nOn Mon, 3 Mar 2008, Shawn O. Pearce wrote:\n\n> I am starting to prepare our application to Google Summer of\n> Code 2008 and would greatly appreciate editing help from everyone\n> interested.\n\nThanks!\n\n> ''' Describe your organization. '''\n> \n> As Git approaches its third anniversary, it is now the revision\n> control system of choice for many of the largest and most successful\n> open source projects, including the Linux kernel and at least eight\n> Google Summer of Code 2007 projects: ikiwiki, One Laptop Per Child,\n> Samba, Thousand Parsec, The Wine Project, VideoLAN, XMMS2, and X.org.\n> \n> This achievement is the product of the Git development community,\n> a loose-knit team of developers, technical writers, and end users\n> with a passion for high quality open-source development.\n> \n> ''sp>'' Is this really a good description of us?\n\nI think so.  Maybe you want to add that we are a very lively community, \nand that Git is so fast-moving that we regularly get feature requests that \nhave been addressed already ;-)\n\n> ''' Why is your organization applying to participate in GSoC 2008? What\n> do you hope to gain by participating? '''\n> \n> During GSoC 2007 Git had two successful student projects.  Although\n> both students contributed useful code to the community, the biggest\n> benefit we received was the increased visibility and the addition of\n> new long-term contributors.\n> \n> By participating in GSoC 2008 the Git community hopes to attract\n> more new talent to our community, and convert that talent into\n> long-term contributors.\n\n... and high-quality enhancements to Git.\n\n> ''' Did your organization participate in past GSoCs? If so, please\n> summarize your involvement and the successes and challenges of your\n> participation. '''\n> \n> During GSoC 2007 we had two student projects (\"GIT library project\",\n> \"Replace most core scripts with C versions\") mentored by two of our\n> active developers.\n> \n> The first project produced a Python binding to the internal Git\n> APIs, showing it is possible to embed our private library in a\n> developer friendly interface.  This work has not yet been merged\n> into a release tree as it still requires additional effort to\n> resolve memory management issues in the underlying private library.\n> \n> The second project ported two core Git functions from Bourne shell\n> to C, as well as cleaned up the implementation to follow our current\n> best practices.  The student involved with this project is still\n> an active contributor almost one year later.\n> \n> ''sp>'' Talk about our challenges.\n\nOne challenge was that we had a third project, which was really \ninteresting, and the student was really interested, too, but for political \nreasons he could not get the grant, and therefore the project had to be \nstopped.\n\n> ''' What license does your project use? '''\n> \n> GPL (GNU Public License)\n\n.. v2 (I think by now there are enough parts limited to v2 that it does \nnot matter how much is \"or later, at the discretion of Linus Torvalds\").\n\n> ''' What will you do to ensure that your accepted students stick with\n> the project after GSoC concludes? '''\n> \n> GSoC will be a good introduction to Git (both the technology and the\n> community) for the students.  Once they know Git and are \"hooked\",\n> we are confident they won't easily leave the arena, for a number\n> of reasons.\n> \n> The interaction between community members has always been very\n> friendly, and new people are have always been warmly welcomed;\n\ns/have//\n\n> especially those with interesting new ideas and viewpoints.\n> Jovial working friendships have been easily formed between the\n> community members, and students will most certainly also be warmly\n> welcomed into that environment.\n\nThanks,\nDscho\n\n"},{"id":"70787","messageId":"88B38F4C-C95E-46AE-95F2-812BDA1CC911@wincent.com","threadId":"12450","inReplyTo":"alpine.LSU.1.00.0803031130210.22527@racer.site","subject":"Re: GSoC 2008 Application - Help Wanted!","fromName":"Wincent Colaiuta","fromEmail":"win@wincent.com","sentAt":"2008-03-03T14:56:40Z","receivedAt":"2008-03-03T14:56:40Z","isPatch":false,"sender":{"key":"greg@hurrell.net","avatar":"https://avatars.githubusercontent.com/u/7074?v=4"},"body":"El 3/3/2008, a las 12:39, Johannes Schindelin escribió:\n\n>> The interaction between community members has always been very\n>> friendly, and new people are have always been warmly welcomed;\n>\n> s/have//\n\n\nIf you drop the \"have\" you'll want to drop the \"been\" as well.\n\nCheers,\nWincent\n\n\n\n"},{"id":"70793","messageId":"alpine.LSU.1.00.0803031552300.22527@racer.site","threadId":"12450","inReplyTo":"88B38F4C-C95E-46AE-95F2-812BDA1CC911@wincent.com","subject":"Re: GSoC 2008 Application - Help Wanted!","fromName":"Johannes Schindelin","fromEmail":"johannes.schindelin@gmx.de","sentAt":"2008-03-03T15:52:44Z","receivedAt":"2008-03-03T15:52:44Z","isPatch":false,"sender":{"key":"johannes.schindelin@gmx.de","avatar":"https://avatars.githubusercontent.com/u/127790?v=4"},"body":"Hi,\n\nOn Mon, 3 Mar 2008, Wincent Colaiuta wrote:\n\n> El 3/3/2008, a las 12:39, Johannes Schindelin escribió:\n> \n> > > The interaction between community members has always been very\n> > > friendly, and new people are have always been warmly welcomed;\n> > \n> > s/have//\n> \n> If you drop the \"have\" you'll want to drop the \"been\" as well.\n\nThanks,\nDscho\n"},{"id":"70857","messageId":"20080304000039.GJ8410@spearce.org","threadId":"12450","inReplyTo":"alpine.LSU.1.00.0803031552300.22527@racer.site","subject":"Re: GSoC 2008 Application - Help Wanted!","fromName":"Shawn O. Pearce","fromEmail":"spearce@spearce.org","sentAt":"2008-03-04T00:00:39Z","receivedAt":"2008-03-04T00:00:39Z","isPatch":false,"sender":{"key":"spearce@spearce.org","avatar":"https://avatars.githubusercontent.com/u/34844?v=4"},"body":"Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:\n> On Mon, 3 Mar 2008, Wincent Colaiuta wrote:\n> \n> > El 3/3/2008, a las 12:39, Johannes Schindelin escribió:\n> > \n> > > > The interaction between community members has always been very\n> > > > friendly, and new people are have always been warmly welcomed;\n> > > \n> > > s/have//\n> > \n> > If you drop the \"have\" you'll want to drop the \"been\" as well.\n\nThanks folks.  Those changes have all been reflected on the Wiki now.\n\n-- \nShawn.\n"},{"id":"70888","messageId":"20080304045539.GR8410@spearce.org","threadId":"12450","inReplyTo":"88B38F4C-C95E-46AE-95F2-812BDA1CC911@wincent.com","subject":"GSoC 2008 Application Draft #2 - Help Wanted!","fromName":"Shawn O. Pearce","fromEmail":"spearce@spearce.org","sentAt":"2008-03-04T04:55:39Z","receivedAt":"2008-03-04T04:55:39Z","isPatch":false,"sender":{"key":"spearce@spearce.org","avatar":"https://avatars.githubusercontent.com/u/34844?v=4"},"body":"OK, round #2 of our GSoC 2008 application.\n\nI'm actually quite happy with this draft, but am looking for any\nsuggestions that would improve it, correct language errors, etc.\n\nThe current text on the wiki\n\n  http://git.or.cz/gitwiki/SoC2008Application\n\nas well as below.\n\nIf there are no further edits, this may very well be what we submit\nto Google.  Remember, its due _*this*_ Friday!\n\n--8<--\nGit's application to Google's Summer of Code 2008.\n\nThe application questions can be found on\n[http://code.google.com/soc/2008/faqs.html#0.1_org_app code.google.com].\nAlso the published [http://groups.google.com/group/google-summer-of-code-announce/web/notes-on-organization-selection-criteria notes on organization selection] may be of interest.\n\nShawn Pearce has volunteered to submit the application and serve\nas our group's primary contact.\n\n''' What is your Organization's Name? '''\n\nGit Development Community\n\n''' What is your Organization's Homepage? '''\n\n[http://git.or.cz/]\n\n''' Describe your organization. '''\n\nAs Git approaches its third anniversary, it is now the revision\ncontrol system of choice for many of the largest and most successful\nopen source projects, including the Linux kernel and at least eight\nother Google Summer of Code 2007 projects: ikiwiki, One Laptop Per\nChild, Samba, Thousand Parsec, The Wine Project, VideoLAN, XMMS2,\nand X.org.\n\nThis achievement is the product of the lively Git development\ncommunity, a loose-knit team of developers, technical writers, and\nend users with a passion for high quality open-source development.\n\n''' Why is your organization applying to participate in GSoC 2008? What\ndo you hope to gain by participating? '''\n\nDuring GSoC 2007 Git had two successful student projects.  Although\nboth students contributed useful code to the community, the biggest\nbenefit we received was the increased visibility and the addition of\nnew long-term contributors.\n\nBy participating in GSoC 2008 the Git community hopes to attract\nmore new talent to our community, and convert that talent into\nlong-term contributors and high-quality enhancements to Git.\n\n''' Did your organization participate in past GSoCs? If so, please\nsummarize your involvement and the successes and challenges of your\nparticipation. '''\n\nDuring GSoC 2007 we had two student projects (\"GIT library project\",\n\"Replace most core scripts with C versions\") mentored by two of our\nactive developers.\n\nThe first project produced a Python binding to the internal Git\nAPIs, showing it is possible to embed our private library in a\ndeveloper friendly interface.  This work has not yet been merged\ninto a release tree as it still requires additional effort to\nresolve memory management issues in the underlying private library.\n\nThe second project ported two core Git functions from Bourne shell\nto C, as well as cleaned up the implementation to follow our current\nbest practices.  The student involved with this project is still\nan active contributor almost one year later.\n\nOne challenge that we faced was a third student project was granted\nby Google but had to be forfeited due to political reasons out of\nour control.  The student was unable to file the proper paperwork\nand the project had to be stopped.  As a community we realized the\nissue too late and did not try to ask Google to replace the student\nwith another.  It was later clear to us at the Mentor Summit that\nwe probably should have asked for a replacement student.\n\n''' If your organization has not previously participated in GSoC,\nhave you applied in the past? If so, for what year(s)? '''\n\nN/A.  Applied and accepted GSoC 2007; did not apply prior to that.\n\n''' Who will your organization administrator be? Please include Google\nAccount information. '''\n\nShawn O. Pearce (have Google Account)\n\n''' What license does your project use? '''\n\nGPL (GNU Public License), version 2\n\n''' What is the URL for your ideas page? '''\n\n[http://git.or.cz/gitwiki/SoC2008Ideas]\n\n''' What is the main development mailing list for your organization? '''\n\ngit@vger.kernel.org\n\n''' What is the main IRC channel for your organization? '''\n\n#git on irc.freenode.org.\n\n''' Does your organization have an application template you would like\nto see students use? If so, please provide it now. '''\n\n[http://git.or.cz/gitwiki/SoC2008Template]\n\n''' Who will be your backup organization administrator? Please include\nGoogle Account information. '''\n\nJohannes Schindelin (have Google Account)\n\n''' Who will your mentors be? Please include Google Account\nInformation. '''\n\n * Shawn O. Pearce (have Google Account)\n * Johannes Schindelin (have Google Account)\n\n''' What criteria did you use to select these individuals as\nmentors? Please be as specific as possible. '''\n\nAll mentors volunteered for the specific project(s) that they could\ncontribute the most to.  All mentors are active contributers within\nthe Git development community.\n\nActive contributers are defined to be those who have submitted and\nhave had accepted into a shipped release a substantial amount of\nnew code or fixes within the last 4 months (Nov 2007 - Mar 2008).\nSubstantial amount of code is defined to be equal in size (or\nlarger) to what might be reasonably expected of a student working\non a Google Summer of Code project.\n\nAll mentors are well known within the Git development community\nfor their accomplishments and contributions.\n\n''' What is your plan for dealing with disappearing students? '''\n\nEvery reasonable effort will be made to maintain contact with\nstudents and ensure they are making progress throughout the summer.\n\nIn the unfortunate event that a student abandons and does not\ncomplete his/her GSoC project, the Git community will try to pick up\nand continue the work without the student.  This is one reason why we\nwill require frequent publishing of project materials to repo.or.cz.\n\nStudents will also be strongly encouraged by our mentors to work\nthrough their project by completing several small milestones\nthroughout the summer.  This strategy of project organization will\nhelp students to feel like they have accomplished something useful\nsooner, as well as making it easier for the Git community to pick\nup an abandoned project.\n\n''' What is your plan for dealing with disappearing mentors? '''\n\nMost of our suggested projects have more than one mentor available.\nAs a community we plan on making sure all of the active projects have\nat least two mentors willing and available to work with the student,\nreducing the likelihood that the project becomes mentor-less during\nGSoC '08.\n\nIn the unlikely event that a mentor disappears during the summer\nanother mentor will be arranged to step in.  The Git community\nhas plenty of good people within that would be more than happy to\nhelp a student finish their project.  It is very probable that the\nreplacement mentor would already be familiar with the student and\nthe project, as many community members routinely review code and\ndiscussions on the mailing list.\n\n''' What steps will you take to encourage students to interact with\nyour project's community before, during and after the program? '''\n\nStudents will be required to join the main development mailing\nlist, and post their patches for discussion to same.  All current\ncontributors already do this, so students will see the experienced\nhands performing the same tasks, and will therefore be able to learn\nby example.  We feel that the list based discussions will help the\nstudents to become, and stay, a member of the community.\n\nMailing list traffic is currently around 80-100 messages per day,\nand is focused on Git feature development.  Keeping current by\nat least skimming list messages is an important part of the Git\ndevelopment process.\n\nStudents will be required to post their work as a Git repository on\nrepo.or.cz (an open community hosting server), or on another publicly\navailable server, so that their work is immediately available for\neveryone to review, experiment with, and make use of.  Nearly all\nmembers of the Git community post their active work to repo.or.cz\nor similar servers.\n\nMentors will also exchange email with students on at least a\nweekly basis, if not more frequently.  Students will be required\nto provide weekly progress reports back to their mentors, so that\nthe mentors are aware of the tasks that a student might be stuck on\nor are having difficulty with.  The intent of the progress reports\nis to give the mentors a chance to provide suggestions for problem\nresolution back to the student.\n\nFrequent email and IRC interaction with mentors and other developers\nwill be strongly encouraged by suggesting students post their\nquestions and ideas to the mailing list, and to discuss them on #git.\nMost developers either already hold \"office-hours\" on IRC, or have\nagreed to do so during GSoC '08.\n\n''' What will you do to ensure that your accepted students stick with\nthe project after GSoC concludes? '''\n\nGSoC will be a good introduction to Git (both the technology and the\ncommunity) for the students.  Once they know Git and are \"hooked\",\nwe are confident they won't easily leave the arena, for a number\nof reasons.\n\nThe interaction between community members has always been very\nfriendly, and new people are always warmly welcomed; especially\nthose with interesting new ideas and viewpoints.  Jovial working\nfriendships have been easily formed between the community members,\nand students will most certainly also be warmly welcomed into\nthat environment.\n\nHacking on Git is an excellent way to hone one's development skills,\nas the community is filled with a wide range of very experienced\nprogrammers who are ready and willing to help a contributor improve\nthe quality of their work.  We hope that students will realize this\nunique opportunity during GSoC and continue staying active within\nthe community even after GSoC '08 completes, just like our GSoC\n'07 students did.\n-- \nShawn.\n"},{"id":"70983","messageId":"2c6b72b30803041047i34c6ad5fx6d8b30d4ce0018e5@mail.gmail.com","threadId":"12450","inReplyTo":"20080304045539.GR8410@spearce.org","subject":"Re: GSoC 2008 Application Draft #2 - Help Wanted!","fromName":"Jonas Fonseca","fromEmail":"jonas.fonseca@gmail.com","sentAt":"2008-03-04T18:47:39Z","receivedAt":"2008-03-04T18:47:39Z","isPatch":false,"sender":{"key":"jonas.fonseca@gmail.com","avatar":"https://gravatar.com/avatar/9b7fa23cce50269e5d164312b6ac5ae818a180f837b38f28f3bdf689dd7f96cd?d=mp&s=160"},"body":"On Tue, Mar 4, 2008 at 5:55 AM, Shawn O. Pearce <spearce@spearce.org> wrote:\n>  ''' What criteria did you use to select these individuals as\n>  mentors? Please be as specific as possible. '''\n>\n>  All mentors volunteered for the specific project(s) that they could\n>  contribute the most to.  All mentors are active contributers within\n\ns/contributers/contributors/\n\n>  the Git development community.\n>\n>  Active contributers are defined to be those who have submitted and\n\ns/contributers/contributors/\n\n-- \nJonas Fonseca\n"},{"id":"71025","messageId":"20080305051044.GY8410@spearce.org","threadId":"12450","inReplyTo":"2c6b72b30803041047i34c6ad5fx6d8b30d4ce0018e5@mail.gmail.com","subject":"Re: GSoC 2008 Application Draft #2 - Help Wanted!","fromName":"Shawn O. Pearce","fromEmail":"spearce@spearce.org","sentAt":"2008-03-05T05:10:44Z","receivedAt":"2008-03-05T05:10:44Z","isPatch":false,"sender":{"key":"spearce@spearce.org","avatar":"https://avatars.githubusercontent.com/u/34844?v=4"},"body":"Jonas Fonseca <jonas.fonseca@gmail.com> wrote:\n> On Tue, Mar 4, 2008 at 5:55 AM, Shawn O. Pearce <spearce@spearce.org> wrote:\n> >  ''' What criteria did you use to select these individuals as\n> >  mentors? Please be as specific as possible. '''\n> >\n> >  All mentors volunteered for the specific project(s) that they could\n> >  contribute the most to.  All mentors are active contributers within\n> \n> s/contributers/contributors/\n\nGaaah.  Thanks Jonas.\n\nThat typo was in there last year.  :-)\n \n-- \nShawn.\n"}]}