[Geoserver-devel] PSC call for vote: freemarker templates REST editing backport to 2.2.x

GeoServer GeoServer Developer
1

+1

-Jukka Rahkonen-

···

Lähettäjä: Andrea Aime [mailto:andrea.aime@anonymised.com]
Lähetetty: 28. marraskuuta 2012 12:51
Vastaanottaja: Geoserver-devel
Aihe: [Geoserver-devel] PSC call for vote: freemarker templates REST editing backport to 2.2.x

Hi,

the freemarker templates editing via REST is ready for backport, has pull requests

in line.

Its position regarding to the guidelines for new feature backports is borderline,

it’s indeed the implementation of a set of extension points without significant

changes to core, but it’s also new API for the users.

(see the “committing guidelines” section http://geoserver.org/display/GEOS/GSIP+77±+Time+boxed+release+model)

There has been significant discussion on the devel mailing list on the subject before the work

got committed on trunk:

http://osgeo-org.1560.n6.nabble.com/Freemarker-templates-editing-via-REST-td5005816.html

http://osgeo-org.1560.n6.nabble.com/Again-about-freemarker-template-rest-editing-td5014783.html

So I’m calling for a PSC vote just to be on the safe side.

Here is my +1

Cheers

Andrea

–

==

Our support, Your Success! Visit http://opensdi.geo-solutions.it for more information.

==

Ing. Andrea Aime

@geowolf

Technical Lead

GeoSolutions S.A.S.

Via Poggio alle Viti 1187

55054 Massarosa (LU)

Italy

phone: +39 0584 962313

fax: +39 0584 1660272

mob: +39 339 8844549

http://www.geo-solutions.it

http://twitter.com/geosolutions_it

2

+0

On Thu, Nov 29, 2012 at 8:10 AM, Rahkonen Jukka
<Jukka.Rahkonen@anonymised.com> wrote:

+1

-Jukka Rahkonen-

Lähettäjä: Andrea Aime [mailto:andrea.aime@anonymised.com]
Lähetetty: 28. marraskuuta 2012 12:51
Vastaanottaja: Geoserver-devel
Aihe: [Geoserver-devel] PSC call for vote: freemarker templates REST editing
backport to 2.2.x

Hi,

the freemarker templates editing via REST is ready for backport, has pull
requests

in line.

Its position regarding to the guidelines for new feature backports is
borderline,

it's indeed the implementation of a set of extension points without
significant

changes to core, but it's also new API for the users.

(see the "committing guidelines" section
http://geoserver.org/display/GEOS/GSIP+77+-+Time+boxed+release+model)

There has been significant discussion on the devel mailing list on the
subject before the work

got committed on trunk:

http://osgeo-org.1560.n6.nabble.com/Freemarker-templates-editing-via-REST-td5005816.html

http://osgeo-org.1560.n6.nabble.com/Again-about-freemarker-template-rest-editing-td5014783.html

So I'm calling for a PSC vote just to be on the safe side.

Here is my +1

Cheers

Andrea

--

==

Our support, Your Success! Visit http://opensdi.geo-solutions.it for more
information.

==

Ing. Andrea Aime

@geowolf

Technical Lead

GeoSolutions S.A.S.

Via Poggio alle Viti 1187

55054 Massarosa (LU)

Italy

phone: +39 0584 962313

fax: +39 0584 1660272

mob: +39 339 8844549

http://www.geo-solutions.it

http://twitter.com/geosolutions_it

-------------------------------------------------------

------------------------------------------------------------------------------
Keep yourself connected to Go Parallel:
VERIFY Test and improve your parallel project with help from experts
and peers. http://goparallel.sourceforge.net
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

--
Gabriel Roldan
OpenGeo - http://opengeo.org
Expert service straight from the developers.

3

+1
I make very little use of ftl template at the moment, instead using gml
and formatting in js. The principle reason for this is lack of an easy
way to edit templates - making changes directly within the file system
on the production server is a no-no. Changing a template means a long
process with the IT Preventers. This looks a very fine addition to the
api to me.

Notice: This email and any attachments are confidential. If received in error please destroy and immediately notify us. Do not copy or disclose the contents.