Hi,
On Mon, 3 Mar 2008, Shawn O. Pearce wrote:
> I am starting to prepare our application to Google Summer of
> Code 2008 and would greatly appreciate editing help from everyone
> interested.
Thanks!
> ''' 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
> 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 Git development community,
> a loose-knit team of developers, technical writers, and end users
> with a passion for high quality open-source development.
>
> ''sp>'' Is this really a good description of us?
I think so. Maybe you want to add that we are a very lively community,
and that Git is so fast-moving that we regularly get feature requests that
have been addressed already ;-)
> ''' 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.
>
> ''sp>'' Talk about our challenges.
One challenge was that we had a third project, which was really
interesting, and the student was really interested, too, but for political
reasons he could not get the grant, and therefore the project had to be
stopped.
> ''' What license does your project use? '''
>
> GPL (GNU Public License)
.. v2 (I think by now there are enough parts limited to v2 that it does
not matter how much is "or later, at the discretion of Linus Torvalds").
> ''' 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 have always been warmly welcomed;
s/have//
> 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.
Thanks,
Dscho
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
