unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Alex Sassmannshausen <alex.sassmannshausen@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: dmd: Some improvements to the dmd manual
Date: Fri, 24 Jan 2014 13:52:28 +0100	[thread overview]
Message-ID: <87ppnhk0dv.fsf@gnu.org> (raw)
In-Reply-To: <8761pau43v.fsf@gmail.com> (Alex Sassmannshausen's message of "Thu, 23 Jan 2014 16:09:40 +0100")

Hello Alex,

Alex Sassmannshausen <alex.sassmannshausen@gmail.com> skribis:

> Ludovic Courtès writes:
>
>>> Let me know if you think I should ba approaching this differently.
>>
>> I will comment on the first patch, but what specific points do you want
>> to address more generally?  Is it more about wording, structure, guiding
>> the user?  (I can see some of that in the first patch.)
>
> It started of being about correcting typos and improving the wording a
> bit, but then it became about enhancing the journey of the reader a bit:
> make things friendlier where appropriate, keep things simpler,
> especially prior to chapter 2, etc.

Sounds good!

> The manual that keeps coming back to me is the Geiser manual: it's
> written in a lovely way and I'd like to introduce some of its style
> whilst maintaining clarity and newbie-friendliness.

That’s a good benchmark.  :-)

> So, fixing typos and wording probably doesn't require large changes,
> guiding the user probably would imply some re-writing.
>
> I could split the job in two: always submit one patch fixing typos and
> wording, and then, if necessary, a rewritten section afterwards? (this
> might be slightly more work for me, but as there is no deadline that's
> fine :-).

I think splitting into two parts here would be annoying for you, and not
very fruitful if large parts are going to be rewritten anyway.  So
submit in whatever form is the most appropriate for you: split by
section when that’s possible, and otherwise whatever you think makes a
consistent change set.

> I like the style of the manual overall anyway, so I'm definitely
> approaching this with respect to what has been done already.
>
> Hope this clarifies my intentions a little

It does, and I like the ideas.  Thank you!

Ludo’.

      reply	other threads:[~2014-01-24 12:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-23  8:15 dmd: Some improvements to the dmd manual Alex Sassmannshausen
2014-01-23  8:15 ` [PATCH] Doc: Introduction: rewrite for style and clarity Alex Sassmannshausen
2014-01-23 13:30   ` Ludovic Courtès
2014-01-23 18:00     ` (unknown), Alex Sassmannshausen
2014-01-23 18:00       ` [PATCH] Doc: Introduction: rewrite for style and clarity Alex Sassmannshausen
2014-01-24 17:11         ` Ludovic Courtès
2014-01-23 13:11 ` dmd: Some improvements to the dmd manual Ludovic Courtès
2014-01-23 15:09   ` Alex Sassmannshausen
2014-01-24 12:52     ` Ludovic Courtès [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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87ppnhk0dv.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=alex.sassmannshausen@gmail.com \
    --cc=guix-devel@gnu.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).