Revert merging of the forked repos about kartotherian HOT 4 OPEN

On the other side this modules add node-mapnik dependency. And it would be better to break the hard dependency between Kartotherian and Mapnik.

from kartotherian.

I'm on the fence on this. You are right about upstream PRs and fork network. But that means that we will need a workaround on linking packages, which is nothing different from the past but makes monorepo pointless and add an extra layer on top development.

In case we decide to revert them, what will do next? Some kind of git submodules control?

from kartotherian.

@mateusbs17 you do bring a good point about submodules - even though I really dislike them, for some limited use like this they might be ok. Also, out of 20ish merged repos, having just the 3 as submodules might be ok... I'm also on the fence on this one, feels dirty either way :)

from kartotherian.

@nyurik we need to discuss it more deeply with the new changes I made for kartotherian to support node 10. I had to "fork" a few packages and it was extremely painful to track every node-mapnik dependency, without yarn workspaces it would be even harder.

from kartotherian.