On 7/4/06, Jacob Kaplan-Moss <[EMAIL PROTECTED]> wrote:
> fingers crossed about that lame-assed ORM patent -- so I'll do what
Patents don't have much to do with copyright. ;-)
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Googl
On Jul 4, 2006, at 7:05 PM, Jan Claeys wrote:
>> From Wikipedia[1]:
>
> Under the U.S. Copyright Act, a transfer of ownership in
> copyright must be memorialized in a writing signed by the
> transferor. For that purpose, ownership in copyright includes
> exclusive l
Jan.
a CLA protects from people changing their minds as well, and in some
cases actually
assets that the person assigning the copyright over is the actual owner.
from my point of view it should be weighed up as follows:
cons of having people sign a CLA:
- about 20 minutes if they are an indivi
On wo, 2006-06-21 at 13:52 -0500, Jacob Kaplan-Moss wrote:
> We don't; my conversations with the company lawyers seemed to
> indicate that you're implicitly assigning copyright simply by
> submitting code to an OSS project. Of course IANAL, but I'm going to
> trust what the ones we talked t
On wo, 2006-06-21 at 13:52 -0500, Jacob Kaplan-Moss wrote:
> We don't; my conversations with the company lawyers seemed to
> indicate that you're implicitly assigning copyright simply by
> submitting code to an OSS project. Of course IANAL, but I'm going to
> trust what the ones we talked t
On 6/21/06, Jacob Kaplan-Moss <[EMAIL PROTECTED]> wrote:
> We don't; my conversations with the company lawyers seemed to
> indicate that you're implicitly assigning copyright simply by
> submitting code to an OSS project. Of course IANAL, but I'm going to
> trust what the ones we talked to say be
On Jun 21, 2006, at 1:26 PM, Deryck Hodge wrote:
> I just wondered if Django had any copyright
> contingencies when submitting large chunks of code (obviously, small
> patches aren't as much a concern.) No biggie, if not.
We don't; my conversations with the company lawyers seemed to
indicate t
Hi, Wilson.
On 6/21/06, Wilson Miner <[EMAIL PROTECTED]> wrote:
>
> AFAIK this is a non-issue with BSD. Under BSD, LJW can do anything
> with code that becomes part of Django, and so can anybody else. If you
> copyright your code, that's independent from you submitting it as a
> patch or committi
AFAIK this is a non-issue with BSD. Under BSD, LJW can do anything
with code that becomes part of Django, and so can anybody else. If you
copyright your code, that's independent from you submitting it as a
patch or committing it to the project. Committers must be able to
attest that the code they
Hi, all.
Do you guys have any guidelines with regard to copyright when
accepting contributions from others? Does copyright need to be
assigned to Lawrence Journal-World when submitting to Django? Or do
programmers retain copyright and assign the code to the project under
the BSD license? (I kn
10 matches
Mail list logo
