From: Christian Couder <chriscool@tuxfamily.org>
To: git@vger.kernel.org
Cc: Jakub Narebski <jnareb@gmail.com>,
Junio C Hamano <gitster@pobox.com>,
Sverre Rabbelier <srabbelier@gmail.com>,
Petr Baudis <pasky@ucw.cz>, Shawn O Pearce <spearce@spearce.org>,
Scott Chacon <schacon@gmail.com>,
Pavan Kumar Sunkara <pavan.sss1991@gmail.com>,
Sam Vilain <sam@vilain.net>,
catalyst@lists.scsys.co.uk
Subject: GSoC 2010: "Integrated Web Client for git" proposal
Date: Thu, 15 Apr 2010 05:30:44 +0100 [thread overview]
Message-ID: <201004150630.44300.chriscool@tuxfamily.org> (raw)
Hi!
Pavan Kumar Sunkara sent an email on the git mailing list a few days ago about
his GSoC proposal:
http://thread.gmane.org/gmane.comp.version-control.git/144658/
His proposal is based on the project he already started:
http://github.com/pkumar/gittor
There have been discussions about it on the GSoC web app and in some private
emails.
Possible GSoC mentors for this proposal don't want yet another web interface,
they want an existing interface to be improved on. As the obvious choice is to
improve gitweb, the current result from the discussions is that the proposal
should be changed so that the integrated web client is developed in Perl into
or alongside gitweb.
Pavan agreed to rewrite his proposal according to that and Petr and myself
volunteered to co-mentor him.
It was suggested that improving Gitalist
(http://wiki.catalystframework.org/wiki/gitalist) would be a better choice.
But this was rejected because Gitalist is too much different from gitweb so it
could not replace it for many people now using gitweb.
Best regards,
Christian.
next reply other threads:[~2010-04-15 4:31 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-15 4:30 Christian Couder [this message]
2010-04-18 0:46 ` GSoC 2010: "Integrated Web Client for git" proposal Jakub Narebski
2010-04-18 0:59 ` Petr Baudis
2010-04-18 1:24 ` Jakub Narebski
2010-04-18 2:12 ` Petr Baudis
2010-04-18 8:52 ` Pavan Kumar Sunkara
2010-04-18 21:22 ` Jakub Narebski
[not found] ` <w2pe72faaa81004182334xd6fc56d7o31420ca4af867cc2@mail.gmail.com>
2010-04-19 6:35 ` Pavan Kumar Sunkara
2010-04-19 17:00 ` Jakub Narebski
2010-04-19 17:55 ` Pavan Kumar Sunkara
2010-04-19 23:14 ` Jakub Narebski
2010-04-20 12:17 ` Pavan Kumar Sunkara
2010-04-18 22:31 ` Petr Baudis
2010-04-19 6:46 ` Pavan Kumar Sunkara
2010-04-19 6:50 ` Matthieu Moy
2010-04-19 7:23 ` Junio C Hamano
2010-04-19 7:38 ` Pavan Kumar Sunkara
2010-04-19 9:07 ` Petr Baudis
2010-04-19 12:27 ` Matthieu Moy
2010-04-19 12:57 ` Pavan Kumar Sunkara
2010-04-19 13:14 ` Matthieu Moy
2010-04-19 11:57 ` Petr Baudis
2010-04-19 18:10 ` Pavan Kumar Sunkara
2010-04-20 11:47 ` Petr Baudis
2010-04-18 17:50 ` Jakub Narebski
2010-04-18 19:56 ` Petr Baudis
2010-04-19 10:43 ` Jakub Narebski
2010-04-19 11:51 ` Petr Baudis
2010-04-19 18:03 ` Pavan Kumar Sunkara
2010-04-20 12:07 ` Petr Baudis
2010-04-20 18:14 ` Jakub Narebski
2010-04-21 20:49 ` Pavan Kumar Sunkara
2010-04-22 20:25 ` Petr Baudis
2010-04-22 21:15 ` Junio C Hamano
2010-04-23 7:10 ` Petr Baudis
2010-04-23 9:44 ` Junio C Hamano
2010-04-22 21:53 ` Pavan Kumar Sunkara
2010-04-23 5:27 ` Christian Couder
2010-04-23 5:42 ` Pavan Kumar Sunkara
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=201004150630.44300.chriscool@tuxfamily.org \
--to=chriscool@tuxfamily.org \
--cc=catalyst@lists.scsys.co.uk \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jnareb@gmail.com \
--cc=pasky@ucw.cz \
--cc=pavan.sss1991@gmail.com \
--cc=sam@vilain.net \
--cc=schacon@gmail.com \
--cc=spearce@spearce.org \
--cc=srabbelier@gmail.com \
/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).