Re: Discontinuing data.guix.gnu.org?

["Ludovic Courtès" <ludo@gnu.org>]

Hello Christopher,

Christopher Baines <mail@cbaines.net> skribis:

> Ludovic Courtès <ludo@gnu.org> writes:

[...]

>> Christopher Baines <mail@cbaines.net> skribis:
>>
>>> As previously set out, I'm planning to stop hosting the data service
>>> instances this year. While I would like to stop hosting the server for
>>> data.guix.gnu.org,
>>
>> I forgot the outcome of previous discussions, but it seems to me that
>> the service itself and all the data it accumulated over the years are
>> super valuable.  I would be sad to see it go!
>
> There was a discussion back in April, but no action came directly from
> it.
>
> Just having data.qa.guix.gnu.org was discussed, and at least
> concentrating on getting to a sustainable hosting situation there seemed
> like a sensible priority. The longer history provided by
> data.guix.gnu.org does have value though in my view.
>
>> Is there something we can do to not lose it all?  It could be
>> distributing responsibility, reducing the scope, ensuring hosting is
>> managed collectively by the project, etc.  WDYT?
>
> Since that discussion, I have disabled the database dumps and backups,
> which has reduced (to 62€ per month) the hosting costs (although
> obviously not having backups isn't ideal). It's possible to further
> reduce the hosting costs as well by switching away from a VM to a
> physical machine at Hetzner.
>
> But yeah, given that having at least one data service instance is a key
> part of keeping the bordeaux build farm running, managing the hosting
> through the project seems to be the way to go. I'm just not sure how we
> can get there, or what I can do to move things in that direction.

Like you, I would have hoped for more reactions.  Unfortunately, I’m not
offering to help here because I have more than enough on my plate and
even a 1+ month backlog on guix-devel…

Maintainers, what’s your take on this?

Guix Foundation, is there any blocker to taking responsibility for
covering hosting expenses, possibly rediscussing the scope and cost?

Let 2024 be a thriving Guix year! :-)

Ludo’.