From mboxrd@z Thu Jan 1 00:00:00 1970 From: ludo@gnu.org (Ludovic =?utf-8?Q?Court=C3=A8s?=) Subject: Re: Should we start a Guix users wiki? Date: Tue, 08 Sep 2015 11:54:01 +0200 Message-ID: <87pp1tnsna.fsf@gnu.org> References: <55EE0ADD.9050701@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:49756) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZZFbI-0002rz-Ip for guix-devel@gnu.org; Tue, 08 Sep 2015 05:54:05 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZZFbH-0003bA-I7 for guix-devel@gnu.org; Tue, 08 Sep 2015 05:54:04 -0400 In-Reply-To: <55EE0ADD.9050701@gmail.com> (Craig Barnes's message of "Mon, 07 Sep 2015 23:08:29 +0100") List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org To: Craig Barnes Cc: guix-devel@gnu.org Hi, Craig Barnes skribis: > Some time ago I asked on IRC about a guix users wiki. Someone suggest > that I propose one here (sorry it's taken so long). > > I think that a wiki would be a good complement to the manual, which > while quite complete, lacks exhaustive examples (which would be > impractical). I have mixed feelings. There are several issues with a Wiki: one can hardly know which version of the software it=E2=80=99s talking about (where= as the installed Info pages of PDFs necessarily match the installed version), and more importantly, it tends to be disorganized, unmaintained, and often misleading. I would strongly encourage people to help fix the manual as a first step. If information that a user deems useful is missing from the manual, then it=E2=80=99s a bug. I=E2=80=99m willing to make it as simple = as possible to fix the manual. But really, the manual should have all the examples necessary for people to understand how to tweak things. There might be cases where specific information doesn=E2=80=99t quite fit i= n the manual, like, say, instructions for a specific laptop model. These could go in a wiki. Overall, I think it=E2=80=99s fine to have stuff at for instance, but the manual should clearly remain the primary source of documentation, without any ambiguity. So, what would you like to add to the manual? :-) Thanks, Ludo=E2=80=99.