From: Mark Wielaard <mark@klomp.org>
To: Overseers mailing list <overseers@sourceware.org>
Cc: Carlos O'Donell <carlos@redhat.com>
Subject: Re: Sourceware / GNU Toolchain at Cauldron
Date: Tue, 27 Sep 2022 13:02:00 +0200 [thread overview]
Message-ID: <dc262cd23b2a98d287e87288143e5e7648089776.camel@klomp.org> (raw)
In-Reply-To: <2db869b5-5724-18c0-e356-9e5df8f7cb4d@redhat.com>
Hi Carlos,
Thanks for joining the public discussion.
On Mon, 2022-09-26 at 18:04 -0400, Carlos O'Donell via Overseers wrote:
> - There is the "hardening" concern of separating unix user
> > accounts
> > for separate services like running git hooks. This is one of the
> > things that the buildbot service offers. We could also adopt
> > something like gitolite.
>
> ... and run them on a distinct machine (which requires machine resources, and admin
> time, etc).
>
> Adopting gitolite is also a great step in the direction of not having real accounts
> for users of a services.
Lets add gitolite to the roadmap, I think it is a great idea to offer
it to projects. I am running it personally for code.wildebeest.org, it
is packaged and I know it is practically zero-maintenance to run. We
can even run it inside a project specific container or vm to have more
isolation.
> Technically speaking, I think the Linux Foundation IT, with their existing work with
> public-inbox (ahead of its time), b4, patatt, and more, means they are globally the
> best positioned to keep solving these problems and supporting the development of
> these FOSS tools for the linux kernel and others. Even more so for a distributed
> development model that we use for the GNU Toolchain.
I agree they do some nice work supporting those upstream tools and
services. And I have been really happy that we now have our own public-
inbox instance at https://inbox.sourceware.org/
There is a bit more background about using it with b4 including a
discussion on patch attestation in the original BoF discussion
presentation:
https://gnu.wildebeest.org/~mark/sourceware/presentation.html#slide14
Press 'p' for presentation notes for some additional
background/questions. Or see the raw markdown presentation:
https://gnu.wildebeest.org/~mark/sourceware/sourceware.md
b4 console session:
https://gnu.wildebeest.org/~mark/sourceware/b4.session.txt
Cheers,
Mark
next prev parent reply other threads:[~2022-09-27 11:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-16 20:57 Zoë Kooyman
2022-09-16 21:10 ` Ian Kelling
2022-09-18 16:27 ` Mark Wielaard
2022-09-18 21:38 ` Mark Wielaard
2022-09-19 21:09 ` Mark Wielaard
2022-09-26 22:04 ` Carlos O'Donell
2022-09-27 1:31 ` Alexandre Oliva
2022-09-27 11:02 ` Mark Wielaard [this message]
2022-09-28 11:14 ` Frank Ch. Eigler
2022-09-30 13:38 ` Carlos O'Donell
2022-10-02 14:55 ` Frank Ch. Eigler
2022-10-03 13:26 ` Siddhesh Poyarekar
2022-10-03 13:53 ` Frank Ch. Eigler
2022-10-03 19:16 ` Mark Wielaard
2022-10-03 15:55 ` Christopher Faylor
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=dc262cd23b2a98d287e87288143e5e7648089776.camel@klomp.org \
--to=mark@klomp.org \
--cc=carlos@redhat.com \
--cc=overseers@sourceware.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.
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).