All of lore.kernel.org
 help / color / mirror / Atom feed
From: Petr Baudis <pasky@suse.cz>
To: Junio C Hamano <gitster@pobox.com>
Cc: Jakub Narebski <jnareb@gmail.com>, git@vger.kernel.org
Subject: Re: repo.or.cz renovated
Date: Mon, 17 Mar 2008 20:25:28 +0100	[thread overview]
Message-ID: <20080317192528.GE10335@machine.or.cz> (raw)
In-Reply-To: <7vhcf5b21n.fsf@gitster.siamese.dyndns.org>

On Mon, Mar 17, 2008 at 12:09:24PM -0700, Junio C Hamano wrote:
> Petr Baudis <pasky@suse.cz> writes:
> 
> > My current plan is to have a [Search project] box at the front page,
> > together with direct link to 'show all'. Other than that, what makes
> > sense to display on the front page? I think recently added projects (age
> > < 1 week) for sure. I'm not so sure about recently changed projects -
> > maybe it is better to keep the front page cruft-free.
> 
> "More important projects"?
> 
> ;-) Ducks...

I'm all for that, get access to projects people are the most likely to
look for. Would it make sense to count accesses to index pages of each
project and then sort by that? Or sort by some activity index?

> How about asking project owners to categorize (tag) their own projects and
> show them in different categories?  Maybe many of them will start in
> "unsorted bin", but if you organize the top page in such a way that the
> link to unsorted bin is much less prominent than nicely sorted ones, that
> may give people incentive to put their project in a real category.

Actually, no reason to restrict tagging to project owners. This might be
interesting, but again the question is, does anyone really want to
browse the project list based on "show me all kernel-related projects"
or "show me all xorg-related projects", especially as we have forks and
it may not be reliable?

-- 
				Petr "Pasky" Baudis
Whatever you can do, or dream you can, begin it.
Boldness has genius, power, and magic in it.	-- J. W. von Goethe

  reply	other threads:[~2008-03-17 19:26 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-13 23:14 [PATCH] gitweb: Support caching projects list Petr Baudis
2008-03-14  0:07 ` Jay Soffian
2008-03-14  0:22   ` Petr Baudis
2008-03-14  0:27     ` Jay Soffian
2008-03-14  0:30       ` J.H.
2008-03-14 12:17         ` Jakub Narebski
2008-03-14  0:36     ` J.H.
2008-03-17 17:49       ` repo.or.cz renovation Petr Baudis
2008-03-17 18:11         ` Petr Baudis
2008-03-17 18:44         ` J.H.
2008-03-17 20:41           ` Jakub Narebski
2008-03-17 21:09           ` Jakub Narebski
2008-03-14 15:29   ` [PATCH] gitweb: Support caching projects list Jakub Narebski
2008-03-14 21:11     ` Jay Soffian
2008-03-14  0:19 ` Junio C Hamano
2008-03-14  8:35 ` Frank Lichtenheld
2008-03-14 12:14 ` Jakub Narebski
2008-03-17 17:40   ` Petr Baudis
2008-03-15 21:44 ` Jakub Narebski
2008-03-16  0:56   ` Miklos Vajna
2008-03-16 11:41   ` Frank Lichtenheld
2008-03-16 16:52     ` J.H.
2008-03-16 18:37       ` Jakub Narebski
2008-03-16 22:37         ` J.H.
2008-03-16 23:39           ` Jakub Narebski
2008-03-17 18:10   ` repo.or.cz renovated Petr Baudis
2008-03-17 19:09     ` Junio C Hamano
2008-03-17 19:25       ` Petr Baudis [this message]
2008-03-17 19:34     ` Theodore Tso
2008-03-17 19:54       ` 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=20080317192528.GE10335@machine.or.cz \
    --to=pasky@suse.cz \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=jnareb@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.