[Mesa-dev] Developer access
jason at jlekstrand.net
Thu Jan 21 17:55:37 UTC 2021
To help smooth things along, I've created a new label "Project Access
Requests" for use with these things. I've subscribed to it myself and
would encourage the other maintainers to do so as well. That way we
see these issues instead of them getting lost in the pile.
On Thu, Jan 21, 2021 at 11:07 AM Mike Blumenkrantz
<michael.blumenkrantz at gmail.com> wrote:
> +1 always in favor of getting more people into the review pipeline
> On Thu, Jan 21, 2021 at 10:05 AM Alyssa Rosenzweig <alyssa.rosenzweig at collabora.com> wrote:
>> Hi all,
>> Icecream95, a long-time Mesa/Panfrost contributor, has requested
>> developer access to mesa on the GitLab issue tracker . Quoting here
>> for convenience of those who monitor the mailing list but not the
>> > @alyssa keeps complaining about getting poked to assign stuff to Marge
>> > for me, so I think it's finally time to ask for Mesa developer access,
>> > so I can do the endless retries until CI stops flaking myself.
>> > Assuming a platform with char as unsigned, I think my 210 patches in
>> > Mesa is more than the 32 commits some have suggested to be required
>> > for the lofty privilege of labelling MRs and bothering the merge bot.
>> All else being equal, with my Panfrost maintainer hat, I am in favour.
>> Marge Bot access would reduce merge friction for their frequent
>> contributions, given the substantial timezone difference with our team
>> at Collabora. Additionally, labeling access would ease triage for us;
>> although I subscribe specifically to Panfrost MRs, I have to monitor all
>> MRs to ensure I haven't missed any from them, a frequent occurrence.
>> [ The cynic reads: This is more for my benefit than theirs ;-) ]
>>  https://gitlab.freedesktop.org/icecream95
>>  https://gitlab.freedesktop.org/mesa/mesa/-/issues/4135
>> mesa-dev mailing list
>> mesa-dev at lists.freedesktop.org
> mesa-dev mailing list
> mesa-dev at lists.freedesktop.org
More information about the mesa-dev