Hi Jody,
> thanks for having setup a starting point.
> I have question since I think it's the first time that a set of classes is
> moved from a plugin module to a core one.
>
> Is there any convention/guidelines to follow up when setting up a proposal
> for this kind of "move-classes refactoring"? (see next question)
>
It is just a normal proposal - we are making a chance that affects other
developers and want to ask around first, check the release schedule, make
sure you have enough resources to do the work, or give you an opportunity
to ask for help.
> In terms of coding, I have mainly moved couple of interfaces, related
> implementing classes and auxiliary helper classes and enums from gt-mosaic
> and gt-coverage.
> What should I add in the "API change" part of the proposal?
>
Suggestions:
- You could list the classes and provide links to their existing javadocs
online
- You could provide an outline of the classes since they are showing up as
new public api and their may be questions
> Should I simply add the "interfaces" (the API) in gt-coverage and avoid
> listing every single class/variant implementing them, enums, utilities?
>
Yes, we are more concerned with showing the functionality change so project
management committee members can approve the work. The proposal is about
communication, the actual details we trust you to do as a committer /
maintainer.
> I also think that I shouldn't add before-after section for gt-imagemosaic
> being a plugin, right?
>
Correct.
Please, let me know.
>
Thanks for the email discussion, we can revise the proposal based on
feedback.
As someone who watches the docs I want to make sure there is a task to add
a code example to the docs. Reminds me to pester Ian for raster symbolizer
normalization docs ...
------------------------------------------------------------------------------
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785471&iu=/4140
_______________________________________________
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel
