From: Jakub Narebski <jnareb@gmail.com>
To: Michael J Gruber <git@drmicha.warpmail.net>
Cc: git@vger.kernel.org, John Hawley <warthog9@kernel.org>
Subject: Re: The future of gitweb (long term goals)
Date: Mon, 21 Feb 2011 23:06:35 +0100 [thread overview]
Message-ID: <201102212306.39084.jnareb@gmail.com> (raw)
In-Reply-To: <4D5A42B2.3090603@drmicha.warpmail.net>
On Tue, 15 Feb 2011, Michael J Gruber wrote:
> Jakub Narebski venit, vidit, dixit 14.02.2011 20:39:
> > Now that we are talking about future of git, including breaking some
> > of backwards compatibility bugs / misdesigns for 1.8.0, perhaps it is
> > the time to discuss long term goals and the future of gitweb.
> ...
> > Current requirements are:
> > - Perl 5.8.x (for proper Unicode / UTF-8 support)
> > - core Perl modules: CGI, Encode, Fcntl, File::Find, File::Basename,...
> > - non-core Perl modules optional, needed for some of extra features
> > - backward compatibility (query params and path_info URLs)
>
> I'd second that this is important for adaption by some main users.
You mean here backward compatibility of API (i.e. old links keep working),
isn't it?
> > - easy installation even without admin rights
> > - scanning for repositories (as an option)
> > - lightweight
>
> All of these are important for instaweb also.
Nowadays git-instaweb uses _installed_ gitweb, so neither easy
installation, nor installing / running without admin rights is necessary
for use of gitweb in git-instaweb. Strictly speaking neither is scanning
for repositories; I think git-isnatweb could generate file with list of
repositories (with repository) to show.
> I consider instaweb a very
> underrated feature! (It also needs some works of love, not just
> appreciation, of course.)
Beside adding support for new web servers (like recently added 'plackup'),
what do you thing needs to be done?
> > 1. Splitting gitweb into modules (packages), for better maintainability.
>
> Also, this may help including other optional parts. The graph viewer as
> used on repo.or.cz sets gitweb apart from quite a few alternatives and
> would be used more widely if it were an optional module shipping with
> gitweb. Just imagine instaweb with graphs ;)
> Also, being part of gitweb, the viewer may attract a few coders.
Well, adding anything major (like e.g. write functionality, output caching;
perhaps graph of history is also in this category) really require split
gitweb. It is getting hard to maintain gitweb as it is now.
--
Jakub Narebski
Poland
next prev parent reply other threads:[~2011-02-21 22:07 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-14 19:39 The future of gitweb (long term goals) Jakub Narebski
2011-02-15 9:09 ` Michael J Gruber
2011-02-21 22:06 ` Jakub Narebski [this message]
2011-02-23 10:54 ` Michael J Gruber
2011-02-25 22:37 ` The future of git-instaweb (was: Re: The future of gitweb (long term goals)) Jakub Narebski
2011-02-22 17:02 ` The future of gitweb (long term goals) Ævar Arnfjörð Bjarmason
2011-02-22 18:17 ` Jakub Narebski
2011-04-14 9:54 ` The future of gitweb - part 2: JavaScript Jakub Narebski
2011-04-14 19:30 ` Michał Łowicki
2011-04-15 1:56 ` david
2011-04-16 17:12 ` Peter Vereshagin
2011-04-16 19:32 ` Jakub Narebski
2011-04-16 20:48 ` Peter Vereshagin
2011-04-16 21:17 ` Jakub Narebski
2011-04-16 21:53 ` Peter Vereshagin
2011-04-16 22:19 ` Jakub Narebski
2011-04-16 22:33 ` Jakub Narebski
2011-04-16 23:00 ` Peter Vereshagin
2011-04-17 10:11 ` Jakub Narebski
2011-04-20 18:24 ` Gitweb != HTTP back-end {Was: Re: The future of gitweb - part 2: JavaScript} Drew Northup
2011-04-20 18:47 ` Jakub Narebski
2011-04-16 17:44 ` The future of gitweb - part 2: JavaScript Pau Garcia i Quiles
2011-04-17 14:59 ` Jakub Narebski
2011-04-17 15:14 ` Pau Garcia i Quiles
2011-04-18 18:13 ` Jakub Narebski
2011-04-17 20:14 ` Petr Baudis
2011-04-18 13:34 ` Jakub Narebski
2011-04-18 13:50 ` Petr Baudis
2011-04-18 14:15 ` Jakub Narebski
2011-04-20 18:39 ` Drew Northup
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=201102212306.39084.jnareb@gmail.com \
--to=jnareb@gmail.com \
--cc=git@drmicha.warpmail.net \
--cc=git@vger.kernel.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).