My apologies if I've brought this up to this list (I searched, and it
looks like I've only brought it up on other listserv), but I'm wondering
if git (or something like it) is the best way for managing crazy changes
to a kmz file.
These projects I'm working on nowadays tend to be heavily GIS-based, and
Google Earth kmz files tend to be what everyone standardizes on for
planning out wireless links.
One problem with all of this is that changes are getting crazy. In
theory, we all work on the same set of requirements (usually a bigass
RFP), but then when the project rolls forward, someone starts plotting
the various spots that need, say, cameras. Then another person (e.g.
me) starts planning out the wireless for that layer. Then another
person (e.g. someone from a microwave PtP company) starts planning out
the big microwave links.
Then the camera guy founds out that he read the RFP wrong and once he
sends out an updated version of his document, it's not the updated
version that any of us used along the way.
This is quickly becoming really frustrating, particularly on giant
projects where there are a dozen cooks in the kitchen, and that mix of
people and vendors is always quickly changing from project to project.
I'm wondering if some sort of quick document control thing I can throw
up on our webserver (or create one myself) would be best here.
Particularly something that allows people to more formally "check out" a
document before committing it back into the stash.
Any ideas?
