Introducing oneDAL roles for contributors and maintainers

[napetrov]

Description

This is initial version of MAINTAINERS.md that define roles and list certain individuals in those roles.

Feedback and recommendations are welcome

[napetrov]

@keeranroth @rakshithgb-fujitsu - please take a look on this. open for recommendations/suggestions

[keeranroth]

@napetrov thanks for the mention, and I'm happy to be down as a code owner for the RISC-V part of the code base, with the caveats listed below.

The wording is good, except I'm always hesitant about putting time commitments on roles, although it would be nice to show that some effort is expected here. In general, as long as a person is fulfilling their responsibilities, then the time commitment doesn't play too much of a role. Using me as an example, for the RISC-V part, I am happy to be down as a code owner, and will have a quick turnaround on code review. However, that won't take 25% of my time, for what is a relatively new and not yet widely used part of the oneDAL project. I can make fixes to broken pipelines, but turnaround might be on the order of a week or two, depending on other responsibilities. As RISC-V usage and contributions pick up, it might be good to come back to this and choose a more active member of the community as a code owner.

So, I suggest that the bullet point around the time requirement be taken out. For the code owners in RISC-V section, I'm happy to be listed, as long as the caveat mentioned above is acceptable. What do you think?

[rakshithgb-fujitsu]

I agree with Keeran on this; as the oneDAL community expands, more individuals will naturally take on roles as code owners and maintainers. Implementing a time requirement isn’t a beneficial approach.

[napetrov]

@keeranroth @rakshithgb-fujitsu Thanks for feedback! cleaned up those lines on time commitments,

[keeranroth]

Looks good to me. Thanks @napetrov