git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Jakub Narebski <jnareb@gmail.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: "Shawn O. Pearce" <spearce@spearce.org>,
	Robin Rosenberg <robin.rosenberg.lists@dewire.com>,
	git@vger.kernel.org, John Hawley <warthog9@kernel.org>
Subject: Re: Google Summer of Code 2008
Date: Fri, 29 Feb 2008 13:04:15 +0100	[thread overview]
Message-ID: <200802291304.16026.jnareb@gmail.com> (raw)
In-Reply-To: <alpine.LSU.1.00.0802281021070.22527@racer.site>

On Thu, 28 Feb 2008, Johannes Schindelin wrote:
> Do go ahead!  I started the page
> 
>         http://git.or.cz/gitwiki/SoC2008Ideas
> 
> which is utterly incomplete.  I just took the ideas of 2007 that I am 
> still interested in,

By the way, when looking at 2007 GSoC ideas one can see that some of 
them got implemented already outside of GSoC, and are no longer valid; 
well, perhaps as "improve <sth>" ideas. 

Subproject/submodule support got implemented, Mozilla has decided to use 
Mecurial instead of Git (but there are other large-scale imports: 
OpenOffice.org, GCC) and cvs2svn supports fast-import output which 
means export to git, gitattributes support got much extended.

> and removed other people from the Mentor list,  
> because I do not want to force them.  So please, if you are interested
> in mentoring one of the existing projects, just add yourself.
> 
> And of course add all those cool projects you have in mind.

I have some interesting ideas for GSoC, but unfortunately none (with 
perhaps single exception) that I could mentor. So I think I'd list them 
here for now, and later I'd add it to SoC2008Ideas page.

Here they are.

First, a few ideas which got partially implemented already, or are 
implemented and need improvements. I don't know if current contributors 
would want to be mentors, or would they want to submit their work under 
GSoC as participants.

* Lazy clone / remote alternates

  The idea here is to be able to remotely access objects from a network
  based object server, as neededm rather than having them all local.

  Goal: A working lazy clone prototype implementation that could be
  considered for inclusion, in a nice series of commits (separate
  branch/fork)
  Language: C
  Suggested mentor: Jan Holesovsky, who submitted proof-of-concept
  patch for lazy clone

* Partial (subtree) checkout, or its generalization: sparse checkout

  The idea is to checkout for example only Documentation subdirectory,
  work on it, but commit full tree. Some workflows may be better suited
  to this type of usage than using submodules. Optionally should include
  partial clone (not needed objects not in repository).

  Goal: A working partial checkout prototype implementation, with
  technical documentation.
  Language: C
  Suggested mentors: 
    gitzilla (sent proposal), 
    Nguyen Thai Ngoc Duy (pclouds), proposed to implements it

* Gitweb caching

  Implementing very smart caching in gitweb, to avoid the thundering
  herd problem on kernel.org whenever a repository gets updated, or at
  least support for caching engines in the form of generating proper
  Last-Modified: and ETag: headers, and responding to If-Modified-Since:
  and If-None-Match: requests, cheaply. 

  Perhaps becoming the gitweb maintainer could come of it, or at least
  the gitweb admin for kernel.org (sorely needed).

  Goal: At minimum, port kernel.org's caching to mainline (git's) gitweb
  Language: Perl, HTML, perhaps JavaScript
  Suggested mentors:
    John 'Warthog9' Hawley (wrote caching for kernel.org's gitweb)
    Petr Baudis (repo.or.cz admin)
    Lars Hjemli (cgit author, git web interface in C, with caching)
    Jakub Narebski (gitweb contributor)

Then, a few ideas which were proposed for GSoC 2007, but never 
implemented, and wasn't mentioned in this thread or on wiki for
GSoC 2008 yet

* Git / Subversion Interoperability

  The idea here is implement something in Git that speaks the Subversion
  protocol on the wire, but uses Git as the backend storage. (This would
  be like the existing git-cvsserver.)

  There are two potential approaches:

   1. git-svnserver
   2. write a backend for Subversion

  Goal: To be able to access git repository, at minimum read-only, from
  a Subversion client, at least svn CLI.
  Language: Open for proposal.
  Suggested mentors: 
    Eric Wong (git-svn author)
    Matthias Urlichs (git-svnimport author)
  Notes: I don't think we could pass it as Subversion SoC project, but
  I guess that we could ask for co-mentor for the Subversion protocol,
  or Subversion backend part of this task.

I'd send other ideas (including new ones, like translating svn:externals 
into git submodules in git-svn; or making git mode for Emacs have all 
features of tig, git-gui and gitk; or improving shallow clone support)
in a later post.

> Shawn, do we have to do the same again, as on this page?
> 
>         http://git.or.cz/gitwiki/Soc2007Application

A few things changes for us: we have participated in GSoC 2007; we need 
to find backup organization administrator (was: Martin Langhoff for 
GSoC2007), list of mentors would change most probably.

As far as I've checked the application form for organizations didn't 
change...
-- 
Jakub Narebski
Poland

  reply	other threads:[~2008-02-29 12: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 [this message]
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

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=200802291304.16026.jnareb@gmail.com \
    --to=jnareb@gmail.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --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).