Agenda:

1. what is up
2. GeoTools 2.4.2 release
3. update headers
4. gt2- prefix removal
5. progress module
6. postgrid in gt2

SamHiatt: Martin: I was considering bringing up PG in the meeting to see what other people's interest in it is... and to discuss how to frame the module, once it moves to geotools.
ggesquiere left the room (quit: Client Quit).
desruisseaux: Sure if you wish
ggesquiere [n=gilles@arl13-3-88-169-136-131.fbx.proxad.net] entered the room.
desruisseaux: But I'm not sure that it is mature enough...
aaime [n=aaime@82.56.105.98] entered the room.
desruisseaux: (would probably be an unsupported module for a while...)
jgarnett: morning
jgarnett: meeting time?
jgarnett: (we moved it an hour earlier; ie now; did we not?)
desruisseaux: yes
aaime: yap
gdavis [n=gdavis@mail.refractions.net] entered the room.
jgarnett: sweet
jgarnett: aside: thanks for the email over the weekend aaime - I will try and stay a bit more on target with udig stuff.
jgarnett has changed the topic to: 0) what is up
aaime: np, sorry for being mad
aaime has changed the topic to: 0) what is up 1) GeoTools 2.4.2 release
jgarnett: it is okay; I have broad sholders; a share of the blame; and I know it is a frustrating topic.
desruisseaux: Topic: gt2- prefix removal in module names
user451 [n=user451@mail.refractions.net] entered the room.
jgarnett: Anyone know if exclisa is around today? It would be fun to talk process stuff with him...
desruisseaux: I don't known...
jgarnett: aside: aaime I was reviewing filtervistors stuff over the weekend and liked what I saw of postgis-versioned module.
jgarnett has changed the topic to: 0) what is up 1) GeoTools 2.4.2 release 2) update headers
aaime: jgarnett, eh, as they say, plan to redo once
aaime: with some modifications to the query support I could do it better
desruisseaux has changed the topic to: 0) what is up 1) GeoTools 2.4.2 release 2) update headers 3) gt2- prefix removal
aaime: without making it postgis specific at al
jgarnett: indeed
gdavis: Topic: unsupported/process module committed
jgarnett: well it would be fun to see the same api backed on to arcsde versioning madness
jgarnett has changed the topic to: 0) what is up 1) GeoTools 2.4.2 release 2) update headers 3) gt2- prefix removal 4) progress module
aaime: jgarnett, yes, that's a reason I did not try to push the versioning interfaces into gt2-api
aaime: (lack of 2nd and 3rd implementation of the concept)
jgarnett: oh: I did look at the renderer; there are a few hacks to check if query was implemented (with respect to reprojection), I cannot tell if they are used - but they exist.
aaime: any other topic?
jgarnett: aaime++ yeah; I think we have 3 clients for the process module so I am hopeful this one will work; but also wanting to check on Eclesia.
jgarnett: I think we better start...
jgarnett: 0) what is up
desruisseaux: Martin: full time on postgrid...
***aaime trying to get geotools 2.4.2 out of the door
jgarnett: jgarnett - hacking up process module with gdavis; going to build a swing user interface for fear of putting too much information in javadocs where it would be ignored.
gdavis: gdavis: same as jgarnett
SamHiatt: whooops... I'm not really away.
SamHiatt: Too late to add a topic?
aaime: no, if it's a quick one
CIA-31: jgarnett * r29830 geotools/gt/modules/unsupported/process/src/ (15 files in 10 dirs): code review of process module part 4, finally with example and test case
SamHiatt: Just concerning how to fram the postgrid stuff once it makes it to gt-unsupported
aaime has changed the topic to: 0) what is up 1) GeoTools 2.4.2 release 2) update headers 3) gt2- prefix removal 4) progress module 5) postgrid in gt2
jgarnett: 1) GeoTools 2.4.2 release
jgarnett: aaime floor is yours
aaime: Any objection for me to go and release?
aaime: (any solid objection)
desruisseaux: All right on my side
jgarnett: sounds good.
aaime: ok
SamHiatt: why would I object?
jgarnett: (If you had a few moments to look at GeoServerOnlineTest case (and see if I am missing something stupid) it would make me happy - I hate the WFSDataStore not working)
CIA-31: jdeolive * r29831 /geotools/tags/2.4.2/: Tagging gt2 2.4.2
jgarnett: do you need any help on the release aaime? Jira and what not...
aaime: (that is really me using jdeolive account)
jdeolive: its /me twin from the alternate universe
jgarnett: aaime++ good way to confuse svn blame.
aaime: jgarnett, announcements as usual beat the hell out of me
jgarnett: anything else for this topic?
aaime: jgarnett, sorry, I'm using a shared VM
jgarnett: okay ping me when you have the anouncement text ready; sending email is a good "Waiting for the build" task.
aaime: I'll do... tomorrow
jgarnett: so ... next topic?
aaime: now I don't even know if I have enough time to make a deploy so that Mike can release GeoServer
aaime: yap
jgarnett: 2) update headers
jgarnett: martin and acuster answered some of my questions last week
jgarnett: so if we have some hot shot with regular expressions
jgarnett: we should be able to get 90% of the library in one shot...
jgarnett: (I think we are now the only origional inccubation progject still going ...)
jgarnett: link is here: http://docs.codehaus.org/display/GEOTOOLS/Graduate+from+OSGeo
jgarnett: we need a search replace for (C) ********, GeoTools Project Managment Committee (PMC)
jgarnett: (C)

