[Maintenance] Identify roles and responsibilities for dedicated tasks

[xames3]

• this issue might be worked upon in future patches with more dedicated contributors but as of now, below are the expectations for closing this issue:

  • setting up policies for code ownership. this can be done using the CODEOWNER file. we need to address the readiness of the contributors in handling respective files or blobs. for starters, the file can have the admins or maintainers as the code owners for all the files but later branch out into respective patterns-matches. for instance, all the translation files can be addressed or marked for ownership under the bilingual or multilingual contributors. this will allow them to review certain commits and issues directly without setting them as a dedicated approver. another example of this feature would be, marking @xames3 as owner for any and all Sphinx related configuration files or GitHub workflows, etc. one good use case would be to have the members from @ciesin-geospatial development team for relevant content about glossary or @kyttmacmanus for high-level TOPST/NASA/Open Science related details.

although, the issue seems relatively straightforward, but we need to discuss about the ownership and dedicated contributors and their respective roles as reviewers internally in the upcoming meetings.