Cool, contribution to the docs would be much appreciated. Usually we prefer to have people submit patches before handing them out commit access.
http://docs.geoserver.org/1.7.x/developer/policies/comitting.html
So you could contribute the first round of doc updates via a patch, which we can review. We can then get you commit access to commit directly. Although even when you do have commit access the patch/review process is still very valuable, and one we try to stick to when we can.
-Justin
Ivan Grcic wrote:
Hi Justin,
I opened issues on those..and about documentation, yup im interested so if you could give me access would be nice. I already have some JAVA REST examples to put there 
Regards
On Tue, Jul 14, 2009 at 2:23 AM, Justin Deoliveira <jdeolive@anonymised.com <mailto:jdeolive@anonymised.com>> wrote:
Ivan Grcic wrote:
> Hi devs,
>
> just few things I noticed when I was working with REST for adding
> CoverageStore...
>
> Here I described how I refresh my Coverage:
>
http://www.nabble.com/Reload-Mosaic-CoverageStore-Coverage-after-shp-properties-file-has-been-modified-td23928766.html#a23998686
>
> Through REST I delete coverage store, coverage and then I PUT it
again.
> It works well, coverage information are updated, but thers one
> problem. The shape file doesnt get updated, until I reload geoserver
> store with admin/loadFromXML.do as described here:
>
http://geoserver.org/display/GEOSDOC/Alternative+for+reloading+the+Geoserver+catalog
>
> I guess it is because shape file is loaded into memory, and REST
> doesnt do neccessary things to update the shape file.
> Bug? Should I open issue for that?
So I guess this is specific to the mosaic plugin? Not sure exactly what
happens. I can try to look into it. Simone?
>
> By the way, I noticed that admin/loadFromXML.do doesnt require any
> permission, anybody can reload store?
> Bug or feature? Ill open an issue if somebody tells me to.
You are correct, indeed you do not, definitely a bug I would think,
although i have been wrong before. I would open an issue in the tracker
for it though.
>
> And just one little correction to REST docs: (dont have knowledge
with
> spynx still, so if someone can change it, tnx)
>
http://docs.geoserver.org/1.7.x/user/extensions/rest/rest-config-api.html
> - coverage store part: under extensions file[.<extension>] -> mosaic
> should be changed to imagemosaic
Good catch. Thanks. I just updated the docs. And if you are interested
in helping out with docs we can get you access.
>
> Regards,
--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
------------------------------------------------------------------------------
Enter the BlackBerry Developer Challenge
This is your chance to win up to $100,000 in prizes! For a limited time,
vendors submitting new applications to BlackBerry App World(TM) will
have
the opportunity to enter the BlackBerry Developer Challenge. See
full prize
details at: http://p.sf.net/sfu/Challenge
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
<mailto:Geoserver-devel@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
--
Ivan Grcic
------------------------------------------------------------------------
------------------------------------------------------------------------------
Enter the BlackBerry Developer Challenge This is your chance to win up to $100,000 in prizes! For a limited time, vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize details at: http://p.sf.net/sfu/Challenge
------------------------------------------------------------------------
_______________________________________________
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.