add CODEOWNERS file for blog content

[bacongobbler]

It was noted by some of the project maintainers that having permissions to edit a website and having permissions to curate the content of the blog should be differentiated.

Github has a concept called a CODEOWNERS file, and that workflow has worked out well for the Helm Charts team. Perhaps the blog directory should have a CODEOWNERS file with the core maintainers on there.

[bridgetkromhout]

Do we want to follow up at this point with trying to define in CODEOWNERS the people who are allowed to edit the website vs the blog? Or do we think the current LGTM process is covering it? or some other option I haven't outlined? Thanks.

[bacongobbler]

I believe the conversation had to do with:

• who can approve/merge certain translations
• who can approve/merge changes to the site theme
• who can approve/merge blog posts
• who can approve/merge changes to the documentation

Maintainers of the helm-www project may be able to fulfill only a few of those roles. For example, I cannot review changes to the Russian locale, as I do not speak Russian.

The current LGTM process is covering this fine at the moment. But this is about how we can delegate roles to new maintainers (and possibly encourage others to help join in).

I've received feedback from prospective maintainers coming to helm/helm that maintaining the entire project seems like a daunting task. I thought splitting into separate, more specialized roles might encourage new maintainers to take on smaller roles. We might adopt a similar system for helm/helm so that we have maintainers responsible for specific packages (pkg/registry and pkg/downloader vs. pkg/kube comes to mind).

[angellk]

closing as stale, please reopen if this is something you'd still like to see @bacongobbler