[gdal-dev] Code sprint Korea, reformat sources tree

[Dmitry Baryshnikov]

Hi everybody,

During the code sprint in FOSS4G 2015 (Korea, Seoul) I plan to start
refactoring Cmake for GDAL (everybody are welcome http://2015.foss4g.org/programme/code-sprint/).
This is good starting point to try release an idea to reformat source
tree (combine drivers on some principles - raster/vector/raster+vector).
I digging the mailing list, but didn't found discussion started by Even about this.
Also we have new type of drivers - network. So, how it'll be best to organise sources?
This can be not only drivers, but the whole source tree. How should the
ideal GDAL source tree looks like?

Also I plan:
1. Move all internal libraries (zlib, libtiff, libjpeg, etc.) to 
separate github repos to use CMake ExternalProject feature.
2. Remove any other building systems
3. Try CTest for testing

As for me the ideal structure should looks like:
+ apps
+ autotests
+ bindings
+ core
   + port
   + ogr
   + gcore
+ cmake
+ data
+ docs
   + doxygen
   + readme
+ drivers
   + raster
   + vector
   + network
   + combined
+ CMakeLists.txt
+ LICENSE

So, at the root of sources tree we will have only 8 folders and 2 files.

-- 
Best regards,
     Dmitry