Development of Creative Commons licenses

[email AT greglondon.com]

there is no "official" version of an Open Source work. The
idea is to give it away so others can expand upon,
improve, and modify the work as they see fit.

You can use 'branding' techniques to get people to
identify your version of the work as the version to use.

RedHat has branded themselves as "THE" place to get Linux,
even though Linux itself is Open Source and anyone can use
it.

If someone creates a derived version of your work, they
should keep your original copyright notice in place and
append their copyright notice to yours, so anyone getting
the derived version can see the notice and know its not
the original.

If you look at any open source files that have been around
for a while, you'll see a laundry list of copyright
notices as the files went through major revisions.

Copyright 2004 John Doe

Copyright 2001 Jane Smith

Copyright 1998 Alan Smithee

Copyright 1996 Original Author

This by itself should distinguish your version of the
document from any other version of the document. It's then
up to you to "brand" yourself as the best source to get
your document.

Greg London

Perl Training manual (licensed GNU-FDL)
http://www.greglondon.com/iperl/pdf/iperl.pdf

Drafting the Gift Domain (licensed GNU-FDL)
http://www.greglondon.com/dtgd/pdf/draftingthegiftdomain.pdf




Thomas Black said:
> Hi All
>
> I represent a non-profit organisation in South Africa
> doing work in
> promoting open source software in South Africa. We prove
> that open
> source software works within various contexts and then
> encourage risk
> averse organisations to continue our projects that work.

> Now, we want to relase all our strategy documents,
> reports, etc. under a
> CC license so that others can benefit from our work. The
> licence which
> seems to fit most naturally is the Attribution licence.
>
> Now, how do you enhance this license so that if an
> organisation makes
> changes to our original docs, all the changes are clearly
> indicated. For
> example, we're happy if people use our docs to develop
> their own
> strategies based on our work - what we don't want people
> to do is make
> changes to our strategy docs and then distribute them,
> without the
> recepient knowing that these are now 'unofficial' docs?
>
> Help with this would be great appreciated.
>
> -Thomas
>
> --
> Thomas Black
> Open Source Program Manager
> The Shuttleworth Foundation
> Tel. +27 21 9701208
> Fax. +27 21 9701209
> http://www.shuttleworthfoundation.org/oscp/
>
> _______________________________________________
> cc-licenses mailing list
> cc-licenses AT lists.ibiblio.org
> http://lists.ibiblio.org/mailman/listinfo/cc-licenses
>


-- 
Do What I Mean and
Autovivification
Sometimes Unwanted