Add elbehery to OWNERS

[Elbehery]

Reference:

• Bump Go to 1.23.10 #116 (comment)
• https://github.com/etcd-io/gofail/commits?author=elbehery

cc @ahrtr @ivanvc @jmhbnz

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: Elbehery
Once this PR has been reviewed and has the lgtm label, please assign ptabor for approval. For more information see the Code Review Process.

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

Needs approval from an approver in each of these files:

• OWNERS

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

[serathius]

Thanks for initiative, please read the etcd requirements for becoming a reviewer https://github.com/etcd-io/etcd/blob/main/Documentation/contributor-guide/community-membership.md#reviewers

[ahrtr]

@Elbehery as we discussed in the community meeting, please read the membership guide as mentioned in #116 (comment) (also mentioned above by @serathius )

For the gofail project/tool, AFAIK we don't have any new TODO features for now, so we don't have opportunity to evaluate the contributor's knowledge on the project by his/her work (i.e PRs). We will have to depend on the existing maintainer's judgement/evaluation. @Elbehery please read the design I provided in #116 (comment) and spend some time to under the internal mechanism of the project. I am happy to have 1:1 talk to evaluate your understanding on the project later. Please anyone let me know if you have better way to proceed.

For now, we have regular (weekly) dependencies bumping PRs and also golang version bumping PRs, we need maintainers/reviews to take care of them. We might have enhancement in future. We also need maintainers to respond to PRs/issues. We should encourage & help people to grow into an approver or reviewer role (being review first, and approver later).

So proposal to @Elbehery :

• Please ensure you have a deep understanding on the project
• Please help us to take care of the daily routine mentioned above.

[Elbehery]

Thanks for initiative, please read the etcd requirements for becoming a reviewer https://github.com/etcd-io/etcd/blob/main/Documentation/contributor-guide/community-membership.md#reviewers

Thanks for your review 🙏🏽 .. Will go through it in details 👍🏽

[Elbehery]

@Elbehery as we discussed in the community meeting, please read the membership guide as mentioned in #116 (comment) (also mentioned above by @serathius )

For the gofail project/tool, AFAIK we don't have any new TODO features for now, so we don't have opportunity to evaluate the contributor's knowledge on the project by his/her work (i.e PRs). We will have to depend on the existing maintainer's judgement/evaluation. @Elbehery please read the design I provided in #116 (comment) and spend some time to under the internal mechanism of the project. I am happy to have 1:1 talk to evaluate your understanding on the project later. Please anyone let me know if you have better way to proceed.

For now, we have regular (weekly) dependencies bumping PRs and also golang version bumping PRs, we need maintainers/reviews to take care of them. We might have enhancement in future. We also need maintainers to respond to PRs/issues. We should encourage & help people to grow into an approver or reviewer role (being review first, and approver later).

So proposal to @Elbehery :

* Please ensure you have a deep understanding on the project

* Please help us to take care of the daily routine mentioned above.

Thanks so much for your guidance, yes indeed, will go through the docs && code-base and will notify you once I am ready for the 1:1 discussion 🙏🏽 🙏🏽 🙏🏽