Nominating Keith Mattix as networking maintainer

83 views
Skip to first unread message

Eitan Yarmush

unread,
Sep 4, 2026, 6:22:34 PMSep 4
to ate-dev
I am sending this email to formally nominate Keith Mattix (@keithmattix) as a networking maintainer for Substrate.

Substrate relies heavily on networking for many aspects of its operation, and there are few folks out there with as much experience in cloud native networking and policy as Keith Mattix.

In addition to the amazing work he's put in to Substrate over the last couple of months, he's also an active maintainer and contributor to many other related cloud native projects such as Istio, and Gateway API.

Similar to previous nominations, if you have objections please feel free to ping me directly. Otherwise like Tim I propose a lazy consensus period of 7 days.

Eitan

Bowei Du

unread,
Sep 8, 2026, 1:09:36 PMSep 8
to Eitan Yarmush, ate-dev
Hi -- 

I love Keith's work in other domains, but do we think this may be a tad early specifically for Substrate? (3 PRs)

BTW -- I'm pretty sure give Keith's current trajectory, he would be able to make it soon.

Thanks,
Bowei

--
You received this message because you are subscribed to the Google Groups "ate-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ate-dev+u...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/ate-dev/665e8a81-9d54-4029-b22c-b39aa9994780n%40googlegroups.com.

Tim Hockin

unread,
Sep 8, 2026, 2:26:24 PMSep 8
to Bowei Du, Eitan Yarmush, ate-dev
We, as a project, need to set better criteria for this.  Right now it says "has made enough contributions" which I confess is a cop out.  It's very easy to "game" metrics like this, but "you know it when you see it" is just as easily abused. 

I know Keith has been super involved in a lot of discussions of very complex things.  Does that count as "enough" to be a full maintainer of the project?  I don't know, and I am not just trying to be polite.  We don't have criteria.  At this early stage, "contribution" is super vague.

We don't yet have OWNERS files (yet!), which I think would help anchor this discussion.  Even if we don't ENFORCE it yet, it captures intentions.  Github CODEOWNERS is a hot mess, IMO.  Is it worth establishing some OWNERS files?

We have all been busy and so this discussion has been postponed, but it has to happen eventually (and soon).

Tim

Bowei Du

unread,
Sep 18, 2026, 1:04:39 PM (5 days ago) Sep 18
to Tim Hockin, Eitan Yarmush, ate-dev
Circling back on this -- my comment was more towards having some sort of documented process in general.

I am +1 with Keith, he has been great on working through and driving some big changes to how the networking bits work.

Thanks,
Bowei
Reply all
Reply to author
Forward
0 new messages