[Geoserver-devel] GSIP#6 trunk on trunk

During todays meeting we started the voting process for GSIP#6:
- http://docs.codehaus.org/display/GEOS/GSIP+6+Track+GeoTools+trunk
- http://jira.codehaus.org/browse/GEOS-824

We did not have enough PSC members present to finish the job, and a nice email asking for a vote needs to go out to email anyways. As usual PSC members have a week ... starting now.

Aside:
- we have pursued GeoTools policy change as outlined in the above GSIP#6, if we are through discussion we can also chase that one through the process.

Jody

I'm with Andrea on wanting a GeoTools policy change too.

And why is the version for this 1.5? Shouldn't it be 1.6?

C

Jody Garnett wrote:

During todays meeting we started the voting process for GSIP#6:
- http://docs.codehaus.org/display/GEOS/GSIP+6+Track+GeoTools+trunk
- http://jira.codehaus.org/browse/GEOS-824

We did not have enough PSC members present to finish the job, and a nice email asking for a vote needs to go out to email anyways. As usual PSC members have a week ... starting now.

Aside:
- we have pursued GeoTools policy change as outlined in the above GSIP#6, if we are through discussion we can also chase that one through the process.

Jody

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

!DSPAM:1003,4588575438951665516417!

--
Chris Holmes
The Open Planning Project
http://topp.openplans.org

Chris Holmes wrote:

I'm with Andrea on wanting a GeoTools policy change too.

Andrea is going to set up something for GeoTools tomorrow, going to try "eating his own dog food" and doing the wiki plus jira routine.

And why is the version for this 1.5? Shouldn't it be 1.6?

No idea Chris, I am a bit lost on the current road map.

Cheers,
Jody

I actually just updated the roadmap. http://docs.codehaus.org/display/GEOS/Roadmap

Though it's not specific with versions, so might not help you much.

But 1.5.x is branched or will be branched soon, so it's not appropriate for 'trunk on trunk' to be 1.5 - the reason we want trunk on trunk is for GeoServer 1.6...

Chris

Jody Garnett wrote:

Chris Holmes wrote:

I'm with Andrea on wanting a GeoTools policy change too.

Andrea is going to set up something for GeoTools tomorrow, going to try "eating his own dog food" and doing the wiki plus jira routine.

And why is the version for this 1.5? Shouldn't it be 1.6?

No idea Chris, I am a bit lost on the current road map.

Cheers,
Jody

!DSPAM:1003,4588598441682223018498!

--
Chris Holmes
The Open Planning Project
http://topp.openplans.org

Thanks Chris, that is a good page.

I would like to see some of the other plans mentioned on that page if we can, for instance supporting a GridCoverage API is causing me grief in GeoTools land but I do not see it in listed, a similar tale for community schema. Even if we push these things to the Longer Term Project / Dreams list at the bottom of the page it would help.

I know (espeically after your feedback on the GeoTools 2.3 anouncement :wink: ) that this stuff should be expressed in user terms ...
Jody

I actually just updated the roadmap. http://docs.codehaus.org/display/GEOS/Roadmap

Though it's not specific with versions, so might not help you much.

But 1.5.x is branched or will be branched soon, so it's not appropriate for 'trunk on trunk' to be 1.5 - the reason we want trunk on trunk is for GeoServer 1.6...

Chris

Jody Garnett wrote:

Chris Holmes wrote:

I'm with Andrea on wanting a GeoTools policy change too.

Andrea is going to set up something for GeoTools tomorrow, going to try "eating his own dog food" and doing the wiki plus jira routine.

And why is the version for this 1.5? Shouldn't it be 1.6?

No idea Chris, I am a bit lost on the current road map.

Cheers,
Jody

!DSPAM:1003,4588598441682223018498!

Jody Garnett wrote:

Thanks Chris, that is a good page.

I would like to see some of the other plans mentioned on that page if we can, for instance supporting a GridCoverage API is causing me grief in GeoTools land but I do not see it in listed, a similar tale for community schema. Even if we push these things to the Longer Term Project / Dreams list at the bottom of the page it would help.

Longer Term Project /Dreams is definitely open for anyone to add to. I put my dreams there, if others have them they're welcome to. And indeed people are welcome to put things on the first categories if they're actually going to finish them in the time frames. I do not know the time frame for GridCoverage or nD support. Though actually, I do know nD is on GeoSolutions todo, as is ingestion engine, so I'll add them.

