git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Google Summer of Code 2008

From
Jakub Narebski <jnareb@gmail.com>
Date
Feb 29, 2008, 12:04 UTC
Message-ID
<200802291304.16026.jnareb@gmail.com>
In-Reply-To
<alpine.LSU.1.00.0802281021070.22527@racer.site>
On Thu, 28 Feb 2008, Johannes Schindelin wrote:
Show 6 quoted lines
> 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.

Show 5 quoted lines
> 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
Previous: Johannes SchindelinNext: Julian Phillips
Message 7 of 20 in “Google Summer of Code 2008”
  1. Jakub NarebskiFeb 26, 2008
  2. Johannes SchindelinFeb 26, 2008
  3. Shawn O. PearceFeb 28, 2008
  4. Jeremy Maitin-ShepardFeb 28, 2008
  5. Johannes SchindelinFeb 28, 2008
  6. Johannes SchindelinFeb 28, 2008
  7. Jakub NarebskiFeb 29, 2008
  8. Julian PhillipsFeb 29, 2008
  9. Johannes SchindelinFeb 29, 2008
  10. Julian PhillipsMar 1, 2008
  11. Sam VilainMar 1, 2008
  12. Johannes SchindelinMar 1, 2008
  13. Sam VilainMar 1, 2008
  14. Jakub NarebskiMar 1, 2008
  15. Matthieu MoyMar 2, 2008
  16. Jakub NarebskiMar 2, 2008
  17. Matthieu MoyMar 2, 2008
  18. Martin LanghoffMar 2, 2008
  19. Johannes SchindelinMar 2, 2008
  20. Jonas FonsecaFeb 28, 2008

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.