Git development
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Toon Claes <toon@iotcl.com>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>,  git@vger.kernel.org
Subject: Re: Git Contributor' summit: Documentation,
Date: Wed, 23 Sep 2026 08:15:02 -0700	[thread overview]
Message-ID: <xmqqbj9oc83t.fsf@gitster.g> (raw)
In-Reply-To: <871pak1151.fsf@emacs.iotcl.com> (Toon Claes's message of "Wed, 23 Sep 2026 16:40:58 +0200")

Toon Claes <toon@iotcl.com> writes:

> I've expressed myself multiple times as well how excited I am to have
> Julia working on this, but it cannot be expressed enough.

;-)

>> list, ever. I just hope that old-timers who really do not need the
>> documentation nor understand the need of those who do need it show
>> enough appreciation for the fresh views and for Julia's understanding
>> of the target audience.)
>
> I think the old-timers do, but it takes skills to have a very deep
> understanding and still being able to explain things to newbies.

Not just these two skills, but you need to know what are the points
new people find hard to get when they are starting, and that is the
weakest spot for our old-timers.

>> There was support for replacing outdated material and for merging useful
>> improvements, then iterating, rather than trying to perfect everything
>> before it lands. Bringing user feedback to the list without flooding it
>> remains a challenge.
>
> Iteration will be key here, and I would say some steps have been taken
> already. Very tiny steps though.

IIRC, the view in the room was in favor of keeping and incrementally
improving the manual pages and reference material while rewriting
tutorials and material on concepts from scratch.  I very much agree
with the "rewrite from scratch" part, because the concepts have
evolved and the world view have been updated even if the concepts at
the very core of the system may have not changed.

      reply	other threads:[~2026-09-23 15:15 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-22  0:11 What's cooking in git.git (Sep 2026, #08) Junio C Hamano
2026-09-22  8:11 ` kh/format-patch-range-diff-notes Kristoffer Haugsbakk
2026-09-22 13:25 ` Git v3.0 timeline, was Re: What's cooking in git.git (Sep 2026, #08) Johannes Schindelin
2026-09-22 13:49   ` Junio C Hamano
2026-09-22 17:06     ` Johannes Schindelin
2026-09-24  3:56       ` Junio C Hamano
2026-09-24  4:30         ` Junio C Hamano
2026-09-24 12:29           ` Johannes Schindelin
2026-09-24 17:00             ` Junio C Hamano
2026-09-24 18:08           ` Ramsay Jones
2026-09-22 18:44     ` My summary of the Git Contributors' Summit 2026, was " Johannes Schindelin
2026-09-23 11:55       ` Daniele Sassoli
2026-09-24 12:31         ` Johannes Schindelin
2026-09-25  9:53         ` Luca Milanesio
2026-09-23 12:52       ` D. Ben Knoble
2026-09-23 14:22       ` Security mailing list & process, was Re: My summary of the Git Contributors' Summit 2026 Toon Claes
2026-09-24 12:38         ` Johannes Schindelin
2026-09-23 14:40       ` Git Contributor' summit: Documentation, was: Re: My summary of the Git Contributors' Summit 2026, was Re: Git v3.0 timeline, was Re: What's cooking in git.git (Sep 2026, #08) Toon Claes
2026-09-23 15:15         ` Junio C Hamano [this message]

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=xmqqbj9oc83t.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=toon@iotcl.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