add CODEOWNERS file

[glimchb]

this helps to show who is reviewing code and mages notifications

[karlatec]

IMO Simon should be here as well

[karlatec]

and mages notifications

Typo "manages"?

[tomzawadzki]

I'm not sure what purpose does it serve to specify CODEOWNERS at this time. Currently only SPDK Core Maintainers have the write permission on the repository (only those can be in CODEOWNERS). Neither Karol or Simon do at this time.

Meanwhile this will be needed once more people are contributing, especially with workflows that they know best and/or own runners for them. Lets come back to this once the process for running the CI is much more clear and working.

[glimchb]

I'm not sure what purpose does it serve to specify CODEOWNERS at this time. Currently only SPDK Core Maintainers have the write permission on the repository (only those can be in CODEOWNERS). Neither Karol or Simon do at this time.

Meanwhile this will be needed once more people are contributing, especially with workflows that they know best and/or own runners for them. Lets come back to this once the process for running the CI is much more clear and working.

1. it adds visibility who is waiting on approvals
2. it adds notifications when PR is open
3. it allows to split owners per file
4. we can also create github team for core maintainers and add a team as owner

[mhae]

I would definitely want to be the ultimate decider to anything that's related to our self-hosted runner.
The other files are okay and we probably don't need to have codeowners. But for security reasons, I would not want anyone besides us to make changes to the yaml that uses our self-hosted runner. I

[mhae]

LGTM