Simone Giannecchini a écrit :
> 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.
This is your vision, but I disagree that it is the way OpenSource work. Linux
and Gnumeric for instance don't work that way. They do have module maintainers
who have the final word on what goes in. Those projects don't let anyone commit
any code. Commiters must proof that they really master the module, and for some
projects like BSD it takes years of contributions in the form of patches.
I remember someone whose very first contribution in the referencing module was
to break the Object.equals(Object) contract in GeneralEnvelope, because he was
not aware of the relationship between equals and hashCode. I had to revert his
commit and write an email about this aspect of Java. Then he made changes based
on an erroneous understanding of what WeakReference are for - I had to revert
again. Then he replaced some calculations on AffineTransform by calculations on
Envelope without asking me, because Envelope are easier to understand. He did
not realize that Envelopes are ambiguous (they said nothing about axis order,
axis reversal, rotations...). Breaking a module with changes based on wrong
Java
and mathematic understanding commited without asking the maintainer is not my
vision of how OpenSource works.
I'm all for collaboration. But given the above, do you understand that I really
want to review every line of code commited in the modules that I maintain? (at
least until I find someone I trust enough). It should not be such a big
problem.
You don't need my agreement; do whatever you want on your own Mercurial clone.
The clone that I maintain will have every lines reviewed by myself or by
someone
that I trust, but no one is forced to use that clone as his primary source. If
it can be done under a GeoTools umbrela, cool!! If it can not, thats fine. We
will leave GeoTools, thats all.
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