Community schema is on there for medium term. I didn't modify it much from the last time, if there are updates to go for it then go for it.

C

I know (espeically after your feedback on the GeoTools 2.3 anouncement :wink: ) that this stuff should be expressed in user terms ...
Jody

I actually just updated the roadmap. http://docs.codehaus.org/display/GEOS/Roadmap

Though it's not specific with versions, so might not help you much.

But 1.5.x is branched or will be branched soon, so it's not appropriate for 'trunk on trunk' to be 1.5 - the reason we want trunk on trunk is for GeoServer 1.6...

Chris

Jody Garnett wrote:

Chris Holmes wrote:

I'm with Andrea on wanting a GeoTools policy change too.

Andrea is going to set up something for GeoTools tomorrow, going to try "eating his own dog food" and doing the wiki plus jira routine.

And why is the version for this 1.5? Shouldn't it be 1.6?

No idea Chris, I am a bit lost on the current road map.

Cheers,
Jody

!DSPAM:1003,458863bc54381804284693!

--
Chris Holmes
The Open Planning Project
http://topp.openplans.org

Hi all guys,
sorry for not being enough present at this time … I’m really overloaded of work …

About our short term plans, in the next few months we will work fully on nD Coverages and Ingestion Engine.

GeoServer WCS won’t see any significant change until GeoTools nD coverages will be in a good development state, of course.
Basically the same for the Ingestion Engine stuff, we would like GeoServer to be as much as possible independent from it, touching just a bit the GeoServer code.

About WCS and WMS with rasters, I’ll continue working on GeoServer 1.5.x branch, porting forward the changes to the trunk when necessary, paying particoular attention to not breaking it, of course.
The 1.5.x branch needs to work against GeoTools 2.3.x for the moment. I don’t know exactly Simone’s plans for GeoTools code, so I’ll continue working with it for now.

About GSIP #6 voting, consider a +0 for me.

On 12/20/06, Chris Holmes <cholmes@anonymised.com> wrote:

Jody Garnett wrote:

Thanks Chris, that is a good page.

I would like to see some of the other plans mentioned on that page if we
can, for instance supporting a GridCoverage API is causing me grief in
GeoTools land but I do not see it in listed, a similar tale for
community schema. Even if we push these things to the Longer Term
Project / Dreams list at the bottom of the page it would help.

Longer Term Project /Dreams is definitely open for anyone to add to. I
put my dreams there, if others have them they’re welcome to. And indeed
people are welcome to put things on the first categories if they’re
actually going to finish them in the time frames. I do not know the
time frame for GridCoverage or nD support. Though actually, I do know
nD is on GeoSolutions todo, as is ingestion engine, so I’ll add them.

Community schema is on there for medium term. I didn’t modify it much
from the last time, if there are updates to go for it then go for it.

C

I know (espeically after your feedback on the GeoTools 2.3 anouncement
:wink: ) that this stuff should be expressed in user terms …
Jody

I actually just updated the roadmap.
http://docs.codehaus.org/display/GEOS/Roadmap

Though it’s not specific with versions, so might not help you much.

But 1.5.x is branched or will be branched soon, so it’s not
appropriate for ‘trunk on trunk’ to be 1.5 - the reason we want trunk
on trunk is for GeoServer 1.6…

Chris

Jody Garnett wrote:

Chris Holmes wrote:

I’m with Andrea on wanting a GeoTools policy change too.
Andrea is going to set up something for GeoTools tomorrow, going to
try “eating his own dog food” and doing the wiki plus jira routine.
And why is the version for this 1.5? Shouldn’t it be 1.6?
No idea Chris, I am a bit lost on the current road map.

Cheers,
Jody

!DSPAM:1003,458863bc54381804284693!


Chris Holmes
The Open Planning Project
http://topp.openplans.org


Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net 's Techsay panel and you’ll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV


Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Eng. Alessio Fabiani
Vice President/CTO GeoSolutions

http://www.geo-solutions.it


Hi Alessio & Simone:

