patches and low-level development discussion
 help / color / mirror / code / Atom feed
From: "Jenni Nikolaenko" <evgeniia.nikolaenko@unikie.com>
To: devel@spectrum-os.org
Subject: Re: [PATCH v3] Docs: new structure
Date: Tue, 08 Nov 2022 15:02:33 -0000	[thread overview]
Message-ID: <166791975371.1913.15771765595007963227@atuin.qyliss.net> (raw)
In-Reply-To: <20221108090439.gi57cr6igmcaoxkc@x220>

> > There's still a change from double spaced to single spaced here.  I
> > think it's the last one, but it might be a good idea to have a look
> > through the diff to make sure that there aren't any more.
Fixed. It is better to put one sentence on each line. This makes it easy to move content around, and also easy to spot (too) long sentences. Also, this recommendation here https://asciidoctor.org/docs/asciidoc-recommended-practices/#one-sentence-per-line 

> > I think "Packages" here should be lowercase.
Here it is written so as it is used in the official documentation https://nixos.org/ 

> > I think this page could use some more work to figure out what exactly we
> > want to say here.  Could we go with something similar to the smaller
> > development/index.adoc page from the previous version of your patch?
> > I don't want all your other great changes to be held up while we discuss
> > a big new chunk of prose like this, so I'd really rather it was kept for
> > a future, self-contained patch.
Ok, sure, let’s do this as a separate change (patch).
I added this general description as my colleagues asked me. Actually, they did not ask to add such a section, but they usually ask about the flow so I decided to describe it once. It helps a lot if guys are not familiar with the process or if it is a new team member.

> > This change just unwraps the line, unless I'm missing something?
This is the same section in which I had some problems with example attributes :D (long-suffering page)
So, I just opened the source code of the current page and made everything by analogy. Actually, there are no changes here.

> > Typo in the file name: "patces"
Fixed! Т_Т

> > I'm not sure this is necessary before starting — it's helpful for
> > applying and testing other people's patches, but somebody who just
> > wants to submit their own work doesn't need b4.
Fixed: Make sure to install and configure the b4 utility for applying and testing other people's patches.



      reply	other threads:[~2022-11-08 15:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-04 13:44 [PATCH v3] Docs: new structure Jenni Nikolaenko
2022-11-04 13:58 ` Jenni Nikolaenko
2022-11-08  9:04 ` Alyssa Ross
2022-11-08 15:02   ` Jenni Nikolaenko [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=166791975371.1913.15771765595007963227@atuin.qyliss.net \
    --to=evgeniia.nikolaenko@unikie.com \
    --cc=devel@spectrum-os.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://spectrum-os.org/git/crosvm
	https://spectrum-os.org/git/doc
	https://spectrum-os.org/git/mktuntap
	https://spectrum-os.org/git/nixpkgs
	https://spectrum-os.org/git/spectrum
	https://spectrum-os.org/git/ucspi-vsock
	https://spectrum-os.org/git/www

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).