From: "Richard Hartmann" <richih.mailinglist@gmail.com>
To: "Jeff King" <peff@peff.net>
Cc: git@vger.kernel.org
Subject: Re: Feedback outside of the user survey
Date: Thu, 16 Oct 2008 13:08:06 +0200 [thread overview]
Message-ID: <2d460de70810160408x784a657fte418d41dd6a06d7f@mail.gmail.com> (raw)
In-Reply-To: <20081016102835.GC20762@sigill.intra.peff.net>
On Thu, Oct 16, 2008 at 12:28, Jeff King <peff@peff.net> wrote:
> Is there something about these that doesn't meet your criteria? Or did
> you not know about them (in which case, maybe we need to be more
> prominently pointing to them)?
In best slapstick fashion, I found the pages you mentioned in 1) and 3)
after sending off my email. Maybe they did not exist back when I last
looked, maybe they are easier to find now, maybe I was too stupid to
look, back then.
In any case, those two fit my needs nicely. In fact, I would have said
as much on this list if I had not become stuck in reading said docs :)
As to the resource you mention in 2), it is nice, but it does not fit
exactly to what I had in mind. You have a lot of snippets and single
steps, which is fine. What I was imagining was more like a use case
& workflow-driven layout.
A basic or complex task could give a short overview of steps, all of
which would be hyperlinked to detailed explanations. As a lot (more)
documentation seems to exist since I last gave git a serious try,
this is probably mainly a work of coming up with workflows and
linking to the correct places, not so much of writing any actual new
text.
And yes, I think the fact that these newbie-friendly docs exist these
days should be pushed more agressively. As you can see from the
links in my initial mail, a _lot_ of people have the same
misinformation I used to have. That will mainly be due to old
knowledge, but the situation exists. Worse, those people will warn
others about the lack of starter-level docs, making more people
shun git for all the wrong reasons.
An easy step in this direction might be to _prominently_ display
direct links to the newbie docs on the entry points, for most users.
I.e. the main site [1] and the wiki [2] along with the FAQ. I would
edit the wiki myself, but I could not find
MoinMaster:MoinPagesEditorGroup nor MoinMaster anywhere
in said wiki, thus decided to heed the warning & not edit at all.
Richard
[1] http://git.or.cz/
[2] http://git.or.cz/gitwiki
next prev parent reply other threads:[~2008-10-16 11:09 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-16 10:19 Feedback outside of the user survey Richard Hartmann
2008-10-16 10:28 ` Jeff King
2008-10-16 11:08 ` Richard Hartmann [this message]
2008-10-16 11:56 ` Garry Dolley
2008-10-16 13:18 ` Richard Hartmann
2008-10-16 20:32 ` Christian Jaeger
2008-10-18 13:49 ` Garry Dolley
2008-10-18 14:01 ` Christian Jaeger
2008-10-20 9:57 ` Andreas Ericsson
2008-10-20 14:43 ` Christian Jaeger
2008-10-20 15:02 ` Andreas Ericsson
2008-10-20 15:20 ` Christian Jaeger
2008-10-20 16:11 ` Andreas Ericsson
2008-10-20 16:57 ` Christian Jaeger
2008-10-20 17:30 ` Christian Jaeger
2008-10-20 22:41 ` Junio C Hamano
2008-10-21 7:24 ` Christian Jaeger
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=2d460de70810160408x784a657fte418d41dd6a06d7f@mail.gmail.com \
--to=richih.mailinglist@gmail.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
/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).