Add CODEOWNERS file for automatic PR review assignment

[SashankBhamidi]

Should we add a CODEOWNERS file to automatically assign reviewers to PRs?

Since we're manually assigning reviewers to every PR. GitHub's CODEOWNERS feature can handle this automatically based on which files get changed.

Benefits:

• PRs automatically get assigned to the right people
• Clearer sense of who owns what parts of the codebase
• Faster review process since the right eyes see it immediately

GitHub docs on CODEOWNERS: https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners

Here's a starting point I'm thinking:

# Default owners
* @niccokunzmann @stevepiercy

# Documentation
/docs/ @stevepiercy
*.rst @stevepiercy
*.md @stevepiercy
CONTRIBUTING.md @stevepiercy

# Core calendar logic
/src/icalendar/cal/ @niccokunzmann
/src/icalendar/attr.py @niccokunzmann
/src/icalendar/parser.py @niccokunzmann

# Tests
/src/icalendar/tests/ @niccokunzmann @SashankBhamidi

# CI and infrastructure
/.github/ @niccokunzmann @stevepiercy
/tox.ini @niccokunzmann
/pyproject.toml @niccokunzmann

# Release stuff
/CHANGES.rst @niccokunzmann @stevepiercy

Obviously this is just a proposal. Can be adjusted based on who actually wants to own what areas.

This just sets up smart defaults.

What do you guys think? Should we do this, and if so, does this structure make sense?

---

Closing criteria by @niccokunzmann

• invite collaborators
• document in the maintenance section
  • invitation when becoming a collaborator
  • invitation to review when you become maintainer

[SashankBhamidi]

Could create teams as well

[niccokunzmann]

That is nice, I would add

# Tests
/src/icalendar/fuzzing/ @ennamarie19 @niccokunzmann

@jacadzaca is there any part that you would like to be invited into reviewing automatically?

I like it explicitely, without teams.
And, I would like to add that this should be documented in the maintenance section:

• invite contributors to add themselved
• review when you get maintainer rights.

[stevepiercy]

I like this, with some revisions.

# Default owners
* @niccokunzmann

I'm not familiar with the code base to feel qualified to do a technical review.

# Documentation
/docs/ @stevepiercy
*.rst @stevepiercy
*.md @stevepiercy
CONTRIBUTING.md @stevepiercy

This is tricky because of docstrings in src, as well as GitHub workflows and other configuration files. Meh, might as well make me Default owner after all.

After that revelation, and after reviewing all the other configurations, I'd say let's omit all the specific configuration with one exception, leaving the default after all and one other:

# Default owners
* @niccokunzmann @stevepiercy

# Tests
/src/icalendar/tests/ @niccokunzmann @SashankBhamidi 

Let's see if there are other contributors who'd like to be assigned to review PRs.

[SashankBhamidi]

I don't mind reviewing changes to .GitHub/ , I'm so used to working with workflows and config

[niccokunzmann]

Could you create the PR with the best of your knowledge? Then we can add modifications to it and assign us. Then, it is clearer. At this point, everyone would try it :)

[niccokunzmann]

@abe-101 @angatha @ennamarie19 @geier @jacadzaca @stlaz, you are collaborators on icalendar and were not active for the last weeks. This is an invitation: adding yourself to to CODEOWNERS file will allow you to get a notification for code parts that you are interested in. If you feel like it, please add yourself. That can be done now or later.

[stlaz]

Feel free to remove me as a collaborator.

I haven't done any work in the area in years, and there's very little chance that I would find much time in the future. If I do, however, I'll try my best to make sure I can be considered a collaborator again 🙂