From: Jani Nikula <jani.nikula@linux.intel.com>
To: Maxime Ripard <mripard@kernel.org>
Cc: dri-devel@lists.freedesktop.org, Daniel Vetter <daniel@ffwll.ch>,
David Airlie <airlied@gmail.com>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Thomas Zimmermann <tzimmermann@suse.de>,
Daniel Stone <daniels@collabora.com>
Subject: Re: drm-misc migration to Gitlab server
Date: Mon, 26 Feb 2024 13:57:40 +0200 [thread overview]
Message-ID: <871q8zo2tn.fsf@intel.com> (raw)
In-Reply-To: <oazstrooilko4tfmead3b4l32tmz3szqpwgzy3kyga3xahjjfw@cbosrrwaul77>
On Mon, 26 Feb 2024, Maxime Ripard <mripard@kernel.org> wrote:
> On Mon, Feb 26, 2024 at 01:33:24PM +0200, Jani Nikula wrote:
>> On Tue, 20 Feb 2024, Maxime Ripard <mripard@kernel.org> wrote:
>> > ## Adding the a remaining users
>> >
>> > I was able to identify most of the users with an account on the old git
>> > server. However, there's a few I couldn't match with certainty to a
>> > gitlab account:
>> >
>> > * andr2000
>> > * jsarha
>> >
>> > Please let me know your Gitlab user so I can add them to the group.
>>
>> Is there no way for project owners/maintainers to see the email
>> addresses for members or access requests?
>>
>> We've been pretty lax with giving reporter role to deal with issues, but
>> it's quite a different thing to give developer role with push access,
>> and feels like you'll need a side channel to match usernames with email
>> addresses.
>
> For the recent-ish subscriptions, it's possible since we've required to
> open a Gitlab issue for a while, so we have the association between the
> Gitlab account and the SSH account already.
>
> During the Gitlab setup, the groups were also created already with the
> people that had an SSH account at the time, and Gitlab account.
>
> But for the rest, yeah, I had to ping Daniel S. about it. He could find
> a few matches, but there's some where we just don't know if or what the
> Gitlab account is.
>
> Generally speaking, we've been conservative about it, and only added
> accounts we were sure of.
Ah, I didn't make myself clear. I'm more interested in the process going
forward, for new access requests. Anyone can create an account and
request access; how does a maintainer verify the request? For our
purposes it's basically just matching againt the email addresses in
existing commits in the repo.
BR,
Jani.
--
Jani Nikula, Intel
next prev parent reply other threads:[~2024-02-26 11:57 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-20 8:49 drm-misc migration to Gitlab server Maxime Ripard
2024-02-20 9:04 ` Maxime Ripard
2024-02-20 11:25 ` Daniel Stone
2024-02-20 22:46 ` Stephen Rothwell
2024-02-21 0:22 ` Daniel Stone
2024-02-26 14:50 ` Daniel Vetter
2024-02-26 21:35 ` Stephen Rothwell
2024-02-28 16:33 ` Daniel Vetter
2024-02-28 21:56 ` Stephen Rothwell
2024-03-14 8:39 ` Maxime Ripard
2024-03-14 10:00 ` Stephen Rothwell
2024-02-26 11:33 ` Jani Nikula
2024-02-26 11:41 ` Maxime Ripard
2024-02-26 11:57 ` Jani Nikula [this message]
2024-02-26 12:00 ` Daniel Stone
2024-02-26 12:03 ` Jani Nikula
2024-02-26 12:09 ` Daniel Stone
2024-02-26 13:14 ` Maxime Ripard
2024-02-26 11:36 ` [dim PATCH] dim: drm-misc: Membership requests now go through Gitlab Maxime Ripard
2024-02-26 11:36 ` [rerere PATCH] nightly.conf: Update the drm-misc repo Maxime Ripard
2024-02-28 14:18 ` drm-misc migration to Gitlab server Daniel Vetter
2024-03-01 16:11 ` Maxime Ripard
2024-03-06 15:29 ` [rerere PATCH v2] nightly.conf: Update the drm-misc repo Maxime Ripard
2024-03-06 15:38 ` [PATCH v2 1/2] MAINTAINERS: Update drm-misc.git URL Maxime Ripard
2024-03-06 15:38 ` [PATCH v2 2/2] MAINTAINERS: Update drm-misc web page Maxime Ripard
2024-03-07 14:02 ` Jani Nikula
2024-03-08 9:49 ` Maxime Ripard
2024-03-12 13:56 ` drm-misc migration to Gitlab server Maxime Ripard
2024-04-01 16:49 ` Tvrtko Ursulin
2024-04-29 17:06 ` Helen Koike
2024-04-29 17:56 ` Jani Nikula
2024-04-29 18:29 ` Helen Koike
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=871q8zo2tn.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=airlied@gmail.com \
--cc=daniel@ffwll.ch \
--cc=daniels@collabora.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=tzimmermann@suse.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.