I also am getting pull requests. I think for many casual uses (documentation
fixes and so on) that a pull request is fine. It amounts to a light code review
by another set of eyes.
For anything more significant (fixes, new features, etc…) JIRA is really
useful; and we can consider mentioning a
+1
:)
==
Our support, Your Success! Visit http://opensdi.geo-solutions.it for more
information.
==
Ing. Alessio Fabiani
@alfa7691
Founder/Technical Lead
GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 962313
mob: +39 331
On 11/07/12 15:52, Alessio Fabiani wrote:
+1
:)
Ha ha!
(For the benefit of the list, Alessio *has* attended meetings, and this
vote is *not* his only activity, although it would be even funnier if it
were.)
--
Ben Caradoc-Davies ben.caradoc-dav...@csiro.au
Software Engineer
CSIRO Earth
On Mon, Jul 9, 2012 at 8:01 PM, Juan Marín Otero
juan.marin.ot...@gmail.com wrote:
All,
With the migration to Git and creation of branch 2.2.x done, I'd like to
gather feedback on a proposed enhancement to the REST API that I worked on a
few weeks ago, which adds configuration options for
Sorry, added the links to the references on the usage of POST and PUT
in the wrong place, they
were meant to follow my statement about the usage of POST and PUT, that is:
As far as I know PUT can be
On Wed, Jul 11, 2012 at 1:49 AM, Gabriel Roldan grol...@opengeo.org wrote:
The problem is not the immutability of the object itself, but the one of its
parameters. During simplification one might notice one of the parameters
is a constant and replace it with it, but if the function itself has
I agree with Sean, er i mean Andrea :P that simply using PUT for these
types of services makes sense. The geoserver restconfig api uses the
convention (and i believe this is consistent with the links Andrea posted)
that POST is generally only used when POSTING to a collection in order to
create a
Given that the pull request was not summarily merged, I guess this counts
as more significant. I have created a JIRA issue:
http://jira.codehaus.org/browse/GEOT-4199
--
David Winslow
OpenGeo - http://opengeo.org/
On Wed, Jul 11, 2012 at 2:50 AM, Jody Garnett jody.garn...@gmail.comwrote:
I
On Tue, Jul 10, 2012 at 9:44 PM, Justin Deoliveira jdeol...@opengeo.orgwrote:
Anyway, I ended up more time than seems necessary because of some
exceptions being silently swallowed in GeoTools code. I issued a pull
request against the new Github repo:
On Wed, Jul 11, 2012 at 10:40 AM, Andrea Aime
andrea.a...@geo-solutions.it wrote:
On Wed, Jul 11, 2012 at 1:49 AM, Gabriel Roldan grol...@opengeo.org wrote:
The problem is not the immutability of the object itself, but the one of its
parameters. During simplification one might notice one of
I am not sure about putting such an emphasis on the meetings as required to
show the necessary participation to be part of the PSC. Given we are
radically spread out across the globe it is not just doable for a lot of
people, but that doesn't mean they aren't active.
To me the biggest thing in
I second Justin here, although honestly my judgment is a bit biased
by the fact that attending meetings si going to be difficult for me in
some periods (like now).
While I am one of those who pushed to have regular meetings I believe
we should be careful on putting too much emphasis on them for
Hey Justin,
On Mon, Jul 9, 2012 at 10:44 PM, Justin Deoliveira jdeol...@opengeo.orgwrote:
Hey Juan,
All in all this proposal looks great. Nice work man.
Thanks a lot for taking a look at it
One thing though is about the ServiceInfo object representations. I would
expect them to match
Andrea / Justin,
Thanks for the feedback, I actually went back and forth with this a bit but
ended up doing it the way the patch reflects and I don't even remember my
reasoning but yours is sound, this should be an easy change. Am I reading
correctly in that you consider that POST should not be
On Wed, Jul 11, 2012 at 8:37 PM, Juan Marín Otero
juan.marin.ot...@gmail.com wrote:
Andrea / Justin,
Thanks for the feedback, I actually went back and forth with this a bit
but ended up doing it the way the patch reflects and I don't even remember
my reasoning but yours is sound, this
On Wed, Jul 11, 2012 at 2:03 PM, Andrea Aime
andrea.a...@geo-solutions.itwrote:
On Wed, Jul 11, 2012 at 8:37 PM, Juan Marín Otero
juan.marin.ot...@gmail.com wrote:
Andrea / Justin,
Thanks for the feedback, I actually went back and forth with this a bit
but ended up doing it the way the
Morning David:
I got a question that keeps me from just hitting the merge option on github
(which is the magic of pull requests).
Do we have an easy way to apply the fix to the older branches? Or is the
author expecting the change to be applied to the older branches.
take 1:
Hit accept
As long as we are talking REST; I got to talk to a few GeoServer users over
coffee and they indicated that the REST api was not complete with respect to
letting them back up and restore a configuration outside of their app.
Apparently for managing styles they could successfully remove a style,
+1. Attending meetings is great if you can, but reviewing and voting on
proposals in both necessary and sufficient to be on the PSC.
I was thinking of people with family obligations when I wrote: It is
not mandatory to attend meetings, but it is mandatory to be active;
those who have other
Separate thread please.
On Wed, Jul 11, 2012 at 8:01 PM, Jody Garnett jody.garn...@gmail.comwrote:
As long as we are talking REST; I got to talk to a few GeoServer users
over coffee and they indicated that the REST api was not complete with
respect to letting them back up and restore a
See http://hudson.opengeo.org/hudson/job/cite-wms-1.3/507/
--
[...truncated 1893 lines...]
[exec]Assertion: For style Forests, when the STYLES
parameter is set to that style name, the MIME type of the response is valid.
[exec]
21 matches
Mail list logo
