unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel@gnu.org
Subject: Re: git hook error
Date: Tue, 28 Dec 2021 18:46:58 -0500	[thread overview]
Message-ID: <Ycuh8uBct5WQoqfK@jasmine.lan> (raw)
In-Reply-To: <871r1wicgr.fsf@elephly.net>

On Tue, Dec 28, 2021 at 11:31:10PM +0100, Ricardo Wurmus wrote:
> The motivation for that is not found in just one big problem.  It’s a
> small trickle of minor annoyances:
> 
> - Savannah’s uptime isn’t quite as high as we’d like

Okay. I wonder if we could actually do a better job, or if anybody who
hosts a comparable repo does.

Our own record with the build farm and the record of major hosts like
Github are both somewhat discouraging. And if we could only hope for an
equivalent uptime to Savannah, it doesn't seem worth it to shoulder this
work ourselves.

> - we can’t have server-side checks to prevent pushing bad commits
> - we can’t have server-side hooks to better integrate with the build farm
> - we can’t have per-branch rules (e.g. to allow contributors to push to
>   some but not all branches)

We do actually have a server-side hook in place to prevent pushing
unsigned commits. And if we wanted to add more tooling, the Savannah
admin(s) would help us.

Now, if we just wanted more control and visibility into the
infrastructure, that's a reason, but again, I wonder if it's worth the
effort. In terms of infrastructure maintenance, we already seem to be
stretched thin.

My opinion is that, in order to consider hosting our own Git server, we
should wait until people are using declarative Guix configuration to
operate reliable, performant, and public Git servers that would meet our
needs. That is, the Guix project needs to grow this capability without
the heroic effort of a single volunteer. Because that's what we have now
with Savannah, more or less, and we don't have to work for it. Maybe
this has already been achieved, I don't know.


  parent reply	other threads:[~2021-12-28 23:47 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-28 20:10 git hook error Ricardo Wurmus
2021-12-28 20:26 ` Tobias Geerinckx-Rice
2021-12-28 20:35   ` Leo Famulari
2021-12-28 21:09     ` Ricardo Wurmus
2021-12-28 21:40       ` Leo Famulari
2021-12-28 22:31         ` Ricardo Wurmus
2021-12-28 22:45           ` Tobias Geerinckx-Rice
2021-12-29  0:01             ` Tobias Geerinckx-Rice
2021-12-28 23:46           ` Leo Famulari [this message]
2021-12-29  8:53             ` zimoun
2021-12-28 23:32         ` raingloom

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Ycuh8uBct5WQoqfK@jasmine.lan \
    --to=leo@famulari.name \
    --cc=guix-devel@gnu.org \
    --cc=rekado@elephly.net \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).