public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: "Cristian Rodríguez" <cristian@rodriguez.im>
Cc: overseers@sourceware.org, libc-alpha@sourceware.org
Subject: Re: Updated Sourceware infrastructure plans
Date: Fri, 17 May 2024 15:42:18 +0200	[thread overview]
Message-ID: <3b0954f4791ad2eec08db59ac93353ebe75f2151.camel@klomp.org> (raw)
In-Reply-To: <CAPBLoAfZbnPK2bf5UmkZn09MQNTeJEkvdLhRqvRB72Y3-Bcbnw@mail.gmail.com>

Hi Cristian,

On Thu, 2024-05-16 at 11:58 -0400, Cristian Rodríguez wrote:
> On Wed, Apr 17, 2024 at 7:28 PM Mark Wielaard <mark@klomp.org> wrote:
> 
> 
> > More feedback is always welcome. See the various contact options at
> > https://sourceware.org/mission.html#organization
> 
> Sorry to revive this oldish thread but I didn't find any other thread
> where my suggestions will be on-topic
> 
> Today I looked at patchwork briefly and found out I need to register
> an account, bugzilla also needs an account, pretty much everything you
> add will in one way or another register an account.
> Do your plans include some sort of single sign on ? ideally one that
> does not need to register new accounts. or at the very least if "login
> with <your favourite code hosting site> is not acceptable..a
> sourceware-specific keycloak instance that replaces all ad-hoc login
> methods?

Good question. There is also the wiki, where you have to create an
account yourself and then be granted access to the EditorGroup. And of
course when we introduce a "pull request" service, being it through
gerrit or some other method, we will want it to be easily accessible.

Things used to be easy some years back. You only needed an account for
pushing commits to a specific project repository. But you could just
submit patches through email that others could commit for you. Accounts
for bugzilla or the wiki could be created by hand and gave you
immediate permission to submit issues or improvements.

Sadly spammers ruined everything. For email patch submissions we seem
to handle it mostly OK (thanks spamassassin). But for bugzilla and the
wikis we had to hand approve everything. Otherwise spammers would mass
create accounts and just produce so much spam comments the system just
wasn't usable anymore.

So for patchwork and the experimental gerrit server we are setting up
now you can self-register and use the service directly. Spammers don't
seem to have found a way abuse those systems yet. But patchwork has
already accumulated 5000+ accounts...

And they aren't linked. patchwork uses the django user framework, the
current gerrit setup uses keycloak (but Sergio would like to switch to
Authentik). Bugzilla uses its own user framework, as does MoinMoin.

It would be great to have one account system to rule them all. But we
will probably always have to have some procedure to register/enable
accounts to keep spammers out. Hopefully if an account is approved for
one system then we can trust the user to contribute through any of the
others.

Cheers,

Mark

      reply	other threads:[~2024-05-17 13:42 UTC|newest]

Thread overview: 59+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-17 23:27 Mark Wielaard
2024-04-18  6:04 ` Thomas Koenig
2024-04-18  8:14   ` FX Coudert
2024-04-18  9:01     ` Christophe Lyon
2024-04-18 11:38     ` Janne Blomqvist
2024-04-18 12:01       ` Generated files in libgfortran for Fortran intrinsic procedures (was: Updated Sourceware infrastructure plans) Tobias Burnus
2024-04-18 12:32         ` Martin Uecker
2024-04-19  9:35   ` Updated Sourceware infrastructure plans Jonathan Wakely
2024-04-18 15:56 ` Joseph Myers
2024-04-18 17:37   ` Frank Ch. Eigler
2024-04-18 17:54     ` Joseph Myers
2024-04-18 18:29     ` Matt Rice
2024-04-22 15:39     ` Tom Tromey
2024-04-23  2:55       ` Jason Merrill
2024-04-23  3:12         ` Simon Marchi
2024-04-23  3:24         ` Tom Tromey
2024-04-23  3:51           ` Jason Merrill
2024-04-23  8:56             ` Mark Wielaard
2024-04-23  9:39               ` Richard Earnshaw (lists)
2024-04-23 15:08             ` Tom Tromey
2024-04-23 15:25               ` Simon Marchi
2024-04-24  8:49                 ` Aktemur, Tankut Baris
2024-04-23  4:06           ` Ian Lance Taylor
2024-04-23  9:30           ` Richard Earnshaw (lists)
2024-04-23 13:51             ` Ian Lance Taylor
2024-05-01 19:15           ` Jeff Law
2024-05-01 19:38             ` Jonathan Wakely
2024-05-01 20:20               ` Mark Wielaard
2024-05-01 20:53                 ` Tom Tromey
2024-05-01 21:04                   ` Simon Marchi
2024-05-02 15:35                     ` Pedro Alves
2024-05-02 23:05                       ` Fangrui Song
     [not found]                       ` <DS7PR12MB57651DA3A5C22B2847C13580CB182@DS7PR12MB5765.namprd12.prod.outlook.com>
2024-05-07 16:17                         ` Joseph Myers
2024-05-10 10:43                           ` Ben Boeckel
2024-05-01 20:04             ` Jason Merrill
2024-05-01 21:26               ` Mark Wielaard
2024-05-01 22:01                 ` Sergio Durigan Junior
2024-05-02 12:54                 ` Claudio Bantaloukas
2024-05-02 15:33                 ` Pedro Alves
2024-05-03  2:59                   ` Ian Lance Taylor
2024-05-04 19:56                 ` Ben Boeckel
2024-05-05  5:22                   ` Benson Muite
2024-05-06 13:58                     ` Ben Boeckel
2024-05-07 16:26                   ` Joseph Myers
2024-05-01 21:38               ` Jeff Law
2024-05-02  6:47                 ` Richard Biener
2024-05-02 11:29                   ` Ian Lance Taylor
2024-05-02 14:26                   ` Simon Marchi
2024-05-02 11:45                 ` Mark Wielaard
2024-05-01 22:56               ` Tom Tromey
2024-04-23 10:34         ` Florian Weimer
2024-04-22 10:01   ` Mark Wielaard
2024-04-22 13:23     ` Joseph Myers
2024-04-19  9:33 ` Jonathan Wakely
2024-04-22 10:24   ` Mark Wielaard
2024-04-22 11:40     ` Jonathan Wakely
2024-04-23  0:48   ` Frank Ch. Eigler
2024-05-16 15:58 ` Cristian Rodríguez
2024-05-17 13:42   ` Mark Wielaard [this message]

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=3b0954f4791ad2eec08db59ac93353ebe75f2151.camel@klomp.org \
    --to=mark@klomp.org \
    --cc=cristian@rodriguez.im \
    --cc=libc-alpha@sourceware.org \
    --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).