Re: The future of gitweb (long term goals)

From: Michael J Gruber <git@drmicha.warpmail.net>
Date: Feb 15, 2011, 09:09 UTC
Message-ID: <4D5A42B2.3090603@drmicha.warpmail.net>
In-Reply-To: <201102142039.59416.jnareb@gmail.com>

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.

...

Show 5 quoted lines

> 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.

> - easy installation even without admin rights
> - scanning for repositories (as an option)
> - lightweight

All of these are important for instaweb also. I consider instaweb a very underrated feature! (It also needs some works of love, not just appreciation, of course.)

> 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.

Michael