unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: "Artyom V. Poptsov" <poptsov.artyom@gmail.com>
To: 74736@debbugs.gnu.org
Subject: [bug#74736] [PATCH v2 0/1] Add Request-For-Comment process.
Date: Mon, 09 Dec 2024 23:47:18 +0300	[thread overview]
Message-ID: <87h67c60tl.fsf@gmail.com> (raw)
In-Reply-To: <cover.1733614983.git.noelopez@free.fr>

[-- Attachment #1: Type: text/plain, Size: 1142 bytes --]

Hello Noé Lopez,

thanks for pushing this idea forward!  I think that the RFC process will
help to track all the major initiatives in GNU Guix -- present and
future ones.

I know that there are several long-term big projects inside Guix, namely
Guile daemon, distributed substitutes and maybe more.  In my view the
problem is that the information about those projects is buried in the
Git branches and E-Mail discussions.  Maybe RFCs in the well-known place
inside the repository will help developers to see what the community at
large is up to.

> # Ludovic Courtès:
> # I’d go for one format, preferably Markdown because we have a library to
> # parse it.

To my taste, as for Emacs user, the plain old org-mode format is good
enough to write RFCs, but that's no more than a preference.  Many people
using Markdown nowadays so maybe it will help to make the RFC process
more friendly for newcomers.

- avp

-- 
Artyom "avp" Poptsov <poptsov.artyom@gmail.com>
Home page: https://memory-heap.org/~avp/
CADR Hackerspace co-founder: https://cadrspace.ru/
GPG: D0C2 EAC1 3310 822D 98DE  B57C E9C5 A2D9 0898 A02F

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 869 bytes --]

      parent reply	other threads:[~2024-12-09 20:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-08 12:29 [bug#74736] [PATCH v2 0/1] Add Request-For-Comment process Noé Lopez via Guix-patches via
2024-12-08 12:31 ` [bug#74736] [PATCH v2 1/1] rfc: " Noé Lopez via Guix-patches via
2024-12-09 20:47 ` Artyom V. Poptsov [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=87h67c60tl.fsf@gmail.com \
    --to=poptsov.artyom@gmail.com \
    --cc=74736@debbugs.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).