http://geoserver.org/display/GEOS/GSIP+39+-+Promote+app-schema+to+extension
app-schema needs to be promoted to extension Real Soon Now (tm) if we want it in 2.0_beta2.
--
Ben Caradoc-Davies <Ben.Caradoc-Davies@anonymised.com>
Software Engineer, CSIRO Exploration and Mining
Australian Resources Research Centre
26 Dick Perry Ave, Kensington WA 6151, Australia
Indeed 2.0_beta2 is near (and thank you for putting application schema
in the short term roadmap - I noted it with Chris yesterday).
Quick question; does GSIP-39 just represent the completion of GSIP-31
or is a separate GSIP needed?
In terms of the proposal; can you also list a link to documentation
for the extension (I don't really mind what form it is in).
Cheers,
Jody
On Thu, Jul 9, 2009 at 12:59 PM, Ben
Caradoc-Davies<Ben.Caradoc-Davies@anonymised.com> wrote:
http://geoserver.org/display/GEOS/GSIP+39+-+Promote+app-schema+to+extension
app-schema needs to be promoted to extension Real Soon Now (tm) if we
want it in 2.0_beta2.--
Ben Caradoc-Davies <Ben.Caradoc-Davies@anonymised.com>
Software Engineer, CSIRO Exploration and Mining
Australian Resources Research Centre
26 Dick Perry Ave, Kensington WA 6151, Australia------------------------------------------------------------------------------
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
Ben Caradoc-Davies wrote:
http://geoserver.org/display/GEOS/GSIP+39+-+Promote+app-schema+to+extension
app-schema needs to be promoted to extension Real Soon Now (tm) if we want it in 2.0_beta2.
There has been an ongoing discussion between the AuScope and OpenGeo crews about including app-schema in GeoServer 2.0_beta2 (now scheduled for Monday). The idea is that app-schema, which consists of one GeoTools artifact and some unit tests (only) in GeoServer, is best distributed as a GeoServer extension. This means that it should be promoted from community module to extension. There was in-principle support for this, but because of the thin nature of app-schema (the implementation is all in GeoTools), we neglected to discuss this on the list or follow the community procedure. The proposal aims to remedy this oversight.
--
Ben Caradoc-Davies <Ben.Caradoc-Davies@anonymised.com>
Software Engineer, CSIRO Exploration and Mining
Australian Resources Research Centre
26 Dick Perry Ave, Kensington WA 6151, Australia
Jody Garnett wrote:
Quick question; does GSIP-39 just represent the completion of GSIP-31
or is a separate GSIP needed?
It needs a separate GSIP for promotion of a community module; GSIP 31 was for refactoring of core code, and independent of app-schema. The release of 2.0 will complete GSIP 31 (completion requires release).
In terms of the proposal; can you also list a link to documentation
for the extension (I don't really mind what form it is in).
Done.
--
Ben Caradoc-Davies <Ben.Caradoc-Davies@anonymised.com>
Software Engineer, CSIRO Exploration and Mining
Australian Resources Research Centre
26 Dick Perry Ave, Kensington WA 6151, Australia
Hi Ben,
Thanks for providing the background. Hopefully this is the first step in the right direction for getting AuScope to start coordinating their milestone releases with the main GeoServer road map. Given the release date is this Monday showing up a couple days before hand with a proposal is less than ideal, but a start 
You do have an opportunity to negotiate release dates by taking part in the weekly road map discussion. I want to stress that the whole point of this discussion is to have people step up and make sure their interests are reflected in the short term road map.
There are also no jira issues that reflect anything app-schema related on the roadmap for beta2.
So if sticking strictly to the road map process app-schema would not make it into this release. I suggest you take part in the road map update and try to negotiate the release date. I for one would be fine with pushing it back if it meant app-schema is included. You should also make sure you have jira items on the road map.
-Justin
Ben Caradoc-Davies wrote:
Ben Caradoc-Davies wrote:
http://geoserver.org/display/GEOS/GSIP+39+-+Promote+app-schema+to+extension
app-schema needs to be promoted to extension Real Soon Now (tm) if we want it in 2.0_beta2.
There has been an ongoing discussion between the AuScope and OpenGeo crews about including app-schema in GeoServer 2.0_beta2 (now scheduled for Monday). The idea is that app-schema, which consists of one GeoTools artifact and some unit tests (only) in GeoServer, is best distributed as a GeoServer extension. This means that it should be promoted from community module to extension. There was in-principle support for this, but because of the thin nature of app-schema (the implementation is all in GeoTools), we neglected to discuss this on the list or follow the community procedure. The proposal aims to remedy this oversight.
--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
Justin Deoliveira wrote:
Given the release date is this Monday showing up a couple days before hand with a proposal is less than ideal, but a start
Well, let's get voting and get it done.
You do have an opportunity to negotiate release dates by taking part in the weekly road map discussion.
These are held at 00:00 or 01:00 my local time. I cannot attend. It would be useful if discussions on the geoserver-devel mailing list were taken into consideration by those who are able to attend.
I want to stress that the whole point of this discussion is to have people step up and make sure their interests are reflected in the short term road map.
A collection of Jira dumps is pretty unreadable.
There are also no jira issues that reflect anything app-schema related on the roadmap for beta2.
I did not understand that one was required. I have added one. It took several attempts to get it to show up. Hint: only fix version matters.
So if sticking strictly to the road map process app-schema would not make it into this release. I suggest you take part in the road map update and try to negotiate the release date. I for one would be fine with pushing it back if it meant app-schema is included. You should also make sure you have jira items on the road map.
App-schema, and community schemas before it, has been on the 2.0 roadmap for ages:
http://geoserver.org/display/GEOS/Roadmap+Ideas
We also agreed to include it in 2.0_beta2.
Part of the problem is that all of app-schema main is in GeoTools, so any issues will not show up in any GeoServer Jira plugin. Working around this is very cumbersome.
--
Ben Caradoc-Davies <Ben.Caradoc-Davies@anonymised.com>
Software Engineer, CSIRO Exploration and Mining
Australian Resources Research Centre
26 Dick Perry Ave, Kensington WA 6151, Australia
Ben Caradoc-Davies wrote:
Justin Deoliveira wrote:
Given the release date is this Monday showing up a couple days before hand with a proposal is less than ideal, but a start
Well, let's get voting and get it done.
You do have an opportunity to negotiate release dates by taking part in the weekly road map discussion.
These are held at 00:00 or 01:00 my local time. I cannot attend. It would be useful if discussions on the geoserver-devel mailing list were taken into consideration by those who are able to attend.
Well we recently moved the planning to the mailing list, partly for this exact purpose. Simply taking into account recent mailing list discussion would be a bit to ad hoc. We need a way to tell who is working on what or what gets into releases becomes arbitrary.
I want to stress that the whole point of this discussion is to have people step up and make sure their interests are reflected in the short term road map.
A collection of Jira dumps is pretty unreadable.
There are also no jira issues that reflect anything app-schema related on the roadmap for beta2.
I did not understand that one was required. I have added one. It took several attempts to get it to show up. Hint: only fix version matters.
So if sticking strictly to the road map process app-schema would not make it into this release. I suggest you take part in the road map update and try to negotiate the release date. I for one would be fine with pushing it back if it meant app-schema is included. You should also make sure you have jira items on the road map.
App-schema, and community schemas before it, has been on the 2.0 roadmap for ages:
http://geoserver.org/display/GEOS/Roadmap+IdeasWe also agreed to include it in 2.0_beta2.
Part of the problem is that all of app-schema main is in GeoTools, so any issues will not show up in any GeoServer Jira plugin. Working around this is very cumbersome.
I am not sure what to say Ben, we have been following this process for months now, and I have stressed to you many times how crucial it is for your group to take part in that process.
--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
I am not sure what to say Ben, we have been following this process for months now, and I have stressed to you many times how crucial it is for your group to take part in that process.
But to be fair, this should be better documented. I am going to make it a top priority to do up a "community process" doc so we can try to minimize communication break downs such as this.
--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
In terms of the proposal; can you also list a link to documentation
for the extension (I don't really mind what form it is in).Done.
Thanks Ben; I have added my vote to the GSIP page. It looks like
Justin is helping you hold up the release train for this much
anticipated feature.
Jody
Justin Deoliveira wrote:
I am not sure what to say Ben, we have been following this process for months now, and I have stressed to you many times how crucial it is for your group to take part in that process.
But to be fair, this should be better documented. I am going to make it a top priority to do up a "community process" doc so we can try to minimize communication break downs such as this.
I have been following the community modules guide as well as I can:
http://geoserver.org/display/GEOS/GSIP+22+-+Community+Modules
Perhaps some mention here of how to get into a release?
--
Ben Caradoc-Davies <Ben.Caradoc-Davies@anonymised.com>
Software Engineer, CSIRO Exploration and Mining
Australian Resources Research Centre
26 Dick Perry Ave, Kensington WA 6151, Australia