From: "J.H." <warthog19@eaglescrag•net>
To: Petr Baudis <pasky@suse•cz>
Cc: git@vger•kernel.org
Subject: Re: [PATCH] gitweb: Support for no project list on gitweb front page
Date: Fri, 06 Nov 2009 11:03:01 -0800 [thread overview]
Message-ID: <4AF472E5.1000602@eaglescrag.net> (raw)
In-Reply-To: <1257520265-16699-1-git-send-email-pasky@suse.cz>
Petr Baudis wrote:
> On very large sites like repo.or.cz (but maybe also git.debian.org,
> git.kernel.org, etc.),
I think between our own caching (which I'll be submitting a cleaned up
patch for here shortly for mainline inclusion) and our users want to
*NOT* deal with searching or pagination this actually isn't that useful
to us, despite having a signifigant number of projects, and the front
page (at leas for us) only weighing in at 567,710bytes means that we are
moving less data to show the git.kernel.org page than facebook does to
show their home screen (I.E. anything modern can trivially cope with that)
> it is desirable not to have the project list
> on the front page since generating it is significant overhead and it
> takes significant data transfer and load time for the user, who might
> prefer to instead use the search form and possibly content tags to
> navigate to the target project. A link to the full list of projects is
> still available on the front page for users who wish to browse it. The
> whole feature is turned off by default.
>
> The patch introduces a new config variable $frontpage_no_project_list,
> by default 0 keeping the current behavior; if set to 1, no project list
> will be shown, but all projects will be still scanned if ctags are
> enabled; if set to 2, no project will be shown and no projects will
> be scanned while showing the front page. The compromise value of 1 is
> useful for sites where project scan time is not an issue or which
> use additional project list caching patches.
I question the need for 0,1,2. If the site doesn't want something like
the tag cloud they are already going to turn it off with the normal
cloud system. I think this should be either a bitmask or an array to
explicitly turn particular things on or off, or a binary value that
would *ONLY* deal with showing the project listing.
- John 'Warthog9' Hawley
next prev parent reply other threads:[~2009-11-06 19:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-06 15:10 [PATCH] gitweb: Polish the content tags support Petr Baudis
2009-11-06 15:11 ` [PATCH] gitweb: Support for no project list on gitweb front page Petr Baudis
2009-11-06 15:10 ` [PATCH] gitweb: Refactor project list routines Petr Baudis
2009-11-06 15:22 ` Petr Baudis
2009-11-06 18:56 ` J.H.
2009-11-16 17:56 ` Petr Baudis
2009-11-06 19:03 ` J.H. [this message]
2009-11-16 17:52 ` [PATCH] gitweb: Support for no project list on gitweb front page Petr Baudis
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=4AF472E5.1000602@eaglescrag.net \
--to=warthog19@eaglescrag$(echo .)net \
--cc=git@vger$(echo .)kernel.org \
--cc=pasky@suse$(echo .)cz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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