Bug 107654 - Account request Kevin Rogovin
Summary: Account request Kevin Rogovin
Status: RESOLVED WONTFIX
Alias: None
Product: Mesa
Classification: Unclassified
Component: Other (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: mesa-dev
QA Contact: mesa-dev
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-08-22 05:13 UTC by Kevin Rogovin
Modified: 2018-08-28 10:18 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
ssh-key (401 bytes, application/vnd.ms-publisher)
2018-08-22 05:13 UTC, Kevin Rogovin
Details
pgp-key (2.41 KB, application/pgp-keys)
2018-08-22 05:15 UTC, Kevin Rogovin
Details

Description Kevin Rogovin 2018-08-22 05:13:54 UTC
Created attachment 141234 [details]
ssh-key

name: Kevin Rogovin
mail: kevin.rogovin@intel.com
user: kevin_rogovin
Comment 1 Kevin Rogovin 2018-08-22 05:15:04 UTC
Created attachment 141235 [details]
pgp-key
Comment 2 Brian Paul 2018-08-22 14:41:50 UTC
Fine by me. Kevin has at least 20 patches in Mesa.
Comment 3 Kenneth Graunke 2018-08-22 17:50:07 UTC
NAK for the time being, as the i965 maintainer.  The 24 patches are over the course of 5 years, with about 1-2 small series a year.  For now, this is easy for people with commit access to review and push as needed.

I'd like to see a) a more recent string of contributions, and b) better evidence of established rapport and trust between the applicant and other developers/reviewers/community members.

We will continue to review/push Kevin's patches and can reevaluate this in the future.
Comment 4 Daniel Stone 2018-08-28 10:18:28 UTC
Ken, Jason, someone - can you please change the Mesa docs so they reference creating a GitLab account and requesting access there (Bugzilla, list, not sure which you'd prefer), rather than attaching GPG keys etc for a legacy account? I had a quick look at Mesa's docs to find out where that might be, but couldn't see it.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.