From: Sam Vilain <sam@vilain.net>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Jakub Narebski <jnareb@gmail.com>,
"Shawn O. Pearce" <spearce@spearce.org>,
Robin Rosenberg <robin.rosenberg.lists@dewire.com>,
git@vger.kernel.org, John Hawley <warthog9@kernel.org>,
Julian Phillips <julian@quantumfyre.co.uk>
Subject: Re: Google Summer of Code 2008
Date: Sat, 01 Mar 2008 18:07:02 +1300 [thread overview]
Message-ID: <47C8E476.7070105@vilain.net> (raw)
In-Reply-To: <alpine.LSU.1.00.0803010102000.22527@racer.site>
Johannes Schindelin wrote:
>> Funnily enough, I'm actually a possible /student/ this year - I'm
>> studying full-time this year - not in Computer Science, but hey that's
>> not a requirement ;-), and perhaps finishing my GitTorrent
>> implementation in my breaks would be a nice way to earn US$5k.
>
> You have my vote. If this works out, I will be your mentor. As you know,
> I will not be easy to work with, but the outcome will be pleasing to you
> _and_ me.
>
> I think GitTorrent is a really interesting project. And since I do not
> have time to do it myself, I would really appreciate this to be a GSoC
> project, preferably a successful one (which is the reason I am willing to
> mentor it).
Excellent, well that was going to be the next question - who would be
the mentor, and what would they do?
I guess I could re-work this RFP to be a proposal to complete it;
http://utsl.gen.nz/git/gittorrent-rfp.txt
So far, the first two milestones on the plan are basically nailed, so
that's something of a head start. The test script fires up two nodes
that connect to each other, sends a choke message and then shuts down.
I'm quite happy with the stack being used (Moose - which is CLOS for
Perl, and Coro - coroutines, similar to stackless python). How about I
brush that up and we can take this discussion off-list.
Sam.
next prev parent reply other threads:[~2008-03-01 5:05 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-26 22:56 Google Summer of Code 2008 Jakub Narebski
2008-02-26 23:39 ` Johannes Schindelin
2008-02-28 6:36 ` Shawn O. Pearce
2008-02-28 7:03 ` Jeremy Maitin-Shepard
2008-02-28 10:27 ` Johannes Schindelin
2008-02-28 10:27 ` Johannes Schindelin
2008-02-29 12:04 ` Jakub Narebski
2008-02-29 12:47 ` Julian Phillips
2008-02-29 13:03 ` Johannes Schindelin
2008-03-01 1:37 ` Julian Phillips
2008-03-01 0:31 ` Sam Vilain
2008-03-01 1:03 ` Johannes Schindelin
2008-03-01 5:07 ` Sam Vilain [this message]
2008-03-01 23:53 ` Jakub Narebski
2008-03-02 16:05 ` Matthieu Moy
2008-03-02 16:46 ` Jakub Narebski
2008-03-02 18:05 ` Matthieu Moy
2008-03-02 23:04 ` Martin Langhoff
2008-03-02 23:35 ` Johannes Schindelin
2008-02-28 13:59 ` Jonas Fonseca
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=47C8E476.7070105@vilain.net \
--to=sam@vilain.net \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.com \
--cc=julian@quantumfyre.co.uk \
--cc=robin.rosenberg.lists@dewire.com \
--cc=spearce@spearce.org \
--cc=warthog9@kernel.org \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).