While I have nothing but the utmost respect for your work Martin, Andrea 
is right. The community and PSC were totally bypassed with this entire 
situation. GeoTools is a community project which has always been run by 
its module maintainers. And that as always been its strength imo. 
Whenever there are controversial topics brought up we all come to a 
consensus, and the best possible product usually emerges.

I can't think of anything more detrimental to an open source project 
than allowing people to fork to get around having to collaborate with 
others about decisions. You can dress it up all you want and call it 
"distributed versioning control" but it is what it is.

The mess that resulted from the threaded EPSG work is unfortunate. But 
Simone is correct that there are processes in place to protect against 
this sort of thing. It is your job as the maintainer to demand a 
proposal, ask for patches, have people work on a branch, etc...

There also the fact that being a community project means doing the best 
to accept contributions when they arise, and accepting the fact that 
they might not always be aesthetically perfect.

Martin Desruisseaux wrote:
> Hello Andrea
> 
> Putting "geotidy" under a GeoTools umbrella (either as a separated Maven 
> project 
> or merged to SVN) is an offering that we make to the community, but as far as 
> we 
> (at geomatys) are concerned we have no obligation to do so. This offer has 
> been 
> made repeatedly since the begining. If the PSC don't want it, we are 
> completly 
> fine with that.
> 
> Creating geotidy on a separated repository may have been a source of 
> critisism, 
> but sincerly it would have been impossible for me to do otherwise. GeoTools 
> SVN 
> has many thousands of javac and javadoc warnings. I can't fix everyone 
> warnings 
> and I want to work on the warnings in the modules that I maintain without 
> being 
> bured under everyone warnings. Furthermore geotidy has been a public 
> repository 
> since its begining.
> 
> You said that I'm aiming to be a "dictator". However every modules in 
> Geotidy, 
> including Coverage, are mine. More important, I'm the benevolent dictator on 
> my 
> Mercurial clone of geotidy. Anyone can be the dictator of their own clone of 
> the 
> repository, can commit whatever changes he wants on his clone and can share 
> his 
> changes with who he wants. Simone or anyone else can not be prevented by 
> myself 
> from commiting, and nothing can prevent Geoserver from using Simone's work. 
> The 
> usage of a Distributed Versionning System is at the heart of this Geotidy 
> move, 
> you really need to understand its principle.
> 
> About the "Threaded EPSG" story: Try to imagine the opposite scenario. 
> Imagine 
> that a big compagny (said ESRI - I'm just inventing) paids Geomatys for doing 
> major work on the JTS library. Geomatys had never touched JTS code before. 
> Geomatys sign the contract then said to Martin Davis (the JTS author and 
> maintainer) "Hey! we are going to change big parts of JTS. You are not going 
> to 
> work with us (unless for free); please let just agree on the plan and let us 
> do 
> the code". Geomatys duplicates lot of code, then leaves the library in a 
> messy 
> state and wait for Martin Davis to clean this code for free. A few JTS 
> releases 
> are made in that state before Martin Davis finally have a chance to work 3 
> weeks 
> - for free - cleaning Geomatys work, fixing bugs and logical inconsistencies. 
> Then someone complains that it tooks years before he did this job, suggesting 
> that it is all Martin's fault.
> 
> This kind of story is part of the reasons why we created geotidy.
> 
> 
>       Martin
> 
> ------------------------------------------------------------------------------
> Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
> powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
> easily build your RIAs with Flex Builder, the Eclipse(TM)based development
> software that enables intelligent coding and step-through debugging.
> Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
> _______________________________________________
> Geotools-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/geotools-devel


-- 
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.

------------------------------------------------------------------------------
_______________________________________________
Geotools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Reply via email to