1 |
Hi! |
2 |
|
3 |
I'm Matt Turner. I've used Gentoo since 2004. I've been a developer since 2010. |
4 |
I have 9100+ commits in ::gentoo since the transition to git in 2015. |
5 |
|
6 |
Please reply to this mail with any questions you have for me. |
7 |
|
8 |
# Employment |
9 |
|
10 |
I am employeed by Google, Inc., as a member of the ChromeOS Graphics team, |
11 |
currently working on the freedreno/turnip 3D drivers in Mesa. Previously I was |
12 |
at Intel where worked on the Mesa/i965 team. |
13 |
|
14 |
# Role of a Council member |
15 |
|
16 |
A Council member should already be a leader in Gentoo, irrespective of the title. |
17 |
|
18 |
A Council member should drive the distro forward and build consensus around |
19 |
current issues (Note that consensus need not be unanimous). |
20 |
|
21 |
A Council member should be willing to disagree and commit [1]. A Council member |
22 |
should participate in discussions in a good faith effort to build consensus; the |
23 |
purpose of a discussion is not for others to hear your point. |
24 |
|
25 |
A Council member should be someone who works on issues larger than their |
26 |
immediate responsibilities. That is to say, a Council member should recognize |
27 |
places that need their help and not shy away from taking on a task because it's |
28 |
not their direct responsibility. The whole Gentoo distribution is the |
29 |
responsibility of a Council member. |
30 |
|
31 |
It should be obvious to say that a Council member should be able to allocate |
32 |
sufficient time and energies to prepare for meetings, participate in |
33 |
discussions, and handle Council matters that are assigned to them. If I were to |
34 |
fail in these most basic responsibilities I would certainly not accept another |
35 |
nomination until I knew I would be able to fulfil them. |
36 |
|
37 |
# Technical Contributions |
38 |
|
39 |
I'm the current lead of the Release Engineering team, where I develop the |
40 |
Catalyst tool, and maintain automated build systems for the various supported |
41 |
architectures. I've been responsible for many hardware upgrades in recent years: |
42 |
I wrote and managed a grant request for a new SPARC developer system; I |
43 |
organized and managed upgrading our ARM64 developer system. Unexpectedly, I'm |
44 |
mentoring a GSoC project working on catalyst this year as well. |
45 |
|
46 |
I'm a member of most of our architecture teams. I'm currently the lead of the |
47 |
Alpha and MIPS teams. Where it's made sense, I've dropped stable keywords to |
48 |
lighten the load for arch testers and to remove roadblocks for others: for |
49 |
example by removing all stable keywords on alpha and ia64, most on hppa. |
50 |
|
51 |
I've been the primary maintainer for X11 in Gentoo since before we transitioned |
52 |
to git. I'm the current lead of the X11 project. |
53 |
|
54 |
More recently I joined the GNOME project, where I added GNOME 3.38 and then |
55 |
GNOME 40 to the tree. See |
56 |
https://mattst88.com/blog/2021/05/13/GNOME_40_available_in_Gentoo/ |
57 |
|
58 |
# Social Contributions |
59 |
|
60 |
I served as a Council member for the 2020-2021 term. I am pleased that I was |
61 |
able to bring the issue of rampant Social Contract violations in the Off The |
62 |
Wall subforum to the Council's attention, leading to its necessary closure. |
63 |
|
64 |
I have been a member of the Community Relations for the last three years. When I |
65 |
was invited to join, I did so not because I wanted to be involved in more |
66 |
disagreements, but because I thought that this was an area that was ripe for |
67 |
improvement. I believe that the difference between ComRel three years ago and |
68 |
today are night and day in an extremely improved way. |
69 |
|
70 |
[1] https://en.wikipedia.org/wiki/Disagree_and_commit |