From: "Michał Górny" <mgorny@gentoo.org>
To: Pascal Jaeger <pascal.jaeger@leimstift.de>, gentoo-guru@lists.gentoo.org
Subject: Re: [gentoo-guru] Discussion: lower entry barriers to the GURU
Date: Thu, 13 Oct 2022 17:25:25 +0200 [thread overview]
Message-ID: <9e37b070580a0be6335a2c93a7ff127b38f6daa7.camel@gentoo.org> (raw)
In-Reply-To: <87o7ufhlon.fsf@leimstift.de>
Hello,
On Thu, 2022-10-13 at 14:51 +0200, Pascal Jaeger wrote:
> I wanted to start a small discussion regarding the entry barriers for new Guru contributors. To wrap up the current situation, in order to get write access to the GURU, people need to:
> • generate a ssh key
I can't imagine this being a problem, given that pretty much any
contribution workflow requires you to authenticate against the server.
I can't really think of an easier way to do that than via SSH keys,
and I find it really hard to imagine that anyone writing ebuilds would
have a problem running ssh-keygen.
> • generate a gpg key
Ok, GPG isn't exactly easy. I suppose it's the hardest part after all
but I think that most of the people interested in contributing manage to
get the absolute minimum of GPG working.
> • file a bug requesting access at b.g.o with their real name, ssh key and the statement they want stick to the project guidelines
How is that a problem? I mean, filing one bug?
> • wait for the bug to be approved and their ssh key to be added
…which usually happens within 24 hours.
I'm sorry but I don't see how your alternative proposal improves
anything. Proxy-maint requires a lot of effort both from contributors
and developers. In fact, the reason I've started GURU was because we
couldn't manage all the influx of pull requests, so I wanted to provide
a way of sharing ebuilds without the bottleneck.
--
Best regards,
Michał Górny
next prev parent reply other threads:[~2024-11-24 22:47 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-13 12:51 [gentoo-guru] Discussion: lower entry barriers to the GURU Pascal Jaeger
2022-10-13 14:18 ` John Helmert III
2022-10-13 14:18 ` Andrew Ammerlaan
2022-10-13 14:33 ` Pascal Jaeger
2022-10-13 14:53 ` tastytea
2022-10-13 15:01 ` Andrew Ammerlaan
2022-10-13 14:45 ` tastytea
2022-10-13 16:24 ` Pascal Jaeger
2022-10-13 19:26 ` tastytea
2022-10-13 21:09 ` Pascal Jaeger
2022-10-13 15:25 ` Michał Górny [this message]
2022-10-13 17:12 ` Pascal Jaeger
2022-10-13 17:29 ` Nicola Smaniotto
2022-10-13 17:39 ` Pascal Jaeger
2022-10-14 8:30 ` Anna “CyberTailor”
2022-10-17 1:49 ` NRK
2022-10-17 7:00 ` Pascal Jaeger
2022-10-17 7:39 ` Andrew Ammerlaan
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=9e37b070580a0be6335a2c93a7ff127b38f6daa7.camel@gentoo.org \
--to=mgorny@gentoo.org \
--cc=gentoo-guru@lists.gentoo.org \
--cc=pascal.jaeger@leimstift.de \
/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