From: Simon Tournier <zimon.toutoune@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Matthew Trzcinski <matt@excalamus.com>,
72839@debbugs.gnu.org,
Maxim Cournoyer <maxim.cournoyer@gmail.com>,
72840@debbugs.gnu.org, Florian Pelz <pelzflorian@pelzflorian.de>
Subject: [bug#72839] bug#72840: [PATCH RFC] DRAFT doc: Add “Deprecation Policy” section.
Date: Fri, 13 Sep 2024 20:11:35 +0200 [thread overview]
Message-ID: <CAJ3okZ2xyRedDzPucqBKzBbFGcN3pJFu1aaz6C2C2Dh3r=BDSQ@mail.gmail.com> (raw)
In-Reply-To: <87zfobe9on.fsf_-_@gnu.org>
Hi Ludo,
On Fri, 13 Sept 2024 at 19:38, Ludovic Courtès <ludo@gnu.org> wrote:
> That’s a question for you no?
Yes and no. :-)
Yes because I sent the first draft, so it's partly my duty.
No because changes and especially collective practices are not only on
the shoulders of one. Is the motivation, time or energy of only one
person the bottleneck of a common willing?
Anyway.
> I already commented on the proposed RFC process. I’m happy to further
> contribute or even take the lead eventually when time permits, if you’d
> like to pass it on. It’s clearly the missing piece here. We’ll get
> there!
It is a good example why Co-Supporter(s) as described by the RFC
process is a strong requirement. ;-) And there is none...
Anyway, I will do my best for resuming.
Cheers,
simon
next prev parent reply other threads:[~2024-09-13 18:14 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-27 19:13 [bug#72839] [PATCH RFC] DRAFT doc: Add “Deprecation Policy” section Ludovic Courtès
2024-09-02 11:53 ` [bug#72840] " pelzflorian (Florian Pelz)
2024-09-05 21:26 ` bug#72840: " Ludovic Courtès
2024-09-05 21:31 ` [bug#72840] [PATCH RFC v2] " Ludovic Courtès
2024-09-11 7:04 ` Maxim Cournoyer
2024-09-11 10:11 ` [bug#72840] [PATCH RFC v3] " Ludovic Courtès
2024-09-12 0:40 ` Maxim Cournoyer
2024-09-11 10:11 ` [bug#72840] [PATCH RFC] DRAFT " Ludovic Courtès
2024-09-11 18:30 ` Noé Lopez via Guix-patches via
2024-09-13 17:23 ` Ludovic Courtès
2024-09-11 19:49 ` [bug#72840] Deprecation policy Konrad Hinsen
2024-09-13 17:32 ` [bug#72840] [PATCH RFC] DRAFT doc: Add “Deprecation Policy” section Ludovic Courtès
2024-09-15 8:22 ` Konrad Hinsen
[not found] ` <66e1e26e.050a0220.2c8e9.9533SMTPIN_ADDED_BROKEN@mx.google.com>
2024-09-12 15:39 ` Greg Hogan
2024-09-13 16:41 ` [bug#72839] Using RFC process? (was Re: [bug#72839] [PATCH RFC] DRAFT doc: Add “Deprecation Policy” section.) Simon Tournier
2024-09-13 17:38 ` [bug#72840] [PATCH RFC] DRAFT doc: Add “Deprecation Policy” section Ludovic Courtès
2024-09-13 18:11 ` Simon Tournier [this message]
2024-09-13 20:57 ` indieterminacy
2024-09-17 12:21 ` [bug#72840] Orphaned packages Konrad Hinsen
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='CAJ3okZ2xyRedDzPucqBKzBbFGcN3pJFu1aaz6C2C2Dh3r=BDSQ@mail.gmail.com' \
--to=zimon.toutoune@gmail.com \
--cc=72839@debbugs.gnu.org \
--cc=72840@debbugs.gnu.org \
--cc=ludo@gnu.org \
--cc=matt@excalamus.com \
--cc=maxim.cournoyer@gmail.com \
--cc=pelzflorian@pelzflorian.de \
/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.