Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
Tree: 2a35dc9846
Fetching contributors…

Cannot retrieve contributors at this time

221 lines (164 sloc) 9.565 kB

Git's application to Google's Summer of Code 2008.

The application questions can be found on code.google.com. Also the published notes on organization selection may be of interest.

Shawn Pearce has volunteered to submit the application and serve as our group's primary contact.

What is your Organization's Name?

Git Development Community

What is your Organization's Homepage?

http://git.or.cz/

Describe your organization.

As Git approaches its third anniversary, it is now the revision control system of choice for many of the largest and most successful open source projects, including the Linux kernel and at least eight other Google Summer of Code 2007 projects: ikiwiki, One Laptop Per Child, Samba, Thousand Parsec, The Wine Project, VideoLAN, XMMS2, and X.org.

This achievement is the product of the lively Git development community, a loose-knit team of developers, technical writers, and end users with a passion for high quality open-source development.

Why is your organization applying to participate in GSoC 2008? What do you hope to gain by participating?

During GSoC 2007 Git had two successful student projects. Although both students contributed useful code to the community, the biggest benefit we received was the increased visibility and the addition of new long-term contributors.

By participating in GSoC 2008 the Git community hopes to attract more new talent to our community, and convert that talent into long-term contributors and high-quality enhancements to Git.

Did your organization participate in past GSoCs? If so, please summarize your involvement and the successes and challenges of your participation.

During GSoC 2007 we had two student projects ("GIT library project", "Replace most core scripts with C versions") mentored by two of our active developers.

The first project produced a Python binding to the internal Git APIs, showing it is possible to embed our private library in a developer friendly interface. This work has not yet been merged into a release tree as it still requires additional effort to resolve memory management issues in the underlying private library.

The second project ported two core Git functions from Bourne shell to C, as well as cleaned up the implementation to follow our current best practices. The student involved with this project is still an active contributor almost one year later.

One challenge that we faced was a third student project was granted by Google but had to be forfeited due to political reasons out of our control. The student was unable to file the proper paperwork and the project had to be stopped. As a community we realized the issue too late and did not try to ask Google to replace the student with another. It was later clear to us at the Mentor Summit that we probably should have asked for a replacement student.

If your organization has not previously participated in GSoC, have you applied in the past? If so, for what year(s)?

N/A. Applied and accepted GSoC 2007; did not apply prior to that.

Who will your organization administrator be? Please include Google Account information.

Shawn O. Pearce (have Google Account)

What license does your project use?

GPL (GNU Public License), version 2

What is the URL for your ideas page?

http://git.or.cz/gitwiki/SoC2008Ideas

What is the main development mailing list for your organization?

git@vger.kernel.org

What is the main IRC channel for your organization?

Does your organization have an application template you would like to see students use? If so, please provide it now.

http://git.or.cz/gitwiki/SoC2008Template

Who will be your backup organization administrator? Please include Google Account information.

Johannes Schindelin (have Google Account)

Who will your mentors be? Please include Google Account Information.

  • Shawn O. Pearce (have Google Account)
  • Johannes Schindelin (have Google Account)
What criteria did you use to select these individuals as mentors? Please be as specific as possible.

All mentors volunteered for the specific project(s) that they could contribute the most to. All mentors are active contributors within the Git development community.

Active contributors are defined to be those who have submitted and have had accepted into a shipped release a substantial amount of new code or fixes within the last 4 months (Nov 2007 - Mar 2008). Substantial amount of code is defined to be equal in size (or larger) to what might be reasonably expected of a student working on a Google Summer of Code project.

All mentors are well known within the Git development community for their accomplishments and contributions.

What is your plan for dealing with disappearing students?

Every reasonable effort will be made to maintain contact with students and ensure they are making progress throughout the summer.

In the unfortunate event that a student abandons and does not complete his/her GSoC project, the Git community will try to pick up and continue the work without the student. This is one reason why we will require frequent publishing of project materials to repo.or.cz.

Students will also be strongly encouraged by our mentors to work through their project by completing several small milestones throughout the summer. This strategy of project organization will help students to feel like they have accomplished something useful sooner, as well as making it easier for the Git community to pick up an abandoned project.

What is your plan for dealing with disappearing mentors?

Most of our suggested projects have more than one mentor available. As a community we plan on making sure all of the active projects have at least two mentors willing and available to work with the student, reducing the likelihood that the project becomes mentor-less during GSoC '08.

In the unlikely event that a mentor disappears during the summer another mentor will be arranged to step in. The Git community has plenty of good people within that would be more than happy to help a student finish their project. It is very probable that the replacement mentor would already be familiar with the student and the project, as many community members routinely review code and discussions on the mailing list.

What steps will you take to encourage students to interact with your project's community before, during and after the program?

Students will be required to join the main development mailing list, and post their patches for discussion to same. All current contributors already do this, so students will see the experienced hands performing the same tasks, and will therefore be able to learn by example. We feel that the list based discussions will help the students to become, and stay, a member of the community.

Mailing list traffic is currently around 80-100 messages per day, and is focused on Git feature development. Keeping current by at least skimming list messages is an important part of the Git development process.

Students will be required to post their work as a Git repository on repo.or.cz (an open community hosting server), or on another publicly available server, so that their work is immediately available for everyone to review, experiment with, and make use of. Nearly all members of the Git community post their active work to repo.or.cz or similar servers.

Mentors will also exchange email with students on at least a weekly basis, if not more frequently. Students will be required to provide weekly progress reports back to their mentors, so that the mentors are aware of the tasks that a student might be stuck on or are having difficulty with. The intent of the progress reports is to give the mentors a chance to provide suggestions for problem resolution back to the student.

Frequent email and IRC interaction with mentors and other developers will be strongly encouraged by suggesting students post their questions and ideas to the mailing list, and to discuss them on #git. Most developers either already hold "office-hours" on IRC, or have agreed to do so during GSoC '08.

What will you do to ensure that your accepted students stick with the project after GSoC concludes?

GSoC will be a good introduction to Git (both the technology and the community) for the students. Once they know Git and are "hooked", we are confident they won't easily leave the arena, for a number of reasons.

The interaction between community members has always been very friendly, and new people are always warmly welcomed; especially those with interesting new ideas and viewpoints. Jovial working friendships have been easily formed between the community members, and students will most certainly also be warmly welcomed into that environment.

Hacking on Git is an excellent way to hone one's development skills, as the community is filled with a wide range of very experienced programmers who are ready and willing to help a contributor improve the quality of their work. We hope that students will realize this unique opportunity during GSoC and continue staying active within the community even after GSoC '08 completes, just like our GSoC '07 students did.

Jump to Line
Something went wrong with that request. Please try again.