unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Léo Le Bouter" <lle-bout@zaclys.net>
To: Vincent Legoll <vincent.legoll@gmail.com>,
	guix-devel <guix-devel@gnu.org>
Subject: Re: Document our WIP
Date: Sat, 27 Mar 2021 15:20:30 +0100	[thread overview]
Message-ID: <a33f0382c4dda3c39887c68f0d86c2246a244997.camel@zaclys.net> (raw)
In-Reply-To: <CAEwRq=psRtmbxweWnyantxGxuO2YED=t1TECdC6qW=X6Q7HENg@mail.gmail.com>

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

On Sat, 2021-03-27 at 11:07 +0100, Vincent Legoll wrote:
> Hello,
> 
> I'd like to reiterate my proposal to document our
> ongoing projects, maybe with a "WIP" page on the
> web site (even if I'm not a web guy, I volunteer
> the maintenance of it).
> 
> * CI-built pinebook-pro images [1]
> * other ARM boards
> * ppc64 & ppc
> * Hurd VM
> * Full source bootstrap
> 
> And probably other things I missed.
> 
> This should complement the ML archives, IRC logs or
> blog, with pointers to (hopefully) more current infos
> on those subjects.
> 
> WDYT ?
> 
> [1] I only (accidentally) discovered today that those
> exist
> 

That would be really awesome, I suggest that we introduce such a
mechanism in a way that ANYONE can edit and that we moderate or filter
spam after the fact, not *before*. As gatekeeping in this way will make
the WIP documents edits grind to a halt and not be a viable solution.

We could use a wiki for this, but inspired by Wikipedia's model where
one does not need to register, or that registration is approved with an
easy process where many people have power to approve registrations so
registrations are never stuck waiting for approval. After such
registrations, users must be able to make unlimited edits to the wiki
as they wish. If there's problematic edits, we can moderate and filter
spam after the fact.

These are to me requirements for such an initiative to succeed.

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

  reply	other threads:[~2021-03-27 14:20 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 [this message]
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
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=a33f0382c4dda3c39887c68f0d86c2246a244997.camel@zaclys.net \
    --to=lle-bout@zaclys.net \
    --cc=guix-devel@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 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).