Add mdemirhan to /OWNERS

[tcnghia]

From https://github.com/knative/docs/blob/master/community/ROLES.md#approver

• Reviewer of the codebase for at least 3 months or 50% of project lifetime, whichever is shorter

  • First review 2/2018: Add build rules and instructions for enabling Istio sidecar injection #278
  • Most recent reviewed 9/2018: fix log format in activator #2083

• Primary reviewer for at least 10 substantial PRs to the codebase

  • Add activator metrics and dashboard #1726
  • Migrate to Istio v1alpha3 Gateway / VirtualService #1228
  • Keep the deployment when scale to zero #1383
  • activator for 0->1 case #341
  • Structured logging for route controller #888
  • Allow traffic going outside the cluster #1123
  • Logging improvements #1620
  • Plumb revision annotations through to services and deployments #576
  • Add retries in activator and envoy timeout to avoid 503's #1226
  • Autoscaler metrics and performance investigation guide #789

• Reviewed or merged at least 30 PRs to the codebase: Authored 56 PRs in serving.

• Nominated by an area lead: Nominated by Networking WG Lead.

[vaikas]

/lgtm

@evankanderson

[mattmoor]

@tcnghia nit: can you break the unrelated ./cmd/webhook file into its own PR?

[mattmoor]

Nominated by an area lead: Nominated by Networking WG Lead.

My interpretation of this process is that the lead nomination is pertinent to adding a person to that WG's area of ownership (e.g. via OWNERS_ALIASES), and generally the justification PRs should be scoped to that area.

This PR touches on a bit of a gray area since this repo straddles a half dozen WGs, and so we've historically left a couple directories very restricted (to basically the TOC). The two that come to mind are the "public API" (pkg/apis/serving) and the root directory.

Given that @mdemirhan is already in a majority of the approver groups (and I'd consider him for at least one more), I'd be receptive to expanding this group and lightening our review load (I'm looking at you Gopkg.toml!).

I'll put this on the agenda for the TOC meeting Thursday.

[mattmoor]

/lgtm
/approve

You can see some commentary on the decision here.

[knative-prow-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: mattmoor, tcnghia

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

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [mattmoor]

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