Hello Chris
Le 30/07/12 19:50, Mattmann, Chris A (388J) a écrit :
OK to clarify, OSGeo will discuss this issue at their board meeting on 8/9?
Yes, I will keep this list informed.
Sure feel free to start threads here on sis-dev@ to discuss your thoughts.
I saw the 5 modules in the root directory of the SIS project. The first
thing that come to my though was that if the project growth to 1 million
lines of code (which could happen relatively fast), we are going to have
a lot of modules. What about a directory tree a little bit deeper, which
regroup modules by category? We could have the following categories
among others:
* utilities
* metadata
* referencing
* geometry
* feature
* coverage
* processing
* index
* display
* client
Each category is a directory, which contains one or many modules. For
example the "coverage" category could contains the following modules:
* sis-coverage
* sis-coverageio
* sis-coverageio-netcdf
I noticed that the current SIS code contains a "sis-core" module. What
about trying to put the content of "sis-core" in some more specific
modules? Otherwise I think that core may become very big if
"referencing", "geometry", "feature" etc. are considered as core...
Martin
