Creative Commons - User contributions [en]

Developers

2026-02-02T06:31:58Z

CCID-timidrobot:

== Join the CC Open Source Community ==

'''Please see our [https://opensource.creativecommons.org/ Creative Commons Open Source] website.'''

It includes information on how to join our community on [https://opensource.creativecommons.org/community/#zulip Zulip] and the [https://opensource.creativecommons.org/blog/entries/ CC Open Source Blog]

<br clear="all"/>

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

[[Category:Developer]]

__NOTOC__

Developers

2025-10-08T06:57:35Z

CCID-timidrobot:

Developers

2025-10-08T06:56:31Z

CCID-timidrobot: Better reference the CC Open Source website and remove content that duplicates it

'''Join the CC Open Source Community'''

Please see our [https://opensource.creativecommons.org/ Creative Commons Open Source] website. It includes information on how to join our community on [https://opensource.creativecommons.org/community/#zulip Zulip] and the [https://opensource.creativecommons.org/blog/entries/ CC Open Source Blog]

<br clear="all"/>

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

[[Category:Developer]]

__NOTOC__

Legal Code Translation Policy

2025-09-15T11:36:17Z

CCID-timidrobot: define "CC" acronym

Creative Commons (CC) has established the following Official Legal Code Translation Process and Policy (“Legal Code Translation Policy”) to facilitate adoption and understanding of our licenses as tools for sharing creative works and data. This Legal Code Translation Policy was established as of 2013 October 29 and is updated and revised by Creative Commons in its discretion. Any non-trivial revisions will be logged and dated at the bottom of this page.

'''Watch this explanatory video:'''

[[File:How-to-translate-licenses.png |link=https://www.youtube.com/watch?v=yhHPORrnMns]]

==Overview==
The legal code for the international Creative Commons licenses and for CC0 is designed for use worldwide, without any need for adaptation to local laws. For these tools to reach their fullest potential, CC encourages linguistic translations of the legal codes and deeds into as many languages as possible. This page describes the policy and process for developing official translations of Creative Commons legal code.

The process for developing new translations (each is called a “translation project”) is coordinated and overseen by CC’s legal team in collaboration with the global network team. Creative Commons reserves the exclusive right to approve and host official translations of its legal tools, as well as to modify this process and adjust translation projects at any time. Per our policy, each official translation is hosted at a specified uniform resource indicator on CC’s website. The English original and the official translations will all be treated as equivalents. Translations of CC licenses that are not made in accordance with this policy are unauthorized modifications of our licenses per the [[Modifying_the_CC_licenses#License_Modification_Policy|License Modification Policy]].

==Translation process==
===Step 1. Beginning new translation projects.===
Anyone may initiate a translation project with CC. To express interest, please email legal [at] creativecommons [dot] org identifying the language you would like to coordinate.

Note that CC’s policy is to publish a single, official translation for any given language unless an important reason exists to allow more than one. This mirrors CC’s policy for translations of deeds. Anyone wanting to coordinate translation projects is expected to accommodate and encourage participation of others in the CC community, including from other jurisdictions where the language is spoken. CC will help coordinate this collaboration.

Once a new translation project is begun, CC will update its [[Legal_Tools_Translation|public tracking chart]] and create and populate a language-specific translation page for public tracking, which will be continually updated by CC throughout the translation process.

===Step 2. Preparing the translation draft.===
Please refer to the [[Legal_tools_translation_guide|legal tools translation guide]] while creating your translation because it contains information about common issues that arise when translating the text of the licenses and CC0. When translating the 4.0 license suite, please begin with BY-NC-SA using the worksheet [[Legal_Code_Translation_Policy#Supporting_documents|here]]. Typically, teams begin only with BY-NC-SA and defer creating the other five licenses until after the public comment period. If you are translating CC0, use this [[Legal_Code_Translation_Policy#Supporting_documents|worksheet]].

Once the draft is complete, the translation team should send it to legal[at]creativecommons[dot]org, along with a writeup of the following:
*Explanation of word choice for the following terms:
**For version 4.0:
***Adapted Material
***Copyright and Similar Rights
***Downstream recipients
***Licensed Material
***Share
***ShareAlike
**For CC0:
***Copyright and Related Rights
***Affirmer
***Work
***License
***Waiver
*Description of which concepts were challenging to translate and how decisions were made
*Explanation of variations compared to terminology used on deed translation
*Explanation of variations compared to terminology used in ports of same language
*Names of translators

CC Legal will use this explanation during their Step 3 review, and will add it to language wiki page as part of public documentation of translation process.

===Step 3. Review of draft.===
CC Legal will conduct a review of the draft translation using the following checklist:
#Use Google Translate to read through from top to bottom, looking for glaring errors like commercial uses allowed in NC license, for example.
#Use Google Translate to ensure there are no references to specific local legislation.
#Check that numbering and ordering of sections matches the English.
#Check that cross-references within text are correct.
#Make sure each defined term is in the same order as the English, and uses same capitalization throughout document.
#Go through relevant issues list, checking draft on each point using Google Translate and asking questions of team as needed: 4.0 issues list [[Legal_tools_translation_guide#4.0_license_suite_issues|here]], CC0 issues list [[Legal_tools_translation_guide#CC0_issues|here]]
#Check draft license translation against translations of deed to see if any notable changes in terminology. If yes, ask team for more information.

CC Legal will correspond with the translation team to clarify questions and make changes until a final draft translation is completed. Note that this step will reveal whether there are updates needed for the deed translations. The translation team is responsible for ensuring that the deed is fully translated. For help translating the deeds, see the instructions [[Translating_CC_Deeds|here]].

===Step 4. Public comment period.===
The public comment period is designed to ensure the highest quality linguistic translations possible. The translation team posts the draft on the CC wiki and in appropriate channels for public comment and feedback for a reasonable period of time (typically about 30-45 days, but may be shortened or extended if circumstances warrant). We encourage teams to seek as much input as possible, including by reaching out directly to local experts where possible.

At the conclusion of the public comment period, the translation team sends CC Legal a written summary of input received and how issues were resolved, along with the revised translation. CC Legal reviews the public comment summary from the translation team and asks questions as needed.

===Step 5. Creating the rest of the license suite.===
Note that this step only applies to translation of the version 4.0 CC license suite. Once all open issues are resolved with CC Legal after public comment, the translation team should create the other 5 licenses in the suite. For help in this process, refer to this [https://wiki.creativecommons.org/images/d/d1/Building_the_4.0_Suite.pdf guide]. Please consult CC Legal if you have any questions about word choices or anything else when creating the rest of the suite.

===Step 6. Readying files for staging server.===
At this point, the team converts the file(s) to HTML and sends the HTML file(s) to legal [at] creativecommons [dot] org. CC puts the file(s) on the staging server and sends the link(s) to the translation team.

''NOTE: To create the HTML files, we recommend using the English legal code pages - [https://creativecommons.org/licenses/by/4.0/legalcode https://creativecommons.org/licenses/by/4.0/legalcode] et. al. - as templates for your own. You can access the HTML page for each license in Github, where the files are stored with comments.

*BY-NC-SA is [https://github.com/creativecommons/creativecommons.org/blob/master/docroot/legalcode/by-nc-sa_4.0.html here]
*BY is [https://github.com/creativecommons/creativecommons.org/blob/master/docroot/legalcode/by_4.0.html here]
*BY-SA is [https://github.com/creativecommons/creativecommons.org/blob/master/docroot/legalcode/by-sa_4.0.html here]
*BY-NC-ND is [https://github.com/creativecommons/creativecommons.org/blob/master/docroot/legalcode/by-nc-nd_4.0.html here]
*BY-NC is [https://github.com/creativecommons/creativecommons.org/blob/master/docroot/legalcode/by-nc_4.0.html here]
*BY-ND is [https://github.com/creativecommons/creativecommons.org/blob/master/docroot/legalcode/by-nd_4.0.html here]
*CC0 is [https://github.com/creativecommons/creativecommons.org/blob/master/docroot/legalcode/zero_1.0.html here]

Copy and paste the appropriate license text into a file using a text editor or HTML editor. Then, copy and paste your appropriate translation text over the English text, being careful not to copy over the existing HTML tags, and re-check the code to ensure that there are no mistakes. Please ensure that all the XHTML files are saved using UTF-8 encoding, which generally will be the default. Then save each file separately according to the following convention:''
*''CC0'':
** ''zero_1.0_[language code].html''

''(For example, "zero_1.0_fr.html" would be the naming for the French translation.)''

*''4.0''
**''by_4.0_[language code].html''
**''by-sa_4.0_[language code].html''
**'' [...]''

===Step 7. Final review.===

The translation team and CC Legal conduct a final review of all files on the staging server. This review should involve a check of both the substance and formatting of the files.

During this final review, CC Legal will use the following checklist:
#Use Google Translate to read through from top to bottom, looking for glaring errors like commercial uses allowed in NC license, for example. [Note: in the case of 4.0, this may be the first time the translations of licenses other than BY-NC-SA have been reviewed, so pay special attention to the changes made to those files.]
#Pay special attention to the license titles - are they correct and consistent throughout each file? Compare to titles on license deeds.
#Check that formatting appears correct as compared to English (same number of provisions, identical section numbering, bold font)
#Check that language list contains all published translations, including English
#Check all links in the files
#Check that deeds are fully translated
#For version 4.0, cut and paste each file into a Word doc and run the following comparisons:
#*BY-NC-SA to BY; compare to [https://wiki.creativecommons.org/images/c/c4/Making_BY_%28comparison%29.pdf this]
#*BY-NC-SA to BY-SA; compare to [https://wiki.creativecommons.org/images/6/64/Making_BY-SA_%28comparison%29.pdf this]
#*BY-NC-SA to BY-NC; compare to [https://wiki.creativecommons.org/images/6/6f/Making_BY-NC_%28comparison%29.pdf this]
#*BY-NC-SA to BY-ND; compare to [https://wiki.creativecommons.org/images/a/a2/Making_BY-ND_%28comparison%29.pdf this]
#*BY-NC-SA to BY-NC-ND; compare to [https://wiki.creativecommons.org/images/7/70/Making_BY-NC-ND_%28comparison%29.pdf this]

This stage continues until all identified problems are resolved.

===Step 8. General Counsel sign-off.===
Once the translation team and CC have signed off on all files, CC Legal sends the file(s) to General Counsel for final sign-off. CC Legal will coordinate details for blog post announcement with translation team at this point.

===Step 9. Publication.===
CC will alert the translation team and publish announcement on the CC blog and social media. CC Legal will update wiki tracking sheet with publication dates. Translation team should update Transifex so that deeds link to published translation rather than English legal code.

==Key Resources==
* [[Legal tools translation guide]]
* [[Media:Building_the_4.0_Suite.pdf|Building the 4.0 Suite (.pdf)]]
* [[Media:Making_BY_(comparison).pdf|Making the BY license (comparison) (.pdf)]]
* [[Media:Making_BY-SA_(comparison).pdf|Making the BY-SA license (comparison) (.pdf)]]
* [[Media:Making_BY-NC_(comparison).pdf|Making the BY-NC license (comparison) (.pdf)]]
* [[Media:Making_BY-ND_(comparison).pdf|Making the BY-ND license (comparison) (.pdf)]]
* [[Media:Making_BY-NC-ND_(comparison).pdf|Making the BY-NC-ND license (comparison) (.pdf)]]
* 4.0 translation worksheet: [https://docs.google.com/document/d/1Vq6b89z6HWP1KZ66FNvx9E1GTeyAguPKk_zb4jXg4u8/ Google Doc], [[Media:4.0_translation_worksheet_(BY-NC-SA)(Feb_2015).odt|.odt]], [[Media:4.0_translation_worksheet_(BY-NC-SA)(Feb_2015).docx|.docx]], [[Media:4.0_translation_worksheet_(BY-NC-SA)(Feb_2015).pdf|.pdf]] (updated 2016 November 23)
* CC0 translation worksheet: [https://docs.google.com/document/d/12bmP4guaewK2U0eGQIFd-2N5XVlpB1rGULfxHthhODA/ Google Doc], [[Media:CC0_translation_worksheet.odt|.odt]], [[Media:CC0_translation_worksheet.docx|.docx]], [[Media:CC0_translation_worksheet.pdf|.pdf]] (updated 2016 November 23)

==Changelog==
* 2019 September 17: Moved formatting check to Step 7 since that is when bold and other formatting is added; changed instructions for converting to HTML
* 2019 September 3: Revised process to better reflect current practice in terms of who and how translations are initiated, and added far more detail about different steps in the process.
* 2018 May 26: As of January 2018, the Affiliate Network transitioned to a Global Network, where everyone - individuals and institutions - are welcome. This policy reflects the new structure.
* 2017 March 14: Moved "Creating the files" from [[Legal tools translation guide]] to this page
* 2016 November 21: Removed the obligation to send the translation proposal using the forms
* 2016 November 4: Added detailed new steps to the translation process
* 2015 April 17: Clarification that unofficial translations violate License Modification Policy
* 2015 February 4: Change in supplemental material requirements, added CC0 translation worksheet
* 2014 February 4: Additional supplemental material requirements, new version of internal checklist posted
* 2014 January 24: More detailed summary.
* 2013 October 29: Policy established.

[[Category:Translation Project]]

Public reports

2025-09-08T12:51:29Z

CCID-timidrobot: Replace Code of Conduct link, improve no longer used formatting

The purpose of this portal is to provide transparent access to public documents concerning the financial status and governance of the Creative Commons organization.

== Governance documents ==
* [[Media:Charter_cc.pdf|Incorporation document and charter]]
* [[ Media:Final_CC_Governance_Policies_.pdf |Board Governance Policies (effective Jan 1, 2022)]]
* [[ Media:Amended_Bylaws_%28Final%29.pdf |Organization Bylaws (amended 2021 December)]]
** [[Media:Bylaws_-_Amended_and_Restated_March_4_2018_%28final%29.pdf|Organization Bylaws (amended 2018 March)]]
** [[Media:CC_Amended_and_Restated_Bylaws_%28effective_6_Dec_2015%2C_amended_5_June_2016%29-1.pdf|Organization Bylaws (amended 2016 June)]]
** [[Media:CC_Amended_and_Restated_Bylaws_%28effective_6_Dec_2015%29.pdf|Organization Bylaws (amended 2015 December)]]
** [[Media:bylaws.pdf|Organization Bylaws (pre 2015 December)]]
* [[Media:1023.pdf|Form 1023 tax-exempt non-profit application and supplements]]
* [[Media:irsexempt.pdf|IRS tax-exempt determination letter]]
* [[Media:Audit_Committee_Charter_as_amended_2017-11-18_3.pdf|Audit Committee Charter]]
* [http://wiki.creativecommons.org/License_Versions License versioning process]

== Policies for staff, board and officers, and community members ==

* [https://creativecommons.org/wp-content/uploads/2017/11/Global_Network_Membership_Charter.pdf CC Global Network Charter, including Code of Conduct for all participants]
* [https://wiki.creativecommons.org/images/b/be/Final_CC_Governance_Policies_.pdf CC Board Governance Policies]
* [https://drive.google.com/file/d/17KO9YPKh4JDb9-JoeNYogBC0kbmWeAUt/view Board Director Expectations]
* [https://creativecommons.org/code-of-conduct/ Code of Conduct - Creative Commons]
* [[Media:CC_Handbook,_April_1,_2022.pdf|All Employee Handbook, April 2022]]
* <s>[[Media:Final_US_employee_handbook.pdf|Creative Commons Employee Handbook]]</s> (no longer in use)
* <s>[[Media:CAHandbookMay2018.pdf|0941176 B.C. LTD Employee Handbook]]</s> (no longer in use)
* <s>[[Media:Codes_of_Conduct_for_Employees_%28approved_March_4%2C_2018%29%281%29.pdf|Code of Conduct (Employees) updated 2018 March]]</s> (no longer in use)
* <s>[[Media:Creative_Commons_Code_of_Conduct_for_Directors_and_Officers_%28adopted_Mar_4_2018%29.pdf|Code of Conduct (Directors) updated 2018 March]]</s> (no longer in use)

== Other policies==
* [http://creativecommons.org/terms Website terms of use]
* [http://creativecommons.org/policies Copyright and trademark policies]
* [http://creativecommons.org/privacy Privacy policy]
* [http://wiki.creativecommons.org/Lobbying Lobbying policy]
* [http://wiki.creativecommons.org/Internet_Services Affiliate Internet Services Policy]
* [http://wiki.creativecommons.org/Merchandising Merchandising Policy]
* [http://wiki.creativecommons.org/Policy_Advocacy_Guidelines Policy & Advocacy Guidelines]
* [https://creativecommons.github.io/community/code-of-conduct/enforcement/ Enforcement policy for our Slack and open source codes of conduct]
* [https://creativecommons.org/about/get-involved/donor-screening-guidelines/ Creative Commons Guidelines for Screening Donors]

== Annual reports ==

''' Organizational strategy document '''
* [http://wiki.creativecommons.org/images/c/ce/Future-of-creative-commons.pdf The Future of Creative Commons], June 2013

''' Organization-wide report '''
* '''(Also see [https://creativecommons.org/annual-reports/ Annual Reports - Creative Commons])'''
* [https://creativecommons.org/wp-content/uploads/2024/04/2023-Creative-Commons-Annual-Report-2-1.pdf 2023 Annual Report (7mb PDF)]
* [https://creativecommons.org/state-of-the-commons-2022/ State of the Commons 2022 - Creative Commons]
* [https://creativecommons.org/2022/04/05/2021-annual-report/ Creative Commons 2021 State of the Commons Annual Report - Creative Commons]
* [https://wiki.creativecommons.org/images/2/2e/CC_State_of_the_Commons_2020.pdf State of the Common | 2020 (2.5mb PDF)]
* [https://wiki.creativecommons.org/images/2/20/CC_AnnualReport_2019.pdf State of the Common | 2019 (4.1mb PDF)]
* [https://stateof.creativecommons.org/ State of the Commons, 2017]
* [https://stateof.creativecommons.org/2016 State of the Commons, 2016]
* [https://stateof.creativecommons.org/2015 State of the Commons, 2015]
* [http://teamopen.cc/thefuture/ 2013-2014]
* [http://dispatches.creativecommons.org/ 2011-2012]

''' Affiliate Network reports '''
* [http://wiki.creativecommons.org/Affiliate_Reporting/2010 2010]

== Funding sources ==
* Donor List: [https://creativecommons.org/supporters/ Supporters - Creative Commons]
* Public announcements of major grants:
** [http://creativecommons.org/weblog/entry/27097 Gates Foundation Department of Labor grantee assistance]
** [http://creativecommons.org/press-releases/entry/8175 Hewlett Foundation general operating and ccLearn]
** [http://creativecommons.org/press-releases/entry/7945 5 x 5 Funding Challenge]
** [http://creativecommons.org/press-releases/entry/8322 Omidyar Network]
** [http://creativecommons.org/press-releases/entry/26078 Nature Publishing Group]
** [http://creativecommons.org/press-releases/entry/7183 Technology company contributions]

== Other ==
* [[Media:Amended_DMCA_form.pdf|DMCA Designation of Agent to Receive Notification of Claimed Infringement]]

== Tax returns and audit information ==
''' 2023 '''
* [[Media: 2023_Creative_Commons_Corporation_Pub_Disc_Client_Copy.pdf| IRS Form 990]]
* [[Media: Creative_Commons_2023_Auditors%E2%80%99_Report_and_Consolidated_Financial_Statements.pdf| Independent audit]]
''' 2022 '''
* [[Media: 2022_Creative_Commons_Corporation_Pub_Disc_Client_Copy.pdf| IRS Form 990]]
* [[Media:Creative_Commons_2022_-_FS_Final_0807.pdf | Independent audit]]
''' 2021 '''
* [[Media: 2021_Creative_Commons_Corporation_Public_Disclosure_Client_Copy.pdf | IRS Form 990]]
* [[Media:Creative_Commons_2021_-_FS_Final_0718.pdf | Independent audit]]
''' 2020 '''
* [[Media:2020_Creative_Commons_Public_Disclosure_Client_Copy.pdf | IRS Form 990]]
* [[Media:Creative_Commons_2020_-_FS_Final_0621_(1).pdf | Independent audit]]
''' 2019 '''
* [[Media:2019_Creative_Commons_990_Public_Disclosure_Client_Copy.pdf | IRS Form 990]]
* [[Media:Creative_Commons_2019_-_FS_Final_0708.pdf |Independent audit]]
''' 2018 '''
* [[Media:2018_Creative_Commons_Pub_Disc_Client_Copy.pdf|IRS Form 990]]
* [[Media:Creative_Commons_2018_-_FS_Final_0306.pdf|Independent audit]]
''' 2017 '''
* [[Media:2017_Creative_Commons_Public_Disclosure_Client_Copy.pdf|IRS Form 990]]
* [[Media:Creative_Commons_2017_-_Final_FS_1002.pdf|Independent audit]]

''' 2016 '''
* [[Media:2016_990_Public_Filing.pdf|IRS Form 990]]
* [[Media:Creative_Commons_2016_Final_FS_11-8.pdf|Independent audit]]

''' 2015 '''
* [[Media:2015_CC.pdf|IRS Form 990]]
* [https://drive.google.com/open?id=0B2UhiNCe0qFcSmRQQUVkUlllem8 Independent audit]

''' 2014 '''
* [[Media:Creative_Commons_2014_Form_990_Public_Disclosure_Copy.pdf|IRS Form 990]]
* [https://drive.google.com/open?id=0B2UhiNCe0qFcSVNPMVdoMUxOdTA Independent audit]

''' 2013 '''
* [[Media:Creative_Commons_form990_2013.pdf|IRS Form 990]]
* [https://drive.google.com/open?id=0B2UhiNCe0qFcUFV1RVk0Rm0xQzg Independent audit]

''' 2012'''
* [[Media:990-2012B.pdf|IRS Form 990]]
* [[Media:2012_CC_Audited_Financials.pdf|Independent audit]]

''' 2011 '''
* [[Media:2011_Form_990_-_Public.pdf|IRS Form 990]]
* [[Media:2011_CC_Audited_Financials.pdf|Independent audit]]

''' 2010 '''
* [[Media:990-2010B.pdf|IRS Form 990]]
* [[Media:Audit2010.pdf|Independent audit]]

''' 2009 '''
* [[Media:990-2009.pdf|IRS Form 990]]
* [[Media:Audit2009.pdf|Independent audit]]

''' 2008 '''
* [[Media:990-2008.pdf|IRS Form 990]]
* [[Media:Audit2008.pdf|Independent audit]]

''' 2007 '''
* [[Media:990-2007.pdf|IRS Form 990]]
* [[Media:Audit2007.pdf|Independent audit]]

''' 2006 '''
* [[Media:990-2006.pdf|IRS Form 990]]
* [[Media:Audit2006.pdf|Independent audit]]

''' 2005 '''
* [[Media:990-2005.pdf|IRS Form 990]]
* [[Media:Audit2005.pdf|Independent audit]]

''' 2004 '''
* [[Media:990-2004.pdf|IRS Form 990]]
* [[Media:Audit2004.pdf|Independent audit]]

''' 2003 '''
* [[Media:990-2003.pdf|IRS Form 990]]
* [[Media:Audit2003.pdf|Independent audit]]

''' 2002 '''
* [[Media:990-2002.pdf|IRS Form 990]]
* [[Media:Audit2002.pdf|Independent audit]]

''' 2001 '''
* [[Media:990-2001.pdf|IRS Form 990]]

Slack/Code of Conduct

2025-09-08T12:47:10Z

CCID-timidrobot: Redirected page to Code of Conduct

#REDIRECT [[Code_of_Conduct]]

Code of Conduct

2025-09-08T12:44:02Z

CCID-timidrobot: link to new unified code of conduct

Creative Commons' Code of Conduct (CoC) is on the primary website: '''[https://creativecommons.org/code-of-conduct/ Code of Conduct - Creative Commons]'''.

Public reports

2025-01-07T21:00:12Z

CCID-timidrobot: Add 2023 IRS Form 990

The purpose of this portal is to provide transparent access to public documents concerning the financial status and governance of the Creative Commons organization.

== Governance documents ==
* [[Media:Charter_cc.pdf|Incorporation document and charter]]
* [[ Media:Final_CC_Governance_Policies_.pdf |Board Governance Policies (effective Jan 1, 2022)]]
* [[ Media:Amended_Bylaws_%28Final%29.pdf |Organization Bylaws (amended 2021 December)]]
** [[Media:Bylaws_-_Amended_and_Restated_March_4_2018_%28final%29.pdf|Organization Bylaws (amended 2018 March)]]
** [[Media:CC_Amended_and_Restated_Bylaws_%28effective_6_Dec_2015%2C_amended_5_June_2016%29-1.pdf|Organization Bylaws (amended 2016 June)]]
** [[Media:CC_Amended_and_Restated_Bylaws_%28effective_6_Dec_2015%29.pdf|Organization Bylaws (amended 2015 December)]]
** [[Media:bylaws.pdf|Organization Bylaws (pre 2015 December)]]
* [[Media:1023.pdf|Form 1023 tax-exempt non-profit application and supplements]]
* [[Media:irsexempt.pdf|IRS tax-exempt determination letter]]
* [[Media:Audit_Committee_Charter_as_amended_2017-11-18_3.pdf|Audit Committee Charter]]
* [http://wiki.creativecommons.org/License_Versions License versioning process]

== Policies for staff, board and officers, and community members==

* [https://creativecommons.org/wp-content/uploads/2017/11/Global_Network_Membership_Charter.pdf CC Global Network Charter, including Code of Conduct for all participants]
* [https://wiki.creativecommons.org/images/b/be/Final_CC_Governance_Policies_.pdf CC Board Governance Policies]
* [https://drive.google.com/file/d/17KO9YPKh4JDb9-JoeNYogBC0kbmWeAUt/view Board Director Expectations]
* [https://summit.creativecommons.org/summit-code-of-conduct/ Summit Code of Conduct, updated in advance of each Summit]]
* [[Media:CC_Handbook,_April_1,_2022.pdf|All Employee Handbook, April 2022]]
* [[Media:Final_US_employee_handbook.pdf|Creative Commons Employee Handbook (no longer in use)]]
* [[Media:CAHandbookMay2018.pdf|0941176 B.C. LTD Employee Handbook(no longer in use)]]
* [[Media:Codes_of_Conduct_for_Employees_%28approved_March_4%2C_2018%29%281%29.pdf|Code of Conduct (Employees) updated 2018 March (no longer in use)]]
* [[Media:Creative_Commons_Code_of_Conduct_for_Directors_and_Officers_%28adopted_Mar_4_2018%29.pdf|Code of Conduct (Directors) updated 2018 March (no longer in use)]]

== Other policies==
* [http://creativecommons.org/terms Website terms of use]
* [http://creativecommons.org/policies Copyright and trademark policies]
* [http://creativecommons.org/privacy Privacy policy]
* [http://wiki.creativecommons.org/Lobbying Lobbying policy]
* [http://wiki.creativecommons.org/Internet_Services Affiliate Internet Services Policy]
* [http://wiki.creativecommons.org/Merchandising Merchandising Policy]
* [http://wiki.creativecommons.org/Policy_Advocacy_Guidelines Policy & Advocacy Guidelines]
* [https://creativecommons.github.io/community/code-of-conduct/enforcement/ Enforcement policy for our Slack and open source codes of conduct]
* [https://creativecommons.org/about/get-involved/donor-screening-guidelines/ Creative Commons Guidelines for Screening Donors]

== Annual reports ==

''' Organizational strategy document '''
* [http://wiki.creativecommons.org/images/c/ce/Future-of-creative-commons.pdf The Future of Creative Commons], June 2013

''' Organization-wide report '''
* '''(Also see [https://creativecommons.org/annual-reports/ Annual Reports - Creative Commons])'''
* [https://creativecommons.org/wp-content/uploads/2024/04/2023-Creative-Commons-Annual-Report-2-1.pdf 2023 Annual Report (7mb PDF)]
* [https://creativecommons.org/state-of-the-commons-2022/ State of the Commons 2022 - Creative Commons]
* [https://creativecommons.org/2022/04/05/2021-annual-report/ Creative Commons 2021 State of the Commons Annual Report - Creative Commons]
* [https://wiki.creativecommons.org/images/2/2e/CC_State_of_the_Commons_2020.pdf State of the Common | 2020 (2.5mb PDF)]
* [https://wiki.creativecommons.org/images/2/20/CC_AnnualReport_2019.pdf State of the Common | 2019 (4.1mb PDF)]
* [https://stateof.creativecommons.org/ State of the Commons, 2017]
* [https://stateof.creativecommons.org/2016 State of the Commons, 2016]
* [https://stateof.creativecommons.org/2015 State of the Commons, 2015]
* [http://teamopen.cc/thefuture/ 2013-2014]
* [http://dispatches.creativecommons.org/ 2011-2012]

''' Affiliate Network reports '''
* [http://wiki.creativecommons.org/Affiliate_Reporting/2010 2010]

== Funding sources ==
* Donor List: [https://creativecommons.org/supporters/ Supporters - Creative Commons]
* Public announcements of major grants:
** [http://creativecommons.org/weblog/entry/27097 Gates Foundation Department of Labor grantee assistance]
** [http://creativecommons.org/press-releases/entry/8175 Hewlett Foundation general operating and ccLearn]
** [http://creativecommons.org/press-releases/entry/7945 5 x 5 Funding Challenge]
** [http://creativecommons.org/press-releases/entry/8322 Omidyar Network]
** [http://creativecommons.org/press-releases/entry/26078 Nature Publishing Group]
** [http://creativecommons.org/press-releases/entry/7183 Technology company contributions]

== Other ==
* [[Media:Amended_DMCA_form.pdf|DMCA Designation of Agent to Receive Notification of Claimed Infringement]]

== Tax returns and audit information ==
''' 2023 '''
* [[Media: 2023_Creative_Commons_Corporation_Pub_Disc_Client_Copy.pdf| IRS Form 990]]
''' 2022 '''
* [[Media: 2022_Creative_Commons_Corporation_Pub_Disc_Client_Copy.pdf| IRS Form 990]]
* [[Media:Creative_Commons_2022_-_FS_Final_0807.pdf | Independent audit]]
''' 2021 '''
* [[Media: 2021_Creative_Commons_Corporation_Public_Disclosure_Client_Copy.pdf | IRS Form 990]]
* [[Media:Creative_Commons_2021_-_FS_Final_0718.pdf | Independent audit]]
''' 2020 '''
* [[Media:2020_Creative_Commons_Public_Disclosure_Client_Copy.pdf | IRS Form 990]]
* [[Media:Creative_Commons_2020_-_FS_Final_0621_(1).pdf | Independent audit]]
''' 2019 '''
* [[Media:2019_Creative_Commons_990_Public_Disclosure_Client_Copy.pdf | IRS Form 990]]
* [[Media:Creative_Commons_2019_-_FS_Final_0708.pdf |Independent audit]]
''' 2018 '''
* [[Media:2018_Creative_Commons_Pub_Disc_Client_Copy.pdf|IRS Form 990]]
* [[Media:Creative_Commons_2018_-_FS_Final_0306.pdf|Independent audit]]
''' 2017 '''
* [[Media:2017_Creative_Commons_Public_Disclosure_Client_Copy.pdf|IRS Form 990]]
* [[Media:Creative_Commons_2017_-_Final_FS_1002.pdf|Independent audit]]

''' 2016 '''
* [[Media:2016_990_Public_Filing.pdf|IRS Form 990]]
* [[Media:Creative_Commons_2016_Final_FS_11-8.pdf|Independent audit]]

''' 2015 '''
* [[Media:2015_CC.pdf|IRS Form 990]]
* [https://drive.google.com/open?id=0B2UhiNCe0qFcSmRQQUVkUlllem8 Independent audit]

''' 2014 '''
* [[Media:Creative_Commons_2014_Form_990_Public_Disclosure_Copy.pdf|IRS Form 990]]
* [https://drive.google.com/open?id=0B2UhiNCe0qFcSVNPMVdoMUxOdTA Independent audit]

''' 2013 '''
* [[Media:Creative_Commons_form990_2013.pdf|IRS Form 990]]
* [https://drive.google.com/open?id=0B2UhiNCe0qFcUFV1RVk0Rm0xQzg Independent audit]

''' 2012'''
* [[Media:990-2012B.pdf|IRS Form 990]]
* [[Media:2012_CC_Audited_Financials.pdf|Independent audit]]

''' 2011 '''
* [[Media:2011_Form_990_-_Public.pdf|IRS Form 990]]
* [[Media:2011_CC_Audited_Financials.pdf|Independent audit]]

''' 2010 '''
* [[Media:990-2010B.pdf|IRS Form 990]]
* [[Media:Audit2010.pdf|Independent audit]]

''' 2009 '''
* [[Media:990-2009.pdf|IRS Form 990]]
* [[Media:Audit2009.pdf|Independent audit]]

''' 2008 '''
* [[Media:990-2008.pdf|IRS Form 990]]
* [[Media:Audit2008.pdf|Independent audit]]

''' 2007 '''
* [[Media:990-2007.pdf|IRS Form 990]]
* [[Media:Audit2007.pdf|Independent audit]]

''' 2006 '''
* [[Media:990-2006.pdf|IRS Form 990]]
* [[Media:Audit2006.pdf|Independent audit]]

''' 2005 '''
* [[Media:990-2005.pdf|IRS Form 990]]
* [[Media:Audit2005.pdf|Independent audit]]

''' 2004 '''
* [[Media:990-2004.pdf|IRS Form 990]]
* [[Media:Audit2004.pdf|Independent audit]]

''' 2003 '''
* [[Media:990-2003.pdf|IRS Form 990]]
* [[Media:Audit2003.pdf|Independent audit]]

''' 2002 '''
* [[Media:990-2002.pdf|IRS Form 990]]
* [[Media:Audit2002.pdf|Independent audit]]

''' 2001 '''
* [[Media:990-2001.pdf|IRS Form 990]]

File:2023 Creative Commons Corporation Pub Disc Client Copy.pdf

2025-01-07T20:59:58Z

CCID-timidrobot:

Public reports

2024-12-17T15:56:20Z

CCID-timidrobot: add link to CreativeCommons.org Annual Reports page

The purpose of this portal is to provide transparent access to public documents concerning the financial status and governance of the Creative Commons organization.

== Governance documents ==
* [[Media:Charter_cc.pdf|Incorporation document and charter]]
* [[ Media:Final_CC_Governance_Policies_.pdf |Board Governance Policies (effective Jan 1, 2022)]]
* [[ Media:Amended_Bylaws_%28Final%29.pdf |Organization Bylaws (amended 2021 December)]]
** [[Media:Bylaws_-_Amended_and_Restated_March_4_2018_%28final%29.pdf|Organization Bylaws (amended 2018 March)]]
** [[Media:CC_Amended_and_Restated_Bylaws_%28effective_6_Dec_2015%2C_amended_5_June_2016%29-1.pdf|Organization Bylaws (amended 2016 June)]]
** [[Media:CC_Amended_and_Restated_Bylaws_%28effective_6_Dec_2015%29.pdf|Organization Bylaws (amended 2015 December)]]
** [[Media:bylaws.pdf|Organization Bylaws (pre 2015 December)]]
* [[Media:1023.pdf|Form 1023 tax-exempt non-profit application and supplements]]
* [[Media:irsexempt.pdf|IRS tax-exempt determination letter]]
* [[Media:Audit_Committee_Charter_as_amended_2017-11-18_3.pdf|Audit Committee Charter]]
* [http://wiki.creativecommons.org/License_Versions License versioning process]

== Policies for staff, board and officers, and community members==

* [https://creativecommons.org/wp-content/uploads/2017/11/Global_Network_Membership_Charter.pdf CC Global Network Charter, including Code of Conduct for all participants]
* [https://wiki.creativecommons.org/images/b/be/Final_CC_Governance_Policies_.pdf CC Board Governance Policies]
* [https://drive.google.com/file/d/17KO9YPKh4JDb9-JoeNYogBC0kbmWeAUt/view Board Director Expectations]
* [https://summit.creativecommons.org/summit-code-of-conduct/ Summit Code of Conduct, updated in advance of each Summit]]
* [[Media:CC_Handbook,_April_1,_2022.pdf|All Employee Handbook, April 2022]]
* [[Media:Final_US_employee_handbook.pdf|Creative Commons Employee Handbook (no longer in use)]]
* [[Media:CAHandbookMay2018.pdf|0941176 B.C. LTD Employee Handbook(no longer in use)]]
* [[Media:Codes_of_Conduct_for_Employees_%28approved_March_4%2C_2018%29%281%29.pdf|Code of Conduct (Employees) updated 2018 March (no longer in use)]]
* [[Media:Creative_Commons_Code_of_Conduct_for_Directors_and_Officers_%28adopted_Mar_4_2018%29.pdf|Code of Conduct (Directors) updated 2018 March (no longer in use)]]

== Other policies==
* [http://creativecommons.org/terms Website terms of use]
* [http://creativecommons.org/policies Copyright and trademark policies]
* [http://creativecommons.org/privacy Privacy policy]
* [http://wiki.creativecommons.org/Lobbying Lobbying policy]
* [http://wiki.creativecommons.org/Internet_Services Affiliate Internet Services Policy]
* [http://wiki.creativecommons.org/Merchandising Merchandising Policy]
* [http://wiki.creativecommons.org/Policy_Advocacy_Guidelines Policy & Advocacy Guidelines]
* [https://creativecommons.github.io/community/code-of-conduct/enforcement/ Enforcement policy for our Slack and open source codes of conduct]
* [https://creativecommons.org/about/get-involved/donor-screening-guidelines/ Creative Commons Guidelines for Screening Donors]

== Annual reports ==

''' Organizational strategy document '''
* [http://wiki.creativecommons.org/images/c/ce/Future-of-creative-commons.pdf The Future of Creative Commons], June 2013

''' Organization-wide report '''
* '''(Also see [https://creativecommons.org/annual-reports/ Annual Reports - Creative Commons])'''
* [https://creativecommons.org/wp-content/uploads/2024/04/2023-Creative-Commons-Annual-Report-2-1.pdf 2023 Annual Report (7mb PDF)]
* [https://creativecommons.org/state-of-the-commons-2022/ State of the Commons 2022 - Creative Commons]
* [https://creativecommons.org/2022/04/05/2021-annual-report/ Creative Commons 2021 State of the Commons Annual Report - Creative Commons]
* [https://wiki.creativecommons.org/images/2/2e/CC_State_of_the_Commons_2020.pdf State of the Common | 2020 (2.5mb PDF)]
* [https://wiki.creativecommons.org/images/2/20/CC_AnnualReport_2019.pdf State of the Common | 2019 (4.1mb PDF)]
* [https://stateof.creativecommons.org/ State of the Commons, 2017]
* [https://stateof.creativecommons.org/2016 State of the Commons, 2016]
* [https://stateof.creativecommons.org/2015 State of the Commons, 2015]
* [http://teamopen.cc/thefuture/ 2013-2014]
* [http://dispatches.creativecommons.org/ 2011-2012]

''' Affiliate Network reports '''
* [http://wiki.creativecommons.org/Affiliate_Reporting/2010 2010]

== Funding sources ==
* Donor List: [https://creativecommons.org/supporters/ Supporters - Creative Commons]
* Public announcements of major grants:
** [http://creativecommons.org/weblog/entry/27097 Gates Foundation Department of Labor grantee assistance]
** [http://creativecommons.org/press-releases/entry/8175 Hewlett Foundation general operating and ccLearn]
** [http://creativecommons.org/press-releases/entry/7945 5 x 5 Funding Challenge]
** [http://creativecommons.org/press-releases/entry/8322 Omidyar Network]
** [http://creativecommons.org/press-releases/entry/26078 Nature Publishing Group]
** [http://creativecommons.org/press-releases/entry/7183 Technology company contributions]

== Other ==
* [[Media:Amended_DMCA_form.pdf|DMCA Designation of Agent to Receive Notification of Claimed Infringement]]

== Tax returns and audit information ==
''' 2022 '''
* [[Media: 2022_Creative_Commons_Corporation_Pub_Disc_Client_Copy.pdf| IRS Form 990]]
* [[Media:Creative_Commons_2022_-_FS_Final_0807.pdf | Independent audit]]
''' 2021 '''
* [[Media: 2021_Creative_Commons_Corporation_Public_Disclosure_Client_Copy.pdf | IRS Form 990]]
* [[Media:Creative_Commons_2021_-_FS_Final_0718.pdf | Independent audit]]
''' 2020 '''
* [[Media:2020_Creative_Commons_Public_Disclosure_Client_Copy.pdf | IRS Form 990]]
* [[Media:Creative_Commons_2020_-_FS_Final_0621_(1).pdf | Independent audit]]
''' 2019 '''
* [[Media:2019_Creative_Commons_990_Public_Disclosure_Client_Copy.pdf | IRS Form 990]]
* [[Media:Creative_Commons_2019_-_FS_Final_0708.pdf |Independent audit]]
''' 2018 '''
* [[Media:2018_Creative_Commons_Pub_Disc_Client_Copy.pdf|IRS Form 990]]
* [[Media:Creative_Commons_2018_-_FS_Final_0306.pdf|Independent audit]]
''' 2017 '''
* [[Media:2017_Creative_Commons_Public_Disclosure_Client_Copy.pdf|IRS Form 990]]
* [[Media:Creative_Commons_2017_-_Final_FS_1002.pdf|Independent audit]]

''' 2016 '''
* [[Media:2016_990_Public_Filing.pdf|IRS Form 990]]
* [[Media:Creative_Commons_2016_Final_FS_11-8.pdf|Independent audit]]

''' 2015 '''
* [[Media:2015_CC.pdf|IRS Form 990]]
* [https://drive.google.com/open?id=0B2UhiNCe0qFcSmRQQUVkUlllem8 Independent audit]

''' 2014 '''
* [[Media:Creative_Commons_2014_Form_990_Public_Disclosure_Copy.pdf|IRS Form 990]]
* [https://drive.google.com/open?id=0B2UhiNCe0qFcSVNPMVdoMUxOdTA Independent audit]

''' 2013 '''
* [[Media:Creative_Commons_form990_2013.pdf|IRS Form 990]]
* [https://drive.google.com/open?id=0B2UhiNCe0qFcUFV1RVk0Rm0xQzg Independent audit]

''' 2012'''
* [[Media:990-2012B.pdf|IRS Form 990]]
* [[Media:2012_CC_Audited_Financials.pdf|Independent audit]]

''' 2011 '''
* [[Media:2011_Form_990_-_Public.pdf|IRS Form 990]]
* [[Media:2011_CC_Audited_Financials.pdf|Independent audit]]

''' 2010 '''
* [[Media:990-2010B.pdf|IRS Form 990]]
* [[Media:Audit2010.pdf|Independent audit]]

''' 2009 '''
* [[Media:990-2009.pdf|IRS Form 990]]
* [[Media:Audit2009.pdf|Independent audit]]

''' 2008 '''
* [[Media:990-2008.pdf|IRS Form 990]]
* [[Media:Audit2008.pdf|Independent audit]]

''' 2007 '''
* [[Media:990-2007.pdf|IRS Form 990]]
* [[Media:Audit2007.pdf|Independent audit]]

''' 2006 '''
* [[Media:990-2006.pdf|IRS Form 990]]
* [[Media:Audit2006.pdf|Independent audit]]

''' 2005 '''
* [[Media:990-2005.pdf|IRS Form 990]]
* [[Media:Audit2005.pdf|Independent audit]]

''' 2004 '''
* [[Media:990-2004.pdf|IRS Form 990]]
* [[Media:Audit2004.pdf|Independent audit]]

''' 2003 '''
* [[Media:990-2003.pdf|IRS Form 990]]
* [[Media:Audit2003.pdf|Independent audit]]

''' 2002 '''
* [[Media:990-2002.pdf|IRS Form 990]]
* [[Media:Audit2002.pdf|Independent audit]]

''' 2001 '''
* [[Media:990-2001.pdf|IRS Form 990]]

Public reports

2024-12-17T15:53:13Z

CCID-timidrobot: add link to 2023 Annual Report

The purpose of this portal is to provide transparent access to public documents concerning the financial status and governance of the Creative Commons organization.

== Governance documents ==
* [[Media:Charter_cc.pdf|Incorporation document and charter]]
* [[ Media:Final_CC_Governance_Policies_.pdf |Board Governance Policies (effective Jan 1, 2022)]]
* [[ Media:Amended_Bylaws_%28Final%29.pdf |Organization Bylaws (amended 2021 December)]]
** [[Media:Bylaws_-_Amended_and_Restated_March_4_2018_%28final%29.pdf|Organization Bylaws (amended 2018 March)]]
** [[Media:CC_Amended_and_Restated_Bylaws_%28effective_6_Dec_2015%2C_amended_5_June_2016%29-1.pdf|Organization Bylaws (amended 2016 June)]]
** [[Media:CC_Amended_and_Restated_Bylaws_%28effective_6_Dec_2015%29.pdf|Organization Bylaws (amended 2015 December)]]
** [[Media:bylaws.pdf|Organization Bylaws (pre 2015 December)]]
* [[Media:1023.pdf|Form 1023 tax-exempt non-profit application and supplements]]
* [[Media:irsexempt.pdf|IRS tax-exempt determination letter]]
* [[Media:Audit_Committee_Charter_as_amended_2017-11-18_3.pdf|Audit Committee Charter]]
* [http://wiki.creativecommons.org/License_Versions License versioning process]

== Policies for staff, board and officers, and community members==

* [https://creativecommons.org/wp-content/uploads/2017/11/Global_Network_Membership_Charter.pdf CC Global Network Charter, including Code of Conduct for all participants]
* [https://wiki.creativecommons.org/images/b/be/Final_CC_Governance_Policies_.pdf CC Board Governance Policies]
* [https://drive.google.com/file/d/17KO9YPKh4JDb9-JoeNYogBC0kbmWeAUt/view Board Director Expectations]
* [https://summit.creativecommons.org/summit-code-of-conduct/ Summit Code of Conduct, updated in advance of each Summit]]
* [[Media:CC_Handbook,_April_1,_2022.pdf|All Employee Handbook, April 2022]]
* [[Media:Final_US_employee_handbook.pdf|Creative Commons Employee Handbook (no longer in use)]]
* [[Media:CAHandbookMay2018.pdf|0941176 B.C. LTD Employee Handbook(no longer in use)]]
* [[Media:Codes_of_Conduct_for_Employees_%28approved_March_4%2C_2018%29%281%29.pdf|Code of Conduct (Employees) updated 2018 March (no longer in use)]]
* [[Media:Creative_Commons_Code_of_Conduct_for_Directors_and_Officers_%28adopted_Mar_4_2018%29.pdf|Code of Conduct (Directors) updated 2018 March (no longer in use)]]

== Other policies==
* [http://creativecommons.org/terms Website terms of use]
* [http://creativecommons.org/policies Copyright and trademark policies]
* [http://creativecommons.org/privacy Privacy policy]
* [http://wiki.creativecommons.org/Lobbying Lobbying policy]
* [http://wiki.creativecommons.org/Internet_Services Affiliate Internet Services Policy]
* [http://wiki.creativecommons.org/Merchandising Merchandising Policy]
* [http://wiki.creativecommons.org/Policy_Advocacy_Guidelines Policy & Advocacy Guidelines]
* [https://creativecommons.github.io/community/code-of-conduct/enforcement/ Enforcement policy for our Slack and open source codes of conduct]
* [https://creativecommons.org/about/get-involved/donor-screening-guidelines/ Creative Commons Guidelines for Screening Donors]

== Annual reports ==

''' Organizational strategy document '''
* [http://wiki.creativecommons.org/images/c/ce/Future-of-creative-commons.pdf The Future of Creative Commons], June 2013

''' Organization-wide report '''
* [https://creativecommons.org/wp-content/uploads/2024/04/2023-Creative-Commons-Annual-Report-2-1.pdf 2023 Annual Report (7mb PDF)]
* [https://creativecommons.org/state-of-the-commons-2022/ State of the Commons 2022 - Creative Commons]
* [https://creativecommons.org/2022/04/05/2021-annual-report/ Creative Commons 2021 State of the Commons Annual Report - Creative Commons]
* [https://wiki.creativecommons.org/images/2/2e/CC_State_of_the_Commons_2020.pdf State of the Common | 2020 (2.5mb PDF)]
* [https://wiki.creativecommons.org/images/2/20/CC_AnnualReport_2019.pdf State of the Common | 2019 (4.1mb PDF)]
* [https://stateof.creativecommons.org/ State of the Commons, 2017]
* [https://stateof.creativecommons.org/2016 State of the Commons, 2016]
* [https://stateof.creativecommons.org/2015 State of the Commons, 2015]
* [http://teamopen.cc/thefuture/ 2013-2014]
* [http://dispatches.creativecommons.org/ 2011-2012]

''' Affiliate Network reports '''
* [http://wiki.creativecommons.org/Affiliate_Reporting/2010 2010]

== Funding sources ==
* Donor List: [https://creativecommons.org/supporters/ Supporters - Creative Commons]
* Public announcements of major grants:
** [http://creativecommons.org/weblog/entry/27097 Gates Foundation Department of Labor grantee assistance]
** [http://creativecommons.org/press-releases/entry/8175 Hewlett Foundation general operating and ccLearn]
** [http://creativecommons.org/press-releases/entry/7945 5 x 5 Funding Challenge]
** [http://creativecommons.org/press-releases/entry/8322 Omidyar Network]
** [http://creativecommons.org/press-releases/entry/26078 Nature Publishing Group]
** [http://creativecommons.org/press-releases/entry/7183 Technology company contributions]

== Other ==
* [[Media:Amended_DMCA_form.pdf|DMCA Designation of Agent to Receive Notification of Claimed Infringement]]

== Tax returns and audit information ==
''' 2022 '''
* [[Media: 2022_Creative_Commons_Corporation_Pub_Disc_Client_Copy.pdf| IRS Form 990]]
* [[Media:Creative_Commons_2022_-_FS_Final_0807.pdf | Independent audit]]
''' 2021 '''
* [[Media: 2021_Creative_Commons_Corporation_Public_Disclosure_Client_Copy.pdf | IRS Form 990]]
* [[Media:Creative_Commons_2021_-_FS_Final_0718.pdf | Independent audit]]
''' 2020 '''
* [[Media:2020_Creative_Commons_Public_Disclosure_Client_Copy.pdf | IRS Form 990]]
* [[Media:Creative_Commons_2020_-_FS_Final_0621_(1).pdf | Independent audit]]
''' 2019 '''
* [[Media:2019_Creative_Commons_990_Public_Disclosure_Client_Copy.pdf | IRS Form 990]]
* [[Media:Creative_Commons_2019_-_FS_Final_0708.pdf |Independent audit]]
''' 2018 '''
* [[Media:2018_Creative_Commons_Pub_Disc_Client_Copy.pdf|IRS Form 990]]
* [[Media:Creative_Commons_2018_-_FS_Final_0306.pdf|Independent audit]]
''' 2017 '''
* [[Media:2017_Creative_Commons_Public_Disclosure_Client_Copy.pdf|IRS Form 990]]
* [[Media:Creative_Commons_2017_-_Final_FS_1002.pdf|Independent audit]]

''' 2016 '''
* [[Media:2016_990_Public_Filing.pdf|IRS Form 990]]
* [[Media:Creative_Commons_2016_Final_FS_11-8.pdf|Independent audit]]

''' 2015 '''
* [[Media:2015_CC.pdf|IRS Form 990]]
* [https://drive.google.com/open?id=0B2UhiNCe0qFcSmRQQUVkUlllem8 Independent audit]

''' 2014 '''
* [[Media:Creative_Commons_2014_Form_990_Public_Disclosure_Copy.pdf|IRS Form 990]]
* [https://drive.google.com/open?id=0B2UhiNCe0qFcSVNPMVdoMUxOdTA Independent audit]

''' 2013 '''
* [[Media:Creative_Commons_form990_2013.pdf|IRS Form 990]]
* [https://drive.google.com/open?id=0B2UhiNCe0qFcUFV1RVk0Rm0xQzg Independent audit]

''' 2012'''
* [[Media:990-2012B.pdf|IRS Form 990]]
* [[Media:2012_CC_Audited_Financials.pdf|Independent audit]]

''' 2011 '''
* [[Media:2011_Form_990_-_Public.pdf|IRS Form 990]]
* [[Media:2011_CC_Audited_Financials.pdf|Independent audit]]

''' 2010 '''
* [[Media:990-2010B.pdf|IRS Form 990]]
* [[Media:Audit2010.pdf|Independent audit]]

''' 2009 '''
* [[Media:990-2009.pdf|IRS Form 990]]
* [[Media:Audit2009.pdf|Independent audit]]

''' 2008 '''
* [[Media:990-2008.pdf|IRS Form 990]]
* [[Media:Audit2008.pdf|Independent audit]]

''' 2007 '''
* [[Media:990-2007.pdf|IRS Form 990]]
* [[Media:Audit2007.pdf|Independent audit]]

''' 2006 '''
* [[Media:990-2006.pdf|IRS Form 990]]
* [[Media:Audit2006.pdf|Independent audit]]

''' 2005 '''
* [[Media:990-2005.pdf|IRS Form 990]]
* [[Media:Audit2005.pdf|Independent audit]]

''' 2004 '''
* [[Media:990-2004.pdf|IRS Form 990]]
* [[Media:Audit2004.pdf|Independent audit]]

''' 2003 '''
* [[Media:990-2003.pdf|IRS Form 990]]
* [[Media:Audit2003.pdf|Independent audit]]

''' 2002 '''
* [[Media:990-2002.pdf|IRS Form 990]]
* [[Media:Audit2002.pdf|Independent audit]]

''' 2001 '''
* [[Media:990-2001.pdf|IRS Form 990]]

Public reports

2024-12-16T15:59:14Z

CCID-timidrobot: update Organization-wide report with 2022, 2021, and 2020

The purpose of this portal is to provide transparent access to public documents concerning the financial status and governance of the Creative Commons organization.

== Governance documents ==
* [[Media:Charter_cc.pdf|Incorporation document and charter]]
* [[ Media:Final_CC_Governance_Policies_.pdf |Board Governance Policies (effective Jan 1, 2022)]]
* [[ Media:Amended_Bylaws_%28Final%29.pdf |Organization Bylaws (amended 2021 December)]]
** [[Media:Bylaws_-_Amended_and_Restated_March_4_2018_%28final%29.pdf|Organization Bylaws (amended 2018 March)]]
** [[Media:CC_Amended_and_Restated_Bylaws_%28effective_6_Dec_2015%2C_amended_5_June_2016%29-1.pdf|Organization Bylaws (amended 2016 June)]]
** [[Media:CC_Amended_and_Restated_Bylaws_%28effective_6_Dec_2015%29.pdf|Organization Bylaws (amended 2015 December)]]
** [[Media:bylaws.pdf|Organization Bylaws (pre 2015 December)]]
* [[Media:1023.pdf|Form 1023 tax-exempt non-profit application and supplements]]
* [[Media:irsexempt.pdf|IRS tax-exempt determination letter]]
* [[Media:Audit_Committee_Charter_as_amended_2017-11-18_3.pdf|Audit Committee Charter]]
* [http://wiki.creativecommons.org/License_Versions License versioning process]

== Policies for staff, board and officers, and community members==

* [https://creativecommons.org/wp-content/uploads/2017/11/Global_Network_Membership_Charter.pdf CC Global Network Charter, including Code of Conduct for all participants]
* [https://wiki.creativecommons.org/images/b/be/Final_CC_Governance_Policies_.pdf CC Board Governance Policies]
* [https://drive.google.com/file/d/17KO9YPKh4JDb9-JoeNYogBC0kbmWeAUt/view Board Director Expectations]
* [https://summit.creativecommons.org/summit-code-of-conduct/ Summit Code of Conduct, updated in advance of each Summit]]
* [[Media:CC_Handbook,_April_1,_2022.pdf|All Employee Handbook, April 2022]]
* [[Media:Final_US_employee_handbook.pdf|Creative Commons Employee Handbook (no longer in use)]]
* [[Media:CAHandbookMay2018.pdf|0941176 B.C. LTD Employee Handbook(no longer in use)]]
* [[Media:Codes_of_Conduct_for_Employees_%28approved_March_4%2C_2018%29%281%29.pdf|Code of Conduct (Employees) updated 2018 March (no longer in use)]]
* [[Media:Creative_Commons_Code_of_Conduct_for_Directors_and_Officers_%28adopted_Mar_4_2018%29.pdf|Code of Conduct (Directors) updated 2018 March (no longer in use)]]

== Other policies==
* [http://creativecommons.org/terms Website terms of use]
* [http://creativecommons.org/policies Copyright and trademark policies]
* [http://creativecommons.org/privacy Privacy policy]
* [http://wiki.creativecommons.org/Lobbying Lobbying policy]
* [http://wiki.creativecommons.org/Internet_Services Affiliate Internet Services Policy]
* [http://wiki.creativecommons.org/Merchandising Merchandising Policy]
* [http://wiki.creativecommons.org/Policy_Advocacy_Guidelines Policy & Advocacy Guidelines]
* [https://creativecommons.github.io/community/code-of-conduct/enforcement/ Enforcement policy for our Slack and open source codes of conduct]
* [https://creativecommons.org/about/get-involved/donor-screening-guidelines/ Creative Commons Guidelines for Screening Donors]

== Annual reports ==

''' Organizational strategy document '''
* [http://wiki.creativecommons.org/images/c/ce/Future-of-creative-commons.pdf The Future of Creative Commons], June 2013

''' Organization-wide report '''
* [https://creativecommons.org/state-of-the-commons-2022/ State of the Commons 2022 - Creative Commons]
* [https://creativecommons.org/2022/04/05/2021-annual-report/ Creative Commons 2021 State of the Commons Annual Report - Creative Commons]
* [https://wiki.creativecommons.org/images/2/2e/CC_State_of_the_Commons_2020.pdf State of the Common | 2020 (2.5mb PDF)]
* [https://wiki.creativecommons.org/images/2/20/CC_AnnualReport_2019.pdf State of the Common | 2019 (4.1mb PDF)]
* [https://stateof.creativecommons.org/ State of the Commons, 2017]
* [https://stateof.creativecommons.org/2016 State of the Commons, 2016]
* [https://stateof.creativecommons.org/2015 State of the Commons, 2015]
* [http://teamopen.cc/thefuture/ 2013-2014]
* [http://dispatches.creativecommons.org/ 2011-2012]

''' Affiliate Network reports '''
* [http://wiki.creativecommons.org/Affiliate_Reporting/2010 2010]

== Funding sources ==
* Donor List: [https://creativecommons.org/supporters/ Supporters - Creative Commons]
* Public announcements of major grants:
** [http://creativecommons.org/weblog/entry/27097 Gates Foundation Department of Labor grantee assistance]
** [http://creativecommons.org/press-releases/entry/8175 Hewlett Foundation general operating and ccLearn]
** [http://creativecommons.org/press-releases/entry/7945 5 x 5 Funding Challenge]
** [http://creativecommons.org/press-releases/entry/8322 Omidyar Network]
** [http://creativecommons.org/press-releases/entry/26078 Nature Publishing Group]
** [http://creativecommons.org/press-releases/entry/7183 Technology company contributions]

== Other ==
* [[Media:Amended_DMCA_form.pdf|DMCA Designation of Agent to Receive Notification of Claimed Infringement]]

== Tax returns and audit information ==
''' 2022 '''
* [[Media: 2022_Creative_Commons_Corporation_Pub_Disc_Client_Copy.pdf| IRS Form 990]]
* [[Media:Creative_Commons_2022_-_FS_Final_0807.pdf | Independent audit]]
''' 2021 '''
* [[Media: 2021_Creative_Commons_Corporation_Public_Disclosure_Client_Copy.pdf | IRS Form 990]]
* [[Media:Creative_Commons_2021_-_FS_Final_0718.pdf | Independent audit]]
''' 2020 '''
* [[Media:2020_Creative_Commons_Public_Disclosure_Client_Copy.pdf | IRS Form 990]]
* [[Media:Creative_Commons_2020_-_FS_Final_0621_(1).pdf | Independent audit]]
''' 2019 '''
* [[Media:2019_Creative_Commons_990_Public_Disclosure_Client_Copy.pdf | IRS Form 990]]
* [[Media:Creative_Commons_2019_-_FS_Final_0708.pdf |Independent audit]]
''' 2018 '''
* [[Media:2018_Creative_Commons_Pub_Disc_Client_Copy.pdf|IRS Form 990]]
* [[Media:Creative_Commons_2018_-_FS_Final_0306.pdf|Independent audit]]
''' 2017 '''
* [[Media:2017_Creative_Commons_Public_Disclosure_Client_Copy.pdf|IRS Form 990]]
* [[Media:Creative_Commons_2017_-_Final_FS_1002.pdf|Independent audit]]

''' 2016 '''
* [[Media:2016_990_Public_Filing.pdf|IRS Form 990]]
* [[Media:Creative_Commons_2016_Final_FS_11-8.pdf|Independent audit]]

''' 2015 '''
* [[Media:2015_CC.pdf|IRS Form 990]]
* [https://drive.google.com/open?id=0B2UhiNCe0qFcSmRQQUVkUlllem8 Independent audit]

''' 2014 '''
* [[Media:Creative_Commons_2014_Form_990_Public_Disclosure_Copy.pdf|IRS Form 990]]
* [https://drive.google.com/open?id=0B2UhiNCe0qFcSVNPMVdoMUxOdTA Independent audit]

''' 2013 '''
* [[Media:Creative_Commons_form990_2013.pdf|IRS Form 990]]
* [https://drive.google.com/open?id=0B2UhiNCe0qFcUFV1RVk0Rm0xQzg Independent audit]

''' 2012'''
* [[Media:990-2012B.pdf|IRS Form 990]]
* [[Media:2012_CC_Audited_Financials.pdf|Independent audit]]

''' 2011 '''
* [[Media:2011_Form_990_-_Public.pdf|IRS Form 990]]
* [[Media:2011_CC_Audited_Financials.pdf|Independent audit]]

''' 2010 '''
* [[Media:990-2010B.pdf|IRS Form 990]]
* [[Media:Audit2010.pdf|Independent audit]]

''' 2009 '''
* [[Media:990-2009.pdf|IRS Form 990]]
* [[Media:Audit2009.pdf|Independent audit]]

''' 2008 '''
* [[Media:990-2008.pdf|IRS Form 990]]
* [[Media:Audit2008.pdf|Independent audit]]

''' 2007 '''
* [[Media:990-2007.pdf|IRS Form 990]]
* [[Media:Audit2007.pdf|Independent audit]]

''' 2006 '''
* [[Media:990-2006.pdf|IRS Form 990]]
* [[Media:Audit2006.pdf|Independent audit]]

''' 2005 '''
* [[Media:990-2005.pdf|IRS Form 990]]
* [[Media:Audit2005.pdf|Independent audit]]

''' 2004 '''
* [[Media:990-2004.pdf|IRS Form 990]]
* [[Media:Audit2004.pdf|Independent audit]]

''' 2003 '''
* [[Media:990-2003.pdf|IRS Form 990]]
* [[Media:Audit2003.pdf|Independent audit]]

''' 2002 '''
* [[Media:990-2002.pdf|IRS Form 990]]
* [[Media:Audit2002.pdf|Independent audit]]

''' 2001 '''
* [[Media:990-2001.pdf|IRS Form 990]]

Recommended practices for attribution

2024-12-04T15:05:18Z

CCID-timidrobot: add links to translation pdfs

Read this in your language: ([https://creativecommons.org/wp-content/uploads/2024/10/Igbo-%E2%80%94-Recommended-Practices-for-Attribution.pdf Igbo]) ([https://creativecommons.org/wp-content/uploads/2024/10/Greek-%E2%80%94-Recommended-Practices-for-Attribution.pdf Ελληνικά]) ([https://creativecommons.org/wp-content/uploads/2024/10/Dutch%E2%80%94-Recommended-Practices-for-Attribution.pdf Nederlands]) ([https://creativecommons.org/wp-content/uploads/2024/10/Indonesian-%E2%80%94-Recommended-Practices-for-Attribution.pdf Bahasa Indonesia]) ([https://creativecommons.org/wp-content/uploads/2024/10/French-%E2%80%94-Recommended-Practices-for-Attribution.pdf français]) ([https://creativecommons.org/wp-content/uploads/2024/10/Turkish-%E2%80%94-Recommended-Practices-for-Attribution-1.pdf Türkçe]) ([https://creativecommons.org/wp-content/uploads/2024/10/Italian-%E2%80%94-Recommended-Practices-for-Attribution-1.pdf Swahili]) ([https://creativecommons.org/wp-content/uploads/2024/10/Italian-%E2%80%94-Recommended-Practices-for-Attribution-1.pdf italiano])

You can use CC-licensed materials as long as you follow the license conditions. One condition of all CC licenses is attribution: crediting the author and noting the source and the license. Generally speaking, attribution must reasonably include all relevant information supplied by the licensor. Because each use case is different, you can decide what form of attribution is most suitable for your specific situation. The following examples are intended to illustrate what typical prudent practices look like. We expect community norms and expectations to evolve with time, and will adapt this guide accordingly.
In addition to attribution, there are also [https://wiki.creativecommons.org/wiki/Considerations_for_licensors_and_licensees#Considerations_for_licensees|other things to consider as a licensor or a licensee]. If you are a licensor and would like to learn how to license your own material, take a look at [https://wiki.creativecommons.org/wiki/Marking_your_work_with_a_CC_license our guide on how to mark your work with a CC license].

==Basic components of attribution==

[[File:19th_century_tassel_from_Smithsonian.jpeg|290px|left]]

Whenever you are reusing CC licensed works, we recommend that the attribution include the '''T'''itle, '''A'''uthor, '''S'''ource, and '''L'''icense. This is true whether you’re sharing the work as-is or if you have made an adaptation. To remember these attribution elements, it’s helpful to think of the acronym: '''TASL'''.

Let’s now go through '''TASL''' — we will explain each element in more detail:

'''Title''': What is the name of the work?

:If a title was provided for the work, include it as a part of the attribution. Sometimes a title is not provided; in that case, there’s no need to mention the title.

:The inclusion of title is a requirement of all CC licenses version 3.0 or earlier, and it is optional for the 4.0 suites. See [https://wiki.creativecommons.org/wiki/Recommended_practices_for_attribution#License_details License details].

'''Author''': Who allows you to use the work?

:We often use “author” as a shorthand when we are, legally speaking, referring to the “licensor” (a.k.a., the “copyright holder” or “rightsholder”). This is because, in most CC-licensed works, the licensor is the same person or entity as the author. When an author is licensing their work under a CC license, and has made their name available, include the author’s name as a component in your attribution. Sometimes, the licensor may want you to give credit to some other entity, like a company or institution, or the licensor may want to be credited by a pseudonym instead of their real name. In rare cases, the licensor may not want to be attributed at all. In all of these cases, do what the licensor requests.

:Sometimes, the author will also provide a copyright notice, which consists of the copyright symbol, year of publication, and the name of the author/licensor. Include the copyright notice as a part of your attribution if such information is provided.

'''Source''': Where can people find the work?

:Please make it possible for future users to find the source of the material by including a URL or hyperlink where the work resides. This often is where you found the work. If you found it somewhere other than the original site, try to include information about the original site where the work was first shared publicly. It is also better to use the original URL instead of a shortened link, whether you are hyperlinking or printing out the entire URL.

'''License''': How can you use the work?

:You must specify which CC license was applied to the work you are reusing. Each of the six different CC licenses come with distinct requirements for re-use. We recommend that you name and provide a link to the license, e.g., [http://creativecommons.org/licenses/by/4.0 CC BY 4.0] (http://creativecommons.org/licenses/by/4.0) for a work licensed under CC BY 4.0.

:Consider also including the “disclaimer of warranties,” which clarifies that the author makes no representations or warranties about the non-infringement or absence of other defects concerning the CC-licensed work. In plain English, this means that the users will use the work at their own risk.

:To sum up, if the licensor has provided any information related to TASL, consider including them in your attribution. We also recommend providing links to the Title, Author, Source, and License, where possible, so future users can easily access the information they need on a work and the license terms.
<hr>
===Reasonable attribution===

The CC licenses ask you to be reasonable:

:<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 90%;">You may satisfy the attribution requirement in any reasonable manner based on the medium, means and context in which the Licensed Material is used. For example, it may be reasonable to satisfy some or all of the conditions by retaining a copyright notice, or by providing a URI or hyperlink associated with the Licensed Material, if the copyright notice or webpage includes some or all of the required information.</div>

There is no single best or correct way of attribution, as long as your attribution is reasonable and suited to the medium you're working with.
<hr>

===License details===

If you have any doubts or questions, you can read the complete attribution requirements which are spelled out in detail in the legal code of every CC license, eg. http://creativecommons.org/licenses/by/4.0/legalcode This [[License_Versions#Detailed_attribution_comparison_chart|chart compares the detailed requirements across all versions of CC licenses.]]

==Examples of attribution==

We will now look at some examples in different media.

===Attributing an image===

Here is a photo. Below, we will go over some good and bad examples of how people might attribute it.

[[File:8256206923_c77e85319e_n.jpg]]
<hr>

====This is a great attribution====
<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">
"[http://www.flickr.com/photos/sixteenmilesofstring/8256206923/in/set-72157632200936657 Creative Commons 10th Birthday Celebration San Francisco]" by [http://www.flickr.com/photos/sixteenmilesofstring/ Timothy Vollmer] is licensed under [http://creativecommons.org/licenses/by/4.0/ CC BY 4.0]</div>

''Let’s go through TASL:''
:'''T'''itle? "Creative Commons 10th Birthday Celebration San Francisco"
:'''A'''uthor? "[http://www.flickr.com/photos/sixteenmilesofstring/ Timothy Vollmer]" - linked to his profile page
:'''S'''ource? "[http://www.flickr.com/photos/sixteenmilesofstring/8256206923/in/set-72157632200936657 Creative Commons 10th Birthday Celebration San Francisco]" - linked to original Flickr page
:'''L'''icense? "[http://creativecommons.org/licenses/by/4.0/ CC BY 4.0]" - linked to license deed

Most importantly, this attribution reasonably includes all the relevant information provided by the author.
<hr>

====This is a pretty good attribution====

<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">[http://www.flickr.com/photos/sixteenmilesofstring/8256206923/in/set-72157632200936657 Photo] by Timothy Vollmer/ [http://creativecommons.org/licenses/by/2.0/ CC BY]</div>

''Let’s go through TASL:''
:'''T'''itle? Title is not noted but at least the source is linked.
:'''A'''uthor? "Timothy Vollmer"
:'''S'''ource? "[http://www.flickr.com/photos/sixteenmilesofstring/8256206923/in/set-72157632200936657 Photo]" - linked to original Flickr page
:'''L'''icense? "[http://creativecommons.org/licenses/by/4.0/ CC BY]" - linked to license deed

As you see, a good attribution includes all the essential '''TASL''' elements, even though they may not mirror the format of credit the author has requested.
<hr>

==== This is an incorrect attribution====
<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">Photo: Creative Commons</div>

''Let’s go through TASL'':
:'''T'''itle? Title of the image is not noted
:'''A'''uthor? Author is not noted (It is a common mistake to attribute CC-licensed photos to CC, but Creative Commons is not the author!)
:'''S'''ource? No link to the original source
:'''L'''icense? There is no mention of a license nor a link to the license. "Creative Commons" is the name of an organization; it does not equate to any of the licenses maintained by the Creative Commons.
<hr>

====This is a great attribution for an image you modified slightly====
:[[File:Cropped_tvol_cupcake.png|300px]]

<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">"[http://www.flickr.com/photos/sixteenmilesofstring/8256206923/in/set-72157632200936657 Creative Commons 10th Birthday Celebration San Francisco]" by [http://www.flickr.com/photos/sixteenmilesofstring/ Timothy Vollmer], used under [http://creativecommons.org/licenses/by/4.0/ CC BY 4.0] / Cropped from original</div>

Here, information on '''T'''itle, '''A'''uthor, '''S'''ource, and '''L'''icense are all included as requested by the author. The slight modification is also noted and briefly described.

Note if the modification changes the work’s meaning in a way that would be considered creative — that is, not a purely mechanical change or a simple crop/excerpt that keeps the original message undistorted, it would be considered creating a new adaptation of the original work. You cannot rely on a CC license that does not allow adaptation (e.g., CC BY-ND or CC BY-NC-ND) when making such modifications.

<hr>

====This is a great attribution for when you have created an adaptation====

:[[File:8256206923_c77e85319e_n_90fied.jpg|300px]]

<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">This work, "90fied", is adapted from "[http://www.flickr.com/photos/sixteenmilesofstring/8256206923/in/set-72157632200936657 Creative Commons 10th Birthday Celebration San Francisco]" by [http://www.flickr.com/photos/sixteenmilesofstring/ Timothy Vollmer], used under [http://creativecommons.org/licenses/by/4.0/ CC BY 4.0]. "90fied" is licensed under [http://creativecommons.org/licenses/by/4.0/ CC BY 4.0] by [Your name here].</div>

''Let’s go through TASL:''

Original '''T'''itle, '''A'''uthor, '''S'''ource, and '''L'''icense are all noted.

The original work is referenced and the fact that it is an adaptation is also noted, so viewers can see what has changed.

The author and other attribution information for the new adapted work is also noted.

Note: If you're at a point where you are licensing works that are adaptations, go to [[Marking your work with a CC license]].
<hr>

===Attributing music===

====When you incorporate music in an audio or video recording====
Music (both the underlying composition and the sound recordings) — such as a song, or a recording of natural sounds — can be attributed within the audio/video, and in the description text of the audio/video. How to attribute a CC licensed music in an audio or video recording will largely depend on what is reasonable for a chosen medium and platform.

Caution: Licenses with “ND” do not allow for adaptations. Your use of CC-licensed music is often an adaptation!

It is considered adaptation if you incorporate CC-licensed music into your work in a way that the CC-licensed music can no longer be seen as a stand-alone piece. For example, if you are using a song as background music in a podcast or in a video, it is considered an adaptation of the song.

Keep in mind that CC BY-ND and CC BY-NC-ND do not allow adaptations (although you may be authorized by law to do so, such as under a users’ right like fair use, or you may ask for the author’s permission independent of the CC license).
<hr>

[[File:Smithsonian_music_stand.jpeg|left|250px]]

=====This is a great attribution of background music in a podcast or a video=====
When reasonable to do so, we recommend that you include attribution both in the description box and in the podcast recording or the video recording itself.

If you are using the following song in a podcast: ‘Day Bird’ by Broke for Free ([https://brokeforfree.com brokeforfree.com]), this would be a great way to provide attribution (which you can see in [https://soundcloud.com/wearecc/open-minds-podcast-catherine-stihler-ceo-of-creative-commons the Creative Commons podcast]) —

:At the end of the podcast audio recording, the host says:
:<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 90%;">Special thanks to the musician Broke for Free, whose track “Day Bird” you heard at the beginning of this episode and you are listening to right now. It's under the Creative Commons Attribution License, meaning it's free for anyone to use. You can find it at the Free Music Archive—freemusicarchive.org</div>

:In the description box, the information text reads:
:<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 90%;">Theme music: “Day Bird” by Broke for Free ([https://brokeforfree.com brokeforfree.com]). Available for use under the CC BY 3.0 license ([https://creativecommons.org/licenses/by/3.0/ creativecommons.org/licenses/by/3.0/]), at [https://freemusicarchive.org/music/Broke_For_Free/Directionless_EP/Broke_For_Free_-_Directionless_EP_-_03_Day_Bird|the Free Music Archive].</div>

''Let’s go through TASL:''

:'''T'''itle? Both the recording and the description box include the title of the work, “Day Bird”

:'''A'''uthor? "Broke for Free," again, noted both in the recording and in the description box

:'''S'''ource? Both the author’s page and the archive’s page are included with links

:'''L'''icense? "CC BY 3.0" — linked to license deed

You cannot talk over, or remix, music licensed under CC BY-ND or CC BY-NC-ND.

<hr>

=====This is a bad attribution of background music in a podcast or a video=====

A bad attribution is one where you do not provide enough information for a user to find the music you are using. The following is a bad attribution for the same song:

:<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">No attribution is included in the podcast recording or the video itself.

In the description box, it says: “ Creative Commons music.”</div>

''Let’s go through TASL:''

:'''T'''itle? Title is not noted

:'''A'''uthor? Author is not noted

:'''S'''ource? Source is not noted; users cannot find the specific song used in the podcast

:'''L'''icense? No information on the CC license

The attribution information is not sufficient for people to find the song you have re-used.
<hr>

====When you are not adding new elements to the music====
When you re-use music without adding new elements to it, you are not making an adaptation. In that case, you can rely on any of the CC licenses, including CC BY-ND and CC BY-NC-ND. We recommend providing attribution information in writing.

[[File:Wiki_page_attributing_night_owl.png|400px]]

On [https://commons.wikimedia.org/wiki/File:Broke_For_Free_-_01_-_Night_Owl.ogg this Wikipedia page], you can see an example of great attribution for the sharing another soundtrack, “Night Owl” by Broke for Free, when it’s without adaptation.

''Let’s go through TASL:''

'''T'''itle? Title of the work, “Night Owl,” is noted

'''A'''uthor? "Broke for Free," noted and linked to the author’s webpage

'''S'''ource? A link is provided for the source

'''L'''icense? "CC BY 3.0" — linked to license deed
<hr>

===Attributing text===
Let’s take [https://github.com/getify/You-Dont-Know-JS ''You Don't Know JS Yet'' (2nd Edition)] as an example, and go over what your attribution may look like if you reuse the book series. The information under the “License & Copyright” section looks like this on the webpage where the book series was originally shared:
:[[File:attributing_You_Don't_Know_JS_Yet_(2nd_Edition).png|200px]]

We recommend that you retain all the information provided by the author of the book series when it is reasonable for you to do so. For example, if you are distributing digital copies or excerpts of the book series in a free seminar, or using parts of the book in a free online course or presentation, the attribution will likely look something like this:

:<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">This chapter is from “[https://github.com/getify/You-Dont-Know-JS You Don't Know JS Yet (2nd Edition)]” by [https://github.com/getify Kyle Simpson]. The book is licensed under the [https://creativecommons.org/licenses/by-nc-nd/4.0/ CC BY-NC-ND 4.0 license]. © 2019-2022 Kyle Simpson.</div>

On the other hand, if you are distributing hard copies of the book series or excerpts from the book series, instead of using hyperlinks, you may wish to include the links so it’s easier for users to locate the original source of the book, the author, and the CC license:

:<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">This chapter is from “You Don't Know JS Yet (2nd Edition)” (https://github.com/getify/You-Dont-Know-JS) by Kyle Simpson (https://github.com/getify). The book is licensed under the CC BY-NC-ND 4.0 license (https://creativecommons.org/licenses/by-nc-nd/4.0/). © 2019-2022 Kyle Simpson.</div>

Note that the CC BY-NC-ND license includes the NoDerivatives requirement, which indicates that no adaptations are allowed. You cannot make any adaptations relying on the CC BY-NC-CD license the author chose for the book. If you would like to make a translation of the book, for example, you will need to ask the author for permission first.

The CC BY-NC-ND license also includes the NonCommercial requirement. To learn more, take a look at [https://en.wikipedia.org/wiki/Creative_Commons_NonCommercial_license our guide about the NonCommercial licenses].
<hr>

=== Attributing materials from multiple sources ===

:[[File:Saylor_marking_example.jpg]]

''Let’s go through TASL:''

:'''T'''itle? Specific works are named, e.g., "Box-and-whisker Plots"

:'''A'''uthor? Different authors noted for the different works

:'''S'''ource? Original materials are linked for each work

:'''L'''icense? The different licenses (Creative Commons Attribution for Collaborative Statistics and Creative Commons Attribution-Noncommercial-ShareAlike for the Khan Academy video) are spelled out and linked for each work

:Lastly, it is clear which attribution belongs to which work.

You can visit the [http://www.saylor.org/courses/ma121/ Saylor.org Introduction to Statistics course page] to see how they marked it up directly.
<hr>

=== Publishing attribution on a separate web page ===
As stated above, recommended attribution depends on the medium you're working with. For media such as offline materials, video, audio, and images, consider publishing a web page with attribution information. For example, on a webpage featuring your audio recording, provide a credit list of material you used that adheres to best practices above. Doing so allows not only your material, but the materials you attribute, to be found by search engines and other web discovery tools. If possible within the medium, make the Author, Source, and License links the user can follow.

:<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">'''Example:'''<br>This video features the song [http://ccmixter.org/media/files/victor/6374 "Desaprendere (Treatment)"] by [http://fourstones.net/ fourstones], available under a Creative Commons [http://creativecommons.org/licenses/by-nc/2.5/ Attribution-Noncommercial 2.5 license].</div>

<hr>

==Citing public domain materials==
Although attribution is not a legal obligation under [https://creativecommons.org/share-your-work/public-domain/cc0/ CC0 dedication]’s or [https://creativecommons.org/share-your-work/public-domain/pdm/ CC Public Domain Mark]’s licensing terms, we recommend that you consider including information about the hosting institution for public domain materials when it is reasonable to do so. Citing public domain works in this way not only encourages institutions to digitize and share more public domain materials in their physical collections, but also empowers users to easily locate the original source.

Here is an example of citing the source of a public domain image. The following public domain image is digitized and hosted by the Rijksmuseum (the national museum of the Netherlands). The Rijksmuseum has applied a CC0 dedication to the image.

:[[File:Attributing_the_milkmaid.png|300px]]

You may provide credit in the following format:

:<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">“[http://hdl.handle.net/10934/RM0001.COLLECT.6417 The Milkmaid]” by Vermeer. The Rijksmuseum collection. The image is dedicated to the public domain under [https://creativecommons.org/share-your-work/public-domain/cc0/ CC0]. </div>

In most cases, people credit the source regardless of the work’s copyright status. Especially in an academic setting, providing source information about other people’s works has long been considered crucial to academic integrity. Copyright cannot be the only checkbox when deciding whether a source will be credited. You can learn more about [https://creativecommons.org/faq/#what-is-the-difference-between-plagiarism-and-copyright-infringement-and-what-role-do-cc-licenses-play-to-address-plagiarism how our licenses interact with academic citation standards in our FAQ].

== Common pitfalls ==

Below are some practices that you may wish to avoid. These practices are not always contrary to the Creative Commons licensing terms, but they often make it more challenging for users to find the original source and/or author.

'''Attribute in alt text'''
:Alt text is intended to provide accessible information about visual materials for users with cognitive disabilities or visual impairment. Using this field for licensing information makes browsing difficult for those users.

'''Attribute in metadata fields only'''
:While it is great to include attribution in metadata fields (such as EXIF for images), in most cases this is not the only place to include attribution information. This is because many users are likely not aware of, and will never see, attribution information included in metadata.

'''Credit authors by names other than the ones they have selected'''
:Many people believe that attribution must be given to the real name of the author of a work, but this is not the case — always give attribution to the name the author has specified, even if it is a pseudonym. If the author does not give a name or explicitly requests to be anonymous, you must give the other attribution information (i.e., “T” and “SL” from “TASL”) without crediting the author.

'''Credit a site (or Creative Commons itself!) instead of the author'''
:Unless an author specifically requests users to only credit a site, crediting the site where you have found the material cannot substitute crediting the author. An author may have uploaded material to a site under a CC license, but in most cases, the copyright is still held by the author, and it is the copyright holder who needs to be credited. For example, many photos sourced from Wikimedia Commons are attributed to Wikimedia when they must be attributed to the authors.

[[Category:Marking]]
[[Category:Licensing]]
[[Category:Community]]
[[Category:Media]]
[[Category:HOWTO]]
[[Category:Guide]]
{{Best Practice}}

PDM FAQ

2024-07-10T15:46:34Z

CCID-timidrobot: comment out chooser related text as current beta chooser does not support PDM

[[Category:FAQ]]
[[Category:PDM]]
[[Category:Public domain]]

These Public Domain Mark FAQs contain information that you should familiarize yourself with before applying the Public Domain Mark (“PDM”) to a work, or before using a work that is marked with the PDM. The information provided below is not exhaustive – it may not cover important issues that could affect you.
__TOC__
These FAQs are intended to supplement, not replace, our existing [http://wiki.creativecommons.org/FAQ FAQs] and our [http://wiki.creativecommons.org/CC0_FAQ CC0 FAQs]. You are encouraged to review those FAQs before using the PDM or any of our other legal tools or licenses. You should also read the [https://creativecommons.org/publicdomain/mark/1.0/ PDM deed] carefully, as well as the information linked to from the deed. The deed and supplemental information contain important information about the work that has been marked, and should be fully understood before you apply it to a work or use a PDM-marked work.

Please note: '''Creative Commons does not provide legal advice.''' The information provided below is not a substitute for legal advice and is not complete. Please consult your own legal advisor if you have any questions or concerns about the information provided below, about the Public Domain Mark or about Creative Commons licenses and tools generally.

=== Questions about the Public Domain Mark generally ===

==== What is the Public Domain Mark? ====

The Public Domain Mark (“PDM”) is a tool that allows anyone to mark and tag a work that is free of known copyright restrictions worldwide, all in a way that clearly communicates that status to the public and allows it to be easily discoverable. The PDM is not a legal instrument like CC0 or our licenses; there is no accompanying legal code or agreement. It should only be used to label a work that is already free of known copyright restrictions around the world, typically very old works. It should not be used to attempt to change a work’s current status under copyright law, or affect any person’s rights in a work. Just like CC0 and our licenses, PDM has a metadata-supported deed and is machine readable, allowing works properly tagged to be readily discovered over the Internet.

==== How does it work? ====

Anyone can use the PDM to mark a work that is free of known copyright restrictions. Information about the work, its author(s), and the person marking the work should be embedded in the HTML generated for the work. When supplied, this information may help users of the work evaluate the copyright status of the work for themselves, and learn more about the work. Again, please keep in mind that the PDM does not affect the legal status of the work or the legal rights of the author, the person identifying it or others. The PDM serves a marking and labeling function only.

====What is the difference between the PDM and CC0?====

PDM and CC0 differ in important respects and have distinct purposes. CC0 is intended for use only by authors or holders of copyright and related or neighboring rights (including sui generis database rights), in connection with '''works that are still subject to those rights''' in one or more jurisdictions. PDM, on the other hand, can be used by anyone, and is intended for use with''' works that are already free of known copyright restrictions throughout the world'''.

The tools also differ in terms of their effect when applied to a work. CC0 is legally operative in the sense that when it is applied, it changes the copyright status of the work, effectively relinquishing all copyright and related or neighboring rights worldwide. PDM is not legally operative in any respect – it is intended to function as a label, marking a work that is already free of known copyright restrictions worldwide. Learn more about [http://wiki.creativecommons.org/CC0_FAQ CC0].

====Can I use the PDM with data, such as metadata? What about databases?====

Yes, PDM can be applied to any work that is free of known copyright restrictions. This means, for example, that you can use PDM to mark [http://wiki.creativecommons.org/Metadata metadata], which is data about data, if the metadata is not copyrightable or otherwise free of copyright. For example, whether or not a photograph is still protected by copyright, metadata that describes the photograph may be unprotected by copyright. In that instance, PDM could be applied to the metadata itself.

PDM can also be applied to databases that are not protected by copyright, including databases containing metadata. The treatment of databases under copyright law varies from jurisdiction to jurisdiction, however, sometimes dramatically. Additionally, databases are also granted sui generis protection in some jurisdictions, which may limit the ability to extract and/or reuse information from the database even if the information itself in the public domain. If you are uncertain whether a database is protected by copyright around the world, then you should not mark the database itself with the PDM, but could use PDM to mark unprotected content in the database.

If you are the creator or maker of a database and want to ensure that anyone can freely extract and reuse content (subject, of course, to other rights that may apply to the contents of the database such as a photograph still under copyright), then you may wish to consider using CC0 to waive all of your copyright and sui generis database rights in the database itself. In all cases, clearly marking and labeling the works to which PDM and CC0 apply is important.

==== What about CC’s Public Domain Dedication and Certification? Can that tool still be used? ====

With the launch of the PDM, Creative Commons is officially deprecating its Public Domain Dedication and Certification (“PDDC”). CC no longer recommends the PDDC for use in any situation. The PDDC had served the dual purposes of allowing a copyright holder to dedicate a work to the public domain, and to mark and certify a work as being in the public domain. We discovered that having a single tool performing both functions was confusing, among other things. In early 2008, we published [http://creativecommons.org/about/cc0 CC0] to take on the dedication function the PDDC had been performing. We [http://creativecommons.org/weblog/entry/13304 announced] at that time that we would be working to improve the way people mark or “tag” a work with information relevant to a work’s public domain status. The PDM is that improved tool. The PDM now assumes the marking and tagging function previously served by PDDC, thereby replacing the PDDC as the recommended tool of choice for doing so.

For those who have used the PDDC to date, you can remain confident that CC will continue to support and serve the PDDC deed.

If you need to certify your public domain dedication, you may visit a service provider such as [http://www.registeredcommons.org RegisteredCommons].

=== Questions for those thinking about applying the PDM to a work ===

==== Who can apply the Public Domain Mark to a work? ====

Anyone who believes a work is free of known copyright restrictions may use the PDM. Keep in mind, however, that the PDM is recommended only for works that are free of known copyright restrictions around the world. You should not apply the PDM to works that you know are only in the public domain in a limited number of jurisdictions. We anticipate that most of the time, the PDM in its current form will only be applied to very old works.

==== If I apply the PDM to a work, am I warranting or promising that the work is free of copyright around the world? ====

No, not unless the law otherwise provides or you want to provide a separate warranty to that effect. Like all CC legal tools, the PDM deed includes express disclaimers of warranties and liabilities, to the extent those are enforceable under applicable laws. Additionally, the PDM deed puts users on notice that the work may not be free of copyright restrictions in all jurisdictions. That notice is intended to caution would-be users of the work that it can be difficult to account for all laws and all possible underlying factual circumstances that impact the copyright status of a particular work in every jurisdiction.

Notwithstanding the disclaimers and notice, if you know that a work you would like to mark is still in copyright in one or more jurisdictions, please do not apply the PDM. We are working on other means for marking works that are in the public domain in some jurisdictions while still restricted by copyright in others, and hope to publish that soon.



==== Does the PDM require those using a work I have marked to give me credit? Or the author? ====

No, there is no credit or attribution requirement, either for the person marking the work or the original author of the work. However, this does not mean that you cannot ask others to give you credit for your effort digitizing and/or marking the work in accordance with community or professional norms and standards.



=== Questions for those thinking about using a PDM-marked work ===

==== Can anyone use a work that is marked using the PDM? ====

Yes, the PDM doesn’t restrict who may use a marked work. Generally, any work free of copyright restrictions can be used for any purpose, even commercial purposes, without asking anyone’s permission first. Note, however, that the PDM deed identifies some important caveats under '''Other Information''' that all would-be users of the work should understand. Among others, it’s possible that a work marked using PDM is not free of all copyright restrictions in all jurisdictions around the world, or that other laws outside of copyright restrict how the work may be used. Read more about these possibilities and others, below.

If you are in doubt about whether or how you can use a PDM-marked work, you should consult with your legal advisor.

==== Am I really free to use a work marked with the PDM anyway I want, anywhere in the world? ====

Like all works that are labeled “free of known copyright restrictions,” “in the public domain” or similar – including works published on the Flickr Commons, museum or library websites or elsewhere – the answer is simple: “It depends.” In this one respect, PDM is no different than any other public domain marking system. That said, one of the most important advantages PDM has over other systems is that the deed alerts would-be users of a work to '''some''' of the important, potential limitations on their ability to use the work.

These potential limitations and caveats are highlighted on the PDM deed under '''Other Information'''. Users are strongly encouraged to review and understand those in advance of using a PDM-marked work (or any other work characterized as part of the public domain, for that matter).

==== Why might a free of copyright restrictions in one jurisdiction not be free of copyright restrictions everywhere? ====

Copyright laws around the world vary; there is no harmonized or standardized copyright law that all jurisdictions follow for purposes of determining when a work is no longer restricted by copyright. Additionally, circumstances causing a work to become part of the public domain under the laws of one jurisdiction may not cause a similar result under others’ laws. Thus, the identical work may be restricted by copyright in some jurisdictions while free of copyright in others.

A work may have this limited or “hybrid” public domain status for a variety of reasons. Some jurisdictions have unusually long copyright terms, which may mean that a work free from copyright restrictions most everywhere else in the world may still be protected by the copyright laws of that particular country. Sometimes a work is no longer restricted by copyright in a jurisdiction because the author or owner failed to comply with formalities such as renewal of registration or publication with notice, where those formalities apply. It could also be the case that certain categories of works are not protected by copyright by operation of law in a particular jurisdiction, but may be afforded protection under the copyright laws of other jurisdictions. This is the case, for example, with [http://www.usa.gov/copyright.shtml U.S. government works].

CC does not recommend the current version of PDM for works with are in public domain in some jurisdictions but known to be restricted by copyright in others. Even when this recommendation is followed, however, you should be aware that the possibility still exists. We choose to alert would-be users to that possibility up front, however remote it may be.

==== What practices do those who apply PDM to works use to arrive at a determination that a work is free of known copyright? ====

That will depend. CC has not established standards, expectations or even suggested practices for those choosing to apply the mark. Nor are we qualified to do so. Every institution and individual applying the mark must exercise their own judgment for marking works they wish to indicate are free of known copyright. Our hope is that those practices will be published widely and made transparent so that would-be users of PDM-marked works are able to understand the review that was undertaken. We also encourage potential users of PDM-marked works to inquire about those practices with the identifying institution or individual if they want to know more.

Unless otherwise stated to the contrary, however, the person applying the PDM to a work is not guaranteeing anything about it, including what processes or diligence they engaged in before applying the PDM to a work. Creative Commons does not verify the copyright status of works to which the Public Domain Mark has been applied.

==== Are there other laws I should be aware of that might restrict my ability to use a PDM-marked work? ====

Probably. PDM is focused exclusively on copyright law and related and [http://wiki.creativecommons.org/CC0_FAQ#What_are_neighboring_rights.3F neighboring rights]. It does not address the applicability (or inapplicability) of other laws, except to alert users that use of the work may be otherwise regulated or limited. For example, if the work contains an image or likeness of a person or their voice, privacy or [http://wiki.creativecommons.org/Faq#When_are_publicity_rights_relevant.3F publicity rights] may be implicated in some jurisdictions. Similarly, personal data protections laws could come into play depending on the nature of the work, its contents and the particular jurisdiction.

The freedom that comes with using a work in the public domain doesn’t extend to uses that may violate other applicable laws. Just as with works licensed under a CC license, you should be cognizant of other laws that may apply to your particular uses of a work.

==== Am I required to attribute the author of the work, or the person who applied the PDM to the work? ====

No, there is no legal requirement that you credit the author of the original work or the person who identified the work, only a request that you do so voluntarily if requested and the means are provided for doing so.

For purposes of author/work citation, the PDM deed provides HTML code that can be copy and pasted into a webpage to easily cite the author and the work if the person who marked the worked provided that information. We encourage you to take advantage of this copy/paste citation feature whenever possible.

==== How can I be sure that I can use the work as I would like? ====

The Public Domain Mark contains a disclaimer of warranties just like our licenses and CC0, so there is no assurance whatsoever that the work is free of all copyright restrictions in every jurisdiction around the world just because the mark is applied. You should also be aware of restrictions or limitations beyond copyright that may apply, such privacy, publicity, personal data laws and the like.

If you are in doubt, then we strongly recommend you not use the work until you have taken all the steps and precautions you feel you need to before doing so, which may include contacting the person who applied the PDM to the work and consulting legal counsel.

{{Translations
| articles = Zh-tw:PDM_常見問題
}}

Translate

2024-04-03T14:09:32Z

CCID-timidrobot:

<div style="font-size:125%; line-height:1.75em; margin-bottom:1.25em;text-align:justify;">Creative Commons would like to work with you in creating a strong voice for openness around the world. There are many Creative Commons produced or curated materials that need '''translation'''.</div>

As of January 2018, the Affiliate Network transitioned to a Global Network, where everyone - individuals and institutions - are welcome. The Creative Commons Global Network works together to realize our shared values and build relationships around the world. '''Interested in signing up?''' Become a member at [https://network.creativecommons.org/ https://network.creativecommons.org/].

You can also join the [https://creativecommons.slack.com/archives/C9LNTF002 #cc-translation] channel on on Slack, to stay informed about materials that need to be translated or to suggest new materials.

<div style="font-size:125%; line-height:1.75em; margin-bottom:1.25em;text-align:justify;">Here are some projects that you can already start working on:</div>

{| class="wikitable sortable" style="border-collapse: collapse;" border="1" cellpadding="10"
|-
! style="width: 3%; background-color:#CCCCCC;" | # || style="width: 15%; background-color:#CCCCCC;" | Item title || style="width: 5%; background-color:#CCCCCC;" | Type || style="width: 32%; background-color:#CCCCCC;" | About || style="width: 10%; background-color:#CCCCCC;" | Lang. <br /><font size="1">(click for details)</font>|| style="width: 35%; background-color:#CCCCCC;" | Localization process
|-
| 1 || [https://github.com/creativecommons/global-network-strategy Global Network Strategy] || Github project || <font size="1">As of January 2018, the Affiliate Network transitioned to a Global Network, where everyone - individuals and institutions - are welcome. This is the strategy that lays the foundation of the new structure. </font> || [[Translate/Global Network Strategy#English|EN]]<br />[[Translate/Global Network Strategy#French|FR]] || <font size="1">1. Log-in (or create an account on Github) <br /> 2. Clone or download the branch <br/> 3. Translate the files locally <br/> 4. Commit the changes to Git <br/> 5. Message the [https://creativecommons.slack.com/archives/C9LNTF002 #cc-translation] channel on on Slack after you've finished the translation</font>
|-
| 2 || [https://www.youtube.com/watch?v=U8g35rt0UmQ Meet Creative Commons] || Video || <font size="1">Short explanatory video about how the CC licenses can help creators and educators around the world.</font> || EN<br />RO || <font size="1">1. Message the [https://creativecommons.slack.com/archives/C9LNTF002 #cc-translation] channel on on Slack to announce your desire to start translating <br />2. Go to the [https://www.youtube.com/watch?v=U8g35rt0UmQ video page] <br /> 3. Click on the three dots in the bottom right corner below the video <br/> 4. Click on Add Translations <br/> 5. Translate <br/> 6. Message the [https://creativecommons.slack.com/archives/C9LNTF002 #cc-translation] channel on on Slack after you've finished the translation</font>
|-
| 3 || [https://network.creativecommons.org/ CC Network] || Website || <font size="1">Official website of the new Creative Commons Network.</font> || EN || <font size="1">Message the [https://creativecommons.slack.com/archives/C9LNTF002 #cc-translation] channel on on Slack to announce your desire to start translating</font>
|-
| 4 || [https://creativecommons.org/policies CC Policies] || Website || <font size="1">All the policies governing the new Creative Commons Network.</font> || EN || <font size="1">Message the [https://creativecommons.slack.com/archives/C9LNTF002 #cc-translation] channel on on Slack to announce your desire to start translating</font>
|-
| 5 || [https://www.youtube.com/watch?v=SP153kdtZ8k&list=PLvvb0smWcMSvMMIXXjUecvpUr2ONZBZhF ApTI Privacy Tricks] || Video || <font size="1">A series of instructional videos about simple online tools to protect your digital privacy, produced by the Association for Technology and Internet (Romania).</font> || EN<br />RO || <font size="1">1. Message the [https://creativecommons.slack.com/archives/C9LNTF002 #cc-translation] channel on on Slack to announce your desire to start translating <br />2. Go to the [https://www.youtube.com/watch?v=SP153kdtZ8k&list=PLvvb0smWcMSvMMIXXjUecvpUr2ONZBZhF video playlist page] <br /> 3. Click on the three dots in the bottom right corner below the video <br/> 4. Click on Add Translations <br/> 5. Translate <br/> 6. Message the [https://creativecommons.slack.com/archives/C9LNTF002 #cc-translation] channel on on Slack after you've finished the translation</font>
|-
| 6 || Personal Data in the Digital Age || Video || <font size="1">A series of instructional animations about digital privacy, produced by the Association for Technology and Internet (Romania).</font> || [https://www.youtube.com/watch?v=s039rWyM_-c&list=PLvvb0smWcMSthdcxoxyEgQt_IJ9fMHh3A EN]<br />[https://www.youtube.com/watch?v=vVq5gerpWEQ&list=PLvvb0smWcMSstwVPblE8ERXYL1iQ6Ti-G BG]<br />[https://www.youtube.com/watch?v=EFATJ17bd4Q&list=PLvvb0smWcMSvIUY1f8vsa7ET4pu-gi4Fv MK]<br />[https://www.youtube.com/watch?v=yjwPhNTHIhQ&list=PLvvb0smWcMSugoORtOneXq6vWBMug8EXL ES]<br />[https://www.youtube.com/watch?v=BqlANpS-4Z0&list=PLvvb0smWcMSt6W8n4snnd50e3FL1MGGWP RO] || <font size="1">1. Message the [https://creativecommons.slack.com/archives/C9LNTF002 #cc-translation] channel on on Slack to announce your desire to start translating <br />2. Go to the videos playlist page <br /> 3. Click on the three dots in the bottom right corner below the video <br/> 4. Click on Add Translations <br/> 5. Translate <br/> 6. Message the [https://creativecommons.slack.com/archives/C9LNTF002 #cc-translation] channel on on Slack after you've finished the translation</font>
|-
| 7 || [https://www.youtube.com/watch?v=A74bZ9he2AY&list=PLvvb0smWcMSt3Nbl-eBZRNQGcSetsAW-l Copyright Reform in the EU] || Video || <font size="1">A series of activist videos against the copyright reform in the European Union, produced by the Association for Technology and Internet (Romania).</font> || EN<br />RO || <font size="1">1. Message the [https://creativecommons.slack.com/archives/C9LNTF002 #cc-translation] channel on on Slack to announce your desire to start translating <br />2. Go to the [https://www.youtube.com/watch?v=A74bZ9he2AY&list=PLvvb0smWcMSt3Nbl-eBZRNQGcSetsAW-l video playlist page] <br /> 3. Click on the three dots in the bottom right corner below the video <br/> 4. Click on Add Translations <br/> 5. Translate <br/> 6. Message the [https://creativecommons.slack.com/archives/C9LNTF002 #cc-translation] channel on on Slack after you've finished the translation</font>
|-
| 8 || [https://wiki.creativecommons.org/images/6/62/Creativecommons-informational-flyer_eng.pdf Creative Commons International] || Leaflet || <font size="1">A 2-page leaflet about what are the CC licenses, who can use them etc.</font> || EN || <font size="1">1. Message the [https://creativecommons.slack.com/archives/C9LNTF002 #cc-translation] channel on on Slack to announce your desire to start translating <br />2. Download the [https://wiki.creativecommons.org/images/6/62/Creativecommons-informational-flyer_eng.pdf PDF file] and the [https://mirrors.creativecommons.org/assets/cc-info-flyer-final.zip INDD file] <br /> 3. Message the [https://creativecommons.slack.com/archives/C9LNTF002 #cc-translation] channel on on Slack after you've finished the translation</font>
|-
| 9 || [https://wiki.creativecommons.org/images/3/35/Creativecommons-what-is-creative-commons_eng.pdf Creative Commons International] || Poster || <font size="1">A poster about what are the CC licenses, who can use them etc.</font> || EN || <font size="1">1. Message the [https://creativecommons.slack.com/archives/C9LNTF002 #cc-translation] channel on on Slack to announce your desire to start translating <br />2. Download the [https://wiki.creativecommons.org/images/3/35/Creativecommons-what-is-creative-commons_eng.pdf PDF file] and the [https://wiki.creativecommons.org/images/7/7d/Cc-fullpage-promo-svg.zip SVGZ file] <br /> 3. Message the [https://creativecommons.slack.com/archives/C9LNTF002 #cc-translation] channel on on Slackg after you've finished the translation</font>
|-
| 10 || [https://wiki.creativecommons.org/images/a/a4/Creativecommons-how-to-license-poster_eng.pdf How to License] || Poster || <font size="1">A poster about the steps to be taken when licensing works under CC.</font> || EN || <font size="1">1. Message the [https://creativecommons.slack.com/archives/C9LNTF002 #cc-translation] channel on on Slack to announce your desire to start translating <br />2. Download the [https://wiki.creativecommons.org/images/a/a4/Creativecommons-how-to-license-poster_eng.pdf PDF file] <br /> 3. Message the [https://creativecommons.slack.com/archives/C9LNTF002 #cc-translation] channel on on Slack after you've finished the translation</font>
|-
| 11 || [http://creativecommons.org.au/content/licensing-flowchart.pdf Which Creative Commons License Is Right for Me?] || Poster || <font size="1">A poster about how to choose the right CC license.</font> || EN || <font size="1">1. Message the [https://creativecommons.slack.com/archives/C9LNTF002 #cc-translation] channel on on Slack to announce your desire to start translating <br />2. Download the [http://creativecommons.org.au/content/licensing-flowchart.pdf PDF file] <br /> 3. SMessage the [https://creativecommons.slack.com/archives/C9LNTF002 #cc-translation] channel on on Slack after you've finished the translation</font>
|-
| 12 || Sharing Creative Works || Comic || <font size="1">A comic book that aims to explain the basics of CC licensing as simply as possible to a general audience, including children..</font> || EN || <font size="1">1. Message the [https://creativecommons.slack.com/archives/C9LNTF002 #cc-translation] channel on on Slack to announce your desire to start translating <br />2. Download the [https://mirrors.creativecommons.org/comics/sharingcreativeworks/sharingcreativeworks.pdf PDF file] and the [https://mirrors.creativecommons.org/comics/sharingcreativeworks/sharingcreativeworks.zip ZIP package with all the source files]<br /> 3. Message the [https://creativecommons.slack.com/archives/C9LNTF002 #cc-translation] channel on on Slack after you've finished the translation</font>
|-
| 13 || [https://cases.internetfreedom.blog/ Legislative and Jurisprudential Guidelines for Internet Freedom] || Website<br/>PDF || <font size="1">First steps in understanding Freedom of Expression online and offline based on current case law from European Court of Human Rights</font> || [https://cases.internetfreedom.blog/ EN]<br/>[https://cases.internetfreedom.blog/FoE-al.html AL]<br/>[https://cases.internetfreedom.blog/FoE-am.html AM]<br/> [https://cases.internetfreedom.blog/FoE-ge.html GE]<br/>[https://cases.internetfreedom.blog/FoE-mk.html MK]<br/>[https://cases.internetfreedom.blog/FoE-ro.html RO ]<br/>[https://cases.internetfreedom.blog/FoE-ru.html RU ]<br/>[https://cases.internetfreedom.blog/FoE-sr.html SR]<br/>[https://cases.internetfreedom.blog/FoE-ua.html UA] ||<font size="1">1. Message the [https://creativecommons.slack.com/archives/C9LNTF002 #cc-translation] channel on on Slack to announce your desire to start translating <br />2. Message the [https://creativecommons.slack.com/archives/C9LNTF002 #cc-translation] channel on on Slack after you've finished the translation</font>
|-
| 14 || [https://stateof.creativecommons.org/ State of the Commons 2017] || Website || <font size="1">Report of activities for 2017 from Creative Commons</font> || [https://stateof.creativecommons.org/ EN]<br/> [https://stateof.creativecommons.org/?lang=ca CA]<br/>[https://stateof.creativecommons.org/?lang=da DA]<br/>[https://stateof.creativecommons.org/?lang=eu EU]<br/>[https://stateof.creativecommons.org/?lang=es ES]<br/>[https://stateof.creativecommons.org/?lang=id ID]<br/>[https://stateof.creativecommons.org/?lang=ja JA]<br/>[https://stateof.creativecommons.org/?lang=ko KO] <Br/>[https://stateof.creativecommons.org/?lang=sv SV] ||<font size="1">1. Send an email to jennie@creativecommons.org to announce your desire to start translating <br />2. Follow the instructions that you will receive</font>
|-
| 15 || [https://www.youtube.com/watch?v=yhHPORrnMns How to Translate CC Licenses] || Video || <font size="1">An instructional video about how to translate CC 4.0 licenses.</font> || EN<br />FR<br />RO || <font size="1">1. Go to the [https://www.youtube.com/watch?v=yhHPORrnMns Youtube page].<br />2. Click on the three dots (...) and choose Add Translations.<br />3. OR copy the video and create your own final video - [https://drive.google.com/file/d/1dvRgYaHCyyWaZu23qdazNalgTVHVOQgk/view download the sources files - iMovie project, MP4 video, graphic files, .srt files etc.].</font>
|-
| 16 || [https://ccommons.cc/what-is-cc/ What is Creative Commons] || Website || <font size="1">A timeline with the most important facts and dates about Creative Commons, created with the [https://rich-web.org/wp-event-timeline/ Wordpress Event Timeline] plugin for.</font> || EN || <font size="1">1. Go to the [https://ccommons.cc/what-is-cc/ Web page].<br />2. Message the [https://creativecommons.slack.com/archives/C9LNTF002 #cc-translation] channel on on Slack after you've finished the translation.</font>
|-
| 17 || [https://ccommons.cc/about-copyright/ About Copyright] || Website || <font size="1">A slideshow about the basic notions of copyright, created with the [https://smartslider3.com/ Smart Slider] plugin for Wordpress.</font> || EN || <font size="1">1. Go to the [https://ccommons.cc/about-copyright/ Web page].<br />2. Message the [https://creativecommons.slack.com/archives/C9LNTF002 #cc-translation] channel on on Slack after you've finished the translation.</font>
|-
| 18 || [https://prezi.com/view/lwoEhbi0Dma9dGWoBRa1/ Creative Commons - The Licenses] || Prezi || <font size="1">A presentation about the elements of the CC licenses and about the 6 licenses.</font> || EN || <font size="1">1. Go to the [https://prezi.com/view/lwoEhbi0Dma9dGWoBRa1/ Prezi Web page].<br />2. Message the [https://creativecommons.slack.com/archives/C9LNTF002 #cc-translation] channel on on Slack after you've finished the translation.</font>
|-
| 19 || [https://www.youtube.com/watch?v=Rta2AlPww8M How to Translate CC Deeds] || Video || <font size="1">An instructional video about how to translate CC deeds using Transifex.</font> || EN<br />FR<br />RO || <font size="1">1. Go to the [https://www.youtube.com/watch?v=Rta2AlPww8M Youtube page].<br />2. Click on the three dots (...) and choose Add Translations.<br />3. OR copy the video and create your own final video - [https://drive.google.com/file/d/1VI5JHWd4c0ssapE71Um6cU8OmF69QHWW/view download the sources files - iMovie project, MP4 video, graphic files, .srt files etc.].</font>
|-
| 20 || [https://www.scribd.com/document/16540395/Which-Creative-Commons-licence-is-right-for-me-poster Which Creative Commons licence is right for me?] || Poster || <font size="1">A poster about how to choose the right CC license.</font> || EN || <font size="1">1. Go to the [https://www.scribd.com/document/16540395/Which-Creative-Commons-licence-is-right-for-me-poster poster Web page].<br />2. Download the poster<br />3. Message the [https://creativecommons.slack.com/archives/C9LNTF002 #cc-translation] channel on on Slack after you've finished the translation.</font>
|-
| 21 || [https://web.law.duke.edu/musiccomic/translate/ Theft! A History of Music] || Graphic novel || <font size="1">A graphic novel about copyright in music history.</font> || [https://web.law.duke.edu/musiccomic/translate/ EN]<br /> [https://ccommons.cc/ RO] || <font size="1">1. Go to the [https://web.law.duke.edu/musiccomic/translate/ Web page].<br />2. Download the files<br />3. Message the [https://creativecommons.slack.com/archives/C9LNTF002 #cc-translation] channel on on Slack after you've finished the translation.</font>
|-
| 22 || [http://www.corintjunior.ro/coronavirus_pe_intelesul_copiilor.html Coronavirus pe înțelesul copiilor] || Brochure || <font size="1">A brochure for children about the coronavirus.</font> || RO || <font size="1">1. Download [http://download.corintjunior.ro/Coronavirus-pe-intelesul-copiilor-carti-copii-editura-corint-junior.pdf the brochure].<br />2. Contact the publishing house and ask them to send you the editable files<br /> 3. Message the [https://creativecommons.slack.com/archives/C9LNTF002 #cc-translation] channel on on Slack after you've finished the translation.</font>
|-
| 23 || [https://virallanguages.org/ Virallanguages. Coronavirus Explained in Your Language] || Website || <font size="1">Website dedicated to disseminate information about the Coronavirus in minority or endangered languages. </font> || [https://virallanguages.org/ EN]<br />[https://virallanguages.org/fr/accueil/ FR] || <font size="1">[https://virallanguages.org/how-it-works/ All the instructions are on the website.]</font>
|-
| 24 || [https://creativecommons.org/2020/04/21/academic-publications-under-no-derivatives-licenses-is-misguided/ Why Sharing Academic Publications Under “No Derivatives” Licenses is Misguided] || Blog entry || <font size="1">Article by Brigitte Vézina </font> || [https://creativecommons.org/2020/04/21/academic-publications-under-no-derivatives-licenses-is-misguided/ EN]<br />[https://scinfolex.com/2020/04/27/pourquoi-diffuser-des-travaux-de-recherche-sous-licence-pas-de-modification-nest-pas-une-bonne-idee/ FR]<br /> [https://drive.google.com/file/d/1cOLLAeleRLXJQWOozolzUhP9cHD3b7RL/view?usp=sharing RU] || <font size="1">1. Translate the article into your language.<br />2. Message the [https://creativecommons.slack.com/archives/C9LNTF002 #cc-translation] channel on on Slack</font>
|-
| 25 || [https://home.digitallibrary.io/translate/ Global Digital Library] || Children's books translation platform || <font size="1">The Global Digital Library is part of the Global Book Alliance - bringing books to every child in the world by 2030 </font> || [https://docs.google.com/spreadsheets/d/1ccLmxIQzs4WfkVSlFOQ_dtDqqY52To1VKsX-WFyVbqY/edit#gid=341319149 Various] || <font size="1">Follow the instructions on the [https://home.digitallibrary.io/translate/ website].</font>
|-
| 26 || [https://storyweaver.org.in/v0/blog_posts/438 StoryWeaver] || Children's books translation platform || <font size="1">Many languages, formats, and stories for children. All open source </font> || [https://storyweaver.org.in/v0/blog_posts/438 Various] || <font size="1">Follow the instructions on the [https://storyweaver.org.in/v0/blog_posts/438 website].</font>
|-
| 27 || [https://www.letsreadathome.org/translate Let's Read at Home] || Children's books translation platform || <font size="1">Collection of great books, reading activities, conversation starters, and coloring pages to help children keep learning, growing, and thriving while out of school </font> || [https://www.letsreadathome.org/translate Various] || <font size="1">Follow the instructions on the [https://www.letsreadathome.org/translate website].</font>
|-
| 28 || [https://translateastory.org/translate-on-the-african-storybook-website/ Translate a Story] || Children's books translation platform || <font size="1">A collaboration including Norway, UNESCO, UNHCR, ADEA, The Global Book Alliance, Verizon, The Global Digital Library, Pratham Books’ StoryWeaver, The Asia Foundation’s Let’s Read initiative, African Storybook, Learning Equality and Creative Commons </font> || [https://translateastory.org/translate-on-the-african-storybook-website/ Various] || <font size="1">Follow the instructions on the [https://translateastory.org/translate-on-the-african-storybook-website/ website].</font>
|}

<div style="font-size:125%; line-height:1.75em; margin-bottom:1.25em">Did you find an interesting CC-licensed material that deserves to be translated? Let us know on the [https://creativecommons.slack.com/archives/C9LNTF002 #cc-translation] channel on on Slack!

{{PageColumn|
===[[Translating CC Deeds|Translating CC Deeds]]===
Important materials such as the license chooser and deeds should be localized. For information on this process, see the [[Translating CC Deeds]] page.
}}
{{PageColumn|
===[[Legal Tools Translation|Licenses and Legal Tools]]===
Join projects working on translating the Creative Commons license suite and CC0 legal waiver into your local language. For information on this process, see the [[Legal Tools Translation]] page.
}}

{{Translations
| articles = de:Übersetzen, Ja:翻訳する, Pt:Tradução
}}

[[Category:i18n]]
[[Category:Translation Project]]

__NOTOC__
__NOEDITSECTION__

Translating CC Deeds

2024-04-03T14:06:28Z

CCID-timidrobot:

As of January 2018, the Affiliate Network transitioned to a Global Network, where everyone - individuals and institutions - are welcome. The Creative Commons Global Network works together to realize our shared values and build relationships around the world. '''Interested in signing up?''' Become a member at [https://network.creativecommons.org/ https://network.creativecommons.org/]. You can also join the [https://creativecommons.slack.com/archives/C9LNTF002 #cc-translation] channel on on Slack, to stay informed about materials that need to be translated or to suggest new materials.

Creative Commons uses [http://www.transifex.com Transifex] to manage translations for the website and our open source software projects. Information on translating using [[Translating PO Files|gettext and poEdit]] is also available.

To translate to the language that interests you, please follow these steps. Watch the video and read the instructions below:

[[File:How-to-translate-cc-deeds.png |link=https://www.youtube.com/watch?v=Rta2AlPww8M]]

===Sign up for an account===

1. If you were invited to join a CC translation team on Transifex, you should’ve received an email with a link to set up your account. Click on the link, then complete the signup form and click '''Create my account'''. After creating your account, you’ll be automatically taken to the page of the team that you were invited to. If you were not invited, go to http://www.transifex.com/signup/ and register for an account. You can also login using your Github, Google or LinkedIN account.

2. If asked to activate your account, check your email for the activation link and click on it.

3. On the first page of the welcome page, fill in your name and select '''Localization''' as your department and '''Translator''' as your job title. Hit '''Next''' to continue.

[[File:Transifex welcome step1.jpg|500px]]

4. The '''"Join an existing project"''' option will be pre-selected for you. Hit '''Next''' again.

[[File:Transifex welcome step2.jpg|500px]]

5. Finally, choose which languages you speak.

6. When you’re ready, click '''Get Started'''.

7. Choose '''Join an existing organization''' and search for '''Creative Commons'''. Choose '''Creative Commons - Share, Remix, Reuse — Legally''' (Organization: Creative Commons) or [https://www.transifex.com/nkinkade/CC/ visit this link].

[[File:Transifex-choose-CC.jpg|500px]]

===Join the CC teams===

1. Go to the Creative Commons project on Transifex, click '''Join team''' and choose the language you wish to translate into. The administrator will approve your request.

2. If a team already exists for the language that interests you, then click on that language and then click the '''Join team''' button, which will allow you to send a message to the coordinator for that language asking them to allow you to become a member of that team.

[[File:Transifex-teams-1.jpg|500px]]

3. If a team doesn't yet exist for the language that interests you then simply click the '''Request language''' button. This will send an email to the administrator for the Creative Commons project requesting the new team.

[[File:Transifex-teams-2.jpg|500px]]

===Start translating and/or reviewing===

# With Transifex, you can help to translate the [http://search.creativecommons.org CC Search section] of the website and the Deeds & Choosers.
# Login to Transifex and go to your language. Choose whether you want to translate CC Search or the Deeds & Choosers.
# Click on '''Translate'''.
# Go to the ''Untranslated'' tab and start translating. When you finish, click ''Save all''.
# You can also review the translations made by your team members. Click on ''Unreviewed'' and start reviewing. Don’t forget to add suggestions by clicking on the corresponding button below the translation.

=== General Notes About Translating ===

==== Using the Transifex Web editor ====

After you selected the untranslated strings, from the strings list on the left, click on the string you want to translate. Your selected string will appear on the right-hand side in the source strings box. Type your translation into the translation box below the source string box. Hit Save or you can hit Save all after you translate several strings. '''Remember:''' you only have to translate the language and preserve the formatting or other code that you may find in the original string.

A very interesting feature of Transifex is called '''Translation Memory (TM) and Concordance Search'''. If the string you're translating is similar to one that was translated in the past, a translation suggestion will appear in the Editor's Suggestions tab. The higher the percentage, the more similar the two source strings are. A 100% match means the two source strings are exactly the same. In such a case, it might be safe to reuse the translation. This is helping Creative Commons to keep the consistency of the Deeds translations.

Concordance search lets you search through the Translation Memory for a specific word or phrase and see how it was translated in other places. This is useful when there's no TM suggestion for a string, but you still want to see how something was translated elsewhere. [https://docs.transifex.com/translation/using-translation-memory-and-concordance-search Read more about this feature at Transifex.]

During the translation process, you can refer to the [https://docs.transifex.com Help section on Transifex]. You can also check any unknown words that you may encounter, in [https://docs.transifex.com/getting-started/glossary Transifex’s Glossary]. Don’t hesitate to ask the opinion of other team members

==== How to handle ${} or %() in strings ====

When you see "${license_name}" or "%(license_name)s" in a string, that indicates a substitution (for the real license name). These are placeholders that the translation machinery uses; if you modify this placeholder, the real license name will never be substituted into your string.

As a result, '''DO NOT''':

* Translate the text ("license_name") into your own language
* Remove the text
* Reverse the order of characters because you have a right-to-left language (ie, "{license_name}$")
* If the text uses the %(), do not remove the trailing character after the close of the parenthesis (i.e. the 's' in "%(license_name)s")

==== HTML links in strings (i.e., <a href="[someurl]">[sometext]</a>) ====

When you encounter an HTML link in a string, you must not translate anything inside of the angle brackets. In the example above, you would '''only''' translate ''[sometext]'', and the rest must be carried into the translation without any changes.

==== Whitespace Characters ====

Sometimes you'll see <code>\t</code> or <code>\n</code> in strings. These are left-over from the source files and can be safely omitted.

==== Wiki Links ====

Some text contains links to the CC Wiki for more information (ie, issues surrounding fair use, public domain, etc). If you would like to translate those pages in the CC Wiki, you may do so and substitute the link to the translated page in the translation. See [[CCWiki:Translate]] for instructions on translating wiki pages.

[[Category:Translation Project]]

==== When Does The Server Get Updated? ====

The live site however is updated with the newest translations every hour. However, caching may delay how soon it appears.

[[Category:Legal]]

ShareAlike compatibility analysis: Mulan

2023-12-08T15:21:35Z

CCID-timidrobot:

“Mulan Open Works License Attribution-ShareAlike, Version 1” (MulanOWL BY-SA v1, http://openworks.mulanos.cn/#/licenses/MulanOWL_BY-SA-v1) and “Mulan Open Works License Attribution-PatentLicensed-ShareAlike, Version 1” (MulanOWL BY-PL-SA v1, http://openworks.mulanos.cn/#/licenses/MulanOWL_BY-PL-SA-v1) were published in 2022. MulanOWL BY-SA v1 and MulanOWL BY-PL-SA v1 are copyright licenses with a ShareAlike mechanism and an attribution mechanism, and [http://freedomdefined.org/Licenses#Free_Art_License they do not violate the definition of Free Cultural Licenses]. Thus, it satisfies the [[ShareAlike_compatibility_process_and_criteria#Minimum_compatibility_criteria.|minimum criteria]] for compatibility set forth in our [[ShareAlike_compatibility_process_and_criteria|ShareAlike compatibility criteria]].

MulanOWL BY-PL-SA v1 grants patent rights and is not compatible with CC BY-SA 4.0.

MulanOWL BY-SA v1 is similar to CC BY-SA 4.0 overall, and the effect of each license as applied to a creative work is largely the same. Inevitably, there are differences between the licenses, which are explained in more detail below.

'''Summary of comparison: MulanOWL BY-SA v1<ref>Note that CC reviewed the English language version of the MulanOWL BY-SA v1 and MulanOWL BY-PL-SA v1 to conduct this analysis.</ref> and BY-SA 4.0'''

*It appears that the MulanOWL BY-SA v1 license referenced the CC BY-SA 4.0 license in its development. We are not sure what decisions went into the choices that made some portion of MulanOWL BY-SA v1 diverge from CC BY-SA 4.0. The steward of Mulan licenses pointed to LearnerHub as a repository for works licensed under Mulan BY-SA v1 license.

*The specific attribution and marking requirements in the two licenses vary slightly. CC BY-SA 4.0 allows for more flexibility depending on the context in which the work is used. Most notably, MulanOWL BY-SA v1 asks users to retain trademark and patent statements.

*We are particularly concerned that, unlike CC BY-SA 4.0, MulanOWL BY-SA v1 does not mention database rights, nor does it mention related rights. This could cause problems for reusers.

*The ShareAlike scope of MulanOWL BY-SA v1 is likely broader.

*MulanOWL BY-SA v1 does not terminate even upon breach, as long as the breach was cured prior to, or within 30 days of, receiving notice of termination. This may create some ambiguity, such as whether a licensor can collect damages during the period when a breach has happened but no notice is yet sent. CC BY-SA terminates automatically upon breach, but is reinstated automatically if the breach is cured within 30 days of discovery.

*

{| style="border-collapse: collapse;" border="1" cellpadding="10"
|-
! style="background-color:#CCCCCC;" | Features || style="background-color:#CCCCCC;" | BY-SA 4.0 || style="background-color:#CCCCCC;" | MulanOWL BY-SA v1
|-
| License scope || Copyright, neighboring rights and sui generis database rights (SGDRs) (Sec 1d) || Copyright only (Sec 1)
|-
| Attribution trigger || If there is applicable copyright in work, then when work or adaptation of work is shared. (Sec 3a)
<br>
If there are applicable SGDRs in work, then when all or a substantial portion of database contents is shared. (Sec 4c)
|| When work (modified or not) is disseminated (Sec 3)
|-
| Attribution removal clause || Yes (Sec 3a3) || No
|-
| Attribution elements ||
#creator and attribution parties
#copyright notice
# license notice
# disclaimer notice
# URI or link to the licensed material
# indicate and link to license
(Sec 3a1)
<br>
||
#name of licensor
#copyright statement
#license notice
#modification statements
#patent statements
# trademark statements
# disclaimer statements
# URI or link to the licensed material
# indicate and link to license
# title and version of the work (optional)
(Sec 3)
|-
| Special marking requirement if work is modified || Yes (indicate if you modified and retain indication of previous modifications) (Sec 3a1B)
|| Yes (indicate if you modified and retain indication of previous modifications) (Sec 3(3) and Sec 3(4))
|-
| ShareAlike trigger || When adaptation is shared (Sec 3b) || When adaptation is shared (Sec 3(3))
|-
| ShareAlike scope || Must ShareAlike contributions to adaptations (Sec 3b);
<br>
Must ShareAlike database if it incorporates substantial portion of database contents (Sec 4b)
|| Must ShareAlike contributions to adaptations (Sec 3(3))
|-
| Source requirement || None || None
|-
| Effective technological measures || May not be applied by licensees if they restrict access to the work or adaptations (Sec 2a5C)
<br>
Licensees have express permission to circumvent if applied by licensor (Sec 2a4)
|| May not be applied by licensees if they restrict access to the work or adaptations (Sec 3(4))
<br>
Licensees have express permission to circumvent even when applied by a third party (Sec 3(4))
|-
| Moral rights || Waived only to the extent necessary to allow the license to function. (Sec 2b1) || Not mentioned
|-
| Termination || Automatic upon breach (Sec 6a) || Terminate upon the receipt of the termination notice from the licensors, unless (1) licensee has cured all the breaches prior to receipt of such notice of termination; or,(2) it’s Licensee's first time to receive a notice of termination from the Licensor, and the licensee has cured all the breaches within 30 days of receipt of such notice; or,(3) licensor has expressly reinstated the license granted to You.(Sec 4.1)
|-
| Reinstatement after termination || Requires express permission unless cured within 30 days of discovery of violation (Sec 6b) || None
|-
| Reps & warranties || Expressly disclaimed (Sec 5) || Expressly disclaimed (Sec 5)
|-
| Choice of law || None || None
|-
| Option to comply with other license versions
|| Yes, but limited. Licensees may choose to comply with a later version of BY-SA if such version is applied to an adaptation of the work.
(Secs 2a5B, 3b1)
|| Yes, but limited. Licensees may choose to comply with a later version of MulanOWL BY-SA if such version is applied to an adaptation of the work.(Sec 3(3))
|}

== Notes ==
<references/>

ShareAlike compatibility analysis: Mulan

2023-12-08T15:21:27Z

CCID-timidrobot:

Talk:Legal Tools Translation/4.0/Estonian

2023-12-08T15:21:14Z

CCID-timidrobot:

'''Estonian 4.0'''

Public comment period: 1-21 June 2019.
Please consult the draft translation ([[Media:Draft-translation-Estonian-4-0.pdf]]) and add your comments, if any, here below. Please note that you have to have a [https://login.creativecommons.org/register.php CC ID] and you must be logged in. To add comments, click the [https://wiki.creativecommons.org/index.php?title=Talk:Legal_Tools_Translation/4.0/Estonian&action=edit Edit] tab.

Comments:

----

'''Estonian CC0'''

Public comment period: 1-21 June 2019.
Please consult the draft translation ([[Media:Draft-translation-Estonian-CC0.pdf]]) and add your comments, if any, here below. Please note that you have to have a [https://login.creativecommons.org/register.php CC ID] and you must be logged in. To add comments, click the [https://wiki.creativecommons.org/index.php?title=Talk:Legal_Tools_Translation/4.0/Estonian&action=edit Edit] tab.

Comments:

Talk:Legal Tools Translation/4.0/Estonian

2023-12-08T15:20:39Z

CCID-timidrobot:

'''Estonian 4.0'''

Public comment period: 1-21 June 2019.
Please consult the draft translation ([[Media:Draft-translation-Estonian-4-0.pdf]]) and add your comments, if any, here below. Please note that you have to have a [https://login.creativecommons.org/register.php CC ID] and you must be logged in. To add comments, click the [https://wiki.creativecommons.org/index.php?title=Talk:Legal_Tools_Translation/4.0/Estonian&action=edit Edit] tab.

Comments:
test edit

----

'''Estonian CC0'''

Public comment period: 1-21 June 2019.
Please consult the draft translation ([[Media:Draft-translation-Estonian-CC0.pdf]]) and add your comments, if any, here below. Please note that you have to have a [https://login.creativecommons.org/register.php CC ID] and you must be logged in. To add comments, click the [https://wiki.creativecommons.org/index.php?title=Talk:Legal_Tools_Translation/4.0/Estonian&action=edit Edit] tab.

Comments:

CC REL

2023-11-28T23:09:47Z

CCID-timidrobot: use "ccREL" instead of "CC REL"

{{Infobox|
'''Creative Commons Rights Expression Language (ccREL)''' is a specification describing how license information may be described using RDF and how license information may be attached to works.
|}}

ccREL is described in ''[[Media:Ccrel-1.0.pdf|ccREL: The Creative Commons Rights Expression Language]]'' (pdf), published March 3, 2008. An overview of the vocabulary is available with [http://creativecommons.org/ns# the namespace description].

ccREL metadata, as encoded using [[RDFa]] or [[XMP]], may be [[Marking Works Technical|embedded]] in a variety of [[:Category:Filetype|filetypes]]. Additional confidence may be added to embedded metadata through the use of [[WebStatement|web statement]].

We have also begun to explore extending ccREL for use by digital copyright registries. See [[CC Network Development]]'s [http://code.creativecommons.org/doc/commoner/metadata.html metadata documentation].

'''[https://opensource.creativecommons.org/ccrel-guide/ ccREL by Example]''' provides examples of many web deployment scenarios with thorough explanations and is the best place to start if you want a HOWTO or to understand through examples which you can copy and experiment with.

== Presentations ==

* A slightly updated version of the CC REL paper is chapter 10 of [http://www.communia-association.org/wp-content/uploads/the_digital_public_domain.pdf The Digital Public Domain: Foundations for an Open Culture] (pdf), 2012
* [[Creative Commons Technology Summit 2009-06-26]], multiple
* [[Creative Commons Technology Summit 2008-12-12]], multiple
* [[An Introduction to CC REL and The Use of Semantic Technology at Creative Commons]]
* [[ccREL update]]
* [[Creative Commons Technology Summit 2008-06-18]], multiple
* [[Deploying the Semantic Web with ccREL and RDFa]]
* [[COMMUNIA January 2008]]

== Examples ==

=== Simple ===
<pre>
the study by VOLKAN TEMEL is licensed under a

<a rel="license" href="http://creativecommons.org/licenses/by-nc/3.0/">Creative Commons
Attribution Non-Commercial 3.0 License</a>.
Permissions beyond the scope of this license may be available at
<a xmlns:cc="http://creativecommons.org/ns#" rel="cc:morePermissions"
href="https://www.hindawi.com/journals/arp/">Hindawi</a>.
</pre>

=== Advanced ===
<pre>
<span xmlns:cc="http://creativecommons.org/ns#" xmlns:dc="http://purl.org/dc/terms/">

<span rel="dc:type" href="http://purl.org/dc/dcmitype/Text" property="dc:title">My Book</span> by
<a rel="cc:attributionURL" property="cc:attributionName" href="http://rejon.org/my_book">Jon Phillips</a>

is licensed under a

<a rel="license" href="http://creativecommons.org/licenses/by-nc/3.0/">Creative Commons
Attribution Non-Commercial 3.0 License</a>.

<span rel="dc:source" href="http://deerfang.org/her_book"/>
Permissions beyond the scope of this license may be available at
<a rel="cc:morePermissions"
href="http://somecompany.com/revenue_sharing_agreement">somecompany.com</a>.

</span>
</pre>

{{Challenge Enabled}}

{{Translations
| articles=Pt:CC REL, Ru:CC REL
}}

[[Category:Metadata]]
[[Category:Developer]]

Developers

2023-02-10T14:24:04Z

CCID-timidrobot:

'''Join the CC Developer Community'''

Join our [http://slack-signup.creativecommons.org/ Slack] community to meet other developers interested in Creative Commons, get feedback on your projects, and talk with CC's full-time technology staff. You can also keep up with us on the [https://opensource.creativecommons.org/blog CC Open Source Blog] or via [https://twitter.com/cc_opensource Twitter].

Know more about our [https://opensource.creativecommons.org/community/ communication channels]

== Get Involved ==

We really appreciate community contributions and feedback (we're a small team and spread thin) and we especially love seeing what you build using CC's tools.

We do all of our development on GitHub and are generally open to pull requests and proposals for new community-maintained projects.
We would especially like help with reviving projects that CC's engineering team does not have the time to actively work on (such as [https://github.com/creativecommons/wp-plugin-creativecommons our WordPress plugin]). We're also looking to improve our documentation and increase our automated test coverage across pretty much all our projects, so help with that would be greatly appreciated.
Please follow [https://opensource.creativecommons.org/contributing-code/pr-guidelines our pull request guidelines] when submitting code. If you are not familiar with GitHub or pull requests, [https://guides.github.com/activities/hello-world/ here is an excellent guide to get started].

Know more about [https://opensource.creativecommons.org/contributing-code/ how to contribute on existing projects or proposing new ones]!

; Mailing list
: [mailto:cc-developers+subscribe@creativecommons.org CC Developers] or [mailto:usability-announce+subscribe@creativecommons.org CC Usability Announcements].
; Slack
: [http://slack-signup.creativecommons.org/ Sign up] and join our sub-communities for tech/developers.

== Other forms of contribution ==

; [https://opensource.creativecommons.org/programs/ Google Summer of Code]
: See CC participation on GSoC since 2006.
; [https://opensource.creativecommons.org/programs/ Outreachy]
: See CC participation on Outreachy since 2019.
; [https://wiki.creativecommons.org/wiki/Translate Translate our Content]
: Find out how to help the Creative Commons community with translations.
; [https://github.com/creativecommons/cc-vocabulary Contribute To Design]
: Contribute to our brand new set of standard UI components and help us apply it to all the existing projects.

<br clear="all"/>

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

[[Category:Developer]]

__NOTOC__

IRC

2023-02-06T14:34:25Z

CCID-timidrobot: dropping irc

'''Effective 2022-01-24 we are dropping IRC as an officially supported messaging platform:'''
* '''[https://opensource.creativecommons.org/blog/entries/2022-01-06-cc-messaging/ CC Messaging Update 2022Q1 (Dropping IRC) — Creative Commons Open Source].'''

Slack

2023-02-06T14:30:30Z

CCID-timidrobot: ensure spacing between sections is consistent

=Slack for Creative Commons=

==What is Slack==
Slack is a chat client that allows us to chat with each other and engage with our community in real time and asynchronously.

==Why Slack?==
While IRC has been a good choice in the past, Slack is more mobile friendly and integrates with the workflows of users who are using Slack for other projects, creating a more robust (and chatty) community. In addition, Slack scores high for accessibility, public familiarity, and adoption. The best news? You don’t have to give up IRC if you don’t want to! We’ve built a bridge from IRC to Slack so you can continue hanging out in #creativecommons if that’s where you feel most comfortable.

==Slack Setup==
Because Slack is a web application, there’s no installation necessary. You can login online or download the [https://slack.com/downloads/osx desktop or mobile clients.]

==How to join Slack==
1. Steps to sign up:
[https://get.slack.help/hc/en-us/articles/218080037-Getting-started-for-new-users Access the “Steps for new users”] document
Note: We got in touch with Slack and they are in the process of translating their documents, but for now it’s English only.

2. Fill out the form here - https://slack-signup.creativecommons.org/

3. Accept the email invitation that is sent to you once you fill out the form.

4. Start in the #general channel, and explore the other channels that may interest you!

==Code of Conduct==
As a global nonprofit committed to establishing inclusive community norms, all participants in the Creative Commons Slack Organization are expected to abide by our [[Slack/Code_of_Conduct]].

==How to suggest a new channel==
We create channels based on how discussions are shaped around specific topics. Any channel with fewer than 10 users and little to no discussion in 30 days will be deleted.
'''Only admins can make a channel.'''

==Channel naming conventions==
* All channels begin with "cc-"
* Channels that end with -community are community channels, designed to find other people with your specific commons interest
* Regional channels will be formatted as follows: cc-region
* Naming conventions can be modified based on community input

==Selected Channels and their uses==
* cc-africa
** For discussion of cc-africa and activities
* cc-animals
** All cuteness, all the time
* cc-announcements
** Blog posts and conversation
* cc-arab-world
* cc-colombia
* cc-comms
* cc-copyrightreform
* cc-india
* cc-nederland
* cc-openedu-goals
* cc-turkey
* cc-uk
* cc-developers
** For chat related to CC's open source development community
* cc-gsoc
** For discussions related to CC's participation in Google Summer of Code
* cc-latinamerica
** For discussion of cc-latinamerica and activities
* awesomefund
** For discussions of the CC awesome fund
* cc-announcements
** For official Creative Commons announcements. Watch this channel for news that everyone should know
* cc-europe
** For discussion of cc-europe and activities
* cc-music
** For CC musicians
* cc-openedu
** For OER and related
* cc-openglam
* cc-reads
** Creative Commons reads
* cc-summit
** For summit related discussion
* general
** For saying hello and where all new users begin
* random
** For non-CC related chatter

==Slack Tips==
* '''Everything in Slack is public''' and is therefore potentially part of the public record (written words that are attributable back to you). Don’t say something on Slack that you wouldn’t feel comfortable appearing on the news.
* '''Slack provides some [https://get.slack.help/hc/en-us/articles/202288908-How-can-I-add-formatting-to-my-messages formatting tips]''' to make your messages extra fancy.
* '''If you customize your profile''' with your location or [http://pronoun.is personal pronoun,] consider also adding those details to the Last Name field so they appear alongside your messages. This is a great way to be remote-friendly and gender inclusive. Otherwise, your colleagues need to view your profile to see that information. Many people use airport codes instead of city names to indicate their location.
* '''The advanced settings section''' provides an option for ''only showing channels that have unread messages.'' This is useful if you’re a member of a lot of channels.
* '''Click the timestamp''' on any post to go to the archival view of it. This is helpful if you’d like to cross-post a link to a message in another channel.
* '''When using Slack on mobile:''' mentioning someone in a channel they aren’t in won’t notify them, and you won’t get the option to invite someone after mentioning them
* '''Feel free to pop in and out of channels.''' You can /mute channels (so you only receive messages when your name or @channel is mentioned) or leave channels if they become overwhelming.
* '''If you’re interested in tracking specific keywords across Slack,''' set up [https://get.slack.help/hc/en-us/articles/201398467-Highlight-word-notifications highlight word notifications].
* '''To add an RSS feed to any channel''', type /feed subscribe "RSS URL"
* '''Never use Slack to share secure information.''' If you need to share short bits of text securely, use a Pastebin or other means. If you want to say something private, it’s easy to ask someone to hop on a call. (See the /slack/#shortcuts">shortcuts below.)
* '''You can use Slack as an archival system, but it's not a permanent archive.''' It has a [https://get.slack.help/hc/en-us/articles/202528808-Searching-in-Slack powerful search feature] and you can search specific channels or conversations. Content and files shared in Slack workspaces and direct messages are set up to delete after 180 days.
* '''You can also search by tagged emoji.''' To see all messages tagged with a particular emoji, search Slack for has: (for example has::cc:).
* '''Set Slack boundaries when you need to be heads-down''' by [https://get.slack.help/hc/en-us/articles/201864558-Setting-your-Slack-status setting your status] to ''Away''. If you use Slack on mobile, you can '''prevent direct messages and mentions from pinging you when you’re not working'''. Just set your phone to Do Not Disturb mode or temporarily turn off notifications from the Slack app. Don’t worry — though we have different schedules and may message each other at strange times, there’s no expectation for people to respond when they’re not working.
* '''Praise your coworkers and community!''' If you’d like to praise someone for doing good work, start a message with love @username or :heart: @username.
* '''Use text encoding when pasting a large chunk of text.</strong> Use the + sign to the left of the text box to create a snippet. There will be an option to select how you would like to encode the text; select plain text to avoid smart quotes, if you’re pasting code.</li>
* '''Emojis come in different colors.''' Tired of tabbing through multiple skin color emoji to find the one you want or identify with? Click on the Emoji Deluxe picker (the smily face in the text box) - then click on the emoji in the bottom right corner. You can then select a default color going forward.
* '''Change your color scheme.''' You can change your color scheme by going to Preferences –> Theme –> Custom Theme. Paste the following for the US Design Standards theme: #112E51,#205493,#0071BC,#FFFFFF,#323A45,#FFFFFF,#4AA564,#981B1E
* '''Screen-sharing tip:''' If you want notifications to stop showing up so people don’t see them, hover over the Notification Center icon in the top right corner of your screen and '''Option or CTRL + click''' on it. Repeat that to turn notifications back on.

==Frequently used emoji==
:check: = I did this or verified it was done

:plus: = I am a +1 for the above</p>

:100: = I am a SUPER +1 to the above OR this comment is keeping it 100 (as in, keeping it real, speaking the 100% truth)

:thumbsup: = Sounds good

:question: = I don’t understand this/needs followup

:point_up: = I would also say this (can mean “this is correct” if you are the decider)

:raised_hand: = I volunteer

:raising_hand: = Have time for a question? (Keep in mind that many folks strongly prefer that you also add what your question is about so they can determine its urgency.)

:facepalm: = Disbelief, shame, or exasperation.

:troll: = I’m intentionally [https://en.wikipedia.org/wiki/Internet_troll" trolling you or making a joke

==Shortcuts==
Type @channel [message] to send your message to everyone in the channel. Use sparingly and only if everyone in the channel needs to see your message.

Type @here [message] to send your message to everyone in the channel with Slack open at a desktop computer. Don’t use this as a softer version of an @channel because there will be no notification for anyone who wasn’t at their computer.

Type /me [message] to “emote” your message. (Just try it.)

Type /mute to suppress notifications from the channel you’re currently in. You can also turn on desktop notifications for specific channels.

Type /hangout to start a Google Hangout in the current channel.

Type [message XPOST #channel-name] to cross-post a message to a different channel while posting it.

Type /remind to remind yourself to do something in the future.

Type love @username for [message] to publicly praise and thank someone. If Charlie is in the channel, it will copy your message to #love.

Press Option + Up or Option + Down to switch between channels and direct messages.

Press Esc to mark all messages in the current channel as read.

Press Shift + Esc to mark all messages across all channels as read. Only do this if you’ve caught up in channels for your projects first.

Press Command + K or Command + T to switch between channels and direct messages by name.

Press Command + [ and Command + ] to jump back and forth along your history of DMs/channels.

To mark messages as unread, click a message on your phone and select mark unread or press Alt and then click your mouse to do so on your desktop.

==Attribution==
Portions of this text are derived from the [https://handbook.18f.gov/slack/ 18f Handbook's guide to Slack].

Slack

2023-02-06T14:29:37Z

CCID-timidrobot: remove inacurate info (including irc info). move code of conduct section up so it is more obvious

Recommended practices for attribution

2022-09-16T19:13:50Z

CCID-timidrobot: Changed protection level for "Best practices for attribution" ([Edit=⧼protect-level-staff⧽] (indefinite) [Move=⧼protect-level-staff⧽] (indefinite))

You can use CC-licensed materials as long as you follow the license conditions. One condition of all CC licenses is attribution. Here are some good (and not so good) examples of attribution. Note: If you want to learn how to mark your own material with a CC license go [[Marking_your_work_with_a_CC_license|here]].

==Examples of attribution==

Here is a photo. Following it are some examples of how people might attribute it.
:[[File:8256206923_c77e85319e_n.jpg]]
<hr>
===This is an ideal attribution===
<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">
"[http://www.flickr.com/photos/sixteenmilesofstring/8256206923/in/set-72157632200936657 Creative Commons 10th Birthday Celebration San Francisco]" by [http://www.flickr.com/photos/sixteenmilesofstring/ tvol] is licensed under [http://creativecommons.org/licenses/by/2.0/ CC BY 2.0]</div>

''Because:''
:Title? "Creative Commons 10th Birthday Celebration San Francisco"
:Author? "[http://www.flickr.com/photos/sixteenmilesofstring/ tvol]" - linked to his profile page
:Source? "[http://www.flickr.com/photos/sixteenmilesofstring/8256206923/in/set-72157632200936657 Creative Commons 10th Birthday Celebration San Francisco]" - linked to original Flickr page
:License? "[http://creativecommons.org/licenses/by/2.0/ CC BY 2.0]" - linked to license deed
<hr>

===This is a pretty good attribution===

<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">[http://www.flickr.com/photos/sixteenmilesofstring/8256206923/in/set-72157632200936657 Photo] by tvol / [http://creativecommons.org/licenses/by/2.0/ CC BY]</div>

''Because:''
:Title? Title is not noted (it should be) but at least the source is linked.
:Author? "tvol"
:Source? "[http://www.flickr.com/photos/sixteenmilesofstring/8256206923/in/set-72157632200936657 Photo]" - linked to original Flickr page
:License? "[http://creativecommons.org/licenses/by/2.0/ CC BY]" - linked to license deed
<hr>
=== This is an incorrect attribution===
<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">Photo: Creative Commons</div>

''Because:''
:Title? Title is not noted.
:Author? Creative Commons is not the author of this photo.
:Source? No link to original photo.
:License? There is no mention of the license, much less a link to the license. "Creative Commons" is an organization.
<hr>
=== This is a good attribution for material you modified slightly===
:[[File:8256206923_c77e85319e_n_desaturated.jpg]]

<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">"[http://www.flickr.com/photos/sixteenmilesofstring/8256206923/in/set-72157632200936657 Creative Commons 10th Birthday Celebration San Francisco]" by [http://www.flickr.com/photos/sixteenmilesofstring/ tvol], used under [http://creativecommons.org/licenses/by/2.0/ CC BY] / Desaturated from original</div>

''Because:''
:Title, Author, Source, and License are all noted
:Modification? "Desaturated from original"
<hr>
=== This is a good attribution for material from which you created a derivative work===

:[[File:8256206923_c77e85319e_n_90fied.jpg]]

<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">This work, "90fied", is a derivative of "[http://www.flickr.com/photos/sixteenmilesofstring/8256206923/in/set-72157632200936657 Creative Commons 10th Birthday Celebration San Francisco]" by [http://www.flickr.com/photos/sixteenmilesofstring/ tvol], used under [http://creativecommons.org/licenses/by/2.0/ CC BY]. "90fied" is licensed under [http://creativecommons.org/licenses/by/2.0/ CC BY] by [Your name here].</div>

''Because:''
:Original Title, Author, Source, and License are all noted
:Derivative? "This work, "90fied", is a derivative of..."
:New author of the derivative work is also noted

Note: If you're at a point where you are licensing derivative works, go to [[Marking your work with a CC license]].
<hr>

=== This is a good attribution for material from multiple sources ===

:[[File:Saylor_marking_example.jpg]]

''Because:''
:Title? Specific works are named, eg. "Box-and-whisker Plots"
:Author? Different authors noted for the different works.
:Source? Original materials are linked for each work
:License? The different licenses (Creative Commons Attribution for Collaborative Statistics and Creative Commons Attribution-Noncommercial-ShareAlike for the Khan Academy video) are spelled out and linked for each work
:Lastly, it is clear which attribution belongs to which work.

You can visit the [http://www.saylor.org/courses/ma121/ Saylor.org Introduction to Statistics course page] to see how they marked it up directly.
<hr>

==Title, Author, Source, License==
A good rule of thumb is to use the acronym '''TASL''', which stands for '''T'''itle, '''A'''uthor, '''S'''ource, '''L'''icense.

'''Title''' - What is the name of the material?
:If a title was provided for the material, include it. Sometimes a title is not provided; in that case, don't worry about it.

'''Author''' - Who owns the material?
:Name the author or authors of the material in question. Sometimes, the licensor may want you to give credit to some other entity, like a company or pseudonym. In rare cases, the licensor may not want to be attributed at all. In all of these cases, just do what they request.

'''Source''' - Where can I find it?
:Since you somehow accessed the material, you know where to find it. Provide the source of the material so others can, too. Since we live in the age of the Internet, this is usually a URL or hyperlink where the material resides.

'''License''' - How can I use it?
:You are obviously using the material for free thanks to the CC license, so make note of it. Don't just say the material is Creative Commons, because that says nothing about how the material can actually be used. Remember that there are six different CC licenses; which one is the material under? Name and provide a link to it, eg. http://creativecommons.org/licenses/by/4.0/ for CC BY.
:: → If the licensor included a license notice with more information, include that as well.

'''Lastly, is there anything else I should know before I use it?'''
:When you accessed the material originally did it come with any copyright notices; a notice that refers to the disclaimer of warranties; or a notice of previous modifications? (That was a mouthful!) Because that kind of legal mumbo jumbo is actually pretty important to potential users of the material. So best practice is to just retain all of that stuff by copying and pasting such notices into your attribution. Don't make it anymore complicated than it is -- just pass on any info you think is important.
:: → Regarding modifications: Don't forget to note if you modified the work yourself ([[Best_practices_for_attribution#This_is_a_good_attribution_for_material_you_modified_slightly|example]]). If you are at the point where you are creating and licensing derivative works ([[Best_practices_for_attribution#This_is_a_good_attribution_for_material_from_which_you_created_a_derivative_work|example]]), see [[Marking your work with a CC license]].

These best practices are based on actual CC license requirements. Noting the title is a requirement of all CC licenses version 3.0 or earlier, optional for 4.0. Noting the author, source, license, and retaining any extra notices is a requirement of all CC licenses. See [[Best_practices_for_attribution#Devil in the details|Devil in the details]].

===Devil in the details===
If you have any doubts or questions, you can read the complete attribution requirements which are spelled out in detail in the legal code of every CC license, eg. http://creativecommons.org/licenses/by/4.0/legalcode#s3a. This [[License_Versions#Detailed_attribution_comparison_chart|chart compares the detailed requirements across all versions of CC licenses.]]

===Don't make it too complicated===

The license tells you to be reasonable:

:''You may satisfy the conditions in (1) and (2) above in any '''reasonable manner''' based on the medium, means and context in which the Licensed Material is used. For example, it may be reasonable to satisfy some or all of the conditions by retaining a copyright notice, or by providing a URI or hyperlink associated with the Licensed Material, if the copyright notice or webpage includes some or all of the required information.''

There is no one right way; just make sure your attribution is reasonable and suited to the medium you're working with. That being said, you still have to include attribution requirements somehow, even if it's just a link to an About page that has that info. (More on different mediums [[Marking/Users#Attribution_in_specific_media|below]].)
<hr>

== Attribution in specific media ==
As stated above, best practices for attribution apply as reasonable to the medium you're working with. For media such as offline materials, video, audio, and images, consider:

:1. '''Publishing a web page with attribution information.''' For example, on a webpage featuring your audio recording, provide a credit list of material you used that adheres to best practices above. Doing so allows not only your material, but the materials you attribute, to be found by search engines and other web discovery tools. If possible within the medium, make the Author, Source, and License links the user can follow.

:<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">'''Example:'''<br>This video features the song [http://ccmixter.org/media/files/victor/6374 "Desaprendere (Treatment)"] by [http://fourstones.net/ fourstones], available under a Creative Commons [http://creativecommons.org/licenses/by-nc/2.5/ Attribution-Noncommercial] license.</div>

:2. '''Mentioning the credits within the media itself.''' For example, crediting videos can be a simple list of the materials used with their associated licenses in a screen at the end of a video. For audio, it can be a verbal recitation of credits at the end of the recording.

:<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">'''Video example 1:''' "Science Commons" by Jesse Dylan - [https://www.youtube.com/watch?v=hZAcTNFzF-s&feature=youtu.be&t=1m52s see attribution starting at 1:52]<br>'''Video example 2:''' "Video Editing and Shot Techniques: Study of jump cuts, match cuts and cutaways " video by New Media Rights - [https://www.youtube.com/watch?v=ONMSe_zhq70&feature=youtu.be&t=3m21s see attribution starting at 3:21]<br>'''Audio example:''' "Down and Out in the Magic Kingdom" by Cory Doctorow read aloud. Mastered by John Taylor Williams - [http://craphound.com/down/?p=1672 listen to attribution starting at 17:08]</div>
<hr>
== If you want to get Technical ==
If you really want to go there, we have a [[Marking_Works_Technical|document about marking materials]] so that they are machine-readable.

Also, several groups are exploring ways to make attribution easier and simultaneously machine-readable for the web. Here are some tools that have been developed:
* [http://openattribute.com/ Open Attribute] - a browser plugin for Firefox and Chrome that grabs the CC license metadata on a web page and turns it into an attribution for you
* [http://commonsmachinery.se/labs/ Commons Machinery] - a suite of plugins for Firefox and open office tools that enables copying and pasting images with the attribution info already attached
<br>
<hr>

== Other guides to attribution ==

* [http://foter.com/blog/how-to-attribute-creative-commons-photos/ How To Attribute CC Photos] poster by foter
* [http://creativecommons.org.au/materials/attribution.pdf Attributing Creative Commons Material] (pdf) - Creative Commons Australia's publication is full of examples with colorful imagery.
* [http://www.newmediarights.org/guide/how_to/creative_commons/best_practices_creative_commons_attributions How to attribute works you reuse under a Creative Commons license] by New Media Rights provides real world examples by different media type
* [https://library.fvtc.edu/Open/ExampleAttrib Library Resources] Fox Valley Technical College provides examples of suggested OER attribution and citations. They recommend the following TASL format: “Content Title” from Encompassing Container Title, Version, by Author © Copyright date [Alternate owner if different from Author] is licensed with License [URL of license description]. Access at DOI or permalink or URL. Additional Publisher notes or licensing requirements.

[[Category:Marking]]
[[Category:Licensing]]
[[Category:Community]]
[[Category:Media]]
[[Category:HOWTO]]
[[Category:Guide]]
{{Best Practice}}

CC REL

2021-09-15T16:18:37Z

CCID-timidrobot: update CC REL by Example link

{{Infobox|
'''Creative Commons Rights Expression Language (CC REL)''' is a specification describing how license information may be described using RDF and how license information may be attached to works.
|}}

CC REL is described in ''[[Media:Ccrel-1.0.pdf|CC REL: The Creative Commons Rights Expression Language]]'' (pdf), published March 3, 2008. An overview of the vocabulary is available with [http://creativecommons.org/ns# the namespace description].

CC REL metadata, as encoded using [[RDFa]] or [[XMP]], may be [[Marking Works Technical|embedded]] in a variety of [[:Category:Filetype|filetypes]]. Additional confidence may be added to embedded metadata through the use of [[WebStatement|web statement]].

We have also begun to explore extending CC REL for use by digital copyright registries. See [[CC Network Development]]'s [http://code.creativecommons.org/doc/commoner/metadata.html metadata documentation].

'''[https://opensource.creativecommons.org/ccrel-guide/ CC REL by Example]''' provides examples of many web deployment scenarios with thorough explanations and is the best place to start if you want a HOWTO or to understand through examples which you can copy and experiment with.

== Presentations ==

* A slightly updated version of the CC REL paper is chapter 10 of [http://www.communia-association.org/wp-content/uploads/the_digital_public_domain.pdf The Digital Public Domain: Foundations for an Open Culture] (pdf), 2012
* [[Creative Commons Technology Summit 2009-06-26]], multiple
* [[Creative Commons Technology Summit 2008-12-12]], multiple
* [[An Introduction to CC REL and The Use of Semantic Technology at Creative Commons]]
* [[CC REL update]]
* [[Creative Commons Technology Summit 2008-06-18]], multiple
* [[Deploying the Semantic Web with ccREL and RDFa]]
* [[COMMUNIA January 2008]]

== Examples ==

=== Simple ===
<pre>
the study by VOLKAN TEMEL is licensed under a

<a rel="license" href="http://creativecommons.org/licenses/by-nc/3.0/">Creative Commons
Attribution Non-Commercial 3.0 License</a>.
Permissions beyond the scope of this license may be available at
<a xmlns:cc="http://creativecommons.org/ns#" rel="cc:morePermissions"
href="https://www.hindawi.com/journals/arp/">Hindawi</a>.
</pre>

=== Advanced ===
<pre>
<span xmlns:cc="http://creativecommons.org/ns#" xmlns:dc="http://purl.org/dc/terms/">

<span rel="dc:type" href="http://purl.org/dc/dcmitype/Text" property="dc:title">My Book</span> by
<a rel="cc:attributionURL" property="cc:attributionName" href="http://rejon.org/my_book">Jon Phillips</a>

is licensed under a

<a rel="license" href="http://creativecommons.org/licenses/by-nc/3.0/">Creative Commons
Attribution Non-Commercial 3.0 License</a>.

<span rel="dc:source" href="http://deerfang.org/her_book"/>
Permissions beyond the scope of this license may be available at
<a rel="cc:morePermissions"
href="http://somecompany.com/revenue_sharing_agreement">somecompany.com</a>.

</span>
</pre>

{{Challenge Enabled}}

{{Translations
| articles=Pt:CC REL, Ru:CC REL
}}

[[Category:Metadata]]
[[Category:Developer]]

Legal Code Translation Policy

2020-10-14T18:16:33Z

CCID-timidrobot: remove outdated link

Creative Commons has established the following Official Legal Code Translation Process and Policy (“Legal Code Translation Policy”) to facilitate adoption and understanding of our licenses as tools for sharing creative works and data. This Legal Code Translation Policy was established as of 2013 October 29 and is updated and revised by Creative Commons in its discretion. Any non-trivial revisions will be logged and dated at the bottom of this page.

'''Watch this explanatory video:'''

[[File:How-to-translate-licenses.png |link=https://www.youtube.com/watch?v=yhHPORrnMns]]

==Overview==
The legal code for the international Creative Commons licenses and for CC0 is designed for use worldwide, without any need for adaptation to local laws. For these tools to reach their fullest potential, CC encourages linguistic translations of the legal codes and deeds into as many languages as possible. This page describes the policy and process for developing official translations of Creative Commons legal code.

The process for developing new translations (each is called a “translation project”) is coordinated and overseen by CC’s legal team in collaboration with the global network team. Creative Commons reserves the exclusive right to approve and host official translations of its legal tools, as well as to modify this process and adjust translation projects at any time. Per our policy, each official translation is hosted at a specified uniform resource indicator on CC’s website. The English original and the official translations will all be treated as equivalents. Translations of CC licenses that are not made in accordance with this policy are unauthorized modifications of our licenses per the [[Modifying_the_CC_licenses#License_Modification_Policy|License Modification Policy]].

==Translation process==
===Step 1. Beginning new translation projects.===
Anyone may initiate a translation project with CC. To express interest, please email legal [at] creativecommons [dot] org identifying the language you would like to coordinate.

Note that CC’s policy is to publish a single, official translation for any given language unless an important reason exists to allow more than one. This mirrors CC’s policy for translations of deeds. Anyone wanting to coordinate translation projects is expected to accommodate and encourage participation of others in the CC community, including from other jurisdictions where the language is spoken. CC will help coordinate this collaboration.

Once a new translation project is begun, CC will update its [[Legal_Tools_Translation|public tracking chart]] and create and populate a language-specific translation page for public tracking, which will be continually updated by CC throughout the translation process.

===Step 2. Preparing the translation draft.===
Please refer to the [[Legal_tools_translation_guide|legal tools translation guide]] while creating your translation because it contains information about common issues that arise when translating the text of the licenses and CC0. When translating the 4.0 license suite, please begin with BY-NC-SA using the worksheet [[Legal_Code_Translation_Policy#Supporting_documents|here]]. Typically, teams begin only with BY-NC-SA and defer creating the other five licenses until after the public comment period. If you are translating CC0, use this [[Legal_Code_Translation_Policy#Supporting_documents|worksheet]].

Once the draft is complete, the translation team should send it to legal[at]creativecommons[dot]org, along with a writeup of the following:
*Explanation of word choice for the following terms:
**For version 4.0:
***Adapted Material
***Copyright and Similar Rights
***Downstream recipients
***Licensed Material
***Share
***ShareAlike
**For CC0:
***Copyright and Related Rights
***Affirmer
***Work
***License
***Waiver
*Description of which concepts were challenging to translate and how decisions were made
*Explanation of variations compared to terminology used on deed translation
*Explanation of variations compared to terminology used in ports of same language
*Names of translators

CC Legal will use this explanation during their Step 3 review, and will add it to language wiki page as part of public documentation of translation process.

===Step 3. Review of draft.===
CC Legal will conduct a review of the draft translation using the following checklist:
#Use Google Translate to read through from top to bottom, looking for glaring errors like commercial uses allowed in NC license, for example.
#Use Google Translate to ensure there are no references to specific local legislation.
#Check that numbering and ordering of sections matches the English.
#Check that cross-references within text are correct.
#Make sure each defined term is in the same order as the English, and uses same capitalization throughout document.
#Go through relevant issues list, checking draft on each point using Google Translate and asking questions of team as needed: 4.0 issues list [[Legal_tools_translation_guide#4.0_license_suite_issues|here]], CC0 issues list [[Legal_tools_translation_guide#CC0_issues|here]]
#Check draft license translation against translations of deed to see if any notable changes in terminology. If yes, ask team for more information.

CC Legal will correspond with the translation team to clarify questions and make changes until a final draft translation is completed. Note that this step will reveal whether there are updates needed for the deed translations. The translation team is responsible for ensuring that the deed is fully translated. For help translating the deeds, see the instructions [[Translating_CC_Deeds|here]].

===Step 4. Public comment period.===
The public comment period is designed to ensure the highest quality linguistic translations possible. The translation team posts the draft on the CC wiki and in appropriate channels for public comment and feedback for a reasonable period of time (typically about 30-45 days, but may be shortened or extended if circumstances warrant). We encourage teams to seek as much input as possible, including by reaching out directly to local experts where possible.

At the conclusion of the public comment period, the translation team sends CC Legal a written summary of input received and how issues were resolved, along with the revised translation. CC Legal reviews the public comment summary from the translation team and asks questions as needed.

===Step 5. Creating the rest of the license suite.===
Note that this step only applies to translation of the version 4.0 CC license suite. Once all open issues are resolved with CC Legal after public comment, the translation team should create the other 5 licenses in the suite. For help in this process, refer to this [https://wiki.creativecommons.org/images/d/d1/Building_the_4.0_Suite.pdf guide]. Please consult CC Legal if you have any questions about word choices or anything else when creating the rest of the suite.

===Step 6. Readying files for staging server.===
At this point, the team converts the file(s) to HTML and sends the HTML file(s) to legal [at] creativecommons [dot] org. CC puts the file(s) on the staging server and sends the link(s) to the translation team.

''NOTE: To create the HTML files, we recommend using the English legal code pages - [https://creativecommons.org/licenses/by/4.0/legalcode https://creativecommons.org/licenses/by/4.0/legalcode] et. al. - as templates for your own. You can access the HTML page for each license in Github, where the files are stored with comments.

*BY-NC-SA is [https://github.com/creativecommons/creativecommons.org/blob/master/docroot/legalcode/by-nc-sa_4.0.html here]
*BY is [https://github.com/creativecommons/creativecommons.org/blob/master/docroot/legalcode/by_4.0.html here]
*BY-SA is [https://github.com/creativecommons/creativecommons.org/blob/master/docroot/legalcode/by-sa_4.0.html here]
*BY-NC-ND is [https://github.com/creativecommons/creativecommons.org/blob/master/docroot/legalcode/by-nc-nd_4.0.html here]
*BY-NC is [https://github.com/creativecommons/creativecommons.org/blob/master/docroot/legalcode/by-nc_4.0.html here]
*BY-ND is [https://github.com/creativecommons/creativecommons.org/blob/master/docroot/legalcode/by-nd_4.0.html here]
*CC0 is [https://github.com/creativecommons/creativecommons.org/blob/master/docroot/legalcode/zero_1.0.html here]

Copy and paste the appropriate license text into a file using a text editor or HTML editor. Then, copy and paste your appropriate translation text over the English text, being careful not to copy over the existing HTML tags, and re-check the code to ensure that there are no mistakes. Please ensure that all the XHTML files are saved using UTF-8 encoding, which generally will be the default. Then save each file separately according to the following convention:''
*''CC0'':
** ''zero_1.0_[language code].html''

''(For example, "zero_1.0_fr.html" would be the naming for the French translation.)''

*''4.0''
**''by_4.0_[language code].html''
**''by-sa_4.0_[language code].html''
**'' [...]''

===Step 7. Final review.===

The translation team and CC Legal conduct a final review of all files on the staging server. This review should involve a check of both the substance and formatting of the files.

During this final review, CC Legal will use the following checklist:
#Use Google Translate to read through from top to bottom, looking for glaring errors like commercial uses allowed in NC license, for example. [Note: in the case of 4.0, this may be the first time the translations of licenses other than BY-NC-SA have been reviewed, so pay special attention to the changes made to those files.]
#Pay special attention to the license titles - are they correct and consistent throughout each file? Compare to titles on license deeds.
#Check that formatting appears correct as compared to English (same number of provisions, identical section numbering, bold font)
#Check that language list contains all published translations, including English
#Check all links in the files
#Check that deeds are fully translated
#For version 4.0, cut and paste each file into a Word doc and run the following comparisons:
#*BY-NC-SA to BY; compare to [https://wiki.creativecommons.org/images/c/c4/Making_BY_%28comparison%29.pdf this]
#*BY-NC-SA to BY-SA; compare to [https://wiki.creativecommons.org/images/6/64/Making_BY-SA_%28comparison%29.pdf this]
#*BY-NC-SA to BY-NC; compare to [https://wiki.creativecommons.org/images/6/6f/Making_BY-NC_%28comparison%29.pdf this]
#*BY-NC-SA to BY-ND; compare to [https://wiki.creativecommons.org/images/a/a2/Making_BY-ND_%28comparison%29.pdf this]
#*BY-NC-SA to BY-NC-ND; compare to [https://wiki.creativecommons.org/images/7/70/Making_BY-NC-ND_%28comparison%29.pdf this]

This stage continues until all identified problems are resolved.

===Step 8. General Counsel sign-off.===
Once the translation team and CC have signed off on all files, CC Legal sends the file(s) to General Counsel for final sign-off. CC Legal will coordinate details for blog post announcement with translation team at this point.

===Step 9. Pull request submitted.===
Once the General Counsel signs off, CC Legal submits a pull request on Github for the CC tech team with details about how language should be listed in the language lists on the footer of other published translations.

===Step 10. Publication.===
Once the pull request is merged by the tech team, CC will alert the translation team and publish announcement on the CC blog and social media. CC Legal will update wiki tracking sheet with publication dates. Translation team should update Transifex so that deeds link to published translation rather than English legal code.

==Key Resources==
* [[Legal tools translation guide]]
* [[Media:Building_the_4.0_Suite.pdf|Building the 4.0 Suite (.pdf)]]
* [[Media:Making_BY_(comparison).pdf|Making the BY license (comparison) (.pdf)]]
* [[Media:Making_BY-SA_(comparison).pdf|Making the BY-SA license (comparison) (.pdf)]]
* [[Media:Making_BY-NC_(comparison).pdf|Making the BY-NC license (comparison) (.pdf)]]
* [[Media:Making_BY-ND_(comparison).pdf|Making the BY-ND license (comparison) (.pdf)]]
* [[Media:Making_BY-NC-ND_(comparison).pdf|Making the BY-NC-ND license (comparison) (.pdf)]]
* 4.0 translation worksheet: [https://docs.google.com/document/d/1Vq6b89z6HWP1KZ66FNvx9E1GTeyAguPKk_zb4jXg4u8/ Google Doc], [[Media:4.0_translation_worksheet_(BY-NC-SA)(Feb_2015).odt|.odt]], [[Media:4.0_translation_worksheet_(BY-NC-SA)(Feb_2015).docx|.docx]], [[Media:4.0_translation_worksheet_(BY-NC-SA)(Feb_2015).pdf|.pdf]] (updated 2016 November 23)
* CC0 translation worksheet: [https://docs.google.com/document/d/12bmP4guaewK2U0eGQIFd-2N5XVlpB1rGULfxHthhODA/ Google Doc], [[Media:CC0_translation_worksheet.odt|.odt]], [[Media:CC0_translation_worksheet.docx|.docx]], [[Media:CC0_translation_worksheet.pdf|.pdf]] (updated 2016 November 23)

==Changelog==
* 2019 September 17: Moved formatting check to Step 7 since that is when bold and other formatting is added; changed instructions for converting to HTML
* 2019 September 3: Revised process to better reflect current practice in terms of who and how translations are initiated, and added far more detail about different steps in the process.
* 2018 May 26: As of January 2018, the Affiliate Network transitioned to a Global Network, where everyone - individuals and institutions - are welcome. This policy reflects the new structure.
* 2017 March 14: Moved "Creating the files" from [[Legal tools translation guide]] to this page
* 2016 November 21: Removed the obligation to send the translation proposal using the forms
* 2016 November 4: Added detailed new steps to the translation process
* 2015 April 17: Clarification that unofficial translations violate License Modification Policy
* 2015 February 4: Change in supplemental material requirements, added CC0 translation worksheet
* 2014 February 4: Additional supplemental material requirements, new version of internal checklist posted
* 2014 January 24: More detailed summary.
* 2013 October 29: Policy established.

[[Category:Translation Project]]

License Properties

2020-05-27T15:40:33Z

CCID-timidrobot: Updated URLs to use HTTPS, where appropropriate

In addition to the human readable license deeds and legal code, Creative Commons provides machine readable metadata for licenses. This page describes how to begin with a license URI and map it to license properties.

License Properties describe the permissions, prohibitions and requirements of a license. Permissions declare a permission given by the license, above and beyond what default copyright law allows. Prohibitions prohibit a particular use of the work, specifically affecting the scope of the permissions provided by a permission. Requirements describe actions required of user when making use of the permissions.

There are two ways to discover license properties given a license URI:
* The "dumb" and easy way: [[#Inspecting the URL|Inspect the URL]]. This can be done with regular expressions or even simple string searching, but requires your code to bake in a little knowledge about CC license URI conventions, and will not work with possible future license URIs that do not follow these conventions (e.g., non-CC licenses that use CC style metadata). But this downside should be of little concern if all you want to do is discover CC licensed material and be able to remember and filter on high level properties such as whether commercial use or derviative works are prohibited.
* The smart and hard way: [[#Using RDFa|Use RDFa]]. This allows you to discover properties for any license URI, including properties that may not be encoded in URI conventions. However, use of this method requires your code to use a RDFa parser.

= Inspecting the URL =

Creative Commons license deed URLs, for version 4.0, have the following format:

https://creativecommons.org/licenses/{license-properties}/{version}/

Creative Commons license deed URLs, prior to version 4.0, have the following format:

https://creativecommons.org/licenses/{license-properties}/{version}/{jurisdiction}/

The jurisdiction is optional. For example:

https://creativecommons.org/licenses/by/3.0/

Is the URL for the Attribution 3.0 (Unported) license. The license is Unported as there is no jurisdiction element present. The Attribution 2.0 (France) license has the following URL:

https://creativecommons.org/licenses/by/2.0/fr/

=== Mapping Individual Properties ===

The license properties portion of the URL is a sequence a letter codes separated by dashes ("-"). These map to the following license properties:

* '''by''': Attribution: Attribution is required with any reuse or redistribution, in the manner specified by the licensor.
* '''nc''': [[NC|Non-Commercial]]: Commercial use is prohibited.
* '''nd''': No Derivatives: Only verbatim reproduction is permitted.
* '''sa''': Share-Alike: Derivative works are allowed, but must also be licensed under the same license.

=== Sample Code ===

<pre><nowiki>
"""extract_simple.py

Command line sample to map a Creative Commons license URI to the properties
it describes. See http://wiki.creativecommons.org/License_Properties for
details.

Example usage:

$ python extract_simple.py https://creativecommons.org/licenses/by/3.0/
Attribution

$ python extract_simply.py https://creativecommons.org/licenses/by-nc/3.0/
Attribution
Non-Commercial

"""

import sys
import urlparse

ATTRIBUTES = dict(
by = 'Attribution',
nc = 'Non-Commercial',
nd = 'No Derivatives',
sa = 'Share-Alike',
)

def parse(url):
"""Return a sequence of attributes for the given license URL."""

# get the path portion of the URL
path = urlparse.urlparse(url)[2]

# extract the license code portion
pieces = path.split('/')
assert(pieces[1] == 'licenses')

# split the individual codes
attribute_codes = pieces[2].split('-')

return [ATTRIBUTES[n] for n in attribute_codes]

if __name__ == '__main__':

print "\n".join(
parse(sys.argv[-1])
)
</nowiki></pre>

=== Special Cases ===

==== Public Domain ====

https://creativecommons.org/licenses/publicdomain/

For this URI, all of the properties above are false, but obviously the (implicit) properties of permitting distribution and derivative works are true.

==== Sampling (retired) ====

The [http://creativecommons.org/license/sampling Sampling Licenses] define specific permissions with respect to sampling a work. The license URLs are

https://creativecommons.org/licenses/sampling/1.0/ (retired)
https://creativecommons.org/licenses/sampling+/1.0/ (retired)
https://creativecommons.org/licenses/nc-sampling+/1.0/ (retired)

Many simple implementations may ignore these.

==== Source Code Licenses ====

Creative Commons provides metadata "wrappers" for some source code licenses. These URLs are:

https://creativecommons.org/licenses/MIT/
https://creativecommons.org/licenses/BSD/
https://creativecommons.org/licenses/GPL/2.0/
https://creativecommons.org/licenses/LGPL/2.1/

= Using RDFa =

[[RDFa]] is an editor's draft at W3 which describes a way to serialize [http://www.w3.org/RDF/ RDF] triples in HTML. Creative Commons includes the appropriate RDFa When selecting a license from http://creativecommons.org/license to indicate that a page is licensed. For example:

<a href="http://creativecommons.org/licenses/by/3.0/" '''rel="license"'''>Attribution 3.0</a>

The <code>rel="license"</code> attribute indicates that the link specified (the license URL in this case) has special semantic meaning.

With the license URI, an RDFa parser may be used to extract license attributes from the human readable deed. RDFa parsers are available for many languages, including Python ([[RdfaDict]], [http://rdflib.net rdflib]), Ruby ([http://code.google.com/p/ruby-rdfa/ ruby-rdfa]) and PHP ([http://www.avthasselt.sohosted.com/rdfamonkey/ RDFa Monkey]).

Passing the Attribution 3.0 Unported deed (http://creativecommons.org/licenses/by/3.0/) through an RDFa parser yields the following [http://www.w3.org/TR/rdf-concepts/#section-triples triples]:

@prefix cc: <http://creativecommons.org/ns#> .
http://creativecommons.org/licenses/by/3.0/ cc:requires cc:Attribution .
http://creativecommons.org/licenses/by/3.0/ cc:requires cc:Notice .
http://creativecommons.org/licenses/by/3.0/ cc:permits cc:Reproduction .
http://creativecommons.org/licenses/by/3.0/ cc:permits cc:Distribution .
http://creativecommons.org/licenses/by/3.0/ cc:permits cc:DerivativeWorks .

For a complete list of Permissions, Prohibitions and Requirements defined by Creative Commons see http://creativecommons.org/ns.

== Sample Code ==

The following sample code uses [[RdfaDict]] to parse the license deed and prints the URIs for the license permissions, prohibitions and requirements.

<pre><nowiki>
"""extract_rdfa.py

Command line sample to map a Creative Commons license URI to the properties
it describes. See http://wiki.creativecommons.org/License_Properties for
details.

Example usage:

$ python extract_rdfa.py http://creativecommons.org/licenses/by/3.0/
http://creativecommons.org/ns#Attribution
http://creativecommons.org/ns#Notice
http://creativecommons.org/ns#Reproduction
http://creativecommons.org/ns#Distribution
http://creativecommons.org/ns#DerivativeWorks

$ python extract_rdfa.py http://creativecommons.org/licenses/by-nc/3.0/
http://creativecommons.org/ns#Attribution
http://creativecommons.org/ns#Notice
http://creativecommons.org/ns#CommercialUse
http://creativecommons.org/ns#Reproduction
http://creativecommons.org/ns#Distribution
http://creativecommons.org/ns#DerivativeWorks

Requires rdfadict (http://python.org/pypi/rdfadict).
"""

import sys
import rdfadict

def parse(url):
"""Return a sequence of attributes for the given license URL."""

# parse the license deed and extract RDFa
rdf = rdfadict.RdfaParser().parseurl(url)

# return all predicates (merging requirements, prohibitions and permissions)
result = []
for predicate in rdf[url]:
for obj in rdf[url][predicate]:
result.append(obj)

return result

if __name__ == '__main__':

print "\n".join(
parse(sys.argv[-1])
)
</nowiki></pre>

[[Category:Developer]]
[[Category:Metadata]]

Legalcode errata

2019-12-03T20:59:41Z

CCID-timidrobot:

Despite our best efforts, spelling errors and other errata are sometimes included in the published legal code for licenses. However, Creative Commons does not amend legal code once published so that the licenses remain static, and not a moving target. This wiki page collects known errata for license legal code. If you discover a spelling error on a license, please send a message to legal@creativecommons.org.

=Errors by license=

==4.0 international license suite (English)==
===Validated HTML===
As originally published, the HTML for the license files did not validate. This was corrected; however, those with older copies of this file will have the incorrect file.

===Italics===
On 2019 September 24, we discovered that Section 2a5 of the 4.0 licenses had become italicized through unknown means. It was investigated and reversed back to its original formatting on 2019 November 12.

==3.0 Unported (International) license suite==
===Section 1===
* '''Incorrect section reference.''' Section 1(b) of BY-SA cites Section 1(f); it should cite Section 1(h).
** BY-SA 1(b)
* '''Incorrect word.''' Section 1(b) of BY-SA says that Adaptation is defined "below"; this should read "above".
** BY-SA 1(b)
===Section 2===
===Section 3===
* '''Inconsistent language'''. In Section 3(d), BY-SA uses "described" instead of "set forth".
** BY-NC-SA 3(d)
* '''Section 8(f) reference incorrect; missing word.''' These sections include a reference to Section 8(f); they should instead refer to Section 8(e). Additionally, BY-NC-ND omits the word "Section", which should be present.
** BY-ND 3(c)(iii), BY-NC-ND 3(b).

===Section 4===
* '''Incorrect reference to "the Applicable License".''' In section 4(b), a reference to "the Applicable License" should instead be to "this License": "You must keep intact all notices that refer to the Applicable License and to the disclaimer of warranties" should read "You must keep intact all notices that refer to this License and to the disclaimer of warranties".
**BY-SA 4(b), BY-NC-SA 4(b)
* '''Missing "the".''' In section 4(b) of BY-NC-SA, there is a sentence reading in part "must include a copy of, or the URI, for Applicable License with every copy". This excerpt should instead read "must include a copy of, or the URI for, the Applicable License with every copy".
**BY-NC-SA 4(b)
* '''Missing "the".''' In Section 4(b) of BY-NC-ND, "if a credit for all contributing authors of Collection appears" should read "if a credit for all contributing authors of the Collection appears".
**BY-NC-ND, 4(b)
* '''Missing numerals and capitalization.''' In section 4(b) of BY-NC-SA, each condition should be numbered with uppercase roman numerals. Additionally, the beginning of item (IV) should be capitalized. (The passage should read: "(I) You must include a copy of[...]"; "(II) You may not offer[...]"; "(III) You must keep intact[...]"; "(IV) When You Distribute[...]")
**BY-NC-SA 4(b)
* '''Numbering of list items.''' In Section 4(b) of BY-NC-SA, "only under: (i) the terms of this License" should instead read "only under the terms of: (i) this License".
** BY-NC-SA 4(b)
* '''Capitalization.''' "Collection" should be lowercase both times in the last sentence of Section 4(b) in BY-SA; the excerpts should read "as incorporated in a collection" and "does not require the collection apart from the Adaptation itself".
** BY-SA 4(b)
* '''Comma placement.''' In the BY-NC and BY-NC-SA licenses, a comma is incorrectly placed. The text reading "and, (iv) consistent with Section 3(b)" should instead read "and (iv), consistent with Section 3(b)".
** BY-NC 4(c), BY-NC-SA 4(d).
* '''Extra hyphen.''' In Section 4(c) of BY-NC-SA, "con-nection" is an error, and should be written as "connection" instead.
** BY-NC-SA 4(c)
* '''Typographical error: "Ssection".''' In Section 4(c), BY-SA contains the text "consistent with Ssection 3(b)"; "Ssection" should be "Section".
** BY-SA 4(c).
* '''Incorrect subsection reference.''' Section 4(d)(iii) of BY-NC references 4(c). It should reference 4(b).
** BY-NC 4(d)(iii)
* '''Typographical error.''' In Section 4, several licenses refer to "a Adaptation"; this should be "an Adaptation".
** BY 4(b), BY-NC, BY-SA 4(c), BY-NC-SA 4(d)

=== Section 5 ===
* '''Omitted phrase.''' The phrase "And to the Fullest Extent Permitted by Applicable Law," should appear before "Licensor Offers the Work As-Is and Makes No Representations".
** BY, BY-SA, BY-NC, BY-ND, BY-NC-ND
* '''Omitted word ("to").''' In BY-NC-ND, "Unless Otherwise Mutually Agreed By the Parties" should read "Unless Otherwise Mutually Agreed To By the Parties".
** BY-NC-ND
* '''Spelling.''' "Merchantability" is misspelled as "Merchantibility" in five licenses.
** BY, BY-NC, BY-SA, BY-ND, BY-NC-ND.
* '''Inconsistent language.''' BY-NC-SA includes the text "This Exclusion May Not Apply To You"; it should read "Such Exclusion May Not Apply To You".
** BY-NC-SA
* '''Typographical error.''' Section 5 contains the text "OR THE PRESENCE OF ABSENCE OF ERRORS". This should read "OR THE PRESENCE OF ERRORS".
** All six licenses.

=== Notice ===
* '''Incorrect word.''' In the last paragraph, "this trademark restriction does not form part of the License" should read "this trademark restriction does not form part of this License".

==3.0 jurisdiction ports==
===Australia===
*'''Incorrect header color. ''' The heading for BY-NC-SA is green, and should be yellow.
** BY-NC-SA

===Czech Republic===
*'''Typographical error.''' In the 2nd sentence of the final section ("Upozornění Creative Commons"), "Commos" should be "Commons".
** All six licenses.

===Ecuador===
*'''Incorrect header color.''' The headings for these four licenses are green, and should be yellow.
** BY-NC, BY-NC-ND, BY-NC-SA, BY-ND

===Germany===
*'''Incorrect word.''' In Section 8(e), the word "angeboteten" should be "angebotenen".
** BY-SA, BY-NC-SA, BY-NC, BY-ND, BY-NC-ND

===Greece===
* '''Incorrect header color.''' The headings for these licenses are yellow, and should be green.
** BY, BY-SA
*'''Incorrect example.''' In section 3(β) of BY-SA, the example given is "Attribution—NonCommercial—ShareAlike 3 U.S."; it should be "Attribution—ShareAlike 3 U.S."
** BY-SA 3(β)
* '''Compatibility.''' In section 4(β), BY-NC-SA is erroneously listed as an example compatible port with BY-SA.
** BY-SA 4(β)

''There are likely to be more errors in Section 4(β) of BY-SA and BY-NC-SA; a Greek speaker is needed to report further errata.'''

===Guatemala===
* '''Incorrect header color.''' The headings for these licenses are green, and should be yellow.
** BY-NC, BY-NC-ND, BY-NC-SA, BY-ND

===Hong Kong===
* '''Incorrect example.''' The example given in Section 4(b) "(e.g., Attribution-ShareAlike 3.0 Hong Kong)" should instead be any ported BY-SA license other than Hong Kong.
** BY-SA, BY-NC-SA 4(b)
* '''Incorrect reference to "the applicable license".''' In section 4(b), a reference to "the applicable license" should instead be to "this license".
** BY-SA, BY-NC-SA 4(b)
* '''Missing numerals and capitalization.''' In section 4(b) of BY-NC-SA, each condition should be numbered with uppercase roman numerals. Additionally, the beginning of item (IV) should be capitalized. (The passage should read: "(I) You must include a copy of[...]"; "(II) You may not offer[...]"; "(III) You must keep intact[...]"; "(IV) When You Distribute[...]")
**BY-NC-SA 4(b)

===IGO===
* '''Incorrect word in the original English (to be corrected in official translations).''' In the definition of "Publicly Perform", the phrase "from a place and at a place" should read "from a place and at a time".
** BY, BY-NC, BY-ND, and BY-NC-ND: 1(g); BY-SA, BY-NC-SA: 1(h)

===Ireland===
* '''Incorrect reference to "the Applicable License".''' In section 4(b), a reference to "the Applicable License" should instead be to "this License". "You must keep intact all notices that refer to the Applicable License and to the disclaimer of warranties" should read "You must keep intact all notices that refer to this License and to the disclaimer of warranties".
* BY-SA 4(b), BY-NC-SA 4(b)

===Luxembourg===
* '''Incorrect header color.''' The headings for these licenses are green, and should be yellow.
** BY-NC, BY-NC-ND, BY-NC-SA, BY-ND

===Netherlands===
* '''Spelling.''' In the last sentence of section 3, the word "beschikt" is misspelled as "beschickt".
** All six licenses.

===New Zealand===
* '''Compatibility.''' "Unported" omitted from "Creative Commons Compatible License" clause. In section 1, "a Creative Commons ''Unported'' license" should be listed.
** BY-SA

===Norway===
* '''Compatibility.''' "Unported" omitted from "Creative Commons Compatible License" clause. In section 1(c), "a Creative Commons ''Unported'' license" should be listed.
** BY-SA 1(c)

''There are likely to be more errors in Section 4(b) of BY-SA and BY-NC-SA; a Norwegian speaker is needed to report further errata.''

===Phillipines===
* '''Compatibility.''' "Unported" omitted from "Creative Commons Compatible License" clause. In section 1(c), "a Creative Commons Unported license" should be listed.
** BY-SA 1(c)
* '''Compatibility.''' In section 4(b), BY-NC-SA is erroneously listed as an example compatible port with BY-SA.
** BY-SA 4(b)
* '''Incorrect reference to "the applicable license".''' In section 4(b), a reference to "the applicable license" should instead be to "this license".
** BY-SA, BY-NC-SA 4(b)

===Romania===
* '''Compatibility.''' "Unported" omitted from "Creative Commons Compatible License" clause. In section 1(c), "a Creative Commons ''Unported'' license" should be listed.
** BY-SA 1(c)

''There are likely to be more errors in Section 4(b) of BY-SA and BY-NC-SA; a Romanian speaker is needed to report further errata.''

===Singapore===
* '''Incorrect example.''' The examples given in Section 4(b) ("e.g., Attribution-ShareAlike 3.0 SG" and "e.g., Attribution-NonCommercial-ShareAlike 3.0 SG") should instead be any ported license with the same license elements other than Singapore.
** BY-SA, BY-NC-SA 4(b)

===Spain===
* '''Missing jurisdiction flag.''' All licenses are missing the Spanish flag image in the header.
** All six licenses.

===Uganda===
* '''Incorrect reference to "the Applicable License".''' In section 4(b), a reference to "the Applicable License" should instead be to "this License". "You must keep intact all notices that refer to the Applicable License and to the disclaimer of warranties" should read "You must keep intact all notices that refer to this License and to the disclaimer of warranties".
**BY-SA 4(b), BY-NC-SA 4(b)

===United States===
*'''Typographical error." Section 3(b) includes two semicolons at the end of this section. Only one should be present.
** BY 3(b)
*'''Extra word.''' In Section 4(a), "exercise of the rights granted" should read simply "exercise the rights granted".
** BY-SA 4(a)
* '''Incorrect reference to "the Applicable License".''' In section 4(b), a reference to "the Applicable License" should instead be to "this License". "You must keep intact all notices that refer to the Applicable License and to the disclaimer of warranties" should read "You must keep intact all notices that refer to this License and to the disclaimer of warranties".
** BY-SA 4(b), BY-NC-SA 4(b)

==2.5 Generic license suite==
===Section 5===
* '''Typographical error.''' Section 5 contains the text "OR THE PRESENCE OF ABSENCE OF ERRORS". This should read "OR THE PRESENCE OF ERRORS".
** All six licenses.

==2.5 jurisdiction ports==
===Canada===
====English====
* '''Compatibility.''' In section 4(b), BY-NC-SA is erroneously listed as an example compatible port with BY-SA.
** BY-SA 4(b)
====French====
* '''Compatibility.''' In section 4(b), BY-NC-SA is erroneously listed as an example compatible port with BY-SA.
** BY-SA 4(b)
* '''Incorrectly included section.''' The last paragraph of Section 4(a) in BY-NC-ND was included in error and should be deleted.
** BY-NC-ND 4(a)

==2.0 Generic license suite==
===Section 5===
* '''Typographical error.''' Section 5 contains the text "OR THE PRESENCE OF ABSENCE OF ERRORS". This should read "OR THE PRESENCE OF ERRORS".
** All six licenses.

==2.0 Jurisdiction ports==
===Austria===
===Canada===
====English====
* '''Compatibility.''' In section 4(b), BY-NC-SA is erroneously listed as an example compatible port with BY-SA.
** BY-SA 4(b)
====French====
* '''Compatibility.''' In section 4(b), BY-NC-SA is erroneously listed as an example compatible port with BY-SA.
** BY-SA 4(b)
===France===
* '''Compatibility.''' In section 4(b), BY-NC-SA is erroneously listed as an example compatible port with BY-SA.
** BY-SA 4(b)
* '''Incorrect section reference.''' Section 5(a)(i) contains a reference to Section 4(e). This reference is only correct in the BY-NC-SA license. In BY and BY-ND this should be a reference to Section 4(c); in BY-SA, BY-NC, and BY-NC-ND it should be a reference to Section 4(d).
** BY, BY-SA, BY-NC, BY-ND, BY-NC-ND

===Germany===
* '''Compatibility.''' In section 4(b), BY-NC-SA is erroneously listed as an example compatible port with BY-SA.
** BY-SA 4(b)
* '''Incorrect spacing.''' In the introduction, "UNTER DER VORAUSSETZUNGEIN, DASS" should instead read "UNTER DER VORAUSSETZUNG EIN, DASS".
** BY
* '''Repeated numbering.''' Section 1(f) is mistakenly labeled with "f. f."; there should be only one.
** BY 1(f)
* '''Repeated comma.''' In Section 5, "vereinbart,," should red "vereinbart,".
* '''Repeated numbering.''' Section 8(a) is mistakenly labeled with "a. a."; there should be only one.
** BY 8(a)
* '''Typographical errors.''' The Disclaimer contains several typographical errors. "ALL RECHTE" should be "ALLE RECHTE"; "LIZENSGEBERS" should be "LIZENZGEBERS"; "KENIE VERTRAGSPARTEI" should be "KEINE VERTRAGSPARTEI", and "ÜBREEINSTIMMUNG" should be "ÜBEREINSTIMMUNG".
** All six licenses.

===Italy===
* '''Repeated section.''' Section 4(b) of this license is an exact duplicate of Section 4(a). It should instead discuss the conditions under which Derivative Works may be distributed. The passage in Version 2.5 of the Italy license contains the correct text.
** BY-SA 4(b)

==Errors in the 1.0 license suite==
===Generic===
===Jurisdiction ports===
====Israel====
* '''Typographical error.''' In Section ח.1, the text is in the masculine but the pronoun is feminine; " בכל פעם שאת מפיץ" should instead be "בכל פעם שאתה מפיץ".

==CC0 (1.0)==
* '''Incorrect word.''' In Section 4(b), "the present or absence of errors" should read "the presence or absence of errors".

==Deprecated licenses==
=== Developing Nations 2.0===
* '''Typographical error.''' In section 1(c), "enconomy" should read "economy".

[[Category:Legal]]

Legalcode errata

2019-12-03T20:59:20Z

CCID-timidrobot:

Despite our best efforts, spelling errors and other errata are sometimes included in the published legal code for licenses. However, Creative Commons does not amend legal code once published so that the licenses remain static, and not a moving target. This wiki page collects known errata for license legal code. If you discover a spelling error on a license, please send a message to legal@creativecommons.org.

=Errors by license=

==4.0 international license suite (English)==
===Validated HTML===
As originally published, the HTML for the license files did not validate. This was corrected; however, those with older copies of this file will have the incorrect file.

===Italics===
On 2019 September 24, we discovered that Section 2a5 of the 4.0 licenses had become italicized through unknown means. It was investigated and reversed back to its original formatting on November 12 2019

==3.0 Unported (International) license suite==
===Section 1===
* '''Incorrect section reference.''' Section 1(b) of BY-SA cites Section 1(f); it should cite Section 1(h).
** BY-SA 1(b)
* '''Incorrect word.''' Section 1(b) of BY-SA says that Adaptation is defined "below"; this should read "above".
** BY-SA 1(b)
===Section 2===
===Section 3===
* '''Inconsistent language'''. In Section 3(d), BY-SA uses "described" instead of "set forth".
** BY-NC-SA 3(d)
* '''Section 8(f) reference incorrect; missing word.''' These sections include a reference to Section 8(f); they should instead refer to Section 8(e). Additionally, BY-NC-ND omits the word "Section", which should be present.
** BY-ND 3(c)(iii), BY-NC-ND 3(b).

===Section 4===
* '''Incorrect reference to "the Applicable License".''' In section 4(b), a reference to "the Applicable License" should instead be to "this License": "You must keep intact all notices that refer to the Applicable License and to the disclaimer of warranties" should read "You must keep intact all notices that refer to this License and to the disclaimer of warranties".
**BY-SA 4(b), BY-NC-SA 4(b)
* '''Missing "the".''' In section 4(b) of BY-NC-SA, there is a sentence reading in part "must include a copy of, or the URI, for Applicable License with every copy". This excerpt should instead read "must include a copy of, or the URI for, the Applicable License with every copy".
**BY-NC-SA 4(b)
* '''Missing "the".''' In Section 4(b) of BY-NC-ND, "if a credit for all contributing authors of Collection appears" should read "if a credit for all contributing authors of the Collection appears".
**BY-NC-ND, 4(b)
* '''Missing numerals and capitalization.''' In section 4(b) of BY-NC-SA, each condition should be numbered with uppercase roman numerals. Additionally, the beginning of item (IV) should be capitalized. (The passage should read: "(I) You must include a copy of[...]"; "(II) You may not offer[...]"; "(III) You must keep intact[...]"; "(IV) When You Distribute[...]")
**BY-NC-SA 4(b)
* '''Numbering of list items.''' In Section 4(b) of BY-NC-SA, "only under: (i) the terms of this License" should instead read "only under the terms of: (i) this License".
** BY-NC-SA 4(b)
* '''Capitalization.''' "Collection" should be lowercase both times in the last sentence of Section 4(b) in BY-SA; the excerpts should read "as incorporated in a collection" and "does not require the collection apart from the Adaptation itself".
** BY-SA 4(b)
* '''Comma placement.''' In the BY-NC and BY-NC-SA licenses, a comma is incorrectly placed. The text reading "and, (iv) consistent with Section 3(b)" should instead read "and (iv), consistent with Section 3(b)".
** BY-NC 4(c), BY-NC-SA 4(d).
* '''Extra hyphen.''' In Section 4(c) of BY-NC-SA, "con-nection" is an error, and should be written as "connection" instead.
** BY-NC-SA 4(c)
* '''Typographical error: "Ssection".''' In Section 4(c), BY-SA contains the text "consistent with Ssection 3(b)"; "Ssection" should be "Section".
** BY-SA 4(c).
* '''Incorrect subsection reference.''' Section 4(d)(iii) of BY-NC references 4(c). It should reference 4(b).
** BY-NC 4(d)(iii)
* '''Typographical error.''' In Section 4, several licenses refer to "a Adaptation"; this should be "an Adaptation".
** BY 4(b), BY-NC, BY-SA 4(c), BY-NC-SA 4(d)

=== Section 5 ===
* '''Omitted phrase.''' The phrase "And to the Fullest Extent Permitted by Applicable Law," should appear before "Licensor Offers the Work As-Is and Makes No Representations".
** BY, BY-SA, BY-NC, BY-ND, BY-NC-ND
* '''Omitted word ("to").''' In BY-NC-ND, "Unless Otherwise Mutually Agreed By the Parties" should read "Unless Otherwise Mutually Agreed To By the Parties".
** BY-NC-ND
* '''Spelling.''' "Merchantability" is misspelled as "Merchantibility" in five licenses.
** BY, BY-NC, BY-SA, BY-ND, BY-NC-ND.
* '''Inconsistent language.''' BY-NC-SA includes the text "This Exclusion May Not Apply To You"; it should read "Such Exclusion May Not Apply To You".
** BY-NC-SA
* '''Typographical error.''' Section 5 contains the text "OR THE PRESENCE OF ABSENCE OF ERRORS". This should read "OR THE PRESENCE OF ERRORS".
** All six licenses.

=== Notice ===
* '''Incorrect word.''' In the last paragraph, "this trademark restriction does not form part of the License" should read "this trademark restriction does not form part of this License".

==3.0 jurisdiction ports==
===Australia===
*'''Incorrect header color. ''' The heading for BY-NC-SA is green, and should be yellow.
** BY-NC-SA

===Czech Republic===
*'''Typographical error.''' In the 2nd sentence of the final section ("Upozornění Creative Commons"), "Commos" should be "Commons".
** All six licenses.

===Ecuador===
*'''Incorrect header color.''' The headings for these four licenses are green, and should be yellow.
** BY-NC, BY-NC-ND, BY-NC-SA, BY-ND

===Germany===
*'''Incorrect word.''' In Section 8(e), the word "angeboteten" should be "angebotenen".
** BY-SA, BY-NC-SA, BY-NC, BY-ND, BY-NC-ND

===Greece===
* '''Incorrect header color.''' The headings for these licenses are yellow, and should be green.
** BY, BY-SA
*'''Incorrect example.''' In section 3(β) of BY-SA, the example given is "Attribution—NonCommercial—ShareAlike 3 U.S."; it should be "Attribution—ShareAlike 3 U.S."
** BY-SA 3(β)
* '''Compatibility.''' In section 4(β), BY-NC-SA is erroneously listed as an example compatible port with BY-SA.
** BY-SA 4(β)

''There are likely to be more errors in Section 4(β) of BY-SA and BY-NC-SA; a Greek speaker is needed to report further errata.'''

===Guatemala===
* '''Incorrect header color.''' The headings for these licenses are green, and should be yellow.
** BY-NC, BY-NC-ND, BY-NC-SA, BY-ND

===Hong Kong===
* '''Incorrect example.''' The example given in Section 4(b) "(e.g., Attribution-ShareAlike 3.0 Hong Kong)" should instead be any ported BY-SA license other than Hong Kong.
** BY-SA, BY-NC-SA 4(b)
* '''Incorrect reference to "the applicable license".''' In section 4(b), a reference to "the applicable license" should instead be to "this license".
** BY-SA, BY-NC-SA 4(b)
* '''Missing numerals and capitalization.''' In section 4(b) of BY-NC-SA, each condition should be numbered with uppercase roman numerals. Additionally, the beginning of item (IV) should be capitalized. (The passage should read: "(I) You must include a copy of[...]"; "(II) You may not offer[...]"; "(III) You must keep intact[...]"; "(IV) When You Distribute[...]")
**BY-NC-SA 4(b)

===IGO===
* '''Incorrect word in the original English (to be corrected in official translations).''' In the definition of "Publicly Perform", the phrase "from a place and at a place" should read "from a place and at a time".
** BY, BY-NC, BY-ND, and BY-NC-ND: 1(g); BY-SA, BY-NC-SA: 1(h)

===Ireland===
* '''Incorrect reference to "the Applicable License".''' In section 4(b), a reference to "the Applicable License" should instead be to "this License". "You must keep intact all notices that refer to the Applicable License and to the disclaimer of warranties" should read "You must keep intact all notices that refer to this License and to the disclaimer of warranties".
* BY-SA 4(b), BY-NC-SA 4(b)

===Luxembourg===
* '''Incorrect header color.''' The headings for these licenses are green, and should be yellow.
** BY-NC, BY-NC-ND, BY-NC-SA, BY-ND

===Netherlands===
* '''Spelling.''' In the last sentence of section 3, the word "beschikt" is misspelled as "beschickt".
** All six licenses.

===New Zealand===
* '''Compatibility.''' "Unported" omitted from "Creative Commons Compatible License" clause. In section 1, "a Creative Commons ''Unported'' license" should be listed.
** BY-SA

===Norway===
* '''Compatibility.''' "Unported" omitted from "Creative Commons Compatible License" clause. In section 1(c), "a Creative Commons ''Unported'' license" should be listed.
** BY-SA 1(c)

''There are likely to be more errors in Section 4(b) of BY-SA and BY-NC-SA; a Norwegian speaker is needed to report further errata.''

===Phillipines===
* '''Compatibility.''' "Unported" omitted from "Creative Commons Compatible License" clause. In section 1(c), "a Creative Commons Unported license" should be listed.
** BY-SA 1(c)
* '''Compatibility.''' In section 4(b), BY-NC-SA is erroneously listed as an example compatible port with BY-SA.
** BY-SA 4(b)
* '''Incorrect reference to "the applicable license".''' In section 4(b), a reference to "the applicable license" should instead be to "this license".
** BY-SA, BY-NC-SA 4(b)

===Romania===
* '''Compatibility.''' "Unported" omitted from "Creative Commons Compatible License" clause. In section 1(c), "a Creative Commons ''Unported'' license" should be listed.
** BY-SA 1(c)

''There are likely to be more errors in Section 4(b) of BY-SA and BY-NC-SA; a Romanian speaker is needed to report further errata.''

===Singapore===
* '''Incorrect example.''' The examples given in Section 4(b) ("e.g., Attribution-ShareAlike 3.0 SG" and "e.g., Attribution-NonCommercial-ShareAlike 3.0 SG") should instead be any ported license with the same license elements other than Singapore.
** BY-SA, BY-NC-SA 4(b)

===Spain===
* '''Missing jurisdiction flag.''' All licenses are missing the Spanish flag image in the header.
** All six licenses.

===Uganda===
* '''Incorrect reference to "the Applicable License".''' In section 4(b), a reference to "the Applicable License" should instead be to "this License". "You must keep intact all notices that refer to the Applicable License and to the disclaimer of warranties" should read "You must keep intact all notices that refer to this License and to the disclaimer of warranties".
**BY-SA 4(b), BY-NC-SA 4(b)

===United States===
*'''Typographical error." Section 3(b) includes two semicolons at the end of this section. Only one should be present.
** BY 3(b)
*'''Extra word.''' In Section 4(a), "exercise of the rights granted" should read simply "exercise the rights granted".
** BY-SA 4(a)
* '''Incorrect reference to "the Applicable License".''' In section 4(b), a reference to "the Applicable License" should instead be to "this License". "You must keep intact all notices that refer to the Applicable License and to the disclaimer of warranties" should read "You must keep intact all notices that refer to this License and to the disclaimer of warranties".
** BY-SA 4(b), BY-NC-SA 4(b)

==2.5 Generic license suite==
===Section 5===
* '''Typographical error.''' Section 5 contains the text "OR THE PRESENCE OF ABSENCE OF ERRORS". This should read "OR THE PRESENCE OF ERRORS".
** All six licenses.

==2.5 jurisdiction ports==
===Canada===
====English====
* '''Compatibility.''' In section 4(b), BY-NC-SA is erroneously listed as an example compatible port with BY-SA.
** BY-SA 4(b)
====French====
* '''Compatibility.''' In section 4(b), BY-NC-SA is erroneously listed as an example compatible port with BY-SA.
** BY-SA 4(b)
* '''Incorrectly included section.''' The last paragraph of Section 4(a) in BY-NC-ND was included in error and should be deleted.
** BY-NC-ND 4(a)

==2.0 Generic license suite==
===Section 5===
* '''Typographical error.''' Section 5 contains the text "OR THE PRESENCE OF ABSENCE OF ERRORS". This should read "OR THE PRESENCE OF ERRORS".
** All six licenses.

==2.0 Jurisdiction ports==
===Austria===
===Canada===
====English====
* '''Compatibility.''' In section 4(b), BY-NC-SA is erroneously listed as an example compatible port with BY-SA.
** BY-SA 4(b)
====French====
* '''Compatibility.''' In section 4(b), BY-NC-SA is erroneously listed as an example compatible port with BY-SA.
** BY-SA 4(b)
===France===
* '''Compatibility.''' In section 4(b), BY-NC-SA is erroneously listed as an example compatible port with BY-SA.
** BY-SA 4(b)
* '''Incorrect section reference.''' Section 5(a)(i) contains a reference to Section 4(e). This reference is only correct in the BY-NC-SA license. In BY and BY-ND this should be a reference to Section 4(c); in BY-SA, BY-NC, and BY-NC-ND it should be a reference to Section 4(d).
** BY, BY-SA, BY-NC, BY-ND, BY-NC-ND

===Germany===
* '''Compatibility.''' In section 4(b), BY-NC-SA is erroneously listed as an example compatible port with BY-SA.
** BY-SA 4(b)
* '''Incorrect spacing.''' In the introduction, "UNTER DER VORAUSSETZUNGEIN, DASS" should instead read "UNTER DER VORAUSSETZUNG EIN, DASS".
** BY
* '''Repeated numbering.''' Section 1(f) is mistakenly labeled with "f. f."; there should be only one.
** BY 1(f)
* '''Repeated comma.''' In Section 5, "vereinbart,," should red "vereinbart,".
* '''Repeated numbering.''' Section 8(a) is mistakenly labeled with "a. a."; there should be only one.
** BY 8(a)
* '''Typographical errors.''' The Disclaimer contains several typographical errors. "ALL RECHTE" should be "ALLE RECHTE"; "LIZENSGEBERS" should be "LIZENZGEBERS"; "KENIE VERTRAGSPARTEI" should be "KEINE VERTRAGSPARTEI", and "ÜBREEINSTIMMUNG" should be "ÜBEREINSTIMMUNG".
** All six licenses.

===Italy===
* '''Repeated section.''' Section 4(b) of this license is an exact duplicate of Section 4(a). It should instead discuss the conditions under which Derivative Works may be distributed. The passage in Version 2.5 of the Italy license contains the correct text.
** BY-SA 4(b)

==Errors in the 1.0 license suite==
===Generic===
===Jurisdiction ports===
====Israel====
* '''Typographical error.''' In Section ח.1, the text is in the masculine but the pronoun is feminine; " בכל פעם שאת מפיץ" should instead be "בכל פעם שאתה מפיץ".

==CC0 (1.0)==
* '''Incorrect word.''' In Section 4(b), "the present or absence of errors" should read "the presence or absence of errors".

==Deprecated licenses==
=== Developing Nations 2.0===
* '''Typographical error.''' In section 1(c), "enconomy" should read "economy".

[[Category:Legal]]

RdfaDict

2019-11-22T19:53:11Z

CCID-timidrobot: added GitHub repo link

[[Category:Developer]]
[[Category:Tools]]
[[Category:Opensource]]

'''rdfadict''' is a Python package which provides an [[RDFa]] parser and a simple, dictionary-like interface for the triples. Download, installation and usage information may be found in the Python Package Index at http://python.org/pypi/rdfadict.

The [https://github.com/creativecommons/rdfadict creativecommons/rdfadict] repository is on GitHub.

<div style="margin-left:-9999px;"> [http://itshumour.blogspot.com/2011/08/funny-statuses-quotes-for-facebook.html funny facebook statuses] [http://www.thefunnyquotessayings.com/random-funny-sayings-and-phrases/ funny sayings and phrases] </div>

Source Repository Information

2019-11-21T18:30:10Z

CCID-timidrobot:

[[Category:Developer]]
[[Category:CC_Tech_Handbook]]

== Open Source Projects ==

'''[https://opensource.creativecommons.org/projects/ Open Source Projects — Creative Commons on GitHub] contains an overview of our FOSS projects.'''

== Git Repositories on GitHub ==

Creative Commons has [http://git.or.cz/ Git] repositories on GitHub:
# https://github.com/creativecommons/
# https://github.com/cc-archive/

== Historical Information ==

* ???? ???: We moved our repositories to GitHub (some time between 2011 September and 2014 April)
* 2008 March: We moved our primary source repository from Sourceforge.net to code.creativecommons.org
** [https://opensource.creativecommons.org/archives/old-tech-blog/entries/version-control-changes/ Version Control Changes — Creative Commons on GitHub]
* 2005 November: In order to take advantage of Subversion source control and other features, Creative Commons moved the ccPublisher 2 project from SourceForge.net to developer.Berlios.de

=== 2008 Subversion Modules ===

<table align="left" valign="top" style="float:none;">
<tr><th>module name </th><th>description</th></tr>
<tr><td>__cvs_import/</td><td>Inactive modules imported to Subversion from CVS circa 2005 (from sourceforge.net).</td></tr>
<tr><td>adobe_panel/</td><td>XMP license panel for legacy Adobe products</td></tr>
<tr><td>api/</td><td>CC API; now developed in git (cc.api)</td></tr>
<tr><td>api_client/</td><td>Wrappers for the API in Python, Java, etc; unmaintained.</td></tr>
<tr><td>asheesh_oneoffs/</td><td></td></tr>
<tr><td>autocurate/</td><td>Scripts to generate packages of content from sites like Flickr, etc, used for LiveCD.</td></tr>
<tr><td>banshee-license-verifier-plugin/</td><td>GSOC project: plugin for Banshee to verify web statement metadata pointed to in MP3 ID3 tags.</td></tr>
<tr><td>bbpress/</td><td>Tracking repository of bbpress</td></tr>
<tr><td>blog_analysis/</td><td>Return top blogs pointing to CC, as reported by Technorati. Used for targeted outreach.</td></tr>
<tr><td>buildout_script/</td><td>Buildout recipe for doing string substitution in script templates</td></tr>
<tr><td>campaign_widget/</td><td>Annual campaign javascript widget</td></tr>
<tr><td>cc-content.deb/</td><td></td></tr>
<tr><td>cc-sharp/</td><td>C# model for CC licenses</td></tr>
<tr><td>cc.engine/</td><td>License engine; now developed in git (cc.license)</td></tr>
<tr><td>cc.license/</td><td></td></tr>
<tr><td>ccbanshee/</td><td>GSOC project: Banshee plugin for displaying license information</td></tr>
<tr><td>cchost/</td><td>Legacy repository for CCHost, platform developed for CC Mixter</td></tr>
<tr><td>cci/</td><td>WordPress for legacy iCommons website</td></tr>
<tr><td>cclabs/</td><td>Legacy CC Labs experiments (DHTML chooser, et al)</td></tr>
<tr><td>cclib/</td><td></td></tr>
<tr><td>cclicense/</td><td></td></tr>
<tr><td>[[CcLookup|cclookup]]/</td><td>wxPython application for verifying web statements embedded in media files</td></tr>
<tr><td>[[CcNutch|ccnutch]]/</td><td>Nutch + cc search customizations</td></tr>
<tr><td>ccoer/</td><td>Early prototype of DiscoverEd, based on Scuttle</td></tr>
<tr><td>ccooo/</td><td>OpenOffice.org add-on, now developed in git.</td></tr>
<tr><td>ccpublisher1/</td><td>CC Publisher 1.x; 2.x code lives in the berlios.de repository/td></tr>
<tr><td>ccrdf/</td><td>A Python wrapper for CC Licenses</td></tr>
<tr><td>ccsearch/</td><td>CC Meta-search</td></tr>
<tr><td>cctagutils/</td><td>Python library for reading and writing CC's suggested web statements</td></tr>
<tr><td>ccwordpress/</td><td>creativecommons.org</td></tr>
<tr><td>cli_tools/</td><td>Command line tools for tagging and verifying licensed works.</td></tr>
<tr><td>desktop_search/</td><td>Prototype of Spotlight plugin for Mac OS X</td></tr>
<tr><td>experimental/</td><td></td></tr>
<tr><td>feed2map/</td><td></td></tr>
<tr><td>hooks/</td><td></td></tr>
<tr><td>i18n/</td><td>Translations, maintenance tools, now in git.</td></tr>
<tr><td>i18nedit/</td><td>Half finished prototype of web based PO editor, herder</td></tr>
<tr><td>jswidget/</td><td>Drop-in javascript widget for license selection</td></tr>
<tr><td>liblicense/</td><td>C library for manipulating license information embedded in files</td></tr>
<tr><td>liblicense-gnome/</td><td>gnome UI bindings for liblicense</td></tr>
<tr><td>liblicense-kde/</td><td>KDE UI bindings for liblicense</td></tr>
<tr><td>liblicense-sugar/</td><td>Sugar UI for liblicense</td></tr>
<tr><td>license-tutorial/</td><td></td></tr>
<tr><td>license.rdf/</td><td>License RDF files</td></tr>
<tr><td>license_xsl/</td><td>Legacy chooser XSLT and questions</td></tr>
<tr><td>livecontent/</td><td>Live CD with CC licensed content</td></tr>
<tr><td>log_analysis/</td><td></td></tr>
<tr><td>metadata_scraper/</td><td>Now developed in git as deedscraper</td></tr>
<tr><td>mozcc2/</td><td>Firefox add-on for displaying CC license information; superseded by OpenAttribute</td></tr>
<tr><td>nagios/</td><td>monitoring configuration</td></tr>
<tr><td>nc-survey/</td><td>Non-Commercial survey related code</td></tr>
<tr><td>oe_search/</td><td>PHP frontend for a Google CSE that acted as early DiscoverEd prototype</td></tr>
<tr><td>oenutch/</td><td>DiscoverEd</td></tr>
<tr><td>operator_userscript/</td><td>User script for Operator to display license information</td></tr>
<tr><td>opml/</td><td>Python library for reading and parsing OPML</td></tr>
<tr><td>pdf_callback/</td><td>Demonstration of a PDF with "phone home" capability</td></tr>
<tr><td>planet/</td><td>CC feed aggregator</td></tr>
<tr><td>pyarchive/</td><td>Python library for uploading works to Internet Archive</td></tr>
<tr><td>pywikipedia/</td><td>Python API for mediawiki, used for sending staff call emails</td></tr>
<tr><td>rdfadict/</td><td>Python dict-like interface for an RDFa parser</td></tr>
<tr><td>scicom/</td><td>Science Commons related projects, including MTA, SCA</td></tr>
<tr><td>scripts/</td><td></td></tr>
<tr><td>smw_tools/</td><td></td></tr>
<tr><td>stats/</td><td></td></tr>
<tr><td>themes/</td><td>Various theme projects</td></tr>
<tr><td>vendorlibs/</td><td>Vendor libraries that are used by other projects. Modules are imported here if the project doesn't use svn, so we can use svn:externals, or if additional customization is required</td></tr>
<tr><td>widgets/</td><td>Widgets for visualizing CC content and information.</td></tr>
<tr><td>wordpressmu/</td><td></td></tr>
<tr><td>wpLicense/</td><td>WordPress plugin for CC licensing; now developed in git/WP svn</td></tr>
<tr><td>www-i/</td><td>i.creativecommons.org</td></tr>
<tr><td>xmp/</td><td>Tools for embedding XMP metadata in PDF, JPEG and (future) other file types.</td></tr>
<tr><td>zope_products/ </td><td>CC developed zope products: the license engine, Plone skin and iStr.</td></tr>
</table>

Source Repository Information

2019-11-21T18:29:26Z

CCID-timidrobot: long overdue updates (we've been on github a long time)

[[Category:Developer]]
[[Category:CC_Tech_Handbook]]

== Open Source Projects ==

'''[https://opensource.creativecommons.org/projects/ Open Source Projects — Creative Commons on GitHub] contains an overview of our FOSS projects.'''

== Git Repositories on GitHub ==

Creative Commons has [http://git.or.cz/ Git] repositories on GitHub:
1. https://github.com/creativecommons/
2. https://github.com/cc-archive/

== Historical Information ==

* ???? ???: We moved our repositories to GitHub (some time between 2011 September and 2014 April)
* 2008 March: We moved our primary source repository from Sourceforge.net to code.creativecommons.org
** [https://opensource.creativecommons.org/archives/old-tech-blog/entries/version-control-changes/ Version Control Changes — Creative Commons on GitHub]
* 2005 November: In order to take advantage of Subversion source control and other features, Creative Commons moved the ccPublisher 2 project from SourceForge.net to developer.Berlios.de

=== 2008 Subversion Modules ===

<table align="left" valign="top" style="float:none;">
<tr><th>module name </th><th>description</th></tr>
<tr><td>__cvs_import/</td><td>Inactive modules imported to Subversion from CVS circa 2005 (from sourceforge.net).</td></tr>
<tr><td>adobe_panel/</td><td>XMP license panel for legacy Adobe products</td></tr>
<tr><td>api/</td><td>CC API; now developed in git (cc.api)</td></tr>
<tr><td>api_client/</td><td>Wrappers for the API in Python, Java, etc; unmaintained.</td></tr>
<tr><td>asheesh_oneoffs/</td><td></td></tr>
<tr><td>autocurate/</td><td>Scripts to generate packages of content from sites like Flickr, etc, used for LiveCD.</td></tr>
<tr><td>banshee-license-verifier-plugin/</td><td>GSOC project: plugin for Banshee to verify web statement metadata pointed to in MP3 ID3 tags.</td></tr>
<tr><td>bbpress/</td><td>Tracking repository of bbpress</td></tr>
<tr><td>blog_analysis/</td><td>Return top blogs pointing to CC, as reported by Technorati. Used for targeted outreach.</td></tr>
<tr><td>buildout_script/</td><td>Buildout recipe for doing string substitution in script templates</td></tr>
<tr><td>campaign_widget/</td><td>Annual campaign javascript widget</td></tr>
<tr><td>cc-content.deb/</td><td></td></tr>
<tr><td>cc-sharp/</td><td>C# model for CC licenses</td></tr>
<tr><td>cc.engine/</td><td>License engine; now developed in git (cc.license)</td></tr>
<tr><td>cc.license/</td><td></td></tr>
<tr><td>ccbanshee/</td><td>GSOC project: Banshee plugin for displaying license information</td></tr>
<tr><td>cchost/</td><td>Legacy repository for CCHost, platform developed for CC Mixter</td></tr>
<tr><td>cci/</td><td>WordPress for legacy iCommons website</td></tr>
<tr><td>cclabs/</td><td>Legacy CC Labs experiments (DHTML chooser, et al)</td></tr>
<tr><td>cclib/</td><td></td></tr>
<tr><td>cclicense/</td><td></td></tr>
<tr><td>[[CcLookup|cclookup]]/</td><td>wxPython application for verifying web statements embedded in media files</td></tr>
<tr><td>[[CcNutch|ccnutch]]/</td><td>Nutch + cc search customizations</td></tr>
<tr><td>ccoer/</td><td>Early prototype of DiscoverEd, based on Scuttle</td></tr>
<tr><td>ccooo/</td><td>OpenOffice.org add-on, now developed in git.</td></tr>
<tr><td>ccpublisher1/</td><td>CC Publisher 1.x; 2.x code lives in the berlios.de repository/td></tr>
<tr><td>ccrdf/</td><td>A Python wrapper for CC Licenses</td></tr>
<tr><td>ccsearch/</td><td>CC Meta-search</td></tr>
<tr><td>cctagutils/</td><td>Python library for reading and writing CC's suggested web statements</td></tr>
<tr><td>ccwordpress/</td><td>creativecommons.org</td></tr>
<tr><td>cli_tools/</td><td>Command line tools for tagging and verifying licensed works.</td></tr>
<tr><td>desktop_search/</td><td>Prototype of Spotlight plugin for Mac OS X</td></tr>
<tr><td>experimental/</td><td></td></tr>
<tr><td>feed2map/</td><td></td></tr>
<tr><td>hooks/</td><td></td></tr>
<tr><td>i18n/</td><td>Translations, maintenance tools, now in git.</td></tr>
<tr><td>i18nedit/</td><td>Half finished prototype of web based PO editor, herder</td></tr>
<tr><td>jswidget/</td><td>Drop-in javascript widget for license selection</td></tr>
<tr><td>liblicense/</td><td>C library for manipulating license information embedded in files</td></tr>
<tr><td>liblicense-gnome/</td><td>gnome UI bindings for liblicense</td></tr>
<tr><td>liblicense-kde/</td><td>KDE UI bindings for liblicense</td></tr>
<tr><td>liblicense-sugar/</td><td>Sugar UI for liblicense</td></tr>
<tr><td>license-tutorial/</td><td></td></tr>
<tr><td>license.rdf/</td><td>License RDF files</td></tr>
<tr><td>license_xsl/</td><td>Legacy chooser XSLT and questions</td></tr>
<tr><td>livecontent/</td><td>Live CD with CC licensed content</td></tr>
<tr><td>log_analysis/</td><td></td></tr>
<tr><td>metadata_scraper/</td><td>Now developed in git as deedscraper</td></tr>
<tr><td>mozcc2/</td><td>Firefox add-on for displaying CC license information; superseded by OpenAttribute</td></tr>
<tr><td>nagios/</td><td>monitoring configuration</td></tr>
<tr><td>nc-survey/</td><td>Non-Commercial survey related code</td></tr>
<tr><td>oe_search/</td><td>PHP frontend for a Google CSE that acted as early DiscoverEd prototype</td></tr>
<tr><td>oenutch/</td><td>DiscoverEd</td></tr>
<tr><td>operator_userscript/</td><td>User script for Operator to display license information</td></tr>
<tr><td>opml/</td><td>Python library for reading and parsing OPML</td></tr>
<tr><td>pdf_callback/</td><td>Demonstration of a PDF with "phone home" capability</td></tr>
<tr><td>planet/</td><td>CC feed aggregator</td></tr>
<tr><td>pyarchive/</td><td>Python library for uploading works to Internet Archive</td></tr>
<tr><td>pywikipedia/</td><td>Python API for mediawiki, used for sending staff call emails</td></tr>
<tr><td>rdfadict/</td><td>Python dict-like interface for an RDFa parser</td></tr>
<tr><td>scicom/</td><td>Science Commons related projects, including MTA, SCA</td></tr>
<tr><td>scripts/</td><td></td></tr>
<tr><td>smw_tools/</td><td></td></tr>
<tr><td>stats/</td><td></td></tr>
<tr><td>themes/</td><td>Various theme projects</td></tr>
<tr><td>vendorlibs/</td><td>Vendor libraries that are used by other projects. Modules are imported here if the project doesn't use svn, so we can use svn:externals, or if additional customization is required</td></tr>
<tr><td>widgets/</td><td>Widgets for visualizing CC content and information.</td></tr>
<tr><td>wordpressmu/</td><td></td></tr>
<tr><td>wpLicense/</td><td>WordPress plugin for CC licensing; now developed in git/WP svn</td></tr>
<tr><td>www-i/</td><td>i.creativecommons.org</td></tr>
<tr><td>xmp/</td><td>Tools for embedding XMP metadata in PDF, JPEG and (future) other file types.</td></tr>
<tr><td>zope_products/ </td><td>CC developed zope products: the license engine, Plone skin and iStr.</td></tr>
</table>

License RDF

2019-11-15T21:41:32Z

CCID-timidrobot: updated protocol to https and added IIIF

Creative Commons provides information on licenses for three audiences: lawyers, humans and machines. The machine-readable information is described using [http://www.w3.org/RDF RDF] and made available from the [https://github.com/creativecommons/cc.licenserdf creativecommons/cc.licenserdf] git repository.

== File Naming ==

Files in the <code>license_rdf</code> module are named using the following convention:

<pre>creativecommons.org_license_[license-code]_[version]_[jurisdiction]_.rdf</pre>

More generally, you can take the URL of a license (i.e. <code>https://creativecommons.org/licenses/by/3.0/</code>), strip the protocol information (<code>https://</code>) and replace all forward-slashes (<code>/</code>) with underscores (<code>_</code>) to arrive at the base filename. [[Liblicense]] provides a function to perform this mapping for you.

== File Contents ==

Each file contains the RDF (encoded as RDF/XML) describing the particular license. Information described by the RDF includes:

* license name, including translations
* license description, including translations
* license properties, as described by [[ccREL]]

== Usages ==

The license RDF files are used in the following CC applications:

* The license engine
* [[OpenOfficeOrg Addin]]
* [[Liblicense]]
* IIIF (International Image Interoperability Framework)

Developers

2019-11-13T23:32:03Z

CCID-timidrobot: fixed additional mailing list urls

'''Join the CC Developer Community'''

Join our [http://slack-signup.creativecommons.org/ Slack], IRC, or [mailto:cc-developers+subscribe@creativecommons.org mailing list] communities to meet other developers interested in Creative Commons, get feedback on your projects, and talk with CC's full-time engineering staff. You can also keep up with us on the [https://opensource.creativecommons.org/blog CC Open Source Blog] or via [https://twitter.com/cc_opensource Twitter].

Know more about our [https://opensource.creativecommons.org/community/ communication channels]

== Get Involved ==

We really appreciate community contributions and feedback (we're a small team and spread thin) and we especially love seeing what you build using CC's tools.

We do all of our development on GitHub and are generally open to pull requests and proposals for new community-maintained projects.
We would especially like help with reviving projects that CC's engineering team does not have the time to actively work on (such as [https://github.com/creativecommons/wp-plugin-creativecommons our WordPress plugin] and [https://github.com/creativecommons/cc-license-chooser license chooser widget]). We're also looking to improve our documentation and increase our automated test coverage across pretty much all our projects, so help with that would be greatly appreciated.
Please follow [https://opensource.creativecommons.org/contributing-code/pr-guidelines our pull request guidelines] when submitting code. If you are not familiar with GitHub or pull requests, [https://guides.github.com/activities/hello-world/ here is an excellent guide to get started].

Know more about [https://opensource.creativecommons.org/contributing-code/ how to contribute on existing projects or proposing new ones]!

; Mailing list
: [mailto:cc-developers+subscribe@creativecommons.org CC Developers] or [mailto:usability-announce+subscribe@creativecommons.org CC Usability Announcements].
; IRC #creativecommons-dev channel on [https://freenode.net/ Freenode]
: This channel is mirrored to the #cc-developers channel on Slack.
; Slack
: [http://slack-signup.creativecommons.org/ Sign up] and join our sub-communities for tech/developers.

== Other forms of contribution ==

; [https://opensource.creativecommons.org/gsoc-2019/ Google Summer of Code]
: See CC participation on GSoC since 2006.
; [https://opensource.creativecommons.org/community/#mailing-lists Usability Testing]
: Participate in one of our regular usability tests for CC tools that we're actively working on (we'll give you a gift card!).
; [https://wiki.creativecommons.org/wiki/Translate Translate our Content]
: Find out how to help the Creative Commons community with translations.
; [https://github.com/creativecommons/cc-vocabulary Contribute To Design]
: Contribute to our brand new set of standard UI components and help us apply it to all the existing projects.

<br clear="all"/>

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

[[Category:Developer]]

__NOTOC__

Developers

2019-11-13T23:30:02Z

CCID-timidrobot: fixed wordpress plugin url

'''Join the CC Developer Community'''

Join our [http://slack-signup.creativecommons.org/ Slack], IRC, or [mailto:cc-developers+subscribe@creativecommons.org mailing list] communities to meet other developers interested in Creative Commons, get feedback on your projects, and talk with CC's full-time engineering staff. You can also keep up with us on the [https://opensource.creativecommons.org/blog CC Open Source Blog] or via [https://twitter.com/cc_opensource Twitter].

Know more about our [https://opensource.creativecommons.org/community/ communication channels]

== Get Involved ==

We really appreciate community contributions and feedback (we're a small team and spread thin) and we especially love seeing what you build using CC's tools.

We do all of our development on GitHub and are generally open to pull requests and proposals for new community-maintained projects.
We would especially like help with reviving projects that CC's engineering team does not have the time to actively work on (such as [https://github.com/creativecommons/wp-plugin-creativecommons our WordPress plugin] and [https://github.com/creativecommons/cc-license-chooser license chooser widget]). We're also looking to improve our documentation and increase our automated test coverage across pretty much all our projects, so help with that would be greatly appreciated.
Please follow [https://opensource.creativecommons.org/contributing-code/pr-guidelines our pull request guidelines] when submitting code. If you are not familiar with GitHub or pull requests, [https://guides.github.com/activities/hello-world/ here is an excellent guide to get started].

Know more about [https://opensource.creativecommons.org/contributing-code/ how to contribute on existing projects or proposing new ones]!

; Mailing list
: [cc-developers+subscribe@creativecommons.org CC Developers] or [usability-announce+subscribe@creativecommons.org CC Usability Announcements].
; IRC #creativecommons-dev channel on [https://freenode.net/ Freenode]
: This channel is mirrored to the #cc-developers channel on Slack.
; Slack
: [http://slack-signup.creativecommons.org/ Sign up] and join our sub-communities for tech/developers.

== Other forms of contribution ==

; [https://opensource.creativecommons.org/gsoc-2019/ Google Summer of Code]
: See CC participation on GSoC since 2006.
; [https://opensource.creativecommons.org/community/#mailing-lists Usability Testing]
: Participate in one of our regular usability tests for CC tools that we're actively working on (we'll give you a gift card!).
; [https://wiki.creativecommons.org/wiki/Translate Translate our Content]
: Find out how to help the Creative Commons community with translations.
; [https://github.com/creativecommons/cc-vocabulary Contribute To Design]
: Contribute to our brand new set of standard UI components and help us apply it to all the existing projects.

<br clear="all"/>

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

[[Category:Developer]]

__NOTOC__

Developers

2019-11-13T23:29:24Z

CCID-timidrobot: fixed mailing list url

'''Join the CC Developer Community'''

Join our [http://slack-signup.creativecommons.org/ Slack], IRC, or [mailto:cc-developers+subscribe@creativecommons.org mailing list] communities to meet other developers interested in Creative Commons, get feedback on your projects, and talk with CC's full-time engineering staff. You can also keep up with us on the [https://opensource.creativecommons.org/blog CC Open Source Blog] or via [https://twitter.com/cc_opensource Twitter].

Know more about our [https://opensource.creativecommons.org/community/ communication channels]

== Get Involved ==

We really appreciate community contributions and feedback (we're a small team and spread thin) and we especially love seeing what you build using CC's tools.

We do all of our development on GitHub and are generally open to pull requests and proposals for new community-maintained projects.
We would especially like help with reviving projects that CC's engineering team does not have the time to actively work on (such as [https://github.com/creativecommons/creativecommons-wordpress-plugin our WordPress plugin] and [https://github.com/creativecommons/cc-license-chooser license chooser widget]). We're also looking to improve our documentation and increase our automated test coverage across pretty much all our projects, so help with that would be greatly appreciated.
Please follow [https://opensource.creativecommons.org/contributing-code/pr-guidelines our pull request guidelines] when submitting code. If you are not familiar with GitHub or pull requests, [https://guides.github.com/activities/hello-world/ here is an excellent guide to get started].

Know more about [https://opensource.creativecommons.org/contributing-code/ how to contribute on existing projects or proposing new ones]!

; Mailing list
: [cc-developers+subscribe@creativecommons.org CC Developers] or [usability-announce+subscribe@creativecommons.org CC Usability Announcements].
; IRC #creativecommons-dev channel on [https://freenode.net/ Freenode]
: This channel is mirrored to the #cc-developers channel on Slack.
; Slack
: [http://slack-signup.creativecommons.org/ Sign up] and join our sub-communities for tech/developers.

== Other forms of contribution ==

; [https://opensource.creativecommons.org/gsoc-2019/ Google Summer of Code]
: See CC participation on GSoC since 2006.
; [https://opensource.creativecommons.org/community/#mailing-lists Usability Testing]
: Participate in one of our regular usability tests for CC tools that we're actively working on (we'll give you a gift card!).
; [https://wiki.creativecommons.org/wiki/Translate Translate our Content]
: Find out how to help the Creative Commons community with translations.
; [https://github.com/creativecommons/cc-vocabulary Contribute To Design]
: Contribute to our brand new set of standard UI components and help us apply it to all the existing projects.

<br clear="all"/>

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

[[Category:Developer]]

__NOTOC__

License RDF

2019-11-13T23:12:00Z

CCID-timidrobot: updated repository link

Creative Commons provides information on licenses for three audiences: lawyers, humans and machines. The machine-readable information is described using [http://www.w3.org/RDF RDF] and made available from the [https://github.com/creativecommons/cc.licenserdf creativecommons/cc.licenserdf] git repository.

== File Naming ==

Files in the <code>license_rdf</code> module are named using the following convention:

<pre>creativecommons.org_license_[license-code]_[version]_[jurisdiction]_.rdf</pre>

More generally, you can take the URL of a license (i.e. <code>http://creativecommons.org/licenses/by/3.0/</code>), strip the protocol information (<code>http://</code>) and replace all forward-slashes (<code>/</code>) with underscores (<code>_</code>) to arrive at the base filename. [[Liblicense]] provides a function to perform this mapping for you.

== File Contents ==

Each file contains the RDF (encoded as RDF/XML) describing the particular license. Information described by the RDF includes:

* license name, including translations
* license description, including translations
* license properties, as described by [[ccREL]]

== Usages ==

The license RDF files are used in the following CC applications:

* The license engine
* [[OpenOfficeOrg Addin]]
* [[Liblicense]]

Legal Code Translation Policy

2019-09-17T17:55:43Z

CCID-timidrobot: updated dates to reflect international date format

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

Creative Commons has established the following Official Legal Code Translation Process and Policy (“Legal Code Translation Policy”) to facilitate adoption and understanding of our licenses as tools for sharing creative works and data. This Legal Code Translation Policy was established as of 2013 October 29 and is updated and revised by Creative Commons in its discretion. Any non-trivial revisions will be logged and dated at the bottom of this page.

'''Watch this explanatory video:'''

[[File:How-to-translate-licenses.png |link=https://www.youtube.com/watch?v=yhHPORrnMns]]

==Overview==
The legal code for the international Creative Commons licenses and for CC0 is designed for use worldwide, without any need for adaptation to local laws. For these tools to reach their fullest potential, CC encourages linguistic translations of the legal codes and deeds into as many languages as possible. This page describes the policy and process for developing official translations of Creative Commons legal code.

The process for developing new translations (each is called a “translation project”) is coordinated and overseen by CC’s legal team in collaboration with the global network team. Creative Commons reserves the exclusive right to approve and host official translations of its legal tools, as well as to modify this process and adjust translation projects at any time. Per our policy, each official translation is hosted at a specified uniform resource indicator on CC’s website. The English original and the official translations will all be treated as equivalents. Translations of CC licenses that are not made in accordance with this policy are unauthorized modifications of our licenses per the [[Modifying_the_CC_licenses#License_Modification_Policy|License Modification Policy]].

==Translation process==
===Step 1. Beginning new translation projects.===
Anyone may initiate a translation project with CC. To express interest, please email legal [at] creativecommons [dot] org identifying the language you would like to coordinate.

Note that CC’s policy is to publish a single, official translation for any given language unless an important reason exists to allow more than one. This mirrors CC’s policy for translations of deeds. Anyone wanting to coordinate translation projects is expected to accommodate and encourage participation of others in the CC community, including from other jurisdictions where the language is spoken. CC will help coordinate this collaboration.

Once a new translation project is begun, CC will update its [[Legal_Tools_Translation|public tracking chart]] and create and populate a language-specific translation page for public tracking, which will be continually updated by CC throughout the translation process.

===Step 2. Preparing the translation draft.===
Please refer to the [[Legal_tools_translation_guide|legal tools translation guide]] while creating your translation because it contains information about common issues that arise when translating the text of the licenses and CC0. When translating the 4.0 license suite, please begin with BY-NC-SA using the worksheet [[Legal_Code_Translation_Policy#Supporting_documents|here]]. Typically, teams begin only with BY-NC-SA and defer creating the other five licenses until after the public comment period. If you are translating CC0, use this [[Legal_Code_Translation_Policy#Supporting_documents|worksheet]].

Once the draft is complete, the translation team should send it to legal[at]creativecommons[dot]org, along with a writeup of the following:
*Explanation of word choice for the following terms:
**For version 4.0:
***Adapted Material
***Copyright and Similar Rights
***Downstream recipients
***Licensed Material
***Share
***ShareAlike
**For CC0:
***Copyright and Related Rights
***Affirmer
***Work
***License
***Waiver
*Description of which concepts were challenging to translate and how decisions were made
*Explanation of variations compared to terminology used on deed translation
*Explanation of variations compared to terminology used in ports of same language
*Names of translators

CC Legal will use this explanation during their Step 3 review, and will add it to language wiki page as part of public documentation of translation process.

===Step 3. Review of draft.===
CC Legal will conduct a review of the draft translation using the following checklist:
#Use Google Translate to read through from top to bottom, looking for glaring errors like commercial uses allowed in NC license, for example.
#Check that formatting is the same as the English - e.g., bold text.
#Use Google Translate to ensure there are no references to specific local legislation.
#Check that numbering and ordering of sections matches the English.
#Check that cross-references within text are correct.
#Make sure each defined term is in the same order as the English, and uses same capitalization throughout document.
#Go through relevant issues list, checking draft on each point using Google Translate and asking questions of team as needed: 4.0 issues list [[Legal_tools_translation_guide#4.0_license_suite_issues|here]], CC0 issues list [[Legal_tools_translation_guide#CC0_issues|here]]
#Check draft license translation against translations of deed to see if any notable changes in terminology. If yes, ask team for more information.

CC Legal will correspond with the translation team to clarify questions and make changes until a final draft translation is completed. Note that this step will reveal whether there are updates needed for the deed translations. The translation team is responsible for ensuring that the deed is fully translated. For help translating the deeds, see the instructions [[Translating_CC_Deeds|here]].

===Step 4. Public comment period.===
The public comment period is designed to ensure the highest quality linguistic translations possible. The translation team posts the draft on the CC wiki and in appropriate channels for public comment and feedback for a reasonable period of time (typically about 30-45 days, but may be shortened or extended if circumstances warrant). We encourage teams to seek as much input as possible, including by reaching out directly to local experts where possible.

At the conclusion of the public comment period, the translation team sends CC Legal a written summary of input received and how issues were resolved, along with the revised translation. CC Legal reviews the public comment summary from the translation team and asks questions as needed.

===Step 5. Creating the rest of the license suite.===
Note that this step only applies to translation of the version 4.0 CC license suite. Once all open issues are resolved with CC Legal after public comment, the translation team should create the other 5 licenses in the suite. For help in this process, refer to this [https://wiki.creativecommons.org/images/d/d1/Building_the_4.0_Suite.pdf guide]. Please consult CC Legal if you have any questions about word choices or anything else when creating the rest of the suite.

===Step 6. Readying files for staging server.===
At this point, the team converts the file(s) to HTML and sends the HTML file(s) to legal [at] creativecommons [dot] org. CC puts the file(s) on the staging server and sends the link(s) to the translation team.

''NOTE: To create the HTML files, we recommend using the English legal code pages - [https://creativecommons.org/licenses/by/4.0/legalcode https://creativecommons.org/licenses/by/4.0/legalcode] et. al. - as templates for your own. You can download the HTML page for each license by going to File -> Save Page As… and then select “Webpage, HTML only”, or whatever equivalent there is for your browser. In a text editor or HTML editor, open each file you have saved. Copy and paste your appropriate license text over the previous text, being careful not to copy over the existing HTML tags, and re-check the code to ensure that there are no mistakes. Please ensure that all the XHTML files are saved using UTF-8 encoding, which generally will be the default. Then save each file separately according to the following convention:''
*''CC0'':
** ''zero_1.0_[language code].html''

''(For example, "zero_1.0_fr.html" would be the naming for the French translation.)''

*''4.0''
**''by_4.0_[language code].html''
**''by-sa_4.0_[language code].html''
**'' [...]''

===Step 7. Final review.===

The translation team and CC Legal conduct a final review of all files on the staging server. This review should involve a check of both the substance and formatting of the files.

During this final review, CC Legal will use the following checklist:
#Use Google Translate to read through from top to bottom, looking for glaring errors like commercial uses allowed in NC license, for example. [Note: in the case of 4.0, this may be the first time the translations of licenses other than BY-NC-SA have been reviewed, so pay special attention to the changes made to those files.]
#Pay special attention to the license titles - are they correct and consistent throughout each file? Compare to titles on license deeds.
#Check that formatting appears correct as compared to English (same number of provisions, identical section numbering)
#Check that language list contains all published translations, including English
#Check all links in the files
#Check that deeds are fully translated
#For version 4.0, cut and paste each file into a Word doc and run the following comparisons:
#*BY-NC-SA to BY; compare to [https://wiki.creativecommons.org/images/c/c4/Making_BY_%28comparison%29.pdf this]
#*BY-NC-SA to BY-SA; compare to [https://wiki.creativecommons.org/images/6/64/Making_BY-SA_%28comparison%29.pdf this]
#*BY-NC-SA to BY-NC; compare to [https://wiki.creativecommons.org/images/6/6f/Making_BY-NC_%28comparison%29.pdf this]
#*BY-NC-SA to BY-ND; compare to [https://wiki.creativecommons.org/images/a/a2/Making_BY-ND_%28comparison%29.pdf this]
#*BY-NC-SA to BY-NC-ND; compare to [https://wiki.creativecommons.org/images/7/70/Making_BY-NC-ND_%28comparison%29.pdf this]

This stage continues until all identified problems are resolved.

===Step 8. General Counsel sign-off.===
Once the translation team and CC have signed off on all files, CC Legal sends the file(s) to General Counsel for final sign-off. CC Legal will coordinate details for blog post announcement with translation team at this point.

===Step 9. Pull request submitted.===
Once the General Counsel signs off, CC Legal submits a pull request on Github for the CC tech team with details about how language should be listed in the language lists on the footer of other published translations.

===Step 10. Publication.===
Once the pull request is merged by the tech team, CC will alert the translation team and publish announcement on the CC blog and social media. CC Legal will update wiki tracking sheet with publication dates. Translation team should update Transifex so that deeds link to published translation rather than English legal code.

==Key Resources==
* [[Legal tools translation guide]]
* [[Media:Building_the_4.0_Suite.pdf|Building the 4.0 Suite (.pdf)]]
* [[Media:Making_BY_(comparison).pdf|Making the BY license (comparison) (.pdf)]]
* [[Media:Making_BY-SA_(comparison).pdf|Making the BY-SA license (comparison) (.pdf)]]
* [[Media:Making_BY-NC_(comparison).pdf|Making the BY-NC license (comparison) (.pdf)]]
* [[Media:Making_BY-ND_(comparison).pdf|Making the BY-ND license (comparison) (.pdf)]]
* [[Media:Making_BY-NC-ND_(comparison).pdf|Making the BY-NC-ND license (comparison) (.pdf)]]
* 4.0 translation worksheet: [https://docs.google.com/document/d/1Vq6b89z6HWP1KZ66FNvx9E1GTeyAguPKk_zb4jXg4u8/ Google Doc], [[Media:4.0_translation_worksheet_(BY-NC-SA)(Feb_2015).odt|.odt]], [[Media:4.0_translation_worksheet_(BY-NC-SA)(Feb_2015).docx|.docx]], [[Media:4.0_translation_worksheet_(BY-NC-SA)(Feb_2015).pdf|.pdf]] (updated 2016 November 23)
* CC0 translation worksheet: [https://docs.google.com/document/d/12bmP4guaewK2U0eGQIFd-2N5XVlpB1rGULfxHthhODA/ Google Doc], [[Media:CC0_translation_worksheet.odt|.odt]], [[Media:CC0_translation_worksheet.docx|.docx]], [[Media:CC0_translation_worksheet.pdf|.pdf]] (updated 2016 November 23)

==Changelog==
* 2019 September 3: Revised process to better reflect current practice in terms of who and how translations are initiated, and added far more detail about different steps in the process.
* 2018 May 26: As of January 2018, the Affiliate Network transitioned to a Global Network, where everyone - individuals and institutions - are welcome. This policy reflects the new structure.
* 2017 March 14: Moved "Creating the files" from [[Legal tools translation guide]] to this page
* 2016 November 21: Removed the obligation to send the translation proposal using the forms
* 2016 November 4: Added detailed new steps to the translation process
* 2015 April 17: Clarification that unofficial translations violate License Modification Policy
* 2015 February 4: Change in supplemental material requirements, added CC0 translation worksheet
* 2014 February 4: Additional supplemental material requirements, new version of internal checklist posted
* 2014 January 24: More detailed summary.
* 2013 October 29: Policy established.

[[Category:Translation Project]]

Public reports

2019-07-01T17:54:17Z

CCID-timidrobot: removed link to Board_Reports

The purpose of this portal is to provide transparent access to public documents concerning the financial status and governance of the Creative Commons organization.

== Governance documents ==
* [[Media:Charter_cc.pdf|Incorporation document and charter]]
* [[Media:Bylaws_-_Amended_and_Restated_March_4_2018_%28final%29.pdf|Organization Bylaws (amended 2018 March)]]
** [[Media:CC_Amended_and_Restated_Bylaws_%28effective_6_Dec_2015%2C_amended_5_June_2016%29-1.pdf|Organization Bylaws (amended 2016 June)]]
** [[Media:CC_Amended_and_Restated_Bylaws_%28effective_6_Dec_2015%29.pdf|Organization Bylaws (amended 2015 December)]]
** [[Media:bylaws.pdf|Organization Bylaws (pre 2015 December)]]
* [[Media:1023.pdf|Form 1023 tax-exempt non-profit application and supplements]]
* [[Media:irsexempt.pdf|IRS tax-exempt determination letter]]
* [[Media:Audit_Committee_Charter_as_amended_2017-11-18_3.pdf|Audit Committee Charter]]
* [http://wiki.creativecommons.org/License_Versions License versioning process]

== Policies for staff, board and officers, and community members==
* [[Media:Codes_of_Conduct_for_Employees_%28approved_March_4%2C_2018%29%281%29.pdf|Code of Conduct (Employees) updated 2018 March]]
* [[Media:Creative_Commons_Code_of_Conduct_for_Directors_and_Officers_%28adopted_Mar_4_2018%29.pdf|Code of Conduct (Directors) updated 2018 March]]
* [https://creativecommons.org/wp-content/uploads/2017/11/Global_Network_Membership_Charter.pdf CC Global Network Charter, including Code of Conduct for all participants]
* [[Media:Code_of_Conduct_CC.pdf|Summit Code of Conduct, updated in advance of each Summit]]
* [[Media:Final_US_employee_handbook.pdf|Creative Commons Employee Handbook]]
* [[Media:CAHandbookMay2018.pdf|0941176 B.C. LTD Employee Handbook]]

== Other policies==
* [http://creativecommons.org/terms Website terms of use]
* [http://creativecommons.org/policies Copyright and trademark policies]
* [http://creativecommons.org/privacy Privacy policy]
* [http://wiki.creativecommons.org/Lobbying Lobbying policy]
* [http://wiki.creativecommons.org/Internet_Services Affiliate Internet Services Policy]
* [http://wiki.creativecommons.org/Merchandising Merchandising Policy]
* [http://wiki.creativecommons.org/Policy_Advocacy_Guidelines Policy & Advocacy Guidelines]
* [https://creativecommons.github.io/community/code-of-conduct/enforcement/ Enforcement policy for our Slack and open source codes of conduct]

== Annual reports ==

''' Organizational strategy document '''
* [http://wiki.creativecommons.org/images/c/ce/Future-of-creative-commons.pdf The Future of Creative Commons], June 2013

''' Organization-wide report '''
* [https://stateof.creativecommons.org/ State of the Commons, 2017]
* [https://stateof.creativecommons.org/2016 State of the Commons, 2016]
* [https://stateof.creativecommons.org/2015 State of the Commons, 2015]
* [https://stateof.creativecommons.org/ State of the Commons, 2014]
* [http://teamopen.cc/thefuture/ 2013-2014]
* [http://dispatches.creativecommons.org/ 2011-2012]

''' Affiliate Network reports '''
* [http://wiki.creativecommons.org/Affiliate_Reporting/2010 2010]

== Funding sources ==
* Donor List: [https://creativecommons.org/supporters/ Supporters - Creative Commons]
* Public announcements of major grants:
** [http://creativecommons.org/weblog/entry/27097 Gates Foundation Department of Labor grantee assistance]
** [http://creativecommons.org/press-releases/entry/8175 Hewlett Foundation general operating and ccLearn]
** [http://creativecommons.org/press-releases/entry/7945 5 x 5 Funding Challenge]
** [http://creativecommons.org/press-releases/entry/8322 Omidyar Network]
** [http://creativecommons.org/press-releases/entry/26078 Nature Publishing Group]
** [http://creativecommons.org/press-releases/entry/7183 Technology company contributions]

== Other ==
* [[Media:Amended_DMCA_form.pdf|DMCA Designation of Agent to Receive Notification of Claimed Infringement]]

== Tax returns and audit information ==
''' 2017 '''
* [[Media:2017_Creative_Commons_Public_Disclosure_Client_Copy.pdf|IRS Form 990]]
* [[Media:Creative_Commons_2017_-_Final_FS_1002.pdf|Independent audit]]

''' 2016 '''
* [[Media:2016_990_Public_Filing.pdf|IRS Form 990]]
* [[Media:Creative_Commons_2016_Final_FS_11-8.pdf|Independent audit]]

''' 2015 '''
* [[Media:2015_CC.pdf|IRS Form 990]]
* [https://drive.google.com/open?id=0B2UhiNCe0qFcSmRQQUVkUlllem8 Independent audit]

''' 2014 '''
* [[Media:Creative_Commons_2014_Form_990_Public_Disclosure_Copy.pdf|IRS Form 990]]
* [https://drive.google.com/open?id=0B2UhiNCe0qFcSVNPMVdoMUxOdTA Independent audit]

''' 2013 '''
* [[Media:Creative_Commons_form990_2013.pdf|IRS Form 990]]
* [https://drive.google.com/open?id=0B2UhiNCe0qFcUFV1RVk0Rm0xQzg Independent audit]

''' 2012'''
* [[Media:990-2012B.pdf|IRS Form 990]]
* [[Media:2012_CC_Audited_Financials.pdf|Independent audit]]

''' 2011 '''
* [[Media:2011_Form_990_-_Public.pdf|IRS Form 990]]
* [[Media:2011_CC_Audited_Financials.pdf|Independent audit]]

''' 2010 '''
* [[Media:990-2010B.pdf|IRS Form 990]]
* [[Media:Audit2010.pdf|Independent audit]]

''' 2009 '''
* [[Media:990-2009.pdf|IRS Form 990]]
* [[Media:Audit2009.pdf|Independent audit]]

''' 2008 '''
* [[Media:990-2008.pdf|IRS Form 990]]
* [[Media:Audit2008.pdf|Independent audit]]

''' 2007 '''
* [[Media:990-2007.pdf|IRS Form 990]]
* [[Media:Audit2007.pdf|Independent audit]]

''' 2006 '''
* [[Media:990-2006.pdf|IRS Form 990]]
* [[Media:Audit2006.pdf|Independent audit]]

''' 2005 '''
* [[Media:990-2005.pdf|IRS Form 990]]
* [[Media:Audit2005.pdf|Independent audit]]

''' 2004 '''
* [[Media:990-2004.pdf|IRS Form 990]]
* [[Media:Audit2004.pdf|Independent audit]]

''' 2003 '''
* [[Media:990-2003.pdf|IRS Form 990]]
* [[Media:Audit2003.pdf|Independent audit]]

''' 2002 '''
* [[Media:990-2002.pdf|IRS Form 990]]
* [[Media:Audit2002.pdf|Independent audit]]

''' 2001 '''
* [[Media:990-2001.pdf|IRS Form 990]]

Translating CC Deeds

2019-06-21T16:00:22Z

CCID-timidrobot:

As of January 2018, the Affiliate Network transitioned to a Global Network, where everyone - individuals and institutions - are welcome. The Creative Commons Global Network works together to realize our shared values and build relationships around the world. '''Interested in signing up?''' Become a member at [https://network.creativecommons.org/ https://network.creativecommons.org/]. You can also join our [https://creativecommons.slack.com/messages/C9LNTF002/details/ Translation Working Group on Slack], to stay informed about materials that need to be translated or to suggest new materials.

Creative Commons uses [http://www.transifex.com Transifex] to manage translations for the website and our open source software projects. Information on translating using [[Translating PO Files|gettext and poEdit]] is also available.

To translate to the language that interests you, please follow these steps. Watch the video and read the instructions below:

[[File:How-to-translate-cc-deeds.png |link=https://www.youtube.com/watch?v=Rta2AlPww8M]]

===Sign up for an account===

1. If you were invited to join a CC translation team on Transifex, you should’ve received an email with a link to set up your account. Click on the link, then complete the signup form and click '''Create my account'''. After creating your account, you’ll be automatically taken to the page of the team that you were invited to. If you were not invited, go to http://www.transifex.com/signup/ and register for an account. You can also login using your Github, Google or LinkedIN account.

2. If asked to activate your account, check your email for the activation link and click on it.

3. On the first page of the welcome page, fill in your name and select '''Localization''' as your department and '''Translator''' as your job title. Hit '''Next''' to continue.

[[File:Transifex welcome step1.jpg|500px]]

4. The '''"Join an existing project"''' option will be pre-selected for you. Hit '''Next''' again.

[[File:Transifex welcome step2.jpg|500px]]

5. Finally, choose which languages you speak.

6. When you’re ready, click '''Get Started'''.

7. Choose '''Join an existing organization''' and search for '''Creative Commons'''. Choose '''Creative Commons - Share, Remix, Reuse — Legally''' (Organization: Creative Commons) or [https://www.transifex.com/nkinkade/CC/ visit this link].

[[File:Transifex-choose-CC.jpg|500px]]

===Join the CC teams===

1. Go to the Creative Commons project on Transifex, click '''Join team''' and choose the language you wish to translate into. The administrator will approve your request.

2. If a team already exists for the language that interests you, then click on that language and then click the '''Join team''' button, which will allow you to send a message to the coordinator for that language asking them to allow you to become a member of that team.

[[File:Transifex-teams-1.jpg|500px]]

3. If a team doesn't yet exist for the language that interests you then simply click the '''Request language''' button. This will send an email to the administrator for the Creative Commons project requesting the new team.

[[File:Transifex-teams-2.jpg|500px]]

===Start translating and/or reviewing===

# With Transifex, you can help to translate the [http://search.creativecommons.org CC Search section] of the website and the Deeds & Choosers.
# Login to Transifex and go to your language. Choose whether you want to translate CC Search or the Deeds & Choosers.
# Click on '''Translate'''.
# Go to the ''Untranslated'' tab and start translating. When you finish, click ''Save all''.
# You can also review the translations made by your team members. Click on ''Unreviewed'' and start reviewing. Don’t forget to add suggestions by clicking on the corresponding button below the translation.

=== General Notes About Translating ===

==== Using the Transifex Web editor ====

After you selected the untranslated strings, from the strings list on the left, click on the string you want to translate. Your selected string will appear on the right-hand side in the source strings box. Type your translation into the translation box below the source string box. Hit Save or you can hit Save all after you translate several strings. '''Remember:''' you only have to translate the language and preserve the formatting or other code that you may find in the original string.

A very interesting feature of Transifex is called '''Translation Memory (TM) and Concordance Search'''. If the string you're translating is similar to one that was translated in the past, a translation suggestion will appear in the Editor's Suggestions tab. The higher the percentage, the more similar the two source strings are. A 100% match means the two source strings are exactly the same. In such a case, it might be safe to reuse the translation. This is helping Creative Commons to keep the consistency of the Deeds translations.

Concordance search lets you search through the Translation Memory for a specific word or phrase and see how it was translated in other places. This is useful when there's no TM suggestion for a string, but you still want to see how something was translated elsewhere. [https://docs.transifex.com/translation/using-translation-memory-and-concordance-search Read more about this feature at Transifex.]

During the translation process, you can refer to the [https://docs.transifex.com Help section on Transifex]. You can also check any unknown words that you may encounter, in [https://docs.transifex.com/getting-started/glossary Transifex’s Glossary]. Don’t hesitate to ask the opinion of other team members

==== How to handle ${} or %() in strings ====

When you see "${license_name}" or "%(license_name)s" in a string, that indicates a substitution (for the real license name). These are placeholders that the translation machinery uses; if you modify this placeholder, the real license name will never be substituted into your string.

As a result, '''DO NOT''':

* Translate the text ("license_name") into your own language
* Remove the text
* Reverse the order of characters because you have a right-to-left language (ie, "{license_name}$")
* If the text uses the %(), do not remove the trailing character after the close of the parenthesis (i.e. the 's' in "%(license_name)s")

==== HTML links in strings (i.e., <a href="[someurl]">[sometext]</a>) ====

When you encounter an HTML link in a string, you must not translate anything inside of the angle brackets. In the example above, you would '''only''' translate ''[sometext]'', and the rest must be carried into the translation without any changes.

==== Whitespace Characters ====

Sometimes you'll see <code>\t</code> or <code>\n</code> in strings. These are left-over from the source files and can be safely omitted.

==== Wiki Links ====

Some text contains links to the CC Wiki for more information (ie, issues surrounding fair use, public domain, etc). If you would like to translate those pages in the CC Wiki, you may do so and substitute the link to the translated page in the translation. See [[CCWiki:Translate]] for instructions on translating wiki pages.

[[Category:Translation Project]]

==== When Does The Server Get Updated? ====

The live site however is updated with the newest translations every hour. However, caching may delay how soon it appears.

[[Category:Legal]]

IRC

2019-06-19T15:36:48Z

CCID-timidrobot:

== Overview ==
There is a Creative Commons IRC channel on the [http://freenode.net/ freenode] network, called '''[irc://irc.freenode.net/#creativecommons #creativecommons]''' <sup><span class="plainlinks">[http://webchat.freenode.net/?channels=creativecommons <font color="green">live connect</font>]</span></sup>

There is also a channel for CC's free software development work: '''[irc://irc.freenode.net/#creativecommons #creativecommons-dev]''' <sup><span class="plainlinks">[http://webchat.freenode.net/?channels=creativecommons-dev <font color="green">live connect</font>]</span></sup>

For those not familar with IRC have a look at the [http://en.wikipedia.org/wiki/Internet_Relay_Chat Wikipedia definition] and [http://en.wikipedia.org/wiki/List_of_IRC_clients download a software program] for your operating-system so you can participate in the CC channel.

* [[Getting started with IRC]]

==Code of Conduct==
As a global nonprofit committed to establishing inclusive community norms, all participants in the Creative Commons Slack Organization are expected to abide by our [https://wiki.creativecommons.org/wiki/Slack/Code_of_Conduct Code of Conduct].

==IRC/Slack Bridge ==
Creative Commons uses [https://github.com/ekmartin/slack-irc ekmartin/slack-irc] to mirror communication between the IRC [http://freenode.net/ freenode] network and Creative Commons Slack workspace:
{|
!IRC
!Slack
|-
|[irc://irc.freenode.net/#creativecommons <code>#creativecommons</code>]
|[https://creativecommons.slack.com/messages/C2BQ815JR <code>#general</code>]
|-
|[irc://irc.freenode.net/#creativecommons-dev <code>#creativecommons-dev</code>]
|[https://creativecommons.slack.com/messages/C2DUTAQJJ <code>#cc-developers</code>]
|-
|[irc://irc.freenode.net/#creativecommons-openedu <code>#creativecommons-openedu</code>]
|[https://creativecommons.slack.com/messages/C2S2MFAJW <code>#cc-openedu</code>]
|}
Also see [[IRC]].

Slack

2019-06-19T15:35:19Z

CCID-timidrobot:

=Slack for Creative Commons=

==What is Slack==
Slack is a chat client that allows us to chat with each other and engage with our community in real time and asynchronously.

==Why Slack?==
While IRC has been a good choice in the past, Slack is more mobile friendly and integrates with the workflows of users who are using Slack for other projects, creating a more robust (and chatty) community. In addition, Slack scores high for accessibility, public familiarity, and adoption. The best news? You don’t have to give up IRC if you don’t want to! We’ve built a bridge from IRC to Slack so you can continue hanging out in #creativecommons if that’s where you feel most comfortable.

==Slack Setup==
Because Slack is a web application, there’s no installation necessary. You can login online or download the [https://slack.com/downloads/osx desktop or mobile clients.]

==How to join Slack==
1. Steps to sign up:
[https://get.slack.help/hc/en-us/articles/218080037-Getting-started-for-new-users Access the “Steps for new users”] document
Note: We got in touch with Slack and they are in the process of translating their documents, but for now it’s English only.

2. Fill out the form here - https://slack-signup.creativecommons.org/

3. Accept the email invitation that is sent to you once you fill out the form.

4. Start in the #general channel, and explore the other channels that may interest you!

==How to suggest a new channel==
We create channels based on how discussions are shaped around specific topics. Any channel with fewer than 10 users and little to no discussion in 30 days will be deleted.
'''Only admins can make a channel.'''
If you would like to suggest a channel via email, please email Jennie [mailto:jennie@creativecommons.org jennie@creativecommons.org] or ping her on Slack @jennierose

==Channel naming conventions==
* All channels begin with "cc-"
* Channels that end with -community are community channels, designed to find other people with your specific commons interest
* Regional channels will be formatted as follows: cc-region
* Naming conventions can be modified based on community input

==Selected Channels and their uses==
* cc-africa
** For discussion of cc-africa and activities
* cc-animals
** All cuteness, all the time
* cc-announcements
** Blog posts and conversation
* cc-arab-world
* cc-colombia
* cc-comms
* cc-copyrightreform
* cc-india
* cc-nederland
* cc-openedu-goals
* cc-turkey
* cc-uk
* cc-developers
** For chat related to CC's open source development community
* cc-gsoc
** For discussions related to CC's participation in Google Summer of Code
* cc-latinamerica
** For discussion of cc-latinamerica and activities
* awesomefund
** For discussions of the CC awesome fund
* cc-announcements
** For official Creative Commons announcements. Watch this channel for news that everyone should know
* cc-europe
** For discussion of cc-europe and activities
* cc-music
** For CC musicians
* cc-openedu
** For OER and related
* cc-openglam
* cc-reads
** Creative Commons reads
* cc-summit
** For summit related discussion
* general
** For saying hello and where all new users begin
* random
** For non-CC related chatter

==Slack Tips==
* '''Everything in Slack is public''' and is therefore potentially part of the public record (written words that are attributable back to you). Don’t say something on Slack that you wouldn’t feel comfortable appearing on the news.
* '''Slack provides some [https://get.slack.help/hc/en-us/articles/202288908-How-can-I-add-formatting-to-my-messages formatting tips]''' to make your messages extra fancy.
* '''If you customize your profile''' with your location or [http://pronoun.is personal pronoun,] consider also adding those details to the Last Name field so they appear alongside your messages. This is a great way to be remote-friendly and gender inclusive. Otherwise, your colleagues need to view your profile to see that information. Many people use airport codes instead of city names to indicate their location.
* '''The advanced settings section''' provides an option for ''only showing channels that have unread messages.'' This is useful if you’re a member of a lot of channels.
* '''Click the timestamp''' on any post to go to the archival view of it. This is helpful if you’d like to cross-post a link to a message in another channel.
* '''When using Slack on mobile:''' mentioning someone in a channel they aren’t in won’t notify them, and you won’t get the option to invite someone after mentioning them
* '''Feel free to pop in and out of channels.''' You can /mute channels (so you only receive messages when your name or @channel is mentioned) or leave channels if they become overwhelming.
* '''If you’re interested in tracking specific keywords across Slack,''' set up [https://get.slack.help/hc/en-us/articles/201398467-Highlight-word-notifications highlight word notifications].
* '''To add an RSS feed to any channel''', type /feed subscribe "RSS URL"
* '''Never use Slack to share secure information.''' If you need to share short bits of text securely, use a Pastebin or other means. If you want to say something private, it’s easy to ask someone to hop on a call. (See the /slack/#shortcuts">shortcuts below.)
* '''You can use Slack as an archival system.''' It has a [https://get.slack.help/hc/en-us/articles/202528808-Searching-in-Slack powerful search feature] and you can search specific channels or conversations.
* '''You can also search by tagged emoji.''' To see all messages tagged with a particular emoji, search Slack for has: (for example has::cc:).
* '''Set Slack boundaries when you need to be heads-down''' by [https://get.slack.help/hc/en-us/articles/201864558-Setting-your-Slack-status setting your status] to ''Away''. If you use Slack on mobile, you can '''prevent direct messages and mentions from pinging you when you’re not working'''. Just set your phone to Do Not Disturb mode or temporarily turn off notifications from the Slack app. Don’t worry — though we have different schedules and may message each other at strange times, there’s no expectation for people to respond when they’re not working.
* '''Praise your coworkers and community!''' If you’d like to praise someone for doing good work, start a message with love @username or :heart: @username.
* '''Use text encoding when pasting a large chunk of text.</strong> Use the + sign to the left of the text box to create a snippet. There will be an option to select how you would like to encode the text; select plain text to avoid smart quotes, if you’re pasting code.</li>
* '''Emojis come in different colors.''' Tired of tabbing through multiple skin color emoji to find the one you want or identify with? Click on the Emoji Deluxe picker (the smily face in the text box) - then click on the emoji in the bottom right corner. You can then select a default color going forward.
* '''Change your color scheme.''' You can change your color scheme by going to Preferences –> Theme –> Custom Theme. Paste the following for the US Design Standards theme: #112E51,#205493,#0071BC,#FFFFFF,#323A45,#FFFFFF,#4AA564,#981B1E
* '''Screen-sharing tip:''' If you want notifications to stop showing up so people don’t see them, hover over the Notification Center icon in the top right corner of your screen and '''Option or CTRL + click''' on it. Repeat that to turn notifications back on.

==Frequently used emoji==
:check: = I did this or verified it was done

:plus: = I am a +1 for the above</p>

:100: = I am a SUPER +1 to the above OR this comment is keeping it 100 (as in, keeping it real, speaking the 100% truth)

:thumbsup: = Sounds good

:question: = I don’t understand this/needs followup

:point_up: = I would also say this (can mean “this is correct” if you are the decider)

:raised_hand: = I volunteer

:raising_hand: = Have time for a question? (Keep in mind that many folks strongly prefer that you also add what your question is about so they can determine its urgency.)

:facepalm: = Disbelief, shame, or exasperation.

:troll: = I’m intentionally [https://en.wikipedia.org/wiki/Internet_troll" trolling you or making a joke

==Shortcuts==
Type @channel [message] to send your message to everyone in the channel. Use sparingly and only if everyone in the channel needs to see your message.

Type @here [message] to send your message to everyone in the channel with Slack open at a desktop computer. Don’t use this as a softer version of an @channel because there will be no notification for anyone who wasn’t at their computer.

Type /me [message] to “emote” your message. (Just try it.)

Type /mute to suppress notifications from the channel you’re currently in. You can also turn on desktop notifications for specific channels.

Type /hangout to start a Google Hangout in the current channel.

Type [message XPOST #channel-name] to cross-post a message to a different channel while posting it.

Type /remind to remind yourself to do something in the future.

Type love @username for [message] to publicly praise and thank someone. If Charlie is in the channel, it will copy your message to #love.

Press Option + Up or Option + Down to switch between channels and direct messages.

Press Esc to mark all messages in the current channel as read.

Press Shift + Esc to mark all messages across all channels as read. Only do this if you’ve caught up in channels for your projects first.

Press Command + K or Command + T to switch between channels and direct messages by name.

Press Command + [ and Command + ] to jump back and forth along your history of DMs/channels.

To mark messages as unread, click a message on your phone and select mark unread or press Alt and then click your mouse to do so on your desktop.

==Code of Conduct==
As a global nonprofit committed to establishing inclusive community norms, all participants in the Creative Commons Slack Organization are expected to abide by our [https://wiki.creativecommons.org/wiki/Slack/Code_of_Conduct Code of Conduct].

==Attribution==
Portions of this text are derived from the [https://handbook.18f.gov/slack/ 18f Handbook's guide to Slack].

==IRC/Slack Bridge ==
Creative Commons uses [https://github.com/ekmartin/slack-irc ekmartin/slack-irc] to mirror communication between the IRC [http://freenode.net/ freenode] network and Creative Commons Slack workspace:
{|
!IRC
!Slack
|-
|[irc://irc.freenode.net/#creativecommons <code>#creativecommons</code>]
|[https://creativecommons.slack.com/messages/C2BQ815JR <code>#general</code>]
|-
|[irc://irc.freenode.net/#creativecommons-dev <code>#creativecommons-dev</code>]
|[https://creativecommons.slack.com/messages/C2DUTAQJJ <code>#cc-developers</code>]
|-
|[irc://irc.freenode.net/#creativecommons-openedu <code>#creativecommons-openedu</code>]
|[https://creativecommons.slack.com/messages/C2S2MFAJW <code>#cc-openedu</code>]
|}
Also see [[IRC]].

Public reports

2019-06-11T14:50:17Z

CCID-timidrobot: Updated broken and absolute links with appropriate media links

The purpose of this portal is to provide transparent access to public documents concerning the financial status and governance of the Creative Commons organization.

== Governance documents ==
* [[Media:Charter_cc.pdf|Incorporation document and charter]]
* [[Media:Bylaws_-_Amended_and_Restated_March_4_2018_%28final%29.pdf|Organization Bylaws (amended 2018 March)]]
** [[Media:CC_Amended_and_Restated_Bylaws_%28effective_6_Dec_2015%2C_amended_5_June_2016%29-1.pdf|Organization Bylaws (amended 2016 June)]]
** [[Media:CC_Amended_and_Restated_Bylaws_%28effective_6_Dec_2015%29.pdf|Organization Bylaws (amended 2015 December)]]
** [[Media:bylaws.pdf|Organization Bylaws (pre 2015 December)]]
* [[Media:1023.pdf|Form 1023 tax-exempt non-profit application and supplements]]
* [[Media:irsexempt.pdf|IRS tax-exempt determination letter]]
* [http://wiki.creativecommons.org/Board_Reports Board of Directors meeting summaries]
* [[Media:Audit_Committee_Charter_as_amended_2017-11-18_3.pdf|Audit Committee Charter]]
* [http://wiki.creativecommons.org/License_Versions License versioning process]

== Policies for staff, board and officers, and community members==
* [[Media:Codes_of_Conduct_for_Employees_%28approved_March_4%2C_2018%29%281%29.pdf|Code of Conduct (Employees) updated 2018 March]]
* [[Media:Creative_Commons_Code_of_Conduct_for_Directors_and_Officers_%28adopted_Mar_4_2018%29.pdf|Code of Conduct (Directors) updated 2018 March]]
* [https://creativecommons.org/wp-content/uploads/2017/11/Global_Network_Membership_Charter.pdf CC Global Network Charter, including Code of Conduct for all participants]
* [[Media:Code_of_Conduct_CC.pdf|Summit Code of Conduct, updated in advance of each Summit]]
* [[Media:Final_US_employee_handbook.pdf|Creative Commons Employee Handbook]]
* [[Media:CAHandbookMay2018.pdf|0941176 B.C. LTD Employee Handbook]]

== Other policies==
* [http://creativecommons.org/terms Website terms of use]
* [http://creativecommons.org/policies Copyright and trademark policies]
* [http://creativecommons.org/privacy Privacy policy]
* [http://wiki.creativecommons.org/Lobbying Lobbying policy]
* [http://wiki.creativecommons.org/Internet_Services Affiliate Internet Services Policy]
* [http://wiki.creativecommons.org/Merchandising Merchandising Policy]
* [http://wiki.creativecommons.org/Policy_Advocacy_Guidelines Policy & Advocacy Guidelines]
* [https://creativecommons.github.io/community/code-of-conduct/enforcement/ Enforcement policy for our Slack and open source codes of conduct]

== Annual reports ==

''' Organizational strategy document '''
* [http://wiki.creativecommons.org/images/c/ce/Future-of-creative-commons.pdf The Future of Creative Commons], June 2013

''' Organization-wide report '''
* [https://stateof.creativecommons.org/ State of the Commons, 2017]
* [https://stateof.creativecommons.org/2016 State of the Commons, 2016]
* [https://stateof.creativecommons.org/2015 State of the Commons, 2015]
* [https://stateof.creativecommons.org/ State of the Commons, 2014]
* [http://teamopen.cc/thefuture/ 2013-2014]
* [http://dispatches.creativecommons.org/ 2011-2012]

''' Affiliate Network reports '''
* [http://wiki.creativecommons.org/Affiliate_Reporting/2010 2010]

== Funding sources ==
* Donor List: [https://creativecommons.org/supporters/ Supporters - Creative Commons]
* Public announcements of major grants:
** [http://creativecommons.org/weblog/entry/27097 Gates Foundation Department of Labor grantee assistance]
** [http://creativecommons.org/press-releases/entry/8175 Hewlett Foundation general operating and ccLearn]
** [http://creativecommons.org/press-releases/entry/7945 5 x 5 Funding Challenge]
** [http://creativecommons.org/press-releases/entry/8322 Omidyar Network]
** [http://creativecommons.org/press-releases/entry/26078 Nature Publishing Group]
** [http://creativecommons.org/press-releases/entry/7183 Technology company contributions]

== Other ==
* [[Media:Amended_DMCA_form.pdf|DMCA Designation of Agent to Receive Notification of Claimed Infringement]]

== Tax returns and audit information ==
''' 2017 '''
* [[Media:2017_Creative_Commons_Public_Disclosure_Client_Copy.pdf|IRS Form 990]]
* [[Media:Creative_Commons_2017_-_Final_FS_1002.pdf|Independent audit]]

''' 2016 '''
* [[Media:2016_990_Public_Filing.pdf|IRS Form 990]]
* [[Media:Creative_Commons_2016_Final_FS_11-8.pdf|Independent audit]]

''' 2015 '''
* [[Media:2015_CC.pdf|IRS Form 990]]
* [https://drive.google.com/open?id=0B2UhiNCe0qFcSmRQQUVkUlllem8 Independent audit]

''' 2014 '''
* [[Media:Creative_Commons_2014_Form_990_Public_Disclosure_Copy.pdf|IRS Form 990]]
* [https://drive.google.com/open?id=0B2UhiNCe0qFcSVNPMVdoMUxOdTA Independent audit]

''' 2013 '''
* [[Media:Creative_Commons_form990_2013.pdf|IRS Form 990]]
* [https://drive.google.com/open?id=0B2UhiNCe0qFcUFV1RVk0Rm0xQzg Independent audit]

''' 2012'''
* [[Media:990-2012B.pdf|IRS Form 990]]
* [[Media:2012_CC_Audited_Financials.pdf|Independent audit]]

''' 2011 '''
* [[Media:2011_Form_990_-_Public.pdf|IRS Form 990]]
* [[Media:2011_CC_Audited_Financials.pdf|Independent audit]]

''' 2010 '''
* [[Media:990-2010B.pdf|IRS Form 990]]
* [[Media:Audit2010.pdf|Independent audit]]

''' 2009 '''
* [[Media:990-2009.pdf|IRS Form 990]]
* [[Media:Audit2009.pdf|Independent audit]]

''' 2008 '''
* [[Media:990-2008.pdf|IRS Form 990]]
* [[Media:Audit2008.pdf|Independent audit]]

''' 2007 '''
* [[Media:990-2007.pdf|IRS Form 990]]
* [[Media:Audit2007.pdf|Independent audit]]

''' 2006 '''
* [[Media:990-2006.pdf|IRS Form 990]]
* [[Media:Audit2006.pdf|Independent audit]]

''' 2005 '''
* [[Media:990-2005.pdf|IRS Form 990]]
* [[Media:Audit2005.pdf|Independent audit]]

''' 2004 '''
* [[Media:990-2004.pdf|IRS Form 990]]
* [[Media:Audit2004.pdf|Independent audit]]

''' 2003 '''
* [[Media:990-2003.pdf|IRS Form 990]]
* [[Media:Audit2003.pdf|Independent audit]]

''' 2002 '''
* [[Media:990-2002.pdf|IRS Form 990]]
* [[Media:Audit2002.pdf|Independent audit]]

''' 2001 '''
* [[Media:990-2001.pdf|IRS Form 990]]

File:Audit2002.pdf

2019-06-11T14:48:56Z

CCID-timidrobot:

File:Audit2003.pdf

2019-06-11T14:48:47Z

CCID-timidrobot:

File:Audit2004.pdf

2019-06-11T14:48:40Z

CCID-timidrobot:

File:Audit2005.pdf

2019-06-11T14:48:32Z

CCID-timidrobot:

File:Audit2006.pdf

2019-06-11T14:48:24Z

CCID-timidrobot: