Creative Commons - User contributions [en]

Marking your work with a CC license

2013-09-25T10:10:11Z

Beritaharian:

==Best Practices for Marking Content with CC Licenses: Creators ==

<div style="padding: 2%;margin:0em 0em 1em 0em; border:1px dotted red; background:#eee; width:60%">
NOTE: This page is for creators and copyright owners who are looking to CC license their own work. If you are looking for the best way to mark CC-licensed work as a user, see http://wiki.creativecommons.org/Marking/Users. If you own a content-sharing site or platform that hosts works by other creators and are interested in enabling CC licensing for your users, see http://wiki.creativecommons.org/Web_Integration.
</div>

As a creator using a CC license, it is important to properly note the license you have chosen so that others know what they can and can't do with your work. No matter what the context, CC licenses should be clearly cited to enable their full potential as a legal tool.

==Marking on Your Site==
Our [http://creativecommons.org/choose/ license chooser] is designed to make this process simple - answer a few questions and a formatted HTML code will be generated for you:

# Insert this HTML code into your webpage so that your work is clearly marked.
# This HTML code includes [http://wiki.creativecommons.org/Rdfa RDFa], a very important aspect of marking your work so that others can find it easily.

The specifics of inserting the code depend on how you edit your website. The block of code should be inserted into the page HTML - most desktop website tools like Dreamweaver, Frontpage, or GoLive offer a "code view" that lets you see the code that makes up your page. Near the end of the page before you see </body></html>, paste the HTML code in directly.

If all of the resources you are publishing on a single website are licensed under the same CC license, it makes sense to paste the HTML code into your website’s template (e.g., in a footer or sidebar area). After saving the template, the chosen license information should appear everywhere on your site. Whether you add license information to a single page or an entire [http://contactspro.net/purple-contacts/ site], once live on the Internet, the license information will be displayed and the machines will be able to detect the license status automatically.

From there, here are three steps to license notice perfection:

# The full URI (link) to the license. Example: http://creativecommons.org/licenses/by/3.0/us/.
# A visible notation (most commonly text) that states the license being used. Example: Except where otherwise noted, content on this site is licensed under a Creative Commons Attribution 3.0 License.
# Optionally, the appropriate Creative Commons license button or CC icon and license property icon(s).

{| cellspacing="5" cellpadding="10" style="padding: 2%;margin:0em 0em 1em 0em; border:1px dotted red; background:#eee; width:100%"
|
NOTE: Because each CC license represents a different set of permissions and restrictions, it is important to note the specific license used. Displaying only the CC icon, “Creative Commons”, or “Some Rights Reserved” is insufficient; always include the full URL.
|}
In order for others to credit you for your work, it is preferable to provide an attribution name and URI. The [http://creativecommons.org/choose/ license chooser] provides the proper license button (if you fill in attribution fields) as well as RDFa attribution data. Alternatively, high resolution buttons and license icons are available from [http://creativecommons.org/about/downloads our logo download page].

For example, see the following screenshot of a license notification that incorporates these best practices:

[[Image:By_small.jpg]]
<br/><small>This work by [http://opencontent.org/blog David Wiley] is licensed under a [http://creativecommons.org/licenses/by/3.0/us/ Creative Commons Attribution 3.0 United States].</small>

If you visit David's [http://opencontent.org/blog/ blog], you will see this notice at the bottom of the page. The license icon links to the license deed that includes attribution information specific to David. In this case, David filled out the attribution fields in the [http://creativecommons.org/choose/ license chooser], which provided the proper license button and formatted attribution information. He then pasted the resulting HTML code with RDFa into his webpage and included the textual notation of attribution and the specific license that you see above and kabar [http://www.liputan6.com/ berita hari ini] Liputan6.com.

Still confused? Take a look at our visual guide. See [[Website/Publish]] for step by step visuals of copying and pasting the HTML code. This page also contains the same information for pages that host a specific type of media ([[Publish/Audio|audio]], [[Publish/Video|video]], [[Publish/Images|images]], and [[Publish/Text|text]] -- which includes various [[Publish/Text#Blog|blogging]] platforms).

If your work is a derivative of another original CC-licensed work, be sure to look at our [http://wiki.creativecommons.org/Marking/Users Marking for Users] primer as well.

== Marking Specific Media ==

While remaining similar in intent, marking will vary depending on the medium. The following are some helpful tips on making sure your media is marked correctly.

For offline works in general, consider publishing a web page with licensing information about your material. Doing so enables your work to be found by search engines and other web discovery tools.

Below are general examples for each medium. If a more technical explanation is your goal, please see [http://wiki.creativecommons.org/Marking_works Marking Works (technical)]:

<div style="padding:1.25em 1em; margin-left:-1em; margin-right:-1em; -moz-border-radius:5px; -webkit-border-radius:5px; background-color: #eaeaea; overflow: auto;">
{{PageColumn|
===Offline Text===
<small>(for online text see [[Marking/Creators#Marking_on_Your_Site|Marking on Your Site]])</small>
*For documents that are meant to be shared in print format (not read online) it is suggested to use a title and/or copyright page to include the Copyright notice and CC license information.
**After going through the [http://creativecommons.org/choose/ license chooser], you can click on "Mark a document not on the web, add this text to your work" in the lower right column.
**And/or you can refer to this sample copyright notice: "Copyright (c) 2009 by Greg Grossmeier. This work is made available under the terms of the Creative Commons Attribution-ShareAlike 3.0 license, http://creativecommons.org/licenses/by-sa/3.0/."
*It is also suggested that you use a visual license notice. Here is a collection of visual markers that can be used:
**[[CC markers]] and [http://creativecommons.org/about/downloads/ official CC license icons]
**[[User submitted markers]]
* [[Publish/Text | Advanced Instructions: Text]]

===Image===
*Adding a watermark or other visual marker on an image can ultimately detract from the original. If you choose to, a safe method of indicating license choice consists of two actions:
**When publishing the image on a website, make sure that your license choice is clearly visible, preferably indicated with one of our [http://creativecommons.org/about/downloads/ license icons].
**Ensure search engines can see it also via the use of [[RDFa]], which you can copy and paste from the HTML code given to you by the [http://creativecommons.org/choose/ license chooser].
*Additionally, you can ensure that the image has [[XMP]] metadata support with your name, date, and license choice.
*[[Publish/Image| Advanced Instructions: Image]]
}}
{{PageColumn|
===Audio===
*For audio files, two actions are recommended:
**When publishing the audio file on a website, make sure that your license choice is clearly visible, preferably using one of our [http://creativecommons.org/about/downloads/ license icons].
**Ensure search engines can find it via the use of [[RDFa]], which you can copy and paste from the HTML code provided by the [http://creativecommons.org/choose/ license chooser].
*Additionally, you may want to ensure that the audio file has metadata support with your name, date, and license choice.
**One easy way to do this is to upload your file to music sharing site that has enabled CC licensing. See [[Marking/Creators#Marking on Other Sites|Marking on Other Sites]] below.
**Alternatively, you can use your favorite audio player to add in the information. To learn more see [[Embedded_Metadata]]. You can also see how to add ID3 tags to a common audio file type, such as the [[MP3]], or browse other [[UsingMarkup|file types]].
*Also, if it is practical to do so (for podcasts, for instance, not song tracks), add an audio bumper to the beginning of the file to indicate your choice of license. Here are some [http://creativecommons.org/podcasting intro bumpers] which you can use to build upon.
*[[Publish/Audio| Advanced Instructions: Audio]]

===Video===
*For movie formats that have the ability to include a 2-5 second copyright frame, it is advisable to use the same format as what is suggested for textual works:
**Sample Copyright notice: Copyright (c) 2009 by Greg Grossmeier. This work is made available under the terms of the Creative Commons Attribution-ShareAlike 3.0 license, http://creativecommons.org/licenses/by-sa/3.0/.
*Here is a collection of stills which can be used as license bumpers:
**[http://wiki.creativecommons.org/CC_video_bumpers Official CC bumpers]
**[http://wiki.creativecommons.org/User_submitted_bumpers Community Submitted bumpers]
*[[Publish/Video| Advanced Instructions: Video]]
}}
</div>

== Marking Specific Formats ==
* CC-[[OpenOfficeOrg Addin]] for [http://openoffice.org OpenOffice].
* To mark a Microsoft Office word document, you can use the Microsoft Office add-ins for [http://www.microsoft.com/downloads/details.aspx?familyid=113b53dd-1cc0-4fbe-9e1d-b91d07c76504&displaylang=en Office 2003/XP] or [http://www.microsoft.com/downloads/details.aspx?FamilyID=d1ddbdc8-627f-415a-9b0a-97362bc9b480&displaylang=en Office 2007]

== Marking on Other Sites ==

===[[Publish]]===

One way to increase visibility and access to your work is to share it with an existing community. Many content platforms have already enabled CC licensing, making it easy for you to indicate the license along with other information, such as who to attribute. In addition, search engines like Google and Yahoo! will index your work as CC licensed if the [[metadata]] is properly attached.

[[Publish]] your work in an existing community.

== Marking third-party content in your work ==
Marking best practices also apply for any third party content your work incorporates. If you are incorporating another person's work, even if used under fair use or other exception or limitation to copyright, then you should be sure you are allowed to incorporate that work. Third party content may be offered under the same or different terms, such as other CC licenses or "all-rights-reserved" copyright. If you are permitted to use the work and it is offered under a CC license, then you should consider adhering to best practices for marking that content as a user, available at [[Marking/Users]]. We also offer additional explanation and tips on [[Marking/Creators/Marking_third_party_content|marking third-party content]]. Note that for all third party material accompanying or used with your CC-licensed work, that material is not covered by the terms and conditions of the CC license that '''''you''''' apply, it remains under the terms of the license (if any) that applies to it.

Laser hair removal machines UK supplies and sells some of the world’s leading laser and IPL machines.

http://www.laserhairremovalmachinesuk.com

== External Links ==

*[http://creativecommons.org.au/marking/examples Marking Examples] explaining metadata from [http://creativecommons.org.au Creative Commons Australia]

== Things to note ==
When marking your work, remember that any restriction or modification to the original license cannot be labeled a 'Creative Commons’ license. See http://creativecommons.org/policies#license.

{{Best Practice}}

[[Category:Marking]]
[[Category:Licensing]]
[[Category:Community]]
[[Category:Media]]
[[Category:HOWTO]]
[[Category:Guide]]

4.0

2013-09-25T10:07:30Z

Beritaharian:

CC has embarked upon a versioning process for its core license suite, which will result in version 4.0. The first public discussions of 4.0 were held at CC's [[Global Summit 2011]]. The public process was kicked off with a [http://creativecommons.org/weblog/entry/29639?utm_campaign=newsletter_1111&utm_medium=blog&utm_source=newsletter blog post] laying out some of the key reasons for pursuing 4.0 at this time.

Since CC's launch in 2002, it has versioned its core license suite [[license versions|three times]], the last ([[Version 3|3.0]]) in early 2007. CC licenses constitute a [http://creativecommons.org/who-uses-cc globally-recognized framework], developed in consultation with legal experts and CC affiliate institutions in [[CC_Affiliate_Network|over 70 jurisdictions]]. Over 500 million CC-licensed works have been published by their authors on the Internet. Today, Creative Commons licenses, public domain tools, and supporting technologies are the global standard for sharing across culture, education, government, science, and more like kabar [http://www.liputan6.com/ berita hari ini] Liputan6.com.

Version 4.0 is a tremendous opportunity to ensure the license suite is ideally crafted to further CC's [http://creativecommons.org/about vision and mission] over the next decades. Please participate in this important discussion.

=== Goals and objectives ===

Creative Commons staff, board, and community have identified several goals for the next version of its core license suite, tied to achieving CC's goal and mission. These include:

:: ''Internationalization'' – further adapt the core suite of international licenses to operate globally, ensuring they are robust, enforceable and easily adopted worldwide;

:: ''Interoperability'' – maximize interoperability between CC licenses and other licenses to reduce friction within the commons, promote standards and stem license proliferation;

:: ''Long-lasting'' — anticipate new and changing adoption opportunities and legal challenges, allowing the new suite of licenses to endure for the foreseeable future;

:: ''Data/PSI/Science/Education'' — recognize and address impediments to adoption of CC by governments as well as other important, publicly-minded institutions in these and other critical arenas; and

:: ''Supporting Existing Adoption Models and Frameworks'' – remain mindful of and accommodate the needs of our existing community of adopters leveraging pre-4.0 licenses, including governments but also other important constituencies.

=== Organization and purpose of this wiki ===

This wiki is the central location for documenting key discussion topics and suggestions for improving the license suite in version 4.0, together with supporting information and relevant links[http://double-oven-reviews.com/ .] It is intended to supplement, not replace, the CC license discuss email list [http://lists.ibiblio.org/mailman/listinfo/cc-licenses (subscribe)] that will serve as the main discussion forum for the versioning process just as it has with prior versioning efforts.

CC has prepared pages on key topics identified to date. We ask contributors to be thoughtful about placement of additional and related topics, as well as the creation of new pages altogether. Before starting a new page, consider posting the suggestion to the [[4.0/Sandbox|Sandbox]]. We would also prefer that contributors use their real names when editing the wiki.

=== Process ===

As a license steward and steward of the commons, our goal for the process is to ensure utmost transparency and inclusiveness. The 4.0 process is being conducted in line with our prior versioning efforts, with periodic publication of license drafts for public comment and documentation of issue resolution as that occurs[http://becoming-a-psychiatrist.org/ .] One important difference from our past efforts, however, was a formal requirements gathering period that ran for a period of time prior to publication of the first draft. During this period, we strongly encouraged the broadest participation possible by everyone with an interest in the commons and the role open licensing plays in its future.

The primary discussion forum for issues relating to the 4.0 versioning process will be the CC license discuss email list. Please [http://lists.ibiblio.org/mailman/listinfo/cc-licenses subscribe] and add your voice to this important effort.

=== Draft timeline ===
The dates noted below are approximate and subject to change. The number of drafts and public comment periods may vary depending on the number and type of issues raised and how they are resolved, among other things. Watch this page for updates, including major events such as affiliate regional meetings where 4.0 discussions will take place.

{| class="wikitable" style="width: 75%; height: 200px" border="1"
|-
| September 2011
| [https://creativecommons.org/weblog/entry/29639 Launch 4.0 process] at CC Global Summit
|-
| December 2011 thru mid-February 2012
| Requirements gathering period
|-
| April 2, 2012
| Publish [[4.0/Drafts#Draft_1_Details|first draft of 4.0]]
|-
| April to June 2012
| [[4.0/Draft_1/Regional_calls|Public comment]] period #1
|-
| August 2012
| Publish [[4.0/Drafts#Draft_2_Details|second draft of 4.0]]
|-
| August 2012 to February 2013
| [[4.0/Draft_2/Regional_calls|Public comment]] period #2
|-
| February 2013
| Publish [[4.0/Drafts#Draft_3_Details|third draft of 4.0]]; begin porting consultation
|-
| February to September 2013
| [[4.0/Draft_3/Regional_calls|Third public comment period]]; porting consultation
|-
| September 2013
| Publication of [[4.0/Drafts#Draft_4_Details|fourth and final draft]]; begin abbreviated final public comment period
|-
| September/October 2013 (expected)
| Finalize and publish version 4.0 license suite
|}

Various aspects of the license suite are being improved in the version 4.0 licenses. We are gathering and rigorously debating and analyzing these items, and corresponding proposals for handling them, in version 4.0. We encourage the broadest possible engagement in this process. This was a particularly important goal during the requirements gathering stage where everyone was strongly encouraged (and our affiliates expected) to provide feedback on proposed changes and suggest other changes they would like to see. You may add, improve, and discuss specific items in the pages linked below.

'''If you do not find a suitable existing page and category for an item you would like to propose or discuss, please add it to the [[4.0/Sandbox]] where suggestions for new pages will be aggregated.'''

Finally, we encourage contributors to take the time to review [http://wiki.creativecommons.org/License_Versions prior versioning efforts], including relevant discussions of important topics previously debated by the CC community and discussions related to their resolution. Being aware of and taking those into account is important to an effective and efficient process, particularly where a request is made to revisit and potentially change direction in 4.0.

{{#ask:[[Category:4.0 Issues]] [[:+]]
|mainlabel=Item/Category Name
|format=broadtable|
=== Items for discussion ===
}}

===Related pages===
:[[4.0/Sandbox|4.0 Sandbox]]
:[[Porting Project]]
:[[4.0 Drafts]]
:[[4.0/Draft_1|4.0 Draft 1]]
:[[4.0/Draft_2|4.0 Draft 2]]
:[[4.0/Draft_3|4.0 Draft 3]]
:[[4.0/Draft_4|4.0 Draft 4]]
[[Category:4.0]]

Integrate

2013-09-25T10:03:17Z

Beritaharian:

__NOTOC__
<div style="font-size:125%; line-height:1.75em; margin-bottom:1.75em;"><strong>Integrating Creative Commons License Information:</strong> One of the most useful attributes of using Creative Commons licenses is the quality metadata standards that can be used to both mark and identify CC licensed work. This can be anything from simply adding the ability for a media player to show the license information of a song to a full-fledge, RDFa using, semantic-web promoting web application for people to upload, share, and remix content.
<br />
Creative Commons is devoted to making it easy for developers to add license metadata functionality to all types of applications. Our tools are divided into two areas; Desktop and the Web with kabar [http://www.liputan6.com/ berita hari ini] Liputan6.com.
</div>

<div style="padding:1.25em 1em; margin-left:-1em; margin-right:-1em; -moz-border-radius:5px; -webkit-border-radius:5px; background-color: #eaeaea; overflow: auto;">
{{PageColumn|
== [[Desktop Integration]] ==
Much of the functionality that is needed to integrate CC license information with desktop applications is available in the [[liblicense]] package. There is also [[License tagger|License Tagger]] which is a small proof of concept application written in python that utilizes [[liblicense]] to embed license metadata information into files. For more information see the main [[Desktop Integration]] page.
}}
{{PageColumn|
== [[Web Integration]] ==
Creative Commons has developed [[LicenseChooser.js]] which provides a lightweight method for integrating license selection into web applications. It does this by utilizing such technologies as [[RDFa]]. Additionally, Creative Commons has also developed a [[Web Services]] interface that can be used to enable license selection in online services. For more information, see the main [[Web Integration]] page.
}}

=== See also: [[Developers]] ===
</div>

<br clear="all"/>

[[Category:Developer]]

Developers

2013-09-25T10:02:38Z

Beritaharian:

'''Welcome to the CC Developer Community!''' This is where you'll find all
about the technologies and software products that CC uses to push
forward our mission to maximize digital creativity, sharing, and
innovation.

== Get Involved ==

All of the projects developed at Creative Commons are open source
software, and just like most open source projects, outside involvement
is key to its success. But you don't have to be a software developer
to join us--we'd love to have you in the discussion if you're a user
researcher, designer, translator, or just interested in the topic.

; E-mail
: Join our [http://lists.ibiblio.org/mailman/listinfo/cc-devel mailing list]
; IRC
: Chat with us real-time on [irc://irc.freenode.net/cc irc] (Freenode, #cc)

Coming soon: public team meetings, and other ways to engage.

== Projects ==

; [[OpenHome]]
: A Creative Commons homepage with your content
; [[Summer of Code 2013|Google Summer of Code 2013]]
: Ideas and more.
; [[Translate|Localization]]
: Find out how to help the Creative Commons community with translations.

== Core Technologies ==

; [[RDFa]]
: Standard for adding machine-readable statements to web pages.
; [[CcREL]]
: Language for adding licensing [http://combinest.blogspot.com/ information] to web pages.
; [[LRMI]]
: Language for describing educational resources on the web like kabar [http://www.liputan6.com/ berita hari ini] Liputan6.com.
; [[Liblicense]]
: Library for embedding licensing metadata into files of various formats. (note: now somewhat out of date!)

<br clear="all"/>

{{Translations
| articles = Pt:Programadores, Ru:Разработчикам, Vi:Phát Triển Viên
}}

[[Category:Developer]]

__NOTOC__

Broadcasting

2013-09-25T09:55:25Z

Beritaharian: /* links (to be moved elsewhere) */

{{Project}}

This page collects information about the interaction between various Creative Commons jurisdiction projects and broadcasters. It provides an overview of jurisdictions where broadcasters are using Creative Commons licenses ('[[#Projects|Projects]]') and of jurisdictions where there are talks between the jurisdiction project and a broadcaster in order to achieve this goal ('[[#Negotiations|Negotiations]]').

== Priorities ==

# Increase usage of CC license in jurisdiction
# ...

'''NOTE: When interacting with broadcasting representatives it is important to be cordial with them and provide information about Creative Commons usage (see [[Case_Studies|case studies]], [[Documentation|documentation]] and [[Metrics|metrics]]) and integrating Creative Commons licenses (see: [[CCPlus|CC+]], [[CcREL]] and [[Web_Integration|web integration]]). Be be mindful of the overall [[#Priorities|priorities]] and ensure that you are in line with the arrangements made as part of ongoing [[#Projects|projects]]'''

==Projects==

* [[Broadcasting/Denmark]] [http://www.dr.dk/ Danish Broadcasting Corporation] features CC-licensed images and content on its website, and it was the first broadcaster to purchase and air the CC-licensed documentary, Good Copy Bad Copy.
* [[Broadcasting/Germany]] In November 2007 the Norddeutscher Rundfunk (NDR), a public radio and television broadcaster in Germany’s national broadcasting consortium ARD, [http://creativecommons.org/weblog/entry/7838 announced] that they will use CC licenses for some of their programs.
* [[Broadcasting/Netherlands]] VPRO [http://creativecommons.org/weblog/entry/18128 released] 2 full length (and one more coming soon) documentaries under CC-BY-NC-SA licenses, aired 10 days prior. VPRO has also implemented CC licenses for its [http://3voor12.vpro.nl/plundertmusea/kaft/index.jsp 3voor12 Plundert Musea] project, which makes available samples from rare musical instruments, and furthermore the Dutch broadcaster also promotes CC music on its radio show [http://www.vpro.nl/programma/wissel/ Wissel].
* [[Broadcasting/Norway]] November 27, 2009 [http://nrkbeta.no/2009/12/18/bergensbanen-eng/ over 1,2 million Norwegians watched] parts of “Bergensbanen” on NRK2. The clip was released under CC BY-SA in HD over BitTorrent, and a successful competition allowed for remixes. The project was featured on prominent sites such as [http://boingboing.net/2009/12/19/norwegian-public-bro.html BoingBoing].
* [[Broadcasting/Switzerland]] http://openbroadcast.ch has the has the night Sunday/Monday (00:00 - 06:00) dedicated to CC music only (http://openbroadcast.ch/de/program).
* [[Broadcasting/UK]] To date, several departments in the BBC publish content under Creative Commons licenses: album reviews ([http://www.bbc.co.uk/music/release/c2w6/ for example]) and a partnership with MusicBrainz, a community music metadatabase that uses CC licenses. Furthermore, under other licensing conditions, the BBC has opened up its website to developers at backstage.bbc.co.uk. It also offers television and radio programs to stream or download through its iPlayer, although the player’s format has been the source of some criticism.
* [[Broadcasting/Colombia]] Although a small experience, [http://altair.udea.edu.co/ Altair] is a good example of CC use in broadcast sector. Altair is the hipermedia and sound lab of the Antioquia University that is located in Medellin- Colombia (second biggest public university in the country). All their programs are CC, they use and promote CC material (music mainly) and they adopt CC BY NC SA for their own productions.

==Negotiations==

* [[Broadcasting/Australia]]
* [[Broadcasting/Denmark]]
* [[Broadcasting/Germany]]

=== links (to be moved elsewhere) ===
* kabar [http://www.liputan6.com/ berita hari ini] Liputan6.com
* http://cc.aljazeera.net/ - select broadcast quality footage that Al Jazeera has released under various Creative Commons licenses, mostly CC BY.
* KQED's QUEST uses CC licenses for its photostream: http://www.flickr.com/photos/kqedquest/. More info at http://creativecommons.org/weblog/entry/8577 [http://www.sepatuonline.org sepatu pria] [http://www.jualjaketkulit.org jual jaket kulit] [http://www.sepatufutsalmurah.org sepatu futsal] [http://modifikasiku.info modif motor] [http://www.jualjaketkulit.org/daftar-harga-mobil-toyota-terbaru-2013.html harga mobil toyota 2013]

Kenya

2013-09-25T09:47:23Z

Beritaharian:

{{Jurisdiction
|jurstatus=Active
|country code=ke
|twitter=http://twitter.com/CCKenya
|region=Africa
|affiliated=CIPIT, Strathmore Law School
|affurl=http://www.cipit.org
|afffocus=Intellectual Property, Information Technology
|afftype=academic institution
|affiliated2=National Council of Law Reporting
|affurl2=http://www.kenyalaw.org
|afffocus2=Kenyan Courts and Laws
|afftype2=governmental body
|plead1=Michael Murungi
|pemail1=mmurungi@kenyalaw.org
|ptitle1=Chief Executive, National Council for Law Reporting
|plead2=Isaac Rutenberg
|pemail2=iruten@gmail.com
|ptitle2=Director, CIPIT
|plead3=Lillian Makanga
}}
AFFILIATE TEAM ROADMAP, CREATIVE COMMONS
Jurisdiction: Kenya (East Africa - Africa)
Date submitted: 6 March 2013
Timespan of this roadmap: January 2013 to December 2013

Public lead: Centre for Intellectual Property and Information Technology law (CIPIT)

Dr. Isaac Rutenberg [Intellectual property and Social media] (Director and Lead Consultant) holds a J.D. from Santa Clara University School of Law (California, 2011) and a Ph.D. in Chemistry from California Institute of Technology (2005). He is a Registered Attorney with the California State Bar and he is registered to practice before the US Patent and Trademark Office and [http://www.liputan6.com/ berita hari ini] Liputan6.com.

Lillian Makanga Wothaya [Research and evangelism] holds an LLB (Hons) degree from the Catholic University of Eastern Africa (CUEA) a post graduate diploma in law from the Kenya School of Law and currently awaiting admission to the Bar as an Advocate of the High Court of Kenya. She has previously worked at MMC Africa Advocates where she gained experience in the practice of Intellectual Property Law as well as other legal disciplines. As part of CIPIT she is involved in the IP Clinic which provides legal advice and cost effective solutions to innovators on all aspects of their IP Rights. In addition, she analyses developments in Kenyan and International IP Case law as well as the implications on the Intellectual Property Landscape.

Douglas Gichuki [Open data and IT policy] (Research Fellow and Assistant Lecturer). Mr Gichuki holds an LLB degree from CUEA and an LLM in Intellectual Property, Information Technology and Internet Law from Norwich Law School (UK). His doctoral research focuses on legal frameworks for financing small to medium enterprises in technology.

Pelase Visit:

* [http://adrian-fh98.web.unair.ac.id/ Informasi Umum]
* [http://www.tokobungasabana.com Toko Bunga]
* [http://andreweweww.wordpress.com/ Curhat Blog]
* [http://mariposa-store.com/ Jual Sepatu Online]

Legal lead: National Council for Law Reporting

Mr . Michael Murungi [Information technology specialist] is a manager, law reporter and ICT legal expert from Kenya. He is the Chief Executive/Editor of Kenya’s National Council for Law Reporting, the official publisher of Kenya’s public legal information, including the decisions of the superior courts of Kenya and the Laws of Kenya. He is the author of Cyber Law in Kenya and Kenya's designated contributor to Wolter Kluwer’s International Encyclopaedia of Cyberlaw. He has been a legal columnist for CIO, East Africa’s premier ICT magazine and a lecturer in cyberlaw at the Catholic University of Eastern Africa. He made key contributions towards the enactment of the Kenya Communications (Amendment) Act, 2009. He has undertaken local and international consultancy and speaking engagements. Michael holds a Masters Degree in ICT law and has professional training in legal practice, management and arbitration

Mr. Alex Gakuru [Regional coordinator Africa] is the Founder and Chair of ICT Consumers Association of Kenya, an ICT consumer rights advocacy group. He is the Executive Director-Content Development and Intellectual property (CODE-IP) Trust, a non-profit organization focusing on creating an enabling environment for local content development and its intellectual property protection. He is an assertive advocate of consumer rights and he represents consumer interests through various platforms locally and internationally. He is an Elected Council Member at the Free and Open Source Software Foundation for Africa and he took part in global Internet Policy formulation as the elected Africa’s representative at ICANN’s Non-Commercial Users Constituency Executive Committee (NCUC). His NCUC term ended in December 2013. Since August 2012, he is the Regional Coordinator – Africa for Creative Commons.

Sponsor :
- [http://www.optimaweb.co.id/ Internet Marketing]
- [http://www.optimaweb.co.id/jasa-seo Jasa SEO]
- [http://www.optimaweb.co.id/iklan-online-google-adwords Iklan Online]
- [http://www.optimaweb.co.id/bisnis-online-lokal Bisnis Online Lokal]
- [http://www.optimaweb.co.id/promosi-website Promosi Website]

Date of latest MOU in jurisdiction N/A

Vision

Why is Creative Commons important for the jurisdiction?

Kenya is home to a thriving cultural industry. These varied creatives require access to shareable resources that facilitate remixing and creativity. It is, however, important to deepen the understanding of new users in Kenya of CC licenses and their usefulness. The increasing use of CC licenses in Kenya will help enhancing the visibility and accessibility of Kenyan creativity in the global networked space.

Kenya is also home to a vibrant if querulous democracy. We are a multi ethnic society comprising 42 odd communities. We hope to harness the wealth that can come from such cultural and linguistic diversity through the creative commons movement. Kenyans are marked in their early adoption of technology to enhance the democratic discourse, examples of these include the shoot from the hip activism of #KOT (Kenyans On Twitter). We hope to use CC licensing in Kenya to support newly realisable democratic freedoms through new media conversation and mobilizing and by enabling wide-spread access to knowledge and information.

What do you think makes a successful jurisdiction project?

A successful jurisdiction project effectively promotes the use of CC licenses in their jurisdiction for the benefit of the various communities in the country. We wish to do this by bringing what is good of these communities to the wider African and global market; translating CC license deeds into local languages is in our opinion key for achieving this.

How do you see the jurisdiction project contributing to the CC Affiliate Network?

We want to help adding to the commons local content and a variety of indigenous and contemporary Kenyan works available under CC licenses.

Community

Describe the communities that are currently active in the project.

1. Educational institutions – schools, universities, colleges, etc.
2. Libraries
3. Cultural institutions – museums, galleries, etc.
4. Government organizations
5. Technology-based companies
6. Open data and technology-focused communities
7. Professional Associations & non-profits
8. Creators – artists, photographers, media producers.

How will you continue to engage with these communities?

We will increase our engagement through: Conference talks & workshops, a Kenyan CC website, Twitter, supporting interested parties with implementing CC licenses.

Describe the communities (existing or new) that you plan to focus on during the timeframe covered by this roadmap?

Target organizations: Bloggers Association of Kenya; KECOBO; The Creativez; Power 254, Media houses; technology hubs such as iHub; Universities; and civil society such as FOSSFA.

How do you plan to engage with these communities?

• Use of social media to establish a linked CC Kenya affiliate
• Implementation of a Creative Commons website
• Case studies and showcase examples
• Compilation of list of Kenyan organizations & individuals using Creative Commons
• Development of a copyright, open licensing course delivered online and face-to-face at the CIPIT
• Open licensing salons, webinars, conference presentations, and events
• FAQ, how-to’s and practical guides to aid decision making and implementation
• Policy guidelines and recommendations
• Development and profiling of business models related to use of Creative Commons, for instance the freemium model.
• Making the case to government institutions for an open license for government content by using the National Council for Law Reporting as a demonstrative case study.

Priority Goals

What are the most important focus areas on which the Affiliate Team will work during this time period?

Focus area: Outreach and deepening license knowledge and use

• Given the newness of the CC team in Kenya, it is essential to build a strong community that understands the licenses, promotes sharing and remix culture. This would be a good starting point to better inform and deepen the use of the CC licenses and to spread their benefits.
• We also wish to have a more diffused knowledge of the CC licenses in the jurisdiction. This includes encouraging the community to adopt the free licenses in distributing their work and expanding gradually to other areas.

Focus area: Legal interface

• As the Legal Lead, the NCLR will drive the CC Kenya team in interfacing with the legal and government communities. All CC work and information will be located on (or linked from) the NCLR website to be accessed freely by the public. Other legal issues will be addressed and dealt with as appropriate.

Focus area: Application of CC to various topics of interest

• At the CC Africa Regional Meeting in 2012, a number of topics were identified as of critical importance to engage with CC and the CC Kenya team. These included open education resources, government adoption, health, advocacy, ICT development, business models, and transparency.
• The CC Kenya team will actively engage stakeholders such as the School of Open and the Open Data initiative within the Government of Kenya to see that the above topics are areas of focus.

Focus area: Website development and update

• This includes things like: a collection of case-studies or organisations using CC in Kenya (wiki); Acknowledge all CC KE volunteers and organizational supporters; Put more information about Creative Commons Licensing. This also involves the building of a mailing list through which we can keep the community informed and updated.
• Why is it important? This will be a key source of information about Creative Commons Kenya.
• Who benefits? All CC Kenya stakeholders

Focus Area: Increased engagement with International and regional stakeholders

• Frequent interaction with already established CC organizations will hasten the progress of this project. We are confident that tapping into the experience of existing CC communities will enrich the growth of the project through their support and contribution.

Focus area: In-depth training of selected individuals

• There exists a critical need in the region for individuals with in-depth training in areas of copyright, licensing, and business development around the CC philosophy of open access. This level of knowledge exceeds the basic understanding that is needed by most users of CC licenses. Typically, this level of specialized knowledge resides in lawyers or other IP specialists, but such knowledge is not common in East Africa.
• We will address this need primarily through training of interns at CIPIT and/or NCLR. One or more interns will be engaged and tasked with learning the necessary background and practical knowledge to be able to advise CC users. It is hoped that the intern(s) will use the skills gained to further the CC cause even after their internship is completed.

Focus Area: Identify source(s) and secure funding for a Creative Commons Kenya affiliate

• While we will largely engage volunteers for a lot of the CC work, a basic minimum level of funding will be required to establish a physical presence and at least partial support for some people and activities. Localizing legal tools, promoting public awareness, translation of licenses to local languages, building out a web presence, all require funding and effort. Our focus must therefore include finding and securing core base level of funding.

Project Outputs

Detail tangible project outputs (e.g., events, papers, blog posts, video/films, etc.) for each focus area including an expected date of completion.

Focus Area: Outreach and Increasing License Use

• Project Output: Events / Blog posts / video & photo coverage of the events. Also FAQs and a practical manual (i.e., a toolkit) located on the CC Kenya website.
• Expected start date - Expected date of completion: February to November 2013.
• Team Member(s) Responsible: ALL, spearheaded by the Public Lead
• How will this output help achieve your goals? Face to face meetings will help us improve the concept of a local community and will help us understand what are the community needs in our area.
• Tentative schedule of events to be provided.

Focus Area: Legal standardization

• Project Output: translation of the license summaries; CC content available or linked on NCLR website, synchronized CC public sensitization events and create an interactive blog
• Goal of Output: To secure government support & provide information to the public; to provide translated licenses
• Expected start date: February 2013
• Expected date of completion: continual
• Team Member(s) Responsible: NCLR

Focus area: Application of CC to various topics of interest

• Project Output: Engagement of the CC initiative with stakeholders in various sectors including music, publishing, film, government, and academia.
• Goal of Output: Increased awareness that CC principles apply beyond the legal field
• Expected start date: March, 2013
• Expected date of completion: 2013
• Team Member(s) Responsible: Douglas Gichuki, Michael Murungi

Focus area: Website

• Project Output: Modern website with features such as a news feed, information about Creative Commons, and a spotlight on Creative Commons content & initiatives in Kenya.
• Goal of Output: To connect with the public & provide information.
• Expected start date: March, 2013
• Expected date of completion: 2013
• Team Member(s) Responsible: Douglas Gichuki

Focus Area: International and regional engagement

• Project Output: material support, active consultancy engagement with regional and international stakeholders (e.g., CC affiliates across Africa, CC HQ, etc.)
• Goal of Output: to share experience and knowledge, cultivate interaction through international seminars and social media
• Expected start date: in progress
• Expected date of completion: continual
• Team Member(s) Responsible: Dr. Isaac Rutenberg

Focus Area: In-depth training

• Project Output: One or more individuals with significant training in the areas of copyright law, licensing, business development based on the Freemium model, etc.
• Goal of Output: To begin the process of creating a community of highly-trained individuals who are able to spread the use of CC licenses, advise users of the licenses, and continue training others in such areas.
• Expected start date: March 2013
• Expected date of completion: continual
• Team Member(s) Responsible: Dr. Isaac Rutenberg

Focus Area: Fundraising

• Project Output: Kshs awarded/granted
• Goal of Output: To secure sustainable funding.
• Expected start date: February 2013
• Expected date of completion: ongoing, but the first round of applications to be completed in April 2013
• Team Member(s) Responsible: All.

Metrics

• How will you evaluate your impact on focus-area 1 (Outreach)? Number of participants at the events & stakeholder groups represented. Numbers of documented cases using CC licenses.
• How will you evaluate your impact on focus-area 2 (Legal Standardization)?
The availability, download rate, and number of known links to CC licenses will be the primary factor in evaluating this area. Other measures include interactions with the creative community and inquiries by would-be users.
• How will you evaluate your impact on focus-area 3 (Application to various topics)?
Frequency of engagement with the sectors identified in this Roadmap; case studies of such engagement.
• How will you evaluate your impact on focus-area 4 (Website)?
Website traffic (eventually, as the site garnishes attention). Also, average number of new posts per month and average number of updates per month.
• How will you evaluate your impact on focus-area 5 (International and regional interaction)?
The number of International meetings/seminars/interactions engaged per annum and internal audits done per annum to measure conformity progress with CC international standards.
• How will you evaluate your impact on focus-area 6 (In-depth training)?
The skill level and competency of the intern(s) trained by CIPIT and/or NCLR will be evaluated to determine impact.
• How will you evaluate your impact on focus-area 7 (Fundraising)?
We will measure this area by our ability to meet our financial needs via funds raised.

Resources Required

What human resources or expertise must the team seek out or add to your existing resources, if any, in order to achieve your priority goals?

• Creative Commons Kenya has commenced operations with the team members described in the "Affiliate Team Information" section. These team members already cover a wide spectrum of expertise. We will seek to add to this expertise if and when the need arises. We will also work on building a broad network of volunteers and supporters.
• We will seek out and engage one or more interns to learn the in-depth knowledge and training identified in the above goals.

How will you involve these people?

• Some involvement is already present. We will have bi-monthly meetings and supporters will be acknowledged on the website.
• We will call for volunteers and interns through announcements on the website, social media, and in universities.

What technology resources must the team seek out or add to your existing resources, if any, in order to achieve your priority goals?

• Website development will require an experienced website developer and possibly an individual with artistic design experience.

How will you obtain these technology resources?

• We will advertise a call for volunteers and may seek assistance from the IT department at Strathmore and/or other universities.

What material resources must the team seek out or add to your existing resources, if any, in order to achieve your priority goals?

• Generally, there is a lack of practical and instructional information available to would-be users of the CC licenses in Kenya. The CC Kenya website will be a perfect forum for disseminating such information, which we plan to generate as a collaborative effort between the Public and Legal Lead organizations. For example, CIPIT has been developing a practical manual of IP identification, acquisition, and use. This model can be adapted and a similar manual will be created for the CC Kenya website. Furthermore, we will generate a FAQ section that will help CC Kenya reach those in most need of basic assistance.
• From a variety of recent events such as the launch of the School of Open, it has become clear that there are numerous individuals in Kenya with an interest in driving the success of an open content platform. There is not, however, a centralized list of such individuals. We will create such a resource and make it available on the CC Kenya website.
• We were very happy to have received SWAG from CC international for our inaugural CC 10 birthday event in Nairobi. These were very popular. We will be requesting more support of this kind from CC International.

How will you obtain these material resources?

• The manuals and FAQ content will be generated in-house at the Public and Legal Lead institutions.
• Advertising and promotional materials will be requested via mail from CC.

How will you ensure your goals will be completed if unforeseen circumstances interrupt the project, such as changes in the leadership of the project or outputs taking longer to complete than anticipated?

• Regular meetings and open discussions among team members.

How will you communicate the project's on-going progress and setbacks within the jurisdiction and the CC Affiliate Network?

• Emails, ccAfrica mailinglist, our website, social media platforms, meetings
• Updates to the African Regional Coordinators

How will you document the project so that others may replicate or learn from your efforts?

• Creative Commons wiki and our website (and through all of the above communication tools for that matter)
• Comments on the roadmap

Collaboration

How could the jurisdiction's plans help drive or support other jurisdictions' activities?

• CC Kenya follows on an illustrious list of African jurisdictions using CC. We have the good examples from South Africa, Nigeria, Egypt, Uganda and others to learn from. We intend to actively court these CC jurisdictions for mentoring to assist us especially with the use of the 4.0 license.
• We intend however to document our experience of setting up a CC affiliate team and disseminate it freely for other jurisdictions considering setting up such teams. We also intend to collaborate and offer support for sister CC jurisdictions by participation in, e.g., face to face meetings and workshops.

What are other jurisdictions doing that might support or contribute to the project?

• We are enamored by the jurisdictions that have been able to build CC communities amongst very culturally diverse communities. CC Brazil and CC South Africa are good examples we want to learn from.

Would you be interested in mentoring new jurisdiction teams? Yes.

Conversely, would you be interested in having a mentor from a more experienced jurisdiction team? Yes.

Suggest three possible projects on which you can collaborate with other teams on a regional level.

The Kenya CC team hopes to contribute to collaboration in Africa by:
1. Networking with team members from other jurisdictions for example by inviting them to events in Kenya to share their experiences or sharing success stories broadly about the application of CC licenses.
2. In addition, the Kenya CC legal team is to work closely with colleagues from South Africa, Egypt and Nigeria, and Uganda who have in-depth knowledge of CC licenses through their experiences in license porting, and in the use of the current 3.0 license.
3. We would like to collaborate for the deliberations on the 4.0 license.

How do you plan to contribute to these projects? Sharing of information and on an ad-hoc basis.

Translation

In what language(s) will you promote CC in the jurisdiction and why? At this point in time, it is only feasible to promote CC licenses in English. Yet, we aim at translating the Commons Deed into Swahili. We also intend to have the deed translated to various local languages.

In which of these languages are licenses already available? English; the unported license.

CcMixter

2013-09-25T09:40:40Z

Beritaharian: /* Contests */

ccMixter uses [[ccHost]], an Open Source project sponsored by Creative Commons to build web infrastructure to support legal media sharing and remixing.

This page is to support ccMixter's use of ccHost:

----

== General ==

{{ContentDirectory|format=Sound|
mainurl=http://ccmixter.org/|
ccportal=|
ccfeed=http://ccmixter.org/rss/remix|
size=8871|
}}

* CC-only portal: everything is CC-licensed
* Notes: Runs on [[CcHost]], supports [[Sample Pool API]]
* Size last updated 20071006.

[[Category:Content_Directory]]

=== [[ccMixter Communication|Communication]] ===

=== [[ccMixter Press Releases|Press Releases]] ===

=== [[ccMixter Winner Announcements|Winner Announcements]] ===

=== [[ccMixter Roadmap|Roadmap / Timeline]] ===

== Procedures ==

=== [[Setting Up a Contest]] ===

=== [[Syncing Magnatune DB|Syncing Magnatune DB]] ===

== Administration ==

=== [[Restarting CC Mixter]] ===

=== Daily Administration Tasks ===

1. Read all forum posts -- look especially for:
:a. People reporting bugs/issues
:b. Flame wars

2. check out all uploads -- look for:
:a. Illegal media
:b. Mis-labled uploads ('sample' is really an a cappella)
:c. un-attributed remixes (uses samples from brad sucks but doesn't mark it as such)

3. handle requests/posts to cchost list

=== Regular ===

1. '''ccHost releases'''

2. '''mixter contests:''' at this point we can assume there will always be at least one contest in some stage of production -- currently we have the LisaD contest wrapping up and the Copyright Criminals one ramping up

3. '''Special projects:''' CC folks (like Mia and Mike) generate special deals/projects that need some kind of attenion.

4. Overall quality music quality management on mixter - this is a vague one but I spent a fair amount of time on a personal mission making sure the music on mixter was actually good -- reviewing/rewarding real
musicians/producers who upload.

=== Contests ===

==== Setting up a Contest ====

The process of creating a contest is basically like a wizard, admin
fills out some forms and a new virtual root is created with the relevant
tabs ('submit', 'entries', 'winners', etc.) the tabs visibility are
controlled by the dates of the contest.

The 'submit' tab is a form that knows how to add tags 'contest_entry'
and the contest name (e.g. '[http://www.articleeveryday.com/ free article directory]')

There is a 'submit entries' tab that only admins can see that mark the
uploads as [http://credit-protection.net credit protection] and the admin can additionally mark the
upload as the 'main source' or an extra upload (for stuff like loop
libraries or a cappellas, etc.)

the only part that's not automated is tagging the winners with the
'winner' tag (which I wrote a scriptlet for but that needs editing in
the winner's names and song title to work, so it's easier to just use
the admin screens for each song and click on 'winner' under 'system tags')

It's all pretty self evident except for this last part which could
probably stand to be part of a how-to faq on the wiki (which is the next part I added)

>>I guess the relevant pages for Magnatune were<br />
>>http://ccmixter.org/contests/magnatune/loops and<br />
>>http://ccmixter.org/contests/magnatune<br />
>> kabar [http://www.liputan6.com berita hari ini] Liputan6.com<br />
>>Were these pretty much custom creations for the Magnatune contest?<br />
>><br />

The contest 'about' tab has the default behavior of showing the contest
description, logo and with relevant dates including online polling
information. If there is an online poll for the contest, the current
results/tally is shown here. On Mixter we replace this default with our
own beautiful contest home page.

The 'sources' tab has the default behavior of listing out all uploads
with the 'contest_source' tags.

http://www.ccmixter.co.za/yfm/view/contest/sources

for Magnatune we replace the default behavior with a completely custom
engine because none of the source was actually on the site. We publish
the source to that in CVS but (up until now) isn't really part of the
mainline cchost installation.

> One other dumb question -- how did Magnatune "receive" the entries. You<br />
> just pointed them to http://ccmixter.org/magnatune/view/contest/entries<br />
> or did you package them in a zip or something else like [http://www.repairpartstock.com/ laptop repair parts] and [http://www.sepatuonline.org Toko Sepatu Online]?<br />
> [http://www.jualjaketkulit.org jual jaket kulit] - [http://modifikasiku.info modifikasi motor] - [http://kesehatan-ku.info kesehatanku] - [http://howtogetridofforeheadacne.blogspot.com/ treat for acne]

All contest entries end up in their own tree on the server (under the
local server path './contest/contest_name/user_name' as opposed to
'./people/user_name' (aka contrib). This lets you just zip up or ftp
point or whatever to just that directory.

For magnatune I wrote a script that, at one minute after the deadline,
zipped up the contest root and ftp'd the result to John's server[http://uslifeinsurancecompanies.com .]

==== Release Procedure Post-Contest ====

''The contest process is mostly automated except for the final stage of publicity.''

* Make release page
* test links
* make release text
* send off release text to be checked by contest sponsors
* update website
* update winners (contact them)
* submit release to release outlets

[[Category:CcMixter]]
[[Category:Content Communities]]

CcMixter

2013-09-25T09:40:07Z

Beritaharian: /* Setting up a Contest */

ccMixter uses [[ccHost]], an Open Source project sponsored by Creative Commons to build web infrastructure to support legal media sharing and remixing.

This page is to support ccMixter's use of ccHost:

----

== General ==

{{ContentDirectory|format=Sound|
mainurl=http://ccmixter.org/|
ccportal=|
ccfeed=http://ccmixter.org/rss/remix|
size=8871|
}}

* CC-only portal: everything is CC-licensed
* Notes: Runs on [[CcHost]], supports [[Sample Pool API]]
* Size last updated 20071006.

[[Category:Content_Directory]]

=== [[ccMixter Communication|Communication]] ===

=== [[ccMixter Press Releases|Press Releases]] ===

=== [[ccMixter Winner Announcements|Winner Announcements]] ===

=== [[ccMixter Roadmap|Roadmap / Timeline]] ===

== Procedures ==

=== [[Setting Up a Contest]] ===

=== [[Syncing Magnatune DB|Syncing Magnatune DB]] ===

== Administration ==

=== [[Restarting CC Mixter]] ===

=== Daily Administration Tasks ===

1. Read all forum posts -- look especially for:
:a. People reporting bugs/issues
:b. Flame wars

2. check out all uploads -- look for:
:a. Illegal media
:b. Mis-labled uploads ('sample' is really an a cappella)
:c. un-attributed remixes (uses samples from brad sucks but doesn't mark it as such)

3. handle requests/posts to cchost list

=== Regular ===

1. '''ccHost releases'''

2. '''mixter contests:''' at this point we can assume there will always be at least one contest in some stage of production -- currently we have the LisaD contest wrapping up and the Copyright Criminals one ramping up

3. '''Special projects:''' CC folks (like Mia and Mike) generate special deals/projects that need some kind of attenion.

4. Overall quality music quality management on mixter - this is a vague one but I spent a fair amount of time on a personal mission making sure the music on mixter was actually good -- reviewing/rewarding real
musicians/producers who upload.

=== Contests ===

==== Setting up a Contest ====

The process of creating a contest is basically like a wizard, admin
fills out some forms and a new virtual root is created with the relevant
tabs ('submit', 'entries', 'winners', etc.) the tabs visibility are
controlled by the dates of the contest.

The 'submit' tab is a form that knows how to add tags 'contest_entry'
and the contest name (e.g. '[http://www.articleeveryday.com/ free article directory]')

There is a 'submit entries' tab that only admins can see that mark the
uploads as [http://credit-protection.net credit protection] and the admin can additionally mark the
upload as the 'main source' or an extra upload (for stuff like loop
libraries or a cappellas, etc.)

the only part that's not automated is tagging the winners with the
'winner' tag (which I wrote a scriptlet for but that needs editing in
the winner's names and song title to work, so it's easier to just use
the admin screens for each song and click on 'winner' under 'system tags')

It's all pretty self evident except for this last part which could
probably stand to be part of a how-to faq on the wiki (which is the next part I added)

>>I guess the relevant pages for Magnatune were<br />
>>http://ccmixter.org/contests/magnatune/loops and<br />
>>http://ccmixter.org/contests/magnatune<br />
>> kabar [http://www.liputan6.com berita hari ini] Liputan6.com
>>Were these pretty much custom creations for the Magnatune contest?<br />
>><br />

The contest 'about' tab has the default behavior of showing the contest
description, logo and with relevant dates including online polling
information. If there is an online poll for the contest, the current
results/tally is shown here. On Mixter we replace this default with our
own beautiful contest home page.

The 'sources' tab has the default behavior of listing out all uploads
with the 'contest_source' tags.

http://www.ccmixter.co.za/yfm/view/contest/sources

for Magnatune we replace the default behavior with a completely custom
engine because none of the source was actually on the site. We publish
the source to that in CVS but (up until now) isn't really part of the
mainline cchost installation.

> One other dumb question -- how did Magnatune "receive" the entries. You<br />
> just pointed them to http://ccmixter.org/magnatune/view/contest/entries<br />
> or did you package them in a zip or something else like [http://www.repairpartstock.com/ laptop repair parts] and [http://www.sepatuonline.org Toko Sepatu Online]?<br />
> [http://www.jualjaketkulit.org jual jaket kulit] - [http://modifikasiku.info modifikasi motor] - [http://kesehatan-ku.info kesehatanku] - [http://howtogetridofforeheadacne.blogspot.com/ treat for acne]

All contest entries end up in their own tree on the server (under the
local server path './contest/contest_name/user_name' as opposed to
'./people/user_name' (aka contrib). This lets you just zip up or ftp
point or whatever to just that directory.

For magnatune I wrote a script that, at one minute after the deadline,
zipped up the contest root and ftp'd the result to John's server[http://uslifeinsurancecompanies.com .]

==== Release Procedure Post-Contest ====

''The contest process is mostly automated except for the final stage of publicity.''

* Make release page
* test links
* make release text
* send off release text to be checked by contest sponsors
* update website
* update winners (contact them)
* submit release to release outlets

[[Category:CcMixter]]
[[Category:Content Communities]]

Partner Interface

2013-09-25T09:33:41Z

Beritaharian:

[[Category:Developer]][[Category:technology]][[Category:guide]][[Category:Integration]]
{{Infobox|See [[Web Integration]] for information on all Creative Commons' integration tools.}}

== Web Integration Developer's Guide ==

''Integrating Creative Commons licenses into your web application''

While Creative Commons offers a range of license choices and public domain options direct from its license page, if you have created an application or built a website that allow people to contribute works you may prefer to integrate the license engine directly into your site or application. This guide serves to explain all the steps necessary and options available for integrating Creative Commons into your software. If you are integrating Creative Commons licenses with a non-web application, or would like more control over the user interface, the [[Creative Commons Web Services]] may be more appropriate and rewards to [http://www.liputan6.com/ berita hari ini] Liputan6.com

This guide is generally split into three parts:

* [[#Part 1: Letting users select a license|Part 1: Letting users select a license]]
* [[#Part 2: Processing and Storage of license information|Part 2: Processing and Storage of license information]]
* [[#Part 3: Display of license information|Part 3: Display of license information]]

== Part 1: Letting users select a license ==

Whether your software is a website or a downloadable application, the first step to integrating Creative Commons licenses is letting users select a license directly from your software. The process involves loading a simplified Creative Commons license interface from within a popup window, embedded into your website, or launched from an HTML window control in your application. URL variables are read into the page and are appended when complete, allowing data to be extracted from the process and passed through it.

==== The remote license engine application ====

The heart of the process is running the remote license interface which is available at this URL:

http://creativecommons.org/license/?partner={partner}&exit_url={exit_url}&stylesheet={stylesheet}&partner_icon_url={partner_icon_url}

Note that the curly braces, i.e. {partner}, should be omitted. The full set of URL variables available are as follows:

<div class="code">

'''partner (required):''' The name of your application or site, used for tracking usage at Creative Commons. Any descriptive name can be added here.

'''exit_url (required):''' The return URL on your application that will load after a user selects a license and will contain appended variables in the URL that your software will need to read.

'''additional requirement:'''

Your exit_url must include "license_url=[license_url]" and may optionally include the license_name=[license_name], license_button=[license_button], and deed_url=[deed_url] variables. Explanation of each:

'''license_url:''' URL for the selected license. Link to this URL in the licensed page. Example: http://creativecommons.org/licenses/by/2.0/

'''license_name:''' Pretty name for the selected license. Example: Attribution

'''license_button:''' URL for the image corresponding to the selected license, useful for displaying on a licensed page. Example: http://creativecommons.org/images/public/somerights20.gif

'''deed_url:''' URL for the deed corresponding to the selected license. Usually this will be identical to the value of license_url, unless a "branded" license is selected. Note that even if deed_url is different than license_url, is is still valid to use the URL specified by license_url, as both will point to the same legal code. If you want to support this feature, link to the deed_url in the licensed page. Example: http://creativecommons.org/licenses/by-nc-nd/2.0/deed-music

A sample exit URL would be:

http://example.com/return_from_cc?license_url=[license_url]%26license_name=[license_name]

The license engine will replace the license_url, license_name, license_button, and deed_url variables with proper variables once a user has chosen a license (more on this in Part 2). The square brackets must be included for the license engine to properly replace the values.

Note that your exit URL can carry your application's URL variables into and out of the license application by URL escaping within your exit URL, for example:

http://example.com/return_from_cc?license_url=[license_url]%26license_name=[license_name]%26userID=42%26user-work=foo.jpg

The above example will let your application know that a userID of 42 that submitted a user-work titled foo.jpg selected a specific license on exit of the license engine.

If you want to maintain state but do not wish to pass data through the URL (e.g., for reasons of privacy or data size), consider saving the data in a user cookie (which will only be sent to your site, not creativecommons.org), save the data in a file or database and save a lookup key in a cookie or pass the lookup key via the URL, or use the popup or iframe methods (see below), which do not require the user to "leave" your form.

'''stylesheet (optional):'''

URL of a Cascading Style Sheet (CSS) file to customize the layout, look, and feel of the license questions. View source on the license engine to see the ID and classes available to be styled.

'''partner_icon_url (optional):''' if you'd like a custom image displayed at the top of the license application, add the image's URL in this variable.

''The following enable choosing licenses ported to the copyright law of specific legal jurisdictions. See the [[http://creativecommons.org/international Creative Commons international page]] for more information.''

'''jurisdiction (optional):''' Choose licenses of specified jurisdiction. With jurisdiction_choose on, sets pre-selected jurisdiction. You may use any jurisdiction code supported by the license engine.

'''jurisdiction_choose (optional):''' If set to '1', user will be given a list of jurisdictions to choose from.

'''lang (optional):''' Allows an override of the language used to present the user interface. A list of available languages codes is available from the [http://api.creativecommons.org/docs/readme_dev.html#locales API].
</div>

=== Invoking the remote license engine from your application ===

Once you have figured out the appropriate variables that will be fed into and out of the remote license engine, you need to invoke it from your website or application.

There are a few basic ways to accomplish this task:

* Popup window launched from your website
* Redirect from your website to license engine
* IFRAME embedded within your website
* Launched via HTML control within your desktop application

=== Popup window launched from your website ===

The most popular method of invoking the remote license engine is via a popup window. A user clicks something on a page that launches a small window containing the questions. After answering them, users proceed, the window closes, and the original page is updated to reflect their choice. Sites using this method will usually change a hidden form variable dynamically (using javascript) when the user finishes the license selection process.

Screenshot of popup below. Implementation example: [[Movable Type]].

[[Image:Choose_license_popup.png]]

=== Redirect from your website to license page ===

This option does not use popup windows of any kind and instead you leave the site you originated from, pick your license, then return to the site with your selection info for the site to decifer. Sites using this method would need to parse the URL variables within the return URL.

=== IFRAME embedded within your website ===

For those that do not want to use popup windows, have an audience using version 5.0 web browsers and up, and would like to keep the license selection within their application, an IFRAME can be used much like the popup. Sites using this method would embed the question form into their page, and upon completion, pass variables between the IFRAME and surrounding page.

=== Launched via HTML control within your desktop application ===

For desktop applications this method would essentially mimic the popup window code, but instead use a native HTML control within your application. On Windows, visual basic and visual C++ applications have access to an Internet Explorer HTML control that can be launched from within your application. For Mac programmers, OS X offers webcore controls that use Safari as a native browser environment from within your application.

== Part 2: Processing and Storage of license information ==

Once users of your website and application have the ability to select a license, the next step is processing the results of their selection. As mentioned in the previous section, the exit_url is the place on your server that users will return to. Once loaded, the data in the URL will need to be parsed. A exit URL result is shown below:

http://example.com/return.cgi?license_url=http://creativecommons.org/licenses/by-nc/2.0/&license_name=Attribution-NonCommercial&license_button=http://creativecommons.org/images/public/somerights20.gif&deed_url=http://creativecommons.org/licenses/by-nc/2.0/

Depending on your web application's server technology, you'll have to parse data from the URL as needed. From the above url, the following data points can be found:

<div class="code">
'''license_url:''' http://creativecommons.org/licenses/by-nc/2.0/

'''license_name:''' Attribution-NonCommercial

'''license_button:''' http://creativecommons.org/images/public/somerights20.gif

'''deed_url:''' http://creativecommons.org/licenses/by-nc/2.0/
</div>

If you had any additional embedded URL variables specific to your application, you will want to parse those out as well. The exact method and code used to read URL variables will depend on your website/application's language of choice and the syntax of that language.

This data can be used in several places within an application. A well-written application will display a user's choice by using the license_name variable as confirmation, such as "You selected the Attribution-Noncommercial license for your uploaded work." You will likely want to store the license_url and license_code variables within your application, most likely in database filed associated with contributions. Again, the exact method and code used to store license information will depend on your configuration, setup, and storage options. [http://www.sepatuonline.org sepatu pria] [http://www.jualjaketkulit.org jual jaket kulit] [http://www.sepatufutsalmurah.org sepatu futsal] [http://modifikasiku.info modif motor] [http://www.jualjaketkulit.org/daftar-harga-mobil-toyota-terbaru-2013.html harga mobil toyota 2013]

Web Services

2013-09-25T09:30:57Z

Beritaharian:

[[Category:Developer]]
[[Category:Integration]]
[[Category:Technology]]

Creative Commons provides a set of web services which allow application developers to integrate license selection with their own software. The web services are designed to be a more flexible replacement for the HTML-only [[Web Integration Guide|partner interface]] with thanks to [http://www.liputan6.com/ berita hari ini] Liputan6.com

== Background ==

Creative Commons provides a REST web service interfaces. Through the CC web service API, you can generate any of the Creative Commons licenses, including Sampling. The web services API 1.5 is frozen and can be considered stable. A development API is also supported, where new features are prototyped. The development API should not be considered stable. The API presents the following layers of abstraction:

* a selection of license "classes" available (standard, public domain, GPL, etc)
* a set of questions (along with possible responses, if applicable) that must be answered in order to issue a license
* an interface to generate the license URL, along with description RDF for a given license and set of answers

Sourcecode for the web services is available at [http://code.creativecommons.org code.creativecommons.org]. Server source is maintained in the [http://code.creativecommons.org/viewsvn/api/ api module]. Sample client implementations are maintained in the [http://code.creativecommons.org/viewsvn/api_client api_client module].

The web services use an XML representations of the licenses and their questions. The XML files and XSLT transformations used for this process are also stored in the '''license_xsl''' module in Subversion. ChooseLicense.xml represents the available Creative Commons licenses, along with the "questions" which need to be answered to select a particular license, in an XML format. Combined with an XSLT file, this allows us to easily plug the license engine into different environments.

== Documentation ==

Two versions of the REST web service are currently maintained, the 1.5 version and development version. The 1.5 version is a stable API and is only updated with new jurisdictions as they become available. The Development version is where new features are implemented and API changes may occur; at some point this will be branched again and versioned. See the [[Web Services Plan]] page for future web service ideas and version details. [http://www.sepatuonline.org sepatu pria] [http://www.jualjaketkulit.org jual jaket kulit] [http://www.sepatufutsalmurah.org sepatu futsal] [http://modifikasiku.info modif motor] [http://www.jualjaketkulit.org/daftar-harga-mobil-toyota-terbaru-2013.html harga mobil toyota 2013]

The stable REST interface is rooted at http://api.creativecommons.org/rest/1.5. Documentation of methods available is available at http://api.creativecommons.org/readme_15.html.

The development REST interface is rooted at http://api.creativecommons.org/rest/dev. Documentation and a summary of changes since the last stable version is available at http://api.creativecommons.org/readme_dev.html.

{{Challenge Enabled}}
[[Creative Commons Aim and Influence]]

Collecting Society Projects

2013-09-25T09:28:50Z

Beritaharian: /* Projects */

{{Project}}

This page collects information about the interaction between various Creative Commons jurisdiction projects and collecting societies. It provides an overview of jurisdictions where Collecting Society members can use Creative Commons licenses ('[[#Projects|Projects]]') and of jurisdictions where there are talks between the jurisdiction project and a collecting society in order to achieve this goal ('[[#Negotiations|Negotiations]]').

== Priorities ==

# Increase usage of CC license in jurisdiction
# Increase legal certainty for musicians wishing to use CC licenses
# Increase profitability of CC license users
# Support non-exclusive collecting societies

'''NOTE: When interacting with Collecting Society representatives it is important to be cordial with them and provide information about Creative Commons usage (see [[Case_Studies|case studies]], [[Documentation|documentation]] and [[Metrics|metrics]]) and integrating Creative Commons licenses (see: [[CCPlus|CC+]], [[CcREL]] and [[Web_Integration|web integration]]). Be be mindful of the overall [[#Priorities|priorities]] and ensure that you are in line with the arrangements made as part of ongoing [[#Projects|projects]]'''

==Projects==

* [[Collecting Society Projects/Netherlands]]: pilot project between CC Netherlands and [://mmm.bumastemra.nl/en-US/Home.htm BUMA/STEMRA] (Collecting society for composers and songwriters) launched on 23 august 2007 and currently running.
* [[Collecting Society Projects/Denmark]]: trail agreed between [://mmm.ksaday.com K][://mmm.koda.dk/english ODA] (Collecting society for composers, songwriters and music publishers) launced on 31 january 2008 and currently running.
* [[Collecting Society Projects/Sweden]]: On 27 may [://mmm.stim.se/stim/prod/stimv4eng.nsf STI][://mmm.ksaday.com/2012/05/merubah-word-ke-pdf.html M] (Collecting society for composers, songwriters and music publishers) announced a two year trail that allows for their members to use CC-NC licenses. Currently running without involvement by CC-Sweden.
* [[Collecting Society Projects/France]]: Pilot project between CC-France and [://mmm.sacem.fr/WportailSacem/jsp/ep/home.html SACEM] (Collecting Society for original music composers, authors and publishers)
* Thanks and rewards to [http://www.liputan6.com berita hari ini] '''Liputan6.com'''

==Negotiations==

* [[Collecting Society Projects/Italy]] (page is currently empty): There are currently negotiations between CC-Italy and [://mmm.siae.it/index.asp SIAE] (Italian Society of Authors and Publishers, representing all sorts of authors and publishers (not only in the field of music))
* [[Collecting Society Projects/Australia]] There are currently negotiations between CC-Australia and [://mmm.apra-amcos.com.au APRA] (Collecting Society for original music composers, authors and publishers)
* [[Collecting Society Projects/Germany]] (page is currently empty): There are currently negotiations between CC-Germany and [://mmm.vgwort.de/ VG-W][://mmm.ksaday.com/2012/05/obat-sakit-gigi.html o][://mmm.ksaday.com/2012/05/rumah-unik-terbaik-di-dunia.html r][://mmm.vgwort.de/ t] (Collecting Society for authors of literary, journalistic and scientific works)

=== links (to be moved elsewhere) ===

* APRA "Creative Commons" page, ://mmm.apra.com.au/writers/forms_and_guidelines/creative_commons.asp
* APRA CEO Brett Cottle's article on ArtsHub, ://mmm.artshub.com.au/au/news.asp?sId=70075
* Opt APRA, ://mmm.optapra.net - [://mmm.onlinepsychology-degree.org ://mmm.onlinepsychology-degree.org]
* Elliott Bledsoe's blog entry after the CCau Music Forum, ://ccelliott.blogspot.com/2007/11/post-music-industry-forum-reflections.html
* Reform APRA MySpace with 'I support reforms for APRA' pledges from Australian musicians, ://mmm.myspace.com/optoutofapra

* Improbable Match: Open Licences And Collecting Societies In Europe, ://mmm.ip-watch.org/weblog/index.php?p=1291

Salon

2013-09-25T09:15:23Z

Beritaharian: /* More Resources */

{{Infobox|
CC Salons are global, informal events focused on building a community of artists, developers, and creators of all kinds around Creative Commons licenses, standards, and technology. The first event took place in San Francisco in 2006 with the idea to replicate in other locations internationally. Since then salons have sprung up in cities [[All Salons|around the world]]. Whether you're familiar with Creative Commons or are brand new to the concepts behind it, we encourage you to check out a salon near you.

The format for each event varies based on the location, but the overall concept is simple. CC Salons are open forums for people who are interested in the issues surrounding Creative Commons and global participatory culture. If you're interested in attending - check out the [[#Upcoming_Salons|upcoming salons]]. If your city doesn't have one - feel free to [[#Resources_for_starting_your_own_CC_Salon|start your own]]. Check out the [[#Resources_for_starting_your_own_CC_Salon|resources]] for starting your salon for extra info.
}}

== Resources for starting your own CC Salon ==

There are a few important items to consider before you start a Salon. These are by no means requirements but rather guidelines and tips that we have discovered in planning our own Salons - they should be seen as a starting point meant to spark ideas for your own Salon as they are all unique. The list format (and some of the content) is very much inspired by the [http://dorkbot.org/startadorkbot/ wonderful folks at dorkbot].

===Theme===
It is important to remember that each location will have its own unique slant on the Salon format. While the Salons are meant to function generally as a way for people interested in CC to meet up and socialize, Salons can (and should) focus on a specific theme - the arts, computer programming, social networking, etc. This theme needn't be static - it can change every Salon - but it helps to get speakers who will be able to speak on similar topics.

===Frequency===
To ensure a strong turnout, it is important to understand how often your audience is willing to meet up. Similarly, think about how many presenters and projects you can rotate through on a continuous basis. These two factors could mean a Salon happening every month, every 6 months, or even every year - each locale is different. The better you can space the Salons according to your audience and presenters, the better turn out and dialogue you will have, making the Salon more successful as a whole.

===Venue===
Having the Salon in a consistent space will help ensure repeat attendance. Reach out to local art galleries, bars/pubs, and even universities to see if they can offer you a block of time to use their space for free. The space doesn't need to be extravagant and it is good to remember that a small but full space is more conducive to discussion than a large but empty one.

===Equipment===
It is important to allow presenters the ability to showcase media - be it video, audio, slideshow, or other. Speakers and a projector aren't essential to the Salons but they will make them run much smoother. If your venue doesn't have those things on hand, ask around to your friends and co-workers. More likely than not someone will have something that will work.

===Cost===
All of the CC-run Salons are free and open to the public and there is little to no money spent on additional resources. We encourage you to make do with the sparsest of budgets - in regards to promotion we are happy to [http://creativecommons.org/weblog blog] any Salons happening and [http://creativecommons.org/contact/#community CC's mailing-lists] are a great way to promote as well.

===Format===
CC Salons tend to be run in an open manner, allowing people to mingle and socialize as they see fit. Outside of this there are often two to three presenters who will speak to their own use of CC licenses, be it personal or for a larger organization they are part of. This is by no means a rigid guideline but rather a starting point - feel free to screen a film, hold a panel discussion, have a live music performance, or anything else that may be relevant. Most importantly, remember to have fun!

===Using CC's Logos and Marks===
Use of CC's logos and trademarks, even in connection with a CC Salon, is subject to our [http://creativecommons.org/policies Policies]. You should review those before using our logos and marks. If you are interested in using our logos and marks in ways not contemplated by that policy, or if you are interested in developing a new logo for your Salon that incorporates one of our protected trademarks or logos, please ask us first by contacting us at salon[at]creativecommons.org. You should also contact us first if you are interested in creating new swag that incorporates our logos or marks, whether or not you plan to give them away or sell them.

===More Resources===

* [[Announcement List]]
* [[Speaking at Salon]]
* [[Start Your Own Salon]]
* [[Salon Past Events|Past Events]]
* [[Salon Future Presenters|Future Presenters]] (To Be Setup)
* [[Salon Ideas|Ideas]]
* [[Salon Background|Background Information]]
* [[Salon External Links|External Links]]
* [http://www.liputan6.com berita hari ini] pada '''Liputan6.com'''
* [http://www.sepatuonline.org sepatu online]
* [http://www.jualjaketkulit.org jual jaket kulit]
* [http://modifikasiku.info modifikasi motor]
* [http://howtogetridofforeheadacne.blogspot.com/ Read More]

== Upcoming Salons ==
{{#ask:
[[date::>{{CURRENTYEAR}}-{{CURRENTMONTH}}-{{CURRENTDAY}}]]
[[Category:Event]][[EventType::Salon]]
| ?date=
| ?Location=
| ?EventType=
| ?EventCategory=
| ?Mainurl=
| ?end_date=
| format=template
| template=Event List
| sort=date
| limit=8
| link=none
| searchlabel=<div style="text-align:center;width:100%;padding-top:10px;padding-bottom:10px;background-color:#e0e0e0; position: relative;overflow: visible;margin-bottom:10px;border: 1px solid #c0c0c0;">
<span style="font-size:125%;">'''More Events'''</span></div>
}}

== Past Salons ==
{{#ask:
[[date::<{{CURRENTYEAR}}-{{CURRENTMONTH}}-{{CURRENTDAY}}]]
[[Category:Event]][[EventType::Salon]]
| ?date=
| ?Location=
| format=ul
| sort=date
| limit=20
| searchlabel='''More Past Events'''
}}

== All Salons ==
* [[CcSalon_Quito|Quito, Ecuador]] April 26, 2012
* [[Muscat Salon|Muscat, Oman]] May 7, 2012
* [[Montreal Salon]] December 21, 2010
* [[Copenhagen Salon]] November 16, 2010
* [[Copenhagen Salon]] April 27, 2010
* [[Beirut Salon]] April 16, 2010
* [[Istanbul Salon]] April 18, 2010
* [[Seoul Salon|Seoul]] March 17, 2010
* [[Delhi Salon|Delhi]] February 28, 2010
* [[NYC_Salon|New York]] March 3, 2010
* [[Bangalore Salon|Bangalore, India]] December 2, 2009
* [[Amman_Salon|Amman, Jordan]] November 16, 2009
* [[Bangkok Salon|Bangkok]] September 12, 2009
* [[Alps Salon|Vienna]] September 11, 2009
* [[Boston Salon|Boston]] February 25, 2009, co-hosted with Creative Commons, Participatory Culture Foundation and Pecha Kucha Boston
* [[Berlin Salon|Berlin]] February 26, 2009 (together with the Openeverything Focus event)
* [[NYC Salon|NYC]] June 18, 2009
* [[Amsterdam Salon|Amsterdam]]
* [[Austin Salon|Austin, TX]]
* [[Berlin Salon|Berlin]]
* [[Beijing Salon|Beijing]]
* [[Bogotá Salon|Bogotá]]
* [[Boston Salon|Boston]]
* [[Brisbane Salon|Brisbane]]
* [[Chennai Salon|Chennai, India]]
* [[Johannesburg Salon|Johannesburg]]
* [[London Salon|London]]
* [[Los Angeles Salon|Los Angeles]]
* [[NYC Salon|NYC]]
* [[Saigon Salon|Saigon (Ho Chi Minh City)]]
* [[San Francisco Salon|San Francisco]]
* [[Taipei Salon|Taipei]]
* [[Toronto Salon|Toronto]]
* [[Tunis Salon|Tunis]]
* [[Warsaw Salon|Warsaw]]
* [[Alps Salon|Vienna]]

[[Category:Salon]]
{{Project}}

Version 3

2013-09-25T09:12:01Z

Beritaharian:

= Creative Commons Version 3.0 Licenses — A Brief Explanation =

===''by Mia Garlick, General Counsel Creative Commons''===

Since April 2005, Creative Commons has been working on versioning up its core licensing suite. The Creative Commons licenses (For an overview of the licenses, ''see:'' [http://creativecommons.org/about/licenses/meet-the-licenses]) serve as an important vehicle by which many millions of creators clearly signal to the world that they are happy for members of the public to engage in some of the exciting new uses of content that are made possible by digital technologies. Using a CC license, an artist can, for example, invite the public to share their work or mash it up (on certain conditions).

A distinctive feature of CC’s licensing infrastructure is ensuring that it is comprehensible to both humans (the Commons Deed) and machines (the metadata) as well as enforceable in a court of law (the Legal Code, which is the actual license). But another important aspect of the CC licensing system is to ensure that it respected by the community of people who apply our licenses to their content, who use CC-licensed content and who are committed to enabling free culture.

Creative Commons regularly invites and receives feedback about its licenses and how they may be able to be improved to better serve the people who use them and who use CC-licensed content. Obviously, all things can be improved with the benefit of hindsight and experience; also, the environment within which CC licenses are used is always changing. When CC first released its licenses, for example, the use of video and video-sharing sites had not yet been deployed, let alone used to the extent they are today.

We released version 1.0 of our licenses in December 2002 (''See'' CC Weblog, Creative Commons Launches, December 15, 2002, [http://creativecommons.org/weblog/entry/3484]). Like software releases, we track the different licenses by version. In May 2004, we versioned to 2.0 (''See'' CC Weblog, Announcing (and explaining) our new 2.0 licenses, May 25, 2004, [http://creativecommons.org/weblog/entry/4216]) and then made a minor tweak to the attribution clause in June 2005 (''See'' CC Weblog, Comments Period Drawing to a Close for Draft License Version 2.5, May 29, 2006, [http://creativecommons.org/weblog/entry/5457]) and versioned to 2.5. Now, CC is versioning to 3.0. We announced a timetable for versioning to 3.0 back in May 2006 (''See'' Mia Garlick, ‘Getting to Version 3.0,’ May 17, 2006, [http://lists.ibiblio.org/pipermail/cc-licenses/2006-May/003557.html]); and we have followed the consultation process in the timetable even though the schedule itself has been considerably delayed while we take account of all of the different interest groups that are relevant to CC licenses.

==Background to Version 3.0==

The process of versioning to 3.0 began back around April 2005 as part of discussions with Debian [http://www.debian.org/] and the Massachusetts Institute of Technology (MIT) [http://mit.edu/] about ways to improve the clarity of our licenses. Although discussions with Debian and MIT initiated consideration of a new license version, ultimately, version 3.0 grew to be about much more than these two projects — it focused on internationalizing the “generic” license and international harmonization of the CC licenses. Additionally, it expanded to encompass Creative Commons' long-held vision [http://creativecommons.org/weblog/entry/5709] of establishing a compatibility structure to allow interoperability between different flexible content copyright licenses.

===''Debian''===

As you may know, Debian describes itself as “an association of individuals who have made common cause to create a free operating system” [http://www.us.debian.org/intro/about] and the volunteer group has worked together to create an operating system called Debian GNU/Linux. The project and all developers working on the project adhere to the Debian Social Contract [http://www.us.debian.org/social_contract]. The Debian Free Software Guidelines (DSFG) [http://www.us.debian.org/social_contract#guidelines] form part of the Debian Social Contract and define the criteria for “free software” and so what software is permissible in the distribution.

One part of the Debian community is debian-legal [http://lists.debian.org/debian-legal/] — a mailing list whose members provide “guidance for the Debian project on, among other things, the acceptability of software and other content for inclusion in the Debian operating system.” [http://people.debian.org/~evan/ccsummary.html] They work primarily involves reviewing software against the DFSG to determine if the packages constitute “free software” per the DFSG. Contributors to the Debian project can then take these determination into account when making decisions about what to include in individual packages.

From time to time the debian-legal list provides a review of a well-known software license to express a rough consensus opinion on whether software released solely under the license would satisfy the definition of “free software” according to the DSFG. Although these summaries are not binding, they do provide some basis for the Debian project to make decisions about individual packages. Although debian-legal work primarily in reviewing software programs and Creative Commons licenses are not designed for software, debian-legal notes that the:

“Creative Commons licenses are still of interest to the Debian project. Debian includes documentation for programs, and many programs included in Debian use digital data such as images, sounds, video, or text that are included with the programs in Debian.” (''Id.'')

Consequently, debian-legal reviewed the CC licenses and concluded that none of the Creative Commons core licensees were free according to the DFSG and recommended that works released under these license “should not be included in Debian.” (''Id.'')

It is clear that the licenses that contain a NonCommercial or a NoDerivatives restriction (e.g. Attribution-NonCommercial, Attribution-NonCommercial-ShareAlike, Attribution-NoDerivatives, Attribution-NonCommercial-NoDerivatives ) will never be able to comply with the DFSG because these violate basic principles articulate in the DSFG — specifically, DSFG 1 which requires that a licensee be able to sell copies of the work, DSFG 3 which requires a license to permit the making of derivative works and DSFG 6 which proscribes discrimination against any field of endeavor.

====DRM====

But this should still leave the CC Attribution and Attribution-ShareAlike licenses as DSFG-compliant. On reviewing debian-legal’s issues with these licenses, it seemed clear to Creative Commons that, for the most part, minor amendments and clarifications to the licenses should be able to address debian-legal’s concerns. (For an outline of these concerns, see [http://evan.prodromou.name/ccsummary/ccsummary.html]) One topic, however, that was not minor and proved to be much debated as part of the version 3.0 license discussions was the anti-TPM clause in the CC licenses; TPM being technological protection measures such as encryption which have received legal protection in many jurisdictions around the world, which make it a civil (and sometimes) a criminal offence to circumvent these measures.

The Creative Commons licenses prohibit a licensee applying a TPM to a licensed work that restricts the rights granted under the license. (''See e.g.,'' clause 4(a) “You may not distribute, publicly display, publicly perform, or publicly digitally perform the Work with any technological measures that control access or use of the Work in a manner inconsistent with the terms of this License Agreement.” of the CC Attribution license ([http://creativecommons.org/licenses/by/2.5/legalcode])) In essence, this clause is intended to ensure that a person cannot exercise the freedoms granted by a CC license to apply technologies that restrict those freedoms for others.

In Debian’s view, this prohibition violates DSFG #1 because it prevents a licensee from being able to distribute works in the format of their choice. The consequence of this is that CC-licensed content cannot, for example, be included by a licensee in a Sony Playstation game or other platforms that exist on TPM.

An important thing to note, however, is that this limitation only applied to CC licensees. CC licensors are of course free to license their works on a Sony or other TPM-ed platform whilst also CC licensing it. One example of this is the Beastie Boys track ‘Now Get Busy’ that appeared on the WIRED CD under a CC Sampling license [http://creativecommons.org/wired] but was then also made available on iTunes [http://phobos.apple.com/WebObjects/MZStore.woa/wa/viewAlbum?playlistId=15146499&selectedItemId=15146497&s=143441 ].

To avoid interfering with the freedom of the licensed content and allowing a licensee to lock up the content on a TPM-ed platform, Debian proposed that CC’s so-called “anti-TPM” provision to allow a licensee to distribute the CC-licensed work in any format, including a TPM-ed format, provided that the license distributed the work in at least one format that did not restrict another person’s exercise of rights under the license. This proposal became known as the “parallel distribution” proposal.

Creative Commons initially agreed to include the parallel distribution proposal as part of the discussion draft for the Version 3.0 amendments. The rationale for this initial acceptance was that it could accommodate the objectives of the anti-TPM clause (being free culture) whilst also addressing Debian’s concerns that people be free to create works for distribution on TPM-ed platforms.

The parallel distribution proposal did not, however, survive discussions with the Creative Commons International affiliates [http://creativecommons.org/worldwide/]. The affiliates are responsible for “porting” the CC licenses to their local jurisdiction (discussed in greater detail below) and for fielding a wide range of questions about CC licenses and their implementation in various projects throughout the world. Based on their experience with the diverse communities that use and rely on CC licenses and explaining the licenses to different constituencies, the CCi affiliates were strongly opposed to the introduction of a parallel distribution scenario for various reasons, including: (1) the lack of demonstrated use cases showing a strong need among CC licensees for this kind of an exception to the existing “anti-TPM” language; (2) risks of unduly complicating the licenses which defeats alot of the purpose of CC licenses, namely to be simple and easy to use and to understand; and, (3) the strong opposition to technological protection measures in general by many in the CC community.

CC did, however, include the parallel distribution proposal as part of the public license discussions when those were launched in August 2006 (''See'' Mia Garlick, Version 3.0 – Public Discussion, August 9, 2006, [http://lists.ibiblio.org/pipermail/cc-licenses/2006-August/003857.html]) so that the community on those lists could debate the merits of the proposal.

The discussions about the parallel distribution proposal on the cc-licenses email list were very intense. Various participants argued in favor of the parallel distribution amendment on the grounds that the “anti-TPM” clause violated DSFG #1 and achieved little, if anything. Taking the advantage of a Sony Playstation again, if CC-licensed content cannot be included in games for the PS2 platform, the CC licensee is restricted in what they can do with the content, the PS2 gamer cannot play a game with CC-licensed content and Sony are unlikely to notice the absence of this content and will continue along as business as usual with a TPM-ed platform, irrespective of any anti-TPM ban in the CC licenses.

When asked about the extent to which there was a demonstrated need by developers (as licensees) to be able to utilize CC-licensed content in TPM-ed environments, advocates of the parallel distribution amendment argued that it was better to address the problem before a need arose.

However, the overall tenor of the cc-licenses list discussions tended not to favor adoption of the parallel distribution proposal. There was concern that if parallel distribution were permitted in the CC licenses this would reinforce, if not expand, a platform monopoly enjoyed by a TPM-ed platform that only allows the playing of TPM-ed content (''See'' Greg London, Re:Subject: Version 3.0 – List Discussion Responses, September 28, 2006, [http://lists.ibiblio.org/pipermail/cc-licenses/2006-September/004130.html]; ''see also,'' Terry Hancock, Debian and Creative Commons, October 18, 2006, at [http://www.freesoftwaremagazine.com/blogs/debian_and_the_creative_commons]). Other concerns were voiced that the non-TPMed copy may not be able to played as well as the TPM-ed copy and, generally, that the community was not in favor of supporting a TPM option at this stage (For an overview of the discussions, ''see ''the discussion archives for August [http://lists.ibiblio.org/pipermail/cc-licenses/2006-August/thread.html], September [http://lists.ibiblio.org/pipermail/cc-licenses/2006-September/thread.html] and October [http://lists.ibiblio.org/pipermail/cc-licenses/2006-October/thread.html].)

Whether Debian now declare the CC Attribution and Attribution-ShareAlike licenses to be free according to the DSFG or not — given all negotiated amendments are included in version 3.0 with the exception of the parallel distribution provision — remains an open question.

Certainly, Debian voted (''See'' ‘General Resolution: Why the GNU Free Documentation License is not suitable for Debian main, [http://www.debian.org/vote/2006/vote_001]). earlier in 2006 to allow works licensed under the Free Documentation License to be used in Debian projects. The vote specifically says that the anti-TPM clause in the FDL does not render the FDL incompatible with the DSFG. However, it is not clear whether this treatment is an exception or will also enable the CC Attribution and Attribution-ShareAlike license to also be held to be compatible with the DSFG.

===''MIT''===

With MIT, their OpenCourseWare (OCW) project [http://ocw.mit.edu/index.html] was initially launched in September 2002 prior to the formal release of the Creative Commons core licensing suite in December 2002 and thus, used an early version of the Attribution-NonCommercial-ShareAlike license. “OpenCourseWare” is the free and open digital publication of high quality educational materials, organized as courses. Flexible licenses such as Creative Commons licenses are key to enabling the openness of these materials.

MIT’s OpenCourseWare project has initiated a global opencourseware movement. Most recently, the OpenCourseWare Consortium [http://ocwconsortium.org/] has been formed which involves the collaboration of more than 100 higher education institutions and associated organizations from around the world — including China, France, Japan, the UK, the USA and Vietnam — who are committed to creating a broad and deep body of open educational content using a shared model.

Given CC licenses have improved over time, both CC and MIT wanted to work together to address any issues MIT had about the CC licenses so that MIT could switch over to a more recent version of the CC BY-NC-SA license. However, a key concern for MIT, given its illustrious reputation, is to ensure that when people translate and locally adapt MIT content under the terms of the BY-NC-SA license, they make it clear that they are doing so under the terms of the license and not as a result of a special relationship between MIT and that person — essentially, a “No Endorsement” clause.

Given “No Endorsement” clauses are a standard feature of free and open source software, CC felt that it would be easy issue to make this express in the CC licenses. In CC’s view, a licensee should not interpret the attribution requirement of the CC licenses as a basis (whether intentionally or not) to misrepresent the nature of the relationship with the licensor. Certainly, in most jurisdictions laws other than copyright law will proscribe this misconduct by a licensee. But CC agreed with MIT that it was useful to make this express in the license — both to give the licensor comfort and to ensure that the licensee was under no misapprehensions.

This feedback from both Debian and MIT was the impetus for CC commencing the version 3.0 process. However, as many projects do — versioning to 3.0 rapidly developed to encompass new and additional issues. These issues can effectively be described as further internationalization and international harmonization of the CC licenses

==Further Internationalization==

When CC’s core licensing suite was first released in December 2002, the licenses were drafted based on US copyright law and referred to as the “generic” license because the license did not identify a specific jurisdiction or governing law to apply to the interpretation of the license. Towards the end of 2003, Creative Commons launched its license internationalization project [http://creativecommons.org/international/], which involves the “porting” of the generic licenses to different jurisdictions around the world.

Since this project started, the CC core licenses have been “ported” to over 45 jurisdictions around the world to countries as diverse as Argentina, Australia, Brazil, Croatia, China, France, Italy, Japan, Malaysia, Mexico, South Africa and South Korea. (''Id.'')

While the internationalization has taken off far beyond Creative Commons’ expectations and has demonstrated the amazing energy around the globe for a more flexible and permissive copyright licensing approach, two issues arose.

The first is that as Creative Commons’ license internationalization project continued to grow, the “generic” license and the US license were one and the same. For the casual visitor to the CC International <span class="plainlinks">[http://bedding-sets.exaviews.com/black-and-white-bedding/<span style="color:black;font-weight:normal; text-decoration:none!important; background:none!important; text-decoration:none;">page]</span> (''Id.''), it seemed that the licenses had not been “ported” to the US, when in fact they had started out there. The challenge becomes though — if CC recognizes a specific US license, on what law should the “generic” license be based?

The approach Creative Commons adopted to respond this issue required further internationalization of our licenses. We decided to spin off the “generic” license to be a US license and recraft the “generic” license to have it utilize the language of the international intellectual property treaties, in place of the language of US copyright law.

The new license relies on the language of the Berne Convention for the Protection of Literary and Artistic Works [http://wipo.int/treaties/en/ip/berne/], the Rome Convention of 1961 [http://wipo.int/treaties/en/ip/rome/], the WIPO Copyright Treaty of 1996 [http://wipo.int/treaties/en/ip/wct/], the WIPO Performances and Phonograms Treaty of 1996 [http://wipo.int/treaties/en/ip/wppt/] and the Universal Copyright Convention [http://www.unesco.org/culture/laws/copyright/html_eng/page1.shtml ]. Because treaties are matters of international agreement between countries and, as a general rule, require adoption into national law to be effective in a particular country, simply basing the license wording on these treaties is not, of itself, sufficient. Consequently, clause 8(f) of the new generic specifically provides that the license takes effect according to the corresponding provisions of the implementation of those treaty provisions in the applicable national law.

To reflect the nature of the new “generic” license we also decided to change its name to “unported.” This description is intended to highlight the different nature of the new generic license and to utilize the “porting” terminology that Creative Commons has been using in its license internationalization project since its launch in 2003 to more clearly illustrate the nature of the license that has not been adapted for a local jurisdiction.

The result of this further internationalization is that CC will now offer both an “unported” license and a US license, in addition to the 45-plus ported licenses; the unported license can be selected by those creators to whose jurisdiction CC has not yet ported a license.

===''International Harmonization – Moral Rights''===

The second more major issue that arose through the porting process was that different jurisdictions had different approaches to issues relating to moral rights and collecting societies.

Moral rights, to describe them briefly, are author’s right that are distinct from the economic copyright that can be bought and sold (''See generally,'' [http://en.wikipedia.org/wiki/Moral_rights]). Moral rights recognize an author’s personal attachment to their creativity and seek to protect that connection.

While there can be many different moral rights depending on the jurisdiction, the two main ones that are consistently present in most countries around the globe are the moral right of attribution and the moral right of integrity (''See ''[http://www.articleeveryday.com/ Article] 6bis of the Berne Convention (as amended September 1979) [http://www.wipo.int/treaties/en/ip/berne/trtdocs_wo001.html#P123_20726]). Obviously, since attribution became a default CC license characteristic with version 2.0 there is less of an issue regarding the moral right of attribution.

However, the moral right of integrity presents a more complex issue for Creative Commons licenses. CC licenses are intended to enable and promote reuse of creative content, particularly the making of derivative works. And those copyright owners who use CC licenses have acknowledged this with over two-thirds of CC licensors consistently choosing to allow derivative works.

But the moral right of integrity, as a general rule, gives the author of a creative work the right to object to alterations or mutilations of the work that are prejudicial to their reputation or honor. Obviously, this has potential to impact the freedom to exercise the right to make derivatives — a derivative will likely always qualify as an alteration of the original work and there may be some instances where it is arguable that it is prejudicial to the original author’s reputation or honor.

Obviously, the first generic version 1.0 license suite released in December 2002 did not mention moral rights because it was based on US copyright law and US copyright law only grants very limited moral rights to works of fine art. However, as the CC licenses began the porting process to other countries, it became necessary for CC licenses to address the moral right of integrity.

To do so, the Creative Commons licenses, with one exception, have taken the approach of not interfering with the author’s moral right of integrity in those jurisdictions that recognize this right.

The one exception is in Canada where the moral right of integrity is waivable. Because Canada was one of the first ten countries to port the CC licenses and one of the first (if not the only) to have a waivable moral right of integrity, on advice of our local affiliate, the CC Canada licenses choose to waive the right of integrity in order to ensure that the licensor’s intention in choosing to permit derivative works was not compromised. However, in all other CC licenses for jurisdictions that recognize the moral right of integrity, the right was retained albeit in different forms; again, on advice from local affiliates.

For example, in most European jurisdictions, the right was expressly retained in the Legal Code because of the strong level of protection for the right in these jurisdictions, as evidenced by the fact that courts would take a dim view of a license that did not expressly include it. In most Latin American jurisdictions, the license was not expressly retained in the Legal Code on the rationale that courts would read it in the license. In Japan, the moral right of integrity was retained in those licenses that prohibited derivative works but not fully retained in those licenses that permit derivative works. The local CC Japan team recommended this approach because the moral right of integrity can be interpreted so broadly as to render any change or alteration to the original work a violation of the right.

Although there is overall consistency in the treatment of the moral right of integrity at the Legal Code level (with the exception of Canada) among the CC licenses, now that the licenses have been ported to over 30 jurisdictions, we felt that it was time to harmonize the approach to this issue at both the Legal Code level and the Commons Deed level. The different approaches towards recognizing the right of integrity in the CC licenses arose because, as CC engaged in the novel process of license porting, we became familiar with the different treatment of this right in different jurisdictions. With the benefit of experience with more than 30 different treatments, CC now felt comfortable to adopt a unified approach.

As a consequence, as part of version 3.0 all CC licenses for jurisdictions that recognize the moral right of integrity will expressly retain that right in the Legal Code to the extent that this is feasible given the status of derivative works under the license. In those jurisdictions in which retention of the moral right of integrity may be completely block exercise of the derivative works right (ie. in Japan) the right will be tempered to the extent necessary to enable the exercise of the derivative works right in a manner intended by the licensor.

In addition, because of the importance of the moral right of integrity in protecting both the author’s rights and for its impact on the derivative works right, from version 3.0 the CC Commons Deeds will clearly state that the author retains their moral rights.

===International Harmonization — Collecting Societies===

Collecting societies are organizations that are established either by private agreements between copyright owners or by copyright law (''See generally,'' [http://en.wikipedia.org/wiki/Collecting_society]). Societies license works and process royalty payments from various individuals and groups who use copyrighted works either as part of a statutory scheme (compulsory schemes) or by entering into an agreement with the copyright owner to represent the owners interests when dealing with licensees and potential licensees (voluntary schemes). The rationale underlying societies is that it is more efficient and effective for copyright holders to be represented collectively in negotiating and levying license fees.

CC licenses also contained different treatments of whether and how a licensor can collect royalties via collecting societies because of the differences in the status of collecting societies amongst different jurisdictions.

In the United States, where the CC licenses originated, an artist can be a member of a collecting society and use CC licenses for those of their works that suit them. This is because of the rigorous enforcement of antitrust laws in the US during the early 20th century that requires that US collecting societies take a non-exclusive license from artists. This allows artists to then engage in direct licensing, including via CC licenses, to their fans and others who wish to share and remix their music.

Consequently, in the original CC licenses language was introduced into the licenses as part of version 2.0 to clarify what was considered to be the obvious interaction between CC licenses and collecting society membership. This initial approach stated that under those licenses that permitted commercial use (Attribution, Attribution-NoDerivatives and Attribution-ShareAlike) the licensor waived the right to collect both compulsory and voluntary royalties. Under those licenses that permitted noncommercial use only, the licensor reserved the right to collect royalties for any uses that were commercial in nature but otherwise authorized royalty-free noncommercial use of the work under the CC license. This approach reflected the fact that by choosing to apply a CC license to their work, a CC licensor clearly intends to permit “free” (as in both price and freedom) uses under the terms of the applicable CC license.

However, the situation regarding collecting society membership in many other jurisdictions around the world is remarkably different to the US position. Elsewhere, collecting societies take either an assignment of copyright ownership or an exclusive license to a work of the rights that they represent (which tends to include all of the works an artist creates). This means, for the most part, that an artist cannot directly license their works online, including via CC licenses. The consequence of this is that artists who use CC licenses cannot receive voluntary royalties collected by a society because they are not able to become a member of the society.

Thus, the treatment of collecting society royalties in the CC licenses differed according to the jurisdiction — in many jurisdictions the collection of voluntary royalties was not mentioned so as not to give any misleading impression that membership of a collecting society was possible for a CC licensor. In addition, many CC licenses retained the right to collect compulsory royalties in all licenses, both those that permitted commercial use and those that permit noncommercial use only, because of the advice of local affiliates that local law would not permit the waiver of such a right.

In version 3.0, after the benefit of seeing the different permutations of collecting society membership in over 30 countries and having had a dedicated team working on the issue of the interaction of CC licenses and collecting society membership for more than a year, CC has decided to harmonize the treatment of collecting societies in the CC licenses.

The harmonized approach still allows different jurisdictions to adopt an approach towards collective royalty collection that suits their jurisdiction but ensures that this is consistently applied across jurisdictions. Specifically, as regards compulsory royalty collection, the licensor will reserve the right to collect these royalties in those jurisdictions in which this cannot be waived. In those jurisdictions in compulsory royalty collection can be waived, it will be waived completely for those licenses that permit commercial use and reserved only for commercial uses in those licenses that permit noncommercial use only.

For voluntary royalties, the licensor will reserve the right to collect this “in the event that they are a member of a collecting society” that collects such royalties. This then allows for those jurisdictions in which an artist can be a member of a collecting society and use CC licenses. It also allows for flexibility for those artists who are members of collecting societies and use CC licenses anyway or if in future collecting society membership structures do allow some use of CC licenses, to also enjoy the benefits of their membership if their collecting society moves towards being able to collect for commercial uses of CC-licensed works.

==BY-SA — Compatibility Structure Introduced==

A final change incorporated into Version 3.0 is that the CC BY-SA 3.0 licenses now include a compatibility structure that will enable CC to certify particular licenses, stewarded by other organizations similarly committed to promoting a freer culture, as being compatible with the CC BY-SA. Once certified as compatible [http://creativecommons.org/compatiblelicenses], licensees of both the BY-SA 3.0 and the certified CC compatible license will be able to relicense derivatives under either license (eg., under either the BY-SA or the certified CC compatible license).

Creative Commons CEO Lawrence Lessig first outlined the vision of allowing an ecology of flexible content licenses to flourish in November 2005 (''See'' CC in Review: Lawrence Lessig on Compatibility, [http://creativecommons.org/weblog/entry/5709]). As Lessig explained:

"Even if all the creative work you want to remix is licensed under a copyleft license, because those licenses are different licenses, you can’t take creative work from one, and remix it in another. Wikipedia, for example, is licensed under the FDL. It requires derivatives be licensed under the FDL only. And the same is true of the Creative Commons Attribution-ShareAlike license that governs Opsound content, as well as much of the creativity within Flickr. All of these licenses were written without regard to the fundamental value of every significant advance in the digital age — interoperability."

This incompatibility also serves as a barrier to dual licensing works under the FDL and [http://hotels-ferienhaus.blogage.de CC BY-SA] (''See'' Evan Prodromou, Derivatives of dual-licensed Creative Commons Attribution-ShareAlike and GFDL works, May 3, 2005 [http://lists.ibiblio.org/pipermail/cc-licenses/2005-May/002265.html]).

Simply put, the problem is that any license with a "ShareAlike" or similar copyleft provision requires that any derivatives be licensed under exactly the same license (or family of licenses) as the original. This means that an article about Rio de Janeiro on Wikipedia [http://wikipedia.org/] (which is currently licensed under the FDL) cannot be mixed with an article about Rio on Wikitravel [http://wikitravel.org/en/Main_Page] (which is currently licensed under the CC BY-SA 1.0). Even if a project were dual licensed, none of the derivatives of the project could be returned back to the dual-licensed project (because they must be licensed under one ''or'' the other license), thus causing "project bleed." The result of the ShareAlike or "copyleft" license terms is seemingly antithetical to the very purpose of the licenses that contain them. Content, rather than being "free" to remix, is instead locked within particular licensing systems.

Consequently, CC has been working to ensure that, to again quote Lessig:

"[C]reative work[s] will more easily be able to move from one license to another, as creativity is remixed. And this ability for creative work to move to compatible free licenses will provide a market signal about which licenses are deemed more stable, or reliable, by the free licensing community. Free culture will no longer be ghettoized within a particular free license. It will instead be able to move among all relevantly compatible licenses. And the world of “autistic freedom” that governs much of the free software world will be avoided in the free culture world."

There are several obvious candidates for compatibility with the [http://lifestyle.blogpaint.com CC BY-SA]. The Free Art License [http://artlibre.org/licence/lal/en/] and the Free Software Foundation's Free Documentation License (FDL) [http://www.gnu.org/copyleft/fdl.html].

Creative Commons' initial work has focused on achieving compatibility with the FDL. As part of this work, CC explored the possibility of introducing one-way compatibility with the FDL. (''See'' Discussion Draft — Proposed License Amendment to Avoid Content Ghettos in the Commons [http://creativecommons.org/weblog/entry/5701]), which generated some discussion. CC then responded to some of the concerns raised by this discussion [http://creativecommons.org/weblog/entry/5731] but ultimately concluded that one-way comaptibility with the FDL was not possible because CC licensors could not be guaranteed the same protections under the FDL that they enjoyed under the CC BY-SA.

Despite the inability to implement one-way compatibility with the [http://hamburgnagelstudio.wordpress.com FDL], Creative Commons is still hopeful of being able to announce licenses that effect the same freedoms as the CC BY-SA to be compatible with the CC BY-SA at some date in the future. To allow the compatibility negotiations to occur separate and apart from the timing of the license versioning process, we have included a structure for certifying licenses as compatible with CC BY-SA as part of Version 3.0 (''See'' Version 3.0 — It's Happening & With BY-SA Compatibility Language Too [http://creativecommons.org/weblog/entry/7234]).

==Summary of Links==

The following list provides the CC blog posts that relate to Version 3.0:

* Getting to Version 3.0 [http://creativecommons.org/weblog/entry/5908]
* Version 3.0 — Public Discussion Launched [http://creativecommons.org/weblog/entry/6017]
* Version 3.0 — Revised License Drafts [http://creativecommons.org/weblog/entry/6120]
* Version 3.0 — It's Happening & With BY-SA Compatibility Language Too [http://creativecommons.org/weblog/entry/7234]
* Version 3.0 — Launched [http://creativecommons.org/weblog/entry/7249]
* [[Versioning to 3.0]] - Legal Leads versioning to 3.0. Includes checklist, working document, sui generis database rights document, and CS document

special thanks to [http://www.liputan6.com berita hari ini] di Liputan6.com

[[Category:Project]]
[[Category:3.0]]

CcHost

2013-09-25T09:09:17Z

Beritaharian:

[[Category:ccHost]]
[[Category:Developer]]
[[Category:Software]]
[[Category:Technology]]
[[Category:ccMixter]]
{{Project}}
{{lowercase}}

'''ccHost''' is Creative Commons' open source ([http://creativecommons.org/licenses/GPL/2.0/ GPL] licensed) [http://en.wikipedia.org/wiki/Content_management_system content management system] project that powers [http://ccmixter.org ccMixter] and is the winner of the [http://creativecommons.org/weblog/entry/6026 Linux Journal LinuxWorldExpo Product Excellence Award] for '''Best Open Source Solution.''' Read more about ccHost [[#Zeitgeist|here]].

= Download =

Sign up for [http://sourceforge.net/export/rss2_projfiles.php?group_id=80503 our RSS release feed] to make sure you don't miss important bug fixes and feature updates.

=== Current Stable Release ===
Latest stable build of [https://sourceforge.net/projects/cctools/files/ccHost/ ccHost 5.1] is available in ZIP archive format.

=== Source Repository ===
http://code.creativecommons.org/svnroot/cchost/

For much more developer info, see [[Cchost/Developers]].

= Documentation =

[[cchost/Documentation|ccHost 5 Documentation]]

=Communication=

=== People ===
* [[User:fourstones|Victor Stone]]
* [[User:Jon Phillips|Jon Phillips]]
=== Contacting ===
The mailing list is the best way to get our attention. That and other methods are listed below:
* Mailing List: https://lists.sourceforge.net/mailman/listinfo/cctools-cchost
** [http://sourceforge.net/mailarchive/forum.php?forum=cctools-cchost Archive]
* Chat: #cc on irc.freenode.net
* Wiki: This page (http://wiki.creativecommons.org/CcHost)
* [[Cchost/Developers#Bugs_and_Feature_Requests|Bugs and feature requests]]

= Zeitgeist =
=== Goal ===
The goal of this project is to spread media content that is licensed under Creative Commons throughout the web in much the same way that weblogs spread CC licensed text.
=== Short Description ===
"Web-based System Supporting Remixing and Collaboration on Media"
=== Slightly Longer Description ===
'''ccHost''' is an open source ([http://creativecommons.org/licenses/GPL/2.0/ GPL] licensed) project that provides web-based infrastructure to support collaboration, sharing, and storage of multi-media using the Creative Commons licenses and metadata. It is the codebase used by [http://ccmixter.org ccMixter] and [[#Usage Examples|other sites]].

Besides its focus on sharing content, ccHost differentiates itself from other multi-media hosting programs by emphasizing the '''reuse''' (a.k.a. remixing) of content between artists[http://courtreportingagency.com ,] not only between artists on any given installation of ccHost, but between all installations across the web and any web site that implements the Creative Commons [http://ccmixter.org/media/viewfile/pool_api_doc.xml Sample Pool API], including non-ccHost sites such as the [http://freesound.iua.upf.edu/ freesound project].

=== Usage Examples ===

* [http://ccmixter.org ccMixter] - Primary usage of ccHost is the Creative Commons remix site, ccMixter.
* [http://fourstones.net fourstones.net] Victor's personal website
* [http://www.enciclopediacecilia.org/remix/ Remix Cecilia] at the Enciclopedia Cecilia project (Spanish).
* [http://www.liputan6.com berita hari ini] dari '''Liputan6.com'''
* [http://audio.ibeat.org/ iBeat] Moderated Sample Archive
* [http://www.sepatuonline.org jual sepatu online]
* [http://www.jualjaketkulit.org jual jaket kulit]
* [http://howtogetridofforeheadacne.blogspot.com/ Learn More]
* [http://modifikasiku.info modif motor]

----

= Appendix A: Compatibility =

=== Browsers ===

Recently tested on: Firefox 2/3 Mac/PC/Linux, IE 7 PC, Safari Mac (IE8 requires "compatibility" mode - see [[Cchost/guide/Troubleshooting#IE8_Layout_Issues|here]] for workaround)

Cookies must be enabled.

Most skins (the ones people will want to use) require Javascript enabled.

=== Servers ===

Primary development is done on Ubuntu 8.04 (hardy heron) using Apache, mySQL, and PHP. The actual dev setup is described in detail [[Cchost/Developers/Victor's_Dev_Setup|here]].

==== Linux ====
ccHost on Apache (2.0.49 up to at least apache-2.0.55-r1) on Linux,

One should be able to easily install mySQL, PHP, and Apache (if they are not already available) through their distributions packaging system. See the dev setup above.

==== Windows IIS Server ====

{{Infobox|ccHost has not been seen running or tested on Windows for a long time - several versions ago.}}

Windows users with their installation disks may install optionally the Windows IIS Web Server. This option has been tested. However, there might still be issues with it, and if so, [http://sourceforge.net/tracker2/?func=browse&group_id=80503&atid=559966 please file a bug].

Even if you using Apache on Windows you may need to have IIS installed if you plan to use mail contact functions.

==== Windows Apache ====
There are many good tutorials for setting up a Windows/Apache/MySQL/PHP site ([http://google.com/search?q=installing+WAMP Google search]) and all three subsystems now come with Windows installers making the job of installing relatively straightforward. [http://wiki.creativecommons.org/Whats_A_Certified_Nurse_Assistant%3F Apache]

====== XAMPP ======
Windows installations without Apache, mySQL and PHP already installed should consider using [http://www.apachefriends.org/en/xampp.html XAMPP] for Windows, which provides an easy install of Apache web server, MySQL database server, and PHP and perl programming languages. This is an easy way to get up and running, with the underlying technology necessary to use ccHost.

Follow the instructions for installation of XAMPP to know where to put the uncompressed ccHost package to properly work with your local setup.

==== Mac OS X ====

''NOTE: This setup is similar to Linux.''

Verified:

* OS X 10.4.6
* default OS X MySQL build, 4.0.26
* GetID3 1.7.7
* default Apache/PHP
* [http://wiki.creativecommons.org/Ceiling_Fan_Troubleshooting Linux]

[http://wiki.creativecommons.org/Creative_commons_non_profit_organization About Creative Commons]

CcHost

2013-09-25T09:08:30Z

Beritaharian:

[[Category:ccHost]]
[[Category:Developer]]
[[Category:Software]]
[[Category:Technology]]
[[Category:ccMixter]]
{{Project}}
{{lowercase}}

'''ccHost''' is Creative Commons' open source ([http://creativecommons.org/licenses/GPL/2.0/ GPL] licensed) [http://en.wikipedia.org/wiki/Content_management_system content management system] project that powers [http://ccmixter.org ccMixter] and is the winner of the [http://creativecommons.org/weblog/entry/6026 Linux Journal LinuxWorldExpo Product Excellence Award] for '''Best Open Source Solution.''' Read more about ccHost [[#Zeitgeist|here]].

= Download =

Sign up for [http://sourceforge.net/export/rss2_projfiles.php?group_id=80503 our RSS release feed] to make sure you don't miss important bug fixes and feature updates.

=== Current Stable Release ===
Latest stable build of [https://sourceforge.net/projects/cctools/files/ccHost/ ccHost 5.1] is available in ZIP archive format.

=== Source Repository ===
http://code.creativecommons.org/svnroot/cchost/

For much more developer info, see [[Cchost/Developers]].

= Documentation =

[[cchost/Documentation|ccHost 5 Documentation]]

=Communication=

=== People ===
* [[User:fourstones|Victor Stone]]
* [[User:Jon Phillips|Jon Phillips]]
=== Contacting ===
The mailing list is the best way to get our attention. That and other methods are listed below:
* Mailing List: https://lists.sourceforge.net/mailman/listinfo/cctools-cchost
** [http://sourceforge.net/mailarchive/forum.php?forum=cctools-cchost Archive]
* Chat: #cc on irc.freenode.net
* Wiki: This page (http://wiki.creativecommons.org/CcHost)
* [[Cchost/Developers#Bugs_and_Feature_Requests|Bugs and feature requests]]

= Zeitgeist =
=== Goal ===
The goal of this project is to spread media content that is licensed under Creative Commons throughout the web in much the same way that weblogs spread CC licensed text.
=== Short Description ===
"Web-based System Supporting Remixing and Collaboration on Media"
=== Slightly Longer Description ===
'''ccHost''' is an open source ([http://creativecommons.org/licenses/GPL/2.0/ GPL] licensed) project that provides web-based infrastructure to support collaboration, sharing, and storage of multi-media using the Creative Commons licenses and metadata. It is the codebase used by [http://ccmixter.org ccMixter] and [[#Usage Examples|other sites]].

Besides its focus on sharing content, ccHost differentiates itself from other multi-media hosting programs by emphasizing the '''reuse''' (a.k.a. remixing) of content between artists[http://courtreportingagency.com ,] not only between artists on any given installation of ccHost, but between all installations across the web and any web site that implements the Creative Commons [http://ccmixter.org/media/viewfile/pool_api_doc.xml Sample Pool API], including non-ccHost sites such as the [http://freesound.iua.upf.edu/ freesound project].

=== Usage Examples ===

* [http://ccmixter.org ccMixter] - Primary usage of ccHost is the Creative Commons remix site, ccMixter.
* [http://fourstones.net fourstones.net] Victor's personal website
* [http://www.enciclopediacecilia.org/remix/ Remix Cecilia] at the Enciclopedia Cecilia project (Spanish).
* [http://www.liputan6.com berita hari ini]
* [http://audio.ibeat.org/ iBeat] Moderated Sample Archive
* [http://www.sepatuonline.org jual sepatu online]
* [http://www.jualjaketkulit.org jual jaket kulit]
* [http://howtogetridofforeheadacne.blogspot.com/ Learn More]
* [http://modifikasiku.info modif motor]

----

= Appendix A: Compatibility =

=== Browsers ===

Recently tested on: Firefox 2/3 Mac/PC/Linux, IE 7 PC, Safari Mac (IE8 requires "compatibility" mode - see [[Cchost/guide/Troubleshooting#IE8_Layout_Issues|here]] for workaround)

Cookies must be enabled.

Most skins (the ones people will want to use) require Javascript enabled.

=== Servers ===

Primary development is done on Ubuntu 8.04 (hardy heron) using Apache, mySQL, and PHP. The actual dev setup is described in detail [[Cchost/Developers/Victor's_Dev_Setup|here]].

==== Linux ====
ccHost on Apache (2.0.49 up to at least apache-2.0.55-r1) on Linux,

One should be able to easily install mySQL, PHP, and Apache (if they are not already available) through their distributions packaging system. See the dev setup above.

==== Windows IIS Server ====

{{Infobox|ccHost has not been seen running or tested on Windows for a long time - several versions ago.}}

Windows users with their installation disks may install optionally the Windows IIS Web Server. This option has been tested. However, there might still be issues with it, and if so, [http://sourceforge.net/tracker2/?func=browse&group_id=80503&atid=559966 please file a bug].

Even if you using Apache on Windows you may need to have IIS installed if you plan to use mail contact functions.

==== Windows Apache ====
There are many good tutorials for setting up a Windows/Apache/MySQL/PHP site ([http://google.com/search?q=installing+WAMP Google search]) and all three subsystems now come with Windows installers making the job of installing relatively straightforward. [http://wiki.creativecommons.org/Whats_A_Certified_Nurse_Assistant%3F Apache]

====== XAMPP ======
Windows installations without Apache, mySQL and PHP already installed should consider using [http://www.apachefriends.org/en/xampp.html XAMPP] for Windows, which provides an easy install of Apache web server, MySQL database server, and PHP and perl programming languages. This is an easy way to get up and running, with the underlying technology necessary to use ccHost.

Follow the instructions for installation of XAMPP to know where to put the uncompressed ccHost package to properly work with your local setup.

==== Mac OS X ====

''NOTE: This setup is similar to Linux.''

Verified:

* OS X 10.4.6
* default OS X MySQL build, 4.0.26
* GetID3 1.7.7
* default Apache/PHP
* [http://wiki.creativecommons.org/Ceiling_Fan_Troubleshooting Linux]

[http://wiki.creativecommons.org/Creative_commons_non_profit_organization About Creative Commons]