From: Luis Felipe <luis.felipe.la@protonmail.com>
To: Leo Famulari <leo@famulari.name>
Cc: "Léo Le Bouter" <lle-bout@zaclys.net>,
guix-devel <guix-devel@gnu.org>,
"Vincent Legoll" <vincent.legoll@gmail.com>
Subject: Re: Document our WIP
Date: Thu, 01 Apr 2021 21:33:20 +0000 [thread overview]
Message-ID: <N4_U7bDY10Dp5lDrVVvxlWq6mXTt3ninqPt55Dn1ifDspPDhymvevow2CHgU8B02rx_Zq9JEy0ib4i18IkjIJSiHvMl98e45i2eqZyjY_p0=@protonmail.com> (raw)
In-Reply-To: <YGS8dVXwqoqyL2+O@jasmine.lan>
Hi,
On Wednesday, March 31, 2021 6:16 PM, Leo Famulari <leo@famulari.name> wrote:
> 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.
I just sent a patch to include a link to the wiki in the Help page (https://issues.guix.gnu.org/47555).
If the patch is applied, I can send a separate patch to update the Help menu as Vincent suggested:
Help
• GNU Guix Manual
• Videos
• Cookbook
• GNU Manuals
• Wiki
• IRC Chat
• Mailing lists
If people think it's ok.
next prev parent reply other threads:[~2021-04-01 21:34 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
2021-04-01 21:33 ` Luis Felipe [this message]
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
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='N4_U7bDY10Dp5lDrVVvxlWq6mXTt3ninqPt55Dn1ifDspPDhymvevow2CHgU8B02rx_Zq9JEy0ib4i18IkjIJSiHvMl98e45i2eqZyjY_p0=@protonmail.com' \
--to=luis.felipe.la@protonmail.com \
--cc=guix-devel@gnu.org \
--cc=leo@famulari.name \
--cc=lle-bout@zaclys.net \
--cc=vincent.legoll@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 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).