Re: Rewriting the Git tutorial to cover less content

"Julia Evans" [off-list ref] writes:

I'm working on a patch series to replace `gittutorial.adoc` with a completely
rewritten tutorial, since a lot has changed since it was originally written.
...
I'm excited about this direction, I've already gotten some positive feedback from
test readers, like:

quoted

I can say I liked this tutorial better than any of the other git tutorials I've tried.

and

quoted

I really like the tutorial, it's easy to follow and I learned a lot!

I have some ideas for what to do with `gittutorial-2` too but I'll leave
that for another discussion.

As long as it does not mean that learners now have to read three
documents instead of two (i.e., your replacement, gittutorial.adoc,
and gittutorial-2.adoc), I am also excited.

Omitting some material that is covered in the current tutorial from
the new one would mean that the topics covered by the remainder of
the current tutorial have to be sifted into three buckets: one that
is to be discarded because it is no longer useful to the target
audience, another that needs to be described somewhere in our
documentation set, and the rest that need to be taught elsewhere,
though that may be beyond the scope of the project documentation
and better left to other projects that produce "books on Git".  It
is somewhat unclear from your description what your plan is to cover
other topics that should still be taught.

As we reached consensus at the contributors' summit, we should wean
ourselves away from the mindset that these tutorial materials can be
incrementally polished to match today's needs, so if the plan for
'the rest' is also to write on these topics from the ground up, that
would be very good.

Thanks.