Open Location Code is a library to generate short codes, called "plus codes", that can be used as digital addresses where street addresses don't exist.
Code is deployed to multiple external package repositories and new ones are requested from time to time. This is a significant amount of work to manage and I'm interested in people's thoughts of how we can do this.
Currently many of the entries in package repositories are owned by people who did a deployment once, haven't necessarily kept it up to date, and who I don't know personally (so I can't poke them).
I can see either this all becoming my problem (but I have limited time), or we keep it distributed (but then need a way to stay coordinated).
Code is deployed to multiple external package repositories and new ones are requested from time to time. This is a significant amount of work to manage and I'm interested in people's thoughts of how we can do this.
Currently many of the entries in package repositories are owned by people who did a deployment once, haven't necessarily kept it up to date, and who I don't know personally (so I can't poke them).
I can see either this all becoming my problem (but I have limited time), or we keep it distributed (but then need a way to stay coordinated).
Ideas?