Re: Bleeding edge documentation
Joshua Branson transcribed 1.1K bytes: > Ricardo Wurmus writes: > > > Nils Gillmann 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. This is about choosing a static webview for the documentation, not a convenience solution which renders them -- which notabug doesn't do by the way. The documentation you view on gnu.org is just checked in into CVS.
Re: Bleeding edge documentation
Ricardo Wurmus writes: > Nils Gillmann 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
Re: Bleeding edge documentation
Nils Gillmann 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. -- Ricardo
Re: Bleeding edge documentation
Ricardo Wurmus transcribed 888 bytes: > > Nils Gillmann 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. > > -- > Ricardo > Ah, good to know. Thanks
Re: Bleeding edge documentation
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?
Bleeding edge documentation
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
