git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "Jonas Fonseca" <jonas.fonseca@gmail.com>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: "Johannes Schindelin" <Johannes.Schindelin@gmx.de>,
	"Jakub Narebski" <jnareb@gmail.com>,
	git@vger.kernel.org
Subject: Re: Google Summer of Code 2008
Date: Thu, 28 Feb 2008 14:59:53 +0100	[thread overview]
Message-ID: <2c6b72b30802280559o4eda2d36m1cb85e5ea7a863f0@mail.gmail.com> (raw)
In-Reply-To: <20080228063621.GR8410@spearce.org>

Hello,

On Thu, Feb 28, 2008 at 7:36 AM, Shawn O. Pearce <spearce@spearce.org> wrote:
> Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
>  > On Tue, 26 Feb 2008, Jakub Narebski wrote:
>  > As for projects, I imagine that Gitorrent, further builtinification and
>  > Windows support would be good candidates.
>
>  Yea, Gitorrent would be cool.  Especially since send-pack is
>  somewhat heavy on the server's resources and there are some very
>  popular projects offered in git format (hello Linux kernel!).

I will take this opportunity to add a few comments and promote a page.
To help improve chances of success for such a project, perhaps a
"community" edition of the protocol is in order. I have been planning
(and still are) to do a review of the protocol specification with input
from the mailing list. Basically, I am thinking to break the current RFC
document into self-contained chunks: a formal introduction + goals,
meta file and tracker part, and finally repository serialization and peer
wire.

In preparation, I started to populate pages at:

  http://gittorrent.googlecode.com/

If there is interest I will try to find time to restart this process.

-- 
Jonas Fonseca

      parent reply	other threads:[~2008-02-28 14:00 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
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 [this message]

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=2c6b72b30802280559o4eda2d36m1cb85e5ea7a863f0@mail.gmail.com \
    --to=jonas.fonseca@gmail.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=jnareb@gmail.com \
    --cc=spearce@spearce.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).