From: Emil Velikov <emil.l.velikov@gmail.com>
To: Daniel Stone <daniel@fooishbar.org>
Cc: Eric Engestrom <eric.engestrom@intel.com>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
Lucas De Marchi <lucas.demarchi@intel.com>,
dri-devel <dri-devel@lists.freedesktop.org>,
"Vivi, Rodrigo" <rodrigo.vivi@intel.com>
Subject: Re: [PATCH libdrm] CONTRIBUTING: clarify how to request a Developer role
Date: Thu, 20 Sep 2018 13:29:45 +0100 [thread overview]
Message-ID: <CACvgo52FHtPi+eMChk-T=NuzcSN-txFcdmRo6w7qZ++quRhOuQ@mail.gmail.com> (raw)
In-Reply-To: <CAPj87rNX2ch2344_Kb11XjPa-Bc0-2xKe_3=PwvASo0=kdVWvA@mail.gmail.com>
On 17 September 2018 at 11:01, Daniel Stone <daniel@fooishbar.org> wrote:
> Hi,
>
> On Sat, 15 Sep 2018 at 00:56, Lucas De Marchi <lucas.demarchi@intel.com> wrote:
>> -To apply for commit rights ("Developer" role in gitlab) send a mail to
>> -dri-devel@lists.freedesktop.org and please ping the maintainers if your request
>> -is stuck.
>> +To apply for commit rights ("Developer" role in gitlab), check project
>> +members who have the "owner" role at
>> +https://gitlab.freedesktop.org/mesa/drm/project_members?sort=access_level_desc.
>> +Any of them can add new developers.
>
> I think it still makes sense to discuss it publicly, either on the
> list or through a bug tracker. Having an audit log of who's there and
> why is pretty important. I would suggest the process be to email
> dri-devel@ and request it, then if nothing happens ping one of the
> people listed there as an owner.
>
Fully agreed on that - transparency is essential.
I wonder if gitlab will get some logging for project specifics -
people added/removed, changing the repo public <> private.
-Emil
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2018-09-20 12:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-14 18:24 Request for commit rights on libdrm Lucas De Marchi
2018-09-14 18:27 ` Daniel Vetter
2018-09-14 23:48 ` Lucas De Marchi
2018-09-14 23:55 ` [PATCH libdrm] CONTRIBUTING: clarify how to request a Developer role Lucas De Marchi
2018-09-17 10:01 ` Daniel Stone
2018-09-17 19:25 ` Sean Paul
2018-09-19 23:27 ` [PATCH libdrm v2] " Lucas De Marchi
2018-09-20 0:20 ` Rodrigo Vivi
2018-09-20 5:54 ` [PATCH libdrm v3] " Lucas De Marchi
2018-09-20 12:18 ` Eric Engestrom
2018-09-20 12:29 ` Emil Velikov [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='CACvgo52FHtPi+eMChk-T=NuzcSN-txFcdmRo6w7qZ++quRhOuQ@mail.gmail.com' \
--to=emil.l.velikov@gmail.com \
--cc=daniel.vetter@ffwll.ch \
--cc=daniel@fooishbar.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=eric.engestrom@intel.com \
--cc=lucas.demarchi@intel.com \
--cc=rodrigo.vivi@intel.com \
/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 NNTP newsgroup(s).