@simeonnedkov @ppkrauss I really like the idea of having many more Data Package registries on GitHub, but I’m not sold yet on having lots of country-specific ones. I’m sure it might be relatively easy to find yourself in the situation where you have a dataset that you need and are willing and able to maintain, but may not fit in either datasets-nl or datasets, which would be a real problem 
. That being said datasets-nl seem like a fine place to start testing out the idea for projects in the Netherlands. We can help promote new datasets as you add them and see if other people jump on board. It might be worth coming up with some guidelines for contribution.
@ppkrauss You said:
In the case of country-codes, and supposing that “join CSV files” is not a problem for users, the federated community can help central /datasets to maintain a new country-codes-names.csv file with all official_name_X columns: this solution seems better than intersection in /datasets-Y projects.
I particularly like this idea. I think it counts as an generally useful dataset to add to /datasets/. Perhaps you could create a new issue for it: Sign in to GitHub · GitHub
@ppkrauss You also said:
Brazil now have two simple and util datasets to add at this proposed “country-specific data package register”,
- GitHub - okfn-brasil/datasets-br-cbo: Dataset for CBO - Classificação Brasileira de Ocupações (Brazilian Classification of Occupations).
- ISO-3166-2-BR-history
As I said above, I’m neutral as to whether you should manage these on /datasets-br/ or /okfn-brasil/, but I do think they both seem important and generally useful! Given that you are managing the ISO-3166-2-BR dataset through Google Sheets, you might be interested in generating a Data Package directly from there. See this post for some background info on it: