[Web Comm] Q&A to choose a software stack
Jason Birch
Jason.Birch at nanaimo.ca
Sun Apr 2 23:57:54 EDT 2006
I guess for web mapping, what stack you use would depend a lot on what your existing preferred development/deployment environment is. Also, people aren't usually looking for an entire stack, just what they need to get the job done.
I certainly see some problems coming trying to distinguish between the various web mapping components, and show how they work together. Also, differentiating between the use cases for some of the smaller agile packages, and the larger ones like MapGuide. We have a real wealth of packages to choose from, but in some ways this is a hinderance.
Jason
________________________________
From: Jody Garnett [mailto:jgarnett at refractions.net]
Sent: Sun 2006-04-02 2:05 PM
To: dev at webcommittee.osgeo.org
Subject: [Web Comm] Q&A to choose a software stack
An interesting idea there ... and a bit of an evil idea. Breakdown our
software into working stacks and the play a Q & A game allowing Nosaj to
find a couple of stack to try out with a single quickstart/install
instructions. I have a series of notes of how to install
Postgres/PostGIS/Mapserver/GeoServer/uDig on to a laptop that Nosaj
could check out to see if it was suitable....
But the point is well made, by focusing on the projects we lose the
solution that Nosaj (and indeed several of the other people on the list
came here to find).
Politically we may need need to find "more then one" stack with
pros/cons between them in that feature table the that
Jody
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe at webcommittee.osgeo.org
For additional commands, e-mail: dev-help at webcommittee.osgeo.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/ms-tnef
Size: 4590 bytes
Desc: not available
Url : http://lists.osgeo.org/pipermail/webcommittee_dev/attachments/20060402/84ae3877/attachment.bin
More information about the Webcommittee_dev
mailing list