OWNERS: sync repositories OWNERS_ALIASES from k/kubevirt to target repositories

[dhiller]

Since k/kubevirt currently is the source of truth when it comes to OWNERS_ALIASES sig_*_approvers and sig_*_reviewers we should sync other repositories OWNERS_ALIASES files in regular intervals, so as to keep them up to date.

Basically the repositories to sync with k/kubevirt are

• k/community
• k/user-guide
• k/enhancements (?)

Suggestion:

• create a postsubmit that kicks in after a change in k/kubevirt OWNERS_ALIASES gets merged and sync target aliases to the same state as in the source file

          How should we sync between changes here and in k/k?
          IOW, if someone is added as an approver for a SIG, would he need to also add himself to here in a different PR?
  

Originally posted by @iholder101 in kubevirt/community#360 (comment)

[dhiller]

/kind enhancement
/area automation

[kubevirt-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[kubevirt-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

/lifecycle rotten

[iholder101]

Very important IMO

/remove-lifecycle rotten

[kubevirt-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale