Hi list,
after the last conversations with Justin on the ML, we have thought to setup a temp restconfig module in community section which contains some fixes and workarounds we need for a shortcoming deadline.
This is a temp module which aims to re-enable some of the features which were available on the old RESTConfig module (that will be removed being no more used) while waiting for an improved catalog also to avoid changing the APIs.
Is “rest-config” a valuable name? (Everyone knows the official restconfig is on extension). Or should I set a totally different name for it?
Please, let me know when I can do this.
Cheers,
Daniele
–
Eng. Daniele Romagnoli
Software Engineer
GeoSolutions S.A.S.
Via Carignoni 51
55041 Camaiore (LU)
Italy
phone: +39 0584983027
fax: +39 0584983027
mob: +39 328 0559267
http://www.geo-solutions.it
hi Daniele,
+1 on creating the new module as per our discussion last week. And again I ask that you open jira issues when you find problems with the code so I can fix them in the regular version.
As for what to name it, i might avoid using restconfig since it is already used. Something like restcofnig_temp maybe?
Aside: I have been playing with mercurial and distributed version control. It is really too bad we don't have a repo set up, it would handle these sorts of things trivially.
-Justin
Daniele Romagnoli wrote:
Hi list,
after the last conversations with Justin on the ML, we have thought to setup a temp restconfig module in community section which contains some fixes and workarounds we need for a shortcoming deadline.
This is a temp module which aims to re-enable some of the features which were available on the old RESTConfig module (that will be removed being no more used) while waiting for an improved catalog also to avoid changing the APIs.
Is "rest-config" a valuable name? (Everyone knows the official restconfig is on extension). Or should I set a totally different name for it?
Please, let me know when I can do this.
Cheers,
Daniele
--
-------------------------------------------------------
Eng. Daniele Romagnoli
Software Engineer
GeoSolutions S.A.S.
Via Carignoni 51
55041 Camaiore (LU)
Italy
phone: +39 0584983027
fax: +39 0584983027
mob: +39 328 0559267
http://www.geo-solutions.it
-------------------------------------------------------
------------------------------------------------------------------------
------------------------------------------------------------------------------
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image processing features enabled. http://p.sf.net/sfu/kodak-com
------------------------------------------------------------------------
_______________________________________________
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.
Justin Deoliveira ha scritto:
hi Daniele,
+1 on creating the new module as per our discussion last week. And again I ask that you open jira issues when you find problems with the code so I can fix them in the regular version.
As for what to name it, i might avoid using restconfig since it is already used. Something like restcofnig_temp maybe?
Aside: I have been playing with mercurial and distributed version control. It is really too bad we don't have a repo set up, it would handle these sorts of things trivially.
What about using Bazaar? It seems to have all it needs to work
against a central svn server in a distributed manner.
Downside, last time I checked it did not support svn externals, so we'd
have to get rid of (most of) them from our codebase.
Cheers
Andrea
--
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.
Andrea Aime wrote:
Justin Deoliveira ha scritto:
hi Daniele,
+1 on creating the new module as per our discussion last week. And again I ask that you open jira issues when you find problems with the code so I can fix them in the regular version.
As for what to name it, i might avoid using restconfig since it is already used. Something like restcofnig_temp maybe?
Aside: I have been playing with mercurial and distributed version control. It is really too bad we don't have a repo set up, it would handle these sorts of things trivially.
What about using Bazaar? It seems to have all it needs to work
against a central svn server in a distributed manner.
Downside, last time I checked it did not support svn externals, so we'd
have to get rid of (most of) them from our codebase.
Have not tried it out at all. I have started playing with using a distributed versioning tool locally and so far I have only covered git and mercurial.
They all seem to have tools which can work directly with a subversion repository. But for now I am more taking a manual approach, for fear of screwing up the svn repo. Basically keeping a clean merc repo which is also an svn repo, and cloning+branching it anytime I want to work on something, pulling the patches back when I am done on that branch. Working quite well.
Cheers
Andrea
--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
Hi,
On Mon, May 11, 2009 at 2:51 PM, Justin Deoliveira <jdeolive@anonymised.com> wrote:
hi Daniele,
+1 on creating the new module as per our discussion last week. And again I ask that you open jira issues when you find problems with the code so I can fix them in the regular version.
Off course
As for what to name it, i might avoid using restconfig since it is already used.
Indeed, I have added a dash (rest-config), anyway restconfig_temp sounds good.
Something like restcofnig_temp maybe?
Aside: I have been playing with mercurial and distributed version control. It is really too bad we don’t have a repo set up, it would handle these sorts of things trivially.
-Justin
Daniele Romagnoli wrote:
Hi list,
after the last conversations with Justin on the ML, we have thought to setup a temp restconfig module in community section which contains some fixes and workarounds we need for a shortcoming deadline.
This is a temp module which aims to re-enable some of the features which were available on the old RESTConfig module (that will be removed being no more used) while waiting for an improved catalog also to avoid changing the APIs.
Is “rest-config” a valuable name? (Everyone knows the official restconfig is on extension). Or should I set a totally different name for it?
Please, let me know when I can do this.
Cheers,
Daniele
–
Eng. Daniele Romagnoli
Software Engineer
GeoSolutions S.A.S.
Via Carignoni 51
55041 Camaiore (LU)
Italy
phone: +39 0584983027
fax: +39 0584983027
mob: +39 328 0559267
http://www.geo-solutions.it
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there’s a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you’ll get full speed at 300 dpi even with all image processing features enabled. http://p.sf.net/sfu/kodak-com
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.
–
Eng. Daniele Romagnoli
Software Engineer
GeoSolutions S.A.S.
Via Carignoni 51
55041 Camaiore (LU)
Italy
phone: +39 0584983027
fax: +39 0584983027
mob: +39 328 0559267
http://www.geo-solutions.it