all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Léo Le Bouter" <lle-bout@zaclys.net>
To: Leo Famulari <leo@famulari.name>
Cc: "Ludovic Courtès" <ludo@gnu.org>,
	"Vincent Legoll" <vincent.legoll@gmail.com>,
	guix-devel <guix-devel@gnu.org>
Subject: Re: Document our WIP
Date: Tue, 06 Apr 2021 01:35:17 +0200	[thread overview]
Message-ID: <ee19cace7f29560847eaf3635ba4dd7150094bf4.camel@zaclys.net> (raw)
In-Reply-To: <YGS8dVXwqoqyL2+O@jasmine.lan>

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

On Wed, 2021-03-31 at 14:16 -0400, Leo Famulari wrote:
> 
> 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 am thinking we could establish policy so that the WIP wiki page is an
index to mailing list threads, git branches or other "updatable"
locations so that it is less likely to need updating and therefore
stays updated w.r.t. it's main purpose: finding out about WIP work.

The policy would say that one must create a mailing list thread, git
branch or else and link it there and **NOT** include original
information on the wiki page but rather just link to ML/git/else.

We could write such policy at the top of the page so contributors to it
can easily see it.

What do you think?

Léo

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  parent reply	other threads:[~2021-04-05 23:36 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
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 [this message]
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=ee19cace7f29560847eaf3635ba4dd7150094bf4.camel@zaclys.net \
    --to=lle-bout@zaclys.net \
    --cc=guix-devel@gnu.org \
    --cc=leo@famulari.name \
    --cc=ludo@gnu.org \
    --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 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.