all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: bokr@bokr.com
To: Simon Tournier <zimon.toutoune@gmail.com>
Cc: "Ludovic Courtès" <ludo@gnu.org>,
	"Guix Devel" <guix-devel@gnu.org>,
	"Efraim Flashner" <efraim@flashner.co.il>,
	"Ricardo Wurmus" <rekado@elephly.net>,
	"Christopher Baines" <mail@cbaines.net>,
	"GNU Guix maintainers" <guix-maintainers@gnu.org>
Subject: Re: Guix Common Document process (v7) (was: Request-For-Comment, RFC)
Date: Tue, 14 Jan 2025 10:28:59 -0800	[thread overview]
Message-ID: <Z4as66vcQeOlI14k@BRL14v1> (raw)
In-Reply-To: <87bjwfh6p8.fsf@gmail.com>

Hi Simon, and anyone interested,

Synopsis:
    1)	SFTN: apologies for mistakenly introducing offtopic tangentials in earlier post ;-/
    2)	IWBN: if links/urls in the GCD document had base names for wget automatic file naming.
    3)	IWBN: if there were a guile-glossary.html AND a guix-glossary.html AND
    4)	IWBN: if the GCD html document had hover-hints with glossary excerpts and links thereto.
    5)	IWBN: if importantly exact references had sha256sum hashes as, or embedded in, the basenames.
    6)	IWBN: to provide links for bewildered visitors to explanatory documentation, e.g. [1]-[6]
    7)	SFTN:= Sorry For The Noise, IWBN:= It Would Be Nice, GCD:= Guix Common Document

[1] https://guix.gnu.org/manual/devel/
[2] https://guix.gnu.org/manual/en/html_node
[3] https://guix.gnu.org/manual/en/html_node/Concept-Index.html
[4] https://www.gnu.org/software/guile/manual/
[5] https://www.gnu.org/software/guile/manual/html_node/index.html
[6] https://www.gnu.org/software/guile/manual/html_node/Concept-Index.html

I like glossaries (4), but [3] and [6] are excellent, and provide more info -- but not
glossary definitions. Quick, What's a thread?  A fiber? A continuation? Wayland protocol?

BTW, I think IWBN to rename the Concept-Index.html files with Guile- or Guix- prefixes
in case someone wgets them :) People can use [1] and [4] to download different formats, and
e.g. get a single file html, which is nice for Ctl-f searching, as Simon has pointed out.
The html_node ones may lessen waits where bandwidth is low/expensive.

Might mention that the guix cookbook (updated?) might be viewable something like:
    info -f <repo-dir>/guix/doc/guix-cookbook.texi
for those who have cloned the guix repo.

Well, I'll leave it at that. Thanks for reading :)

Cheers,
--
Bengt Richter

On +2025-01-10 01:07:47 +0100, Simon Tournier wrote:
> Hi all,
> 
> On Tue, 07 Jan 2025 at 11:40, Ludovic Courtès <ludo@gnu.org> wrote:
> 
> >> The submission is: <https://issues.guix.gnu.org/74736#22>.
> >
> > And now v6! https://issues.guix.gnu.org/74736#27
> 
> See v7: https://issues.guix.gnu.org/74736#44
> 
> > Even better if we can finalize before Guix Days so:
> >
> >   discussion period ending on Jan. 14th
> >   deliberation period ending on Jan. 28th
> >
> > How does that sound?
> 
> It sounds good to me.
> 
> Please make your voice heard.  Especially if the document appears to you
> unclear.  All voice counts!  Your voice is important if you feel part of
> the Guix community; don’t be shy. :-)
> 
> Cheers,
> simon
> 


  parent reply	other threads:[~2025-01-14 18:30 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-31 11:14 Request-For-Comment process: concrete implementation Simon Tournier
2023-11-16 15:03 ` Ludovic Courtès
2023-11-20  9:42   ` Simon Tournier
2023-11-22 18:17     ` Ludovic Courtès
2023-11-23  7:04 ` Efraim Flashner
2023-11-28 13:34   ` Simon Tournier
2023-12-19 12:33 ` Simon Tournier
2023-12-20 11:49   ` Ricardo Wurmus
2024-02-03 10:09     ` Simon Tournier
2024-02-03 10:34 ` [post Guix Days] Guix Common Document (was: Request-For-Comment process) Simon Tournier
2024-02-07  8:27   ` Efraim Flashner
2025-01-03 18:38 ` Request-For-Comment process: concrete implementation (v5) Simon Tournier
2025-01-07 10:40   ` Ludovic Courtès
2025-01-08 15:15     ` Suhail Singh
2025-01-09 17:33     ` Simon Tournier
2025-01-09 23:49       ` bokr
2025-01-10  6:26       ` Suhail Singh
2025-01-15 18:42         ` Simon Tournier
2025-01-10  0:07     ` Guix Common Document process (v7) (was: Request-For-Comment, RFC) Simon Tournier
2025-01-12 15:11       ` Arun Isaac
2025-01-15 15:34         ` Andreas Enge
2025-01-15 21:50           ` Guix Common Document process (v7) indieterminacy
2025-01-15 22:32           ` Guix Common Document process (v7) (was: Request-For-Comment, RFC) Simon Tournier
2025-01-15 22:32             ` [bug#74736] " Simon Tournier
2025-01-15 23:28             ` Vagrant Cascadian
2025-01-16  9:23               ` [bug#74736] " Andreas Enge
2025-01-16 12:04             ` Guix Common Document process (v7) Suhail Singh
2025-01-16 16:10           ` bug#74736: [PATCH v2 0/1] Add Request-For-Comment process Ludovic Courtès
2025-01-16 18:01             ` Simon Tournier
2025-01-17  9:37               ` Ludovic Courtès
2025-01-15 19:18         ` Guix Common Document process (v7) (was: Request-For-Comment, RFC) Simon Tournier
2025-01-16 13:21           ` Arun Isaac
2025-01-14 18:28       ` bokr [this message]
2025-01-15 19:22         ` Simon Tournier
2025-01-17  1:06 ` Guix Consensus Document process (v10) Simon Tournier
2025-01-19 21:52   ` Ludovic Courtès

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=Z4as66vcQeOlI14k@BRL14v1 \
    --to=bokr@bokr.com \
    --cc=efraim@flashner.co.il \
    --cc=guix-devel@gnu.org \
    --cc=guix-maintainers@gnu.org \
    --cc=ludo@gnu.org \
    --cc=mail@cbaines.net \
    --cc=rekado@elephly.net \
    --cc=zimon.toutoune@gmail.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.
Code repositories for project(s) associated with this external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.