Hey, so this is my concern wrt community modules: IMHO the whole concept of having community modules in the mainstream svn repo is obsolete.
I don't quite remember if we already discussed it, but for how long are we going to keep tied to svn? Moving to git is a natural step forward IMHO and it'd enable anyone to develop their modules on their own repos and ask to pull from it when is a mature enough state. I'm seeing this kind of collaboration work great for the GeoNode project and I'm looking forward for GeoServer to benefit from it too. Second concern perhaps of a more immediate solution is there seems to ~43 folders under community/ some of them look like empty (control-flow, performanceChecker), some may be obsolete, so we might want to go through some sort of clean up round? may be move the ones that are not really used to a top folder next to /data, /src and /docs, maybe to /tutorials, /spike, or something like that, as needed? well, on a fresh checkout of src/, community/ seems to be roughly 15MB out of ~115MB total, so not the biggest offender size wise, but still... Cheers, Gabriel -- Gabriel Roldan [email protected] Expert service straight from the developers ------------------------------------------------------------------------------ Achieve unprecedented app performance and reliability What every C/C++ and Fortran developer should know. Learn how Intel has extended the reach of its next-generation tools to help boost performance applications - inlcuding clusters. http://p.sf.net/sfu/intel-dev2devmay _______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
