Re: Re-using copyrighted code

References	(3 earlier) <51B4DCA2.9000903@gmail.com> <CAMjeLr9LT_pWUWUCsDEiW9vDRc71VdOtDnK+zfb2UtEJwVOqaQ@mail.gmail.com> <mailman.2942.1370815687.3114.python-list@python.org> <51b51ef9$0$30001$c3e8da3$5496439d@news.astraweb.com> <CAPTjJmosLFmK3GgiTsTmHQsMb9+bJQKKKcC0Q3Ea1qaeVcsGwg@mail.gmail.com>
Date	2013-06-09 20:40 -0700
Subject	Re: Re-using copyrighted code
From	Mark Janssen <dreamingforward@gmail.com>
Newsgroups	comp.lang.python
Message-ID	<mailman.2954.1370835651.3114.python-list@python.org> (permalink)

Show all headers | View raw

> Granted, IANAL, but the scholarly article I linked to above refers to
> several of the same issues. I don't know about publication revoking
> *all rights*, but there was definitely an understanding by the court
> that publication meant a reduction of copyright claim.

Again, I don't think I said that publication revokes "all rights", but
it certainly opens the can of worms that wouldn't have been open had
you kept it to yourself.  So while it *exposes you*, it does not still
*deprive you of rights*.  That is what copyright is for:  to protect
you after you've exposed yourself.
-- 
MarkJ
Tacoma, Washington

Back to comp.lang.python | Previous | Next — Previous in thread | Find similar | Unroll thread

Thread

Re: Re-using copyrighted code Chris Angelico <rosuav@gmail.com> - 2013-06-10 08:07 +1000
  Re: Re-using copyrighted code Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2013-06-10 00:34 +0000
    Re: Re-using copyrighted code Chris Angelico <rosuav@gmail.com> - 2013-06-10 13:31 +1000
    Re: Re-using copyrighted code Mark Janssen <dreamingforward@gmail.com> - 2013-06-09 20:40 -0700

csiph-web