[Geoserver-devel] extension proposal

Justin_Deoliveira · June 11, 2008, 2:14am

Hi all,

While waiting for maven builds and cite test runs I decided to whip up a proposal for the extension process that was discussed in IRC today.

http://geoserver.org/display/GEOS/GSIP+22+-+Extensions

Enjoy :).

-Justin

--
Justin Deoliveira
The Open Planning Project
jdeolive@anonymised.com

jive · June 11, 2008, 3:01am

Sorry I missed the meeting today; the proposal seems fine, here are two ideas to consider:
- User Documentation: Installation / Configuration instructions to cut down on questions
- Are the extensions are freestanding or they are allowed to require each other? If possible it would be nice to keep these things independent; if they start depending on each other it may be a sign that the functionality belongs in core.

Cheers,
Jody

Justin Deoliveira wrote:

Hi all,

While waiting for maven builds and cite test runs I decided to whip up a proposal for the extension process that was discussed in IRC today.

http://geoserver.org/display/GEOS/GSIP+22+-+Extensions

Enjoy :).

-Justin

--
Justin Deoliveira
The Open Planning Project
jdeolive@anonymised.com

-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Alessio_Fabiani · June 11, 2008, 9:27am

Sorry I missed the meeting too … I had a look at the proposal, not bad … but I thought the extension requirements were almost the same for community modules ready to be ported on trunk.

So … on my understanding the extension module will contain stable and approved GeoServer plugins that could be or not included in the release, is that right?

On Wed, Jun 11, 2008 at 5:01 AM, Jody Garnett <jgarnett@anonymised.com> wrote:

Sorry I missed the meeting today; the proposal seems fine, here are two
ideas to consider:

User Documentation: Installation / Configuration instructions to cut
down on questions

Are the extensions are freestanding or they are allowed to require
each other? If possible it would be nice to keep these things
independent; if they start depending on each other it may be a sign that
the functionality belongs in core.

Cheers,
Jody

Justin Deoliveira wrote:

Hi all,

While waiting for maven builds and cite test runs I decided to whip up a
proposal for the extension process that was discussed in IRC today.

http://geoserver.org/display/GEOS/GSIP+22±+Extensions

Enjoy :).

-Justin

–
Justin Deoliveira
The Open Planning Project
jdeolive@anonymised.com

Check out the new SourceForge.net Marketplace.
It’s the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php

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

Check out the new SourceForge.net Marketplace.
It’s the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php

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

–

Eng. Alessio Fabiani
Vice-President /CTO GeoSolutions S.A.S.
Via Carignoni 51
55041 Camaiore (LU)
Italy

phone: +39 0584983027
fax: +39 0584983027
mob: +39 349 8227000

http://www.geo-solutions.it

Justin_Deoliveira · June 11, 2008, 3:33pm

Hi Alessio,

Yup, they are pretty much the same. The major distinction is:

1. They are stable, maintained, and tested
2. They are explicitly released every time geoserver is released

Now a community module that is ready to be part of the core also fits those requirements, you are right. The difference is that the community module (when part of the core) is not optional, and does not get its own release artifact.

-Justin

Alessio Fabiani wrote:

Sorry I missed the meeting too ... I had a look at the proposal, not bad ... but I thought the extension requirements were almost the same for community modules ready to be ported on trunk.

So ... on my understanding the extension module will contain stable and approved GeoServer plugins that could be or not included in the release, is that right?

On Wed, Jun 11, 2008 at 5:01 AM, Jody Garnett <jgarnett@anonymised.com <mailto:jgarnett@anonymised.com>> wrote:

    Sorry I missed the meeting today; the proposal seems fine, here are two
    ideas to consider:
    - User Documentation: Installation / Configuration instructions to cut
    down on questions
    - Are the extensions are freestanding or they are allowed to require
    each other? If possible it would be nice to keep these things
    independent; if they start depending on each other it may be a sign that
    the functionality belongs in core.

    Cheers,
    Jody

    Justin Deoliveira wrote:
     > Hi all,
     >
     > While waiting for maven builds and cite test runs I decided to
    whip up a
     > proposal for the extension process that was discussed in IRC today.
     >
     > http://geoserver.org/display/GEOS/GSIP+22+-+Extensions
     >
     > Enjoy :).
     >
     > -Justin
     >
     > --
     > Justin Deoliveira
     > The Open Planning Project
     > jdeolive@anonymised.com <mailto:jdeolive@anonymised.com>
     >
    -------------------------------------------------------------------------
     > Check out the new SourceForge.net Marketplace.
     > It's the best place to buy or sell services for
     > just about anything Open Source.
     > http://sourceforge.net/services/buy/index.php
     > _______________________________________________
     > Geoserver-devel mailing list
     > Geoserver-devel@lists.sourceforge.net
    <mailto:Geoserver-devel@lists.sourceforge.net>
     > https://lists.sourceforge.net/lists/listinfo/geoserver-devel
     >

    -------------------------------------------------------------------------
    Check out the new SourceForge.net Marketplace.
    It's the best place to buy or sell services for
    just about anything Open Source.
    http://sourceforge.net/services/buy/index.php
    _______________________________________________
    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 S.A.S.
