From: Jani Nikula <jani.nikula@linux.intel.com>
To: Daniel Stone <daniel@fooishbar.org>
Cc: Maxime Ripard <mripard@kernel.org>,
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 14:03:53 +0200 [thread overview]
Message-ID: <87y1b7mnyu.fsf@intel.com> (raw)
In-Reply-To: <CAPj87rPB9+o1g8gJyZk3m2DLhW=FC+3m5Nrm=Mxq3SwqxX3KCg@mail.gmail.com>
On Mon, 26 Feb 2024, Daniel Stone <daniel@fooishbar.org> wrote:
> On Mon, 26 Feb 2024 at 11:57, Jani Nikula <jani.nikula@linux.intel.com> wrote:
>> On Mon, 26 Feb 2024, Maxime Ripard <mripard@kernel.org> wrote:
>> > 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.
>
> It's a fair question. If you want to verify that someone is
> @intel.com, maybe get them to email you out-of-band to check it. If
> you want to check something else, just ask an admin I suppose.
I thought you wanted not to be bothered with access requests! ;D
BR,
Jani.
--
Jani Nikula, Intel
next prev parent reply other threads:[~2024-02-26 12:04 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
2024-02-26 12:00 ` Daniel Stone
2024-02-26 12:03 ` Jani Nikula [this message]
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=87y1b7mnyu.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=airlied@gmail.com \
--cc=daniel@ffwll.ch \
--cc=daniel@fooishbar.org \
--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.