Update OWNERS file with adding more approvers

[jstourac]

No description provided.

[harshad16]

I believe we should first confirm with everyone if they all want this responsibility
before including this PR.

/hold

[jstourac]

At the moment, there are only the people who are explicitly okay with being approvers for this repository. Please, let me know in case anymore changes are necessary! 🙂

[jiridanek]

/lgtm

[atheo89]

It's always good to have new ideas for improvements but I am not fully convinced yet.

I feel that each step of our process should have only the appropriate people, it doent's sound correct to have the same people in two consecutive steps. I mean obviously that could cause a degradation. The owners are the people that know the component almost from end to end, and they have a knowledge history of it.

I will bring an example,
Imagine to have a PR open from a contributor that re-introduce some things that are already covered by a feature long time ago, a member from our team likes this changes, imagine now another member that may review this pr and don't know the exact history assign also lgtm, so here, we can have two lgtm so any of these two people can allow a merge. In this scenario a merge could be fatal in our code base.

Also, even if the unit tests would be fully matured (which in our case they aren't) we could not just rely solely on them for approvals etc... So, maybe temporarily we will gain some time but i am afraid that we loose time later on chasing unexpected issues.

[jiridanek]

/test images

[harshad16]

/lgtm
/approve
/unhold

thanks for the PR 💯
Kudos to the team for having more approvers

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: caponetto, harshad16, paulovmr

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 [harshad16]

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

[jstourac]

Thank you, guys. I'll now backport the changes to other active branches in the upstream. Later in the downstream.

2024a seem to miss just this one commit, so lets do:

/cherrypick 2024a

[openshift-cherrypick-robot]

@jstourac: only opendatahub-io org members may request cherry picks. If you are already part of the org, make sure to change your membership to public. Otherwise you can still do the cherry-pick manually.

In response to this:

Thank you, guys. I'll now backport the changes to other active branches in the upstream. Later in the downstream.

2024a seem to miss just this one commit, so lets do:

/cherrypick 2024a

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[jstourac]

/cherrypick 2024a

[openshift-cherrypick-robot]

@jstourac: new pull request created: #623

In response to this:

/cherrypick 2024a

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.