On Fri, Jul 16, 2010 at 02:38:52PM -0400, Andrew Ross wrote:
> Thanks for the explanation Paul. Very much appreciated.
>
> My apologies for prolonging this thread with one more question. In terms of
> coding style, does it make sense to have the copyright notices for each
> change in the code as t
Thanks for the explanation Paul. Very much appreciated.
My apologies for prolonging this thread with one more question. In terms of
coding style, does it make sense to have the copyright notices for each
change in the code as this example? Should copyright notices from previous
modifications ever
They can't withdraw rights to use it, they've licensed it under the
LGPL. Once it's out, it's out. Multi-copyright projects are all over
the place, it's not a big deal. The only thing copyright assignment
gets you is the ability to change the license of future releases of
the code. (The old release
On Fri, Jul 16, 2010 at 08:53:59AM -0400, Andrew Ross wrote:
> My concern is what prevents a contributor from withdrawing the rights to use
> their source code on a whim?
I don't understand this concern.
You mean what prevents people to assign a different licence to the code they
commit to the GE
Multi-people joint copyright with an organization like OSGeo also owning
joint copyright is great and a very common model in open source. It doesn't
seem that this is the case for geos though. A liberal license (such as LGPL)
helps of course as it states very generous rights to use the source. My
c
On Thu, Jul 15, 2010 at 07:53:33PM -0400, Andrew Ross wrote:
> Hi Tom, All
>
> Saw the copyright notice in the change. Copyright for geos seems to be held
> by a number of people and organizations. That seems legally murky to me but
> I am not a lawyer. Has this been discussed previously?
Not tha
