Hi Simone, > Andrea is right. > I think that we should try to avoid the situation where someone "owns" > the code of coverage, I'd like to have a some critical mass working > with that codebase, exchanging ideas and bringing in different > perspectives for that module. > Since you are working a lot with JAI and coverage I thought that you > should be somehow involved with the coverage module's maintaireship. >
I understand completely and agree with both you and Andrea. For my own part, while I'm a regular user of the coverage classes, depending on them heavily in my own work, I haven't delved into their internals very much - hardly at all in fact. To date, I've tended to treat them as black boxes and write stuff around them. I guess this was partly because I could rely on asking Martin questions rather than doing my own detective work :) I certainly want to assist with the coverage module, so I'm happy to be listed as a co-maintainer. So I'll spend some time studying the existing code more thoroughly over the next couple of weeks. cheers Michael ------------------------------------------------------------------------------ Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT is a gathering of tech-side developers & brand creativity professionals. Meet the minds behind Google Creative Lab, Visual Complexity, Processing, & iPhoneDevCamp asthey present alongside digital heavyweights like Barbarian Group, R/GA, & Big Spaceship. http://www.creativitycat.com _______________________________________________ Geotools-devel mailing list Geotools-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
