I like the latter cause it is so Hadley-esque (i'd go with the mapvizier pronunciation). That sad, mapvizier has a nice ring to it and most will pronounce it correctly.
So all of that said, why don't we stick with the latter.
At this point I think we should rename the package and perhaps move it to the @kippdata repo. I think we'd simply fork this branch to that repo and then anyone developing should start a new remote directory and clone from the @kippdata version. Put another way, we freeze development on this repo, fork it to @kippdata, and continue development from that fork by individuals forking from there.
mapvizrormapvizierI like the latter cause it is so Hadley-esque (i'd go with the mapvizier pronunciation). That sad, mapvizier has a nice ring to it and most will pronounce it correctly.
So all of that said, why don't we stick with the latter.
At this point I think we should rename the package and perhaps move it to the @kippdata repo. I think we'd simply fork this branch to that repo and then anyone developing should start a new remote directory and clone from the @kippdata version. Put another way, we freeze development on this repo, fork it to @kippdata, and continue development from that fork by individuals forking from there.