, Open Source Geospatial Foundation (OSGeo)
jgarnett: (or whatever the syntax is...)
jgarnett: any takers?
SamHiatt: I might be able to help with that...
aaime: SamHiatt, do you have committer access?
aaime: (in any case, you could try to setup an ant script to do the rename and have someone else run it)
SamHiatt: However, I'm probably not the best candidate for the job at the moment...
aaime: I guess no one is better than the only candidate
jgarnett: note; we still have to review the result; but no sense working hard.
SamHiatt: Haha...
jgarnett: I think eclipse search and replace can handle it; I may try later.
jgarnett: SamHiatt can I email you if I fail?
SamHiatt: No, I am not a GT committer...
jgarnett: fair'nuff
desruisseaux: I may ask Cédric to help me on this one for the metadata, referencing and coverage module, and ask peoples if we run the script on other modules. But not right now...
SamHiatt: jgarnett:
jgarnett: thanks...
SamHiatt: sounds good...
jgarnett: 3) gt2-prefix removal
jgarnett: martin? I think ...
SamHiatt: I was planning on doing the same kind of thing.
SamHiatt:
desruisseaux: Cédric refreshed the gt2-prefix-removal branch.
desruisseaux: I think we are ready for a merge with trunk
jgarnett: so what does that actually mean? we need to change our maven dependencies in geoserver?
desruisseaux: But I probably need to remind what it is about
desruisseaux: and what would be the consequence.
desruisseaux: Yes, the Maven depencies would need to be updated.
aaime: what was the status for the eclipse users? (since that was the blocker last time)
desruisseaux: Eclipse can now include the version in the module name
jgarnett: I thought jdeolive found some magic setting.
jdeolive: yes
jdeolive: there is a property you can set to se the pattern to be used for the eclipse projection name
desruisseaux: This is not a very robust workaround, but it would work as long as Geotools's main doesn't have the same version number than Geoserver's main.
jdeolive: i think you could use the groupid to get around it
desruisseaux: Maybe, I don't know about the Eclipse plugin...
desruisseaux: (I'm on Netbeans)
desruisseaux: As a side note, GeoAPI site is now generated every day by Hudson (since last week).
desruisseaux: The goal of this gt2-prefix removal is to do the same with GeoTools
jdeolive: doing maven eclipse:eclipse -DprojectNameTemplate=[groupId].[artifactId]
jdeolive: woudl do it
jgarnett: so we would need to modify our developers guide instructions justin?
jgarnett: I will do so now...
desruisseaux: Thanks Justin Sound like a much cleaner approach than version number.
jdeolive: np
aaime: which version of the eclipse plugin does support that?
jgarnett: (or can we bake that setting into the pom.xml ?)
jdeolive: yup
jdeolive: butn ot eveyone might want it through
aaime: (in gt2 we have declard version numbers, we're not using "lastest and greatest")
jdeolive: aaime: correct
jdeolive: i think we might need to upgrade the version of the eclipse plugin
jdeolive: which might mean people have to upgrade maven
jdeolive: what is the current receommended version?
aaime: release guide says 2.0.5
aaime: but I've been using 2.0.8 for the latest releases I made
SamHiatt: I'm on 2.0.8...
desruisseaux: I'm on 2.0.8 as well
desruisseaux: (linux box)
jgarnett: (updated http://docs.codehaus.org/display/GEOT/2.5.8+Maven+Eclipse+Plugin+Goals)
jgarnett: I think everyone is actually using 2.0.8 now...but email asking if we could switch to 2.0.8 did not get any response.
SamHiatt: (sorry... maybe off topic, but... does anyone have a problem with the latest maven-surefire-plugin?)
jgarnett: aaime; if that is what you are using for release
aaime: yep
jgarnett: I will update the developers guide instructions now.
desruisseaux: (Samuel: no issue with surefire on my side lately)
SamHiatt: (I have to specify version 2.3.1 to prevent build failures)
SamHiatt: (oh, well...)
aaime: (SamHiatt, sometimes we see "failure to load main class from surefirexxx.jar" on the build server)
desruisseaux: So is there any objection about going ahead with the gt2- prefix removal in module name?
aaime: (but it's random)
aaime: not really... what was the advantage again?
SamHiatt: (Hmmm... thx)
aaime: some site generation issue right?
desruisseaux: When generation the web site with "mvn install", URL are broken if the module name doesn't match exactly the directory name.
desruisseaux: (typo: when generating...)
desruisseaux: (typo: with "mvn site")
aaime: right right
jgarnett: did you not have a question about the "xsd" group of modules?
desruisseaux: Yes
desruisseaux: Actually Justin gave his agreement a while ago, but we wanted to verify that it was still possible (maybe the situation has changed).
desruisseaux: The xsd child projects have name like "xml-core", which doesn't match the directory name because of the "xml" prefix.
CIA-31: jdeolive * r29832 /geotools/tags/2.4.2/ (97 files in 97 dirs): Changed version number to 2.4.2
desruisseaux: The proposal was to put those child modules in a "org.geotools.xml" groupID, and remove the "xml-" prefix from the artifactID.
jdeolive: desruisseaux: yeah i agreed with that
jdeolive: and still like the idea
desruisseaux: Just two details (would like to known your preference):
desruisseaux: groupID: "org.geotools.xml" or "org.geotools.xsd"?
desruisseaux: (since the parent module is "xsd"...à)
jdeolive: right... hmmm... no huge preferemce... i think xml is more logical... but then i think there would be a collision with teh old xml module
jdeolive: since the root pom would be org.geotools.xml and so would the old module in library
jdeolive: woudl it not?
desruisseaux: At your choice...
jdeolive: lets stick with xsd
desruisseaux: Okay
jdeolive: that way we dont have to change any modules names
jgarnett: sweet
desruisseaux: Second minor details: should we add a "xsd-" prefix in the JAR name?
desruisseaux: (would be: gt-lib-ext-...)
desruisseaux: sorry
desruisseaux: gt-lib-xsd-...
desruisseaux: (assuming the XSD modules are in "library", I don't remember)
jdeolive: nope, extension
desruisseaux: Thanks. Would be gt-ext-xsd...jar then
jdeolive: would this just be for release artifacts?
desruisseaux: This is just the JAR name
desruisseaux: The module name don't have any prefix.
desruisseaux: But we use Maven <finalName> construct for adding those prefix automatically in JAR names only.
jdeolive: is this the same name as the jar will have in teh local maven repo?
jdeolive: that will still be just artifactId-version.jar correct?
desruisseaux: Yes
jdeolive: cool
jdeolive: yeah i am fine with that
desruisseaux: Okay, we will go ahead with that then. Thanks!
jgarnett: 4) progress module
jdeolive: desruisseaux: suggestion
jgarnett: opps
desruisseaux: Yes?
jdeolive: we might want to clear out old artifacts in the online repositories, at RR and the one youg uys mirror
desruisseaux: Yes I agree
jdeolive: cool
ticheler [n=ticheler@87.1.7.2] entered the room.
CIA-31: jdeolive * r29833 /geotools/tags/2.4.2/README.html: Updated README file
jgarnett: may make checking out and building an older udig impossible..
desruisseaux: But it may be safe to wait a few weeks, until uDig and Geoserver (at least) updated their dependencies.
jgarnett: not sure that we care?
jdeolive: agreed
jdeolive: see mailing list, user confusion
jgarnett: we can update udig the moment you are done.
jdeolive: and our builds might keep kicking along not updating geotoosl aritfacts
jgarnett: okay ... moving on?
jgarnett: 4) progress module
jgarnett: gdavis you have the floor
SamHiatt: I ain't away!
gdavis: so the process module is committed under unsuported currently
gdavis: with the interfaces, etc, and currently one implemented process
gdavis: I guess I'm looking for any feedback on what's currently there
gdavis: if anyone wants to try making another process and see if they run into any walls or problems
gdavis: if not I will continue on
SamHiatt: What kinds of modules are in there?
gdavis: also, i will be making 2 new modules next
aaime: the new ones, and the old ones without a maintainer
gdavis: one for a wps client, and one to hold beans/bindings
gdavis: does anyone have any feedback about where the beans/bindings should live?
jgarnett: (the beans may exist in geoserver; which is currently providing a home to wfs 1.1 beans as I understand it?)
aaime: what binding framework are you going to use?
aaime: jgarnett, correct, thought it would be better to move all those bindings to gt2
gdavis: which is why we thought we should do that for this module from teh start
aaime: so you're using xml-xsd bindings?
gdavis: yes
gdavis: should I be making a new module just for the beans/bindings?
jgarnett: kudos to jdeolive on the documentation btw - it really helps
aaime: Ok. Remember to ask before creating those two modules (the procedure is alays the same)
aaime: (jgarnett, if someone wonders who's bombing lists.refractions.net, that's me doing the deploy)
jgarnett: understood; I can give an update on server hell after the meeting
gdavis: ok, I think I've done my spiel
jgarnett: anything else on the process side of things? I do wish Eclesia was here as having three clients to drive the api would really help my trust.
gdavis: i would welcome any feedback anyone has after looking over the current process api
jgarnett: okay moving on ...
desruisseaux: I can ask Eclesia tomorrow if he can contact you Jody
jgarnett: 5) postgrid in gt2
aaime: SamHiatt, this is yours
jgarnett: (thanks martin; it would really help; we will try and have a swing example for him)
SamHiatt: So I just wanted to quickly share my ideas for PG
SamHiatt: At the FOSS4G 07 Geomatys was the only group I found doing anything to organize and serve nD coverages...
SamHiatt: I would hope that by the time FOSS4G08 rolls around that we will have PostGrid somehow integrated into GT so that GT can boast of having an ND solution for Grid Coverages.
jgarnett: I got a couple of questions
SamHiatt: IFREMER, as well as my group, Ecocast, will have some cool stuff to show by then...
jgarnett: I have been watching this work take shape over a while ..
jgarnett: and I have it in my mind that I was going to check it out
jgarnett: when two things happened:
jgarnett: - some kind of geoapi interfaces were set up for me to review
jgarnett: - some kind of data access api was actually agreed on by simone and martin
jgarnett: Are either of these things in store? If not how do you expect to interrate with geotools?
desruisseaux: I can bring some more point here:
jgarnett: the current solution of client code making use of GridFormatReader scares me
desruisseaux: Jody has raised one of the issue that I see with postgrid integration with GT.
desruisseaux: The issues are:
SamHiatt: I should point out here that I don't know the details....
mcoudert [n=mcoudert@AAnnecy-256-1-12-49.w90-10.abo.wanadoo.fr] entered the room.
desruisseaux: - For now PostGrid avoid any use of GridFormatReader. It interact directly with ImageIO. I don't know it it is acceptable for GeoTools (for sure it is not an example of what to do).
desruisseaux: The plan was to refactor it when some kind of GridCoverageStore would be ready, but we are not yet there.
aaime: right right
aaime: we should find some time to define a GridCoverageStore indeed
aaime: I think everybody wants it
aaime: it's just that nobody seems to have time
SamHiatt: I would be interested in being involved in that discussion.
aaime: SamHiatt, everybody would
SamHiatt: Can you point me to any past discussions/wikis on the issue so I can get up to speed?
aaime: we need someone that takes the time to do the heavy lifting or
aaime: of setting up a proposal
desruisseaux: 2) Postgrid test suite is hard to setup. It could take a while before a postgrid integrated in GT has a test suite run at "mvn install" time.
aaime: creating a prototype implementation
aaime: desriusseaux, that would only mean it would take a while before it goes into supported land
jgarnett: simone already agreed to this approach: http://docs.codehaus.org/display/GEOTOOLS/GridAccess+based+on+WCS+Specification
simboss: I am planning to put ou something before the end of the month
SamHiatt: desruisseaux: I plan on fixing the test suite, at least for my case...
SamHiatt: perhaps I could help with that.
aaime: jgarnett, I like the general idea (based on WCS)
simboss: we are doing some work to support Eo time series for ESA
jgarnett: but was sad when it was not discussed and accepted at the same time as groldan's data access stuff.
aaime: but the names are scary
jgarnett: The names?
aaime: GridAccess... arg, reminds me of the dreaded DataAccess
jgarnett: (ah
jgarnett: I don't care about the names this instant
SamHiatt: this sounds cool.
jgarnett: more that developers can set aside some time to work together)
jgarnett: Honestly "Raster" rather than "Grid" may be better all around for everyone
aaime: moreover, there is no metadata access there, which is bad (we lakc the equivalent of DataStore.getSchema())
SamHiatt: I agree, jgarnett;
jgarnett: indeed; page is there to record what people think are a good idea.
simboss: well if samhiatt ha some time
aaime: Grid comes from the specs thought
simboss: has
simboss: he can start throwing some ideas up on the wili
simboss: wiki
SamHiatt: I'll read up on the issue and offer my input.
desruisseaux: Maybe because Raster is typically though as 2D while grid can be ND?
simboss: as a start
aaime: SamHiatt, you subscribed to the ml?
SamHiatt: I'll start throwing my ideas all over the wali.
jgarnett: cool; thanks guys - I am happy to review (I am so tired of this problem frustrating everyone)
aaime: (since it's a better place to discuss, wiki is better to store the results of the discussion)
jgarnett: martin had a second issue... where did it go?
desruisseaux: I'm here
SamHiatt: Ok, so "raster" isn't the best either.
desruisseaux: The second issue was test suite hard to setup.
SamHiatt: I like the idea of "ND Coverage" or something
aaime: (the 3d equivalent of raster being voxel)
sfarber [n=sfarber@88-149-177-23.static.ngi.it] entered the room.
jgarnett: any thoughts on that one martin?
SamHiatt: aaime, I think I am on the ml...
SamHiatt: but I don't have time to keep up with much of it.
aaime: nice
jgarnett: set up the database on the build server or something ... or boil all the setup steps into a java class people can run.
desruisseaux: A third issue is that current postgrid code still have strong links with its original purpose, which was to perform statistical analysis that may not be of general interrest. So some part would probably need to be trimmed down, but it may take a little while before it can be separated without breaking the statistical stuff.
aaime: SamHiatt, I just don't want the wiki page to degerate on a comment mess
SamHiatt: VoxelAccess?
jgarnett: martin you may be able to hide the stats stuff behind gdavis's process module.
jgarnett: (just a thought)
desruisseaux: Yes sure I should look at time, but the usual problem is that I'm slow...
zzorn [n=zzorn@212.16.103.33] entered the room.
zzorn_ [n=zzorn@212.16.103.33] entered the room.
jgarnett: so we are a few mins past meeting time; just a warning that we need to wrap up.
jgarnett: darn ...
jgarnett: SoC
zzorn left the room (quit: Read error: 104 (Connection reset by peer)).
jgarnett: deadline was today; there are lots of proposals for people to review this week.
SamHiatt: Cool...
jgarnett: Something we can take out to the mailing list this year; one email thread per proposal?
jgarnett: You are done SamHiatt?
SamHiatt: Yeah, sounds great!
jgarnett: okay thanks for the efficient meeting everyone. happy hacking.
jgarnett: I will post the logs.
aaime: thanks
SamHiatt: Thanks!
aaime: 2.4.2 is up on the repos
SamHiatt: Yay!
aaime: I'll do the rest of the release procedure tomorrow