On Tue, Jan 27, 2015 at 3:59 PM, Jody Garnett
wrote:
> We have several procedures that refer to the module matrix. I would like
> to rewrite those two sections. Creating a new module and supporting your
> module.
>
Oh ok. Works for me
Cheers
Andrea
--
==
GeoServer Professional Services from t
We have several procedures that refer to the module matrix. I would like to
rewrite those two sections. Creating a new module and supporting your
module.
On Tue, Jan 27, 2015 at 1:33 AM Andrea Aime
wrote:
> On Tue, Jan 27, 2015 at 2:28 AM, Jody Garnett
> wrote:
>
>> I have handed out a couple of
On Tue, Jan 27, 2015 at 2:28 AM, Jody Garnett
wrote:
> I have handed out a couple of developer manual links that reference the
> now abandoned module matrix wiki pages.
>
> Serves two purposes:
>
> * point of call for unsupported modules
> * level of maturity used when evaluating modules for grad
I have handed out a couple of developer manual links that reference the now
abandoned module matrix wiki pages.
Serves two purposes:
* point of call for unsupported modules
* level of maturity used when evaluating modules for graduation
Is it worth cutting this out of our developers guide?
--
Jo
I reviewed the page and it looked reasonable. I fixed the broken link for
"review.txt" at the top and the link to my profile page although this
doesn't contain much that is interesting.
What is needed to move the DB2 plug-in from "unsupported" to the "Plugin"
category?
Regards,
David
At 01:2
I have done the usual trick of using parent/child relationships to
maintain the page:
http://docs.codehaus.org/display/GEOTOOLS/Module+Matrix
There is a small number of modules with pages defined, the {excerpt}
being used to show their current "rating".
David Adler you may wish to review the DB2
