Update contributing doc for reviewing, update owners file

[cdrage]

Owners file currently isn't being used (unless we have the Kubernetes
bot in-use), however, it needed a well-overdue update.

I've gone ahead and updated the CONTRIBUTING.md doc to add the change
that it requires two reviews for a code-review and one for a doc
review.

[kadel]

few stupid questions as always 😇
What is difference between assignees, reviewers and reviewers in OWNERS file?

It might be better to write names in alphabetical order, it will easier to find name there.

Are we going to require 2 acks for every code PR?
I know that we discussed that before, and decided that we will do it only for some PR, but didn't set any rules around that :-(
I'm OK with requiring 2 ack from now on, we can try it to see how much it will slow us down, or if at all.

[cdrage]

@kadel

It's to do with their "mungebot" for merging. Difference is that you can /lgtm to the bot as an reviewer, same as the asignee. Approvers of course are able to /merge the PR with mungebot.

Honestly, I doubt we're going to use mungebot here (I've tried configuring it once before and found it too cumbersome for our needs), but it's nice to have consistency here.

👍 for two ack's comment. If it slows us down let's switch back to one ack. Or we could have it that it's 1 maintainer ack and 1 other maintainer OR non-maintainer ack.

[kadel]

OK, lets go with 2 maintainers lgtm for now, if will be too much we can relax rules to 1 maintainer and one other.

There is no way to enforce 2 lgtms without bot :-(, we will have to keep that in mind and trust each other.

[surajssd]

@cdrage my username is added twice in reviewer section, i think you wanted to add @surajnarwade

[cdrage]

@surajssd Updated! Just need another review and then we can merge this in.

[kadel]

pretty please, can you sort names alphabetically?

[kadel]

this is not me ;-)
it should be here.

[cdrage]

@kadel Done!