GbOpen

[leeberryman]

@DanRunfola curious if there is further explanation for the other datasets migrating to archived repos. We continue to be grateful for the amazing geoboundaries project. Is the gbOpen team ready to receive and process community contributions that have a clear and friendly license?

[DanRunfola]

We're working on 7.0 right now, and one part of it will be moving those two datasets into their own repositories - some legal reasons for separating it out. Should see some rapid movement soon.

We are very close to some improved submission tools as well for community contributions. Probably a few weeks out on that going live, unless we hit a big blocker with out implementations.

[leeberryman]

Thanks @DanRunfola.

[leeberryman]

@DanRunfola Its exciting to hear about the infrastructure enhancements that are enabling geoBoundaries to grow with 7.0 and k8s. Is the "the geoBoundaries contribution form" ready for public submissions?

[DanRunfola]

I would hold off just a little longer - I hope to go live with a fully functional version at the same time as our 7.0 launch.

…

On Mon, Apr 14, 2025 at 11:09 AM, Lee Berryman < ***@***.*** > wrote: @ DanRunfola ( https://github.com/DanRunfola ) Its exciting to hear about the infrastructure enhancements that are enabling geoBoundaries to grow with 7.0 and k8s. Is the "the geoBoundaries contribution form" ready for public submissions? — Reply to this email directly, view it on GitHub ( #4207 (reply in thread) ) , or unsubscribe ( https://github.com/notifications/unsubscribe-auth/AB4EPFMKLKX7D2ZVBE2NAAD2ZPFTDAVCNFSM6AAAAABX6EIDQCVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTEOBTGA3DSMI ). You are receiving this because you were mentioned. Message ID: <wmgeolab/geoBoundaries/repo-discussions/4207/comments/12830691 @ github. com>