Via Carignoni 51
55041 Camaiore (LU)
Italy

phone: +39 0584983027
fax: +39 0584983027
mob: +39 349 8227000

http://www.geo-solutions.it

------------------------------------------------------- !DSPAM:4007,484f9a78250422143011171!

--
Justin Deoliveira
The Open Planning Project
jdeolive@anonymised.com

Justin_Deoliveira · June 11, 2008, 3:38pm

Thanks for the feedback Jody.

Jody Garnett wrote:

Sorry I missed the meeting today; the proposal seems fine, here are two ideas to consider:
- User Documentation: Installation / Configuration instructions to cut down on questions

Good call. There is a bit of docs in the README for the extension, but that hardly cuts it. Adding a wiki page to the requirements.

- Are the extensions are freestanding or they are allowed to require each other? If possible it would be nice to keep these things independent; if they start depending on each other it may be a sign that the functionality belongs in core.

Yeah... its not explicitly stated. But there are two paths for a community module to go when its "ready", that is to the core or to extension. Which path depends on the module and if it makes sense to have it an optional download.

As for dependencies... good question. Perhaps for now just manage it with maven + docs, and if it becomes a problem we can come up with something fancier.

Cheers,
Jody

Justin Deoliveira wrote:

Hi all,

While waiting for maven builds and cite test runs I decided to whip up a proposal for the extension process that was discussed in IRC today.

http://geoserver.org/display/GEOS/GSIP+22+-+Extensions

Enjoy :).

-Justin

--
Justin Deoliveira
The Open Planning Project
jdeolive@anonymised.com

-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

!DSPAM:4007,484f4039119401012714783!

--
Justin Deoliveira
The Open Planning Project
jdeolive@anonymised.com

Andrea_Aime3 · June 11, 2008, 3:43pm

Justin Deoliveira ha scritto:

Hi all,

While waiting for maven builds and cite test runs I decided to whip up a proposal for the extension process that was discussed in IRC today.

http://geoserver.org/display/GEOS/GSIP+22+-+Extensions

Hum, the only thing that's surprising me a bit is the fact that extensions are not in the standard build, and that you have
to activate them with a profile, but I can go with that.

There is the following sentence that seem to be incomplete?
"The profile is added to release/pom.xml and ..."

Besides that, looks good
Cheers
Andrea

Justin_Deoliveira · June 11, 2008, 4:07pm

Andrea Aime wrote:

Justin Deoliveira ha scritto:

Hi all,

While waiting for maven builds and cite test runs I decided to whip up a proposal for the extension process that was discussed in IRC today.

http://geoserver.org/display/GEOS/GSIP+22+-+Extensions

Hum, the only thing that's surprising me a bit is the fact that extensions are not in the standard build, and that you have
to activate them with a profile, but I can go with that.

Hmmm... good point. I think you are right... since these things are stable they should be part of the build by default. If noone else objects I can change that.

There is the following sentence that seem to be incomplete?
"The profile is added to release/pom.xml and ..."

Fixed :).

Besides that, looks good
Cheers
Andrea

!DSPAM:4007,484ff2b8101111804284693!

--
Justin Deoliveira
The Open Planning Project
jdeolive@anonymised.com

jive · June 11, 2008, 7:55pm

Justin Deoliveira wrote:

Hum, the only thing that's surprising me a bit is the fact that extensions are not in the standard build, and that you have
to activate them with a profile, but I can go with that

Hmmm... good point. I think you are right... since these things are stable they should be part of the build by default. If noone else objects I can change that.

Build early; build often - agreed this is a good idea. These are part of the standard build (ie geoserver project) ; but are not part of the standard release (ie geoserver product).
Jody