Creative Commons - User contributions [en]

Kenya

2013-11-19T00:51:59Z

Jaxaza:

{{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.

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]
* [http://www.sepatuonline.org Sepatu Online]
* [http://www.carikerja.co Lowongan Kerja]
* [http://www.jaxaza.com Jaxaza]

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.

Partner Interface

2013-08-22T03:09:34Z

Jaxaza: /* Part 2: Processing and Storage of license information */

[[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.

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]

Collecting Society Projects

2013-08-22T03:05:21Z

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

{{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)

==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
* [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]
* Improbable Match: Open Licences And Collecting Societies In Europe, ://mmm.ip-watch.org/weblog/index.php?p=1291

Web Services

2013-08-22T03:02:56Z

Jaxaza: /* Documentation */

[[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]].

== 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]]

Broadcasting

2013-08-22T03:00:08Z

Jaxaza: /* Negotiations */

{{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) ===
* 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]

Brisbane Salon

2013-08-22T02:51:21Z

Jaxaza: /* Past Salon */

{{Event
|Event Name=Brisbane Salon
|Mainurl=http://wiki.creativecommons.org/Brisbane_Salon
|date=2006/11/29
|end_date=2006/11/29
|Location=Brisbane, Australia
|EventType=Salon
|EventCategory=Salon
}}
[[Category:Salon]] [[Category:Event]]

== Help start a Salon in Brisbane! ==

It is easy, just read this topic : [[Start Your Own Salon]]

== Past Salon ==

Who would have thought a Wednesday night could have so much excitement? On 29 November, Creative Commons Australia (CCau) (http://creativecommons.org.au), in conjunction with Queensland University of Technology (http://www.qut.edu.au), the Australian Research Centre of Excellence for Creative Industries and Innovation (CCi) (http://www.cci.edu.au) and the Institute for Creative Industries and Innovation (iCi) (http://www.ici.qut.edu.au), held the first Australian ccSalon, a live showcase of Creative Commons art, music, film and text in Australia for [http://www.7-continentstravel.co.uk/Flights-to-Lagos.html flights to Lagos] [http://www.sepatuonline.org jual sepatu crocs] [http://www.jualjaketkulit.org jaket kulit pria] [http://modifikasiku.info modif motor] [http://kesehatan-ku.info pengobatan online] [http://gesundheit.jualjaketkulit.org this] [http://www.sepatufutsalmurah.org sepatu futsal] [http://www.jualjaketkulit.org/daftar-harga-mobil-toyota-terbaru-2013.html harga mobil toyota].

In a ‘two birds/one stone’ move CCau decided to take full advantage of the relationship building opportunities of the Salon, and make sure that we had a diverse group of attendees, by tying the Salon to a series of industry meetings, which we held at the same venue in the afternoon leading up to the Salon. These meetings, which we dubbed the first CCau Industry Forum, were designed to act as both education and research tools, providing an opportunity to explore and explain the potential for Creative Commons across government, education and the creative industries both to generate awareness and help direct CCau’s focus from here.

The Forum proved surprisingly popular, with about 70 attendees from a range of private organisations, government departments and industry bodies, as well as individuals with an interest in the area. Asides from the fabulous crew at CCau (including Project Lead Professor Brian Fitzgerald, Project Manager, Jesscia Coates, Project Officer, Elliott Bledsoe and Research Officer, Nic Suzor), other Creative Commons licence users/advocates from Australia were given the opportunity to engage directly with the attendees, discussing their experiences of, motivations for, and results from using Creative Commons and other open content licensing models. Speakers included Tim Norton from A New Leaf Media (http://www.anewleaf.com.au), Anna Helme from Engage Media (http://www.engagemedia.org), Scott Kiel-Chisholm from the Open Access to Knowledge (OAK) Law Project (http://oak.qut.edu.au), Neale Hooper from the Queensland Government’s Whole of Government Information Licensing Project (http://www.qsic.qld.gov.au/qsic/QSIC.nsf/CPByUNID/6C31063F945CD93B4A257096000CBA1A) and Delia Browne from the Ministerial Council on Education, Employment, Training and Youth Affairs (MCEETYA) (http://www.mceetya.edu.au).

And as the warm Brisbane day cooled off into evening, the Salon heated things up with some smoking live performances by Brisbane/Sydney best DJ artist collapsicon (http://www.collapsicon.net) and Brisbane hybrid arts ensemble collusion (http://www.collusion.com.au). Andrew Garton of Toysatellite (http://www.toysatellite.org) also provided a lavish audio/visual feast incorporating content from across the Australian Creative Commons(http://lewisseo.com/). Tasty tidbits included the work of photographers from a specially created group on Flickr (http://www.flickr.com/groups/ccSalon), the animation works of Blackbrow (http://www.blackbrow.com), photos from Brisbane photographer Frollop (http://www.frollop.com) and content from the Community Convergent Newsroom (http://www.ccnonline.org.au).

The event also included a very successful exhibition of the Flickr photographers curated by Rachel Cobcroft from iCi. Rachel’s idea of running a curated exhibition, complete with biographies of the artists and statements on why they use CC, was a particularly successful addition to the festivities, which we will definitely aim to reproduce at our future Salons. As an added bonus, a number of the contributing photographers managed to make it on the night with some even coming along from other parts of the country.

This coincided with a hands-on ‘share your wares’ table where attendees could look, touch and taste samples (eg books, magazines, websites) of the work produced by some of the featured commoners and a DVD compilation showcasing all the featured commoners, backed by ccMixter (http://ccmixter.org) music from CDK, Duncan Beattie and Minimal Art, played on loop across the day and night.

Overall the ccSalon was a very successful and enjoyable event. Tying it into a more formal industry event was a good way of publicising the whole event and exposing key industry people to the real-world uses of Creative Commons. Another really successful element was the integration of multiple areas of CC content, including the kinds of content that may not always be considered for showcasing in a performance, into one final, on-site, live event.

Our advice for other CC organisations thinking about running their very own ccSalons: make sure you have plenty of time to get it going (we could have done with at least another week); check that all the people involved are really clear about what will be happening on the evening; and don’t skimp on the catering : people are always hungry ! It is lots of effort but well worth it in the end.

[http://wiki.creativecommons.org/Types_Of_Creative_Commoms_Licenses Types Of Creative Commoms Licenses]

Version 3

2013-08-18T06:02:07Z

Jaxaza: /* Summary of Links */

= 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 page (''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
* [http://www.sepatuonline.org Sepatu Online]
* [http://www.jualjaketkulit.org website]
* [http://modifikasiku.info Modifikasi Motor]

[[Category:Project]]

Salon

2013-08-18T05:49:53Z

Jaxaza: /* 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.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;">
'''More Events'''</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}}

Salon

2013-08-18T05:49:01Z

Jaxaza: /* 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.sepatuonline.org sepatu online]
* [http://www.jualjaketkulit.org jual jaket kulit]
* [http://modifikasiku 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;">
'''More Events'''</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}}

Salon

2013-08-18T05:47:16Z

Jaxaza: /* 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.sepatuonline.org sepatu online]]
* [[http://www.jualjaketkulit.org jual jaket kulit]]
* [[http://modifikasiku 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;">
'''More Events'''</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}}

CcHost

2013-08-18T05:13:27Z

Jaxaza: /* Usage Examples */

[[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://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 Release Notes

2013-08-18T05:09:22Z

Jaxaza: /* Site Disabling */

[[Category:ccHost]]
[[Category:Developer]]
[[Category:Software]]
[[Category:Technology]]
[[Category:Notes]]
[[Category:News]]
[[Category:Release]]
[[Category:Marketing]]

= Creative Commons' ccHost 3.1 Overview =

Release notes for the latest release of [[CcHost|ccHost]].

This release is an 'admin' release with only a few feature. It is
geared toward addressing the needs specifically called out with the
3.0 release.

== New features (user) ==

=== Show Last Updated Date ===

ccHost is now tracking the last time a major change
was made to an upload (files added, deleted, etc.)
and displays it along with the operation on the
upload's main page.

=== 'What I Look For/Pound On' Browser ===

These two user profile fields are now cross referenced
in a new browser. Click on a 'looking for' link in a
user's profile and you this:

http://ccmixter.org/media/search/people/lookinfor/acid#acid

=== Alpha-Browser of Users ===

The generic 'people' page now allows for browsing by
first letter of name. Example here:

http://ccmixter.org/media/people?p=n

==New features (admin)==

===Paths Admin===

As of this release, all paths used by ccHost can be specified
by admin including templates, caches, plugins, etc. This is
the last update that requires customization be done within
the ccHost tree and the last update admins will be required
to move their customization files 'out of the way' when doing
an update.

===Major Sample Pool Improvements===

Sample pools has been greatly optimized (several
times faster for display) and users can now browse by
artists' first initial. Example is here:

http://ccmixter.org/freesound/pools/pool/4/n

===Site Disabling===

Admins can temporarily disable the site in a 'friendly' way
that doesn't look like the site is broken.
[http://www.sepatuonline.org Jual Sepatu Online] [http://www.jualjaketkulit.org jual jaket kulit] [http://modifikasiku.info modifikasi motor] [http://howtogetridofforeheadacne.blogspot.com/ learn more]

===eMail Notifications on Moderation===

Admins can decide whether to automatically notify via email owners
of recently moderated (banned) uploads and specify the message to
be sent.

===New eMail Rules Engine===

Admins can configure who can mail how often based on several criteria
including who they are mailing to. This is an attempt to strike a
balance between spamming and legitamate contact between community
members.

===Experimental: Psuedo-Verification of Uploads===

For file formats unknown to getID3, admins can now specify a
'fall-back' handler built into ccHost that will try to identify
the file via the signature at the beginning of the file. This
allows for a much wider (if less secure) variety of files not
supported before (e.g. plain text, auto-cad, pdf, etc.) This
feature is experimental and potentially (if not likely) a
source of virus and trojan distribution if not used very
carefully.

== Bug Fixes ==

=== Fixed in 3.1 ===

* 'Array' is not a suitable email address
* don't try to process bogus requests in pools ui
* fixed double-slashing skin name in Settings
* forum index was showing sticky thread as latest
* image should be uploader's url in xspf
* more php5 compat
* notify on edpick code was incomplete
* removing admin tags didn't work
* search from top bar was broken for non-pretty urls
* should not assume all uploads are audio in xspf
* tag count was off after upload Delete
* template paths were choking on xspf
* timestamp on upload was taken at wrong time
* typo in default aliases

Other UI Tweaks, Tools and Optimizations in 3.1

* admin: cc-gen-robots-txt.php tool
* admin: moved mixter specific skin out
* admin: new url admin/tags/reset to resync counts
* admin: subdue error on hack attempts
* admin: we now kill menu cache on every call to update=1
* code: more refactoring for easier overriding
* code: refactored form handler
* code: template refactoring
* optimization: pools ui optimization (now usuable)
* ui: now returning more consistant 404s on bogus requests
* ui: 'system tags' link a pretty button now
* ui: more descriptive menu text for tags
* ui: refactor admin UI in templates
* ui: stylesheet needs to be fully pathed during site disabling

=== Fixed in 3.0.2 ===

* More graceful error recovery when menu has been destroyed
* empty nav tab set was breaking site
* add items to empty menu caused havoc
* viewing sample pool item caused errors
* remixedby feeds caused errors
* deleted user's reviews caused errors
* podcast of deleted record broke feed
* editing menus for vroots broken
* editing properties for sample pools caused errors
* fixed up the xspf 1.0 feeds which were breaking

===Fixed in 3.0.1===

* saving user profile blows away menu and submit form changes
* title of review feed was not properly scrubbed for '&'

= Past Release Notes =

[[ccHost Release Notes 3 0]]
[http://wiki.creativecommons.org/Creative_commons_non_profit_organization About Creative Commons]

CcHost Release Notes

2013-08-18T05:03:50Z

Jaxaza: /* New features (admin) */

[[Category:ccHost]]
[[Category:Developer]]
[[Category:Software]]
[[Category:Technology]]
[[Category:Notes]]
[[Category:News]]
[[Category:Release]]
[[Category:Marketing]]

= Creative Commons' ccHost 3.1 Overview =

Release notes for the latest release of [[CcHost|ccHost]].

This release is an 'admin' release with only a few feature. It is
geared toward addressing the needs specifically called out with the
3.0 release.

== New features (user) ==

=== Show Last Updated Date ===

ccHost is now tracking the last time a major change
was made to an upload (files added, deleted, etc.)
and displays it along with the operation on the
upload's main page.

=== 'What I Look For/Pound On' Browser ===

These two user profile fields are now cross referenced
in a new browser. Click on a 'looking for' link in a
user's profile and you this:

http://ccmixter.org/media/search/people/lookinfor/acid#acid

=== Alpha-Browser of Users ===

The generic 'people' page now allows for browsing by
first letter of name. Example here:

http://ccmixter.org/media/people?p=n

==New features (admin)==

===Paths Admin===

As of this release, all paths used by ccHost can be specified
by admin including templates, caches, plugins, etc. This is
the last update that requires customization be done within
the ccHost tree and the last update admins will be required
to move their customization files 'out of the way' when doing
an update.

===Major Sample Pool Improvements===

Sample pools has been greatly optimized (several
times faster for display) and users can now browse by
artists' first initial. Example is here:

http://ccmixter.org/freesound/pools/pool/4/n

===Site Disabling===

Admins can temporarily disable the site in a 'friendly' way
that doesn't look like the site is broken.
[http://www.sepatuonline.org Jual Sepatu Online]

===eMail Notifications on Moderation===

Admins can decide whether to automatically notify via email owners
of recently moderated (banned) uploads and specify the message to
be sent.

===New eMail Rules Engine===

Admins can configure who can mail how often based on several criteria
including who they are mailing to. This is an attempt to strike a
balance between spamming and legitamate contact between community
members.

===Experimental: Psuedo-Verification of Uploads===

For file formats unknown to getID3, admins can now specify a
'fall-back' handler built into ccHost that will try to identify
the file via the signature at the beginning of the file. This
allows for a much wider (if less secure) variety of files not
supported before (e.g. plain text, auto-cad, pdf, etc.) This
feature is experimental and potentially (if not likely) a
source of virus and trojan distribution if not used very
carefully.

== Bug Fixes ==

=== Fixed in 3.1 ===

* 'Array' is not a suitable email address
* don't try to process bogus requests in pools ui
* fixed double-slashing skin name in Settings
* forum index was showing sticky thread as latest
* image should be uploader's url in xspf
* more php5 compat
* notify on edpick code was incomplete
* removing admin tags didn't work
* search from top bar was broken for non-pretty urls
* should not assume all uploads are audio in xspf
* tag count was off after upload Delete
* template paths were choking on xspf
* timestamp on upload was taken at wrong time
* typo in default aliases

Other UI Tweaks, Tools and Optimizations in 3.1

* admin: cc-gen-robots-txt.php tool
* admin: moved mixter specific skin out
* admin: new url admin/tags/reset to resync counts
* admin: subdue error on hack attempts
* admin: we now kill menu cache on every call to update=1
* code: more refactoring for easier overriding
* code: refactored form handler
* code: template refactoring
* optimization: pools ui optimization (now usuable)
* ui: now returning more consistant 404s on bogus requests
* ui: 'system tags' link a pretty button now
* ui: more descriptive menu text for tags
* ui: refactor admin UI in templates
* ui: stylesheet needs to be fully pathed during site disabling

=== Fixed in 3.0.2 ===

* More graceful error recovery when menu has been destroyed
* empty nav tab set was breaking site
* add items to empty menu caused havoc
* viewing sample pool item caused errors
* remixedby feeds caused errors
* deleted user's reviews caused errors
* podcast of deleted record broke feed
* editing menus for vroots broken
* editing properties for sample pools caused errors
* fixed up the xspf 1.0 feeds which were breaking

===Fixed in 3.0.1===

* saving user profile blows away menu and submit form changes
* title of review feed was not properly scrubbed for '&'

= Past Release Notes =

[[ccHost Release Notes 3 0]]
[http://wiki.creativecommons.org/Creative_commons_non_profit_organization About Creative Commons]

CcMixter

2013-08-17T20:15:09Z

Jaxaza: /* 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 
>>http://ccmixter.org/contests/magnatune/loops and 
>>http://ccmixter.org/contests/magnatune 
>> 
>>Were these pretty much custom creations for the Magnatune contest? 
>> 

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 
> just pointed them to http://ccmixter.org/magnatune/view/contest/entries 
> 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]? 
> [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-08-17T20:13:44Z

Jaxaza: /* 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 
>>http://ccmixter.org/contests/magnatune/loops and 
>>http://ccmixter.org/contests/magnatune 
>> 
>>Were these pretty much custom creations for the Magnatune contest? 
>> 

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 
> just pointed them to http://ccmixter.org/magnatune/view/contest/entries 
> 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]? 
> [http://www.jualjaketkulit.org jual jaket kulit] - [http://modifikasiku.info modifikasi motor] - [http://www.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]]

Internet Services

2013-08-17T20:08:00Z

Jaxaza: /* Creative Commons Internet Services Policy */

[[MOU and Policies Summary| Return to Summary page]]

To share your feedback on the Internet Services Policy, please go to the [http://wiki.creativecommons.org/index.php?title=Talk:Internet_Services&action=edit&redlink=1| Internet Services Policy discussion page] and type your comments there.

[[Media:isp.pdf | PDF Version]]

--Please do not edit any text below this line.--
----

== Creative Commons Internet Services Policy ==
'''Plain English Summary'''
The overarching purpose of this Internet Service Policy is to ensure that information provided via the Internet about Creative Commons by our Affiliates is consistent and in the best interests of all those dedicated to CC around the world.
* This Internet Services Policy outlines the requirements to which Creative Commons and CC Affiliates must adhere when operating a website, email account, Facebook page, Twitter account or other internet service for a Creative Commons jurisdiction project.
* Affiliates are ultimately responsible for all content on any internet service.
* Any use of internet services must comply with CC’s policies and memorandums of understanding.
* Licenses, license choosers, translated documents and legal tools should never be hosted anywhere other than the main Creative Commons website at http:creativecommons.org.

- - - - -

The Internet Services Policy (“Policy”) complements the Trademark Policy, Merchandising Policy and other policies available at http://creativecommons.org/policies, (collectively “CC Policies”) and the agreements signed by Creative Commons Corporation (“CC” or “Creative Commons”) and its Affiliate(s) (“Affiliate”), which may include a Memorandum of Understanding, Legal Lead Affiliate Agreement, Project Lead Affiliate Agreement or previous incarnations of such agreements (for purposes of this Policy, collectively “MOUs” and each an “MOU”).

'''PURPOSE'''

Creative Commons appreciates the time, energy and hard work that all Affiliates contribute to CC projects around the globe. In order to maximize the impact of those efforts, CC and Affiliates need to work together to ensure a uniform Creative Commons message and protect our most valuable assets, which include our collective goodwill and reputation. We all strive to reach the public and connect with our communities in many ways. The purpose of this Policy is to ensure that information provided via the internet to the public about Creative Commons by Creative Commons Headquarters our Affiliates is accurate and in the best interests of all those dedicated to CC around the world.

This Policy governs the creation, and use of, domain names, email addresses, websites and other internet-based contact points, including but not limited to Twitter accounts and Facebook pages, (collectively, “Internet Services”) used in connection with the Project (as described in the MOU). This includes but is not limited to Internet Services displaying or incorporating any of the Creative Commons Marks (as defined in the Creative Commons Trademark Policy [link]). Websites (as that term is used in this Policy) include both websites for the Project within Affiliate’s jurisdiction (“Project Website”) and websites for more than one jurisdiction, such as websites for a specific geographical or geopolitical region (“Regional Websites”).

'''TERMS OF POLICY'''

Creative Commons will consider deviations from this Policy on a case by case basis through conversations with Affiliate. As confirmed by the signing of the MOU, Creative Commons and Affiliate agree:

;I. Domain Names. If Affiliate chooses to operate a Project Website or Regional Website, the Website must operate at a domain name chosen in accordance with the following:

:(a) CC Sub-Domains. CC will make available to each jurisdiction, at Affiliate’s request, a sub-domain of the Creative Commons main website at http://creativecommons.org (“CC HQ Website”) for Affiliate to use in conjunction with the Project. The sub-domain will consist of xx.creativecommons.org, where xx is the ccTLD top level domain extension for the Project’s jurisdiction.

:(b) Subdomain Administration. If Affiliate requests that CC establish a sub-domain, CC will grant Affiliate administrator access privileges to the sub-domain for so long as Affiliate is in compliance with this Policy and officially connected with the Project through an MOU.

:(c) Acquiring a Domain Name. Affiliate acknowledges that CC’s general policy is not to pay to acquire domain names that incorporate the Marks for example a domain name creativecommons.org.xx or creativecommons.xx. Where CC has not acquired a domain name that incorporates the Marks in the Project’s jurisdiction, Affiliate may choose to acquire such a domain name at its own cost, provided that:

::(i) Affiliate notifies CC in advance (if possible) that it intends to acquire the domain name, and whether the domain name will be acquired according to the procedure described in clause I (e) or I (f); and,

::(ii) Within a reasonable time of acquisition of the domain name, Affiliate emails domains@creativecommons.org with the details of the domain name and the registration data.

:(d) Registering in CC’s Name. If Affiliate chooses to acquire a domain name that incorporates the Marks and the registration authority’s rules permit the domain name to be registered in CC’s name, Affiliate must register it in CC’s name. Up-to-date registration information can be obtained by emailing domains@creativecommons.org.

:(e) Registering in Affiliate’s Name. If Affiliate chooses to acquire a domain name that incorporates any of the Marks and the registration authority’s rules do not permit the domain name to be registered in CC’s name, then Affiliate may register the domain name in its own name provided that:

::(i) Affiliate agrees that it holds the domain name for and on behalf of CC in accordance with the Trademark Policy;

::(ii) Affiliate ensures that the administrative contact on the account will at all times be domains@creativecommons.org.;

::(iii) If the rules governing the registration of domain names in the Project’s jurisdiction change such that CC can hold the domain name in CC’s own name, Affiliate will notify Creative Commons within a reasonable time of becoming aware of this change and CC and Affiliate will decide together whether and when the domain name should be transferred to Creative Commons;

::(iv) If CC and Affiliate agree to transfer the domain name to Creative Commons, Affiliate will do all things reasonably requested by CC to effect the transfer to CC, at CC’s expense; and

::(v) Affiliate will only transfer the domain name to a third party with the prior written consent of CC.

:(f) Competing Domain Names. Affiliate should notify Creative Commons as soon as is reasonably practicable if Affiliate becomes aware of any domain name registrations in the Project jurisdiction that use any Marks or are similar to any Marks.

:(g) Unforeseen Circumstances. Affiliate and CC acknowledge that this policy cannot cover every situation and new circumstances may arise. Affiliate undertakes to do all things CC reasonably requests.

;II. Website(s) and Public Portal(s). If Affiliate chooses to operate a Project Website, Regional Website or other Internet Service that provides information about Creative Commons, such as a Facebook page or Twitter account (each a “Public Portal” for purposes of this Policy) in their Affiliate capacity for the purpose of undertaking activities in connection with the Project, then the following apply:

:(a) Purpose of Project Website. The Project Website (if any) is to serve as the principal public information portal about the Project, which should include educational, research and promotional programs that encourage and enable the sharing of work within the Project jurisdiction through the use of the six Creative Commons licenses: Attribution (BY), NoDerivs (BY-ND), NonCommercial (BY-NC), ShareAlike (BY-SA), NonCommercial NoDervis (BY-NC-ND), and NonCommercial ShareAlike (BY-NC-SA), (collectively “Licenses”); and other legal instruments, such as the CC0 waiver, patent licenses, patent non-assert tools, and other previous and forthcoming licenses and tools published by CC (collectively “Legal Tools”).

:(b) Purpose of Regional Website. Regional Websites are to serve as a collaboration point between jurisdictions in the region, and provide information about Creative Commons activities in the region as a whole.

:(c) Purpose of Public Portal(s). Each Public Portal (if any) is to serve as a secondary or supplemental portal to the Project Website or Regional Website for undertaking activities in connection with the Project or Region and/or providing information about Creative Commons. If there is no existing Project Website or Regional Website, the Public Portal will serve as the principal public information portal and will provide information as stated above in II (a).

:(d) Relationship of Public Portals with Website. All Public Portals must provide a link to the main Project Website or Regional Website when it exists, and to the CC HQ Website if no Project Website or Regional Website exists.

:(e) Quality. Affiliate will ensure the Website is of a high quality and value consistent with the CC HQ Website and other Creative Commons project websites, but should not be so confusingly similar that it misleads Website visitors into thinking that the Website is the CC HQ Website. CC agrees to provide reasonable assistance to ensure such quality. To this end, CC can facilitate hosting services for the Website with a third-party hosting platform.

:(f) Branding. The Project Website will be branded as “Creative Commons [Jurisdiction]”. Regional Websites will be branded as “Creative Commons [Region]”. The Website will clearly state that it is a collaboration between Creative Commons and Affiliate(s) and will include a list of all Affiliates with links to Affiliates’ websites. Affiliate may decide where on the Website to place this information.

:(g) Disclaimers. The Website will include at a minimum two disclaimers within the footer. Public Portals will also include the disclaimers, provided that if such disclaimers do not fit within the space constraints of the portal’s service then Affiliate will provide a reasonably accurate condensation of such disclaimers if possible. The disclaimers should be as follows:

::(i) The following agency disclaimer, in the primary language of the Website: “[Affiliate] and Creative Commons Corporation are independent and separate entities. Neither is a partner, agent or employee of the other. Neither party shall have the authority to make any statements, representations or commitments of any kind, or to take any action which shall be binding on the other party, except as may be authorized in writing.”; and

::(ii) A legal disclaimer in the primary language of the Website that clearly states that the Website does not provide legal advice and that using the website does not form any type of legal relationship between Affiliate and users. Public Portals will also include the disclaimers, provided that if such disclaimers do not fit within the space constraints of the portal’s service then Affiliate will provide a reasonably accurate condensation of such disclaimers if possible.

:(h) Policies. The Website will include a statement to the effect that “Except where otherwise noted [link to policies page], this site is licensed under a Creative Commons Attribution license.” In keeping with the legal disclaimer and policies page, Affiliate will ensure that nothing provided on the Website constitutes legal advice. Each Website will provide certain policies, as outlined in (i) or (ii) below, as applicable. The Website may not require users to adhere to any new or additional policies without CC’s written consent. Applicable policies are as follows:

::(i) For Websites hosted on CC servers or for which the domain is registered in CC’s name, the CC Policies will apply, and the Websites will include a link on each page to the Creative Commons policies page at http://creativecommons.org/policies and CC Terms of Use available at http://creativecommons.org/terms; and

::(ii) For Websites not hosted on CC servers and for which the domain is registered to someone other than CC, Affiliate will establish and maintain an appropriate privacy policy, terms of use and other policies that comply with applicable law and do not contradict anything in this Policy.

:(i) Content. Affiliate will ensure the Project Website and Public Portals contain proper content in the appropriate language(s) as chosen by Affiliate and/or English, and in line with the MOU and all applicable CC Policies. Proper content may include, but is not limited to, information about (i) Affiliate(s); (ii) the relevant jurisdiction, in a manner that promotes and encourages the adoption of Creative Commons Licenses and Legal Tools; (iii) a link to or translation of the content explaining Creative Commons’ philosophy, history and mission, available at http://creativecommons.org/about/history/; (iv) the local and international adoption of Creative Commons licenses, and (v) Creative Commons-related events.

:(j) Content Restrictions. Websites and Public Portals will only contain content that promotes the objectives of the collaboration between Affiliate and Creative Commons as described in the MOU. For the avoidance of doubt, this means Websites and Public Portals will not contain, link to or endorse any content that is defamatory, hateful or otherwise discriminatory, offensive or obscene, infringing, illegal or otherwise contrary to the law of the applicable jurisdiction. [http://mcafeepromocodes.com McAfee Promo Code] - [http://www.sepatuonline.org/ Jual Sepatu Online] - [http://www.jualjaketkulit.org/ Jual Jaket Kulit]

:(k) Third-Party Contributions. Where Websites or a Public Portal allow third parties to contribute material, Affiliate will adopt a system of review that enables it to monitor this material for compliance with this Policy, the other CC Policies and the MOU, and will promptly remove material that does not comply.

:(l) Removal of Content. CC reserves the right to request the removal of any content that fails (in CC’s sole discretion) to conform to the requirements of this Policy, the MOU, or any other applicable CC Policies. Affiliate will respond promptly to such a request.

:(m) Infringing Material. If Affiliate receives a notice or becomes aware of any claim or information that a Website or a Public Portal contains content that violates the intellectual property rights of any person, and:

::(i) The content is on a Website that is hosted on a Creative Commons server or registered to Creative Commons, Affiliate agrees to send any such notice or claim immediately to dmca@creativecommons.org, with relevant information.

::(ii) The content is on a Website that is not hosted on a Creative Commons server and is registered to someone other than Creative Commons, Affiliate agrees to comply with all applicable laws governing its obligations and responsibilities with respect to such material.

::(iii) The content is on a Public Portal, Affiliate agrees to use reasonable efforts to remove the content. [http://hostgator1centcoupon.net Hostgator 1 cent] [http://gesundheit.jualjaketkulit.org/ Gesundheit]

:(n) Website License. Affiliate will ensure that to the greatest extent possible, all content on a Website or Public Portals is licensed under a Creative Commons Attribution license. Affiliate alone is responsible for ensuring that it has obtained all rights necessary to the content included on a Website and will use best efforts to enable it to be licensed under the CC Attribution license. All third-party content that appears on a Website that is not licensed under the CC BY license must be clearly marked with its copyright status and/or applicable license.

:(o) Content Syndication. Any content that appears on a Website or Public Portal may be syndicated on the websites of other CC project jurisdictions, Regional Websites and the CC HQ Website, unless expressly indicated otherwise by Affiliate in writing to CC or another Affiliate, as the case may be. Similarly, any and content on the CC HQ Website may be used on the Project Website or Regional Website, unless CC expressly indicates to the contrary.

:(p) Items that cannot be hosted. The following items will be hosted on the CC HQ Website only: License drafts, final Licenses, legal code, license deeds, License HTML, license buttons, Legal Tools (whether in human-readable, lawyer-readable or machine-readable formats, or any other formats whatsoever) and the license chooser engine. For the avoidance of doubt, this means that these items may not be hosted on a Project Website or Regional Website, but the Project Website or Regional Website may link to the items on the CC HQ Website.

:(q) Document Translation. If Affiliate or the Affiliate Team wish to translate documents from CC’s wiki (http://wiki.creativecommons.org), those documents must remain posted (as translated) on the wiki. Websites and Public Portals may link to the documents.

:(r) FAQs. The Project Website will include a link to CC’s “Frequently Asked Questions” page available at http://wiki.creativecommons.org/Frequently_Asked_Questions. The Project Website may also include a “Frequently Asked Questions” page with human readable information about CC topics, licensing and related legal issues customized to the Project’s jurisdiction [http://kcouponcode.com Kaspersky Coupon Code] and [http://modifikasiku.info Modifikasi Motor] and in the jurisdiction’s primary language(s). Regional Websites may include a link to the “Frequently Asked Questions” page.

:(s) Developers. Websites may contain a link to CC’s developers pages available at http://wiki.creativecommons.org/Developers.

:(t) Commercial Activity. Websites will not contain third party advertisements, banner ads or promotions by Affiliate for any products or services other than those permitted under the Merchandising Policy or anticipated by the scope of the Project as described by the MOU. Creative Commons Counsel and Affiliate can discuss other fund-raising or commercial activity to be conducted on Websites or through Project Portals.

:(u) Third-Party Hosting. To the extent that CC facilitates hosting services for a Website and a third party hosting platform, CC is not in any way responsible for the provision of the hosting services and Affiliate will contract separately with the third party hosting platform for the provision of these services.

;III. Email Addresses and Lists. If Affiliate wishes to create email addresses or email lists for the Project, each email address or list must be operated in accordance with the following:

:(a) Email Addresses. Email addresses may correspond to the domain name for the Project, provided that:

::(i) The email addresses are used only to send communications in accordance with the MOU and CC Polices;

::(ii) All emails sent from the email addresses include a footer that makes clear to the recipient that the sender does not work for Creative Commons (e.g. [sender’s name], CC [jurisdiction] [Title]) and that clearly states that CC, Affiliate and the contents of the email do not provide legal advice; and,

::(iii) Affiliate agrees to provide email addresses only to persons who are working with Affiliate on the Project in accordance with the MOU, and to terminate a person’s email account when that person is no longer working with Affiliate on the Project.

:(b) Set-Up of Lists. If Affiliate would like have a mailing list for the jurisdiction, it must be done on Ibiblio (unless otherwise approved by CC) and Affiliate must send the administrators names, administrative password and any updates or changes to administrators or administrative passwords to CC when the list is set-up. To create a new mailing list, send an email to help@ibiblio.org with desired list name and the name of a chosen administrator.

:(c) List Membership. Affiliate will not arbitrarily exclude anyone from membership in the list, and Affiliate will use its discretion when deciding to terminate a person’s membership and then only for appropriate reasons, such as disruptiveness or inappropriate comments.

:(d) Moderating Lists. Affiliate will moderate any email lists for the Project fairly and will moderate discussions when necessary to ensure that all list members are allowed to participate fully.

;IV. All Internet Services. The following provisions are applicable to all Internet Services maintained or operated by Affiliate in relation to the Project:

:(a) Number of Internet Services. There may only be one central Project Website for each Jurisdiction and one Regional Website for a given region. For the avoidance of doubt, this does not preclude the use of supporting sites such as wikis. Public Portals should be limited in number to a reasonable amount. Additional Project Websites or Regional Websites will only be allowed if authorized in writing by Creative Commons.

:(b) Costs. Affiliate will be responsible for all costs and expenses associated with administering all Internet Services.

:(c) Delegation. Affiliate may grant administrative access for the Internet Services to a reasonable number of people for the purpose of maintaining the Internet Services in accordance with this Policy and the MOU. Affiliate will use its best judgment in deciding who will be allowed administrative access to the Internet Services. Affiliate will at all times remain ultimately responsible for ensuring that all Internet Services comply with this Policy, the MOU, and other CC Policies. Affiliate will terminate access granted to others if instructed to do so by Creative Commons. For the avoidance of doubt, CC will only instruct Affiliate to terminate another’s administrative access privileges if CC decides, in its sole discretion, that the access privilege is not being used in accordance with this Policy and the MOU.

:(d) Conduct. Affiliate, the Affiliate Team (as defined in the MOU) and others authorized as administrators of a Project Website or Regional Website in accordance with this Policy will work together with the relevant jurisdiction community, the CC Affiliate Network (as defined in the MOU), and Creative Commons, adhering to a high standard of civility, fairness, ethics and general conduct with each other. Affiliate and the Affiliate Team will engage in consensus-based decision-making on matters relating to administration of the Internet Services, using reasonable efforts to maintain, improve and operate the Internet Services for the purposes contemplated in furtherance of CC’s mission. Everyone with administrative access to an Internet Service registered to Creative Commons or hosted on CC’s servers agrees to comply with the Creative Commons Terms of Use available at http://creativecommons.org/terms.

:(e) Transfer of Internet Services. If Affiliate discontinues its official relationship with Creative Commons, habitually fails to adhere to this Policy, or if CC reasonably determines that a transfer is in the best interests of the maintenance and control of the domain name and the Marks, Affiliate agrees that CC may direct Affiliate to transfer to Creative Commons or a third party (and Affiliate will cooperate with CC in doing so):

::(i) Any domain name registered to someone other than CC;

::(ii) The entire Website, intact (to the extent not otherwise prohibited by third-party license terms); and

::(iii) Administrative access to any Public Portal, including changing all login ids and passwords as directed by Creative Commons.

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

Internet Services

2013-08-17T19:45:20Z

Jaxaza: /* Creative Commons Internet Services Policy */

[[MOU and Policies Summary| Return to Summary page]]

To share your feedback on the Internet Services Policy, please go to the [http://wiki.creativecommons.org/index.php?title=Talk:Internet_Services&action=edit&redlink=1| Internet Services Policy discussion page] and type your comments there.

[[Media:isp.pdf | PDF Version]]

--Please do not edit any text below this line.--
----

== Creative Commons Internet Services Policy ==
'''Plain English Summary'''
The overarching purpose of this Internet Service Policy is to ensure that information provided via the Internet about Creative Commons by our Affiliates is consistent and in the best interests of all those dedicated to CC around the world.
* This Internet Services Policy outlines the requirements to which Creative Commons and CC Affiliates must adhere when operating a website, email account, Facebook page, Twitter account or other internet service for a Creative Commons jurisdiction project.
* Affiliates are ultimately responsible for all content on any internet service.
* Any use of internet services must comply with CC’s policies and memorandums of understanding.
* Licenses, license choosers, translated documents and legal tools should never be hosted anywhere other than the main Creative Commons website at http:creativecommons.org.

- - - - -

The Internet Services Policy (“Policy”) complements the Trademark Policy, Merchandising Policy and other policies available at http://creativecommons.org/policies, (collectively “CC Policies”) and the agreements signed by Creative Commons Corporation (“CC” or “Creative Commons”) and its Affiliate(s) (“Affiliate”), which may include a Memorandum of Understanding, Legal Lead Affiliate Agreement, Project Lead Affiliate Agreement or previous incarnations of such agreements (for purposes of this Policy, collectively “MOUs” and each an “MOU”).

'''PURPOSE'''

Creative Commons appreciates the time, energy and hard work that all Affiliates contribute to CC projects around the globe. In order to maximize the impact of those efforts, CC and Affiliates need to work together to ensure a uniform Creative Commons message and protect our most valuable assets, which include our collective goodwill and reputation. We all strive to reach the public and connect with our communities in many ways. The purpose of this Policy is to ensure that information provided via the internet to the public about Creative Commons by Creative Commons Headquarters our Affiliates is accurate and in the best interests of all those dedicated to CC around the world.

This Policy governs the creation, and use of, domain names, email addresses, websites and other internet-based contact points, including but not limited to Twitter accounts and Facebook pages, (collectively, “Internet Services”) used in connection with the Project (as described in the MOU). This includes but is not limited to Internet Services displaying or incorporating any of the Creative Commons Marks (as defined in the Creative Commons Trademark Policy [link]). Websites (as that term is used in this Policy) include both websites for the Project within Affiliate’s jurisdiction (“Project Website”) and websites for more than one jurisdiction, such as websites for a specific geographical or geopolitical region (“Regional Websites”).

'''TERMS OF POLICY'''

Creative Commons will consider deviations from this Policy on a case by case basis through conversations with Affiliate. As confirmed by the signing of the MOU, Creative Commons and Affiliate agree:

;I. Domain Names. If Affiliate chooses to operate a Project Website or Regional Website, the Website must operate at a domain name chosen in accordance with the following:

:(a) CC Sub-Domains. CC will make available to each jurisdiction, at Affiliate’s request, a sub-domain of the Creative Commons main website at http://creativecommons.org (“CC HQ Website”) for Affiliate to use in conjunction with the Project. The sub-domain will consist of xx.creativecommons.org, where xx is the ccTLD top level domain extension for the Project’s jurisdiction.

:(b) Subdomain Administration. If Affiliate requests that CC establish a sub-domain, CC will grant Affiliate administrator access privileges to the sub-domain for so long as Affiliate is in compliance with this Policy and officially connected with the Project through an MOU.

:(c) Acquiring a Domain Name. Affiliate acknowledges that CC’s general policy is not to pay to acquire domain names that incorporate the Marks for example a domain name creativecommons.org.xx or creativecommons.xx. Where CC has not acquired a domain name that incorporates the Marks in the Project’s jurisdiction, Affiliate may choose to acquire such a domain name at its own cost, provided that:

::(i) Affiliate notifies CC in advance (if possible) that it intends to acquire the domain name, and whether the domain name will be acquired according to the procedure described in clause I (e) or I (f); and,

::(ii) Within a reasonable time of acquisition of the domain name, Affiliate emails domains@creativecommons.org with the details of the domain name and the registration data.

:(d) Registering in CC’s Name. If Affiliate chooses to acquire a domain name that incorporates the Marks and the registration authority’s rules permit the domain name to be registered in CC’s name, Affiliate must register it in CC’s name. Up-to-date registration information can be obtained by emailing domains@creativecommons.org.

:(e) Registering in Affiliate’s Name. If Affiliate chooses to acquire a domain name that incorporates any of the Marks and the registration authority’s rules do not permit the domain name to be registered in CC’s name, then Affiliate may register the domain name in its own name provided that:

::(i) Affiliate agrees that it holds the domain name for and on behalf of CC in accordance with the Trademark Policy;

::(ii) Affiliate ensures that the administrative contact on the account will at all times be domains@creativecommons.org.;

::(iii) If the rules governing the registration of domain names in the Project’s jurisdiction change such that CC can hold the domain name in CC’s own name, Affiliate will notify Creative Commons within a reasonable time of becoming aware of this change and CC and Affiliate will decide together whether and when the domain name should be transferred to Creative Commons;

::(iv) If CC and Affiliate agree to transfer the domain name to Creative Commons, Affiliate will do all things reasonably requested by CC to effect the transfer to CC, at CC’s expense; and

::(v) Affiliate will only transfer the domain name to a third party with the prior written consent of CC.

:(f) Competing Domain Names. Affiliate should notify Creative Commons as soon as is reasonably practicable if Affiliate becomes aware of any domain name registrations in the Project jurisdiction that use any Marks or are similar to any Marks.

:(g) Unforeseen Circumstances. Affiliate and CC acknowledge that this policy cannot cover every situation and new circumstances may arise. Affiliate undertakes to do all things CC reasonably requests.

;II. Website(s) and Public Portal(s). If Affiliate chooses to operate a Project Website, Regional Website or other Internet Service that provides information about Creative Commons, such as a Facebook page or Twitter account (each a “Public Portal” for purposes of this Policy) in their Affiliate capacity for the purpose of undertaking activities in connection with the Project, then the following apply:

:(a) Purpose of Project Website. The Project Website (if any) is to serve as the principal public information portal about the Project, which should include educational, research and promotional programs that encourage and enable the sharing of work within the Project jurisdiction through the use of the six Creative Commons licenses: Attribution (BY), NoDerivs (BY-ND), NonCommercial (BY-NC), ShareAlike (BY-SA), NonCommercial NoDervis (BY-NC-ND), and NonCommercial ShareAlike (BY-NC-SA), (collectively “Licenses”); and other legal instruments, such as the CC0 waiver, patent licenses, patent non-assert tools, and other previous and forthcoming licenses and tools published by CC (collectively “Legal Tools”).

:(b) Purpose of Regional Website. Regional Websites are to serve as a collaboration point between jurisdictions in the region, and provide information about Creative Commons activities in the region as a whole.

:(c) Purpose of Public Portal(s). Each Public Portal (if any) is to serve as a secondary or supplemental portal to the Project Website or Regional Website for undertaking activities in connection with the Project or Region and/or providing information about Creative Commons. If there is no existing Project Website or Regional Website, the Public Portal will serve as the principal public information portal and will provide information as stated above in II (a).

:(d) Relationship of Public Portals with Website. All Public Portals must provide a link to the main Project Website or Regional Website when it exists, and to the CC HQ Website if no Project Website or Regional Website exists.

:(e) Quality. Affiliate will ensure the Website is of a high quality and value consistent with the CC HQ Website and other Creative Commons project websites, but should not be so confusingly similar that it misleads Website visitors into thinking that the Website is the CC HQ Website. CC agrees to provide reasonable assistance to ensure such quality. To this end, CC can facilitate hosting services for the Website with a third-party hosting platform.

:(f) Branding. The Project Website will be branded as “Creative Commons [Jurisdiction]”. Regional Websites will be branded as “Creative Commons [Region]”. The Website will clearly state that it is a collaboration between Creative Commons and Affiliate(s) and will include a list of all Affiliates with links to Affiliates’ websites. Affiliate may decide where on the Website to place this information.

:(g) Disclaimers. The Website will include at a minimum two disclaimers within the footer. Public Portals will also include the disclaimers, provided that if such disclaimers do not fit within the space constraints of the portal’s service then Affiliate will provide a reasonably accurate condensation of such disclaimers if possible. The disclaimers should be as follows:

::(i) The following agency disclaimer, in the primary language of the Website: “[Affiliate] and Creative Commons Corporation are independent and separate entities. Neither is a partner, agent or employee of the other. Neither party shall have the authority to make any statements, representations or commitments of any kind, or to take any action which shall be binding on the other party, except as may be authorized in writing.”; and

::(ii) A legal disclaimer in the primary language of the Website that clearly states that the Website does not provide legal advice and that using the website does not form any type of legal relationship between Affiliate and users. Public Portals will also include the disclaimers, provided that if such disclaimers do not fit within the space constraints of the portal’s service then Affiliate will provide a reasonably accurate condensation of such disclaimers if possible.

:(h) Policies. The Website will include a statement to the effect that “Except where otherwise noted [link to policies page], this site is licensed under a Creative Commons Attribution license.” In keeping with the legal disclaimer and policies page, Affiliate will ensure that nothing provided on the Website constitutes legal advice. Each Website will provide certain policies, as outlined in (i) or (ii) below, as applicable. The Website may not require users to adhere to any new or additional policies without CC’s written consent. Applicable policies are as follows:

::(i) For Websites hosted on CC servers or for which the domain is registered in CC’s name, the CC Policies will apply, and the Websites will include a link on each page to the Creative Commons policies page at http://creativecommons.org/policies and CC Terms of Use available at http://creativecommons.org/terms; and

::(ii) For Websites not hosted on CC servers and for which the domain is registered to someone other than CC, Affiliate will establish and maintain an appropriate privacy policy, terms of use and other policies that comply with applicable law and do not contradict anything in this Policy.

:(i) Content. Affiliate will ensure the Project Website and Public Portals contain proper content in the appropriate language(s) as chosen by Affiliate and/or English, and in line with the MOU and all applicable CC Policies. Proper content may include, but is not limited to, information about (i) Affiliate(s); (ii) the relevant jurisdiction, in a manner that promotes and encourages the adoption of Creative Commons Licenses and Legal Tools; (iii) a link to or translation of the content explaining Creative Commons’ philosophy, history and mission, available at http://creativecommons.org/about/history/; (iv) the local and international adoption of Creative Commons licenses, and (v) Creative Commons-related events.

:(j) Content Restrictions. Websites and Public Portals will only contain content that promotes the objectives of the collaboration between Affiliate and Creative Commons as described in the MOU. For the avoidance of doubt, this means Websites and Public Portals will not contain, link to or endorse any content that is defamatory, hateful or otherwise discriminatory, offensive or obscene, infringing, illegal or otherwise contrary to the law of the applicable jurisdiction. [http://mcafeepromocodes.com McAfee Promo Code] - [http://www.sepatuonline.org/ Jual Sepatu Online] - [http://www.jualjaketkulit.org/ Jual Jaket Kulit]

:(k) Third-Party Contributions. Where Websites or a Public Portal allow third parties to contribute material, Affiliate will adopt a system of review that enables it to monitor this material for compliance with this Policy, the other CC Policies and the MOU, and will promptly remove material that does not comply.

:(l) Removal of Content. CC reserves the right to request the removal of any content that fails (in CC’s sole discretion) to conform to the requirements of this Policy, the MOU, or any other applicable CC Policies. Affiliate will respond promptly to such a request.

:(m) Infringing Material. If Affiliate receives a notice or becomes aware of any claim or information that a Website or a Public Portal contains content that violates the intellectual property rights of any person, and:

::(i) The content is on a Website that is hosted on a Creative Commons server or registered to Creative Commons, Affiliate agrees to send any such notice or claim immediately to dmca@creativecommons.org, with relevant information.

::(ii) The content is on a Website that is not hosted on a Creative Commons server and is registered to someone other than Creative Commons, Affiliate agrees to comply with all applicable laws governing its obligations and responsibilities with respect to such material.

::(iii) The content is on a Public Portal, Affiliate agrees to use reasonable efforts to remove the content. [http://hostgator1centcoupon.net Hostgator 1 cent]

:(n) Website License. Affiliate will ensure that to the greatest extent possible, all content on a Website or Public Portals is licensed under a Creative Commons Attribution license. Affiliate alone is responsible for ensuring that it has obtained all rights necessary to the content included on a Website and will use best efforts to enable it to be licensed under the CC Attribution license. All third-party content that appears on a Website that is not licensed under the CC BY license must be clearly marked with its copyright status and/or applicable license.

:(o) Content Syndication. Any content that appears on a Website or Public Portal may be syndicated on the websites of other CC project jurisdictions, Regional Websites and the CC HQ Website, unless expressly indicated otherwise by Affiliate in writing to CC or another Affiliate, as the case may be. Similarly, any and content on the CC HQ Website may be used on the Project Website or Regional Website, unless CC expressly indicates to the contrary.

:(p) Items that cannot be hosted. The following items will be hosted on the CC HQ Website only: License drafts, final Licenses, legal code, license deeds, License HTML, license buttons, Legal Tools (whether in human-readable, lawyer-readable or machine-readable formats, or any other formats whatsoever) and the license chooser engine. For the avoidance of doubt, this means that these items may not be hosted on a Project Website or Regional Website, but the Project Website or Regional Website may link to the items on the CC HQ Website.

:(q) Document Translation. If Affiliate or the Affiliate Team wish to translate documents from CC’s wiki (http://wiki.creativecommons.org), those documents must remain posted (as translated) on the wiki. Websites and Public Portals may link to the documents.

:(r) FAQs. The Project Website will include a link to CC’s “Frequently Asked Questions” page available at http://wiki.creativecommons.org/Frequently_Asked_Questions. The Project Website may also include a “Frequently Asked Questions” page with human readable information about CC topics, licensing and related legal issues customized to the Project’s jurisdiction [http://kcouponcode.com Kaspersky Coupon Code] and in the jurisdiction’s primary language(s). Regional Websites may include a link to the “Frequently Asked Questions” page.

:(s) Developers. Websites may contain a link to CC’s developers pages available at http://wiki.creativecommons.org/Developers.

:(t) Commercial Activity. Websites will not contain third party advertisements, banner ads or promotions by Affiliate for any products or services other than those permitted under the Merchandising Policy or anticipated by the scope of the Project as described by the MOU. Creative Commons Counsel and Affiliate can discuss other fund-raising or commercial activity to be conducted on Websites or through Project Portals.

:(u) Third-Party Hosting. To the extent that CC facilitates hosting services for a Website and a third party hosting platform, CC is not in any way responsible for the provision of the hosting services and Affiliate will contract separately with the third party hosting platform for the provision of these services.

;III. Email Addresses and Lists. If Affiliate wishes to create email addresses or email lists for the Project, each email address or list must be operated in accordance with the following:

:(a) Email Addresses. Email addresses may correspond to the domain name for the Project, provided that:

::(i) The email addresses are used only to send communications in accordance with the MOU and CC Polices;

::(ii) All emails sent from the email addresses include a footer that makes clear to the recipient that the sender does not work for Creative Commons (e.g. [sender’s name], CC [jurisdiction] [Title]) and that clearly states that CC, Affiliate and the contents of the email do not provide legal advice; and,

::(iii) Affiliate agrees to provide email addresses only to persons who are working with Affiliate on the Project in accordance with the MOU, and to terminate a person’s email account when that person is no longer working with Affiliate on the Project.

:(b) Set-Up of Lists. If Affiliate would like have a mailing list for the jurisdiction, it must be done on Ibiblio (unless otherwise approved by CC) and Affiliate must send the administrators names, administrative password and any updates or changes to administrators or administrative passwords to CC when the list is set-up. To create a new mailing list, send an email to help@ibiblio.org with desired list name and the name of a chosen administrator.

:(c) List Membership. Affiliate will not arbitrarily exclude anyone from membership in the list, and Affiliate will use its discretion when deciding to terminate a person’s membership and then only for appropriate reasons, such as disruptiveness or inappropriate comments.

:(d) Moderating Lists. Affiliate will moderate any email lists for the Project fairly and will moderate discussions when necessary to ensure that all list members are allowed to participate fully.

;IV. All Internet Services. The following provisions are applicable to all Internet Services maintained or operated by Affiliate in relation to the Project:

:(a) Number of Internet Services. There may only be one central Project Website for each Jurisdiction and one Regional Website for a given region. For the avoidance of doubt, this does not preclude the use of supporting sites such as wikis. Public Portals should be limited in number to a reasonable amount. Additional Project Websites or Regional Websites will only be allowed if authorized in writing by Creative Commons.

:(b) Costs. Affiliate will be responsible for all costs and expenses associated with administering all Internet Services.

:(c) Delegation. Affiliate may grant administrative access for the Internet Services to a reasonable number of people for the purpose of maintaining the Internet Services in accordance with this Policy and the MOU. Affiliate will use its best judgment in deciding who will be allowed administrative access to the Internet Services. Affiliate will at all times remain ultimately responsible for ensuring that all Internet Services comply with this Policy, the MOU, and other CC Policies. Affiliate will terminate access granted to others if instructed to do so by Creative Commons. For the avoidance of doubt, CC will only instruct Affiliate to terminate another’s administrative access privileges if CC decides, in its sole discretion, that the access privilege is not being used in accordance with this Policy and the MOU.

:(d) Conduct. Affiliate, the Affiliate Team (as defined in the MOU) and others authorized as administrators of a Project Website or Regional Website in accordance with this Policy will work together with the relevant jurisdiction community, the CC Affiliate Network (as defined in the MOU), and Creative Commons, adhering to a high standard of civility, fairness, ethics and general conduct with each other. Affiliate and the Affiliate Team will engage in consensus-based decision-making on matters relating to administration of the Internet Services, using reasonable efforts to maintain, improve and operate the Internet Services for the purposes contemplated in furtherance of CC’s mission. Everyone with administrative access to an Internet Service registered to Creative Commons or hosted on CC’s servers agrees to comply with the Creative Commons Terms of Use available at http://creativecommons.org/terms.

:(e) Transfer of Internet Services. If Affiliate discontinues its official relationship with Creative Commons, habitually fails to adhere to this Policy, or if CC reasonably determines that a transfer is in the best interests of the maintenance and control of the domain name and the Marks, Affiliate agrees that CC may direct Affiliate to transfer to Creative Commons or a third party (and Affiliate will cooperate with CC in doing so):

::(i) Any domain name registered to someone other than CC;

::(ii) The entire Website, intact (to the extent not otherwise prohibited by third-party license terms); and

::(iii) Administrative access to any Public Portal, including changing all login ids and passwords as directed by Creative Commons.

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

Kenya

2013-08-17T18:46:50Z

Jaxaza:

{{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.

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://blogs.unpad.ac.id/dominodiaz/ Blog Teknik]
* [http://andreweweww.wordpress.com/ Curhat Blog]
* [http://www.sepatuonline.org/ Jual Sepatu Online]
* [http://modifikasiku.info/ Modif Motor Terbaru]
* [http://kesehatan-ku.info/ Kesehatan 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]
-[http://www.jualjaketkulit.org/ Jual Jaket Kulit]

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 [http://www.proweb365.com web] communities?

• Use of social media to establish a linked CC Kenya affiliate
• Implementation of a Creative Commons [http://webdesignvalley.com web]site
• 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 [http://goarticles.com/author/Justin-Version/414314/ 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, [https://lookboard.com Lookboard] 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.