From: Joshua Roys <roysjosh@gmail.com>
To: Jakub Narebski <jnareb@gmail.com>
Cc: git@vger.kernel.org, Sam Vilain <sam@vilain.net>,
Sverre Rabbelier <alturin@gmail.com>,
Sverre Rabbelier <sverre@rabbelier.nl>,
David Symonds <dsymonds@gmail.com>,
Lea Wiemann <LeWiemann@gmail.com>,
John Hawley <warthog19@eaglescrag.net>,
Marek Zawirski <marek.zawirski@gmail.com>,
"Shawn O. Pearce" <spearce@spearce.org>,
Miklos Vajna <vmiklos@frugalware.org>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Stephan Beyer <s-beyer@gmx.net>,
Christian Couder <chriscool@tuxfamily.org>,
Daniel Barkalow <barkalow@iabervon.org>,
Junio Hamano <gitster@pobox.com>
Subject: Re: [GSoC] Git projects for Google Summer of Code 2008 final evaluation
Date: Thu, 04 Sep 2008 18:22:45 -0400 [thread overview]
Message-ID: <48C05FB5.3010901@gmail.com> (raw)
In-Reply-To: <200809042315.58898.jnareb@gmail.com>
Jakub Narebski wrote:
>
> So students and mentors, please write what do you think current status
> of project is: is it done, is it ready, is it perhaps already merged
> in, or can be merged in at any time. Please write also what wasn't
> done, or what should be done different way (hindsight and all that).
>
> Students, could you please tell us if you plan to work on git further,
> and in what range (how much time can you get to work on git). What do
> you think about git development community? What have you learned from
> participating in GSoC?
>
> 1. GitTorrent
>
> Student: Joshua Roys
> Mentor: Sam Vilain
>
Hello all,
VCS::Git::Torrent can only transfer data under limited circumstances at
the moment, and doesn't do peering. Part of that is actually due to
work done after the deadline, unfortunately for me :-) Anyway, I am
definitely interested in continuing to work on git (and GitTorrent) as
it is the VCS I use personally. It is, however, the start of the
semester here and I am currently focusing on that and job searching as
this is my last semester.
I had a really good experience working with the git community over the
past few months. It was really cool to see very talented people working
together. It was a little intimidating too. Another thing I learned
about was the 'O' in OSS, or being 'Open' about development. This is a
completely different paradigm for me, as all of my previous experience
is personal development or 'corporate' development (things done at
work), neither of which required telling anybody about anything until
completion. Regular status updates that were requested during the
second half made that much more clear and, in fact, facilitated my
understanding in this area.
So, thank you all again, and I hope to continue to work with you in the
future.
Joshua Roys
next prev parent reply other threads:[~2008-09-04 22:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-04 21:15 [GSoC] Git projects for Google Summer of Code 2008 final evaluation Jakub Narebski
2008-09-04 22:10 ` Daniel Barkalow
2008-09-04 22:22 ` Joshua Roys [this message]
2008-09-04 22:36 ` Stephan Beyer
2008-09-04 22:44 ` Sverre Rabbelier
2008-09-04 22:55 ` Miklos Vajna
2008-09-04 23:04 ` Shawn O. Pearce
2008-09-08 17:46 ` Marek Zawirski
2008-09-09 14:52 ` Johannes Schindelin
2008-09-15 12:13 ` Jakub Narebski
2008-09-15 12:40 ` Johannes Schindelin
2008-09-15 14:08 ` Shawn O. Pearce
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=48C05FB5.3010901@gmail.com \
--to=roysjosh@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=LeWiemann@gmail.com \
--cc=alturin@gmail.com \
--cc=barkalow@iabervon.org \
--cc=chriscool@tuxfamily.org \
--cc=dsymonds@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jnareb@gmail.com \
--cc=marek.zawirski@gmail.com \
--cc=s-beyer@gmx.net \
--cc=sam@vilain.net \
--cc=spearce@spearce.org \
--cc=sverre@rabbelier.nl \
--cc=vmiklos@frugalware.org \
--cc=warthog19@eaglescrag.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).