From: Leo Famulari <leo@famulari.name>
To: "Léo Le Bouter" <lle-bout@zaclys.net>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Document our WIP
Date: Wed, 31 Mar 2021 14:16:21 -0400 [thread overview]
Message-ID: <YGS8dVXwqoqyL2+O@jasmine.lan> (raw)
In-Reply-To: <717cf0d663b9323bb6435891e6937a05bb495f5e.camel@zaclys.net>
[-- Attachment #1: Type: text/plain, Size: 1365 bytes --]
On Wed, Mar 31, 2021 at 07:52:30PM +0200, Léo Le Bouter wrote:
> On Tue, 2021-03-30 at 12:37 +0200, Ludovic Courtès wrote:
> > To me, a good way to make sure work remains “in progress” is to post
> > regular updates to this list, and then to write blog posts for the
> > web
> > site whenever an important milestone is reached.
> >
> > I think a web page is likely to quickly become outdated… unless said
> > work transitions from “in progress” to “stalled”. :-)
>
> I feel like using the mailing list fails at solving one concern that is
> discoverability of WIP problems for people to show up and help tackle
> them, even if they were abandonned by the people who started them. Not
> everyone can handle the load of incoming mail in the ML. On the GNOME
> 40 upgrade for example I linked the mailing list thread on the wiki
> page also. The wiki page is also more likely to get outdated if it
> doesnt have great visibility on the GNU Guix official website, that,
> for sure.
Yeah, I agree that it's hard to learn about "what's cooking" when you
first arrive at the mailing lists.
It's true that wikis tend to get out of date, but I think that it won't
be too bad for this use case. At least, it won't be worse than the
mailing lists, for newcomers who want to know about longer-term efforts
like the GNOME upgrade.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2021-03-31 18:16 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-27 10:07 Document our WIP Vincent Legoll
2021-03-27 14:20 ` Léo Le Bouter
2021-03-27 14:44 ` Ricardo Wurmus
2021-03-27 15:32 ` Joshua Branson
2021-03-27 15:34 ` Léo Le Bouter
2021-03-27 15:44 ` Luis Felipe
2021-03-27 15:54 ` Léo Le Bouter
2021-03-27 15:41 ` Vincent Legoll
2021-03-27 15:50 ` Vincent Legoll
2021-03-27 15:54 ` Luis Felipe
2021-03-27 16:03 ` Vincent Legoll
2021-03-27 16:04 ` Léo Le Bouter
2021-03-27 16:42 ` Luis Felipe
2021-03-27 16:50 ` Léo Le Bouter
2021-03-27 17:02 ` Luis Felipe
2021-03-27 17:05 ` Vincent Legoll
2021-03-27 18:12 ` Vincent Legoll
2021-03-27 18:18 ` Luis Felipe
2021-03-28 15:33 ` Vincent Legoll
2021-03-27 17:02 ` Vincent Legoll
2021-03-27 18:11 ` Luis Felipe
2021-03-27 18:13 ` Vincent Legoll
2021-03-27 16:01 ` Léo Le Bouter
2021-03-30 10:37 ` Ludovic Courtès
2021-03-31 17:52 ` Léo Le Bouter
2021-03-31 18:16 ` Leo Famulari [this message]
2021-04-01 21:33 ` Luis Felipe
2021-04-02 16:11 ` Léo Le Bouter
2021-04-08 19:55 ` Luis Felipe
2021-04-08 21:06 ` Vincent Legoll
2021-04-02 4:42 ` Gurjeet Singh
2021-04-05 23:35 ` Léo Le Bouter
2021-04-07 15:55 ` Vincent Legoll
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=YGS8dVXwqoqyL2+O@jasmine.lan \
--to=leo@famulari.name \
--cc=guix-devel@gnu.org \
--cc=lle-bout@zaclys.net \
/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.