Define "code owners" for datasets

[seabbs]

It would help with keeping the package up to date if contributors were assigned as code owners for a specific dataset, given some kind of credit (i.e @author in the documentation for that dataset) and assigned all code reviews/issues related to that dataset. What do people think?

Obviously it isn't like to work perfectly so core authors will probably have to step in fairly regularly but conceptually the idea appeals.

[RichardMN]

For me I'm quite aware that I'm largely working to do renovation of significant work that others did on the countries that I'm now refactoring. I'm tending to learn a little from the existing code with each country I work on, so I might be more comfortable with a "maintainer" label than author. Lithuania I'll clearly admit as mine; the others I think I can work to keep up to date.

It may be worth reaching out to some outside this immediate group who contributed some of these country chunks to ask how/whether they'd like to be involved/credited/blamed/nagged going forward.

[seabbs]

All good points. I will start pinging previous authors and look to find interested parties who may be keen to be responsible for data sets. I would hope this could happen organically but that might be asking a bit much.