[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Discussion on Salsa account creation for newcomers during on-site events



On Sat, Nov 29, 2025 at 02:51:55PM +0100, Joerg Jaspert wrote:
> On 17792 March 1977, Jongmin Kim wrote:
> 
> > We experienced the following three blocking cases during a recent
> > on-site
> > event.
> 
> > As like contributors.debian.org, there could be an automatic
> > account-approval process (e.g. form) available at least to DDs:
> >     [Claim identifiers for $UID]
> > https://contributors.debian.org/claim/$UID/
> > Such a feature would greatly improve the smooth running and timing of
> > on-site events to gather new contributors.
> 
> In general there is nothing to say against a process where an existing DD
> could vouch for a new signup on salsa.
> 
> Gitlab has an API that allows one to do so.
> 
> I can imagine a webapp where a DD can approve (or deny) requests. That's
> basically what we salsa admins currently do (well, mostly with a script, but
> that uses the Gitlab API thing). Only, we do have admin rights, and we do
> not want to hand those to each and every DD, obviously, and as far as I can
> see, it is currently bound to that admin role.
> 
> So if you (or someone) comes up with a standalone webapp that we can run on
> some .d.o host that allows the user approval step (and writes some logs
> about it) for anyone who is a DD - I do think it has a good chance of
> getting run. It would take much pretty boring work away from us.
> 
> Basic requirements:
> 
> - Does *NOT* patch gitlab in any way. Runs externally on some web server and
> only uses gitlab API, that is, is entirely independent of the actual gitlab
> instance.
> - Does some verification that the user using it is actually a DD.
> - Keeps logs of the actions.
> 
> There might be more requirements, this is just quick thinking, and its only
> me speaking, not yet the rest of the team. But I'm in favor, if its
> implemented with care.

IMO we do not even need a web app for this. We can solve this with a git
repository where only DDs can write to. DDs would list usernames that
should be approved in a text file, one per line. It
would then be easy to change our user review script to fetch that
repository and read the hints from it. git gives us logging and
traceability for free.

This idea was inspired by how the Release team manages their hints files
for the testing migration scripts.

I can draft something like this relatively easily.

Attachment: signature.asc
Description: PGP signature


Reply to: