I am slightly ++ on the latter but mostly just looking for explicitness in the proposal.
Another comment: my first thought would have been to choose briefer names for the directories, like
geoserver/{src,docs,data}
Again, I don't have a strong opinion here but am just throwing it out there; short URLs are nice but this would be a pretty marginal difference.
-David Winslow
Justin Deoliveira wrote:
Hi all,
I whipped up a quick little GSIP for the svn reorg discussed last week:
Good point, that is confusing. Yes, i am proposing the latter. I have edited the proposal to make it clearer.
I am slightly ++ on the latter but mostly just looking for explicitness in the proposal.
Another comment: my first thought would have been to choose briefer names for the directories, like
geoserver/{src,docs,data}
Another good point. The reason for using the full name was to remain consistent with the "configuration" directory (from my original email last week about the svn reorg). ie being consistent by using {configuration,source,documentation} rather than {config,src,doc}.
But as the proposal indicates we have decided to abandon "configuration" so that is not really valid anymore.
So I am +1 on the shorter names but I won't update the proposal yet until others have a chance to weigh in with an opinion.
Again, I don't have a strong opinion here but am just throwing it out there; short URLs are nice but this would be a pretty marginal difference.
-David Winslow
Justin Deoliveira wrote:
Hi all,
I whipped up a quick little GSIP for the svn reorg discussed last week:
Another comment: my first thought would have been to choose briefer names for the directories, like
geoserver/{src,docs,data}
Another good point. The reason for using the full name was to remain consistent with the "configuration" directory (from my original email last week about the svn reorg). ie being consistent by using {configuration,source,documentation} rather than {config,src,doc}.
But as the proposal indicates we have decided to abandon "configuration" so that is not really valid anymore.
So I am +1 on the shorter names but I won't update the proposal yet until others have a chance to weigh in with an opinion.
I like shorter names better as well.
Cheers
Andrea
--
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.
On Mon, Nov 17, 2008 at 11:42 AM, Andrea Aime <aaime@anonymised.com> wrote:
Justin Deoliveira ha scritto:
<snip>
Another comment: my first thought would have been to choose briefer
names for the directories, like
geoserver/{src,docs,data}
Another good point. The reason for using the full name was to remain
consistent with the "configuration" directory (from my original email
last week about the svn reorg). ie being consistent by using
{configuration,source,documentation} rather than {config,src,doc}.
But as the proposal indicates we have decided to abandon "configuration"
so that is not really valid anymore.
So I am +1 on the shorter names but I won't update the proposal yet
until others have a chance to weigh in with an opinion.
I like shorter names better as well.
Cheers
Andrea
--
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
I like where this is going. Thanks, Justin, for putting this together. Just out of curiosity, why is "data" outside of "src"? I guess, if I understand the thrust of what the directory is for if it's used when building geoserver, shouldn't it be inside "src"? I recognize that it's not Java code, but in my (non-programmer) head I see things breaking down as "that which is used to build GeoServer" and "that which is used to describe GeoServer". I trust everyone's judgment here, just wanted to throw that in...
On Mon, Nov 17, 2008 at 11:42 AM, Andrea Aime <aaime@anonymised.com> wrote:
Justin Deoliveira ha scritto:
<snip>
Another comment: my first thought would have been to choose briefer
names for the directories, like
geoserver/{src,docs,data}
Another good point. The reason for using the full name was to remain
consistent with the "configuration" directory (from my original email
last week about the svn reorg). ie being consistent by using
{configuration,source,documentation} rather than {config,src,doc}.
But as the proposal indicates we have decided to abandon "configuration"
so that is not really valid anymore.
So I am +1 on the shorter names but I won't update the proposal yet
until others have a chance to weigh in with an opinion.
I like shorter names better as well.
Cheers
Andrea
--
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
Actually the data directories used to be stored in the source tree, but a while back we decided to separate them out. However, in order to build the web module we actually do require one of the directories inside the source tree so we use the svn:externals trick to get around that.
-Justin
Mike Pumphrey wrote:
I like where this is going. Thanks, Justin, for putting this together. Just out of curiosity, why is "data" outside of "src"? I guess, if I understand the thrust of what the directory is for if it's used when building geoserver, shouldn't it be inside "src"? I recognize that it's not Java code, but in my (non-programmer) head I see things breaking down as "that which is used to build GeoServer" and "that which is used to describe GeoServer". I trust everyone's judgment here, just wanted to throw that in...
On Mon, Nov 17, 2008 at 11:42 AM, Andrea Aime <aaime@anonymised.com> wrote:
Justin Deoliveira ha scritto:
<snip>
Another comment: my first thought would have been to choose briefer
names for the directories, like
geoserver/{src,docs,data}
Another good point. The reason for using the full name was to remain
consistent with the "configuration" directory (from my original email
last week about the svn reorg). ie being consistent by using
{configuration,source,documentation} rather than {config,src,doc}.
But as the proposal indicates we have decided to abandon "configuration"
so that is not really valid anymore.
So I am +1 on the shorter names but I won't update the proposal yet
until others have a chance to weigh in with an opinion.
I like shorter names better as well.
Cheers
Andrea
--
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
Actually the data directories used to be stored in the source tree, but a while back we decided to separate them out. However, in order to build the web module we actually do require one of the directories inside the source tree so we use the svn:externals trick to get around that.
The rationale for moving them out was that if you're in a
low bandwith/shaky internet situation you're probably not
interested in having all the data dirs, and you can have
your code checkout work fine anyways thanks to svn:externals
pointing to the minimal data dir.
Granted, you cannot do a release, you cannot run CITE tests,
but very few people actually need to do the above.
Cheers
Andera
--
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.