Not sure if you are aware what is going on here - this GSIP#6 is me pushing back on GeoTools development. I do not want to see any work on nD coverages unless GeoServer is maintaining a branch tracking it. I know in the past you had to maintain two branches, even with these sometimes heroic measure from your team the delay getting 2.3 out the door was too great (and GeoServer is still a ways away from 1.5). We are looking at a repeat of this performance for GeoTools 2.4, ... so we are trying for policy changes in both projects.

Chris and Andrea have asked for a couple of things from GeoTools in return for setting up "trunk on trunk". So far the list is nightly builds and an API change policy.

If you can hunt down Simone for comment it would be helpful, we must attend to nD coverage plans with the same care currently being taken with Gabriel's proposed work.

Cheers,
Jody

Hi all guys,
sorry for not being enough present at this time ... I'm really overloaded of work ...
About our short term plans, in the next few months we will work fully on nD Coverages and Ingestion Engine.
GeoServer WCS won't see any significant change until GeoTools nD coverages will be in a good development state, of course.
Basically the same for the Ingestion Engine stuff, we would like GeoServer to be as much as possible independent from it, touching just a bit the GeoServer code.
About WCS and WMS with rasters, I'll continue working on GeoServer 1.5.x branch, porting forward the changes to the trunk when necessary, paying particoular attention to not breaking it, of course.
The 1.5.x branch needs to work against GeoTools 2.3.x for the moment. I don't know exactly Simone's plans for GeoTools code, so I'll continue working with it for now.
About GSIP #6 voting, consider a +0 for me.

On 12/20/06, *Chris Holmes* <cholmes@anonymised.com <mailto:cholmes@anonymised.com>> wrote:

    Jody Garnett wrote:
    > Thanks Chris, that is a good page.
    >
    > I would like to see some of the other plans mentioned on that
    page if we
    > can, for instance supporting a GridCoverage API is causing me
    grief in
    > GeoTools land but I do not see it in listed, a similar tale for
    > community schema. Even if we push these things to the Longer Term
    > Project / Dreams list at the bottom of the page it would help.

    Longer Term Project /Dreams is definitely open for anyone to add
    to. I
    put my dreams there, if others have them they're welcome to. And
    indeed
    people are welcome to put things on the first categories if they're
    actually going to finish them in the time frames. I do not know the
    time frame for GridCoverage or nD support. Though actually, I do
    know
    nD is on GeoSolutions todo, as is ingestion engine, so I'll add them.

    Community schema is on there for medium term. I didn't modify it much
    from the last time, if there are updates to go for it then go for it.

    C

    >
    > I know (espeically after your feedback on the GeoTools 2.3
    anouncement
    > :wink: ) that this stuff should be expressed in user terms ...
    > Jody
    >> I actually just updated the roadmap.
    >> http://docs.codehaus.org/display/GEOS/Roadmap
    >>
    >> Though it's not specific with versions, so might not help you much.
    >>
    >> But 1.5.x is branched or will be branched soon, so it's not
    >> appropriate for 'trunk on trunk' to be 1.5 - the reason we want
    trunk
    >> on trunk is for GeoServer 1.6...
    >>
    >> Chris
    >>
    >> Jody Garnett wrote:
    >>> Chris Holmes wrote:
    >>>> I'm with Andrea on wanting a GeoTools policy change too.
    >>> Andrea is going to set up something for GeoTools tomorrow,
    going to
    >>> try "eating his own dog food" and doing the wiki plus jira
    routine.
    >>>> And why is the version for this 1.5? Shouldn't it be 1.6?
    >>> No idea Chris, I am a bit lost on the current road map.
    >>>
    >>> Cheers,
    >>> Jody
    >>>
    >>
    >
    > !DSPAM:1003,458863bc54381804284693!
    >

    --
    Chris Holmes
    The Open Planning Project
    http://topp.openplans.org

    -------------------------------------------------------------------------
    Take Surveys. Earn Cash. Influence the Future of IT
    Join SourceForge.net 's Techsay panel and you'll get the chance to
    share your
    opinions on IT & business topics through brief surveys - and earn cash
    http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
    <http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV&gt;

    _______________________________________________
    Geoserver-devel mailing list
    Geoserver-devel@lists.sourceforge.net
    <mailto:Geoserver-devel@lists.sourceforge.net>
    https://lists.sourceforge.net/lists/listinfo/geoserver-devel

--
-------------------------------------------------------
Eng. Alessio Fabiani
Vice President/CTO GeoSolutions

http://www.geo-solutions.it

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