Add markusthoemmes as Scaling Working Group Lead.

[josephburnett]

I propose to add Markus Thömmes (Red Hat) as an additional Scaling Working Group Lead.

Requirements: (link):

Working group leads, or just ‘leads’, are approvers of an entire area that have demonstrated good judgement and responsibility. Leads accept design proposals and approve design decisions for their area of ownership.

Getting to be a lead of an existing working group:

• Recognized as having expertise in the group’s subject matter.
• Approver for some part of the codebase for at least 3 months.
• Member for at least 1 year or 50% of project lifetime, whichever is shorter.
• Primary reviewer for 20 substantial PRs.
• Reviewed or merged at least 50 PRs.
• Sponsored by the technical oversight committee.

Additional requirements for leads of a new working group:

• Originally authored or contributed major functionality to the group's area.
• An approver in the OWNERS file for the group’s code.

Markus has expertise in the Scaling WG subject matter. He has worked deeply with the core autoscaling algorithm to stabilize and improve it (#1091, #1194, #3289). Additionally he was a core contributor to Open Whisk and has prior expertise in the autoscaling problem space (Open Whisk commits).

He has been an approver in the Scaling WG for over 6 months (Nov. 7, 2018). He has been an active code contributor and reviewer. Additionally he has contributed directly to the working group's roadmap (2019 roadmap).

Markus has contributed a lot of critical relayering to the autoscaling code base. E.g. moving activation to the Autoscaler from the Activator (#2198, #2215, #1923) and now separating autoscaler metrics from the decider to allow for HPA scale-to-zero and HPA custom metrics (#4236, #4007, #4260, #4237). As such, he has a good view and vision for the full autoscaling system.

Markus has demonstrated the good judgement and responsibility necessary to serve as Scaling Working Group Lead over a sustained period of time.

[josephburnett]

Technical Oversight Committee: @evankanderson @vaikas-google @mattmoor, please review.

[mattmoor]

/lgtm

[evankanderson]

/lgtm
/approve

[josephburnett]

/assign @mbehrendt

@evankanderson and @mattmoor have approved. Need steering committee approval because of OWNERS file.

[vaikas]

/lgtm

[josephburnett]

@rgregg or @isdal, can you please approve this?

[mbehrendt]

/approve

[knative-prow-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: evankanderson, josephburnett, mbehrendt

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [mbehrendt]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment