Le portail francophone de la géomatique

Though it wasn't really clear until an hour into the meeting, we were basically discussing two alternative proposals regarding infrastructure and communication:
Merge Geo Ext communication & development with Map Fish (web space, communication channels, community).
Do nothing. (Leave Map Fish as it is. Keep the existing Geo Ext repository, mailing list, website/trac.)
Camptocamp expressed concerns about "hollowing out" Map Fish and raised the potential of confusing any existing community of users by having an independent set of communication channels and web space for Geo Ext.
We all agreed that we want to do nothing to disrupt the Map Fish incubation process with OSGeo, and do not think it makes sense to proceed by pulling large pieces of code out of Map Fish to establish a new project.
We also agreed that Geo Ext as an independent project is nowhere near being ready for consideration as an OSGeo project. For organizations concerned about the ownership of Geo Ext code, we will investigate opportunities for OSGeo or some other trusted body to accept copyright assignment.
The suggestion was made to let Map Fish proceed "undisturbed" in OSGeo incubation while letting Geo Ext evolve naturally on its own for a while. When Geo Ext matures to the point where it is ready for a stable release, Camptocamp (or a future Map Fish PSC) could evaluate whether it makes sense to restructure Map Fish in any way. Since there are multiple organizations & individuals who have an interest in incorporating Geo Ext into a stack or framework or other software, we want to provide the same opportunity for all.
With a discussion on changing infrastructure behind us for now, we are enthusiastic about moving on to discussion about real development - and we will prioritize the design of an initial roadmap for Geo Ext. This roadmap design, of course, should involve anybody interested in participating.