Hopefully I'm not speaking out of school here, but to remind one and all of
the position previously, CSIRO is engaged in a project to bring eResearch
infrastructure to a community of practice, and is funded to support this for
a three year period. We expect to have one or two developers, but at least
twice as many further resources working through testing and deployment
support, working with Geoserver, but probably also client technologies (eg
uDIG, GeoNetwork) etc.
At the very least, this means help getting solid test cases and bug reports
to make maintenance efficiency imporivements. It will certainly be effort
available for aspects of the move to a product footing.
The domain of use will be exercising a wide spectrum of the RnD space -
initially Community Schema support (the bare minimum baseline), then
improved ease of configuration, probably then nD coverage support, SLD and
data subscription/synchronisation capabilities.
Hopefully this provides a little bit of comfort that at least some of the
community is willing to invest in the boring stuff. There is a broad
eResearch agenda around the world, and of course the INSPIRE activity. These
communities need to be tapped, but that means paying attention to their
ongoing needs as well as the seductive eye-candy of mash-up extravaganzas.
RobA
On Tue, Jul 8, 2008 at 6:17 AM, Jody Garnett <[EMAIL PROTECTED]> wrote:
> The remainder of the meeting was interesting; but I am not sure if you
> caught it - everyone was exactly right.
>
> From the standpoint of Refractions we often wish GeoTools was more self
> sustaining; none of the other open source projects we work with have
> such an overhead for us. Now in each case there is usually a dedicated
> project leader; and nothing like IRC meetings (usually an email thread
> is enough to formally work out most problems). And the vast body of code
> is stable and non changing ...
>
> Where do I see this heading for us?
>
> Well the system we have set up with module maintainers (and modules for
> that matter) is very suited to an RnD project; witness the array of
> active RnD modules going on even now :-) As code becomes stable (and
> fall into maintenance mode) we need to treat things more like a library
> (and less like a project). We can see this in many areas already; the
> GeoServer developers (and in a smaller way the uDig developers) have
> been maintaining the library.
>
> Right now we have a fair bit of friction from all sides - let me sum up.
> - Thanks to the GeoServer crew for taking on maintenance for so many
> years (I was sad uDig could not keep up)
> - Everyone has at different times pushed the RnD envelope; the amount of
> technical debt we are carrying is making it not cost effective for
> Geomatys to take on more RnD.
> - It is hard to raise money / time for maintenance work - we need to
> recognize this and plan accordingly
> - PMC responsibility is planning ... not maintenance and bug fixes.
>
> Martin proposed one way forward today; I will review and comment when I
> am a bit more awake. Personally I am not going to make any decisions
> about this until our graduation requirements are met.
>
> Cheers,
> Jody
>
> -------------------------------------------------------------------------
> Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
> Studies have shown that voting for your favorite open source project,
> along with a healthy diet, reduces your potential for chronic lameness
> and boredom. Vote Now at http://www.sourceforge.net/community/cca08
> _______________________________________________
> Geotools-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/geotools-devel
>
-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
_______________________________________________
Geotools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
