Re: [PATCH 0/5] My first few patches

[Ludovic Courtès]

Hi,

(Looks like this message got stuck in my “draft” folder for a while…)

Arun Isaac <arunisaac@systemreboot.net> skribis:

>> Nope, it’s very low-tech: web pages at gnu.org and nongnu.org are
>> committed to a CVS (yes, CVS!) repository.  Here are the instructions on
>> how to fetch it:
>>
>>   https://savannah.nongnu.org/cvs/?group=skribilo
>>
>> When a new release comes out, I would build the manual and web site,
>> copy it to the CVS checkout, and run “cvs commit -m whatever”.
>
> Low tech indeed! But, the manual work involved is a pain. I think we
> should consider laminar[1], a light-weight continuous integration tool,
> that is much more minimalistic and elegant than big CI systems such as
> Travis. We just need to provide laminar with shell scripts. There is
> even a Guix service for laminar. So, deployment is really easy.
>
> Is it possible to set this up with savannah and GNU's servers? If
> not, could we consider setting up laminar on one of our own servers
> outside GNU?

Unfortunately no, we can’t deploy anything there.  We’d need
infrastructure elsewhere (or perhaps move to, say, sr.ht, which provides
such services apparently.)

>> I would suggest waiting for the next release before updating the manual,
>> so users get to see the one corresponding to the current stable
>> version.
>
> Yes, agreed. But, we should probably host web versions of the manual for
> both the current stable release and the bleeding edge development
> version. This is what many Python projects do, after all.

Yes, that would be ideal.

Thanks,
Ludo’.