From: "PJ Hyett" <pjhyett@gmail.com>
To: git@vger.kernel.org
Subject: git-scm.com (was Re: Git graph on GitHub)
Date: Wed, 15 Oct 2008 03:18:09 -0700 [thread overview]
Message-ID: <bab6a2ab0810150318pb616a6dj867efa36623ac12e@mail.gmail.com> (raw)
In-Reply-To: <bab6a2ab0810150315l273d4ef3k95cda8f43a4745ca@mail.gmail.com>
> One nitpick regarding your git.git mirror: I doubt that people here
> ("the community") consider git-scm.com to be "the git homepage". I don't
> want to go into the reasons and start a pointless thread, but since
> git-scm.com is a fork of git.or.cz pointing to the latter (the root)
> should make everyone happy.
Hi Michael,
I'll go ahead and start a pointless thread along with the reasons
provided via answers to the 2008 Git Survey[1]:
43) What could be improved on the Git homepage(s)?
* Use git-scm.com instead of git.or.cz as the default homepage
* Learn from git-scm.com. Make it more newbie-friendly. More focus on
documentation
* Better graphical design/organization - new(?) git-scm.com looks better
* Look at git-scm.com :)
* Cleaner design, better organization (http://git-scm.com/ is a good start).
* Design - git-scm.com is superior compared to git.or.cz. Also the
first one is more user-friendly having exposed more important things
for users rather for experienced veterans who want to download most
current git release.
* I like what Scott Chacon has done with http://git-scm.com
* I prefer Scot Chacons rewrite, but mostly just it's look and feel.
The original site is perfectly functional; though it could do with
better documentation.
* git-scm.com
* git-scm.com is a great example of some light improvement. I do think
that the online man-page navigation is a little annoying, having to
revert to find in the browser to get to the right spot on the page. An
alternate alphabetical listing might help.
* Don't put everything on the first page, it is a little confusing.
Create categories, like download, documentation, About git and at
least a dedicated page for each of these categories. I think the
"design" could also be improved. I saw a proposition not long ago
aboutr a new git homepage on the mailing list: www.git-scm.com. I
think this site is easier to navigate and thus makes it easier to find
informations.
* I like the new git-scm site (with the blob committed to storing trees)
* Merge with Git-scm page?
* I like <http://www.git-scm.com> very much. I'd vote for it to be the
official Git homepage.
* git.or.cz?? I prefer http://git-scm.com/, it's better for beginners,
and the information is nicely presented (doc, tips, videos..).
* promote git-scm.com instead of git.or.cz
* See http://git-scm.com/
* I think git-scm.com is starting to get things right. Making
documentation readily available especially.
* Complete re-design by somebody actually the least bit proficient in
design? Oh wait, that's already been done at http://git-scm.com/.
* Rather ugly design. git-scm.com looks much better.
* I like Scott Chacon's site a lot and use it often: http://git-scm.com/
* Compare #1 and #2 1) http://git-scm.com 2) http://git.or.cz
* http://git.or.cz and http://git-scm.com should be merged
* http://git-scm.com/ is a worderfull project, making the homepage
look and feel much better and "user friendly". The source code is at
http://github.com/schacon/gitscm. What about using this as the Git
official homepage (not the domain, but the interface and images).
* git-scm.com should be the official page :)
* Organization and flow particularly for new users. I think Scott
Chacon's git-scm.com site does a much better job. Organization and
navigation of the content are the things that make it a winner.
* The www.git-scm.com homepage is great.
* Which one? http://git.or.cz/ or http://git-scm.com/ I tend to use
git-scm.com just because it looks nicer, is written in Rails and has
more user friendly information. Rather than browsing what feels like
"A manual online" that is git.or.cz
* I think the homepage (http://git-scm.com/) however work should be
done to have that come ahead of http://git.or.cz/ which currently tops
all the queries. I would try to strike a deal with that domain to
http-redirect to the new url. I can only imagine that this duplication
leads to confusion and a bad experience.
* It should look more like http://git-scm.com
* http://git-scm.com/ > git.or.cz -scm has all the info I might want
up front in one page, while my eyes gloss over just looking at or.cz.
Cheers,
PJ Hyett
http://github.com/pjhyett
1. http://www.survs.com/app/4/wo/IQ2m9AwQ2qFAVwuZrRLF4w/0.0.9.3.3.0.1.3.42.1.7.1
next parent reply other threads:[~2008-10-15 10:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bab6a2ab0810150315l273d4ef3k95cda8f43a4745ca@mail.gmail.com>
2008-10-15 10:18 ` PJ Hyett [this message]
2008-10-15 10:34 ` git-scm.com (was Re: Git graph on GitHub) Wincent Colaiuta
2008-10-15 16:21 ` Scott Chacon
2008-10-15 17:25 ` Petr Baudis
2008-10-16 9:42 ` git-scm.com Nanako Shiraishi
2008-10-16 9:49 ` git-scm.com Petr Baudis
2008-10-17 1:57 ` git-scm.com Junio C Hamano
2008-10-15 18:36 ` git-scm.com (was Re: Git graph on GitHub) PJ Hyett
2008-10-15 19:02 ` Jonathan del Strother
2008-10-15 19:20 ` Jakub Narebski
2008-10-15 19:26 ` git-scm.com Teemu Likonen
2008-10-15 20:12 ` git-scm.com (was Re: Git graph on GitHub) Garry Dolley
2008-10-15 21:04 ` Aaron Cohen
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=bab6a2ab0810150318pb616a6dj867efa36623ac12e@mail.gmail.com \
--to=pjhyett@gmail.com \
--cc=git@vger.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.
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).