From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Cc: Sam Vilain <sam@vilain.net>, Joshua Roys <roysjosh@gmail.com>,
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>
Subject: [GSoC] What is status of Git's Google Summer of Code 2008 projects?
Date: Tue, 8 Jul 2008 02:27:41 +0200 [thread overview]
Message-ID: <200807080227.43515.jnareb@gmail.com> (raw)
I'd very much like to have (or perhaps to wrote) some sort of interim
progress report for Google Summer of Code 2008 projects on
http://git.or.cz/gitwiki/SoC2008Projects. Therefore I'd like you to
expand and/or correct those mini-summaries below.
(It would be, I guess, good preparation for GSoC 2008 mid-term
evaluations, which according to GSoC 2008 timeline
http://code.google.com/opensource/gsoc/2008/faqs.html#0.1_timeline
are to take place July 7 -- July 14.)
1. GitTorrent (???)
Student: Joshua Roys
Mentor: Sam Vilain
There was short thread of me asking about project
http://thread.gmane.org/gmane.comp.version-control.git/83611
where I got gittorrent mailing list (no activity at least according to
list archive http://lists.utsl.gen.nz/pipermail/gittorrent/) and URL
for project repo / gitweb... which is currently down, so I cannot check
if there is anything here.
What is the status of this project, please?
http://www.codinghorror.com/blog/archives/001134.html ("Don't Got Dark")
2. git-statistics (?)
Student: Sverre Rabbelier
Mentor: David Symonds
There were some posts about how git-statistics can be used:
http://thread.gmane.org/gmane.comp.version-control.git/81534
http://thread.gmane.org/gmane.comp.version-control.git/82027
but it was mainly theoretical thread
The git-stats repository at http://repo.or.cz/w/git-stats.git (gitweb)
has some commits, but I don't remember any of them on git mailing list.
Not ready?
3. Gitweb caching
Student: Lea Wiemann
Mentor: John 'warthog' Hawley
Lea has chosen caching data and memcached as primary caching engine,
and is working on object layer on top of Git.pm, namely Git::Repo and
friends, which will be used by gitweb. If I understand correctly
caching is to be done, or at least helped by this layer.
There were added tests for Git.pm (now in git.git I think) and Mechanize
test for gitweb (which detected a few errors).
Is it correct?
4. Eclipse plugin push support (!)
Student: Marek Zawirski
Mentor: Shawn O. Pearce
I am not following egit/jgit development close enough, but if I remember
correctly there is some code which provides very rudimentary support
for native generation of simplified packs, and IIRC also for push over
some protocols.
And there is push support over SFTP and (encrypted) Amazon S3...
5. git-merge builtin (!!!)
Student: Miklos Vajna
Mentor: Johannes Schindelin
Builtin merge, together with preparation patches, is now at n-th
iteration, as shown in the "Build in merge" thread:
http://thread.gmane.org/gmane.comp.version-control.git/86584
In "What's cooking in git.git (topics)" Junio C Hamano wrote:
It already is beginning to become clear what 1.6.0 will look like.
[...]
* git-merge will be rewritten in C.
6. git-sequencer (!)
Student: Stephan Beyer
Mentor: Christian Couder, Daniel Barkalow
It started with discussion over TODO file format:
http://thread.gmane.org/gmane.comp.version-control.git/84230
Now there is prototype shell script implementation (which has some
limitations because it is prototype) in "git sequencer prototype"
http://thread.gmane.org/gmane.comp.version-control.git/86985
Stephan Beyer wrote:
I'm using sequencer-based git-am and git-rebase-i and also
git-sequencer itself for around 2-3 weeks now. So, for me, it is
reality-proven [...]
--
Jakub Narebski
Poland
next reply other threads:[~2008-07-08 0:28 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-08 0:27 Jakub Narebski [this message]
2008-07-08 0:43 ` [GSoC] What is status of Git's Google Summer of Code 2008 projects? David Symonds
2008-07-08 1:00 ` Stephan Beyer
2008-07-08 1:14 ` Junio C Hamano
2008-07-08 1:47 ` Stephan Beyer
2008-07-08 7:39 ` Jakub Narebski
2008-07-08 14:42 ` Stephan Beyer
2008-07-08 16:12 ` Jakub Narebski
2008-07-08 16:34 ` Stephan Beyer
2008-07-08 17:31 ` Jakub Narebski
2008-07-08 4:08 ` Lea Wiemann
2008-07-08 7:20 ` J.H.
2008-07-08 4:19 ` Shawn O. Pearce
2008-07-08 16:31 ` Joshua Roys
2008-07-08 16:45 ` Johannes Schindelin
2008-07-08 17:22 ` Jakub Narebski
2008-07-08 17:00 ` Petr Baudis
2008-07-08 21:24 ` Sam Vilain
2008-07-09 10:18 ` Sverre Rabbelier
2008-07-09 10:56 ` Miklos Vajna
2008-07-09 11:36 ` Jakub Narebski
2008-07-20 22:29 ` Jakub Narebski
2008-07-20 22:43 ` Sverre Rabbelier
2008-07-20 22:57 ` Stephan Beyer
2008-07-21 0:55 ` Sam Vilain
2008-07-21 1:05 ` Johannes Schindelin
2008-07-21 10:23 ` Jakub Narebski
2008-07-21 10:40 ` Petr Baudis
2008-07-21 13:23 ` Joshua Roys
2008-07-21 3:22 ` Shawn O. Pearce
2008-08-17 5:26 ` Sverre Rabbelier
2008-08-14 2:57 ` Jakub Narebski
2008-08-14 12:42 ` Sam Vilain
2008-08-14 23:17 ` Petr Baudis
2008-08-14 23:23 ` Jakub Narebski
2008-08-14 23:04 ` Johannes Schindelin
2008-08-15 19:38 ` Lea Wiemann
2008-08-15 20:36 ` Jakub Narebski
2008-08-16 1:16 ` Stephan Beyer
2008-08-16 1:22 ` Shawn O. Pearce
2008-08-16 3:10 ` Jakub Narebski
2008-08-17 20:49 ` Marek Zawirski
2008-08-18 5:51 ` Shawn O. Pearce
2008-08-19 1:25 ` Joshua Roys
2008-08-20 6:19 ` Sam Vilain
2008-08-22 23:03 ` Stephan Beyer
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=200807080227.43515.jnareb@gmail.com \
--to=jnareb@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=marek.zawirski@gmail.com \
--cc=roysjosh@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).