Hi all,
I would like to promote the teradata community module to a fully supported
extension. The module itself simply pulls geotools datastore and doesn't do
much on its own. Similar in nature to the oracle or sql server extensions.
The geotools datastore has recently been approved as an extension and
backported to the stable branch. The relevant discussion can be found in
this email thread [1]. So I would like to do the same for the geoserver
equivalent. Move to supported and backport to stable branch. In terms of the
geoserver checklist [2]:
1. Users
As described in the gt thread the users are not really show up on our email
list yet but customers of teradata have indeed been using the geoserver
extension
2. Maintainer
myself
3. Stable
Being a simple wrapper around the datastore there is not much going on
there... no planned changes for the forseeable future.
4. Test coverage
Not much to test at the gs level but the gt datastore maintains around 55%
coverage.
5. IP Check
Good to go
6. User docs
Courtesy of our master wordsmith mike:
http://docs.geoserver.org/latest/en/user/community/teradata/index.html
7. Contributor agreement
No issues there.
So... any objections?
-Justin
[1]
http://osgeo-org.1803224.n2.nabble.com/moving-teradata-to-supported-plugin-status-td6386819.html
[2]
http://docs.geoserver.org/stable/en/developer/policies/community-modules.html#id2
--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
------------------------------------------------------------------------------
vRanger cuts backup time in half-while increasing security.
With the market-leading solution for virtual backup and recovery,
you get blazing-fast, flexible, and affordable data protection.
Download your free trial now.
http://p.sf.net/sfu/quest-d2dcopy1
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
