git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Narebski <jnareb@gmail.com>
To: Dill <sarpulhu@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: RFC: Website redesign
Date: Tue, 15 Apr 2008 00:59:49 -0700 (PDT)	[thread overview]
Message-ID: <m3mynvsg40.fsf@localhost.localdomain> (raw)
In-Reply-To: <acfbfe5b-f3a1-4c22-a873-ed329552d1bb@b5g2000pri.googlegroups.com>

Dill <sarpulhu@gmail.com> writes:

> Perhaps we should just make the home page a wiki! It would work really
> good! If we use a theme like they do at wiki.ubuntu.com or somewhere
> else we could make it look really nice for a home page. Then once it's
> set up, no one has to manage the page, worry about commits, who's
> doing what, etc, and just have the pages edited and worked on by the
> community at large who register at the site to edit. 

First, as far as I now all _popular_ wikis offer quite limited markup.

Second, current git homepage has information about latest release, and
latest release date etc. updated *automatically*, by the script IIRC
examinimg announcement on git mailing list.  This I think would be not
possible with wiki.

> (Unlike the wiki in use now something would have to be done to stop
> the spam, like having those boxes at registration where you have
> pick the letters out).

If you have wiki which is popular page you would have spam.  Or you
wouldn't have contributors (or at least as many contributors) if you
would bring barriers to entry (e.g. register to edit, validation via
email, CAPTCHA) against spam.

[cut] 
Many more projects IMVHO have _both_ homepage and wiki, than only wiki
(wiki as homepage).

P.S. Please do not toppost.  If your post doesn't refer to the message
you are replying to, simply post it as clean message, without quoted
text.
-- 
Jakub Narebski
Poland
ShadeHawk on #git

  reply	other threads:[~2008-04-15  8:01 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-14  5:37 RFC: Website redesign Dill
2008-04-14 13:56 ` Jonas Fonseca
2008-04-14 15:38   ` Dill
2008-04-14 17:03     ` Wincent Colaiuta
2008-04-14 18:29       ` Sverre Rabbelier
2008-04-14 20:39         ` Anand Kumria
2008-04-14 21:33           ` Dmitry Potapov
2008-04-15  3:24             ` Anand Kumria
2008-04-15  5:05               ` Dill
2008-04-15  6:48                 ` Dill
2008-04-15  7:59                   ` Jakub Narebski [this message]
2008-04-15 11:57                   ` Petr Baudis
2008-04-15 16:20                     ` Git Homepge Update Petr Baudis
2008-04-15 17:57                       ` Steve Hoelzer
2008-04-16  1:36                       ` Jakub Narebski
2008-04-15  7:08               ` RFC: Website redesign Dmitry Potapov
2008-04-15  7:53               ` Jakub Narebski
2008-04-15 14:33                 ` Petr Baudis
2008-04-15 11:54     ` Petr Baudis
2008-04-15 18:04       ` Junio C Hamano

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=m3mynvsg40.fsf@localhost.localdomain \
    --to=jnareb@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=sarpulhu@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).