From: Maxime Devos <maximedevos@telenet.be>
To: Andreas Enge <andreas@enge.fr>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: v2: A proposal of a consistent set of clear rules and guidelines involving snippets, phases and patches.
Date: Tue, 9 Aug 2022 17:06:43 +0200 [thread overview]
Message-ID: <c5b22f52-b675-6c6c-cfaf-2bcbaddcc25e@telenet.be> (raw)
In-Reply-To: <YvGFS8SF13ppuDWL@jurong>
[-- Attachment #1.1.1: Type: text/plain, Size: 1797 bytes --]
On 08-08-2022 23:51, Andreas Enge wrote:
> Hello,
>
> Am Fri, Aug 05, 2022 at 03:59:14PM +0200 schrieb Maxime Devos:
>> Here's a v2. I've changed the structure to something close to what Julien
>> proposed, it looks a lot better now to me!
> thanks, it does! I still find it a bit too verbose compared to Liliana's
> suggestion, which I would prefer as a starting point of the discussion.
WDYM with 'still' here? The v2 patch I sent preceded Liliana's patch.
I'm not seeing a 'too verbose'-ity or a difference in verbosity myself
---
Something I liked about Julien's proposed structure is:
> [...] derive rules for specific cases, based on these principles:
>
> How do I remove non-free software? -> snippet because …
>
> How do I remove bundled libraries? -> snippet or phase because …
>
> How do I fix a build issue? -> patch or snippet if this affects
> building from source, can also be a phase if the result of --sources
> can still build
>
> A test issue?
>
> …
>
> This leaves some cases up to interpretation, but that's probably not
> so different from "it's not an absolute rule". It's also much clearer
> and quicker to figure out in which case you are. If not documented as
> a case, you can fall back to the general principles.
-- i.e., if I want to do $FOO, I could quickly find out how to do it.
In the v2 I sent, this was reflected in the subsections, each subsection
is a 'howto $FOO'. Whereas the patch Liliana sent is kind of the inverse
-- each @item corresponds to a 'what can the method $FOO be used for'.
Similarly, in the v1 I sent, I followed a similar structure (an item for
patches, an item for snippets, an item for phases).
As such, the v2 I sent seems a better basis to me.
Greetings,
Maxime.
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 929 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]
next prev parent reply other threads:[~2022-08-09 15:07 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-25 3:17 A proposal of a consistent set of clear rules and guidelines involving snippets, phases and patches Maxime Devos
2022-07-25 5:21 ` Julien Lepiller
2022-07-25 11:18 ` Maxime Devos
2022-07-25 11:37 ` Julien Lepiller
2022-08-04 8:51 ` Ludovic Courtès
2022-08-05 3:23 ` Philip McGrath
2022-08-05 8:13 ` Maxime Devos
2022-08-05 3:38 ` Philip McGrath
2022-08-05 8:09 ` Maxime Devos
2022-08-05 10:18 ` Maxime Devos
2022-08-05 13:59 ` v2: " Maxime Devos
2022-08-06 6:55 ` [PATCH] doc: Update contribution guidelines on patches, etc Liliana Marie Prikler
2022-08-06 6:55 ` [PATCH v2] " Liliana Marie Prikler
2022-09-02 13:12 ` Ludovic Courtès
2022-09-02 18:05 ` Maxime Devos
2022-09-05 9:47 ` Ludovic Courtès
2022-09-05 13:12 ` Maxime Devos
2022-09-05 16:05 ` Maxime Devos
2022-08-09 16:45 ` [PATCH] " Maxime Devos
2022-08-09 17:05 ` Liliana Marie Prikler
2022-08-09 18:19 ` Maxime Devos
2022-08-09 19:08 ` Liliana Marie Prikler
2022-08-09 20:30 ` Maxime Devos
2022-08-10 4:25 ` Liliana Marie Prikler
2022-08-09 20:40 ` Maxime Devos
2022-08-08 21:51 ` v2: A proposal of a consistent set of clear rules and guidelines involving snippets, phases and patches Andreas Enge
2022-08-09 15:06 ` Maxime Devos [this message]
2022-08-09 17:10 ` Andreas Enge
2022-09-05 13:03 ` Maxime Devos
2022-09-07 12:17 ` Andreas Enge
2022-09-07 18:08 ` Maxime Devos
2022-08-09 18:58 ` david larsson
2022-08-09 20:53 ` Maxime Devos
2022-08-10 11:23 ` david larsson
2022-08-05 16:59 ` blake
2022-08-09 16:30 ` Maxime Devos
2022-09-05 14:06 ` Maxime Devos
2022-08-10 6:10 ` blake
2022-08-10 9:06 ` Maxime Devos
2022-08-10 10:33 ` blake
2022-08-10 10:44 ` Maxime Devos
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=c5b22f52-b675-6c6c-cfaf-2bcbaddcc25e@telenet.be \
--to=maximedevos@telenet.be \
--cc=andreas@enge.fr \
--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).