On Wed, Mar 25, 2009 at 2:58 PM, Martin Desruisseaux <[email protected]> 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
This is -THE- problem Martin, the modules are not YOURS (maintainer != owner), the modules are part of the project and being so someone else may change them providing that is follows the rules, which means proposal and everything. If you don't have time to review changes, even roughly, you cannot stop them. You are the original author but this should give you only a limited amount of special rights on the modules, if you like it or not. This is how open source usually works, what you describe, is what I call closed-open source, you want people to use your work not to participate in it. > 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. Sorry Martin, but this example is somehow irrelevant. There are processes to handle this: - proposal - discussion - work If the work has been done without a proposal, then the people cannot expect us to accept it, but on the other side, you cannot even expect people to stop working because you want to always have the last word on *your* modules or review every single line of code. You have to realize that this will never happen, even inside a single company. Therefore when the proposal procedure is in place there should not be any problems of accepting contributions. Of course we may want to discuss about improving the proposal stuff and about setting coding standards and everything as well as about ways to enforce them. About what aaime reported, I am going to pretend that you were somehow misunderstood, since I believe that anyone whose age is >= 12 years would not behave like it has been reported. On my side, I will repeat what I usually say, I have always found your work useful and interesting, I have always promoted/used it myself, I will always try to collaborate if possible (see my email about coverage IO), but if this does not happen, I don't think I will cut my wrists :-). Btw, for me this discussion is closed, I don't have any more time to spend on analyzing this geotidy-thing at least until I see plans, proposals and a collaborative approach. Whatever I will propose on coverages will be proposed for GeoTools and will follow its procedures. Simone. > > > 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 > -- ------------------------------------------------------- Ing. Simone Giannecchini GeoSolutions S.A.S. Owner - Software Engineer Via Carignoni 51 55041 Camaiore (LU) Italy phone: +39 0584983027 fax: +39 0584983027 mob: +39 333 8128928 http://www.geo-solutions.it http://simboss.blogspot.com/ http://www.linkedin.com/in/simonegiannecchini ------------------------------------------------------- ------------------------------------------------------------------------------ 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
