all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Joshua Branson <jbranso@fastmail.com>
To: guix-devel@gnu.org
Subject: Re: Bleeding edge documentation
Date: Wed, 20 Jun 2018 10:39:40 -0400	[thread overview]
Message-ID: <87zhzpo72r.fsf@fastmail.com> (raw)
In-Reply-To: <87r2l1uac3.fsf@elephly.net> (Ricardo Wurmus's message of "Wed, 20 Jun 2018 10:32:44 +0200")

Ricardo Wurmus <rekado@elephly.net> writes:

> Nils Gillmann <ng0@n0.is> writes:
>
>> swedebugia transcribed 1.0K bytes:
>>> Hi
>>>
>>> I would like to have a continously updated documentation for guix on the webpage in addition to the release documentation.
>>>
>>> I'm trying to read up on guix and the guix.texi file is hard to handle on a mobile device and it is quite cumbersome.
>>>
>>> The 0.14 docs are now heavily outdated in my opinion.
>>> --
>>> Cheers Swedebugia
>>
>> This is due to gnu.org using CVS and with every release we have
>> to upload the documentation by hand.
>> Instead of moving the entire webpage out of gnu.org (which has
>> been proposed before), why not create docs.guixsd.org and
>> use that for updated documentation material?
>
> We have applied for a gnu.org subdomain a couple of weeks ago, but
> progress is slow.  The goal is to move to infrastructure that we can
> more easily (and automatically) update.

May I ask what are some of the other infrastructure options are?
notabug? I'm sure you'll guys will choose a good one, but I'm just curious.

>
> --
> Ricardo

  parent reply	other threads:[~2018-06-20 14:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-20  4:00 Bleeding edge documentation swedebugia
2018-06-20  6:10 ` Nils Gillmann
2018-06-20  8:32   ` Ricardo Wurmus
2018-06-20  8:44     ` Nils Gillmann
2018-06-20 14:39     ` Joshua Branson [this message]
2018-06-20 15:12       ` Nils Gillmann

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=87zhzpo72r.fsf@fastmail.com \
    --to=jbranso@fastmail.com \
    --cc=guix-devel@gnu.org \
    /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.