Re: [License-discuss] MakeHuman, CC0 and AGPL

2017-11-01 Thread Diane Peters
"CC0 is both a public domain dedication and a license. If the dedication is effective, then it affects all the manifestations (on a website or a CD/DVD-ROM) and copies. If it is not, then the permissive license affects only the copies it is attached to." The final sentence is incorrect, at

Re: [License-discuss] MakeHuman, CC0 and AGPL

2017-10-25 Thread Diane Peters
It's the former if you're using CC0. The work itself -- in whatever form and whatever the number of copies -- is placed as nearly as possible in the public domain. You could try to enforce a license on a particular copy, but you can't enforce it as a matter of copyright and related rights (as

Re: [License-discuss] Possible alternative was: Re: U.S. Army Research Laboratory Open Source License (ARL OSL) Version 0.4.1

2017-03-01 Thread Diane Peters
Hi everyone, As regards CC0 and its use by the USG, you may find this comment we posted previously of possible interest and relevance. https://github.com/WhiteHouse/source-code-policy/issues/149 Diane Diane M. Peters General Counsel, Creative Commons Portland, Oregon

Re: [License-discuss] [Non-DoD Source] Re: [Non-DoD Source] Re: U.S. Army Research Laboratory Open Source License (ARL OSL) 0.4.0

2016-08-18 Thread Diane Peters
Copyright is not available for US government works as a matter of US copyright law (section 105), but that does not mean those works may not be restricted by copyright laws of other countries. Congress contemplated that expressly. “The prohibition on copyright protection for United States

Re: [License-discuss] Words that don't mean derivative work

2016-02-03 Thread Diane Peters
To the extent helpful, we at CC put a lot of thought into how to best define the notion of what constitutes a derivative work ("Adapted Material" in CC 4.0 vernacular) when we last versioned. We expressly tied it to copyright law. If a downstream licensee uses the work in a manner that implicates