https://wiki.creativecommons.org/api.php?action=feedcontributions&user=CCID-diane+peters&feedformat=atomCreative Commons - User contributions [en]2024-03-29T00:48:05ZUser contributionsMediaWiki 1.30.0https://wiki.creativecommons.org/index.php?title=Legal_code&diff=116957Legal code2018-11-29T21:50:36Z<p>CCID-diane peters: /* Elements of the license page that are not part of the legal code */</p>
<hr />
<div>Every Creative Commons license has three layers: the lawyer-readable legal code, the human-readable deed, and the machine-readable code. As the only legally-operative layer, the legal code is the primary layer of the CC licenses. It consists of the text of the licenses, as well as any meaningful formatting and other inseparable elements listed below.<br />
<br />
===Elements of the legal code===<br />
<br />
*Text of the license (excluding "Using Creative Commons licenses", the CC notice at bottom and disclaimer at the top)<br />
*Title of the license (including version number)<br />
*Formatting of license text (bold, italic, underline, etc.)<br />
*Numbering scheme<br />
<br />
===Elements of the license page that are not part of the legal code===<br />
Anything not specifically named as legal code above, including:<br />
<br />
*"CC is not a law firm" disclaimer at top<br />
*Creative Commons notice at bottom<br />
*"Using Creative Commons licenses" text<br />
*Formatting of text of notices/disclaimers (except that found in the disclaimer of warranties//limitation of liabilities section of the legal text)<br />
*Formatting of "Using Creative Commons Licenses" text<br />
*Links within the license for internal navigation<br />
*Flag or picture<br />
*Navigational links<br />
*External resources linked to from "Using Creative Commons Licenses" or elsewhere<br />
*Link color<br />
*Text color<br />
*Coloring of header and footer<br />
*Existence of shading of disclaimers and intro material<br />
*Coloring of shading of disclaimers and intro material<br />
*HTML and other coding that does not change the user's view of legal<br />
code elements<br />
<br />
==Maintenance of the legal code==<br />
<br />
CC has committed to maintaining the legal code of its licenses completely unchanged after publication. Licensors and licensees can depend on the text remaining static, and do not have to check back to see if anything has changed. <br />
<br />
Any change to the legal code itself requires CC to release a new version. Small errors may remain in the legal code and be noted as errata; these may be found separately on the [[Legalcode errata|errata page]] or otherwise maintained separately from the main legal code. <br />
<br />
Elements of the license page that are not legal code may be changed by CC in its discretion. For example, the disclaimer text may be altered, inter-language links included, or explanatory non-license text added. <br />
<br />
The legal code is currently maintained as part of the HTML files that are displayed, where the legal code itself is mixed in with non-legal elements such as stylistic display information and additional text. There does not currently (as of September 2013) exist a file with a canonical version of the legal code without the non-legal code elements of that page, such as the navigational and stylistic elements. <br />
<br />
There are proposals to maintain a canonical version of the legal code only, which have been set aside to be reconsidered sometime after the launch of 4.0. One presentation of this idea by CC staff [http://lists.ibiblio.org/pipermail/cc-devel/2013-April/001767.html is posted here].<br />
<br />
A note that on 27 June 2018, CC updated some of the design elements of the legal code pages, but did not change the legal code.<br />
<br />
==See also==<br />
<br />
* [[Legalcode errata|Errata in the legal code of various CC licenses]]<br />
* [[4.0_License_Errata_Annotation_Tool|Proposal for an errata annotation tool]]<br />
<br />
[[Category:Legal]]</div>CCID-diane petershttps://wiki.creativecommons.org/index.php?title=Public_reports&diff=116928Public reports2018-09-27T22:50:52Z<p>CCID-diane peters: /* Policies*/ split into two categories</p>
<hr />
<div>The purpose of this portal is to provide transparent access to public documents concerning the financial status and governance of the Creative Commons organization. <br />
<br />
== Tax returns and audit information == <br />
''' 2017 '''<br />
* IRS Form 990, coming soon<br />
* Independent audit, coming soon<br />
<br />
''' 2016 '''<br />
* [https://wiki.creativecommons.org/images/0/05/2016_990_Public_Filing.pdf IRS Form 990]<br />
* [https://wiki.creativecommons.org/images/e/e3/Creative_Commons_2016_Final_FS_11-8.pdf Independent audit] <br />
<br />
''' 2015 '''<br />
* [https://wiki.creativecommons.org/images/b/bc/2015_CC.pdf IRS Form 990]<br />
* [https://drive.google.com/open?id=0B2UhiNCe0qFcSmRQQUVkUlllem8 Independent audit]<br />
<br />
''' 2014 '''<br />
* [https://wiki.creativecommons.org/images/c/c6/Creative_Commons_2014_Form_990_Public_Disclosure_Copy.pdf IRS Form 990]<br />
* [https://drive.google.com/open?id=0B2UhiNCe0qFcSVNPMVdoMUxOdTA Independent audit]<br />
<br />
''' 2013 '''<br />
* [https://wiki.creativecommons.org/images/9/9f/Creative_Commons_form990_2013.pdf IRS Form 990]<br />
* [https://drive.google.com/open?id=0B2UhiNCe0qFcUFV1RVk0Rm0xQzg Independent audit]<br />
<br />
''' 2012'''<br />
* [http://wiki.creativecommons.org/images/3/31/990-2012B.pdf IRS Form 990]<br />
* [http://wiki.creativecommons.org/images/8/89/2012_CC_Audited_Financials.pdf Independent audit]<br />
<br />
''' 2011 '''<br />
* [http://wiki.creativecommons.org/images/8/8a/2011_Form_990_-_Public.pdf IRS Form 990]<br />
* [http://wiki.creativecommons.org/images/c/c0/2011_CC_Audited_Financials.pdf Independent audit]<br />
<br />
''' 2010 '''<br />
* [http://ibiblio.org/cccr/docs/990.pdf IRS Form 990]<br />
* [http://www.ibiblio.org/cccr/docs/audit.pdf Independent audit]<br />
<br />
''' 2009 '''<br />
* [http://www.ibiblio.org/cccr/docs/990-2009.pdf IRS Form 990]<br />
* [http://www.ibiblio.org/cccr/docs/audit2009.pdf Independent audit]<br />
<br />
''' 2008 '''<br />
* [http://www.ibiblio.org/cccr/docs/990-2008.pdf IRS Form 990]<br />
* [http://www.ibiblio.org/cccr/docs/audit2008.pdf Independent audit]<br />
<br />
''' 2007 '''<br />
* [http://www.ibiblio.org/cccr/docs/990-2007.pdf IRS Form 990]<br />
* [http://www.ibiblio.org/cccr/docs/audit2007.pdf Independent audit]<br />
<br />
''' 2006 '''<br />
* [http://www.ibiblio.org/cccr/docs/990-2006.pdf IRS Form 990]<br />
* [http://www.ibiblio.org/cccr/docs/audit2006.pdf Independent audit]<br />
<br />
''' 2005 '''<br />
* [http://www.ibiblio.org/cccr/docs/990-2005.pdf IRS Form 990]<br />
* [http://www.ibiblio.org/cccr/docs/audit2005.pdf Independent audit]<br />
<br />
''' 2004 '''<br />
* [http://www.ibiblio.org/cccr/docs/990-2004.pdf IRS Form 990]<br />
* [http://www.ibiblio.org/cccr/docs/audit2004.pdf Independent audit]<br />
<br />
''' 2003 '''<br />
* [http://www.ibiblio.org/cccr/docs/990-2003.pdf IRS Form 990]<br />
* [http://www.ibiblio.org/cccr/docs/audit2003.pdf Independent audit]<br />
<br />
''' 2002 '''<br />
* [http://www.ibiblio.org/cccr/docs/990-2002.pdf IRS Form 990]<br />
* [http://www.ibiblio.org/cccr/docs/audit2002.pdf Independent audit]<br />
<br />
''' 2001 '''<br />
* [http://www.ibiblio.org/cccr/docs/990-2001.pdf IRS Form 990]<br />
<br />
== Governance documents == <br />
* [http://ibiblio.org/cccr/docs/articles.pdf Incorporation document and charter]<br />
* [https://wiki.creativecommons.org/images/a/aa/Bylaws_-_Amended_and_Restated_March_4_2018_%28final%29.pdf Organization Bylaws (amended March 2018)]<br />
* [https://wiki.creativecommons.org/images/f/f9/CC_Amended_and_Restated_Bylaws_%28effective_6_Dec_2015%2C_amended_5_June_2016%29-1.pdf Organization Bylaws (amended June 2016)]<br />
* [https://wiki.creativecommons.org/images/a/a6/CC_Amended_and_Restated_Bylaws_%28effective_6_Dec_2015%29.pdf Organization Bylaws (amended Dec. 2015)]<br />
* [http://ibiblio.org/cccr/docs/bylaws.pdf Organization Bylaws (pre Dec. 2015)]<br />
* [http://www.ibiblio.org/cccr/docs/1023.pdf Form 1023 tax-exempt non-profit application and supplements]<br />
* [http://www.ibiblio.org/cccr/docs/irsexempt.pdf IRS tax-exempt determination letter]<br />
* [http://wiki.creativecommons.org/Board_Reports Board of Directors meeting summaries]<br />
* [http://ibiblio.org/cccr/docs/tab.pdf Technical Advisory Board charter]<br />
* [http://www.ibiblio.org/cccr/docs/auditcharter.pdf Audit Committee Charter]<br />
* [http://wiki.creativecommons.org/images/d/d7/SCIENCEADVISORYBOARDCHARGE.pdf Science Advisory Board charge]<br />
* [Board of Directors nomination process]<br />
* [http://wiki.creativecommons.org/License_Versions License versioning process]<br />
<br />
== Policies for staff, board and officers, and community members==<br />
* [https://wiki.creativecommons.org/images/e/e2/Codes_of_Conduct_for_Employees_%28approved_March_4%2C_2018%29%281%29.pdf Code of Conduct (Employees) updated March 2018]<br />
* [https://wiki.creativecommons.org/images/9/91/Creative_Commons_Code_of_Conduct_for_Directors_and_Officers_%28adopted_Mar_4_2018%29.pdf Code of Conduct(Directors) updated March 2018]<br />
* [https://creativecommons.org/wp-content/uploads/2017/11/Global_Network_Membership_Charter.pdf CC Global Network Charter, including Code of Conduct for all participants]<br />
* [https://wiki.creativecommons.org/images/c/c1/Code_of_Conduct_CC.pdf Summit Code of Conduct, updated in advance of each Summit]<br />
* [https://wiki.creativecommons.org/images/7/74/Final_US_employee_handbook.pdf Creative Commons Employee Handbook]<br />
* [https://wiki.creativecommons.org/images/e/e7/CAHandbookMay2018.pdf 0941176 B.C. LTD Employee Handbook]<br />
<br />
== Other policies==<br />
* [http://creativecommons.org/terms Website terms of use]<br />
* [http://creativecommons.org/policies Copyright and trademark policies]<br />
* [http://creativecommons.org/privacy Privacy policy]<br />
* [http://wiki.creativecommons.org/Lobbying Lobbying policy]<br />
* [http://wiki.creativecommons.org/MOU Affiliate Memorandum of Understanding (MOU) '''NO LONGER IN USE''']<br />
* [http://wiki.creativecommons.org/Internet_Services Affiliate Internet Services Policy]<br />
* [http://wiki.creativecommons.org/Merchandising Merchandising Policy] <br />
* [http://wiki.creativecommons.org/Language Language Policy]<br />
* [http://wiki.creativecommons.org/Policy_Advocacy_Guidelines Policy & Advocacy Guidelines]<br />
<br />
== Annual reports ==<br />
<br />
''' Organizational strategy document '''<br />
* [http://wiki.creativecommons.org/images/c/ce/Future-of-creative-commons.pdf The Future of Creative Commons], June 2013<br />
<br />
''' Organization-wide report '''<br />
* [https://stateof.creativecommons.org/2017 State of the Commons, 2017]<br />
* [https://stateof.creativecommons.org/2016 State of the Commons, 2016]<br />
* [https://stateof.creativecommons.org/2015 State of the Commons, 2015]<br />
* [https://stateof.creativecommons.org/ State of the Commons, 2014]<br />
* [http://teamopen.cc/thefuture/ 2013-2014]<br />
* [http://dispatches.creativecommons.org/ 2011-2012]<br />
<br />
''' Affiliate Network reports '''<br />
* [http://wiki.creativecommons.org/Affiliate_Reporting/2010 2010]<br />
<br />
== Funding sources ==<br />
* [https://creativecommons.net/supporters/ Donor list]<br />
* [https://creativecommons.net/figures/ Fundraising dashboard]<br />
* Public announcements of major grants:<br />
** [http://creativecommons.org/weblog/entry/27097 Gates Foundation Department of Labor grantee assistance]<br />
** [http://creativecommons.org/press-releases/entry/8175 Hewlett Foundation general operating and ccLearn]<br />
** [http://creativecommons.org/press-releases/entry/7945 5 x 5 Funding Challenge]<br />
** http://creativecommons.org/press-releases/entry/8322 Omidyar Network]<br />
** [http://creativecommons.org/press-releases/entry/26078 Nature Publishing Group]<br />
** [http://creativecommons.org/press-releases/entry/7183 Technology company contributions]<br />
<br />
== Other ==<br />
* [https://wiki.creativecommons.org/images/3/3a/Amended_DMCA_form.pdf DMCA Designation of Agent to Receive Notification of Claimed Infringement]</div>CCID-diane petershttps://wiki.creativecommons.org/index.php?title=Public_reports&diff=116919Public reports2018-09-26T22:02:09Z<p>CCID-diane peters: /* Policies */</p>
<hr />
<div>The purpose of this portal is to provide transparent access to public documents concerning the financial status and governance of the Creative Commons organization. <br />
<br />
== Tax returns and audit information == <br />
''' 2017 '''<br />
* IRS Form 990, coming soon<br />
* Independent audit, coming soon<br />
<br />
''' 2016 '''<br />
* [https://wiki.creativecommons.org/images/0/05/2016_990_Public_Filing.pdf IRS Form 990]<br />
* [https://wiki.creativecommons.org/images/e/e3/Creative_Commons_2016_Final_FS_11-8.pdf Independent audit] <br />
<br />
''' 2015 '''<br />
* [https://wiki.creativecommons.org/images/b/bc/2015_CC.pdf IRS Form 990]<br />
* [https://drive.google.com/open?id=0B2UhiNCe0qFcSmRQQUVkUlllem8 Independent audit]<br />
<br />
''' 2014 '''<br />
* [https://wiki.creativecommons.org/images/c/c6/Creative_Commons_2014_Form_990_Public_Disclosure_Copy.pdf IRS Form 990]<br />
* [https://drive.google.com/open?id=0B2UhiNCe0qFcSVNPMVdoMUxOdTA Independent audit]<br />
<br />
''' 2013 '''<br />
* [https://wiki.creativecommons.org/images/9/9f/Creative_Commons_form990_2013.pdf IRS Form 990]<br />
* [https://drive.google.com/open?id=0B2UhiNCe0qFcUFV1RVk0Rm0xQzg Independent audit]<br />
<br />
''' 2012'''<br />
* [http://wiki.creativecommons.org/images/3/31/990-2012B.pdf IRS Form 990]<br />
* [http://wiki.creativecommons.org/images/8/89/2012_CC_Audited_Financials.pdf Independent audit]<br />
<br />
''' 2011 '''<br />
* [http://wiki.creativecommons.org/images/8/8a/2011_Form_990_-_Public.pdf IRS Form 990]<br />
* [http://wiki.creativecommons.org/images/c/c0/2011_CC_Audited_Financials.pdf Independent audit]<br />
<br />
''' 2010 '''<br />
* [http://ibiblio.org/cccr/docs/990.pdf IRS Form 990]<br />
* [http://www.ibiblio.org/cccr/docs/audit.pdf Independent audit]<br />
<br />
''' 2009 '''<br />
* [http://www.ibiblio.org/cccr/docs/990-2009.pdf IRS Form 990]<br />
* [http://www.ibiblio.org/cccr/docs/audit2009.pdf Independent audit]<br />
<br />
''' 2008 '''<br />
* [http://www.ibiblio.org/cccr/docs/990-2008.pdf IRS Form 990]<br />
* [http://www.ibiblio.org/cccr/docs/audit2008.pdf Independent audit]<br />
<br />
''' 2007 '''<br />
* [http://www.ibiblio.org/cccr/docs/990-2007.pdf IRS Form 990]<br />
* [http://www.ibiblio.org/cccr/docs/audit2007.pdf Independent audit]<br />
<br />
''' 2006 '''<br />
* [http://www.ibiblio.org/cccr/docs/990-2006.pdf IRS Form 990]<br />
* [http://www.ibiblio.org/cccr/docs/audit2006.pdf Independent audit]<br />
<br />
''' 2005 '''<br />
* [http://www.ibiblio.org/cccr/docs/990-2005.pdf IRS Form 990]<br />
* [http://www.ibiblio.org/cccr/docs/audit2005.pdf Independent audit]<br />
<br />
''' 2004 '''<br />
* [http://www.ibiblio.org/cccr/docs/990-2004.pdf IRS Form 990]<br />
* [http://www.ibiblio.org/cccr/docs/audit2004.pdf Independent audit]<br />
<br />
''' 2003 '''<br />
* [http://www.ibiblio.org/cccr/docs/990-2003.pdf IRS Form 990]<br />
* [http://www.ibiblio.org/cccr/docs/audit2003.pdf Independent audit]<br />
<br />
''' 2002 '''<br />
* [http://www.ibiblio.org/cccr/docs/990-2002.pdf IRS Form 990]<br />
* [http://www.ibiblio.org/cccr/docs/audit2002.pdf Independent audit]<br />
<br />
''' 2001 '''<br />
* [http://www.ibiblio.org/cccr/docs/990-2001.pdf IRS Form 990]<br />
<br />
== Governance documents == <br />
* [http://ibiblio.org/cccr/docs/articles.pdf Incorporation document and charter]<br />
* [https://wiki.creativecommons.org/images/a/aa/Bylaws_-_Amended_and_Restated_March_4_2018_%28final%29.pdf Organization Bylaws (amended March 2018)]<br />
* [https://wiki.creativecommons.org/images/f/f9/CC_Amended_and_Restated_Bylaws_%28effective_6_Dec_2015%2C_amended_5_June_2016%29-1.pdf Organization Bylaws (amended June 2016)]<br />
* [https://wiki.creativecommons.org/images/a/a6/CC_Amended_and_Restated_Bylaws_%28effective_6_Dec_2015%29.pdf Organization Bylaws (amended Dec. 2015)]<br />
* [http://ibiblio.org/cccr/docs/bylaws.pdf Organization Bylaws (pre Dec. 2015)]<br />
* [http://www.ibiblio.org/cccr/docs/1023.pdf Form 1023 tax-exempt non-profit application and supplements]<br />
* [http://www.ibiblio.org/cccr/docs/irsexempt.pdf IRS tax-exempt determination letter]<br />
* [http://wiki.creativecommons.org/Board_Reports Board of Directors meeting summaries]<br />
* [http://ibiblio.org/cccr/docs/tab.pdf Technical Advisory Board charter]<br />
* [http://www.ibiblio.org/cccr/docs/auditcharter.pdf Audit Committee Charter]<br />
* [http://wiki.creativecommons.org/images/d/d7/SCIENCEADVISORYBOARDCHARGE.pdf Science Advisory Board charge]<br />
* [Board of Directors nomination process]<br />
* [http://wiki.creativecommons.org/License_Versions License versioning process]<br />
<br />
== Policies ==<br />
* [https://wiki.creativecommons.org/images/e/e2/Codes_of_Conduct_for_Employees_%28approved_March_4%2C_2018%29%281%29.pdf Code of Conduct (Employees) updated March 2018]<br />
* [https://wiki.creativecommons.org/images/9/91/Creative_Commons_Code_of_Conduct_for_Directors_and_Officers_%28adopted_Mar_4_2018%29.pdf Code of Conduct(Directors) updated March 2018]<br />
* [https://creativecommons.org/wp-content/uploads/2017/11/Global_Network_Membership_Charter.pdf CC Global Network Charter, including Code of Conduct for all participants]<br />
* [https://wiki.creativecommons.org/images/c/c1/Code_of_Conduct_CC.pdf Summit Code of Conduct, updated in advance of each Summit]<br />
* [http://creativecommons.org/terms Website terms of use]<br />
* [http://creativecommons.org/policies Copyright and trademark policies]<br />
* [http://creativecommons.org/privacy Privacy policy]<br />
* [http://wiki.creativecommons.org/Lobbying Lobbying policy]<br />
* [http://wiki.creativecommons.org/MOU Affiliate Memorandum of Understanding (MOU) '''NO LONGER IN USE''']<br />
* [http://wiki.creativecommons.org/Internet_Services Affiliate Internet Services Policy]<br />
* [http://wiki.creativecommons.org/Merchandising Merchandising Policy] <br />
* [http://wiki.creativecommons.org/Language Language Policy]<br />
* [http://wiki.creativecommons.org/Policy_Advocacy_Guidelines Policy & Advocacy Guidelines]<br />
<br />
== Annual reports ==<br />
<br />
''' Organizational strategy document '''<br />
* [http://wiki.creativecommons.org/images/c/ce/Future-of-creative-commons.pdf The Future of Creative Commons], June 2013<br />
<br />
''' Organization-wide report '''<br />
* [https://stateof.creativecommons.org/2017 State of the Commons, 2017]<br />
* [https://stateof.creativecommons.org/2016 State of the Commons, 2016]<br />
* [https://stateof.creativecommons.org/2015 State of the Commons, 2015]<br />
* [https://stateof.creativecommons.org/ State of the Commons, 2014]<br />
* [http://teamopen.cc/thefuture/ 2013-2014]<br />
* [http://dispatches.creativecommons.org/ 2011-2012]<br />
<br />
''' Affiliate Network reports '''<br />
* [http://wiki.creativecommons.org/Affiliate_Reporting/2010 2010]<br />
<br />
== Funding sources ==<br />
* [https://creativecommons.net/supporters/ Donor list]<br />
* [https://creativecommons.net/figures/ Fundraising dashboard]<br />
* Public announcements of major grants:<br />
** [http://creativecommons.org/weblog/entry/27097 Gates Foundation Department of Labor grantee assistance]<br />
** [http://creativecommons.org/press-releases/entry/8175 Hewlett Foundation general operating and ccLearn]<br />
** [http://creativecommons.org/press-releases/entry/7945 5 x 5 Funding Challenge]<br />
** http://creativecommons.org/press-releases/entry/8322 Omidyar Network]<br />
** [http://creativecommons.org/press-releases/entry/26078 Nature Publishing Group]<br />
** [http://creativecommons.org/press-releases/entry/7183 Technology company contributions]<br />
<br />
== Other ==<br />
* [https://wiki.creativecommons.org/images/3/3a/Amended_DMCA_form.pdf DMCA Designation of Agent to Receive Notification of Claimed Infringement]</div>CCID-diane petershttps://wiki.creativecommons.org/index.php?title=Public_reports&diff=116918Public reports2018-09-26T22:00:42Z<p>CCID-diane peters: /* Policies */</p>
<hr />
<div>The purpose of this portal is to provide transparent access to public documents concerning the financial status and governance of the Creative Commons organization. <br />
<br />
== Tax returns and audit information == <br />
''' 2017 '''<br />
* IRS Form 990, coming soon<br />
* Independent audit, coming soon<br />
<br />
''' 2016 '''<br />
* [https://wiki.creativecommons.org/images/0/05/2016_990_Public_Filing.pdf IRS Form 990]<br />
* [https://wiki.creativecommons.org/images/e/e3/Creative_Commons_2016_Final_FS_11-8.pdf Independent audit] <br />
<br />
''' 2015 '''<br />
* [https://wiki.creativecommons.org/images/b/bc/2015_CC.pdf IRS Form 990]<br />
* [https://drive.google.com/open?id=0B2UhiNCe0qFcSmRQQUVkUlllem8 Independent audit]<br />
<br />
''' 2014 '''<br />
* [https://wiki.creativecommons.org/images/c/c6/Creative_Commons_2014_Form_990_Public_Disclosure_Copy.pdf IRS Form 990]<br />
* [https://drive.google.com/open?id=0B2UhiNCe0qFcSVNPMVdoMUxOdTA Independent audit]<br />
<br />
''' 2013 '''<br />
* [https://wiki.creativecommons.org/images/9/9f/Creative_Commons_form990_2013.pdf IRS Form 990]<br />
* [https://drive.google.com/open?id=0B2UhiNCe0qFcUFV1RVk0Rm0xQzg Independent audit]<br />
<br />
''' 2012'''<br />
* [http://wiki.creativecommons.org/images/3/31/990-2012B.pdf IRS Form 990]<br />
* [http://wiki.creativecommons.org/images/8/89/2012_CC_Audited_Financials.pdf Independent audit]<br />
<br />
''' 2011 '''<br />
* [http://wiki.creativecommons.org/images/8/8a/2011_Form_990_-_Public.pdf IRS Form 990]<br />
* [http://wiki.creativecommons.org/images/c/c0/2011_CC_Audited_Financials.pdf Independent audit]<br />
<br />
''' 2010 '''<br />
* [http://ibiblio.org/cccr/docs/990.pdf IRS Form 990]<br />
* [http://www.ibiblio.org/cccr/docs/audit.pdf Independent audit]<br />
<br />
''' 2009 '''<br />
* [http://www.ibiblio.org/cccr/docs/990-2009.pdf IRS Form 990]<br />
* [http://www.ibiblio.org/cccr/docs/audit2009.pdf Independent audit]<br />
<br />
''' 2008 '''<br />
* [http://www.ibiblio.org/cccr/docs/990-2008.pdf IRS Form 990]<br />
* [http://www.ibiblio.org/cccr/docs/audit2008.pdf Independent audit]<br />
<br />
''' 2007 '''<br />
* [http://www.ibiblio.org/cccr/docs/990-2007.pdf IRS Form 990]<br />
* [http://www.ibiblio.org/cccr/docs/audit2007.pdf Independent audit]<br />
<br />
''' 2006 '''<br />
* [http://www.ibiblio.org/cccr/docs/990-2006.pdf IRS Form 990]<br />
* [http://www.ibiblio.org/cccr/docs/audit2006.pdf Independent audit]<br />
<br />
''' 2005 '''<br />
* [http://www.ibiblio.org/cccr/docs/990-2005.pdf IRS Form 990]<br />
* [http://www.ibiblio.org/cccr/docs/audit2005.pdf Independent audit]<br />
<br />
''' 2004 '''<br />
* [http://www.ibiblio.org/cccr/docs/990-2004.pdf IRS Form 990]<br />
* [http://www.ibiblio.org/cccr/docs/audit2004.pdf Independent audit]<br />
<br />
''' 2003 '''<br />
* [http://www.ibiblio.org/cccr/docs/990-2003.pdf IRS Form 990]<br />
* [http://www.ibiblio.org/cccr/docs/audit2003.pdf Independent audit]<br />
<br />
''' 2002 '''<br />
* [http://www.ibiblio.org/cccr/docs/990-2002.pdf IRS Form 990]<br />
* [http://www.ibiblio.org/cccr/docs/audit2002.pdf Independent audit]<br />
<br />
''' 2001 '''<br />
* [http://www.ibiblio.org/cccr/docs/990-2001.pdf IRS Form 990]<br />
<br />
== Governance documents == <br />
* [http://ibiblio.org/cccr/docs/articles.pdf Incorporation document and charter]<br />
* [https://wiki.creativecommons.org/images/a/aa/Bylaws_-_Amended_and_Restated_March_4_2018_%28final%29.pdf Organization Bylaws (amended March 2018)]<br />
* [https://wiki.creativecommons.org/images/f/f9/CC_Amended_and_Restated_Bylaws_%28effective_6_Dec_2015%2C_amended_5_June_2016%29-1.pdf Organization Bylaws (amended June 2016)]<br />
* [https://wiki.creativecommons.org/images/a/a6/CC_Amended_and_Restated_Bylaws_%28effective_6_Dec_2015%29.pdf Organization Bylaws (amended Dec. 2015)]<br />
* [http://ibiblio.org/cccr/docs/bylaws.pdf Organization Bylaws (pre Dec. 2015)]<br />
* [http://www.ibiblio.org/cccr/docs/1023.pdf Form 1023 tax-exempt non-profit application and supplements]<br />
* [http://www.ibiblio.org/cccr/docs/irsexempt.pdf IRS tax-exempt determination letter]<br />
* [http://wiki.creativecommons.org/Board_Reports Board of Directors meeting summaries]<br />
* [http://ibiblio.org/cccr/docs/tab.pdf Technical Advisory Board charter]<br />
* [http://www.ibiblio.org/cccr/docs/auditcharter.pdf Audit Committee Charter]<br />
* [http://wiki.creativecommons.org/images/d/d7/SCIENCEADVISORYBOARDCHARGE.pdf Science Advisory Board charge]<br />
* [Board of Directors nomination process]<br />
* [http://wiki.creativecommons.org/License_Versions License versioning process]<br />
<br />
== Policies ==<br />
* [https://wiki.creativecommons.org/images/e/e2/Codes_of_Conduct_for_Employees_%28approved_March_4%2C_2018%29%281%29.pdf Code of Conduct (Employees) updated March 2018]<br />
* [https://wiki.creativecommons.org/images/9/91/Creative_Commons_Code_of_Conduct_for_Directors_and_Officers_%28adopted_Mar_4_2018%29.pdf Code of Conduct(Directors) updated March 2018]<br />
* [https://creativecommons.org/wp-content/uploads/2017/11/Global_Network_Membership_Charter.pdf CC Global Network Charter, including Code of Conduct for all participants]<br />
* [https://wiki.creativecommons.org/images/c/c1/Code_of_Conduct_CC.pdf Summit Code of Conduct, updated annually]<br />
* [http://creativecommons.org/terms Website terms of use]<br />
* [http://creativecommons.org/policies Copyright and trademark policies]<br />
* [http://creativecommons.org/privacy Privacy policy]<br />
* [http://wiki.creativecommons.org/Lobbying Lobbying policy]<br />
* [http://wiki.creativecommons.org/MOU Affiliate Memorandum of Understanding (MOU) '''NO LONGER IN USE''']<br />
* [http://wiki.creativecommons.org/Internet_Services Affiliate Internet Services Policy]<br />
* [http://wiki.creativecommons.org/Merchandising Merchandising Policy] <br />
* [http://wiki.creativecommons.org/Language Language Policy]<br />
* [http://wiki.creativecommons.org/Policy_Advocacy_Guidelines Policy & Advocacy Guidelines]<br />
<br />
== Annual reports ==<br />
<br />
''' Organizational strategy document '''<br />
* [http://wiki.creativecommons.org/images/c/ce/Future-of-creative-commons.pdf The Future of Creative Commons], June 2013<br />
<br />
''' Organization-wide report '''<br />
* [https://stateof.creativecommons.org/2017 State of the Commons, 2017]<br />
* [https://stateof.creativecommons.org/2016 State of the Commons, 2016]<br />
* [https://stateof.creativecommons.org/2015 State of the Commons, 2015]<br />
* [https://stateof.creativecommons.org/ State of the Commons, 2014]<br />
* [http://teamopen.cc/thefuture/ 2013-2014]<br />
* [http://dispatches.creativecommons.org/ 2011-2012]<br />
<br />
''' Affiliate Network reports '''<br />
* [http://wiki.creativecommons.org/Affiliate_Reporting/2010 2010]<br />
<br />
== Funding sources ==<br />
* [https://creativecommons.net/supporters/ Donor list]<br />
* [https://creativecommons.net/figures/ Fundraising dashboard]<br />
* Public announcements of major grants:<br />
** [http://creativecommons.org/weblog/entry/27097 Gates Foundation Department of Labor grantee assistance]<br />
** [http://creativecommons.org/press-releases/entry/8175 Hewlett Foundation general operating and ccLearn]<br />
** [http://creativecommons.org/press-releases/entry/7945 5 x 5 Funding Challenge]<br />
** http://creativecommons.org/press-releases/entry/8322 Omidyar Network]<br />
** [http://creativecommons.org/press-releases/entry/26078 Nature Publishing Group]<br />
** [http://creativecommons.org/press-releases/entry/7183 Technology company contributions]<br />
<br />
== Other ==<br />
* [https://wiki.creativecommons.org/images/3/3a/Amended_DMCA_form.pdf DMCA Designation of Agent to Receive Notification of Claimed Infringement]</div>CCID-diane petershttps://wiki.creativecommons.org/index.php?title=Public_reports&diff=116917Public reports2018-09-26T21:59:31Z<p>CCID-diane peters: /* Policies */</p>
<hr />
<div>The purpose of this portal is to provide transparent access to public documents concerning the financial status and governance of the Creative Commons organization. <br />
<br />
== Tax returns and audit information == <br />
''' 2017 '''<br />
* IRS Form 990, coming soon<br />
* Independent audit, coming soon<br />
<br />
''' 2016 '''<br />
* [https://wiki.creativecommons.org/images/0/05/2016_990_Public_Filing.pdf IRS Form 990]<br />
* [https://wiki.creativecommons.org/images/e/e3/Creative_Commons_2016_Final_FS_11-8.pdf Independent audit] <br />
<br />
''' 2015 '''<br />
* [https://wiki.creativecommons.org/images/b/bc/2015_CC.pdf IRS Form 990]<br />
* [https://drive.google.com/open?id=0B2UhiNCe0qFcSmRQQUVkUlllem8 Independent audit]<br />
<br />
''' 2014 '''<br />
* [https://wiki.creativecommons.org/images/c/c6/Creative_Commons_2014_Form_990_Public_Disclosure_Copy.pdf IRS Form 990]<br />
* [https://drive.google.com/open?id=0B2UhiNCe0qFcSVNPMVdoMUxOdTA Independent audit]<br />
<br />
''' 2013 '''<br />
* [https://wiki.creativecommons.org/images/9/9f/Creative_Commons_form990_2013.pdf IRS Form 990]<br />
* [https://drive.google.com/open?id=0B2UhiNCe0qFcUFV1RVk0Rm0xQzg Independent audit]<br />
<br />
''' 2012'''<br />
* [http://wiki.creativecommons.org/images/3/31/990-2012B.pdf IRS Form 990]<br />
* [http://wiki.creativecommons.org/images/8/89/2012_CC_Audited_Financials.pdf Independent audit]<br />
<br />
''' 2011 '''<br />
* [http://wiki.creativecommons.org/images/8/8a/2011_Form_990_-_Public.pdf IRS Form 990]<br />
* [http://wiki.creativecommons.org/images/c/c0/2011_CC_Audited_Financials.pdf Independent audit]<br />
<br />
''' 2010 '''<br />
* [http://ibiblio.org/cccr/docs/990.pdf IRS Form 990]<br />
* [http://www.ibiblio.org/cccr/docs/audit.pdf Independent audit]<br />
<br />
''' 2009 '''<br />
* [http://www.ibiblio.org/cccr/docs/990-2009.pdf IRS Form 990]<br />
* [http://www.ibiblio.org/cccr/docs/audit2009.pdf Independent audit]<br />
<br />
''' 2008 '''<br />
* [http://www.ibiblio.org/cccr/docs/990-2008.pdf IRS Form 990]<br />
* [http://www.ibiblio.org/cccr/docs/audit2008.pdf Independent audit]<br />
<br />
''' 2007 '''<br />
* [http://www.ibiblio.org/cccr/docs/990-2007.pdf IRS Form 990]<br />
* [http://www.ibiblio.org/cccr/docs/audit2007.pdf Independent audit]<br />
<br />
''' 2006 '''<br />
* [http://www.ibiblio.org/cccr/docs/990-2006.pdf IRS Form 990]<br />
* [http://www.ibiblio.org/cccr/docs/audit2006.pdf Independent audit]<br />
<br />
''' 2005 '''<br />
* [http://www.ibiblio.org/cccr/docs/990-2005.pdf IRS Form 990]<br />
* [http://www.ibiblio.org/cccr/docs/audit2005.pdf Independent audit]<br />
<br />
''' 2004 '''<br />
* [http://www.ibiblio.org/cccr/docs/990-2004.pdf IRS Form 990]<br />
* [http://www.ibiblio.org/cccr/docs/audit2004.pdf Independent audit]<br />
<br />
''' 2003 '''<br />
* [http://www.ibiblio.org/cccr/docs/990-2003.pdf IRS Form 990]<br />
* [http://www.ibiblio.org/cccr/docs/audit2003.pdf Independent audit]<br />
<br />
''' 2002 '''<br />
* [http://www.ibiblio.org/cccr/docs/990-2002.pdf IRS Form 990]<br />
* [http://www.ibiblio.org/cccr/docs/audit2002.pdf Independent audit]<br />
<br />
''' 2001 '''<br />
* [http://www.ibiblio.org/cccr/docs/990-2001.pdf IRS Form 990]<br />
<br />
== Governance documents == <br />
* [http://ibiblio.org/cccr/docs/articles.pdf Incorporation document and charter]<br />
* [https://wiki.creativecommons.org/images/a/aa/Bylaws_-_Amended_and_Restated_March_4_2018_%28final%29.pdf Organization Bylaws (amended March 2018)]<br />
* [https://wiki.creativecommons.org/images/f/f9/CC_Amended_and_Restated_Bylaws_%28effective_6_Dec_2015%2C_amended_5_June_2016%29-1.pdf Organization Bylaws (amended June 2016)]<br />
* [https://wiki.creativecommons.org/images/a/a6/CC_Amended_and_Restated_Bylaws_%28effective_6_Dec_2015%29.pdf Organization Bylaws (amended Dec. 2015)]<br />
* [http://ibiblio.org/cccr/docs/bylaws.pdf Organization Bylaws (pre Dec. 2015)]<br />
* [http://www.ibiblio.org/cccr/docs/1023.pdf Form 1023 tax-exempt non-profit application and supplements]<br />
* [http://www.ibiblio.org/cccr/docs/irsexempt.pdf IRS tax-exempt determination letter]<br />
* [http://wiki.creativecommons.org/Board_Reports Board of Directors meeting summaries]<br />
* [http://ibiblio.org/cccr/docs/tab.pdf Technical Advisory Board charter]<br />
* [http://www.ibiblio.org/cccr/docs/auditcharter.pdf Audit Committee Charter]<br />
* [http://wiki.creativecommons.org/images/d/d7/SCIENCEADVISORYBOARDCHARGE.pdf Science Advisory Board charge]<br />
* [Board of Directors nomination process]<br />
* [http://wiki.creativecommons.org/License_Versions License versioning process]<br />
<br />
== Policies ==<br />
* [https://wiki.creativecommons.org/images/e/e2/Codes_of_Conduct_for_Employees_%28approved_March_4%2C_2018%29%281%29.pdf Code of Conduct (Employees) updated March 2018]<br />
* [https://wiki.creativecommons.org/images/9/91/Creative_Commons_Code_of_Conduct_for_Directors_and_Officers_%28adopted_Mar_4_2018%29.pdf Code of Conduct(Directors) updated March 2018]<br />
* [https://creativecommons.org/wp-content/uploads/2017/11/Global_Network_Membership_Charter.pdf CC Global Network Charter]<br />
* [http://creativecommons.org/terms Website terms of use]<br />
* [http://creativecommons.org/policies Copyright and trademark policies]<br />
* [http://creativecommons.org/privacy Privacy policy]<br />
* [http://wiki.creativecommons.org/Lobbying Lobbying policy]<br />
* [http://wiki.creativecommons.org/MOU Affiliate Memorandum of Understanding (MOU) '''NO LONGER IN USE''']<br />
* [http://wiki.creativecommons.org/Internet_Services Affiliate Internet Services Policy]<br />
* [http://wiki.creativecommons.org/Merchandising Merchandising Policy] <br />
* [http://wiki.creativecommons.org/Language Language Policy]<br />
* [http://wiki.creativecommons.org/Policy_Advocacy_Guidelines Policy & Advocacy Guidelines]<br />
<br />
== Annual reports ==<br />
<br />
''' Organizational strategy document '''<br />
* [http://wiki.creativecommons.org/images/c/ce/Future-of-creative-commons.pdf The Future of Creative Commons], June 2013<br />
<br />
''' Organization-wide report '''<br />
* [https://stateof.creativecommons.org/2017 State of the Commons, 2017]<br />
* [https://stateof.creativecommons.org/2016 State of the Commons, 2016]<br />
* [https://stateof.creativecommons.org/2015 State of the Commons, 2015]<br />
* [https://stateof.creativecommons.org/ State of the Commons, 2014]<br />
* [http://teamopen.cc/thefuture/ 2013-2014]<br />
* [http://dispatches.creativecommons.org/ 2011-2012]<br />
<br />
''' Affiliate Network reports '''<br />
* [http://wiki.creativecommons.org/Affiliate_Reporting/2010 2010]<br />
<br />
== Funding sources ==<br />
* [https://creativecommons.net/supporters/ Donor list]<br />
* [https://creativecommons.net/figures/ Fundraising dashboard]<br />
* Public announcements of major grants:<br />
** [http://creativecommons.org/weblog/entry/27097 Gates Foundation Department of Labor grantee assistance]<br />
** [http://creativecommons.org/press-releases/entry/8175 Hewlett Foundation general operating and ccLearn]<br />
** [http://creativecommons.org/press-releases/entry/7945 5 x 5 Funding Challenge]<br />
** http://creativecommons.org/press-releases/entry/8322 Omidyar Network]<br />
** [http://creativecommons.org/press-releases/entry/26078 Nature Publishing Group]<br />
** [http://creativecommons.org/press-releases/entry/7183 Technology company contributions]<br />
<br />
== Other ==<br />
* [https://wiki.creativecommons.org/images/3/3a/Amended_DMCA_form.pdf DMCA Designation of Agent to Receive Notification of Claimed Infringement]</div>CCID-diane petershttps://wiki.creativecommons.org/index.php?title=Public_reports&diff=116859Public reports2018-09-04T16:55:54Z<p>CCID-diane peters: /* Policies */</p>
<hr />
<div>The purpose of this portal is to provide transparent access to public documents concerning the financial status and governance of the Creative Commons organization. <br />
<br />
== Tax returns and audit information == <br />
''' 2016 '''<br />
* [https://wiki.creativecommons.org/images/0/05/2016_990_Public_Filing.pdf IRS Form 990]<br />
* [https://wiki.creativecommons.org/images/e/e3/Creative_Commons_2016_Final_FS_11-8.pdf Independent audit] <br />
<br />
''' 2015 '''<br />
* [https://wiki.creativecommons.org/images/b/bc/2015_CC.pdf IRS Form 990]<br />
* [https://drive.google.com/open?id=0B2UhiNCe0qFcSmRQQUVkUlllem8 Independent audit]<br />
<br />
''' 2014 '''<br />
* [https://wiki.creativecommons.org/images/c/c6/Creative_Commons_2014_Form_990_Public_Disclosure_Copy.pdf IRS Form 990]<br />
* [https://drive.google.com/open?id=0B2UhiNCe0qFcSVNPMVdoMUxOdTA Independent audit]<br />
<br />
''' 2013 '''<br />
* [https://wiki.creativecommons.org/images/9/9f/Creative_Commons_form990_2013.pdf IRS Form 990]<br />
* [https://drive.google.com/open?id=0B2UhiNCe0qFcUFV1RVk0Rm0xQzg Independent audit]<br />
<br />
''' 2012'''<br />
* [http://wiki.creativecommons.org/images/3/31/990-2012B.pdf IRS Form 990]<br />
* [http://wiki.creativecommons.org/images/8/89/2012_CC_Audited_Financials.pdf Independent audit]<br />
<br />
''' 2011 '''<br />
* [http://wiki.creativecommons.org/images/8/8a/2011_Form_990_-_Public.pdf IRS Form 990]<br />
* [http://wiki.creativecommons.org/images/c/c0/2011_CC_Audited_Financials.pdf Independent audit]<br />
<br />
''' 2010 '''<br />
* [http://ibiblio.org/cccr/docs/990.pdf IRS Form 990]<br />
* [http://www.ibiblio.org/cccr/docs/audit.pdf Independent audit]<br />
<br />
''' 2009 '''<br />
* [http://www.ibiblio.org/cccr/docs/990-2009.pdf IRS Form 990]<br />
* [http://www.ibiblio.org/cccr/docs/audit2009.pdf Independent audit]<br />
<br />
''' 2008 '''<br />
* [http://www.ibiblio.org/cccr/docs/990-2008.pdf IRS Form 990]<br />
* [http://www.ibiblio.org/cccr/docs/audit2008.pdf Independent audit]<br />
<br />
''' 2007 '''<br />
* [http://www.ibiblio.org/cccr/docs/990-2007.pdf IRS Form 990]<br />
* [http://www.ibiblio.org/cccr/docs/audit2007.pdf Independent audit]<br />
<br />
''' 2006 '''<br />
* [http://www.ibiblio.org/cccr/docs/990-2006.pdf IRS Form 990]<br />
* [http://www.ibiblio.org/cccr/docs/audit2006.pdf Independent audit]<br />
<br />
''' 2005 '''<br />
* [http://www.ibiblio.org/cccr/docs/990-2005.pdf IRS Form 990]<br />
* [http://www.ibiblio.org/cccr/docs/audit2005.pdf Independent audit]<br />
<br />
''' 2004 '''<br />
* [http://www.ibiblio.org/cccr/docs/990-2004.pdf IRS Form 990]<br />
* [http://www.ibiblio.org/cccr/docs/audit2004.pdf Independent audit]<br />
<br />
''' 2003 '''<br />
* [http://www.ibiblio.org/cccr/docs/990-2003.pdf IRS Form 990]<br />
* [http://www.ibiblio.org/cccr/docs/audit2003.pdf Independent audit]<br />
<br />
''' 2002 '''<br />
* [http://www.ibiblio.org/cccr/docs/990-2002.pdf IRS Form 990]<br />
* [http://www.ibiblio.org/cccr/docs/audit2002.pdf Independent audit]<br />
<br />
''' 2001 '''<br />
* [http://www.ibiblio.org/cccr/docs/990-2001.pdf IRS Form 990]<br />
<br />
== Governance documents == <br />
* [http://ibiblio.org/cccr/docs/articles.pdf Incorporation document and charter]<br />
* [https://wiki.creativecommons.org/images/a/aa/Bylaws_-_Amended_and_Restated_March_4_2018_%28final%29.pdf Organization Bylaws (amended March 2018)]<br />
* [https://wiki.creativecommons.org/images/f/f9/CC_Amended_and_Restated_Bylaws_%28effective_6_Dec_2015%2C_amended_5_June_2016%29-1.pdf Organization Bylaws (amended June 2016)]<br />
* [https://wiki.creativecommons.org/images/a/a6/CC_Amended_and_Restated_Bylaws_%28effective_6_Dec_2015%29.pdf Organization Bylaws (amended Dec. 2015)]<br />
* [http://ibiblio.org/cccr/docs/bylaws.pdf Organization Bylaws (pre Dec. 2015)]<br />
* [http://www.ibiblio.org/cccr/docs/1023.pdf Form 1023 tax-exempt non-profit application and supplements]<br />
* [http://www.ibiblio.org/cccr/docs/irsexempt.pdf IRS tax-exempt determination letter]<br />
* [http://wiki.creativecommons.org/Board_Reports Board of Directors meeting summaries]<br />
* [http://ibiblio.org/cccr/docs/tab.pdf Technical Advisory Board charter]<br />
* [http://www.ibiblio.org/cccr/docs/auditcharter.pdf Audit Committee Charter]<br />
* [http://wiki.creativecommons.org/images/d/d7/SCIENCEADVISORYBOARDCHARGE.pdf Science Advisory Board charge]<br />
* [Board of Directors nomination process]<br />
* [http://wiki.creativecommons.org/License_Versions License versioning process]<br />
<br />
== Policies ==<br />
* [https://wiki.creativecommons.org/images/e/e2/Codes_of_Conduct_for_Employees_%28approved_March_4%2C_2018%29%281%29.pdf Code of Conduct (Employees) updated March 2018]<br />
* [https://wiki.creativecommons.org/images/9/91/Creative_Commons_Code_of_Conduct_for_Directors_and_Officers_%28adopted_Mar_4_2018%29.pdf Code of Conduct(Directors) updated March 2018]<br />
* [http://creativecommons.org/terms Website terms of use]<br />
* [http://creativecommons.org/policies Copyright and trademark policies]<br />
* [http://creativecommons.org/privacy Privacy policy]<br />
* [http://wiki.creativecommons.org/Lobbying Lobbying policy]<br />
* [http://wiki.creativecommons.org/MOU Affiliate Memorandum of Understanding (MOU) '''NO LONGER IN USE''']<br />
* [http://wiki.creativecommons.org/Internet_Services Affiliate Internet Services Policy]<br />
* [http://wiki.creativecommons.org/Merchandising Merchandising Policy] <br />
* [http://wiki.creativecommons.org/Language Language Policy]<br />
* [http://wiki.creativecommons.org/Policy_Advocacy_Guidelines Policy & Advocacy Guidelines]<br />
<br />
== Annual reports ==<br />
<br />
''' Organizational strategy document '''<br />
* [http://wiki.creativecommons.org/images/c/ce/Future-of-creative-commons.pdf The Future of Creative Commons], June 2013<br />
<br />
''' Organization-wide report '''<br />
* [https://stateof.creativecommons.org/2017 State of the Commons, 2017]<br />
* [https://stateof.creativecommons.org/2016 State of the Commons, 2016]<br />
* [https://stateof.creativecommons.org/2015 State of the Commons, 2015]<br />
* [https://stateof.creativecommons.org/ State of the Commons, 2014]<br />
* [http://teamopen.cc/thefuture/ 2013-2014]<br />
* [http://dispatches.creativecommons.org/ 2011-2012]<br />
<br />
''' Affiliate Network reports '''<br />
* [http://wiki.creativecommons.org/Affiliate_Reporting/2010 2010]<br />
<br />
== Funding sources ==<br />
* [https://creativecommons.net/supporters/ Donor list]<br />
* [https://creativecommons.net/figures/ Fundraising dashboard]<br />
* Public announcements of major grants:<br />
** [http://creativecommons.org/weblog/entry/27097 Gates Foundation Department of Labor grantee assistance]<br />
** [http://creativecommons.org/press-releases/entry/8175 Hewlett Foundation general operating and ccLearn]<br />
** [http://creativecommons.org/press-releases/entry/7945 5 x 5 Funding Challenge]<br />
** http://creativecommons.org/press-releases/entry/8322 Omidyar Network]<br />
** [http://creativecommons.org/press-releases/entry/26078 Nature Publishing Group]<br />
** [http://creativecommons.org/press-releases/entry/7183 Technology company contributions]<br />
<br />
== Other ==<br />
* [https://wiki.creativecommons.org/images/3/3a/Amended_DMCA_form.pdf DMCA Designation of Agent to Receive Notification of Claimed Infringement]</div>CCID-diane petershttps://wiki.creativecommons.org/index.php?title=Public_reports&diff=116858Public reports2018-09-04T16:55:12Z<p>CCID-diane peters: /* Policies */</p>
<hr />
<div>The purpose of this portal is to provide transparent access to public documents concerning the financial status and governance of the Creative Commons organization. <br />
<br />
== Tax returns and audit information == <br />
''' 2016 '''<br />
* [https://wiki.creativecommons.org/images/0/05/2016_990_Public_Filing.pdf IRS Form 990]<br />
* [https://wiki.creativecommons.org/images/e/e3/Creative_Commons_2016_Final_FS_11-8.pdf Independent audit] <br />
<br />
''' 2015 '''<br />
* [https://wiki.creativecommons.org/images/b/bc/2015_CC.pdf IRS Form 990]<br />
* [https://drive.google.com/open?id=0B2UhiNCe0qFcSmRQQUVkUlllem8 Independent audit]<br />
<br />
''' 2014 '''<br />
* [https://wiki.creativecommons.org/images/c/c6/Creative_Commons_2014_Form_990_Public_Disclosure_Copy.pdf IRS Form 990]<br />
* [https://drive.google.com/open?id=0B2UhiNCe0qFcSVNPMVdoMUxOdTA Independent audit]<br />
<br />
''' 2013 '''<br />
* [https://wiki.creativecommons.org/images/9/9f/Creative_Commons_form990_2013.pdf IRS Form 990]<br />
* [https://drive.google.com/open?id=0B2UhiNCe0qFcUFV1RVk0Rm0xQzg Independent audit]<br />
<br />
''' 2012'''<br />
* [http://wiki.creativecommons.org/images/3/31/990-2012B.pdf IRS Form 990]<br />
* [http://wiki.creativecommons.org/images/8/89/2012_CC_Audited_Financials.pdf Independent audit]<br />
<br />
''' 2011 '''<br />
* [http://wiki.creativecommons.org/images/8/8a/2011_Form_990_-_Public.pdf IRS Form 990]<br />
* [http://wiki.creativecommons.org/images/c/c0/2011_CC_Audited_Financials.pdf Independent audit]<br />
<br />
''' 2010 '''<br />
* [http://ibiblio.org/cccr/docs/990.pdf IRS Form 990]<br />
* [http://www.ibiblio.org/cccr/docs/audit.pdf Independent audit]<br />
<br />
''' 2009 '''<br />
* [http://www.ibiblio.org/cccr/docs/990-2009.pdf IRS Form 990]<br />
* [http://www.ibiblio.org/cccr/docs/audit2009.pdf Independent audit]<br />
<br />
''' 2008 '''<br />
* [http://www.ibiblio.org/cccr/docs/990-2008.pdf IRS Form 990]<br />
* [http://www.ibiblio.org/cccr/docs/audit2008.pdf Independent audit]<br />
<br />
''' 2007 '''<br />
* [http://www.ibiblio.org/cccr/docs/990-2007.pdf IRS Form 990]<br />
* [http://www.ibiblio.org/cccr/docs/audit2007.pdf Independent audit]<br />
<br />
''' 2006 '''<br />
* [http://www.ibiblio.org/cccr/docs/990-2006.pdf IRS Form 990]<br />
* [http://www.ibiblio.org/cccr/docs/audit2006.pdf Independent audit]<br />
<br />
''' 2005 '''<br />
* [http://www.ibiblio.org/cccr/docs/990-2005.pdf IRS Form 990]<br />
* [http://www.ibiblio.org/cccr/docs/audit2005.pdf Independent audit]<br />
<br />
''' 2004 '''<br />
* [http://www.ibiblio.org/cccr/docs/990-2004.pdf IRS Form 990]<br />
* [http://www.ibiblio.org/cccr/docs/audit2004.pdf Independent audit]<br />
<br />
''' 2003 '''<br />
* [http://www.ibiblio.org/cccr/docs/990-2003.pdf IRS Form 990]<br />
* [http://www.ibiblio.org/cccr/docs/audit2003.pdf Independent audit]<br />
<br />
''' 2002 '''<br />
* [http://www.ibiblio.org/cccr/docs/990-2002.pdf IRS Form 990]<br />
* [http://www.ibiblio.org/cccr/docs/audit2002.pdf Independent audit]<br />
<br />
''' 2001 '''<br />
* [http://www.ibiblio.org/cccr/docs/990-2001.pdf IRS Form 990]<br />
<br />
== Governance documents == <br />
* [http://ibiblio.org/cccr/docs/articles.pdf Incorporation document and charter]<br />
* [https://wiki.creativecommons.org/images/a/aa/Bylaws_-_Amended_and_Restated_March_4_2018_%28final%29.pdf Organization Bylaws (amended March 2018)]<br />
* [https://wiki.creativecommons.org/images/f/f9/CC_Amended_and_Restated_Bylaws_%28effective_6_Dec_2015%2C_amended_5_June_2016%29-1.pdf Organization Bylaws (amended June 2016)]<br />
* [https://wiki.creativecommons.org/images/a/a6/CC_Amended_and_Restated_Bylaws_%28effective_6_Dec_2015%29.pdf Organization Bylaws (amended Dec. 2015)]<br />
* [http://ibiblio.org/cccr/docs/bylaws.pdf Organization Bylaws (pre Dec. 2015)]<br />
* [http://www.ibiblio.org/cccr/docs/1023.pdf Form 1023 tax-exempt non-profit application and supplements]<br />
* [http://www.ibiblio.org/cccr/docs/irsexempt.pdf IRS tax-exempt determination letter]<br />
* [http://wiki.creativecommons.org/Board_Reports Board of Directors meeting summaries]<br />
* [http://ibiblio.org/cccr/docs/tab.pdf Technical Advisory Board charter]<br />
* [http://www.ibiblio.org/cccr/docs/auditcharter.pdf Audit Committee Charter]<br />
* [http://wiki.creativecommons.org/images/d/d7/SCIENCEADVISORYBOARDCHARGE.pdf Science Advisory Board charge]<br />
* [Board of Directors nomination process]<br />
* [http://wiki.creativecommons.org/License_Versions License versioning process]<br />
<br />
== Policies ==<br />
* [https://wiki.creativecommons.org/images/e/e2/Codes_of_Conduct_for_Employees_%28approved_March_4%2C_2018%29%281%29.pdf Code of Conduct (Employees) updated March 2018]<br />
* [https://wiki.creativecommons.org/images/9/91/Creative_Commons_Code_of_Conduct_for_Directors_and_Officers_%28adopted_Mar_4_2018%29.pdf Code of Conduct(Directors) updated March 2018]<br />
* [http://creativecommons.org/terms Website terms of use]<br />
* [http://creativecommons.org/policies Copyright and trademark policies]<br />
* [http://creativecommons.org/privacy Privacy policy]<br />
* [http://wiki.creativecommons.org/Lobbying Lobbying policy]<br />
* [http://wiki.creativecommons.org/MOU Affiliate Memorandum of Understanding (MOU)]<br />
* [http://wiki.creativecommons.org/Internet_Services Affiliate Internet Services Policy]<br />
* [http://wiki.creativecommons.org/Merchandising Merchandising Policy] <br />
* [http://wiki.creativecommons.org/Language Language Policy]<br />
* [http://wiki.creativecommons.org/Policy_Advocacy_Guidelines Policy & Advocacy Guidelines]<br />
<br />
== Annual reports ==<br />
<br />
''' Organizational strategy document '''<br />
* [http://wiki.creativecommons.org/images/c/ce/Future-of-creative-commons.pdf The Future of Creative Commons], June 2013<br />
<br />
''' Organization-wide report '''<br />
* [https://stateof.creativecommons.org/2017 State of the Commons, 2017]<br />
* [https://stateof.creativecommons.org/2016 State of the Commons, 2016]<br />
* [https://stateof.creativecommons.org/2015 State of the Commons, 2015]<br />
* [https://stateof.creativecommons.org/ State of the Commons, 2014]<br />
* [http://teamopen.cc/thefuture/ 2013-2014]<br />
* [http://dispatches.creativecommons.org/ 2011-2012]<br />
<br />
''' Affiliate Network reports '''<br />
* [http://wiki.creativecommons.org/Affiliate_Reporting/2010 2010]<br />
<br />
== Funding sources ==<br />
* [https://creativecommons.net/supporters/ Donor list]<br />
* [https://creativecommons.net/figures/ Fundraising dashboard]<br />
* Public announcements of major grants:<br />
** [http://creativecommons.org/weblog/entry/27097 Gates Foundation Department of Labor grantee assistance]<br />
** [http://creativecommons.org/press-releases/entry/8175 Hewlett Foundation general operating and ccLearn]<br />
** [http://creativecommons.org/press-releases/entry/7945 5 x 5 Funding Challenge]<br />
** http://creativecommons.org/press-releases/entry/8322 Omidyar Network]<br />
** [http://creativecommons.org/press-releases/entry/26078 Nature Publishing Group]<br />
** [http://creativecommons.org/press-releases/entry/7183 Technology company contributions]<br />
<br />
== Other ==<br />
* [https://wiki.creativecommons.org/images/3/3a/Amended_DMCA_form.pdf DMCA Designation of Agent to Receive Notification of Claimed Infringement]</div>CCID-diane petershttps://wiki.creativecommons.org/index.php?title=Author_Addendum_Project&diff=116857Author Addendum Project2018-09-03T21:47:27Z<p>CCID-diane peters: Created page with "[text TK]"</p>
<hr />
<div>[text TK]</div>CCID-diane petershttps://wiki.creativecommons.org/index.php?title=CC-related_legal_scholarship_and_references&diff=116723CC-related legal scholarship and references2018-05-10T15:43:39Z<p>CCID-diane peters: </p>
<hr />
<div>This is for collecting legal scholarship related to the CC licenses' interpretation and enforceability that is not [[Case Law|case law]] directly concerning the CC licenses. <br />
<br />
<br />
==General (uncategorized)==<br />
<br />
* [https://ir.law.fsu.edu/cgi/viewcontent.cgi?article=1114&context=lr Little Victories: Promoting Artistic Progress Through the Enforcement of Creative Commons Attribution and Share-Alike Licenses: Ashley West: 2008]<br />
*[http://www.tandfonline.com/doi/full/10.1080/13600869.2013.869923#.VJO-LsCsA The Creative Commons licences through moral rights provisions in French law: Alexandra Giannopoulou: 2014]<br />
<br />
==Compatibility==<br />
<br />
* [http://theodi.org/blog/exploring-compatibility-between-data-licences ODI: exploring compatibility between data licenses]<br />
** [https://github.com/theodi/open-data-licensing/blob/master/guides/licence-compatibility.md in-progress document]<br />
* [http://ssrn.com/abstract=2361682 Margoni, Thomas, Not for Designers: On the Inadequacies of EU Design Law and How to Fix It (October 1, 2013). Journal of Intellectual Property, Information Technology and E-Commerce Law, 4 (3) 2013]<br />
* [http://www.creativecommons.nl/downloads/101220cc_incompatibilityfinal.pdf “Creative Commons Licenses Legal Pitfalls: Incompatibilities and Solutions“, Melanie Dulong de Rosnay, Institute for Information Law/Creative Commons Nederland, 2010]<br />
* [http://www.creativecommons.nl/downloads/091201cc_sound_recordings.pdf ”Creative Commons and Related Rights in Sound Recordings: Are the Two Systems Compatible?“, Christina Angelopoulos, Amsterdam: Instituut voor Informatierecht December 2009]<br />
* [http://www.jipitec.eu/issues/jipitec-2-2-2011/3085 Creative Commons licences and design Are the two compatible?. Catherine Jasserand (2011), jipitec, Vol. 2.]<br />
<br />
==Database Rights==<br />
* [http://www.ifosslr.org/ifosslr/article/view/62 Open licensing and databases: Simone Aliprandi: 2012]<br />
* [http://ssrn.com/abstract=2391280 Dietr, Nil and Guibault, Lucie and Margoni, Thomas and Siewicz, Krzysztof and Spindler, Gerald and Wiebe, Andreas, Safe to Be Open: Study on the Protection of Research Data and Recommendations for Access and Usage (2013). OpenAirePlus]<br />
* [http://creativecommons.nl/wp-content/uploads/2012/05/I-buri-Accessing-and-Licensing-Government-Data-under-Open-Access-Conditions.pdf Accessing and Licensing Government Data under Open Access Conditions Ilaria Buri: 2012]<br />
<br />
==Termination of Transfers==<br />
<br />
* [http://scholarship.law.uc.edu/cgi/viewcontent.cgi?article=1146&context=fac_pubs Shrinking the Commons: Termination of Copyright Licenses and Transfers for the Benefit of the Public: Timothy K. Armstrong: 2007]<br />
<br />
* [http://papers.ssrn.com/sol3/papers.cfm?abstract_id=957939 Building a Reliable Semicommons of Creative Works: Enforcement of Creative Commons Licenses and Limited Abandonment of Copyright: Lydia Loren: 2007]<br />
<br />
<br />
[[Category:Legal]]</div>CCID-diane petershttps://wiki.creativecommons.org/index.php?title=CC_Friendly_Lawyers&diff=115379CC Friendly Lawyers2016-07-18T20:38:05Z<p>CCID-diane peters: </p>
<hr />
<div><span style="color: red">Please note that CC does not provide referral services, and that we do not necessarily endorse or recommend anyone on this list for any particular client or circumstance.</span><br />
<br />
== Canada ==<br />
* [http://artistslegaloutreach.ca/ Artists' Legal Outreach]<br />
<br />
== Germany ==<br />
* [http://jbb.de JBB Rechtsanwälte] including [http://www.jbb.de/anwaelte/till-jaeger/ Till Jaeger]<br />
<br />
== Italy ==<br />
* [http://www.array.eu/#people Array], including Carlo Piana<br />
<br />
== South Africa ==<br />
* [http://opencounsel.net Open Counsel], including Andrew Rens<br />
<br />
== Sweden ==<br />
* Morus konsult AB: info@morus.se [http://morus.se/en/ http://morus.se/en/]<br />
<br />
== United States == <br />
<br />
* Withrow & Betinol Law (Los Angeles, CA): info@wibelaw.com. [http://www.wibelaw.com www.wibelaw.com]<br />
* '''Michael Sullivan''' (San Jose, CA): msullivan@mikesullivanlaw.com [http://www.mikesullivanlaw.com/creative-commons-license-questions.html Law Office of Michael J. Sullivan]<br />
* [http://www.lilabailey.com/ Lila Bailey]<br />
* '''Daniel Senter''' (Berkeley, CA): daniel at danielsenterlaw.com, [http://danielsenterlaw.com Law Office of Daniel Senter]</div>CCID-diane petershttps://wiki.creativecommons.org/index.php?title=Global_Summit_2015/Presentations_%26_Notes&diff=114564Global Summit 2015/Presentations & Notes2015-11-03T13:41:43Z<p>CCID-diane peters: /* Saturday Oct 17 */</p>
<hr />
<div>==Wednesday Oct 14==<br />
CC Affiliate MiniConference<br />
<br />
==Thursday Oct 15==<br />
*Welcome & Opening Remarks - Jeongwook Seo <br />
*Sponsor Spotlight - Rick Falkvinge, Private Internet Access<br />
*Opening keynotes<br />
**[http://www.slideshare.net/cckslide/what-i-learned-from-cc-jay-yoon What I learned from CC] - Jay Yoon<br />
**[http://www.slideshare.net/cckslide/the-idea-of-the-commons-future-of-capitalism-yochai-benkler The idea of the commons and the future of capitalism] - Yochai Benkler <br />
*Keynote Panel<br />
**Importance of Creative Commons in the digital era - Yochai Benkler, Ryan Merkley, Jay Yoon<br />
*Exploring Open Business Models<br />
**[http://www.slideshare.net/Paul_Stacey/creative-commons-global-summit-2015-open-business-models-book-and-business-toolkit Open business models book and business toolkit] - Paul Stacey, Sarah Pearson, Teresa Nobre, Fátima São Simão<br />
**[http://www.slideshare.net/terburg/sharing-manual-seoul The Sharing Manual] - Sebastiaan ter Burg [https://vimeo.com/142884101 video recording]<br />
**[http://www.slideshare.net/cckslide/rhymeduck-music-service Rhymeduck Music Service] - Hee-sung Do, Wantreez Music<br />
**[http://www.slideshare.net/cckslide/500px-nuno-silva 500px] - Nuno Silva, 500px<br />
*Social, cultural, and economic implications of open content<br />
**[http://www.slideshare.net/cgreen/global-oer-movement-cc-cc-summit Global OER Movement and CC] - Cable Green <br />
**[http://www.slideshare.net/paulkeller/how-europeana-came-to-embrace-openness How Europeana came to embrace openness] - Paul Keller<br />
**[http://www.slideshare.net/cckslide/ss-54415051 Open content and reuse] - Tae-yong Yoon<br />
*CC in art and film<br />
**The Long Road Project - Reda Zine<br />
*CC Tech Team 1<br />
**Road Map & The List - Ryan Merkley, Rob Myers<br />
*Do-It-Yourself / Maker<br />
**[http://www.slideshare.net/cckslide/open-source-satellite-initiative Open Source Satellite Initiative] - Hojun Song<br />
**Ji-hyun Kim<br />
**[http://www.slideshare.net/cckslide/digital-fabrication-open-source-hardware-and-creative-commons-michael-weinberg Digital Fabrication, Open Source Hardware, and Creative Commons: So Into Each Other] - Michael Weinberg<br />
*[http://www.slideshare.net/technollama/institutional-cc-adoption-in-glam Institutional CC adoption in GLAM] - Andres Guadamuz<br />
*Open Data in Korea and the World<br />
**Seon-tae Kim (KISTI)<br />
**[http://www.slideshare.net/cckslide/open-data-strategy-portal-of-korea-govt Open data strategy & open data portal of Korea govt] - Munshil Choi (NIA)<br />
**Naeema Zarif<br />
*CC Tech Team 2<br />
**CC Search & CC License Chooser - Ryan Merkley, Rob Myers<br />
*Closing keynotes<br />
**[http://www.slideshare.net/cckslide/age-of-emotion-sohyeong-noh Age of emotion] - SohYeong Roh, Art Center Nabi<br />
**[http://www.slideshare.net/cckslide/on-the-shoulders-of-giants-54415246 On the shoulders of giants] - Lila Tretikov, Wikimedia Foundation<br />
<br />
==Friday Oct 16==<br />
*Welcome & Opening Remarks - Paul Brest<br />
*Opening Keynote - Ryan Merkley <br />
*wikiHow announcement of Korean site launch<br />
*Fair use and business <br />
**Jay Yoon<br />
*Sharing City: City rediscovers the values of sharing<br />
**[http://www.slideshare.net/cckslide/3-54416173 Urban Problems Innovative Approaches] - Hyo-kwan Chon, Seoul Metropolitan Government<br />
**[http://www.slideshare.net/cckslide/amsterdam-sharing-city-pieter-bas-van-de-glind Amsterdam Sharing City] - Pieter van de Glind, ShareNL<br />
**[http://www.slideshare.net/cckslide/ss-54416200 Parking lot sharing system] - Dong-hyeon Kim<br />
**[http://www.slideshare.net/cckslide/ss-54416199 Sharing City and Sharing Home] - Sang-hyun Lee, Airbnb<br />
*OER: Mainstreaming and the Moonshot <br />
**Cable Green <br />
**Nicole Allen, TJ Bliss, Delia Browne, Meena Hwang, Ryan Merkley, Stella Hayoung Shin, Alek Tarkowski, Esther Wojcicki<br />
*Showcases of Sharing Culture 1<br />
**Baden Appleyard<br />
**Tyng-Ruey Chuang<br />
**McCoy Smith (see slides from Saturday presentation)<br />
**Chunyan Wang<br />
*Showcases of Sharing Culture 2<br />
**[http://www.slideshare.net/cckslide/ss-54416489 Art of Happy Sharing] - Jinho Jung<br />
**[http://www.slideshare.net/cckslide/400-54416490 Mania DB] - Hyeong-kyu Ryu<br />
**[http://www.slideshare.net/cckslide/2015-open-access-korea Open Access Korea] - Sung-chul Park, National Library of Korea<br />
**[http://www.slideshare.net/mobile/cckslide/data-big-data-and-communication Data, big data and communication] - Ki-Byoung Kim<br />
**[http://www.slideshare.net/cckslide/luxi-island-oer-summer-camp-liu-ping Luxi island OER summer camp] - Liu Ping<br />
**[http://www.slideshare.net/cckslide/free-music-week-jorge-gabriel-jimenez Free Music Week] - Jorge Gabriel Jimenez<br />
*Measuring the impact of open policy for GLAM - Klaudia Grabowska<br />
*Legal Code Translations 2 Years Strong: Successes, Challenges and Impact <br />
**Carolina Botero, Marianne Diaz, Hala Essalmawi, Ignasi Labastida, Maksym Naumko, Sarah Pearson, Dr. Mohammad El Said, Chunyan Wang<br />
*[http://www.slideshare.net/cckslide/over-the-long-terms-the-state-of-activism-on-toolong-copyright-terms-and-how-you-can-join-in Copyright Advocacy: Over the Long Terms: The State of Activism on Too-Long Copyright Terms (And How You Can Join In)] - Maira Sutton, Parker Higgins<br />
*Showcases of Sharing Culture 3 - [http://www.slideshare.net/cckslide/showcases-of-sharing-culture-3 slide deck]<br />
**Free Music Communities in Uruguay - Salvador Garcia - no slides<br />
**How do we scale OER? - Matt McGregor - slides in deck<br />
**Global Voices and CC - Mohamed ElGohary - slides in deck<br />
**Helping authors who write to be read -- Michael Wolfe - slides<br />
**Introducing Embedr.eu - Maarten Zeinstra - slides in deck<br />
**New Palmyra and Free Souls 2 - Christopher Adams - slides in deck<br />
**[https://prezi.com/f3vl5w91bdme/copyright-relinquishment-across-the-world/ CC0 and copyright relinquishment] - Andres Guadamuz<br />
*CC Licensing the Sum of All Knowledge: Community and Legal Considerations for Wikipedia and Platforms <br />
**Jane Park, Baden Appleyard, Tyng-Ruey Chuang, Stephen LaPorte, Sarah Pearson ([http://www.slideshare.net/shpearson/legal-considerations-for-platforms?related=2 slides]), Tomoaki Watanabe ([http://www.slideshare.net/TomoakiWatanabe/platform-terms-and-cc-licenses slides])<br />
*OER Project Showcase <br />
**Cable Green <br />
**George Abdelnour, Baden Appleyard, Kamil Åšliwowski, Dr Fawzi Baroud, Mostafa Azad Kamal, Simeon Oriko, Alek Tarkowski<br />
*Open Access: Developing tools, practices, and stories in support of OA publishing <br />
**Ignasi Labastida, Thomas Margoni, Diane Peters ([http://www.slideshare.net/peterspdx/retaining-and-regaining-author-publication-rights slides]), Georgina Taylor, Michael Wolfe<br />
*[http://www.slideshare.net/cckslide/unpacking-an-activist-toolbox-effs-tools-and-tips-for-effective-copyright-advocacy-maira-sutton Unpacking an Activist Toolbox: EFF's Tools and Tips for Effective Copyright Advocacy] - Maira Sutton, Parker Higgins<br />
*Closing Keynote<br />
**[http://www.slideshare.net/cckslide/ecological-internet-kilnam-chon Ecological Internet] - Kilnam Chon <br />
*Closing Panel<br />
**Open Internet Issues - Renata Avila, Yochai Benkler, Kilnam Chon<br />
<br />
==Saturday Oct 17==<br />
*Welcome & Opening Remarks <br />
**Michael Carrol<br />
*[http://www.slideshare.net/cckslide/copyright-reform-and-the-role-of-creative-commons Copyright reform and the role of Creative Commons] - Julia Reda <br />
*CC Affiliates Policies Hands-On - John Weitzmann<br />
*Creative Commons and the Future of Design: The 3D and Hardware Commons <br />
**How will CC shape the future of design? - Jane Park<br />
**Mahmoud Abu-Wardeh <br />
**A pick into open hardware - Tomoaki Watanabe<br />
**Michael Weinberg<br />
*Jump-starting commons advocacy and copyright reform<br />
**Delia Browne, Paul Keller, Claudio Ruiz, Maira Sutton, Alek Tarkowski, Timothy Vollmer<br />
*The Vibrant and Social Commons: Designing for User Engagement <br />
**Ryan Merkley, Jane Park, Eric Steuer<br />
*Rights Statements, the Public Domain Mark, and Blockchain: Extending the CC infrastructure <br />
**[https://docs.google.com/presentation/d/16YnIRdgzxlavdIwhWOJnLjNGOAYsQFyQjjqvmvtv2Po/edit#slide=id.gc47e82bdf_0_35 Blockchain and Creative Commons], Constance Choi and Primavera De Filippi <br />
**Paul Keller and Maarten Zeinstra<br />
** [http://www.slideshare.net/peterspdx/creative-commons-public-domain-mark-version-2 Exploring a new or revised Public Domain Mark], Diane Peters<br />
*Open Licensing Education and Advocacy - Tools and Tactics for Communicating with Decisionmakers <br />
**Meredith Jacob<br />
*Affiliates 2.0 - CC as a true network organisation followup discussion <br />
**Paul Keller, Alek Tarkowski<br />
*Open Hardware and Design: Solutions for Licensing Rights Beyond Copyright and Open Hardware Certification <br />
**[https://drive.google.com/file/d/0B0HBOY8b2doERnoxbHV4WE1UX1U/view?usp=sharing CC+Design (Rights)],Thomas Margoni<br />
**[http://www.slideshare.net/peterspdx/extending-the-creative-commons-license-suite Fundamentals of Extending the Scope of CC Licenses], Diane Peters<br />
**[https://drive.google.com/file/d/0B0HBOY8b2doESnl2d0M1clJ5bG8/view?usp=sharing PLUG License - a proposal] McCoy Smith<br />
**[https://docs.google.com/presentation/d/14wT_NmcBro1QWYct50yTZ6PoyqjWNXUHb0oA9VHVs4A/edit?usp=sharing What's Happening with Open Hardware Certification], Michael Weinberg ([https://www.shapeways.com/blog/archives/22679-by-3d-creative-commons-attribution-and-3d-printing.html related blog post])<br />
*Closing Keynote - Carolina Botero, Tobias Schonwetter<br />
*Wrap-up Summary - Ryan Merkley</div>CCID-diane petershttps://wiki.creativecommons.org/index.php?title=Global_Summit_2015/Presentations_%26_Notes&diff=114563Global Summit 2015/Presentations & Notes2015-11-03T13:36:33Z<p>CCID-diane peters: /* Saturday Oct 17 */</p>
<hr />
<div>==Wednesday Oct 14==<br />
CC Affiliate MiniConference<br />
<br />
==Thursday Oct 15==<br />
*Welcome & Opening Remarks - Jeongwook Seo <br />
*Sponsor Spotlight - Rick Falkvinge, Private Internet Access<br />
*Opening keynotes<br />
**[http://www.slideshare.net/cckslide/what-i-learned-from-cc-jay-yoon What I learned from CC] - Jay Yoon<br />
**[http://www.slideshare.net/cckslide/the-idea-of-the-commons-future-of-capitalism-yochai-benkler The idea of the commons and the future of capitalism] - Yochai Benkler <br />
*Keynote Panel<br />
**Importance of Creative Commons in the digital era - Yochai Benkler, Ryan Merkley, Jay Yoon<br />
*Exploring Open Business Models<br />
**[http://www.slideshare.net/Paul_Stacey/creative-commons-global-summit-2015-open-business-models-book-and-business-toolkit Open business models book and business toolkit] - Paul Stacey, Sarah Pearson, Teresa Nobre, Fátima São Simão<br />
**[http://www.slideshare.net/terburg/sharing-manual-seoul The Sharing Manual] - Sebastiaan ter Burg [https://vimeo.com/142884101 video recording]<br />
**[http://www.slideshare.net/cckslide/rhymeduck-music-service Rhymeduck Music Service] - Hee-sung Do, Wantreez Music<br />
**[http://www.slideshare.net/cckslide/500px-nuno-silva 500px] - Nuno Silva, 500px<br />
*Social, cultural, and economic implications of open content<br />
**[http://www.slideshare.net/cgreen/global-oer-movement-cc-cc-summit Global OER Movement and CC] - Cable Green <br />
**[http://www.slideshare.net/paulkeller/how-europeana-came-to-embrace-openness How Europeana came to embrace openness] - Paul Keller<br />
**[http://www.slideshare.net/cckslide/ss-54415051 Open content and reuse] - Tae-yong Yoon<br />
*CC in art and film<br />
**The Long Road Project - Reda Zine<br />
*CC Tech Team 1<br />
**Road Map & The List - Ryan Merkley, Rob Myers<br />
*Do-It-Yourself / Maker<br />
**[http://www.slideshare.net/cckslide/open-source-satellite-initiative Open Source Satellite Initiative] - Hojun Song<br />
**Ji-hyun Kim<br />
**[http://www.slideshare.net/cckslide/digital-fabrication-open-source-hardware-and-creative-commons-michael-weinberg Digital Fabrication, Open Source Hardware, and Creative Commons: So Into Each Other] - Michael Weinberg<br />
*[http://www.slideshare.net/technollama/institutional-cc-adoption-in-glam Institutional CC adoption in GLAM] - Andres Guadamuz<br />
*Open Data in Korea and the World<br />
**Seon-tae Kim (KISTI)<br />
**[http://www.slideshare.net/cckslide/open-data-strategy-portal-of-korea-govt Open data strategy & open data portal of Korea govt] - Munshil Choi (NIA)<br />
**Naeema Zarif<br />
*CC Tech Team 2<br />
**CC Search & CC License Chooser - Ryan Merkley, Rob Myers<br />
*Closing keynotes<br />
**[http://www.slideshare.net/cckslide/age-of-emotion-sohyeong-noh Age of emotion] - SohYeong Roh, Art Center Nabi<br />
**[http://www.slideshare.net/cckslide/on-the-shoulders-of-giants-54415246 On the shoulders of giants] - Lila Tretikov, Wikimedia Foundation<br />
<br />
==Friday Oct 16==<br />
*Welcome & Opening Remarks - Paul Brest<br />
*Opening Keynote - Ryan Merkley <br />
*wikiHow announcement of Korean site launch<br />
*Fair use and business <br />
**Jay Yoon<br />
*Sharing City: City rediscovers the values of sharing<br />
**[http://www.slideshare.net/cckslide/3-54416173 Urban Problems Innovative Approaches] - Hyo-kwan Chon, Seoul Metropolitan Government<br />
**[http://www.slideshare.net/cckslide/amsterdam-sharing-city-pieter-bas-van-de-glind Amsterdam Sharing City] - Pieter van de Glind, ShareNL<br />
**[http://www.slideshare.net/cckslide/ss-54416200 Parking lot sharing system] - Dong-hyeon Kim<br />
**[http://www.slideshare.net/cckslide/ss-54416199 Sharing City and Sharing Home] - Sang-hyun Lee, Airbnb<br />
*OER: Mainstreaming and the Moonshot <br />
**Cable Green <br />
**Nicole Allen, TJ Bliss, Delia Browne, Meena Hwang, Ryan Merkley, Stella Hayoung Shin, Alek Tarkowski, Esther Wojcicki<br />
*Showcases of Sharing Culture 1<br />
**Baden Appleyard<br />
**Tyng-Ruey Chuang<br />
**McCoy Smith (see slides from Saturday presentation)<br />
**Chunyan Wang<br />
*Showcases of Sharing Culture 2<br />
**[http://www.slideshare.net/cckslide/ss-54416489 Art of Happy Sharing] - Jinho Jung<br />
**[http://www.slideshare.net/cckslide/400-54416490 Mania DB] - Hyeong-kyu Ryu<br />
**[http://www.slideshare.net/cckslide/2015-open-access-korea Open Access Korea] - Sung-chul Park, National Library of Korea<br />
**[http://www.slideshare.net/mobile/cckslide/data-big-data-and-communication Data, big data and communication] - Ki-Byoung Kim<br />
**[http://www.slideshare.net/cckslide/luxi-island-oer-summer-camp-liu-ping Luxi island OER summer camp] - Liu Ping<br />
**[http://www.slideshare.net/cckslide/free-music-week-jorge-gabriel-jimenez Free Music Week] - Jorge Gabriel Jimenez<br />
*Measuring the impact of open policy for GLAM - Klaudia Grabowska<br />
*Legal Code Translations 2 Years Strong: Successes, Challenges and Impact <br />
**Carolina Botero, Marianne Diaz, Hala Essalmawi, Ignasi Labastida, Maksym Naumko, Sarah Pearson, Dr. Mohammad El Said, Chunyan Wang<br />
*[http://www.slideshare.net/cckslide/over-the-long-terms-the-state-of-activism-on-toolong-copyright-terms-and-how-you-can-join-in Copyright Advocacy: Over the Long Terms: The State of Activism on Too-Long Copyright Terms (And How You Can Join In)] - Maira Sutton, Parker Higgins<br />
*Showcases of Sharing Culture 3 - [http://www.slideshare.net/cckslide/showcases-of-sharing-culture-3 slide deck]<br />
**Free Music Communities in Uruguay - Salvador Garcia - no slides<br />
**How do we scale OER? - Matt McGregor - slides in deck<br />
**Global Voices and CC - Mohamed ElGohary - slides in deck<br />
**Helping authors who write to be read -- Michael Wolfe - slides<br />
**Introducing Embedr.eu - Maarten Zeinstra - slides in deck<br />
**New Palmyra and Free Souls 2 - Christopher Adams - slides in deck<br />
**[https://prezi.com/f3vl5w91bdme/copyright-relinquishment-across-the-world/ CC0 and copyright relinquishment] - Andres Guadamuz<br />
*CC Licensing the Sum of All Knowledge: Community and Legal Considerations for Wikipedia and Platforms <br />
**Jane Park, Baden Appleyard, Tyng-Ruey Chuang, Stephen LaPorte, Sarah Pearson ([http://www.slideshare.net/shpearson/legal-considerations-for-platforms?related=2 slides]), Tomoaki Watanabe ([http://www.slideshare.net/TomoakiWatanabe/platform-terms-and-cc-licenses slides])<br />
*OER Project Showcase <br />
**Cable Green <br />
**George Abdelnour, Baden Appleyard, Kamil Åšliwowski, Dr Fawzi Baroud, Mostafa Azad Kamal, Simeon Oriko, Alek Tarkowski<br />
*Open Access: Developing tools, practices, and stories in support of OA publishing <br />
**Ignasi Labastida, Thomas Margoni, Diane Peters ([http://www.slideshare.net/peterspdx/retaining-and-regaining-author-publication-rights slides]), Georgina Taylor, Michael Wolfe<br />
*[http://www.slideshare.net/cckslide/unpacking-an-activist-toolbox-effs-tools-and-tips-for-effective-copyright-advocacy-maira-sutton Unpacking an Activist Toolbox: EFF's Tools and Tips for Effective Copyright Advocacy] - Maira Sutton, Parker Higgins<br />
*Closing Keynote<br />
**[http://www.slideshare.net/cckslide/ecological-internet-kilnam-chon Ecological Internet] - Kilnam Chon <br />
*Closing Panel<br />
**Open Internet Issues - Renata Avila, Yochai Benkler, Kilnam Chon<br />
<br />
==Saturday Oct 17==<br />
*Welcome & Opening Remarks <br />
**Michael Carrol<br />
*[http://www.slideshare.net/cckslide/copyright-reform-and-the-role-of-creative-commons Copyright reform and the role of Creative Commons] - Julia Reda <br />
*CC Affiliates Policies Hands-On - John Weitzmann<br />
*Creative Commons and the Future of Design: The 3D and Hardware Commons <br />
**How will CC shape the future of design? - Jane Park<br />
**Mahmoud Abu-Wardeh <br />
**A pick into open hardware - Tomoaki Watanabe<br />
**Michael Weinberg<br />
*Jump-starting commons advocacy and copyright reform<br />
**Delia Browne, Paul Keller, Claudio Ruiz, Maira Sutton, Alek Tarkowski, Timothy Vollmer<br />
*The Vibrant and Social Commons: Designing for User Engagement <br />
**Ryan Merkley, Jane Park, Eric Steuer<br />
*Rights Statements, the Public Domain Mark, and Blockchain: Extending the CC infrastructure <br />
**[https://docs.google.com/presentation/d/16YnIRdgzxlavdIwhWOJnLjNGOAYsQFyQjjqvmvtv2Po/edit#slide=id.gc47e82bdf_0_35 Blockchain and Creative Commons], Constance Choi and Primavera De Filippi <br />
**Paul Keller and Maarten Zeinstra<br />
** [http://www.slideshare.net/peterspdx/creative-commons-public-domain-mark-version-2 Exploring a new or revised Public Domain Mark], Diane Peters<br />
*Open Licensing Education and Advocacy - Tools and Tactics for Communicating with Decisionmakers <br />
**Meredith Jacob<br />
*Affiliates 2.0 - CC as a true network organisation followup discussion <br />
**Paul Keller, Alek Tarkowski<br />
*Open Hardware and Design: Solutions for Licensing Rights Beyond Copyright and Open Hardware Certification <br />
**Thomas Margoni<br />
**[http://www.slideshare.net/peterspdx/extending-the-creative-commons-license-suite Fundamentals of Extending the Scope of CC Licenses], Diane Peters<br />
**McCoy Smith<br />
**[https://docs.google.com/presentation/d/14wT_NmcBro1QWYct50yTZ6PoyqjWNXUHb0oA9VHVs4A/edit?usp=sharing What's Happening with Open Hardware Certification], Michael Weinberg ([https://www.shapeways.com/blog/archives/22679-by-3d-creative-commons-attribution-and-3d-printing.html related blog post])<br />
*Closing Keynote - Carolina Botero, Tobias Schonwetter<br />
*Wrap-up Summary - Ryan Merkley</div>CCID-diane petershttps://wiki.creativecommons.org/index.php?title=Global_Summit_2015/Presentations_%26_Notes&diff=114562Global Summit 2015/Presentations & Notes2015-11-03T13:31:25Z<p>CCID-diane peters: /* Saturday Oct 17 */</p>
<hr />
<div>==Wednesday Oct 14==<br />
CC Affiliate MiniConference<br />
<br />
==Thursday Oct 15==<br />
*Welcome & Opening Remarks - Jeongwook Seo <br />
*Sponsor Spotlight - Rick Falkvinge, Private Internet Access<br />
*Opening keynotes<br />
**[http://www.slideshare.net/cckslide/what-i-learned-from-cc-jay-yoon What I learned from CC] - Jay Yoon<br />
**[http://www.slideshare.net/cckslide/the-idea-of-the-commons-future-of-capitalism-yochai-benkler The idea of the commons and the future of capitalism] - Yochai Benkler <br />
*Keynote Panel<br />
**Importance of Creative Commons in the digital era - Yochai Benkler, Ryan Merkley, Jay Yoon<br />
*Exploring Open Business Models<br />
**[http://www.slideshare.net/Paul_Stacey/creative-commons-global-summit-2015-open-business-models-book-and-business-toolkit Open business models book and business toolkit] - Paul Stacey, Sarah Pearson, Teresa Nobre, Fátima São Simão<br />
**[http://www.slideshare.net/terburg/sharing-manual-seoul The Sharing Manual] - Sebastiaan ter Burg [https://vimeo.com/142884101 video recording]<br />
**[http://www.slideshare.net/cckslide/rhymeduck-music-service Rhymeduck Music Service] - Hee-sung Do, Wantreez Music<br />
**[http://www.slideshare.net/cckslide/500px-nuno-silva 500px] - Nuno Silva, 500px<br />
*Social, cultural, and economic implications of open content<br />
**[http://www.slideshare.net/cgreen/global-oer-movement-cc-cc-summit Global OER Movement and CC] - Cable Green <br />
**[http://www.slideshare.net/paulkeller/how-europeana-came-to-embrace-openness How Europeana came to embrace openness] - Paul Keller<br />
**[http://www.slideshare.net/cckslide/ss-54415051 Open content and reuse] - Tae-yong Yoon<br />
*CC in art and film<br />
**The Long Road Project - Reda Zine<br />
*CC Tech Team 1<br />
**Road Map & The List - Ryan Merkley, Rob Myers<br />
*Do-It-Yourself / Maker<br />
**[http://www.slideshare.net/cckslide/open-source-satellite-initiative Open Source Satellite Initiative] - Hojun Song<br />
**Ji-hyun Kim<br />
**[http://www.slideshare.net/cckslide/digital-fabrication-open-source-hardware-and-creative-commons-michael-weinberg Digital Fabrication, Open Source Hardware, and Creative Commons: So Into Each Other] - Michael Weinberg<br />
*[http://www.slideshare.net/technollama/institutional-cc-adoption-in-glam Institutional CC adoption in GLAM] - Andres Guadamuz<br />
*Open Data in Korea and the World<br />
**Seon-tae Kim (KISTI)<br />
**[http://www.slideshare.net/cckslide/open-data-strategy-portal-of-korea-govt Open data strategy & open data portal of Korea govt] - Munshil Choi (NIA)<br />
**Naeema Zarif<br />
*CC Tech Team 2<br />
**CC Search & CC License Chooser - Ryan Merkley, Rob Myers<br />
*Closing keynotes<br />
**[http://www.slideshare.net/cckslide/age-of-emotion-sohyeong-noh Age of emotion] - SohYeong Roh, Art Center Nabi<br />
**[http://www.slideshare.net/cckslide/on-the-shoulders-of-giants-54415246 On the shoulders of giants] - Lila Tretikov, Wikimedia Foundation<br />
<br />
==Friday Oct 16==<br />
*Welcome & Opening Remarks - Paul Brest<br />
*Opening Keynote - Ryan Merkley <br />
*wikiHow announcement of Korean site launch<br />
*Fair use and business <br />
**Jay Yoon<br />
*Sharing City: City rediscovers the values of sharing<br />
**[http://www.slideshare.net/cckslide/3-54416173 Urban Problems Innovative Approaches] - Hyo-kwan Chon, Seoul Metropolitan Government<br />
**[http://www.slideshare.net/cckslide/amsterdam-sharing-city-pieter-bas-van-de-glind Amsterdam Sharing City] - Pieter van de Glind, ShareNL<br />
**[http://www.slideshare.net/cckslide/ss-54416200 Parking lot sharing system] - Dong-hyeon Kim<br />
**[http://www.slideshare.net/cckslide/ss-54416199 Sharing City and Sharing Home] - Sang-hyun Lee, Airbnb<br />
*OER: Mainstreaming and the Moonshot <br />
**Cable Green <br />
**Nicole Allen, TJ Bliss, Delia Browne, Meena Hwang, Ryan Merkley, Stella Hayoung Shin, Alek Tarkowski, Esther Wojcicki<br />
*Showcases of Sharing Culture 1<br />
**Baden Appleyard<br />
**Tyng-Ruey Chuang<br />
**McCoy Smith (see slides from Saturday presentation)<br />
**Chunyan Wang<br />
*Showcases of Sharing Culture 2<br />
**[http://www.slideshare.net/cckslide/ss-54416489 Art of Happy Sharing] - Jinho Jung<br />
**[http://www.slideshare.net/cckslide/400-54416490 Mania DB] - Hyeong-kyu Ryu<br />
**[http://www.slideshare.net/cckslide/2015-open-access-korea Open Access Korea] - Sung-chul Park, National Library of Korea<br />
**[http://www.slideshare.net/mobile/cckslide/data-big-data-and-communication Data, big data and communication] - Ki-Byoung Kim<br />
**[http://www.slideshare.net/cckslide/luxi-island-oer-summer-camp-liu-ping Luxi island OER summer camp] - Liu Ping<br />
**[http://www.slideshare.net/cckslide/free-music-week-jorge-gabriel-jimenez Free Music Week] - Jorge Gabriel Jimenez<br />
*Measuring the impact of open policy for GLAM - Klaudia Grabowska<br />
*Legal Code Translations 2 Years Strong: Successes, Challenges and Impact <br />
**Carolina Botero, Marianne Diaz, Hala Essalmawi, Ignasi Labastida, Maksym Naumko, Sarah Pearson, Dr. Mohammad El Said, Chunyan Wang<br />
*[http://www.slideshare.net/cckslide/over-the-long-terms-the-state-of-activism-on-toolong-copyright-terms-and-how-you-can-join-in Copyright Advocacy: Over the Long Terms: The State of Activism on Too-Long Copyright Terms (And How You Can Join In)] - Maira Sutton, Parker Higgins<br />
*Showcases of Sharing Culture 3 - [http://www.slideshare.net/cckslide/showcases-of-sharing-culture-3 slide deck]<br />
**Free Music Communities in Uruguay - Salvador Garcia - no slides<br />
**How do we scale OER? - Matt McGregor - slides in deck<br />
**Global Voices and CC - Mohamed ElGohary - slides in deck<br />
**Helping authors who write to be read -- Michael Wolfe - slides<br />
**Introducing Embedr.eu - Maarten Zeinstra - slides in deck<br />
**New Palmyra and Free Souls 2 - Christopher Adams - slides in deck<br />
**[https://prezi.com/f3vl5w91bdme/copyright-relinquishment-across-the-world/ CC0 and copyright relinquishment] - Andres Guadamuz<br />
*CC Licensing the Sum of All Knowledge: Community and Legal Considerations for Wikipedia and Platforms <br />
**Jane Park, Baden Appleyard, Tyng-Ruey Chuang, Stephen LaPorte, Sarah Pearson ([http://www.slideshare.net/shpearson/legal-considerations-for-platforms?related=2 slides]), Tomoaki Watanabe ([http://www.slideshare.net/TomoakiWatanabe/platform-terms-and-cc-licenses slides])<br />
*OER Project Showcase <br />
**Cable Green <br />
**George Abdelnour, Baden Appleyard, Kamil Åšliwowski, Dr Fawzi Baroud, Mostafa Azad Kamal, Simeon Oriko, Alek Tarkowski<br />
*Open Access: Developing tools, practices, and stories in support of OA publishing <br />
**Ignasi Labastida, Thomas Margoni, Diane Peters ([http://www.slideshare.net/peterspdx/retaining-and-regaining-author-publication-rights slides]), Georgina Taylor, Michael Wolfe<br />
*[http://www.slideshare.net/cckslide/unpacking-an-activist-toolbox-effs-tools-and-tips-for-effective-copyright-advocacy-maira-sutton Unpacking an Activist Toolbox: EFF's Tools and Tips for Effective Copyright Advocacy] - Maira Sutton, Parker Higgins<br />
*Closing Keynote<br />
**[http://www.slideshare.net/cckslide/ecological-internet-kilnam-chon Ecological Internet] - Kilnam Chon <br />
*Closing Panel<br />
**Open Internet Issues - Renata Avila, Yochai Benkler, Kilnam Chon<br />
<br />
==Saturday Oct 17==<br />
*Welcome & Opening Remarks <br />
**Michael Carrol<br />
*[http://www.slideshare.net/cckslide/copyright-reform-and-the-role-of-creative-commons Copyright reform and the role of Creative Commons] - Julia Reda <br />
*CC Affiliates Policies Hands-On - John Weitzmann<br />
*Creative Commons and the Future of Design: The 3D and Hardware Commons <br />
**How will CC shape the future of design? - Jane Park<br />
**Mahmoud Abu-Wardeh <br />
**A pick into open hardware - Tomoaki Watanabe<br />
**Michael Weinberg<br />
*Jump-starting commons advocacy and copyright reform<br />
**Delia Browne, Paul Keller, Claudio Ruiz, Maira Sutton, Alek Tarkowski, Timothy Vollmer<br />
*The Vibrant and Social Commons: Designing for User Engagement <br />
**Ryan Merkley, Jane Park, Eric Steuer<br />
*Rights Statements, the Public Domain Mark, and Blockchain: Extending the CC infrastructure <br />
**[https://docs.google.com/presentation/d/16YnIRdgzxlavdIwhWOJnLjNGOAYsQFyQjjqvmvtv2Po/edit#slide=id.gc47e82bdf_0_35 Blockchain and Creative Commons], Constance Choi and Primavera De Filippi <br />
**Paul Keller and Maarten Zeinstra<br />
** [http://www.slideshare.net/peterspdx/creative-commons-public-domain-mark-version-2 Exploring a new or revised Public Domain Mark], Diane Peters<br />
*Open Licensing Education and Advocacy - Tools and Tactics for Communicating with Decisionmakers <br />
**Meredith Jacob<br />
*Affiliates 2.0 - CC as a true network organisation followup discussion <br />
**Paul Keller, Alek Tarkowski<br />
*Open Hardware and Design: Solutions for Licensing Rights Beyond Copyright and Open Hardware Certification <br />
**Thomas Margoni, Diane Peters ([http://www.slideshare.net/peterspdx/extending-the-creative-commons-license-suite ]slides), McCoy Smith, Michael Weinberg<br />
*Closing Keynote - Carolina Botero, Tobias Schonwetter<br />
*Wrap-up Summary - Ryan Merkley</div>CCID-diane petershttps://wiki.creativecommons.org/index.php?title=Global_Summit_2015/Presentations_%26_Notes&diff=114561Global Summit 2015/Presentations & Notes2015-11-03T13:29:40Z<p>CCID-diane peters: /* Friday Oct 16 */</p>
<hr />
<div>==Wednesday Oct 14==<br />
CC Affiliate MiniConference<br />
<br />
==Thursday Oct 15==<br />
*Welcome & Opening Remarks - Jeongwook Seo <br />
*Sponsor Spotlight - Rick Falkvinge, Private Internet Access<br />
*Opening keynotes<br />
**[http://www.slideshare.net/cckslide/what-i-learned-from-cc-jay-yoon What I learned from CC] - Jay Yoon<br />
**[http://www.slideshare.net/cckslide/the-idea-of-the-commons-future-of-capitalism-yochai-benkler The idea of the commons and the future of capitalism] - Yochai Benkler <br />
*Keynote Panel<br />
**Importance of Creative Commons in the digital era - Yochai Benkler, Ryan Merkley, Jay Yoon<br />
*Exploring Open Business Models<br />
**[http://www.slideshare.net/Paul_Stacey/creative-commons-global-summit-2015-open-business-models-book-and-business-toolkit Open business models book and business toolkit] - Paul Stacey, Sarah Pearson, Teresa Nobre, Fátima São Simão<br />
**[http://www.slideshare.net/terburg/sharing-manual-seoul The Sharing Manual] - Sebastiaan ter Burg [https://vimeo.com/142884101 video recording]<br />
**[http://www.slideshare.net/cckslide/rhymeduck-music-service Rhymeduck Music Service] - Hee-sung Do, Wantreez Music<br />
**[http://www.slideshare.net/cckslide/500px-nuno-silva 500px] - Nuno Silva, 500px<br />
*Social, cultural, and economic implications of open content<br />
**[http://www.slideshare.net/cgreen/global-oer-movement-cc-cc-summit Global OER Movement and CC] - Cable Green <br />
**[http://www.slideshare.net/paulkeller/how-europeana-came-to-embrace-openness How Europeana came to embrace openness] - Paul Keller<br />
**[http://www.slideshare.net/cckslide/ss-54415051 Open content and reuse] - Tae-yong Yoon<br />
*CC in art and film<br />
**The Long Road Project - Reda Zine<br />
*CC Tech Team 1<br />
**Road Map & The List - Ryan Merkley, Rob Myers<br />
*Do-It-Yourself / Maker<br />
**[http://www.slideshare.net/cckslide/open-source-satellite-initiative Open Source Satellite Initiative] - Hojun Song<br />
**Ji-hyun Kim<br />
**[http://www.slideshare.net/cckslide/digital-fabrication-open-source-hardware-and-creative-commons-michael-weinberg Digital Fabrication, Open Source Hardware, and Creative Commons: So Into Each Other] - Michael Weinberg<br />
*[http://www.slideshare.net/technollama/institutional-cc-adoption-in-glam Institutional CC adoption in GLAM] - Andres Guadamuz<br />
*Open Data in Korea and the World<br />
**Seon-tae Kim (KISTI)<br />
**[http://www.slideshare.net/cckslide/open-data-strategy-portal-of-korea-govt Open data strategy & open data portal of Korea govt] - Munshil Choi (NIA)<br />
**Naeema Zarif<br />
*CC Tech Team 2<br />
**CC Search & CC License Chooser - Ryan Merkley, Rob Myers<br />
*Closing keynotes<br />
**[http://www.slideshare.net/cckslide/age-of-emotion-sohyeong-noh Age of emotion] - SohYeong Roh, Art Center Nabi<br />
**[http://www.slideshare.net/cckslide/on-the-shoulders-of-giants-54415246 On the shoulders of giants] - Lila Tretikov, Wikimedia Foundation<br />
<br />
==Friday Oct 16==<br />
*Welcome & Opening Remarks - Paul Brest<br />
*Opening Keynote - Ryan Merkley <br />
*wikiHow announcement of Korean site launch<br />
*Fair use and business <br />
**Jay Yoon<br />
*Sharing City: City rediscovers the values of sharing<br />
**[http://www.slideshare.net/cckslide/3-54416173 Urban Problems Innovative Approaches] - Hyo-kwan Chon, Seoul Metropolitan Government<br />
**[http://www.slideshare.net/cckslide/amsterdam-sharing-city-pieter-bas-van-de-glind Amsterdam Sharing City] - Pieter van de Glind, ShareNL<br />
**[http://www.slideshare.net/cckslide/ss-54416200 Parking lot sharing system] - Dong-hyeon Kim<br />
**[http://www.slideshare.net/cckslide/ss-54416199 Sharing City and Sharing Home] - Sang-hyun Lee, Airbnb<br />
*OER: Mainstreaming and the Moonshot <br />
**Cable Green <br />
**Nicole Allen, TJ Bliss, Delia Browne, Meena Hwang, Ryan Merkley, Stella Hayoung Shin, Alek Tarkowski, Esther Wojcicki<br />
*Showcases of Sharing Culture 1<br />
**Baden Appleyard<br />
**Tyng-Ruey Chuang<br />
**McCoy Smith (see slides from Saturday presentation)<br />
**Chunyan Wang<br />
*Showcases of Sharing Culture 2<br />
**[http://www.slideshare.net/cckslide/ss-54416489 Art of Happy Sharing] - Jinho Jung<br />
**[http://www.slideshare.net/cckslide/400-54416490 Mania DB] - Hyeong-kyu Ryu<br />
**[http://www.slideshare.net/cckslide/2015-open-access-korea Open Access Korea] - Sung-chul Park, National Library of Korea<br />
**[http://www.slideshare.net/mobile/cckslide/data-big-data-and-communication Data, big data and communication] - Ki-Byoung Kim<br />
**[http://www.slideshare.net/cckslide/luxi-island-oer-summer-camp-liu-ping Luxi island OER summer camp] - Liu Ping<br />
**[http://www.slideshare.net/cckslide/free-music-week-jorge-gabriel-jimenez Free Music Week] - Jorge Gabriel Jimenez<br />
*Measuring the impact of open policy for GLAM - Klaudia Grabowska<br />
*Legal Code Translations 2 Years Strong: Successes, Challenges and Impact <br />
**Carolina Botero, Marianne Diaz, Hala Essalmawi, Ignasi Labastida, Maksym Naumko, Sarah Pearson, Dr. Mohammad El Said, Chunyan Wang<br />
*[http://www.slideshare.net/cckslide/over-the-long-terms-the-state-of-activism-on-toolong-copyright-terms-and-how-you-can-join-in Copyright Advocacy: Over the Long Terms: The State of Activism on Too-Long Copyright Terms (And How You Can Join In)] - Maira Sutton, Parker Higgins<br />
*Showcases of Sharing Culture 3 - [http://www.slideshare.net/cckslide/showcases-of-sharing-culture-3 slide deck]<br />
**Free Music Communities in Uruguay - Salvador Garcia - no slides<br />
**How do we scale OER? - Matt McGregor - slides in deck<br />
**Global Voices and CC - Mohamed ElGohary - slides in deck<br />
**Helping authors who write to be read -- Michael Wolfe - slides<br />
**Introducing Embedr.eu - Maarten Zeinstra - slides in deck<br />
**New Palmyra and Free Souls 2 - Christopher Adams - slides in deck<br />
**[https://prezi.com/f3vl5w91bdme/copyright-relinquishment-across-the-world/ CC0 and copyright relinquishment] - Andres Guadamuz<br />
*CC Licensing the Sum of All Knowledge: Community and Legal Considerations for Wikipedia and Platforms <br />
**Jane Park, Baden Appleyard, Tyng-Ruey Chuang, Stephen LaPorte, Sarah Pearson ([http://www.slideshare.net/shpearson/legal-considerations-for-platforms?related=2 slides]), Tomoaki Watanabe ([http://www.slideshare.net/TomoakiWatanabe/platform-terms-and-cc-licenses slides])<br />
*OER Project Showcase <br />
**Cable Green <br />
**George Abdelnour, Baden Appleyard, Kamil Åšliwowski, Dr Fawzi Baroud, Mostafa Azad Kamal, Simeon Oriko, Alek Tarkowski<br />
*Open Access: Developing tools, practices, and stories in support of OA publishing <br />
**Ignasi Labastida, Thomas Margoni, Diane Peters ([http://www.slideshare.net/peterspdx/retaining-and-regaining-author-publication-rights slides]), Georgina Taylor, Michael Wolfe<br />
*[http://www.slideshare.net/cckslide/unpacking-an-activist-toolbox-effs-tools-and-tips-for-effective-copyright-advocacy-maira-sutton Unpacking an Activist Toolbox: EFF's Tools and Tips for Effective Copyright Advocacy] - Maira Sutton, Parker Higgins<br />
*Closing Keynote<br />
**[http://www.slideshare.net/cckslide/ecological-internet-kilnam-chon Ecological Internet] - Kilnam Chon <br />
*Closing Panel<br />
**Open Internet Issues - Renata Avila, Yochai Benkler, Kilnam Chon<br />
<br />
==Saturday Oct 17==<br />
*Welcome & Opening Remarks <br />
**Michael Carrol<br />
*[http://www.slideshare.net/cckslide/copyright-reform-and-the-role-of-creative-commons Copyright reform and the role of Creative Commons] - Julia Reda <br />
*CC Affiliates Policies Hands-On - John Weitzmann<br />
*Creative Commons and the Future of Design: The 3D and Hardware Commons <br />
**How will CC shape the future of design? - Jane Park<br />
**Mahmoud Abu-Wardeh <br />
**A pick into open hardware - Tomoaki Watanabe<br />
**Michael Weinberg<br />
*Jump-starting commons advocacy and copyright reform<br />
**Delia Browne, Paul Keller, Claudio Ruiz, Maira Sutton, Alek Tarkowski, Timothy Vollmer<br />
*The Vibrant and Social Commons: Designing for User Engagement <br />
**Ryan Merkley, Jane Park, Eric Steuer<br />
*Rights Statements, the Public Domain Mark, and Blockchain: Extending the CC infrastructure <br />
**Constance Choi, Primavera De Filippi, Paul Keller, Diane Peters ([http://www.slideshare.net/peterspdx/creative-commons-public-domain-mark-version-2 slides]), Maarten Zeinstra<br />
*Open Licensing Education and Advocacy - Tools and Tactics for Communicating with Decisionmakers <br />
**Meredith Jacob<br />
*Affiliates 2.0 - CC as a true network organisation followup discussion <br />
**Paul Keller, Alek Tarkowski<br />
*Open Hardware and Design: Solutions for Licensing Rights Beyond Copyright and Open Hardware Certification <br />
**Thomas Margoni, Diane Peters ([http://www.slideshare.net/peterspdx/extending-the-creative-commons-license-suite ]slides), McCoy Smith, Michael Weinberg<br />
*Closing Keynote - Carolina Botero, Tobias Schonwetter<br />
*Wrap-up Summary - Ryan Merkley</div>CCID-diane petershttps://wiki.creativecommons.org/index.php?title=Global_Summit_2015/Presentations_%26_Notes&diff=114534Global Summit 2015/Presentations & Notes2015-10-26T08:12:48Z<p>CCID-diane peters: /* Friday Oct 16 */</p>
<hr />
<div>==Wednesday Oct 14==<br />
CC Affiliate MiniConference<br />
<br />
==Thursday Oct 15==<br />
*Welcome & Opening Remarks - Jeongwook Seo <br />
*Sponsor Spotlight - Rick Falkvinge, Private Internet Access<br />
*Opening keynotes<br />
**Redefine Creative Commons - Jay Yoon<br />
**The idea of the commons and the future of capitalism - Yochai Benkler <br />
*Keynote Panel<br />
**Importance of Creative Commons in the digital era - Yochai Benkler, Ryan Merkley, Jay Yoon<br />
*Exploring Open Business Models<br />
**Paul Stacey, Sarah Pearson<br />
**Teresa Nobre, Fátima São Simão<br />
**Sebastiaan ter Burg<br />
**Hee-sung Do, Wantreez Music<br />
**Nuno Silva, 500px [[File:500px NunoSilva.pdf]]<br />
*Social, cultural, and economic implications of open content<br />
**[http://www.slideshare.net/cgreen/global-oer-movement-cc-cc-summit Global OER Movement and CC] - Cable Green <br />
**[http://www.slideshare.net/paulkeller/how-europeana-came-to-embrace-openness How Europeana came to embrace openness] - Paul Keller<br />
**Tae-yong Yoon<br />
*CC in art and film<br />
**The Long Road Project - Reda Zine<br />
*CC Tech Team 1<br />
**Road Map & The List - Ryan Merkley, Rob Myers<br />
*Do-It-Yourself / Maker<br />
**Hojun Song<br />
**Ji-hyun Kim<br />
**Digital Fabrication, Open Source Hardware, and Creative Commons: So Into Each Other - Michael Weinberg<br />
*CC and openness in GLAM - Andres Guadamuz<br />
*Open Data in Korea and the World<br />
**Seon-tae Kim (KISTI)<br />
**Dong-seok Kang (NIA)<br />
**Naeema Zarif<br />
*CC Tech Team 2<br />
**CC Search & CC License Chooser - Ryan Merkley, Rob Myers<br />
*Closing keynotes<br />
**NABI's Experiment - SohYeong Roh, Art Center Nabi<br />
**Lila Tretikov, Wikimedia Foundation<br />
<br />
==Friday Oct 16==<br />
*Welcome & Opening Remarks - Paul Brest<br />
*Opening Keynote - Ryan Merkley <br />
*wikiHow announcement of Korean site launch<br />
*Fair use and business <br />
**Jay Yoon<br />
*Sharing City: City rediscovers the values of sharing<br />
**Hyo-kwan Chon<br />
**Pieter van de Glind<br />
**Dong-hyeon Kim<br />
**Sang-hyun Lee<br />
*OER: Mainstreaming and the Moonshot <br />
**Cable Green <br />
**Nicole Allen, TJ Bliss, Delia Browne, Meena Hwang, Ryan Merkley, Stella Hayoung Shin, Alek Tarkowski, Esther Wojcicki<br />
*Showcases of Sharing Culture 1<br />
**Baden Appleyard<br />
**Tyng-Ruey Chuang<br />
**McCoy Smith<br />
**Chunyan Wang<br />
*Showcases of Sharing Culture 2<br />
*Measuring the impact of open policy for GLAM - Klaudia Grabowska<br />
*Legal Code Translations 2 Years Strong: Successes, Challenges and Impact <br />
**Carolina Botero, Marianne Diaz, Hala Essalmawi, Ignasi Labastida, Maksym Naumko, Sarah Pearson, Dr. Mohammad El Said, Chunyan Wang<br />
*Copyright Advocacy: Over the Long Terms: The State of Activism on Too-Long Copyright Terms (And How You Can Join In) - Parker Higgins<br />
*Showcases of Sharing Culture 3<br />
**Free Music Communities in Uruguay - Salvador Garcia - no slides<br />
**How do we scale OER? - Matt McGregor - slides in deck<br />
**Global Voices and CC - Mohamed ElGohary - slides in deck<br />
**Helping authors who write to be read -- Michael Wolfe - slides<br />
**Introducing Embedr.eu - Maarten Zeinstra - slides in deck<br />
**New Palmyra and Free Souls 2 - Christopher Adams - slides in deck<br />
**CC0 and copyright relinquishment - Andres Guadamuz [[https://prezi.com/f3vl5w91bdme/copyright-relinquishment-across-the-world/ prezi]]<br />
*CC Licensing the Sum of All Knowledge: Community and Legal Considerations for Wikipedia and Platforms <br />
**Jane Park, Baden Appleyard, Tyng-Ruey Chuang, Stephen LaPorte, Sarah Pearson, Tomoaki Watanabe<br />
*OER Project Showcase <br />
**Cable Green <br />
**George Abdelnour, Baden Appleyard, Kamil Åšliwowski, Dr Fawzi Baroud, Mostafa Azad Kamal, Simeon Oriko, Alek Tarkowski<br />
*Open Access: Developing tools, practices, and stories in support of OA publishing <br />
**Ignasi Labastida, Thomas Margoni, Diane Peters ([http://www.slideshare.net/peterspdx/retaining-and-regaining-author-publication-rights slides]), Georgina Taylor, Michael Wolfe<br />
*Unpacking an Activist Toolbox: EFF's Tools and Tips for Effective Copyright Advocacy <br />
**Maira Sutton<br />
*Closing Keynote<br />
**Ecological Internet - Kilnam Chon <br />
*Closing Panel<br />
**Open Internet Issues - Renata Avila, Yochai Benkler, Kilnam Chon<br />
<br />
==Saturday Oct 17==<br />
*Welcome & Opening Remarks <br />
**Michael Carrol<br />
*Opening Keynote - Julia Reda <br />
*CC Affiliates Policies Hands-On - John Weitzmann<br />
*Creative Commons and the Future of Design: The 3D and Hardware Commons <br />
**How will CC shape the future of design? - Jane Park<br />
**Mahmoud Abu-Wardeh <br />
**A pick into open hardware - Tomoaki Watanabe<br />
**Michael Weinberg<br />
*Jump-starting commons advocacy and copyright reform<br />
**Delia Browne, Paul Keller, Claudio Ruiz, Maira Sutton, Alek Tarkowski, Timothy Vollmer<br />
*The Vibrant and Social Commons: Designing for User Engagement <br />
**Ryan Merkley, Jane Park, Eric Steuer<br />
*Rights Statements, the Public Domain Mark, and Blockchain: Extending the CC infrastructure <br />
**Constance Choi, Primavera De Filippi, Paul Keller, Diane Peters ([http://www.slideshare.net/peterspdx/creative-commons-public-domain-mark-version-2 slides]), Maarten Zeinstra<br />
*Open Licensing Education and Advocacy - Tools and Tactics for Communicating with Decisionmakers <br />
**Meredith Jacob<br />
*Affiliates 2.0 - CC as a true network organisation followup discussion <br />
**Paul Keller, Alek Tarkowski<br />
*Open Hardware and Design: Solutions for Licensing Rights Beyond Copyright and Open Hardware Certification <br />
**Thomas Margoni, Diane Peters ([http://www.slideshare.net/peterspdx/extending-the-creative-commons-license-suite ]slides), McCoy Smith, Michael Weinberg<br />
*Closing Keynote - Carolina Botero, Tobias Schonwetter<br />
*Wrap-up Summary - Ryan Merkley</div>CCID-diane petershttps://wiki.creativecommons.org/index.php?title=Global_Summit_2015/Presentations_%26_Notes&diff=114533Global Summit 2015/Presentations & Notes2015-10-26T08:11:35Z<p>CCID-diane peters: /* Friday Oct 16 */</p>
<hr />
<div>==Wednesday Oct 14==<br />
CC Affiliate MiniConference<br />
<br />
==Thursday Oct 15==<br />
*Welcome & Opening Remarks - Jeongwook Seo <br />
*Sponsor Spotlight - Rick Falkvinge, Private Internet Access<br />
*Opening keynotes<br />
**Redefine Creative Commons - Jay Yoon<br />
**The idea of the commons and the future of capitalism - Yochai Benkler <br />
*Keynote Panel<br />
**Importance of Creative Commons in the digital era - Yochai Benkler, Ryan Merkley, Jay Yoon<br />
*Exploring Open Business Models<br />
**Paul Stacey, Sarah Pearson<br />
**Teresa Nobre, Fátima São Simão<br />
**Sebastiaan ter Burg<br />
**Hee-sung Do, Wantreez Music<br />
**Nuno Silva, 500px [[File:500px NunoSilva.pdf]]<br />
*Social, cultural, and economic implications of open content<br />
**[http://www.slideshare.net/cgreen/global-oer-movement-cc-cc-summit Global OER Movement and CC] - Cable Green <br />
**[http://www.slideshare.net/paulkeller/how-europeana-came-to-embrace-openness How Europeana came to embrace openness] - Paul Keller<br />
**Tae-yong Yoon<br />
*CC in art and film<br />
**The Long Road Project - Reda Zine<br />
*CC Tech Team 1<br />
**Road Map & The List - Ryan Merkley, Rob Myers<br />
*Do-It-Yourself / Maker<br />
**Hojun Song<br />
**Ji-hyun Kim<br />
**Digital Fabrication, Open Source Hardware, and Creative Commons: So Into Each Other - Michael Weinberg<br />
*CC and openness in GLAM - Andres Guadamuz<br />
*Open Data in Korea and the World<br />
**Seon-tae Kim (KISTI)<br />
**Dong-seok Kang (NIA)<br />
**Naeema Zarif<br />
*CC Tech Team 2<br />
**CC Search & CC License Chooser - Ryan Merkley, Rob Myers<br />
*Closing keynotes<br />
**NABI's Experiment - SohYeong Roh, Art Center Nabi<br />
**Lila Tretikov, Wikimedia Foundation<br />
<br />
==Friday Oct 16==<br />
*Welcome & Opening Remarks - Paul Brest<br />
*Opening Keynote - Ryan Merkley <br />
*wikiHow announcement of Korean site launch<br />
*Fair use and business <br />
**Jay Yoon<br />
*Sharing City: City rediscovers the values of sharing<br />
**Hyo-kwan Chon<br />
**Pieter van de Glind<br />
**Dong-hyeon Kim<br />
**Sang-hyun Lee<br />
*OER: Mainstreaming and the Moonshot <br />
**Cable Green <br />
**Nicole Allen, TJ Bliss, Delia Browne, Meena Hwang, Ryan Merkley, Stella Hayoung Shin, Alek Tarkowski, Esther Wojcicki<br />
*Showcases of Sharing Culture 1<br />
**Baden Appleyard<br />
**Tyng-Ruey Chuang<br />
**McCoy Smith<br />
**Chunyan Wang<br />
*Showcases of Sharing Culture 2<br />
*Measuring the impact of open policy for GLAM - Klaudia Grabowska<br />
*Legal Code Translations 2 Years Strong: Successes, Challenges and Impact <br />
**Carolina Botero, Marianne Diaz, Hala Essalmawi, Ignasi Labastida, Maksym Naumko, Sarah Pearson, Dr. Mohammad El Said, Chunyan Wang<br />
*Copyright Advocacy: Over the Long Terms: The State of Activism on Too-Long Copyright Terms (And How You Can Join In) - Parker Higgins<br />
*Showcases of Sharing Culture 3<br />
**Free Music Communities in Uruguay - Salvador Garcia - no slides<br />
**How do we scale OER? - Matt McGregor - slides in deck<br />
**Global Voices and CC - Mohamed ElGohary - slides in deck<br />
**Helping authors who write to be read -- Michael Wolfe - slides<br />
**Introducing Embedr.eu - Maarten Zeinstra - slides in deck<br />
**New Palmyra and Free Souls 2 - Christopher Adams - slides in deck<br />
**CC0 and copyright relinquishment - Andres Guadamuz [[https://prezi.com/f3vl5w91bdme/copyright-relinquishment-across-the-world/ prezi]]<br />
*CC Licensing the Sum of All Knowledge: Community and Legal Considerations for Wikipedia and Platforms <br />
**Jane Park, Baden Appleyard, Tyng-Ruey Chuang, Stephen LaPorte, Sarah Pearson, Tomoaki Watanabe<br />
*OER Project Showcase <br />
**Cable Green <br />
**George Abdelnour, Baden Appleyard, Kamil Åšliwowski, Dr Fawzi Baroud, Mostafa Azad Kamal, Simeon Oriko, Alek Tarkowski<br />
*Open Access: Developing tools, practices, and stories in support of OA publishing <br />
**Ignasi Labastida, Thomas Margoni, Diane Peters ([http://www.slideshare.net/peterspdx/retaining-and-regaining-author-publication-rights ]slides), Georgina Taylor, Michael Wolfe<br />
*Unpacking an Activist Toolbox: EFF's Tools and Tips for Effective Copyright Advocacy <br />
**Maira Sutton<br />
*Closing Keynote<br />
**Ecological Internet - Kilnam Chon <br />
*Closing Panel<br />
**Open Internet Issues - Renata Avila, Yochai Benkler, Kilnam Chon<br />
<br />
==Saturday Oct 17==<br />
*Welcome & Opening Remarks <br />
**Michael Carrol<br />
*Opening Keynote - Julia Reda <br />
*CC Affiliates Policies Hands-On - John Weitzmann<br />
*Creative Commons and the Future of Design: The 3D and Hardware Commons <br />
**How will CC shape the future of design? - Jane Park<br />
**Mahmoud Abu-Wardeh <br />
**A pick into open hardware - Tomoaki Watanabe<br />
**Michael Weinberg<br />
*Jump-starting commons advocacy and copyright reform<br />
**Delia Browne, Paul Keller, Claudio Ruiz, Maira Sutton, Alek Tarkowski, Timothy Vollmer<br />
*The Vibrant and Social Commons: Designing for User Engagement <br />
**Ryan Merkley, Jane Park, Eric Steuer<br />
*Rights Statements, the Public Domain Mark, and Blockchain: Extending the CC infrastructure <br />
**Constance Choi, Primavera De Filippi, Paul Keller, Diane Peters ([http://www.slideshare.net/peterspdx/creative-commons-public-domain-mark-version-2 slides]), Maarten Zeinstra<br />
*Open Licensing Education and Advocacy - Tools and Tactics for Communicating with Decisionmakers <br />
**Meredith Jacob<br />
*Affiliates 2.0 - CC as a true network organisation followup discussion <br />
**Paul Keller, Alek Tarkowski<br />
*Open Hardware and Design: Solutions for Licensing Rights Beyond Copyright and Open Hardware Certification <br />
**Thomas Margoni, Diane Peters ([http://www.slideshare.net/peterspdx/extending-the-creative-commons-license-suite ]slides), McCoy Smith, Michael Weinberg<br />
*Closing Keynote - Carolina Botero, Tobias Schonwetter<br />
*Wrap-up Summary - Ryan Merkley</div>CCID-diane petershttps://wiki.creativecommons.org/index.php?title=Global_Summit_2015/Presentations_%26_Notes&diff=114532Global Summit 2015/Presentations & Notes2015-10-26T08:08:31Z<p>CCID-diane peters: /* Saturday Oct 17 */</p>
<hr />
<div>==Wednesday Oct 14==<br />
CC Affiliate MiniConference<br />
<br />
==Thursday Oct 15==<br />
*Welcome & Opening Remarks - Jeongwook Seo <br />
*Sponsor Spotlight - Rick Falkvinge, Private Internet Access<br />
*Opening keynotes<br />
**Redefine Creative Commons - Jay Yoon<br />
**The idea of the commons and the future of capitalism - Yochai Benkler <br />
*Keynote Panel<br />
**Importance of Creative Commons in the digital era - Yochai Benkler, Ryan Merkley, Jay Yoon<br />
*Exploring Open Business Models<br />
**Paul Stacey, Sarah Pearson<br />
**Teresa Nobre, Fátima São Simão<br />
**Sebastiaan ter Burg<br />
**Hee-sung Do, Wantreez Music<br />
**Nuno Silva, 500px [[File:500px NunoSilva.pdf]]<br />
*Social, cultural, and economic implications of open content<br />
**[http://www.slideshare.net/cgreen/global-oer-movement-cc-cc-summit Global OER Movement and CC] - Cable Green <br />
**[http://www.slideshare.net/paulkeller/how-europeana-came-to-embrace-openness How Europeana came to embrace openness] - Paul Keller<br />
**Tae-yong Yoon<br />
*CC in art and film<br />
**The Long Road Project - Reda Zine<br />
*CC Tech Team 1<br />
**Road Map & The List - Ryan Merkley, Rob Myers<br />
*Do-It-Yourself / Maker<br />
**Hojun Song<br />
**Ji-hyun Kim<br />
**Digital Fabrication, Open Source Hardware, and Creative Commons: So Into Each Other - Michael Weinberg<br />
*CC and openness in GLAM - Andres Guadamuz<br />
*Open Data in Korea and the World<br />
**Seon-tae Kim (KISTI)<br />
**Dong-seok Kang (NIA)<br />
**Naeema Zarif<br />
*CC Tech Team 2<br />
**CC Search & CC License Chooser - Ryan Merkley, Rob Myers<br />
*Closing keynotes<br />
**NABI's Experiment - SohYeong Roh, Art Center Nabi<br />
**Lila Tretikov, Wikimedia Foundation<br />
<br />
==Friday Oct 16==<br />
*Welcome & Opening Remarks - Paul Brest<br />
*Opening Keynote - Ryan Merkley <br />
*wikiHow announcement of Korean site launch<br />
*Fair use and business <br />
**Jay Yoon<br />
*Sharing City: City rediscovers the values of sharing<br />
**Hyo-kwan Chon<br />
**Pieter van de Glind<br />
**Dong-hyeon Kim<br />
**Sang-hyun Lee<br />
*OER: Mainstreaming and the Moonshot <br />
**Cable Green <br />
**Nicole Allen, TJ Bliss, Delia Browne, Meena Hwang, Ryan Merkley, Stella Hayoung Shin, Alek Tarkowski, Esther Wojcicki<br />
*Showcases of Sharing Culture 1<br />
**Baden Appleyard<br />
**Tyng-Ruey Chuang<br />
**McCoy Smith<br />
**Chunyan Wang<br />
*Showcases of Sharing Culture 2<br />
*Measuring the impact of open policy for GLAM - Klaudia Grabowska<br />
*Legal Code Translations 2 Years Strong: Successes, Challenges and Impact <br />
**Carolina Botero, Marianne Diaz, Hala Essalmawi, Ignasi Labastida, Maksym Naumko, Sarah Pearson, Dr. Mohammad El Said, Chunyan Wang<br />
*Copyright Advocacy: Over the Long Terms: The State of Activism on Too-Long Copyright Terms (And How You Can Join In) - Parker Higgins<br />
*Showcases of Sharing Culture 3<br />
**Free Music Communities in Uruguay - Salvador Garcia - no slides<br />
**How do we scale OER? - Matt McGregor - slides in deck<br />
**Global Voices and CC - Mohamed ElGohary - slides in deck<br />
**Helping authors who write to be read -- Michael Wolfe - slides<br />
**Introducing Embedr.eu - Maarten Zeinstra - slides in deck<br />
**New Palmyra and Free Souls 2 - Christopher Adams - slides in deck<br />
**CC0 and copyright relinquishment - Andres Guadamuz [[https://prezi.com/f3vl5w91bdme/copyright-relinquishment-across-the-world/ prezi]]<br />
*CC Licensing the Sum of All Knowledge: Community and Legal Considerations for Wikipedia and Platforms <br />
**Jane Park, Baden Appleyard, Tyng-Ruey Chuang, Stephen LaPorte, Sarah Pearson, Tomoaki Watanabe<br />
*OER Project Showcase <br />
**Cable Green <br />
**George Abdelnour, Baden Appleyard, Kamil Åšliwowski, Dr Fawzi Baroud, Mostafa Azad Kamal, Simeon Oriko, Alek Tarkowski<br />
*Open Access: Developing tools, practices, and stories in support of OA publishing <br />
**Ignasi Labastida, Thomas Margoni, Diane Peters, Georgina Taylor, Michael Wolfe<br />
*Unpacking an Activist Toolbox: EFF's Tools and Tips for Effective Copyright Advocacy <br />
**Maira Sutton<br />
*Closing Keynote<br />
**Ecological Internet - Kilnam Chon <br />
*Closing Panel<br />
**Open Internet Issues - Renata Avila, Yochai Benkler, Kilnam Chon<br />
<br />
==Saturday Oct 17==<br />
*Welcome & Opening Remarks <br />
**Michael Carrol<br />
*Opening Keynote - Julia Reda <br />
*CC Affiliates Policies Hands-On - John Weitzmann<br />
*Creative Commons and the Future of Design: The 3D and Hardware Commons <br />
**How will CC shape the future of design? - Jane Park<br />
**Mahmoud Abu-Wardeh <br />
**A pick into open hardware - Tomoaki Watanabe<br />
**Michael Weinberg<br />
*Jump-starting commons advocacy and copyright reform<br />
**Delia Browne, Paul Keller, Claudio Ruiz, Maira Sutton, Alek Tarkowski, Timothy Vollmer<br />
*The Vibrant and Social Commons: Designing for User Engagement <br />
**Ryan Merkley, Jane Park, Eric Steuer<br />
*Rights Statements, the Public Domain Mark, and Blockchain: Extending the CC infrastructure <br />
**Constance Choi, Primavera De Filippi, Paul Keller, Diane Peters ([http://www.slideshare.net/peterspdx/creative-commons-public-domain-mark-version-2 slides]), Maarten Zeinstra<br />
*Open Licensing Education and Advocacy - Tools and Tactics for Communicating with Decisionmakers <br />
**Meredith Jacob<br />
*Affiliates 2.0 - CC as a true network organisation followup discussion <br />
**Paul Keller, Alek Tarkowski<br />
*Open Hardware and Design: Solutions for Licensing Rights Beyond Copyright and Open Hardware Certification <br />
**Thomas Margoni, Diane Peters ([http://www.slideshare.net/peterspdx/extending-the-creative-commons-license-suite ]slides), McCoy Smith, Michael Weinberg<br />
*Closing Keynote - Carolina Botero, Tobias Schonwetter<br />
*Wrap-up Summary - Ryan Merkley</div>CCID-diane petershttps://wiki.creativecommons.org/index.php?title=Global_Summit_2015/Presentations_%26_Notes&diff=114531Global Summit 2015/Presentations & Notes2015-10-26T08:05:58Z<p>CCID-diane peters: /* Saturday Oct 17 */</p>
<hr />
<div>==Wednesday Oct 14==<br />
CC Affiliate MiniConference<br />
<br />
==Thursday Oct 15==<br />
*Welcome & Opening Remarks - Jeongwook Seo <br />
*Sponsor Spotlight - Rick Falkvinge, Private Internet Access<br />
*Opening keynotes<br />
**Redefine Creative Commons - Jay Yoon<br />
**The idea of the commons and the future of capitalism - Yochai Benkler <br />
*Keynote Panel<br />
**Importance of Creative Commons in the digital era - Yochai Benkler, Ryan Merkley, Jay Yoon<br />
*Exploring Open Business Models<br />
**Paul Stacey, Sarah Pearson<br />
**Teresa Nobre, Fátima São Simão<br />
**Sebastiaan ter Burg<br />
**Hee-sung Do, Wantreez Music<br />
**Nuno Silva, 500px [[File:500px NunoSilva.pdf]]<br />
*Social, cultural, and economic implications of open content<br />
**[http://www.slideshare.net/cgreen/global-oer-movement-cc-cc-summit Global OER Movement and CC] - Cable Green <br />
**[http://www.slideshare.net/paulkeller/how-europeana-came-to-embrace-openness How Europeana came to embrace openness] - Paul Keller<br />
**Tae-yong Yoon<br />
*CC in art and film<br />
**The Long Road Project - Reda Zine<br />
*CC Tech Team 1<br />
**Road Map & The List - Ryan Merkley, Rob Myers<br />
*Do-It-Yourself / Maker<br />
**Hojun Song<br />
**Ji-hyun Kim<br />
**Digital Fabrication, Open Source Hardware, and Creative Commons: So Into Each Other - Michael Weinberg<br />
*CC and openness in GLAM - Andres Guadamuz<br />
*Open Data in Korea and the World<br />
**Seon-tae Kim (KISTI)<br />
**Dong-seok Kang (NIA)<br />
**Naeema Zarif<br />
*CC Tech Team 2<br />
**CC Search & CC License Chooser - Ryan Merkley, Rob Myers<br />
*Closing keynotes<br />
**NABI's Experiment - SohYeong Roh, Art Center Nabi<br />
**Lila Tretikov, Wikimedia Foundation<br />
<br />
==Friday Oct 16==<br />
*Welcome & Opening Remarks - Paul Brest<br />
*Opening Keynote - Ryan Merkley <br />
*wikiHow announcement of Korean site launch<br />
*Fair use and business <br />
**Jay Yoon<br />
*Sharing City: City rediscovers the values of sharing<br />
**Hyo-kwan Chon<br />
**Pieter van de Glind<br />
**Dong-hyeon Kim<br />
**Sang-hyun Lee<br />
*OER: Mainstreaming and the Moonshot <br />
**Cable Green <br />
**Nicole Allen, TJ Bliss, Delia Browne, Meena Hwang, Ryan Merkley, Stella Hayoung Shin, Alek Tarkowski, Esther Wojcicki<br />
*Showcases of Sharing Culture 1<br />
**Baden Appleyard<br />
**Tyng-Ruey Chuang<br />
**McCoy Smith<br />
**Chunyan Wang<br />
*Showcases of Sharing Culture 2<br />
*Measuring the impact of open policy for GLAM - Klaudia Grabowska<br />
*Legal Code Translations 2 Years Strong: Successes, Challenges and Impact <br />
**Carolina Botero, Marianne Diaz, Hala Essalmawi, Ignasi Labastida, Maksym Naumko, Sarah Pearson, Dr. Mohammad El Said, Chunyan Wang<br />
*Copyright Advocacy: Over the Long Terms: The State of Activism on Too-Long Copyright Terms (And How You Can Join In) - Parker Higgins<br />
*Showcases of Sharing Culture 3<br />
**Free Music Communities in Uruguay - Salvador Garcia - no slides<br />
**How do we scale OER? - Matt McGregor - slides in deck<br />
**Global Voices and CC - Mohamed ElGohary - slides in deck<br />
**Helping authors who write to be read -- Michael Wolfe - slides<br />
**Introducing Embedr.eu - Maarten Zeinstra - slides in deck<br />
**New Palmyra and Free Souls 2 - Christopher Adams - slides in deck<br />
**CC0 and copyright relinquishment - Andres Guadamuz [[https://prezi.com/f3vl5w91bdme/copyright-relinquishment-across-the-world/ prezi]]<br />
*CC Licensing the Sum of All Knowledge: Community and Legal Considerations for Wikipedia and Platforms <br />
**Jane Park, Baden Appleyard, Tyng-Ruey Chuang, Stephen LaPorte, Sarah Pearson, Tomoaki Watanabe<br />
*OER Project Showcase <br />
**Cable Green <br />
**George Abdelnour, Baden Appleyard, Kamil Åšliwowski, Dr Fawzi Baroud, Mostafa Azad Kamal, Simeon Oriko, Alek Tarkowski<br />
*Open Access: Developing tools, practices, and stories in support of OA publishing <br />
**Ignasi Labastida, Thomas Margoni, Diane Peters, Georgina Taylor, Michael Wolfe<br />
*Unpacking an Activist Toolbox: EFF's Tools and Tips for Effective Copyright Advocacy <br />
**Maira Sutton<br />
*Closing Keynote<br />
**Ecological Internet - Kilnam Chon <br />
*Closing Panel<br />
**Open Internet Issues - Renata Avila, Yochai Benkler, Kilnam Chon<br />
<br />
==Saturday Oct 17==<br />
*Welcome & Opening Remarks <br />
**Michael Carrol<br />
*Opening Keynote - Julia Reda <br />
*CC Affiliates Policies Hands-On - John Weitzmann<br />
*Creative Commons and the Future of Design: The 3D and Hardware Commons <br />
**How will CC shape the future of design? - Jane Park<br />
**Mahmoud Abu-Wardeh <br />
**A pick into open hardware - Tomoaki Watanabe<br />
**Michael Weinberg<br />
*Jump-starting commons advocacy and copyright reform<br />
**Delia Browne, Paul Keller, Claudio Ruiz, Maira Sutton, Alek Tarkowski, Timothy Vollmer<br />
*The Vibrant and Social Commons: Designing for User Engagement <br />
**Ryan Merkley, Jane Park, Eric Steuer<br />
*Rights Statements, the Public Domain Mark, and Blockchain: Extending the CC infrastructure <br />
**Constance Choi, Primavera De Filippi, Paul Keller, Diane Peters ([http://www.slideshare.net/peterspdx/creative-commons-public-domain-mark-version-2 slides]), Maarten Zeinstra<br />
*Open Licensing Education and Advocacy - Tools and Tactics for Communicating with Decisionmakers <br />
**Meredith Jacob<br />
*Affiliates 2.0 - CC as a true network organisation followup discussion <br />
**Paul Keller, Alek Tarkowski<br />
*Open Hardware and Design: Solutions for Licensing Rights Beyond Copyright and Open Hardware Certification <br />
**Thomas Margoni, Diane Peters, McCoy Smith, Michael Weinberg<br />
*Closing Keynote - Carolina Botero, Tobias Schonwetter<br />
*Wrap-up Summary - Ryan Merkley</div>CCID-diane petershttps://wiki.creativecommons.org/index.php?title=ShareAlike_compatibility&diff=114400ShareAlike compatibility2015-09-21T11:45:54Z<p>CCID-diane peters: /* FAQs about ShareAlike compatibility */</p>
<hr />
<div>==FAQs about ShareAlike compatibility==<br />
<br />
'''What is ShareAlike compatibility and why is it important?'''<br />
<br />
The ShareAlike licenses are designed to ensure that the freedoms associated with a licensed work survive as the work is adapted by others and that those freedoms attach to adaptations of the work as well. There are other copyleft licenses designed for this same purpose, but unfortunately, the works licensed under these other licenses are not compatible with works licensed under BY-SA. Creative Commons created the [https://wiki.creativecommons.org/ShareAlike_compatibility_criteria ShareAlike compatibility process] as a means to solving this problem. The process allows CC to evaluate other copyleft licenses to determine if they are similar enough to BY-SA to meet licensor expectations to be deemed compatible. BY-SA Compatible Licenses are listed [https://creativecommons.org/compatiblelicenses here]. <br />
<br />
'''How does ShareAlike compatibility work?'''<br />
<br />
Once a license is declared compatible with BY-SA, anyone adapting BY-SA works can apply that license to their own contributions to the adaptation. With version 4.0, future versions of BY-SA are automatically compatible. Non-CC licenses have to undergo the ShareAlike compatibility process to be officially designated as a BY-SA Compatible License by CC. In either case, if someone applies a compatible license to an adaptation, both the original BY-SA license and the compatible license apply to the adaptation and must be followed. However, downstream users of the adaptation may choose to look ‘'''only at the compatible license''' (that is, the last license applied) to determine what their attribution and ShareAlike obligations are '''under both licenses''' when they reuse the work. <br />
<br />
'''What does one-way or two-way compatibility mean?'''<br />
<br />
One-way compatibility means that you may adapt work under one license (X) and apply a second license (Y) to your own contributions, but you may not adapt work under the Y license and apply the X license to your contributions. For example, CC BY is one-way compatible with BY-SA. You may adapt a BY work and apply BY-SA to your contributions, but you may not adapt a BY-SA work and apply BY to your contributions. <br />
<br />
Two-way compatibility means that you may adapt work under one license (X) and apply a second license (Y), and vice versa. <br />
<br />
For ShareAlike compatibility, a license listed as a ShareAlike Compatible License on the [https://creativecommons.org/compatiblelicenses compatible licenses page] is two-way compatible unless otherwise noted. <br />
<br />
'''What licenses are compatible with BY-SA?'''<br />
<br />
Different versions of BY-SA have [https://wiki.creativecommons.org/License_Versions#Compatibility_mechanism_in_BY-SA_licenses different compatibility mechanisms]. Each version is addressed below.<br />
<br />
:*For BY-SA 4.0, all future versions of BY-SA and all ports (if any) of BY-SA 4.0 or later are automatically compatible, as well as licenses explicitly deemed compatible pursuant to the ShareAlike compatibility process<br />
<br />
:*For BY-SA 3.0, all future versions of BY-SA and all ports of BY-SA 3.0 or later are automatically compatible, as well as licenses explicitly deemed compatible pursuant to the ShareAlike compatibility process<br />
<br />
:*For BY-SA 2.0, all future versions of BY-SA and all ports of BY-SA 2.0 or later are automatically compatible<br />
<br />
:*For BY-SA 1.0, only BY-SA 1.0 is compatible. <br />
<br />
'''Why did CC choose the Free Art License to be the first BY-SA Compatible License?'''<br />
<br />
Drafted in 2000, the Free Art License was one of the original copyleft licenses designed for content, not code. The [http://artlibre.org/licence/lal/en/ latest version] (1.3) was published in 2007 with an eye toward compatibility with CC licenses. The FAL 1.3 is very similar to BY-SA 4.0 in spirit and substance, and raised no significant obstacles to compatibility. For a detailed explanation of the policy decisions involved in the compatibility determination, see [https://wiki.creativecommons.org/ShareAlike_compatibility:_FAL here]. <br />
<br />
'''Why did CC decide to pursue compatibility with a software license (GPLv3)?'''<br />
<br />
In some niche areas such as gaming, content is increasingly blended with code in ways that make it difficult for downstream users to differentiate between the two. Developers in these fields sometimes abstain from integrating BY-SA content into GPL-licensed software projects because of potential conflict between the two copyleft licenses, or are adapting and incorporating BY-SA content without accounting for the incompatibility between the licenses. This obstacle to reuse and remix of BY-SA content in projects published under a license so similar in spirit and substance was at the heart of the problem the compatibility mechanism in BY-SA was designed to solve. <br />
<br />
Together with the Free Software Foundation, CC has pursued a limited form of compatibility to address the problem. Because the GPLv3 is designed for software and CC discourages use of its licenses for software, there are [[ShareAlike_compatibility:_GPLv3#Considerations_for_adapters_applying_the_GPLv3|special considerations]] for those seeking to take advantage of this compatibility mechanism. Please read those considerations carefully before deciding to take advantage of the one-way compatibility mechanism.<br />
<br />
===Example compatibility scenarios===<br />
<br />
:'''BY-SA 4.0 story is adapted into a screenplay and FAL 1.3 is applied to the original contributions'''<br />
:*both licenses apply, but reusers of the screenplay can attribute both authors and comply with their ShareAlike obligations according to FAL terms<br />
<br />
:'''FAL 1.3 image is adapted and BY-SA 4.0 is applied to the original contributions''' <br />
:*only BY-SA 4.0 applies to the adaptation; reusers of the BY-SA adaptation may look only at the terms of BY-SA 4.0 to determine their attribution and ShareAlike obligations<br />
<br />
:'''BY-SA 3.0 song is synched with your original video and BY-SA 4.0 is applied to the original contributions'''<br />
:*both licenses apply, and reusers of the video must comply with the terms of both versions to the extent they differ [note: this is unlikely to have much practical significance; see [https://wiki.creativecommons.org/License_Versions here] for details on how the license versions differ]<br />
<br />
:'''BY-SA 4.0 content is adapted and incorporated into a GPLv3-licensed game and GPLv3 is applied to the original contributions'''<br />
:*both licenses apply, but reusers of the GPL game can attribute and ShareAlike according to the GPLv3 terms</div>CCID-diane petershttps://wiki.creativecommons.org/index.php?title=ShareAlike_compatibility:_GPLv3&diff=114399ShareAlike compatibility: GPLv32015-09-21T11:34:01Z<p>CCID-diane peters: /* Considerations for adapters applying the GPLv3 */</p>
<hr />
<div>This page documents the primary decisions made by Creative Commons when considering the [https://www.gnu.org/copyleft/gpl.html GNU General Public License version 3] (the "GPL") for one-way ShareAlike compatibility pursuant to the [https://wiki.creativecommons.org/ShareAlike_compatibility_process_and_criteria compatibility process and criteria]. <br />
<br />
==Timeline==<br />
*The GPL was [http://lists.ibiblio.org/pipermail/cc-licenses/2015-January/007635.html proposed] by CC and the Free Software Foundation as a candidate for one-way compatibility on 29 January 2015. <br />
*CC published a [[ShareAlike_compatibility_analysis:_GPL|preliminary analysis]] of compatibility with GPL on its wiki. <br />
*Public discussion period ran from 29 January to [http://lists.ibiblio.org/pipermail/cc-licenses/2015-April/007691.html 2 April 2015].<br />
*Compatibility determination published on __ September 2015 and GPLv3 added to [https://creativecommons.org/compatiblelicenses the CC compatible license page]<br />
<br />
==License texts analyzed==<br />
*[https://www.gnu.org/copyleft/gpl.html GPLv3] <br />
*[http://creativecommons.org/licenses/by-sa/4.0/legalcode BY-SA 4.0] <br />
<br />
==How one-compatibility operates==<br />
<br />
When someone creates an adaptation of a BY-SA licensed work and includes it in a GPLv3-licensed project, both licenses apply and downstream users must comply with both licenses. However, [https://creativecommons.org/licenses/by-sa/4.0/legalcode#s2a5B Section 2(a)(5)(B)] of BY-SA 4.0 allows anyone who receives the adapted material downstream to satisfy the conditions of both BY-SA and GPLv3 (i.e. attribution and ShareAlike) in the manner dictated by the GPLv3.<br />
<br />
People may *not* adapt a GPLv3-licensed work and use BY-SA to license their contributions. This is not allowed by GPLv3. Thus, this compatibility determination only allows movement one way, from BY-SA 4.0 to GPLv3. <br />
<br />
For more information, see the compatibility-specific FAQs and explanatory information [https://wiki.creativecommons.org/ShareAlike_compatibility here]. We also encourage you to read this list of [[ShareAlike_compatibility:_GPLv3#Considerations_for_adapters_applying_the_GPLv3|considerations before applying the GPLv3]] as the adapter’s license.<br />
<br />
==Gatekeeping determination==<br />
<br />
In 2008, Creative Commons published the [https://wiki.creativecommons.org/CC_Attribution-ShareAlike_Intent CC Attribution-ShareAlike Statement of Intent], in which CC articulated its intentions as steward for the SA licenses. In point 4 of the statement, CC commits that "any candidate for compatibility must also satisfy the definition of a Free Cultural License set out in the Definition of Free Cultural Works." This criteria serves as the initial gatekeeping factor for all candidate licenses.<br />
<br />
The General Public License v.3 is [http://freedomdefined.org/Licenses#GNU_General_Public_License listed as a Free Cultural License], and conforms to the [http://opendefinition.org/licenses/ Open Definition].<br />
<br />
==Policy decisions==<br />
<br />
===Attribution===<br />
<br />
The specific attribution and marking requirements in the two licenses vary slightly.<br />
<br />
BY-SA 4.0 requires:<br />
#creator and attribution parties (if supplied)<br />
# copyright notice (if supplied)<br />
#license notice (if supplied)<br />
#disclaimer notice (if supplied)<br />
#URI or link to the licensed material (if supplied)<br />
#indicate and link to license<br />
<br />
If you change the work, BY-SA also requires you to indicate that you did so and retain any notice on the work about previous changes made to it. BY-SA requires reusers to remove attribution if practicable when requested by the licensor. <br />
<br />
GPLv3 requires:<br />
#copyright notice<br />
#license notices and notice of [http://www.gnu.org/licenses/gpl-3.0.html#section7 Section 7 additional conditions] (if supplied)<br />
#notices about lack of warranty (if supplied)<br />
#copy of the license<br />
<br />
If you change the work, GPL requires you include a prominent notice to indicate that you did so, along with the relevant date. It also requires special notices for certain interactive user interfaces. GPLv3 does not have an attribution removal clause. <br />
<br />
When BY-SA 4.0 content is adapted and used in a GPLv3-licensed project, the adapter has to comply with the BY-SA attribution and marking requirements. However, Section 2(a)(5)(B) of BY-SA 4.0 enables downstream reusers of the GPL-licensed project to look to the GPL to satisfy their obligations under both licenses. CC determined that GPL-style attribution would satisfy the expectations of BY-SA licensors.<br />
<br />
===License scope===<br />
The tone and scope of the two licenses differ, due largely to the fact that the GPLv3 was designed for use with software and software-like works. Both licenses are primarily designed to license copyright, but each license also covers some rights closely related to copyright. GPL covers “copyright-like laws that apply to other kinds of works, such as semiconductor masks,” while BY-SA covers “Copyright and Similar Rights,” which is defined to include neighboring rights, sui generis database rights, and other closely-related rights.<br />
<br />
The most significant difference in license scope is the treatment of patent rights. BY-SA expressly reserves patent rights to the licensor, while GPLv3 expressly includes a patent grant from each contributor.<br />
<br />
Because patent rights are expressly excluded from BY-SA, there is no reliable claim of an implied license to do things with a BY-SA licensed work that implicate patent rights. From a compatibility perspective, this means that when a BY-SA work is adapted and included in a GPL-licensed project, downstream users of the project would not have patent rights (if any) to the adapted BY-SA work.<br />
(Although the GPL includes a patent license, the scope of rights licensed by the BY-SA licensor cannot be unilaterally expanded by an adapter who choses to apply the GPL, just as it is not expanded when an adapter applies a later version of BY-SA that licenses more rights than the original.)<br />
<br />
This creates the possibility that a downstream user of a GPL project will mistakenly assume that all patent rights are treated as they are in GPLv3 when in fact they are not. We have determined, however, that this should not prevent a determination of one-way compatibility because it is largely an academic problem. Rarely (if ever) would a BY-SA work be subject to patent rights that would be implicated by reproducing or adapting the content.<br />
<br />
===Source=== <br />
<br />
The GPL requires that works be distributed with source or that source be made available (with “source” being the preferred form for making modifications to the work). BY-SA does not impose a similar requirement. Instead, BY-SA licensors are free to distribute their works in any format, whether or not modifiable.<br />
<br />
With one-way compatibility to the GPL, no new obligations are imposed under the BY-SA license, either upon the original licensor or any downstream adapter who wishes to license their contributions under the GPL instead of BY-SA. However, those who adapt BY-SA works and choose to license their contributions under the GPL do, however, have to comply with the GPL obligation to distribute or make available the work in the preferred form for making modifications. If an adapter cannot provide or make available source either because she never received the work in modifiable format from the BY-SA licensor or cannot convert the content to modifiable format, then that person cannot take advantage of the one-way compatibility declaration and use the GPLv3 for her contributions.<br />
<br />
===Effective technological measures===<br />
<br />
BY-SA prohibits application of ETMs by licensees if those measures would prevent others from exercising their rights under the license. In contrast, the GPL does not explicitly prohibit application of DRM and other ETMs. Instead, it addresses any potential lockdown of licensed works by requiring distribution of source code in a modifiable form. <br />
<br />
This difference is not problematic, because in order to comply with GPLv3 the adapter must provide source. As stated in the previous section, if an adapter cannot provide or make source available, she cannot take advantage of the one-way compatibility declaration and may not use GPLv3 for her contributions.<br />
<br />
===License termination===<br />
<br />
Both licenses terminate automatically upon breach. BY-SA is reinstated automatically if the breach is cured within 30 days of discovery. GPLv3 is reinstated for first-time violators who cure within 30 days of getting notice of the violation from the copyright holder, and may be reinstated after other violations if it has been corrected for 60 days without the licensor's objection. These differences make it so one could technically have rights under the GPLv3<br />
reinstated but not under BY-SA in situations where both licenses apply (i.e. when BY-SA content is adapted and integrated into a GPL-licensed project).<ref>[1] Theoretically, one could have their rights reinstated under BY-SA but not GPL, but this does not create the same risk of potential infringement. Because this is one-way compatibility from BY-SA to GPL only, the adapter’s license (i.e. the last-applied license) will always be the GPL. If someone looks only at the GPL when using a GPL project that incorporates a BY-SA work, at worst they will they will not realize they still have rights to the BY-SA work.</ref> As a practical matter, licensors and licensees in both communities typically deal with license violations outside the strict letter of the license, so we feel this is unlikely to be a real world obstacle to compatibility.<br />
<br />
===Option to comply with later versions===<br />
<br />
GPLv3 gives licensees the option to comply with a later version of the GPL if the licensor has so specified, or to use *any* version of the GPL if no version number was specified, regardless of whether the work has been adapted. BY-SA 4.0 allows licensees to comply with the conditions of future versions of BY-SA, but only if that version was applied to an adaptation of the work. Because this compatibility determination is limited to version 3 of the GPL, reusers that adapt BY-SA 4.0 content and incorporate it into GPL-licensed projects are only able to use GPLv3 unless and until other GPL versions are declared compatible. With solid education for both communities and encouragement of clear marking by licensors, we do not feel this is an obstacle to compatibility.<br />
<br />
GPL licensors who are concerned with enabling use under later versions do have the option of using the proxy provision in the GPLv3 to address this limitation. Section 14 of GPLv3 allows licensors to specify a proxy to determine whether future versions of the GPL can be used. Therefore, if someone adapts a BY-SA 4.0 work and incorporates it into a GPLv3-licensed project, they can specify Creative Commons as their proxy (via http://creativecommons.org/compatiblelicenses) so that if and when Creative Commons determines that a future version of the GPL is a compatible license, the adapted and combined work could be used under that later version of GPL.<br />
<br />
==Related policy notes==<br />
Creative Commons consulted extensively with the Free Software Foundation during the 4.0 versioning process, as well as throughout the compatibility process on the policy matters described above. The final determination and policy statements above reflect the best interpretations by both stewards of their respective licenses.<br />
<br />
==Considerations for adapters applying the GPLv3==<br />
Because of the limited one-way nature of this compatibility determination and because GPLv3 is designed for software, there are a few particular considerations to take into account before applying the GPLv3 as the adapter’s license when adapting BY-SA 4.0 works.<br />
<br />
:*'''This one-way compatibility mechanism with GPLv3 is not for general use.''' It was designed to help solve a specific problem for those working in niche areas where content is adapted and melded with code. Please take advantage of it only when you are adapting BY-SA 4.0 works and incorporating the adaptation into GPLv3 software in ways that make it difficult or impossible for downstream users to distinguish the content from code. <br />
<br />
:* '''BY-SA does not include a patent license.''' We recommend against applying GPLv3 if you have any reason to suspect that any patent rights held by the original BY-SA 4.0 licensor could pose a problem for downstream users. <br />
<br />
:* '''BY-SA 4.0 works may not be available in the preferred form for making modifications.''' Do not apply the GPLv3 if you cannot comply with the source requirement in the GPL. <br />
<br />
:* '''This compatibility determination only applies to BY-SA 4.0 and GPLv3.''' You must specify version 3 of the GPL when redistributing a GPL project into which BY-SA 4.0 content is adapted. Please see [[ShareAlike_compatibility:_GPLv3#Option_to_comply_with_later_versions|above]] for information on how to deal with this if you are particularly concerned with enabling compatibility with future versions of the GPL.<br />
<br />
== Notes ==<br />
<references /></div>CCID-diane petershttps://wiki.creativecommons.org/index.php?title=ShareAlike_compatibility:_GPLv3&diff=114398ShareAlike compatibility: GPLv32015-09-21T11:30:45Z<p>CCID-diane peters: /* Related policy notes */</p>
<hr />
<div>This page documents the primary decisions made by Creative Commons when considering the [https://www.gnu.org/copyleft/gpl.html GNU General Public License version 3] (the "GPL") for one-way ShareAlike compatibility pursuant to the [https://wiki.creativecommons.org/ShareAlike_compatibility_process_and_criteria compatibility process and criteria]. <br />
<br />
==Timeline==<br />
*The GPL was [http://lists.ibiblio.org/pipermail/cc-licenses/2015-January/007635.html proposed] by CC and the Free Software Foundation as a candidate for one-way compatibility on 29 January 2015. <br />
*CC published a [[ShareAlike_compatibility_analysis:_GPL|preliminary analysis]] of compatibility with GPL on its wiki. <br />
*Public discussion period ran from 29 January to [http://lists.ibiblio.org/pipermail/cc-licenses/2015-April/007691.html 2 April 2015].<br />
*Compatibility determination published on __ September 2015 and GPLv3 added to [https://creativecommons.org/compatiblelicenses the CC compatible license page]<br />
<br />
==License texts analyzed==<br />
*[https://www.gnu.org/copyleft/gpl.html GPLv3] <br />
*[http://creativecommons.org/licenses/by-sa/4.0/legalcode BY-SA 4.0] <br />
<br />
==How one-compatibility operates==<br />
<br />
When someone creates an adaptation of a BY-SA licensed work and includes it in a GPLv3-licensed project, both licenses apply and downstream users must comply with both licenses. However, [https://creativecommons.org/licenses/by-sa/4.0/legalcode#s2a5B Section 2(a)(5)(B)] of BY-SA 4.0 allows anyone who receives the adapted material downstream to satisfy the conditions of both BY-SA and GPLv3 (i.e. attribution and ShareAlike) in the manner dictated by the GPLv3.<br />
<br />
People may *not* adapt a GPLv3-licensed work and use BY-SA to license their contributions. This is not allowed by GPLv3. Thus, this compatibility determination only allows movement one way, from BY-SA 4.0 to GPLv3. <br />
<br />
For more information, see the compatibility-specific FAQs and explanatory information [https://wiki.creativecommons.org/ShareAlike_compatibility here]. We also encourage you to read this list of [[ShareAlike_compatibility:_GPLv3#Considerations_for_adapters_applying_the_GPLv3|considerations before applying the GPLv3]] as the adapter’s license.<br />
<br />
==Gatekeeping determination==<br />
<br />
In 2008, Creative Commons published the [https://wiki.creativecommons.org/CC_Attribution-ShareAlike_Intent CC Attribution-ShareAlike Statement of Intent], in which CC articulated its intentions as steward for the SA licenses. In point 4 of the statement, CC commits that "any candidate for compatibility must also satisfy the definition of a Free Cultural License set out in the Definition of Free Cultural Works." This criteria serves as the initial gatekeeping factor for all candidate licenses.<br />
<br />
The General Public License v.3 is [http://freedomdefined.org/Licenses#GNU_General_Public_License listed as a Free Cultural License], and conforms to the [http://opendefinition.org/licenses/ Open Definition].<br />
<br />
==Policy decisions==<br />
<br />
===Attribution===<br />
<br />
The specific attribution and marking requirements in the two licenses vary slightly.<br />
<br />
BY-SA 4.0 requires:<br />
#creator and attribution parties (if supplied)<br />
# copyright notice (if supplied)<br />
#license notice (if supplied)<br />
#disclaimer notice (if supplied)<br />
#URI or link to the licensed material (if supplied)<br />
#indicate and link to license<br />
<br />
If you change the work, BY-SA also requires you to indicate that you did so and retain any notice on the work about previous changes made to it. BY-SA requires reusers to remove attribution if practicable when requested by the licensor. <br />
<br />
GPLv3 requires:<br />
#copyright notice<br />
#license notices and notice of [http://www.gnu.org/licenses/gpl-3.0.html#section7 Section 7 additional conditions] (if supplied)<br />
#notices about lack of warranty (if supplied)<br />
#copy of the license<br />
<br />
If you change the work, GPL requires you include a prominent notice to indicate that you did so, along with the relevant date. It also requires special notices for certain interactive user interfaces. GPLv3 does not have an attribution removal clause. <br />
<br />
When BY-SA 4.0 content is adapted and used in a GPLv3-licensed project, the adapter has to comply with the BY-SA attribution and marking requirements. However, Section 2(a)(5)(B) of BY-SA 4.0 enables downstream reusers of the GPL-licensed project to look to the GPL to satisfy their obligations under both licenses. CC determined that GPL-style attribution would satisfy the expectations of BY-SA licensors.<br />
<br />
===License scope===<br />
The tone and scope of the two licenses differ, due largely to the fact that the GPLv3 was designed for use with software and software-like works. Both licenses are primarily designed to license copyright, but each license also covers some rights closely related to copyright. GPL covers “copyright-like laws that apply to other kinds of works, such as semiconductor masks,” while BY-SA covers “Copyright and Similar Rights,” which is defined to include neighboring rights, sui generis database rights, and other closely-related rights.<br />
<br />
The most significant difference in license scope is the treatment of patent rights. BY-SA expressly reserves patent rights to the licensor, while GPLv3 expressly includes a patent grant from each contributor.<br />
<br />
Because patent rights are expressly excluded from BY-SA, there is no reliable claim of an implied license to do things with a BY-SA licensed work that implicate patent rights. From a compatibility perspective, this means that when a BY-SA work is adapted and included in a GPL-licensed project, downstream users of the project would not have patent rights (if any) to the adapted BY-SA work.<br />
(Although the GPL includes a patent license, the scope of rights licensed by the BY-SA licensor cannot be unilaterally expanded by an adapter who choses to apply the GPL, just as it is not expanded when an adapter applies a later version of BY-SA that licenses more rights than the original.)<br />
<br />
This creates the possibility that a downstream user of a GPL project will mistakenly assume that all patent rights are treated as they are in GPLv3 when in fact they are not. We have determined, however, that this should not prevent a determination of one-way compatibility because it is largely an academic problem. Rarely (if ever) would a BY-SA work be subject to patent rights that would be implicated by reproducing or adapting the content.<br />
<br />
===Source=== <br />
<br />
The GPL requires that works be distributed with source or that source be made available (with “source” being the preferred form for making modifications to the work). BY-SA does not impose a similar requirement. Instead, BY-SA licensors are free to distribute their works in any format, whether or not modifiable.<br />
<br />
With one-way compatibility to the GPL, no new obligations are imposed under the BY-SA license, either upon the original licensor or any downstream adapter who wishes to license their contributions under the GPL instead of BY-SA. However, those who adapt BY-SA works and choose to license their contributions under the GPL do, however, have to comply with the GPL obligation to distribute or make available the work in the preferred form for making modifications. If an adapter cannot provide or make available source either because she never received the work in modifiable format from the BY-SA licensor or cannot convert the content to modifiable format, then that person cannot take advantage of the one-way compatibility declaration and use the GPLv3 for her contributions.<br />
<br />
===Effective technological measures===<br />
<br />
BY-SA prohibits application of ETMs by licensees if those measures would prevent others from exercising their rights under the license. In contrast, the GPL does not explicitly prohibit application of DRM and other ETMs. Instead, it addresses any potential lockdown of licensed works by requiring distribution of source code in a modifiable form. <br />
<br />
This difference is not problematic, because in order to comply with GPLv3 the adapter must provide source. As stated in the previous section, if an adapter cannot provide or make source available, she cannot take advantage of the one-way compatibility declaration and may not use GPLv3 for her contributions.<br />
<br />
===License termination===<br />
<br />
Both licenses terminate automatically upon breach. BY-SA is reinstated automatically if the breach is cured within 30 days of discovery. GPLv3 is reinstated for first-time violators who cure within 30 days of getting notice of the violation from the copyright holder, and may be reinstated after other violations if it has been corrected for 60 days without the licensor's objection. These differences make it so one could technically have rights under the GPLv3<br />
reinstated but not under BY-SA in situations where both licenses apply (i.e. when BY-SA content is adapted and integrated into a GPL-licensed project).<ref>[1] Theoretically, one could have their rights reinstated under BY-SA but not GPL, but this does not create the same risk of potential infringement. Because this is one-way compatibility from BY-SA to GPL only, the adapter’s license (i.e. the last-applied license) will always be the GPL. If someone looks only at the GPL when using a GPL project that incorporates a BY-SA work, at worst they will they will not realize they still have rights to the BY-SA work.</ref> As a practical matter, licensors and licensees in both communities typically deal with license violations outside the strict letter of the license, so we feel this is unlikely to be a real world obstacle to compatibility.<br />
<br />
===Option to comply with later versions===<br />
<br />
GPLv3 gives licensees the option to comply with a later version of the GPL if the licensor has so specified, or to use *any* version of the GPL if no version number was specified, regardless of whether the work has been adapted. BY-SA 4.0 allows licensees to comply with the conditions of future versions of BY-SA, but only if that version was applied to an adaptation of the work. Because this compatibility determination is limited to version 3 of the GPL, reusers that adapt BY-SA 4.0 content and incorporate it into GPL-licensed projects are only able to use GPLv3 unless and until other GPL versions are declared compatible. With solid education for both communities and encouragement of clear marking by licensors, we do not feel this is an obstacle to compatibility.<br />
<br />
GPL licensors who are concerned with enabling use under later versions do have the option of using the proxy provision in the GPLv3 to address this limitation. Section 14 of GPLv3 allows licensors to specify a proxy to determine whether future versions of the GPL can be used. Therefore, if someone adapts a BY-SA 4.0 work and incorporates it into a GPLv3-licensed project, they can specify Creative Commons as their proxy (via http://creativecommons.org/compatiblelicenses) so that if and when Creative Commons determines that a future version of the GPL is a compatible license, the adapted and combined work could be used under that later version of GPL.<br />
<br />
==Related policy notes==<br />
Creative Commons consulted extensively with the Free Software Foundation during the 4.0 versioning process, as well as throughout the compatibility process on the policy matters described above. The final determination and policy statements above reflect the best interpretations by both stewards of their respective licenses.<br />
<br />
==Considerations for adapters applying the GPLv3==<br />
Both because of the limited one-way nature of compatibility and because GPLv3 is designed for software, there are a few particular considerations to take into account before applying the GPLv3 as the adapter’s license when adapting BY-SA works.<br />
<br />
:*'''This one-way compatibility mechanism with GPLv3 is not for general use.''' It was designed to help solve a specific problem for those working in niche areas where content is melded with code. Please take advantage of it only when you are adapting BY-SA works into GPLv3 software in ways that make it difficult or impossible for downstream users to distinguish the content from code. <br />
<br />
:* '''BY-SA does not include a patent license.''' Do not apply the GPLv3 if you have any reason to suspect that any patent rights held by the original BY-SA licensor could pose a problem for downstream users. <br />
<br />
:* '''BY-SA works may not be available in the preferred form for making modifications.''' Do not apply the GPLv3 if you cannot comply with the source requirement in the GPL. <br />
<br />
:* '''This compatibility determination only applies to GPL version 3.''' You must specify version 3 of the GPL when redistributing a GPL project into which BY-SA content is adapted. Please see [[ShareAlike_compatibility:_GPLv3#Option_to_comply_with_later_versions|above]] for information on how to deal with this if you are particularly concerned with enabling compatibility with future versions of the GPL. <br />
<br />
== Notes ==<br />
<references /></div>CCID-diane petershttps://wiki.creativecommons.org/index.php?title=ShareAlike_compatibility:_GPLv3&diff=114397ShareAlike compatibility: GPLv32015-09-21T11:30:04Z<p>CCID-diane peters: /* Option to comply with later versions */</p>
<hr />
<div>This page documents the primary decisions made by Creative Commons when considering the [https://www.gnu.org/copyleft/gpl.html GNU General Public License version 3] (the "GPL") for one-way ShareAlike compatibility pursuant to the [https://wiki.creativecommons.org/ShareAlike_compatibility_process_and_criteria compatibility process and criteria]. <br />
<br />
==Timeline==<br />
*The GPL was [http://lists.ibiblio.org/pipermail/cc-licenses/2015-January/007635.html proposed] by CC and the Free Software Foundation as a candidate for one-way compatibility on 29 January 2015. <br />
*CC published a [[ShareAlike_compatibility_analysis:_GPL|preliminary analysis]] of compatibility with GPL on its wiki. <br />
*Public discussion period ran from 29 January to [http://lists.ibiblio.org/pipermail/cc-licenses/2015-April/007691.html 2 April 2015].<br />
*Compatibility determination published on __ September 2015 and GPLv3 added to [https://creativecommons.org/compatiblelicenses the CC compatible license page]<br />
<br />
==License texts analyzed==<br />
*[https://www.gnu.org/copyleft/gpl.html GPLv3] <br />
*[http://creativecommons.org/licenses/by-sa/4.0/legalcode BY-SA 4.0] <br />
<br />
==How one-compatibility operates==<br />
<br />
When someone creates an adaptation of a BY-SA licensed work and includes it in a GPLv3-licensed project, both licenses apply and downstream users must comply with both licenses. However, [https://creativecommons.org/licenses/by-sa/4.0/legalcode#s2a5B Section 2(a)(5)(B)] of BY-SA 4.0 allows anyone who receives the adapted material downstream to satisfy the conditions of both BY-SA and GPLv3 (i.e. attribution and ShareAlike) in the manner dictated by the GPLv3.<br />
<br />
People may *not* adapt a GPLv3-licensed work and use BY-SA to license their contributions. This is not allowed by GPLv3. Thus, this compatibility determination only allows movement one way, from BY-SA 4.0 to GPLv3. <br />
<br />
For more information, see the compatibility-specific FAQs and explanatory information [https://wiki.creativecommons.org/ShareAlike_compatibility here]. We also encourage you to read this list of [[ShareAlike_compatibility:_GPLv3#Considerations_for_adapters_applying_the_GPLv3|considerations before applying the GPLv3]] as the adapter’s license.<br />
<br />
==Gatekeeping determination==<br />
<br />
In 2008, Creative Commons published the [https://wiki.creativecommons.org/CC_Attribution-ShareAlike_Intent CC Attribution-ShareAlike Statement of Intent], in which CC articulated its intentions as steward for the SA licenses. In point 4 of the statement, CC commits that "any candidate for compatibility must also satisfy the definition of a Free Cultural License set out in the Definition of Free Cultural Works." This criteria serves as the initial gatekeeping factor for all candidate licenses.<br />
<br />
The General Public License v.3 is [http://freedomdefined.org/Licenses#GNU_General_Public_License listed as a Free Cultural License], and conforms to the [http://opendefinition.org/licenses/ Open Definition].<br />
<br />
==Policy decisions==<br />
<br />
===Attribution===<br />
<br />
The specific attribution and marking requirements in the two licenses vary slightly.<br />
<br />
BY-SA 4.0 requires:<br />
#creator and attribution parties (if supplied)<br />
# copyright notice (if supplied)<br />
#license notice (if supplied)<br />
#disclaimer notice (if supplied)<br />
#URI or link to the licensed material (if supplied)<br />
#indicate and link to license<br />
<br />
If you change the work, BY-SA also requires you to indicate that you did so and retain any notice on the work about previous changes made to it. BY-SA requires reusers to remove attribution if practicable when requested by the licensor. <br />
<br />
GPLv3 requires:<br />
#copyright notice<br />
#license notices and notice of [http://www.gnu.org/licenses/gpl-3.0.html#section7 Section 7 additional conditions] (if supplied)<br />
#notices about lack of warranty (if supplied)<br />
#copy of the license<br />
<br />
If you change the work, GPL requires you include a prominent notice to indicate that you did so, along with the relevant date. It also requires special notices for certain interactive user interfaces. GPLv3 does not have an attribution removal clause. <br />
<br />
When BY-SA 4.0 content is adapted and used in a GPLv3-licensed project, the adapter has to comply with the BY-SA attribution and marking requirements. However, Section 2(a)(5)(B) of BY-SA 4.0 enables downstream reusers of the GPL-licensed project to look to the GPL to satisfy their obligations under both licenses. CC determined that GPL-style attribution would satisfy the expectations of BY-SA licensors.<br />
<br />
===License scope===<br />
The tone and scope of the two licenses differ, due largely to the fact that the GPLv3 was designed for use with software and software-like works. Both licenses are primarily designed to license copyright, but each license also covers some rights closely related to copyright. GPL covers “copyright-like laws that apply to other kinds of works, such as semiconductor masks,” while BY-SA covers “Copyright and Similar Rights,” which is defined to include neighboring rights, sui generis database rights, and other closely-related rights.<br />
<br />
The most significant difference in license scope is the treatment of patent rights. BY-SA expressly reserves patent rights to the licensor, while GPLv3 expressly includes a patent grant from each contributor.<br />
<br />
Because patent rights are expressly excluded from BY-SA, there is no reliable claim of an implied license to do things with a BY-SA licensed work that implicate patent rights. From a compatibility perspective, this means that when a BY-SA work is adapted and included in a GPL-licensed project, downstream users of the project would not have patent rights (if any) to the adapted BY-SA work.<br />
(Although the GPL includes a patent license, the scope of rights licensed by the BY-SA licensor cannot be unilaterally expanded by an adapter who choses to apply the GPL, just as it is not expanded when an adapter applies a later version of BY-SA that licenses more rights than the original.)<br />
<br />
This creates the possibility that a downstream user of a GPL project will mistakenly assume that all patent rights are treated as they are in GPLv3 when in fact they are not. We have determined, however, that this should not prevent a determination of one-way compatibility because it is largely an academic problem. Rarely (if ever) would a BY-SA work be subject to patent rights that would be implicated by reproducing or adapting the content.<br />
<br />
===Source=== <br />
<br />
The GPL requires that works be distributed with source or that source be made available (with “source” being the preferred form for making modifications to the work). BY-SA does not impose a similar requirement. Instead, BY-SA licensors are free to distribute their works in any format, whether or not modifiable.<br />
<br />
With one-way compatibility to the GPL, no new obligations are imposed under the BY-SA license, either upon the original licensor or any downstream adapter who wishes to license their contributions under the GPL instead of BY-SA. However, those who adapt BY-SA works and choose to license their contributions under the GPL do, however, have to comply with the GPL obligation to distribute or make available the work in the preferred form for making modifications. If an adapter cannot provide or make available source either because she never received the work in modifiable format from the BY-SA licensor or cannot convert the content to modifiable format, then that person cannot take advantage of the one-way compatibility declaration and use the GPLv3 for her contributions.<br />
<br />
===Effective technological measures===<br />
<br />
BY-SA prohibits application of ETMs by licensees if those measures would prevent others from exercising their rights under the license. In contrast, the GPL does not explicitly prohibit application of DRM and other ETMs. Instead, it addresses any potential lockdown of licensed works by requiring distribution of source code in a modifiable form. <br />
<br />
This difference is not problematic, because in order to comply with GPLv3 the adapter must provide source. As stated in the previous section, if an adapter cannot provide or make source available, she cannot take advantage of the one-way compatibility declaration and may not use GPLv3 for her contributions.<br />
<br />
===License termination===<br />
<br />
Both licenses terminate automatically upon breach. BY-SA is reinstated automatically if the breach is cured within 30 days of discovery. GPLv3 is reinstated for first-time violators who cure within 30 days of getting notice of the violation from the copyright holder, and may be reinstated after other violations if it has been corrected for 60 days without the licensor's objection. These differences make it so one could technically have rights under the GPLv3<br />
reinstated but not under BY-SA in situations where both licenses apply (i.e. when BY-SA content is adapted and integrated into a GPL-licensed project).<ref>[1] Theoretically, one could have their rights reinstated under BY-SA but not GPL, but this does not create the same risk of potential infringement. Because this is one-way compatibility from BY-SA to GPL only, the adapter’s license (i.e. the last-applied license) will always be the GPL. If someone looks only at the GPL when using a GPL project that incorporates a BY-SA work, at worst they will they will not realize they still have rights to the BY-SA work.</ref> As a practical matter, licensors and licensees in both communities typically deal with license violations outside the strict letter of the license, so we feel this is unlikely to be a real world obstacle to compatibility.<br />
<br />
===Option to comply with later versions===<br />
<br />
GPLv3 gives licensees the option to comply with a later version of the GPL if the licensor has so specified, or to use *any* version of the GPL if no version number was specified, regardless of whether the work has been adapted. BY-SA 4.0 allows licensees to comply with the conditions of future versions of BY-SA, but only if that version was applied to an adaptation of the work. Because this compatibility determination is limited to version 3 of the GPL, reusers that adapt BY-SA 4.0 content and incorporate it into GPL-licensed projects are only able to use GPLv3 unless and until other GPL versions are declared compatible. With solid education for both communities and encouragement of clear marking by licensors, we do not feel this is an obstacle to compatibility.<br />
<br />
GPL licensors who are concerned with enabling use under later versions do have the option of using the proxy provision in the GPLv3 to address this limitation. Section 14 of GPLv3 allows licensors to specify a proxy to determine whether future versions of the GPL can be used. Therefore, if someone adapts a BY-SA 4.0 work and incorporates it into a GPLv3-licensed project, they can specify Creative Commons as their proxy (via http://creativecommons.org/compatiblelicenses) so that if and when Creative Commons determines that a future version of the GPL is a compatible license, the adapted and combined work could be used under that later version of GPL.<br />
<br />
==Related policy notes==<br />
Creative Commons consulted extensively with the steward of the GPL v.3 during the 4.0 versioning process, as well as throughout the compatibility process on the policy matters described above. The final determination and policy statements above reflect the best interpretations by both stewards of their respective licenses.<br />
<br />
==Considerations for adapters applying the GPLv3==<br />
Both because of the limited one-way nature of compatibility and because GPLv3 is designed for software, there are a few particular considerations to take into account before applying the GPLv3 as the adapter’s license when adapting BY-SA works.<br />
<br />
:*'''This one-way compatibility mechanism with GPLv3 is not for general use.''' It was designed to help solve a specific problem for those working in niche areas where content is melded with code. Please take advantage of it only when you are adapting BY-SA works into GPLv3 software in ways that make it difficult or impossible for downstream users to distinguish the content from code. <br />
<br />
:* '''BY-SA does not include a patent license.''' Do not apply the GPLv3 if you have any reason to suspect that any patent rights held by the original BY-SA licensor could pose a problem for downstream users. <br />
<br />
:* '''BY-SA works may not be available in the preferred form for making modifications.''' Do not apply the GPLv3 if you cannot comply with the source requirement in the GPL. <br />
<br />
:* '''This compatibility determination only applies to GPL version 3.''' You must specify version 3 of the GPL when redistributing a GPL project into which BY-SA content is adapted. Please see [[ShareAlike_compatibility:_GPLv3#Option_to_comply_with_later_versions|above]] for information on how to deal with this if you are particularly concerned with enabling compatibility with future versions of the GPL. <br />
<br />
== Notes ==<br />
<references /></div>CCID-diane petershttps://wiki.creativecommons.org/index.php?title=ShareAlike_compatibility:_GPLv3&diff=114396ShareAlike compatibility: GPLv32015-09-21T11:08:39Z<p>CCID-diane peters: /* Effective technological measures */</p>
<hr />
<div>This page documents the primary decisions made by Creative Commons when considering the [https://www.gnu.org/copyleft/gpl.html GNU General Public License version 3] (the "GPL") for one-way ShareAlike compatibility pursuant to the [https://wiki.creativecommons.org/ShareAlike_compatibility_process_and_criteria compatibility process and criteria]. <br />
<br />
==Timeline==<br />
*The GPL was [http://lists.ibiblio.org/pipermail/cc-licenses/2015-January/007635.html proposed] by CC and the Free Software Foundation as a candidate for one-way compatibility on 29 January 2015. <br />
*CC published a [[ShareAlike_compatibility_analysis:_GPL|preliminary analysis]] of compatibility with GPL on its wiki. <br />
*Public discussion period ran from 29 January to [http://lists.ibiblio.org/pipermail/cc-licenses/2015-April/007691.html 2 April 2015].<br />
*Compatibility determination published on __ September 2015 and GPLv3 added to [https://creativecommons.org/compatiblelicenses the CC compatible license page]<br />
<br />
==License texts analyzed==<br />
*[https://www.gnu.org/copyleft/gpl.html GPLv3] <br />
*[http://creativecommons.org/licenses/by-sa/4.0/legalcode BY-SA 4.0] <br />
<br />
==How one-compatibility operates==<br />
<br />
When someone creates an adaptation of a BY-SA licensed work and includes it in a GPLv3-licensed project, both licenses apply and downstream users must comply with both licenses. However, [https://creativecommons.org/licenses/by-sa/4.0/legalcode#s2a5B Section 2(a)(5)(B)] of BY-SA 4.0 allows anyone who receives the adapted material downstream to satisfy the conditions of both BY-SA and GPLv3 (i.e. attribution and ShareAlike) in the manner dictated by the GPLv3.<br />
<br />
People may *not* adapt a GPLv3-licensed work and use BY-SA to license their contributions. This is not allowed by GPLv3. Thus, this compatibility determination only allows movement one way, from BY-SA 4.0 to GPLv3. <br />
<br />
For more information, see the compatibility-specific FAQs and explanatory information [https://wiki.creativecommons.org/ShareAlike_compatibility here]. We also encourage you to read this list of [[ShareAlike_compatibility:_GPLv3#Considerations_for_adapters_applying_the_GPLv3|considerations before applying the GPLv3]] as the adapter’s license.<br />
<br />
==Gatekeeping determination==<br />
<br />
In 2008, Creative Commons published the [https://wiki.creativecommons.org/CC_Attribution-ShareAlike_Intent CC Attribution-ShareAlike Statement of Intent], in which CC articulated its intentions as steward for the SA licenses. In point 4 of the statement, CC commits that "any candidate for compatibility must also satisfy the definition of a Free Cultural License set out in the Definition of Free Cultural Works." This criteria serves as the initial gatekeeping factor for all candidate licenses.<br />
<br />
The General Public License v.3 is [http://freedomdefined.org/Licenses#GNU_General_Public_License listed as a Free Cultural License], and conforms to the [http://opendefinition.org/licenses/ Open Definition].<br />
<br />
==Policy decisions==<br />
<br />
===Attribution===<br />
<br />
The specific attribution and marking requirements in the two licenses vary slightly.<br />
<br />
BY-SA 4.0 requires:<br />
#creator and attribution parties (if supplied)<br />
# copyright notice (if supplied)<br />
#license notice (if supplied)<br />
#disclaimer notice (if supplied)<br />
#URI or link to the licensed material (if supplied)<br />
#indicate and link to license<br />
<br />
If you change the work, BY-SA also requires you to indicate that you did so and retain any notice on the work about previous changes made to it. BY-SA requires reusers to remove attribution if practicable when requested by the licensor. <br />
<br />
GPLv3 requires:<br />
#copyright notice<br />
#license notices and notice of [http://www.gnu.org/licenses/gpl-3.0.html#section7 Section 7 additional conditions] (if supplied)<br />
#notices about lack of warranty (if supplied)<br />
#copy of the license<br />
<br />
If you change the work, GPL requires you include a prominent notice to indicate that you did so, along with the relevant date. It also requires special notices for certain interactive user interfaces. GPLv3 does not have an attribution removal clause. <br />
<br />
When BY-SA 4.0 content is adapted and used in a GPLv3-licensed project, the adapter has to comply with the BY-SA attribution and marking requirements. However, Section 2(a)(5)(B) of BY-SA 4.0 enables downstream reusers of the GPL-licensed project to look to the GPL to satisfy their obligations under both licenses. CC determined that GPL-style attribution would satisfy the expectations of BY-SA licensors.<br />
<br />
===License scope===<br />
The tone and scope of the two licenses differ, due largely to the fact that the GPLv3 was designed for use with software and software-like works. Both licenses are primarily designed to license copyright, but each license also covers some rights closely related to copyright. GPL covers “copyright-like laws that apply to other kinds of works, such as semiconductor masks,” while BY-SA covers “Copyright and Similar Rights,” which is defined to include neighboring rights, sui generis database rights, and other closely-related rights.<br />
<br />
The most significant difference in license scope is the treatment of patent rights. BY-SA expressly reserves patent rights to the licensor, while GPLv3 expressly includes a patent grant from each contributor.<br />
<br />
Because patent rights are expressly excluded from BY-SA, there is no reliable claim of an implied license to do things with a BY-SA licensed work that implicate patent rights. From a compatibility perspective, this means that when a BY-SA work is adapted and included in a GPL-licensed project, downstream users of the project would not have patent rights (if any) to the adapted BY-SA work.<br />
(Although the GPL includes a patent license, the scope of rights licensed by the BY-SA licensor cannot be unilaterally expanded by an adapter who choses to apply the GPL, just as it is not expanded when an adapter applies a later version of BY-SA that licenses more rights than the original.)<br />
<br />
This creates the possibility that a downstream user of a GPL project will mistakenly assume that all patent rights are treated as they are in GPLv3 when in fact they are not. We have determined, however, that this should not prevent a determination of one-way compatibility because it is largely an academic problem. Rarely (if ever) would a BY-SA work be subject to patent rights that would be implicated by reproducing or adapting the content.<br />
<br />
===Source=== <br />
<br />
The GPL requires that works be distributed with source or that source be made available (with “source” being the preferred form for making modifications to the work). BY-SA does not impose a similar requirement. Instead, BY-SA licensors are free to distribute their works in any format, whether or not modifiable.<br />
<br />
With one-way compatibility to the GPL, no new obligations are imposed under the BY-SA license, either upon the original licensor or any downstream adapter who wishes to license their contributions under the GPL instead of BY-SA. However, those who adapt BY-SA works and choose to license their contributions under the GPL do, however, have to comply with the GPL obligation to distribute or make available the work in the preferred form for making modifications. If an adapter cannot provide or make available source either because she never received the work in modifiable format from the BY-SA licensor or cannot convert the content to modifiable format, then that person cannot take advantage of the one-way compatibility declaration and use the GPLv3 for her contributions.<br />
<br />
===Effective technological measures===<br />
<br />
BY-SA prohibits application of ETMs by licensees if those measures would prevent others from exercising their rights under the license. In contrast, the GPL does not explicitly prohibit application of DRM and other ETMs. Instead, it addresses any potential lockdown of licensed works by requiring distribution of source code in a modifiable form. <br />
<br />
This difference is not problematic, because in order to comply with GPLv3 the adapter must provide source. As stated in the previous section, if an adapter cannot provide or make source available, she cannot take advantage of the one-way compatibility declaration and may not use GPLv3 for her contributions.<br />
<br />
===License termination===<br />
<br />
Both licenses terminate automatically upon breach. BY-SA is reinstated automatically if the breach is cured within 30 days of discovery. GPLv3 is reinstated for first-time violators who cure within 30 days of getting notice of the violation from the copyright holder, and may be reinstated after other violations if it has been corrected for 60 days without the licensor's objection. These differences make it so one could technically have rights under the GPLv3<br />
reinstated but not under BY-SA in situations where both licenses apply (i.e. when BY-SA content is adapted and integrated into a GPL-licensed project).<ref>[1] Theoretically, one could have their rights reinstated under BY-SA but not GPL, but this does not create the same risk of potential infringement. Because this is one-way compatibility from BY-SA to GPL only, the adapter’s license (i.e. the last-applied license) will always be the GPL. If someone looks only at the GPL when using a GPL project that incorporates a BY-SA work, at worst they will they will not realize they still have rights to the BY-SA work.</ref> As a practical matter, licensors and licensees in both communities typically deal with license violations outside the strict letter of the license, so we feel this is unlikely to be a real world obstacle to compatibility.<br />
<br />
===Option to comply with later versions===<br />
<br />
GPLv3 gives licensees the option to comply with a later version of the GPL if the licensor has so specified, or to use *any* version of the GPL if no version number was specified, regardless of whether the work has been adapted. BY-SA allows licensees to comply with the conditions of future versions of BY-SA, but only if that version was applied to an adaptation of the work. Because only version 3 of the GPL is an option for compatibility at this time, reusers that adapt BY-SA content into GPL-licensed projects are only able to use GPLv3 unless and until other GPL versions are made compatible. With solid education for both communities and encouragement of clear marking by licensors, we do not feel this is an obstacle to compatibility.<br />
<br />
Also, those GPL licensors who are concerned with enabling use under later versions do have the option of using the proxy provision in the GPLv3 for this. Section 14 of the GPLv3 allows licensors to specify a proxy to determine whether future versions of the GPL can be used. Therefore, if someone adapts a BY-SA 4.0 work into a GPLv3 project, they can specify Creative Commons as their proxy (via http://creativecommons.org/compatiblelicenses) so that if and when Creative Commons determines that a future version of the GPL is a compatible license, the adapted work could be used under that later version. <br />
<br />
==Related policy notes==<br />
Creative Commons consulted extensively with the steward of the GPL v.3 during the 4.0 versioning process, as well as throughout the compatibility process on the policy matters described above. The final determination and policy statements above reflect the best interpretations by both stewards of their respective licenses.<br />
<br />
==Considerations for adapters applying the GPLv3==<br />
Both because of the limited one-way nature of compatibility and because GPLv3 is designed for software, there are a few particular considerations to take into account before applying the GPLv3 as the adapter’s license when adapting BY-SA works.<br />
<br />
:*'''This one-way compatibility mechanism with GPLv3 is not for general use.''' It was designed to help solve a specific problem for those working in niche areas where content is melded with code. Please take advantage of it only when you are adapting BY-SA works into GPLv3 software in ways that make it difficult or impossible for downstream users to distinguish the content from code. <br />
<br />
:* '''BY-SA does not include a patent license.''' Do not apply the GPLv3 if you have any reason to suspect that any patent rights held by the original BY-SA licensor could pose a problem for downstream users. <br />
<br />
:* '''BY-SA works may not be available in the preferred form for making modifications.''' Do not apply the GPLv3 if you cannot comply with the source requirement in the GPL. <br />
<br />
:* '''This compatibility determination only applies to GPL version 3.''' You must specify version 3 of the GPL when redistributing a GPL project into which BY-SA content is adapted. Please see [[ShareAlike_compatibility:_GPLv3#Option_to_comply_with_later_versions|above]] for information on how to deal with this if you are particularly concerned with enabling compatibility with future versions of the GPL. <br />
<br />
== Notes ==<br />
<references /></div>CCID-diane petershttps://wiki.creativecommons.org/index.php?title=ShareAlike_compatibility:_GPLv3&diff=114395ShareAlike compatibility: GPLv32015-09-21T11:07:57Z<p>CCID-diane peters: </p>
<hr />
<div>This page documents the primary decisions made by Creative Commons when considering the [https://www.gnu.org/copyleft/gpl.html GNU General Public License version 3] (the "GPL") for one-way ShareAlike compatibility pursuant to the [https://wiki.creativecommons.org/ShareAlike_compatibility_process_and_criteria compatibility process and criteria]. <br />
<br />
==Timeline==<br />
*The GPL was [http://lists.ibiblio.org/pipermail/cc-licenses/2015-January/007635.html proposed] by CC and the Free Software Foundation as a candidate for one-way compatibility on 29 January 2015. <br />
*CC published a [[ShareAlike_compatibility_analysis:_GPL|preliminary analysis]] of compatibility with GPL on its wiki. <br />
*Public discussion period ran from 29 January to [http://lists.ibiblio.org/pipermail/cc-licenses/2015-April/007691.html 2 April 2015].<br />
*Compatibility determination published on __ September 2015 and GPLv3 added to [https://creativecommons.org/compatiblelicenses the CC compatible license page]<br />
<br />
==License texts analyzed==<br />
*[https://www.gnu.org/copyleft/gpl.html GPLv3] <br />
*[http://creativecommons.org/licenses/by-sa/4.0/legalcode BY-SA 4.0] <br />
<br />
==How one-compatibility operates==<br />
<br />
When someone creates an adaptation of a BY-SA licensed work and includes it in a GPLv3-licensed project, both licenses apply and downstream users must comply with both licenses. However, [https://creativecommons.org/licenses/by-sa/4.0/legalcode#s2a5B Section 2(a)(5)(B)] of BY-SA 4.0 allows anyone who receives the adapted material downstream to satisfy the conditions of both BY-SA and GPLv3 (i.e. attribution and ShareAlike) in the manner dictated by the GPLv3.<br />
<br />
People may *not* adapt a GPLv3-licensed work and use BY-SA to license their contributions. This is not allowed by GPLv3. Thus, this compatibility determination only allows movement one way, from BY-SA 4.0 to GPLv3. <br />
<br />
For more information, see the compatibility-specific FAQs and explanatory information [https://wiki.creativecommons.org/ShareAlike_compatibility here]. We also encourage you to read this list of [[ShareAlike_compatibility:_GPLv3#Considerations_for_adapters_applying_the_GPLv3|considerations before applying the GPLv3]] as the adapter’s license.<br />
<br />
==Gatekeeping determination==<br />
<br />
In 2008, Creative Commons published the [https://wiki.creativecommons.org/CC_Attribution-ShareAlike_Intent CC Attribution-ShareAlike Statement of Intent], in which CC articulated its intentions as steward for the SA licenses. In point 4 of the statement, CC commits that "any candidate for compatibility must also satisfy the definition of a Free Cultural License set out in the Definition of Free Cultural Works." This criteria serves as the initial gatekeeping factor for all candidate licenses.<br />
<br />
The General Public License v.3 is [http://freedomdefined.org/Licenses#GNU_General_Public_License listed as a Free Cultural License], and conforms to the [http://opendefinition.org/licenses/ Open Definition].<br />
<br />
==Policy decisions==<br />
<br />
===Attribution===<br />
<br />
The specific attribution and marking requirements in the two licenses vary slightly.<br />
<br />
BY-SA 4.0 requires:<br />
#creator and attribution parties (if supplied)<br />
# copyright notice (if supplied)<br />
#license notice (if supplied)<br />
#disclaimer notice (if supplied)<br />
#URI or link to the licensed material (if supplied)<br />
#indicate and link to license<br />
<br />
If you change the work, BY-SA also requires you to indicate that you did so and retain any notice on the work about previous changes made to it. BY-SA requires reusers to remove attribution if practicable when requested by the licensor. <br />
<br />
GPLv3 requires:<br />
#copyright notice<br />
#license notices and notice of [http://www.gnu.org/licenses/gpl-3.0.html#section7 Section 7 additional conditions] (if supplied)<br />
#notices about lack of warranty (if supplied)<br />
#copy of the license<br />
<br />
If you change the work, GPL requires you include a prominent notice to indicate that you did so, along with the relevant date. It also requires special notices for certain interactive user interfaces. GPLv3 does not have an attribution removal clause. <br />
<br />
When BY-SA 4.0 content is adapted and used in a GPLv3-licensed project, the adapter has to comply with the BY-SA attribution and marking requirements. However, Section 2(a)(5)(B) of BY-SA 4.0 enables downstream reusers of the GPL-licensed project to look to the GPL to satisfy their obligations under both licenses. CC determined that GPL-style attribution would satisfy the expectations of BY-SA licensors.<br />
<br />
===License scope===<br />
The tone and scope of the two licenses differ, due largely to the fact that the GPLv3 was designed for use with software and software-like works. Both licenses are primarily designed to license copyright, but each license also covers some rights closely related to copyright. GPL covers “copyright-like laws that apply to other kinds of works, such as semiconductor masks,” while BY-SA covers “Copyright and Similar Rights,” which is defined to include neighboring rights, sui generis database rights, and other closely-related rights.<br />
<br />
The most significant difference in license scope is the treatment of patent rights. BY-SA expressly reserves patent rights to the licensor, while GPLv3 expressly includes a patent grant from each contributor.<br />
<br />
Because patent rights are expressly excluded from BY-SA, there is no reliable claim of an implied license to do things with a BY-SA licensed work that implicate patent rights. From a compatibility perspective, this means that when a BY-SA work is adapted and included in a GPL-licensed project, downstream users of the project would not have patent rights (if any) to the adapted BY-SA work.<br />
(Although the GPL includes a patent license, the scope of rights licensed by the BY-SA licensor cannot be unilaterally expanded by an adapter who choses to apply the GPL, just as it is not expanded when an adapter applies a later version of BY-SA that licenses more rights than the original.)<br />
<br />
This creates the possibility that a downstream user of a GPL project will mistakenly assume that all patent rights are treated as they are in GPLv3 when in fact they are not. We have determined, however, that this should not prevent a determination of one-way compatibility because it is largely an academic problem. Rarely (if ever) would a BY-SA work be subject to patent rights that would be implicated by reproducing or adapting the content.<br />
<br />
===Source=== <br />
<br />
The GPL requires that works be distributed with source or that source be made available (with “source” being the preferred form for making modifications to the work). BY-SA does not impose a similar requirement. Instead, BY-SA licensors are free to distribute their works in any format, whether or not modifiable.<br />
<br />
With one-way compatibility to the GPL, no new obligations are imposed under the BY-SA license, either upon the original licensor or any downstream adapter who wishes to license their contributions under the GPL instead of BY-SA. However, those who adapt BY-SA works and choose to license their contributions under the GPL do, however, have to comply with the GPL obligation to distribute or make available the work in the preferred form for making modifications. If an adapter cannot provide or make available source either because she never received the work in modifiable format from the BY-SA licensor or cannot convert the content to modifiable format, then that person cannot take advantage of the one-way compatibility declaration and use the GPLv3 for her contributions.<br />
<br />
===Effective technological measures===<br />
<br />
BY-SA prohibits application of ETMs by licensees if those measures would prevent others from exercising their rights under the license. In contrast, the GPL does not explicitly prohibit application of DRM and other ETMs. Instead, it addresses any potential lockdown of licensed works by requiring distribution of source code in a modifiable form. <br />
<br />
This difference is not problematic, because in order to comply with GPLv3 the adapter must provide source. As stated in the previous section, if an adapter cannot provide or make source available, she cannot use GPLv3 for her contributions. <br />
<br />
===License termination===<br />
<br />
Both licenses terminate automatically upon breach. BY-SA is reinstated automatically if the breach is cured within 30 days of discovery. GPLv3 is reinstated for first-time violators who cure within 30 days of getting notice of the violation from the copyright holder, and may be reinstated after other violations if it has been corrected for 60 days without the licensor's objection. These differences make it so one could technically have rights under the GPLv3<br />
reinstated but not under BY-SA in situations where both licenses apply (i.e. when BY-SA content is adapted and integrated into a GPL-licensed project).<ref>[1] Theoretically, one could have their rights reinstated under BY-SA but not GPL, but this does not create the same risk of potential infringement. Because this is one-way compatibility from BY-SA to GPL only, the adapter’s license (i.e. the last-applied license) will always be the GPL. If someone looks only at the GPL when using a GPL project that incorporates a BY-SA work, at worst they will they will not realize they still have rights to the BY-SA work.</ref> As a practical matter, licensors and licensees in both communities typically deal with license violations outside the strict letter of the license, so we feel this is unlikely to be a real world obstacle to compatibility.<br />
<br />
===Option to comply with later versions===<br />
<br />
GPLv3 gives licensees the option to comply with a later version of the GPL if the licensor has so specified, or to use *any* version of the GPL if no version number was specified, regardless of whether the work has been adapted. BY-SA allows licensees to comply with the conditions of future versions of BY-SA, but only if that version was applied to an adaptation of the work. Because only version 3 of the GPL is an option for compatibility at this time, reusers that adapt BY-SA content into GPL-licensed projects are only able to use GPLv3 unless and until other GPL versions are made compatible. With solid education for both communities and encouragement of clear marking by licensors, we do not feel this is an obstacle to compatibility.<br />
<br />
Also, those GPL licensors who are concerned with enabling use under later versions do have the option of using the proxy provision in the GPLv3 for this. Section 14 of the GPLv3 allows licensors to specify a proxy to determine whether future versions of the GPL can be used. Therefore, if someone adapts a BY-SA 4.0 work into a GPLv3 project, they can specify Creative Commons as their proxy (via http://creativecommons.org/compatiblelicenses) so that if and when Creative Commons determines that a future version of the GPL is a compatible license, the adapted work could be used under that later version. <br />
<br />
==Related policy notes==<br />
Creative Commons consulted extensively with the steward of the GPL v.3 during the 4.0 versioning process, as well as throughout the compatibility process on the policy matters described above. The final determination and policy statements above reflect the best interpretations by both stewards of their respective licenses.<br />
<br />
==Considerations for adapters applying the GPLv3==<br />
Both because of the limited one-way nature of compatibility and because GPLv3 is designed for software, there are a few particular considerations to take into account before applying the GPLv3 as the adapter’s license when adapting BY-SA works.<br />
<br />
:*'''This one-way compatibility mechanism with GPLv3 is not for general use.''' It was designed to help solve a specific problem for those working in niche areas where content is melded with code. Please take advantage of it only when you are adapting BY-SA works into GPLv3 software in ways that make it difficult or impossible for downstream users to distinguish the content from code. <br />
<br />
:* '''BY-SA does not include a patent license.''' Do not apply the GPLv3 if you have any reason to suspect that any patent rights held by the original BY-SA licensor could pose a problem for downstream users. <br />
<br />
:* '''BY-SA works may not be available in the preferred form for making modifications.''' Do not apply the GPLv3 if you cannot comply with the source requirement in the GPL. <br />
<br />
:* '''This compatibility determination only applies to GPL version 3.''' You must specify version 3 of the GPL when redistributing a GPL project into which BY-SA content is adapted. Please see [[ShareAlike_compatibility:_GPLv3#Option_to_comply_with_later_versions|above]] for information on how to deal with this if you are particularly concerned with enabling compatibility with future versions of the GPL. <br />
<br />
== Notes ==<br />
<references /></div>CCID-diane petershttps://wiki.creativecommons.org/index.php?title=ShareAlike_compatibility:_GPLv3&diff=114394ShareAlike compatibility: GPLv32015-09-21T10:58:02Z<p>CCID-diane peters: /* License scope */</p>
<hr />
<div>This page documents the primary decisions made by Creative Commons when considering the [https://www.gnu.org/copyleft/gpl.html GNU General Public License version 3] (the "GPL") for one-way ShareAlike compatibility pursuant to the [https://wiki.creativecommons.org/ShareAlike_compatibility_process_and_criteria compatibility process and criteria]. <br />
<br />
==Timeline==<br />
*The GPL was [http://lists.ibiblio.org/pipermail/cc-licenses/2015-January/007635.html proposed] by CC and the Free Software Foundation as a candidate for one-way compatibility on 29 January 2015. <br />
*CC published a [[ShareAlike_compatibility_analysis:_GPL|preliminary analysis]] of compatibility with GPL on its wiki. <br />
*Public discussion period ran from 29 January to [http://lists.ibiblio.org/pipermail/cc-licenses/2015-April/007691.html 2 April 2015].<br />
*Compatibility determination published on __ September 2015 and GPLv3 added to [https://creativecommons.org/compatiblelicenses the CC compatible license page]<br />
<br />
==License texts analyzed==<br />
*[https://www.gnu.org/copyleft/gpl.html GPLv3] <br />
*[http://creativecommons.org/licenses/by-sa/4.0/legalcode BY-SA 4.0] <br />
<br />
==How one-compatibility operates==<br />
<br />
When someone creates an adaptation of a BY-SA licensed work and includes it in a GPLv3-licensed project, both licenses apply and downstream users must comply with both licenses. However, [https://creativecommons.org/licenses/by-sa/4.0/legalcode#s2a5B Section 2(a)(5)(B)] of BY-SA 4.0 allows anyone who receives the adapted material downstream to satisfy the conditions of both BY-SA and GPLv3 (i.e. attribution and ShareAlike) in the manner dictated by the GPLv3.<br />
<br />
People may *not* adapt a GPLv3-licensed work and use BY-SA to license their contributions. This is not allowed by GPLv3. Thus, this compatibility determination only allows movement one way, from BY-SA 4.0 to GPLv3. <br />
<br />
For more information, see the compatibility-specific FAQs and explanatory information [https://wiki.creativecommons.org/ShareAlike_compatibility here]. We also encourage you to read this list of [[ShareAlike_compatibility:_GPLv3#Considerations_for_adapters_applying_the_GPLv3|considerations before applying the GPLv3]] as the adapter’s license.<br />
<br />
==Gatekeeping determination==<br />
<br />
In 2008, Creative Commons published the [https://wiki.creativecommons.org/CC_Attribution-ShareAlike_Intent CC Attribution-ShareAlike Statement of Intent], in which CC articulated its intentions as steward for the SA licenses. In point 4 of the statement, CC commits that "any candidate for compatibility must also satisfy the definition of a Free Cultural License set out in the Definition of Free Cultural Works." This criteria serves as the initial gatekeeping factor for all candidate licenses.<br />
<br />
The General Public License v.3 is [http://freedomdefined.org/Licenses#GNU_General_Public_License listed as a Free Cultural License], and conforms to the [http://opendefinition.org/licenses/ Open Definition].<br />
<br />
==Policy decisions==<br />
<br />
===Attribution===<br />
<br />
The specific attribution and marking requirements in the two licenses vary slightly.<br />
<br />
BY-SA 4.0 requires:<br />
#creator and attribution parties (if supplied)<br />
# copyright notice (if supplied)<br />
#license notice (if supplied)<br />
#disclaimer notice (if supplied)<br />
#URI or link to the licensed material (if supplied)<br />
#indicate and link to license<br />
<br />
If you change the work, BY-SA also requires you to indicate that you did so and retain any notice on the work about previous changes made to it. BY-SA requires reusers to remove attribution if practicable when requested by the licensor. <br />
<br />
GPLv3 requires:<br />
#copyright notice<br />
#license notices and notice of [http://www.gnu.org/licenses/gpl-3.0.html#section7 Section 7 additional conditions] (if supplied)<br />
#notices about lack of warranty (if supplied)<br />
#copy of the license<br />
<br />
If you change the work, GPL requires you include a prominent notice to indicate that you did so, along with the relevant date. It also requires special notices for certain interactive user interfaces. GPLv3 does not have an attribution removal clause. <br />
<br />
When BY-SA 4.0 content is adapted and used in a GPLv3-licensed project, the adapter has to comply with the BY-SA attribution and marking requirements. However, Section 2(a)(5)(B) of BY-SA 4.0 enables downstream reusers of the GPL-licensed project to look to the GPL to satisfy their obligations under both licenses. CC determined that GPL-style attribution would satisfy the expectations of BY-SA licensors.<br />
<br />
===License scope===<br />
The tone and scope of the two licenses differ, due largely to the fact that the GPLv3 was designed for use with software and software-like works. Both licenses are primarily designed to license copyright, but each license also covers some rights closely related to copyright. GPL covers “copyright-like laws that apply to other kinds of works, such as semiconductor masks,” while BY-SA covers “Copyright and Similar Rights,” which is defined to include neighboring rights, sui generis database rights, and other closely-related rights.<br />
<br />
The most significant difference in license scope is the treatment of patent rights. BY-SA expressly reserves patent rights to the licensor, while GPLv3 expressly includes a patent grant from each contributor.<br />
<br />
Because patent rights are expressly excluded from BY-SA, there is no reliable claim of an implied license to do things with a BY-SA licensed work that implicate patent rights. From a compatibility perspective, this means that when a BY-SA work is adapted and included in a GPL-licensed project, downstream users of the project would not have patent rights (if any) to the adapted BY-SA work.<br />
(Although the GPL includes a patent license, the scope of rights licensed by the BY-SA licensor cannot be unilaterally expanded by an adapter who choses to apply the GPL, just as it is not expanded when an adapter applies a later version of BY-SA that licenses more rights than the original.)<br />
<br />
This creates the possibility that a downstream user of a GPL project will mistakenly assume that all patent rights are treated as they are in GPLv3 when in fact they are not. We have determined, however, that this should not prevent a determination of one-way compatibility because it is largely an academic problem. Rarely (if ever) would a BY-SA work be subject to patent rights that would be implicated by reproducing or adapting the content.<br />
<br />
===Effective technological measures===<br />
<br />
BY-SA prohibits application of ETMs by licensees entirely if those measures would prevent others from exercising their rights under the license. In contrast, the GPL does not explicitly prohibit application of DRM and other ETMs. Instead, it addresses any potential lockdown of licensed works by requiring distribution of source code in a modifiable form. <br />
<br />
This creates a risk that BY-SA works adapted into GPL-licensed projects could be subject to DRM applied by downstream users who look only at the GPL requirements. However, we feel this risk is adequately neutralized by the GPL requirement to provide source. <br />
<br />
===Source=== <br />
<br />
The GPL requires that works be distributed with source or that source be made available (with “source” being the preferred form for making modifications to the work). BY-SA does not impose a similar requirement. Instead, BY-SA licensors are free to distribute their works in any format, whether or not modifiable.<br />
<br />
With one-way compatibility to the GPL, no new obligations are imposed under the BY-SA license, either upon the original licensor or any downstream adapter who wishes to license their contributions under the GPL instead of BY-SA. However, those who adapt BY-SA works and choose to license their contributions under the GPL do, however, still have to comply with the GPL obligation to distribute or make available the work in the preferred form for making modifications. If a particular adapter cannot do this because she never received modifiable format from the BY-SA licensor and/or cannot convert the content to modifiable format, then that person may not take advantage of the one-way compatibility declaration and use the GPL.<br />
<br />
===License termination===<br />
<br />
Both licenses terminate automatically upon breach. BY-SA is reinstated automatically if the breach is cured within 30 days of discovery. GPLv3 is reinstated for first-time violators who cure within 30 days of getting notice of the violation from the copyright holder, and may be reinstated after other violations if it has been corrected for 60 days without the licensor's objection. These differences make it so one could technically have rights under the GPLv3<br />
reinstated but not under BY-SA in situations where both licenses apply (i.e. when BY-SA content is adapted and integrated into a GPL-licensed project).<ref>[1] Theoretically, one could have their rights reinstated under BY-SA but not GPL, but this does not create the same risk of potential infringement. Because this is one-way compatibility from BY-SA to GPL only, the adapter’s license (i.e. the last-applied license) will always be the GPL. If someone looks only at the GPL when using a GPL project that incorporates a BY-SA work, at worst they will they will not realize they still have rights to the BY-SA work.</ref> As a practical matter, licensors and licensees in both communities typically deal with license violations outside the strict letter of the license, so we feel this is unlikely to be a real world obstacle to compatibility.<br />
<br />
===Option to comply with later versions===<br />
<br />
GPLv3 gives licensees the option to comply with a later version of the GPL if the licensor has so specified, or to use *any* version of the GPL if no version number was specified, regardless of whether the work has been adapted. BY-SA allows licensees to comply with the conditions of future versions of BY-SA, but only if that version was applied to an adaptation of the work. Because only version 3 of the GPL is an option for compatibility at this time, reusers that adapt BY-SA content into GPL-licensed projects are only able to use GPLv3 unless and until other GPL versions are made compatible. With solid education for both communities and encouragement of clear marking by licensors, we do not feel this is an obstacle to compatibility.<br />
<br />
Also, those GPL licensors who are concerned with enabling use under later versions do have the option of using the proxy provision in the GPLv3 for this. Section 14 of the GPLv3 allows licensors to specify a proxy to determine whether future versions of the GPL can be used. Therefore, if someone adapts a BY-SA 4.0 work into a GPLv3 project, they can specify Creative Commons as their proxy (via http://creativecommons.org/compatiblelicenses) so that if and when Creative Commons determines that a future version of the GPL is a compatible license, the adapted work could be used under that later version. <br />
<br />
==Related policy notes==<br />
Creative Commons consulted extensively with the steward of the GPL v.3 during the 4.0 versioning process, as well as throughout the compatibility process on the policy matters described above. The final determination and policy statements above reflect the best interpretations by both stewards of their respective licenses.<br />
<br />
==Considerations for adapters applying the GPLv3==<br />
Both because of the limited one-way nature of compatibility and because GPLv3 is designed for software, there are a few particular considerations to take into account before applying the GPLv3 as the adapter’s license when adapting BY-SA works.<br />
<br />
:*'''This one-way compatibility mechanism with GPLv3 is not for general use.''' It was designed to help solve a specific problem for those working in niche areas where content is melded with code. Please take advantage of it only when you are adapting BY-SA works into GPLv3 software in ways that make it difficult or impossible for downstream users to distinguish the content from code. <br />
<br />
:* '''BY-SA does not include a patent license.''' Do not apply the GPLv3 if you have any reason to suspect that any patent rights held by the original BY-SA licensor could pose a problem for downstream users. <br />
<br />
:* '''BY-SA works may not be available in the preferred form for making modifications.''' Do not apply the GPLv3 if you cannot comply with the source requirement in the GPL. <br />
<br />
:* '''This compatibility determination only applies to GPL version 3.''' You must specify version 3 of the GPL when redistributing a GPL project into which BY-SA content is adapted. Please see [[ShareAlike_compatibility:_GPLv3#Option_to_comply_with_later_versions|above]] for information on how to deal with this if you are particularly concerned with enabling compatibility with future versions of the GPL. <br />
<br />
== Notes ==<br />
<references /></div>CCID-diane petershttps://wiki.creativecommons.org/index.php?title=ShareAlike_compatibility:_GPLv3&diff=114393ShareAlike compatibility: GPLv32015-09-21T10:53:32Z<p>CCID-diane peters: /* Attribution */</p>
<hr />
<div>This page documents the primary decisions made by Creative Commons when considering the [https://www.gnu.org/copyleft/gpl.html GNU General Public License version 3] (the "GPL") for one-way ShareAlike compatibility pursuant to the [https://wiki.creativecommons.org/ShareAlike_compatibility_process_and_criteria compatibility process and criteria]. <br />
<br />
==Timeline==<br />
*The GPL was [http://lists.ibiblio.org/pipermail/cc-licenses/2015-January/007635.html proposed] by CC and the Free Software Foundation as a candidate for one-way compatibility on 29 January 2015. <br />
*CC published a [[ShareAlike_compatibility_analysis:_GPL|preliminary analysis]] of compatibility with GPL on its wiki. <br />
*Public discussion period ran from 29 January to [http://lists.ibiblio.org/pipermail/cc-licenses/2015-April/007691.html 2 April 2015].<br />
*Compatibility determination published on __ September 2015 and GPLv3 added to [https://creativecommons.org/compatiblelicenses the CC compatible license page]<br />
<br />
==License texts analyzed==<br />
*[https://www.gnu.org/copyleft/gpl.html GPLv3] <br />
*[http://creativecommons.org/licenses/by-sa/4.0/legalcode BY-SA 4.0] <br />
<br />
==How one-compatibility operates==<br />
<br />
When someone creates an adaptation of a BY-SA licensed work and includes it in a GPLv3-licensed project, both licenses apply and downstream users must comply with both licenses. However, [https://creativecommons.org/licenses/by-sa/4.0/legalcode#s2a5B Section 2(a)(5)(B)] of BY-SA 4.0 allows anyone who receives the adapted material downstream to satisfy the conditions of both BY-SA and GPLv3 (i.e. attribution and ShareAlike) in the manner dictated by the GPLv3.<br />
<br />
People may *not* adapt a GPLv3-licensed work and use BY-SA to license their contributions. This is not allowed by GPLv3. Thus, this compatibility determination only allows movement one way, from BY-SA 4.0 to GPLv3. <br />
<br />
For more information, see the compatibility-specific FAQs and explanatory information [https://wiki.creativecommons.org/ShareAlike_compatibility here]. We also encourage you to read this list of [[ShareAlike_compatibility:_GPLv3#Considerations_for_adapters_applying_the_GPLv3|considerations before applying the GPLv3]] as the adapter’s license.<br />
<br />
==Gatekeeping determination==<br />
<br />
In 2008, Creative Commons published the [https://wiki.creativecommons.org/CC_Attribution-ShareAlike_Intent CC Attribution-ShareAlike Statement of Intent], in which CC articulated its intentions as steward for the SA licenses. In point 4 of the statement, CC commits that "any candidate for compatibility must also satisfy the definition of a Free Cultural License set out in the Definition of Free Cultural Works." This criteria serves as the initial gatekeeping factor for all candidate licenses.<br />
<br />
The General Public License v.3 is [http://freedomdefined.org/Licenses#GNU_General_Public_License listed as a Free Cultural License], and conforms to the [http://opendefinition.org/licenses/ Open Definition].<br />
<br />
==Policy decisions==<br />
<br />
===Attribution===<br />
<br />
The specific attribution and marking requirements in the two licenses vary slightly.<br />
<br />
BY-SA 4.0 requires:<br />
#creator and attribution parties (if supplied)<br />
# copyright notice (if supplied)<br />
#license notice (if supplied)<br />
#disclaimer notice (if supplied)<br />
#URI or link to the licensed material (if supplied)<br />
#indicate and link to license<br />
<br />
If you change the work, BY-SA also requires you to indicate that you did so and retain any notice on the work about previous changes made to it. BY-SA requires reusers to remove attribution if practicable when requested by the licensor. <br />
<br />
GPLv3 requires:<br />
#copyright notice<br />
#license notices and notice of [http://www.gnu.org/licenses/gpl-3.0.html#section7 Section 7 additional conditions] (if supplied)<br />
#notices about lack of warranty (if supplied)<br />
#copy of the license<br />
<br />
If you change the work, GPL requires you include a prominent notice to indicate that you did so, along with the relevant date. It also requires special notices for certain interactive user interfaces. GPLv3 does not have an attribution removal clause. <br />
<br />
When BY-SA 4.0 content is adapted and used in a GPLv3-licensed project, the adapter has to comply with the BY-SA attribution and marking requirements. However, Section 2(a)(5)(B) of BY-SA 4.0 enables downstream reusers of the GPL-licensed project to look to the GPL to satisfy their obligations under both licenses. CC determined that GPL-style attribution would satisfy the expectations of BY-SA licensors.<br />
<br />
===License scope===<br />
The tone and scope of the two licenses differ, due largely to the fact that the GPLv3 was designed for use with software and software-like works. Both licenses are primarily designed to license copyright, but each license also covers some rights closely related to copyright. GPL covers “copyright-like laws that apply to other kinds of works, such as semiconductor masks,” while BY-SA covers “Copyright and Similar Rights,” which is defined to include neighboring rights, sui generis database rights, and other closely-related rights.<br />
<br />
The most significant difference in license scope is the treatment of patent rights. BY-SA expressly reserves patent rights to the licensor, while GPLv3 expressly includes a patent grant from each contributor.<br />
<br />
Because patent rights are expressly excluded from BY-SA, there is no reliable claim of an implied license to do things with a BY-SA licensed work that implicate patent rights. From a compatibility perspective, this means that when a BY-SA work is adapted into a GPL-licensed project, downstream users of the project would not have patent rights to the BY-SA work.<br />
(Although the GPL includes a patent license, the scope of rights licensed by the BY-SA licensor cannot be expanded because an adapter applies the GPL, just as it is not expanded when an adapter applies a later version of BY-SA that licenses more rights than the original.)<br />
<br />
This creates the possibility that a downstream user of a GPL project will mistakenly assume that they do not have to consider patent rights even though a BY-SA work is adapted into the project. However, we do not feel this is should prevent one-way compatibility because it is largely an academic problem, given how rarely BY-SA works are subject to patents that would be implicated by simply reproducing or adapting the content. <br />
<br />
===Effective technological measures===<br />
<br />
BY-SA prohibits application of ETMs by licensees entirely if those measures would prevent others from exercising their rights under the license. In contrast, the GPL does not explicitly prohibit application of DRM and other ETMs. Instead, it addresses any potential lockdown of licensed works by requiring distribution of source code in a modifiable form. <br />
<br />
This creates a risk that BY-SA works adapted into GPL-licensed projects could be subject to DRM applied by downstream users who look only at the GPL requirements. However, we feel this risk is adequately neutralized by the GPL requirement to provide source. <br />
<br />
===Source=== <br />
<br />
The GPL requires that works be distributed with source or that source be made available (with “source” being the preferred form for making modifications to the work). BY-SA does not impose a similar requirement. Instead, BY-SA licensors are free to distribute their works in any format, whether or not modifiable.<br />
<br />
With one-way compatibility to the GPL, no new obligations are imposed under the BY-SA license, either upon the original licensor or any downstream adapter who wishes to license their contributions under the GPL instead of BY-SA. However, those who adapt BY-SA works and choose to license their contributions under the GPL do, however, still have to comply with the GPL obligation to distribute or make available the work in the preferred form for making modifications. If a particular adapter cannot do this because she never received modifiable format from the BY-SA licensor and/or cannot convert the content to modifiable format, then that person may not take advantage of the one-way compatibility declaration and use the GPL.<br />
<br />
===License termination===<br />
<br />
Both licenses terminate automatically upon breach. BY-SA is reinstated automatically if the breach is cured within 30 days of discovery. GPLv3 is reinstated for first-time violators who cure within 30 days of getting notice of the violation from the copyright holder, and may be reinstated after other violations if it has been corrected for 60 days without the licensor's objection. These differences make it so one could technically have rights under the GPLv3<br />
reinstated but not under BY-SA in situations where both licenses apply (i.e. when BY-SA content is adapted and integrated into a GPL-licensed project).<ref>[1] Theoretically, one could have their rights reinstated under BY-SA but not GPL, but this does not create the same risk of potential infringement. Because this is one-way compatibility from BY-SA to GPL only, the adapter’s license (i.e. the last-applied license) will always be the GPL. If someone looks only at the GPL when using a GPL project that incorporates a BY-SA work, at worst they will they will not realize they still have rights to the BY-SA work.</ref> As a practical matter, licensors and licensees in both communities typically deal with license violations outside the strict letter of the license, so we feel this is unlikely to be a real world obstacle to compatibility.<br />
<br />
===Option to comply with later versions===<br />
<br />
GPLv3 gives licensees the option to comply with a later version of the GPL if the licensor has so specified, or to use *any* version of the GPL if no version number was specified, regardless of whether the work has been adapted. BY-SA allows licensees to comply with the conditions of future versions of BY-SA, but only if that version was applied to an adaptation of the work. Because only version 3 of the GPL is an option for compatibility at this time, reusers that adapt BY-SA content into GPL-licensed projects are only able to use GPLv3 unless and until other GPL versions are made compatible. With solid education for both communities and encouragement of clear marking by licensors, we do not feel this is an obstacle to compatibility.<br />
<br />
Also, those GPL licensors who are concerned with enabling use under later versions do have the option of using the proxy provision in the GPLv3 for this. Section 14 of the GPLv3 allows licensors to specify a proxy to determine whether future versions of the GPL can be used. Therefore, if someone adapts a BY-SA 4.0 work into a GPLv3 project, they can specify Creative Commons as their proxy (via http://creativecommons.org/compatiblelicenses) so that if and when Creative Commons determines that a future version of the GPL is a compatible license, the adapted work could be used under that later version. <br />
<br />
==Related policy notes==<br />
Creative Commons consulted extensively with the steward of the GPL v.3 during the 4.0 versioning process, as well as throughout the compatibility process on the policy matters described above. The final determination and policy statements above reflect the best interpretations by both stewards of their respective licenses.<br />
<br />
==Considerations for adapters applying the GPLv3==<br />
Both because of the limited one-way nature of compatibility and because GPLv3 is designed for software, there are a few particular considerations to take into account before applying the GPLv3 as the adapter’s license when adapting BY-SA works.<br />
<br />
:*'''This one-way compatibility mechanism with GPLv3 is not for general use.''' It was designed to help solve a specific problem for those working in niche areas where content is melded with code. Please take advantage of it only when you are adapting BY-SA works into GPLv3 software in ways that make it difficult or impossible for downstream users to distinguish the content from code. <br />
<br />
:* '''BY-SA does not include a patent license.''' Do not apply the GPLv3 if you have any reason to suspect that any patent rights held by the original BY-SA licensor could pose a problem for downstream users. <br />
<br />
:* '''BY-SA works may not be available in the preferred form for making modifications.''' Do not apply the GPLv3 if you cannot comply with the source requirement in the GPL. <br />
<br />
:* '''This compatibility determination only applies to GPL version 3.''' You must specify version 3 of the GPL when redistributing a GPL project into which BY-SA content is adapted. Please see [[ShareAlike_compatibility:_GPLv3#Option_to_comply_with_later_versions|above]] for information on how to deal with this if you are particularly concerned with enabling compatibility with future versions of the GPL. <br />
<br />
== Notes ==<br />
<references /></div>CCID-diane petershttps://wiki.creativecommons.org/index.php?title=ShareAlike_compatibility:_GPLv3&diff=114392ShareAlike compatibility: GPLv32015-09-21T10:51:19Z<p>CCID-diane peters: /* How one-compatibility operates */</p>
<hr />
<div>This page documents the primary decisions made by Creative Commons when considering the [https://www.gnu.org/copyleft/gpl.html GNU General Public License version 3] (the "GPL") for one-way ShareAlike compatibility pursuant to the [https://wiki.creativecommons.org/ShareAlike_compatibility_process_and_criteria compatibility process and criteria]. <br />
<br />
==Timeline==<br />
*The GPL was [http://lists.ibiblio.org/pipermail/cc-licenses/2015-January/007635.html proposed] by CC and the Free Software Foundation as a candidate for one-way compatibility on 29 January 2015. <br />
*CC published a [[ShareAlike_compatibility_analysis:_GPL|preliminary analysis]] of compatibility with GPL on its wiki. <br />
*Public discussion period ran from 29 January to [http://lists.ibiblio.org/pipermail/cc-licenses/2015-April/007691.html 2 April 2015].<br />
*Compatibility determination published on __ September 2015 and GPLv3 added to [https://creativecommons.org/compatiblelicenses the CC compatible license page]<br />
<br />
==License texts analyzed==<br />
*[https://www.gnu.org/copyleft/gpl.html GPLv3] <br />
*[http://creativecommons.org/licenses/by-sa/4.0/legalcode BY-SA 4.0] <br />
<br />
==How one-compatibility operates==<br />
<br />
When someone creates an adaptation of a BY-SA licensed work and includes it in a GPLv3-licensed project, both licenses apply and downstream users must comply with both licenses. However, [https://creativecommons.org/licenses/by-sa/4.0/legalcode#s2a5B Section 2(a)(5)(B)] of BY-SA 4.0 allows anyone who receives the adapted material downstream to satisfy the conditions of both BY-SA and GPLv3 (i.e. attribution and ShareAlike) in the manner dictated by the GPLv3.<br />
<br />
People may *not* adapt a GPLv3-licensed work and use BY-SA to license their contributions. This is not allowed by GPLv3. Thus, this compatibility determination only allows movement one way, from BY-SA 4.0 to GPLv3. <br />
<br />
For more information, see the compatibility-specific FAQs and explanatory information [https://wiki.creativecommons.org/ShareAlike_compatibility here]. We also encourage you to read this list of [[ShareAlike_compatibility:_GPLv3#Considerations_for_adapters_applying_the_GPLv3|considerations before applying the GPLv3]] as the adapter’s license.<br />
<br />
==Gatekeeping determination==<br />
<br />
In 2008, Creative Commons published the [https://wiki.creativecommons.org/CC_Attribution-ShareAlike_Intent CC Attribution-ShareAlike Statement of Intent], in which CC articulated its intentions as steward for the SA licenses. In point 4 of the statement, CC commits that "any candidate for compatibility must also satisfy the definition of a Free Cultural License set out in the Definition of Free Cultural Works." This criteria serves as the initial gatekeeping factor for all candidate licenses.<br />
<br />
The General Public License v.3 is [http://freedomdefined.org/Licenses#GNU_General_Public_License listed as a Free Cultural License], and conforms to the [http://opendefinition.org/licenses/ Open Definition].<br />
<br />
==Policy decisions==<br />
<br />
===Attribution===<br />
<br />
The specific attribution and marking requirements in the two licenses vary slightly.<br />
<br />
BY-SA requires:<br />
#creator and attribution parties (if supplied)<br />
# copyright notice (if supplied)<br />
#license notice (if supplied)<br />
#disclaimer notice (if supplied)<br />
#URI or link to the licensed material (if supplied)<br />
#indicate and link to license<br />
<br />
If you change the work, BY-SA also requires you to indicate that you did so and retain any notice on the work about previous changes made to it. BY-SA requires reusers to remove attribution when requested by the licensor. <br />
<br />
GPL requires:<br />
#copyright notice<br />
#license notices and notice of [http://www.gnu.org/licenses/gpl-3.0.html#section7 Section 7 additional conditions] (if supplied)<br />
#notices about lack of warranty (if supplied)<br />
#copy of the license<br />
<br />
If you change the work, GPL requires you include a prominent notice to indicate that you did so, along with the relevant date. It also requires special notices for certain interactive user interfaces. GPLv3 does not have an attribution removal clause. <br />
<br />
When BY-SA content is adapted into a GPL-licensed project, the adapter has to comply with the BY-SA attribution and marking requirements. However, Section 2(a)(5)(B) of BY-SA 4.0 enables downstream reusers of the GPL-licensed project to look to the GPL to satisfy their obligations to both authors. CC determined that GPL-style attribution would satisfy the expectations of BY-SA licensors. <br />
<br />
===License scope===<br />
The tone and scope of the two licenses differ, due largely to the fact that the GPLv3 was designed for use with software and software-like works. Both licenses are primarily designed to license copyright, but each license also covers some rights closely related to copyright. GPL covers “copyright-like laws that apply to other kinds of works, such as semiconductor masks,” while BY-SA covers “Copyright and Similar Rights,” which is defined to include neighboring rights, sui generis database rights, and other closely-related rights.<br />
<br />
The most significant difference in license scope is the treatment of patent rights. BY-SA expressly reserves patent rights to the licensor, while GPLv3 expressly includes a patent grant from each contributor.<br />
<br />
Because patent rights are expressly excluded from BY-SA, there is no reliable claim of an implied license to do things with a BY-SA licensed work that implicate patent rights. From a compatibility perspective, this means that when a BY-SA work is adapted into a GPL-licensed project, downstream users of the project would not have patent rights to the BY-SA work.<br />
(Although the GPL includes a patent license, the scope of rights licensed by the BY-SA licensor cannot be expanded because an adapter applies the GPL, just as it is not expanded when an adapter applies a later version of BY-SA that licenses more rights than the original.)<br />
<br />
This creates the possibility that a downstream user of a GPL project will mistakenly assume that they do not have to consider patent rights even though a BY-SA work is adapted into the project. However, we do not feel this is should prevent one-way compatibility because it is largely an academic problem, given how rarely BY-SA works are subject to patents that would be implicated by simply reproducing or adapting the content. <br />
<br />
===Effective technological measures===<br />
<br />
BY-SA prohibits application of ETMs by licensees entirely if those measures would prevent others from exercising their rights under the license. In contrast, the GPL does not explicitly prohibit application of DRM and other ETMs. Instead, it addresses any potential lockdown of licensed works by requiring distribution of source code in a modifiable form. <br />
<br />
This creates a risk that BY-SA works adapted into GPL-licensed projects could be subject to DRM applied by downstream users who look only at the GPL requirements. However, we feel this risk is adequately neutralized by the GPL requirement to provide source. <br />
<br />
===Source=== <br />
<br />
The GPL requires that works be distributed with source or that source be made available (with “source” being the preferred form for making modifications to the work). BY-SA does not impose a similar requirement. Instead, BY-SA licensors are free to distribute their works in any format, whether or not modifiable.<br />
<br />
With one-way compatibility to the GPL, no new obligations are imposed under the BY-SA license, either upon the original licensor or any downstream adapter who wishes to license their contributions under the GPL instead of BY-SA. However, those who adapt BY-SA works and choose to license their contributions under the GPL do, however, still have to comply with the GPL obligation to distribute or make available the work in the preferred form for making modifications. If a particular adapter cannot do this because she never received modifiable format from the BY-SA licensor and/or cannot convert the content to modifiable format, then that person may not take advantage of the one-way compatibility declaration and use the GPL.<br />
<br />
===License termination===<br />
<br />
Both licenses terminate automatically upon breach. BY-SA is reinstated automatically if the breach is cured within 30 days of discovery. GPLv3 is reinstated for first-time violators who cure within 30 days of getting notice of the violation from the copyright holder, and may be reinstated after other violations if it has been corrected for 60 days without the licensor's objection. These differences make it so one could technically have rights under the GPLv3<br />
reinstated but not under BY-SA in situations where both licenses apply (i.e. when BY-SA content is adapted and integrated into a GPL-licensed project).<ref>[1] Theoretically, one could have their rights reinstated under BY-SA but not GPL, but this does not create the same risk of potential infringement. Because this is one-way compatibility from BY-SA to GPL only, the adapter’s license (i.e. the last-applied license) will always be the GPL. If someone looks only at the GPL when using a GPL project that incorporates a BY-SA work, at worst they will they will not realize they still have rights to the BY-SA work.</ref> As a practical matter, licensors and licensees in both communities typically deal with license violations outside the strict letter of the license, so we feel this is unlikely to be a real world obstacle to compatibility.<br />
<br />
===Option to comply with later versions===<br />
<br />
GPLv3 gives licensees the option to comply with a later version of the GPL if the licensor has so specified, or to use *any* version of the GPL if no version number was specified, regardless of whether the work has been adapted. BY-SA allows licensees to comply with the conditions of future versions of BY-SA, but only if that version was applied to an adaptation of the work. Because only version 3 of the GPL is an option for compatibility at this time, reusers that adapt BY-SA content into GPL-licensed projects are only able to use GPLv3 unless and until other GPL versions are made compatible. With solid education for both communities and encouragement of clear marking by licensors, we do not feel this is an obstacle to compatibility.<br />
<br />
Also, those GPL licensors who are concerned with enabling use under later versions do have the option of using the proxy provision in the GPLv3 for this. Section 14 of the GPLv3 allows licensors to specify a proxy to determine whether future versions of the GPL can be used. Therefore, if someone adapts a BY-SA 4.0 work into a GPLv3 project, they can specify Creative Commons as their proxy (via http://creativecommons.org/compatiblelicenses) so that if and when Creative Commons determines that a future version of the GPL is a compatible license, the adapted work could be used under that later version. <br />
<br />
==Related policy notes==<br />
Creative Commons consulted extensively with the steward of the GPL v.3 during the 4.0 versioning process, as well as throughout the compatibility process on the policy matters described above. The final determination and policy statements above reflect the best interpretations by both stewards of their respective licenses.<br />
<br />
==Considerations for adapters applying the GPLv3==<br />
Both because of the limited one-way nature of compatibility and because GPLv3 is designed for software, there are a few particular considerations to take into account before applying the GPLv3 as the adapter’s license when adapting BY-SA works.<br />
<br />
:*'''This one-way compatibility mechanism with GPLv3 is not for general use.''' It was designed to help solve a specific problem for those working in niche areas where content is melded with code. Please take advantage of it only when you are adapting BY-SA works into GPLv3 software in ways that make it difficult or impossible for downstream users to distinguish the content from code. <br />
<br />
:* '''BY-SA does not include a patent license.''' Do not apply the GPLv3 if you have any reason to suspect that any patent rights held by the original BY-SA licensor could pose a problem for downstream users. <br />
<br />
:* '''BY-SA works may not be available in the preferred form for making modifications.''' Do not apply the GPLv3 if you cannot comply with the source requirement in the GPL. <br />
<br />
:* '''This compatibility determination only applies to GPL version 3.''' You must specify version 3 of the GPL when redistributing a GPL project into which BY-SA content is adapted. Please see [[ShareAlike_compatibility:_GPLv3#Option_to_comply_with_later_versions|above]] for information on how to deal with this if you are particularly concerned with enabling compatibility with future versions of the GPL. <br />
<br />
== Notes ==<br />
<references /></div>CCID-diane petershttps://wiki.creativecommons.org/index.php?title=ShareAlike_compatibility:_GPLv3&diff=114391ShareAlike compatibility: GPLv32015-09-21T10:47:21Z<p>CCID-diane peters: /* Timeline */</p>
<hr />
<div>This page documents the primary decisions made by Creative Commons when considering the [https://www.gnu.org/copyleft/gpl.html GNU General Public License version 3] (the "GPL") for one-way ShareAlike compatibility pursuant to the [https://wiki.creativecommons.org/ShareAlike_compatibility_process_and_criteria compatibility process and criteria]. <br />
<br />
==Timeline==<br />
*The GPL was [http://lists.ibiblio.org/pipermail/cc-licenses/2015-January/007635.html proposed] by CC and the Free Software Foundation as a candidate for one-way compatibility on 29 January 2015. <br />
*CC published a [[ShareAlike_compatibility_analysis:_GPL|preliminary analysis]] of compatibility with GPL on its wiki. <br />
*Public discussion period ran from 29 January to [http://lists.ibiblio.org/pipermail/cc-licenses/2015-April/007691.html 2 April 2015].<br />
*Compatibility determination published on __ September 2015 and GPLv3 added to [https://creativecommons.org/compatiblelicenses the CC compatible license page]<br />
<br />
==License texts analyzed==<br />
*[https://www.gnu.org/copyleft/gpl.html GPLv3] <br />
*[http://creativecommons.org/licenses/by-sa/4.0/legalcode BY-SA 4.0] <br />
<br />
==How one-compatibility operates==<br />
<br />
When someone adapts a BY-SA work into a GPLv3 project, both licenses apply and downstream users must comply with both. However, because of [https://creativecommons.org/licenses/by-sa/4.0/legalcode#s2a5B Section 2(a)(5)(B)] of BY-SA 4.0, anyone who receives the adapted material downstream may satisfy the conditions of both BY-SA and GPLv3 (i.e. attribution and ShareAlike) in the manner dictated by the GPLv3.<br />
<br />
People may *not* take GPLv3 work and apply BY-SA to their contributions. This compatibility determination only allows movement one way, from BY-SA to GPL. <br />
<br />
For more information, see the compatibility-specific FAQs and explanatory information [https://wiki.creativecommons.org/ShareAlike_compatibility here]. We also encourage you to read this list of [[ShareAlike_compatibility:_GPLv3#Considerations_for_adapters_applying_the_GPLv3|considerations before applying the GPLv3]] as the adapter’s license. <br />
<br />
==Gatekeeping determination==<br />
<br />
In 2008, Creative Commons published the [https://wiki.creativecommons.org/CC_Attribution-ShareAlike_Intent CC Attribution-ShareAlike Statement of Intent], in which CC articulated its intentions as steward for the SA licenses. In point 4 of the statement, CC commits that "any candidate for compatibility must also satisfy the definition of a Free Cultural License set out in the Definition of Free Cultural Works." This criteria serves as the initial gatekeeping factor for all candidate licenses.<br />
<br />
The General Public License v.3 is [http://freedomdefined.org/Licenses#GNU_General_Public_License listed as a Free Cultural License], and conforms to the [http://opendefinition.org/licenses/ Open Definition].<br />
<br />
==Policy decisions==<br />
<br />
===Attribution===<br />
<br />
The specific attribution and marking requirements in the two licenses vary slightly.<br />
<br />
BY-SA requires:<br />
#creator and attribution parties (if supplied)<br />
# copyright notice (if supplied)<br />
#license notice (if supplied)<br />
#disclaimer notice (if supplied)<br />
#URI or link to the licensed material (if supplied)<br />
#indicate and link to license<br />
<br />
If you change the work, BY-SA also requires you to indicate that you did so and retain any notice on the work about previous changes made to it. BY-SA requires reusers to remove attribution when requested by the licensor. <br />
<br />
GPL requires:<br />
#copyright notice<br />
#license notices and notice of [http://www.gnu.org/licenses/gpl-3.0.html#section7 Section 7 additional conditions] (if supplied)<br />
#notices about lack of warranty (if supplied)<br />
#copy of the license<br />
<br />
If you change the work, GPL requires you include a prominent notice to indicate that you did so, along with the relevant date. It also requires special notices for certain interactive user interfaces. GPLv3 does not have an attribution removal clause. <br />
<br />
When BY-SA content is adapted into a GPL-licensed project, the adapter has to comply with the BY-SA attribution and marking requirements. However, Section 2(a)(5)(B) of BY-SA 4.0 enables downstream reusers of the GPL-licensed project to look to the GPL to satisfy their obligations to both authors. CC determined that GPL-style attribution would satisfy the expectations of BY-SA licensors. <br />
<br />
===License scope===<br />
The tone and scope of the two licenses differ, due largely to the fact that the GPLv3 was designed for use with software and software-like works. Both licenses are primarily designed to license copyright, but each license also covers some rights closely related to copyright. GPL covers “copyright-like laws that apply to other kinds of works, such as semiconductor masks,” while BY-SA covers “Copyright and Similar Rights,” which is defined to include neighboring rights, sui generis database rights, and other closely-related rights.<br />
<br />
The most significant difference in license scope is the treatment of patent rights. BY-SA expressly reserves patent rights to the licensor, while GPLv3 expressly includes a patent grant from each contributor.<br />
<br />
Because patent rights are expressly excluded from BY-SA, there is no reliable claim of an implied license to do things with a BY-SA licensed work that implicate patent rights. From a compatibility perspective, this means that when a BY-SA work is adapted into a GPL-licensed project, downstream users of the project would not have patent rights to the BY-SA work.<br />
(Although the GPL includes a patent license, the scope of rights licensed by the BY-SA licensor cannot be expanded because an adapter applies the GPL, just as it is not expanded when an adapter applies a later version of BY-SA that licenses more rights than the original.)<br />
<br />
This creates the possibility that a downstream user of a GPL project will mistakenly assume that they do not have to consider patent rights even though a BY-SA work is adapted into the project. However, we do not feel this is should prevent one-way compatibility because it is largely an academic problem, given how rarely BY-SA works are subject to patents that would be implicated by simply reproducing or adapting the content. <br />
<br />
===Effective technological measures===<br />
<br />
BY-SA prohibits application of ETMs by licensees entirely if those measures would prevent others from exercising their rights under the license. In contrast, the GPL does not explicitly prohibit application of DRM and other ETMs. Instead, it addresses any potential lockdown of licensed works by requiring distribution of source code in a modifiable form. <br />
<br />
This creates a risk that BY-SA works adapted into GPL-licensed projects could be subject to DRM applied by downstream users who look only at the GPL requirements. However, we feel this risk is adequately neutralized by the GPL requirement to provide source. <br />
<br />
===Source=== <br />
<br />
The GPL requires that works be distributed with source or that source be made available (with “source” being the preferred form for making modifications to the work). BY-SA does not impose a similar requirement. Instead, BY-SA licensors are free to distribute their works in any format, whether or not modifiable.<br />
<br />
With one-way compatibility to the GPL, no new obligations are imposed under the BY-SA license, either upon the original licensor or any downstream adapter who wishes to license their contributions under the GPL instead of BY-SA. However, those who adapt BY-SA works and choose to license their contributions under the GPL do, however, still have to comply with the GPL obligation to distribute or make available the work in the preferred form for making modifications. If a particular adapter cannot do this because she never received modifiable format from the BY-SA licensor and/or cannot convert the content to modifiable format, then that person may not take advantage of the one-way compatibility declaration and use the GPL.<br />
<br />
===License termination===<br />
<br />
Both licenses terminate automatically upon breach. BY-SA is reinstated automatically if the breach is cured within 30 days of discovery. GPLv3 is reinstated for first-time violators who cure within 30 days of getting notice of the violation from the copyright holder, and may be reinstated after other violations if it has been corrected for 60 days without the licensor's objection. These differences make it so one could technically have rights under the GPLv3<br />
reinstated but not under BY-SA in situations where both licenses apply (i.e. when BY-SA content is adapted and integrated into a GPL-licensed project).<ref>[1] Theoretically, one could have their rights reinstated under BY-SA but not GPL, but this does not create the same risk of potential infringement. Because this is one-way compatibility from BY-SA to GPL only, the adapter’s license (i.e. the last-applied license) will always be the GPL. If someone looks only at the GPL when using a GPL project that incorporates a BY-SA work, at worst they will they will not realize they still have rights to the BY-SA work.</ref> As a practical matter, licensors and licensees in both communities typically deal with license violations outside the strict letter of the license, so we feel this is unlikely to be a real world obstacle to compatibility.<br />
<br />
===Option to comply with later versions===<br />
<br />
GPLv3 gives licensees the option to comply with a later version of the GPL if the licensor has so specified, or to use *any* version of the GPL if no version number was specified, regardless of whether the work has been adapted. BY-SA allows licensees to comply with the conditions of future versions of BY-SA, but only if that version was applied to an adaptation of the work. Because only version 3 of the GPL is an option for compatibility at this time, reusers that adapt BY-SA content into GPL-licensed projects are only able to use GPLv3 unless and until other GPL versions are made compatible. With solid education for both communities and encouragement of clear marking by licensors, we do not feel this is an obstacle to compatibility.<br />
<br />
Also, those GPL licensors who are concerned with enabling use under later versions do have the option of using the proxy provision in the GPLv3 for this. Section 14 of the GPLv3 allows licensors to specify a proxy to determine whether future versions of the GPL can be used. Therefore, if someone adapts a BY-SA 4.0 work into a GPLv3 project, they can specify Creative Commons as their proxy (via http://creativecommons.org/compatiblelicenses) so that if and when Creative Commons determines that a future version of the GPL is a compatible license, the adapted work could be used under that later version. <br />
<br />
==Related policy notes==<br />
Creative Commons consulted extensively with the steward of the GPL v.3 during the 4.0 versioning process, as well as throughout the compatibility process on the policy matters described above. The final determination and policy statements above reflect the best interpretations by both stewards of their respective licenses.<br />
<br />
==Considerations for adapters applying the GPLv3==<br />
Both because of the limited one-way nature of compatibility and because GPLv3 is designed for software, there are a few particular considerations to take into account before applying the GPLv3 as the adapter’s license when adapting BY-SA works.<br />
<br />
:*'''This one-way compatibility mechanism with GPLv3 is not for general use.''' It was designed to help solve a specific problem for those working in niche areas where content is melded with code. Please take advantage of it only when you are adapting BY-SA works into GPLv3 software in ways that make it difficult or impossible for downstream users to distinguish the content from code. <br />
<br />
:* '''BY-SA does not include a patent license.''' Do not apply the GPLv3 if you have any reason to suspect that any patent rights held by the original BY-SA licensor could pose a problem for downstream users. <br />
<br />
:* '''BY-SA works may not be available in the preferred form for making modifications.''' Do not apply the GPLv3 if you cannot comply with the source requirement in the GPL. <br />
<br />
:* '''This compatibility determination only applies to GPL version 3.''' You must specify version 3 of the GPL when redistributing a GPL project into which BY-SA content is adapted. Please see [[ShareAlike_compatibility:_GPLv3#Option_to_comply_with_later_versions|above]] for information on how to deal with this if you are particularly concerned with enabling compatibility with future versions of the GPL. <br />
<br />
== Notes ==<br />
<references /></div>CCID-diane petershttps://wiki.creativecommons.org/index.php?title=Legal_tools_translation_guide&diff=114222Legal tools translation guide2015-08-13T23:08:18Z<p>CCID-diane peters: /* 4.0 license suite issues */</p>
<hr />
<div>This Translation Guide is intended to guide teams preparing linguistic translations of the CC legal tools in accordance with the [[Legal Code Translation Policy]]. It identifies common issues that arise when translating and proofing the text. Please review this guide when proofing your first draft before submitting to CC HQ. (This is not a complete list of potential issues, and review by CC HQ is still necessary before a translation can be finalized and published.)<br />
<br />
This document will be continually updated and improved as we work with teams on their translations and identify additional issues: please send any comments and additions not already identifed through the translation process to legal@creativecommons.org. <br />
<br />
==General issues for all documents==<br />
* Formatting should be kept the same&mdash;text that is bold or emphasized in the original English text should also be formatted that way in any translation. (Even if different jurisdictions would customarily do this emphasis differently.)<br />
<br />
* All definitions should remain in the same order (even though the translated terms will no longer be in alphabetical order). Similarly, all license sections should remain in the same order. This is to ensure that cross-references to sections within the text remain the same, and also so that explanatory materials that refer to particular sections of the license are applicable to all translations of the license.<br />
<br />
* Capitalized phrases should be translated the same way throughout the document. For example, wherever "Copyright and Similar Rights" is used, the phrase used for its translation in the definition of Adapted Material (the first time it appears) should also be used in all of the other definitions where the phrase appears.<br />
<br />
* All defined terms should correspond as closely as possible to the English meaning. It is fine to replace these defined terms with longer phrases if it is necessary to get the correct meaning. <br />
<br />
* No references to specific local legislation should be included; the legal meaning of all provisions should be kept the same as in the English version. (Where there are questions about something that does not have an appropriate linguistic translation, please point them out to Legal. If you are able to come to an appropriate solution within your community, we'd like to hear the decisions you made, and if you are stuck we will work with you to find something that comes closest to the meaning of the English text. )<br />
<br />
* All substantive clauses from the original document should be included.<br />
<br />
* Cross-references to other sections should be correct; this is particularly something to watch for when translating the 4.0 license suite.<br />
<br />
* Numbering of sections should match with the original. <br />
<br />
* Please check spelling and grammar.<br />
<br />
* Connecting words should be checked: for example, "and" and "or" in English should line up with words with corresponding meaning in the translation.<br />
<br />
* Include the navigational boxes indicating the availability of other languages. Please note that if you are translating from English, you should also include English on the "in other languages" box! Languages should appear on the list in that langauge&mdash;for example, "English", "Nederlands", "français ", "Ελληνικά".)<br />
<br />
* Explanatory text should be kept outside the license, except for English terms quoted for clarity when no exact translation exists. We do encourage you to create or translate FAQs and other explanatory materials, however.<br />
<br />
* Notes should be kept on the translation worksheet, available at [[Legal_Code_Translation_Policy#Supporting_documents]]. This worksheet will be the primary place where the legal team leaves comments on a translation in progress. You are encouraged to include other translation and process notes as a separate section, if they are not specific to a particular item in the chart or if they require more explanation.<br />
<br />
===Using references===<br />
If there are ports of earlier versions of the license in your language (in any jurisdiction), please note any differences in word choice or other elements that would might otherwise be expected to be the same. (It is acceptable to choose differently, but should be for a reason that makes sense for the current project.) Where there are differences between multiple ports in a language used by multiple jurisdictions, please note the reasoning for the choice made.<br />
<br />
Where there are terms that correspond to concepts in legal references, such as national copyright laws in jurisdictions which use your language, the Berne Convention, the Database Directive, other national/regional laws or international treaties, or legal scholarship in your language, please note where you are using these reference as a guide to word choices, or where you are making a different choice.<br />
<br />
===Elements outside the legal code===<br />
* Elements that are not part of the Legal code (as defined at [[Legal code]]) must still be translated, though it is not required that they correspond as strictly. This includes all notices and diclaimers on the page.<br />
<br />
* Remember to change links to translations in your language, where applicable. For example, in the 4.0 licenses, the link back to the Commons Deed at the bottom of the document should link directly back to the Deed in your language. Similarly, if you have translated the Considerations page, the link to that page in the introductory paragraphs should be to your language's translation.<br />
<br />
* Before a translation will be published, the Deed and the Chooser must also be translated. Even if you already have a translation in your language, you may wish to revisit these before the translation is published to make sure the word choice matches up with the choices made in the legal code.<br />
<br />
* URLs in the document are protocol relative; that is, they do not begin with "http:" or "https:". Links in the document should look like "//creativecommons.org".<br />
<br />
==4.0 license suite issues==<br />
* "Using Creative Commons Public Licenses": "Creative Commons Public Licenses" should all be capitalized as a defined phrase.<br />
* "Copyright and Similar Rights": in English, this was deliberately written to be broader than "Copyright and Neighboring Rights", which appears in 3.0. Many jurisdictions have a set of rights often referred to as "Neighboring Rights", and a term corresponding to that set of rights was probably used in any 3.0 ports, and may appear in national copyright laws. The term in your 4.0 translation should not be that term--it should be broader, to include neighboring rights and others mentioned in the scope of the license. The term used in 4.0 should also be different from the translation for "Copyright and Related Rights" used in CC0 because the CC0 term has a slightly different scope. <br />
* "Effective Technological Measures": this is not equivalent to "Technical Protection Measures" or "Digital Rights Management"/"DRM". The phrase was chosen in English to correspond exactly to those measures which carry legal penalties for circumvention (which is not necessarily true of all Technological Protection Measures). If there is a distinction between the two in reference in your languages, please use the one that corresponds to "Effective Technological Measures".<br />
* "You": in the definition, please mention all forms of the word that appear in the translated document (for example, English mentions both "You" and "Your").<br />
* "For the avoidance of doubt": this is an idiomatic English phrase. Where this phrase occurs, the translation should be something that indicates that the text which follows is not necessary and does not change the meaning of any other text in the license, but is included to ensure that the other license text is not misinterpreted. <br />
* "Fair use" and "fair dealing": where these terms do not have equivalents in your language, you may wish to include the English phrase in quotations to be clear that they are referring to particular legal concepts that apply to some jurisdictions. <br />
* If you are using terms that are abbreviated (such as "URI"), be sure that you also replace the abbreviation if you are using a translated term. You may wish to also include the English in parentheses (such as "URI") if it is commonly known or used in your language.<br />
* "Adapted Material" is the equivalent of a derivative work, which is to say that the licensee required permission as a matter of copyright to create the new derived work. Not every alteration to a CC-licensed work results in creation of Adapted Material. Alterations that are not sufficiently creative to result in Adapted Material would not violate the NoDerivatives restriction or require that the modified work be licensed under the ShareAlike condition for works licensed under an ND or SA license.<br />
<br />
==CC0 issues==<br />
*Key Words: these words are most important to determining the meaning of the document. Please let us know if you have any questions around how to translate these words (particularly if there is not an exact translation, if the English meaning is not clear to you, or if the difference between the key word and other similar terms is not clear to you).<br />
** "Copyright and Related Rights": note that this is a different phrase than the language in 4.0 for "Copyright and Similar Rights"&mdash;these are not identical in scope and should probably be different in most translations. <br />
** "Work"<br />
** "Affirmer": the English version states that CC0 is "associated with" or "applied to" the work. Translations should choose words that convey that this is being done by an Affirmer who has authority to apply CC0 to the work.<br />
** "License"<br />
** "Waiver"<br />
** "Statement of Purpose": this should be referred to as a proper name everywhere in the document, with the same wording that is used in the first section heading. It must be clear that references elsewhere in the text mean the "Statement of Purpose" section of the document, not simply any statement of purpose.<br />
<br />
*The heading should be "CC0 1.0 Universal"<br />
* In paragraphs 2 and 3, subsections i-iv should use the same wording in each place where the English text is also identical, unless there is a particular reason for them to be different.<br />
* If there is a [http://pro.europeana.eu/support-for-open-data Europeana translation for your language], please refer to it and note any important differences in your worksheet.<br />
<br />
==Creating the files==<br />
To create the HTML files, we recommend using the English legal code pages as templates for your own. You can download the HTML 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.<br />
<br />
Once you have completed the above steps and relevant processes in the [[legal code translation policy]], please send the XHTML file to legal@creativecommons.org along with your report of drafting issues you encountered.<br />
<br />
Then save each file separately according to the following convention:<br />
<br />
*CC0:<br />
** zero_1.0_[language code].html<br />
<br />
(For example, "zero_1.0_fr.html" would be for the French translation.)<br />
<br />
*4.0<br />
**by_4.0_[language code].html<br />
**by-sa_4.0_[language code].html<br />
** [...]<br />
<br />
[[Category:CC0]]<br />
[[Category:4.0]]<br />
[[Category:Legal]]<br />
[[Category:Translation]]</div>CCID-diane petershttps://wiki.creativecommons.org/index.php?title=IRC&diff=113919IRC2015-06-04T12:58:11Z<p>CCID-diane peters: /* People */</p>
<hr />
<div>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.<br />
<br />
There is a Creative Commons IRC channel on the [http://freenode.net/ freenode] network, called '''[irc://irc.freenode.net/creativecommons #creativecommons]'''.<br />
<br />
There is also a channel for CC's free software development work: '''[irc://irc.freenode.net/creativecommons-dev #creativecommons-dev]'''.<br />
<br />
==People==<br />
Some people use IRC nicks that may or may not correspond to their actual names, and sometimes it's just not clear who people are. If you would like to be listed so that people can better identify you, add yourself here (in alphabetical order):<br />
<br />
* billytwosheds: Billy Meinke, CC Education staff<br />
* mattl: Matt Lee, CC Tech<br />
* mindspillage (or mind|wandering): Kat Walsh, CC Legal staff.<br />
* stace: Paul Stacey, CC Education staff<br />
* tvol: Timothy Vollmer, CC Policy staff<br />
* peterspdx: Diane Peters, CC General Counsel<br />
<br />
== IRC help ==<br />
<br />
Nicknames on IRC are on a per-server basis. We use the freenode server exclusively, so registering a nickname is a one-time deal.<br />
<br />
First change your nickname to something unique:<br />
<br />
/nick mattl<br />
<br />
=== Registration ===<br />
<br />
When you have chosen your nickname register it with the nickname service.<br />
<br />
/msg nickserv register password email<br />
<br />
Replacing password with a strong password and email with your email address. For example:<br />
<br />
/msg nickserv register sci3nce!! punkish@creativecommons.biz<br />
<br />
You should save this password in your IRC client, if you can. <br />
<br />
'''On IRCCloud:''' <br />
<br />
* Click the name of the network (freenode) on the right of the screen<br />
* Then click edit<br />
* Expand the advanced options to find a place to save your nickserv password.<br />
<br />
[[File:IRCCloudNicknames.png]]</div>CCID-diane petershttps://wiki.creativecommons.org/index.php?title=ShareAlike_compatibility&diff=113915ShareAlike compatibility2015-05-28T14:19:03Z<p>CCID-diane peters: /* FAQs about ShareAlike compatibility */</p>
<hr />
<div>==FAQs about ShareAlike compatibility==<br />
<br />
'''What is ShareAlike compatibility and why is it important?'''<br />
<br />
The ShareAlike licenses are designed to ensure that the freedoms associated with a licensed work survive as the work is adapted by others and that those freedoms attach to adaptations of the work as well. There are other copyleft licenses designed for this same purpose, but unfortunately, the works licensed under these other licenses are not compatible with works licensed under BY-SA. Creative Commons created the [https://wiki.creativecommons.org/ShareAlike_compatibility_criteria ShareAlike compatibility process] as a means to solving this problem. The process allows CC to evaluate other similar copyleft licenses to determine if they are similar enough to BY-SA to meet licensor expectations and hence be deemed compatible. BY-SA Compatible Licenses are listed [https://creativecommons.org/compatiblelicenses here]. <br />
<br />
'''How does ShareAlike compatibility work?'''<br />
<br />
Once a license is deemed compatible with BY-SA, anyone adapting BY-SA works can apply that license to their own contributions to the adaptation. With version 4.0, future versions of BY-SA are automatically compatible. Non-CC licenses have to undergo the ShareAlike compatibility process to be officially designated as a BY-SA Compatible License by CC. In either case, if someone applies a compatible license to an adaptation, both the original BY-SA license and the compatible license apply to the adaptation. However, downstream users of the adaptation may choose to look ‘’’only at the compatible license’’’ (that is, the last license applied) to determine what their attribution and ShareAlike obligations are ‘’’under both licenses’’’ if they reuse the work. <br />
<br />
'''What does one-way or two-way compatibility mean?'''<br />
<br />
One-way compatibility means that you may adapt work under one license (X) and apply a second license (Y), but you may not adapt work under the Y license and apply the X license. For example, CC BY is one-way compatible with BY-SA. You may adapt a BY work and apply BY-SA, but you may not adapt a BY-SA work and apply BY. <br />
<br />
Two-way compatibility means that you may adapt work under one license (X) and apply a second license (Y), or vice versa. <br />
<br />
For ShareAlike compatibility, a license listed as a ShareAlike Compatible License on the [https://creativecommons.org/compatiblelicenses compatible licenses page] is two-way compatible unless otherwise noted. <br />
<br />
'''What licenses are compatible with BY-SA?'''<br />
<br />
Different versions of BY-SA have [https://wiki.creativecommons.org/License_Versions#Compatibility_mechanism_in_BY-SA_licenses different compatibility mechanisms]. Each version is addressed below.<br />
<br />
:*For BY-SA 4.0, all future versions of BY-SA and all ports of BY-SA 4.0 or later are automatically compatible, as well as licenses explicitly deemed compatible pursuant to the ShareAlike compatibility process<br />
<br />
:*For BY-SA 3.0, all future versions of BY-SA and all ports of BY-SA 3.0 or later are automatically compatible, as well as licenses explicitly deemed compatible pursuant to the ShareAlike compatibility process<br />
<br />
:*For BY-SA 2.0, all future versions of BY-SA and all ports of BY-SA 2.0 or later are automatically compatible<br />
<br />
:*For BY-SA 1.0, only BY-SA 1.0 is compatible. <br />
<br />
'''Why did CC choose the Free Art License to be the first BY-SA Compatible License?'''<br />
<br />
Drafted in 2000, the Free Art License was one of the original copyleft licenses designed for content, not code. The [http://artlibre.org/licence/lal/en/ latest version] (1.3) was published in 2007 with an eye toward compatibility with CC licenses. The FAL 1.3 is very similar to BY-SA in spirit and substance, and raises no significant obstacles to compatibility. For a detailed explanation of the policy decisions involved in the compatibility determination, see [https://wiki.creativecommons.org/ShareAlike_compatibility:_FAL here]. <br />
<br />
'''Why did CC decide to pursue compatibility with a software license (GPLv3)?'''<br />
<br />
In some niche areas such as gaming, content is increasingly blended with code in ways that make it impossible for downstream users to differentiate the two. Developers in these fields were sometimes abstaining from integrating BY-SA content into GPL-licensed software projects because of potential conflict between the two copyleft licenses. This obstacle to reuse and remix of BY-SA content into projects published under a license so similar in spirit and substance was at the heart of the problem the compatibility mechanism in BY-SA was designed to solve. [Note to Sarah, do we have a link to any posts that Chris or Jonathan P. did that would be useful to reference here?]<br />
<br />
Together with the Free Software Foundation, CC decided to pursue a limited form of compatibility to address the problem. Because the GPLv3 is designed for software and CC discourages use of its licenses for software, there are [[ShareAlike_compatibility:_GPLv3|special considerations]] for those seeking to take advantage of this compatibility mechanism. <br />
<br />
===Example compatibility scenarios===<br />
<br />
:'''BY-SA 4.0 story is adapted into a screenplay and FAL 1.3 is applied'''<br />
:*both licenses apply, but reusers of the screenplay can attribute both authors and ShareAlike according to FAL terms<br />
<br />
:'''FAL 1.3 image is adapted and BY-SA 4.0 is applied''' <br />
:*only BY-SA 4.0 applies to the adaptation; reusers of the BY-SA adaptation may look only at the terms of BY-SA 4.0 to determine their obligations<br />
<br />
:'''BY-SA 3.0 song is synched with your original video and BY-SA 4.0 is applied'''<br />
:*both licenses apply, and reusers of the video must comply with the terms of both versions to the extent they differ [note: this is unlikely to have much practical significance; see [https://wiki.creativecommons.org/License_Versions here] for details on how the license versions differ]<br />
<br />
:'''BY-SA 4.0 assets are adapted into GPL game and GPLv3 is applied'''<br />
:*both licenses apply, but reusers of the GPL game can attribute and ShareAlike according to the GPL terms</div>CCID-diane petershttps://wiki.creativecommons.org/index.php?title=ShareAlike_compatibility&diff=113914ShareAlike compatibility2015-05-28T14:15:37Z<p>CCID-diane peters: /* FAQs about ShareAlike compatibility */</p>
<hr />
<div>==FAQs about ShareAlike compatibility==<br />
<br />
'''What is ShareAlike compatibility and why is it important?'''<br />
<br />
The ShareAlike licenses are designed to ensure that the freedoms associated with a licensed work survive as the work is adapted by others and that those freedoms attach to adaptations of the work as well. There are other copyleft licenses designed for this same purpose, but unfortunately, the works licensed under these other licenses are not compatible with works licensed under BY-SA. Creative Commons created the [https://wiki.creativecommons.org/ShareAlike_compatibility_criteria ShareAlike compatibility process] as a means to solving this problem. The process allows CC to evaluate other similar copyleft licenses to determine if they are similar enough to BY-SA to meet licensor expectations and hence be deemed compatible. BY-SA Compatible Licenses are listed [https://creativecommons.org/compatiblelicenses here]. <br />
<br />
'''How does ShareAlike compatibility work?'''<br />
<br />
Once a license is deemed compatible with BY-SA, anyone adapting BY-SA works can apply that license to their own contributions to the adaptation. With version 4.0, future versions of BY-SA are automatically compatible. Non-CC licenses have to undergo the ShareAlike compatibility process to be officially designated as a BY-SA Compatible License by CC. In either case, if someone applies a compatible license to an adaptation, both the original BY-SA license and the compatible license apply to the adaptation. However, downstream users of the adaptation may choose to look ‘’’only at the compatible license’’’ (that is, the last license applied) to determine what their attribution and ShareAlike obligations are ‘’’under both licenses’’’ if they reuse the work. <br />
<br />
'''What does one-way or two-way compatibility mean?'''<br />
<br />
One-way compatibility means that you may adapt work under one license (X) and apply a second license (Y), but you may not adapt work under the Y license and apply the X license. For example, CC BY is one-way compatible with BY-SA. You may adapt a BY work and apply BY-SA, but you may not adapt a BY-SA work and apply BY. <br />
<br />
Two-way compatibility means that you may adapt work under one license (X) and apply a second license (Y), or vice versa. <br />
<br />
For ShareAlike compatibility, a license listed as a ShareAlike Compatible License on the [https://creativecommons.org/compatiblelicenses compatible licenses page] is two-way compatible unless otherwise noted. <br />
<br />
'''What licenses are compatible with BY-SA?'''<br />
<br />
Different versions of BY-SA have [https://wiki.creativecommons.org/License_Versions#Compatibility_mechanism_in_BY-SA_licenses different compatibility mechanisms]. Each version is addressed below.<br />
<br />
:*For BY-SA 4.0, all future versions of BY-SA and all ports of BY-SA 4.0 or later are automatically compatible, as well as licenses explicitly deemed compatible pursuant to the ShareAlike compatibility process<br />
<br />
:*For BY-SA 3.0, all future versions of BY-SA and all ports of BY-SA 3.0 or later are automatically compatible, as well as licenses explicitly deemed compatible pursuant to the ShareAlike compatibility process<br />
<br />
:*For BY-SA 2.0, all future versions of BY-SA and all ports of BY-SA 2.0 or later are automatically compatible<br />
<br />
:*For BY-SA 1.0, only BY-SA 1.0 is compatible. <br />
<br />
'''Why did CC choose the Free Art License to be the first BY-SA Compatible License?'''<br />
<br />
Drafted in 2000, the Free Art License was one of the original copyleft licenses designed for content, not code. The [http://artlibre.org/licence/lal/en/ latest version] (1.3) was published in 2007 with an eye toward compatibility with CC licenses. The FAL 1.3 is very similar to BY-SA in spirit and substance, and raises no significant obstacles to compatibility. For a detailed explanation of the policy decisions involved in the compatibility determination, see [https://wiki.creativecommons.org/ShareAlike_compatibility:_FAL here]. <br />
<br />
'''Why did CC decide to pursue compatibility with a software license (GPLv3)?'''<br />
<br />
In some niche areas such as gaming, content is increasingly blended with code in ways that make it impossible for downstream users to differentiate the two. Developers in these fields were sometimes abstaining from integrating BY-SA content into GPL-licensed software projects because of potential conflict between the two copyleft licenses. This obstacle to reuse and remix of BY-SA content into projects published under a license so similar in spirit and substance was at the heart of the problem the compatibility mechanism in BY-SA was designed to solve. <br />
<br />
Together with the Free Software Foundation, CC decided to pursue a limited form of compatibility to address the problem. Because the GPLv3 is designed for software and CC discourages use of its licenses for software, there are [[ShareAlike_compatibility:_GPLv3|special considerations]] for those seeking to take advantage of this compatibility mechanism. <br />
<br />
===Example compatibility scenarios===<br />
<br />
:'''BY-SA 4.0 story is adapted into a screenplay and FAL 1.3 is applied'''<br />
:*both licenses apply, but reusers of the screenplay can attribute both authors and ShareAlike according to FAL terms<br />
<br />
:'''FAL 1.3 image is adapted and BY-SA 4.0 is applied''' <br />
:*only BY-SA 4.0 applies to the adaptation; reusers of the BY-SA adaptation may look only at the terms of BY-SA 4.0 to determine their obligations<br />
<br />
:'''BY-SA 3.0 song is synched with your original video and BY-SA 4.0 is applied'''<br />
:*both licenses apply, and reusers of the video must comply with the terms of both versions to the extent they differ [note: this is unlikely to have much practical significance; see [https://wiki.creativecommons.org/License_Versions here] for details on how the license versions differ]<br />
<br />
:'''BY-SA 4.0 assets are adapted into GPL game and GPLv3 is applied'''<br />
:*both licenses apply, but reusers of the GPL game can attribute and ShareAlike according to the GPL terms</div>CCID-diane petershttps://wiki.creativecommons.org/index.php?title=Hackspace&diff=113659Hackspace2015-03-28T11:20:06Z<p>CCID-diane peters: /* The List */</p>
<hr />
<div>__NOTOC__<br />
<br />
Welcome to the CC Hackspace! <br />
<br />
Current projects at CC and ideas for future projects:<br />
<br />
* The List powered by Creative Commons<br />
* CC Search<br />
* CCID<br />
* New CC website<br />
<br />
<br />
== The List Powered by Creative Commons ==<br />
<br />
The List is a new mobile application from Creative Commons. The List enables people to contribute to the commons by taking photographs of interesting things from a list of images put together by Creative Commons and affliiated organizations known as List Makers. The app works on both Android and the mobile web. <br />
<br />
All of the resulting images will be released onto sites such as the Internet Archive under CC-BY 4.0. All of our code is under the GNU Affero GPL v3 or later.<br />
<br />
* [https://github.com/creativecommons/list The List at GitHub]<br />
* [https://github.com/creativecommons/list/issues Open issues in The List]<br />
* [https://github.com/creativecommons/list/tree/master/webapp Install The List web app on your laptop]<br />
* [https://projects.invisionapp.com/share/C71IOF1V8#/screens Prototype screens for the Android app]<br />
<br />
== CC Search ==<br />
<br />
CC Search (codename: Garmonbozia) is a meta-search engine from CC. We search Flickr, Internet Archive and more and provide a simple, flat set of results that works on any browser and provides a simple, clean way to search by media type and license.<br />
<br />
All of our code is under the GNU Affero GPL v3 or later.<br />
<br />
* [https://github.com/creativecommons/garmonbozia Check out the code]<br />
* [https://github.com/creativecommons/garmonbozia/issues Open issues for CC Search]<br />
<br />
=== Bootstrapping The List webapp and CC Search ===<br />
<br />
Both CC search and The List are based on GNU FM. They require PHP 5.3, MySQL or MariaDB and a web server (Apache, typically... but others will probably be okay) plus php-curl, php-adodb, php-gd and php-smarty. If you're developing on GNU/Linux, you can usually get these from your package manager. On OS X, you'll have most luck with [http://brew.sh/ Homebrew].<br />
<br />
You may also need to symlink or alter the path in templating.php to your Smarty install. <br />
<br />
Ping mattl on #creativecommons-dev or write to [http://lists.ibiblio.org/mailman/listinfo/cc-devel cc-devel] with ideas.<br />
<br />
=== New CC website ===<br />
<br />
* https://github.com/creativecommons/www2015<br />
<br />
The site is a Jekyll site.<br />
<br />
==== Other things ====<br />
<br />
* CC is developing a free software hacker-friendly CLA for people who want to contribute to these projects.</div>CCID-diane petershttps://wiki.creativecommons.org/index.php?title=Affiliate_logo_guidelines&diff=110212Affiliate logo guidelines2015-02-25T21:39:51Z<p>CCID-diane peters: /* Affiliate Logo Guidelines */</p>
<hr />
<div>==Affiliate logo guidelines==<br />
<br />
Affiliates may use the CC name and logo in their own affiliate team logo provided they first obtain approval of the resulting logo from CC HQ. Our goals are to make affiliate logos recognizably related to Creative Commons, yet sufficiently distinct to avoid any confusion that the logo represents CC HQ, and ensure that only high quality logos are associated with CC’s activities. <br />
<br />
CC requires affiliate teams to submit proposed logos to HQ for approval. If approved, CC will prepare a standard trademark agreement granting the affiliate formal permission to use the CC trademark in their logo. In connection with our review, we may ask affiliate teams to make adjustments to the proposed logos before approval is given.<br />
<br />
To make the process more efficient, CC provides the following guidelines to help teams as they develop their logos.<br />
<br />
: Affiliates may incorporate the full CC corporate logo or the CC in a circle logo in the original, unmodified form made available [http://creativecommons.org/about/downloads on our website]. Note that CC does allow changes to the colors of the CC logos consistent with the parameters described in our [https://creativecommons.org/policies Trademark Policy]. <br />
<br />
: No text or design should touch or overlay any part of the CC logo.<br />
<br />
: The jurisdiction name or other jurisdiction identifier should be approximately as prominent as (but not substantially more prominent than) the CC logo. <br />
<br />
Please submit requests for logo approvals to legal@creativecommons.org (with a copy to your regional coordinator(s)), together with a sample of the proposed logo. Affiliates are also encouraged to review the CC [https://wiki.creativecommons.org/Merchandising Merchandising Policy], which contains information about how approved logos may be used in connection with swag and other merchandise.<br />
<br />
==Sample logos [TK]==<br />
<br />
Published: February 25, 2015</div>CCID-diane petershttps://wiki.creativecommons.org/index.php?title=Affiliate_logo_guidelines&diff=110211Affiliate logo guidelines2015-02-25T21:00:06Z<p>CCID-diane peters: </p>
<hr />
<div>==Affiliate Logo Guidelines==<br />
<br />
Affiliates may use the CC name and logo in their own affiliate team logo provided they first obtain approval of the resulting logo from CC HQ. Our goals are to make affiliate logos recognizably related to Creative Commons, yet sufficiently distinct to avoid any confusion that the logo represents CC HQ, and ensure that only high quality logos are associated with CC’s activities. <br />
<br />
CC requires affiliate teams to submit proposed logos to HQ for approval. If approved, CC will prepare a standard trademark agreement granting the affiliate formal permission to use the CC trademark in their logo. In connection with our review, we may ask affiliate teams to make adjustments to the proposed logos before approval is given.<br />
<br />
To make the process more efficient, CC provides the following guidelines to help teams as they develop their logos.<br />
<br />
: Affiliates may incorporate the full CC corporate logo or the CC in a circle logo in the original, unmodified form made available [http://creativecommons.org/about/downloads on our website]. Note that CC does allow changes to the colors of the CC logos consistent with the parameters described in our [https://creativecommons.org/policies Trademark Policy]. <br />
<br />
: No text or design should touch or overlay any part of the CC logo.<br />
<br />
: The jurisdiction name or other jurisdiction identifier should be approximately as prominent as (but not substantially more prominent than) the CC logo. <br />
<br />
Please submit requests for logo approvals to legal@creativecommons.org (with a copy to your regional coordinator(s)), together with a sample of the proposed logo. Affiliates are also encouraged to review the CC [https://wiki.creativecommons.org/Merchandising Merchandising Policy], which contains information about how approved logos may be used in connection with swag and other merchandise.<br />
<br />
==Sample logos [TK]==<br />
<br />
Published: February 25, 2015</div>CCID-diane petershttps://wiki.creativecommons.org/index.php?title=Affiliate_logo_guidelines&diff=110210Affiliate logo guidelines2015-02-25T20:59:02Z<p>CCID-diane peters: Created page with "Creative Commons Affiliate Logo Guidelines Affiliates may use the CC name and logo in their own affiliate team logo provided they first obtain approval of the resulting logo..."</p>
<hr />
<div>Creative Commons<br />
Affiliate Logo Guidelines<br />
<br />
Affiliates may use the CC name and logo in their own affiliate team logo provided they first obtain approval of the resulting logo from CC HQ. Our goals are to make affiliate logos recognizably related to Creative Commons, yet sufficiently distinct to avoid any confusion that the logo represents CC HQ, and ensure that only high quality logos are associated with CC’s activities. <br />
<br />
CC requires affiliate teams to submit proposed logos to HQ for approval. If approved, CC will prepare a standard trademark agreement granting the affiliate formal permission to use the CC trademark in their logo. In connection with our review, we may ask affiliate teams to make adjustments to the proposed logos before approval is given.<br />
<br />
To make the process more efficient, CC provides the following guidelines to help teams as they develop their logos.<br />
<br />
: Affiliates may incorporate the full CC corporate logo or the CC in a circle logo in the original, unmodified form made available [http://creativecommons.org/about/downloads on our website]. Note that CC does allow changes to the colors of the CC logos consistent with the parameters described in our [https://creativecommons.org/policies Trademark Policy]. <br />
<br />
: No text or design should touch or overlay any part of the CC logo.<br />
<br />
: The jurisdiction name or other jurisdiction identifier should be approximately as prominent as (but not substantially more prominent than) the CC logo. <br />
<br />
Please submit requests for logo approvals to legal@creativecommons.org (with a copy to your regional coordinator(s)), together with a sample of the proposed logo. Affiliates are also encouraged to review the CC [https://wiki.creativecommons.org/Merchandising Merchandising Policy], which contains information about how approved logos may be used in connection with swag and other merchandise.<br />
<br />
[Sample logos TK]<br />
<br />
Published: February 25, 2015</div>CCID-diane petershttps://wiki.creativecommons.org/index.php?title=Updated_Policies_Page&diff=107397Updated Policies Page2015-01-27T15:15:48Z<p>CCID-diane peters: /* DRAFT: Full text of proposed policies page below */</p>
<hr />
<div>This page features a '''DRAFT''' revision of the policies page for the CC websites. Once approved, these policies will replace the [http://creativecommons.org/policies current policies page]. Please note that when the changes to this page go live, appropriate links will be inserted and exemplars of the relevant marks will be inserted as indicated.<br />
<br />
===Summary of changes from the existing policies:===<br />
# Added brief explanation about trademarks and the purposes they serve, for context.<br />
# Added permission in advance to change colors of the double-c logo and its background. Under our prior policy, users did not have explicit permission to change those. It became a frequent ask and we're comfortable granting this permission in advance.<br />
# Clarity that permission isn't needed for referential use. We receive a fair number of inquiries about whether permission is needed to refer to Creative Commons in a book or article or blog post. That's all perfectly fine of course, and couldn't be controlled via trademark in any event.<br />
# Improved language re prohibition on using our logos with modifications of our licenses or legal tools or deeds, whether directly in the text or indirectly through terms of service. Cross reference is made to our expanded explanation and our policy [https://wiki.creativecommons.org/Modifying_the_CC_licenses here], which is already posted.<br />
# Clarity about use of our legacy marks (for retired tools) -- that those remain subject to the policy even if retired, because works to which those have been applied remain under those terms.<br />
<br />
===DRAFT: Full text of proposed policies page below===<br />
<br />
'''Policies'''<br />
<br />
Creative Commons maintains and publishes policies that apply to the use of our websites, content and software that we publish, our trademarks, and our affiliates. Note that some of these policies are maintained on other website pages but can be viewed by clicking on the relevant link below.<br />
<br />
*Privacy Policy<br />
*Website Terms of Use<br />
*Copyright Licensing Policy for Content and Software Code<br />
*Creative Commons Trademark Policy<br />
*Copyright Infringement Notification Policy<br />
*Affiliate Policies (see Agreements and Policies)<br />
<br />
'''Copyright Licensing Policy for Content and Software Code'''<br />
<br />
Other than the Creative Commons trademarks (licensed subject to the Trademark Policy below) and the text of Creative Commons legal tools and human-readable Commons deeds (dedicated to the public domain as specified below), all content on this site is licensed under the Creative Commons Attribution 4.0 International license unless otherwise marked.<br />
<br />
:'''Software:''' All of the software code we create is free software. Please check our code repository for the specific license that applies to software code you wish to use.<br />
<br />
:'''Legal text (we call this legal code) and Commons deeds:''' Creative Commons makes the legal code of its licenses and the CC0 Public Domain Dedication available under the CC0 Public Domain Dedication. CC also makes the Commons deeds associated with its licenses, the CC0 Public Domain Dedication, and the Public Domain Mark available under the CC0 Public Domain Dedication. This allows anyone to reuse those texts for any purpose; however, CC reserves fully and unconditionally all trademark and branding rights associated with the licenses, the CC0 Public Domain Dedication, and the Commons deeds. See the Trademark Policy below for more detail.<br />
<br />
'''Creative Commons Trademark Policy'''<br />
<br />
Trademarks are words, graphic designs, or other indicia that identify the source of a product or service. Creative Commons uses a variety of trademarks. Some Creative Commons trademarks serve the purpose of (i) communicating the type of legal tool chosen by the rights holder and/or (ii) indicating that the creator has applied a Creative Commons license to her work. Our registered trademarks and other trademarks include CREATIVE COMMONS (regardless of stylization, capitalization, translation, or other presentation), CC (including the CC in a circle logo (the “CC Logo”) and CC standing alone), CC+ (within a circle or standing alone), CC0, all of the Creative Commons license and public domain buttons and icons, and any combination of the foregoing, whether integrated into a larger whole or standing alone.<br />
<br />
You are authorized to use our trademarks subject to this Trademark Policy, and only on the further condition that you download images of the trademarks directly from our website. You are not authorized to use any modified versions of our trademarks, except that you may use a different color for the CC logo and its background so long as the two colors chosen have a contrast ratio of at least 3:1.<br />
<br />
Creative Commons retains the right to revoke any trademark license for any reason or for no specified reason. Creative Commons is particularly likely to revoke a license if, in its sole discretion, it finds that your use of the trademark is likely to bring disrepute to Creative Commons or any of its trademarks, or confuses the public.<br />
For the avoidance of doubt, you do not need our permission to use our corporate logo for referential use (e.g., to refer to Creative Commons as an organization), provided that such use does not imply endorsement by or association with Creative Commons.<br />
<br />
:'''Modification of CC Licenses:''' To prevent confusion and maintain consistency, you are not allowed to use CREATIVE COMMONS, CC, the CC Logo, or any other Creative Commons trademarks with modified versions of any of our legal tools or Commons deeds, including modifications that do not modify the legal code directly but that further restrict or condition the rights granted by the particular legal tool. These modifications are often contained in a website’s terms of use, and where they are present you may not suggest that you are offering works under a Creative Commons legal tool. See this page for more information.<br />
<br />
:'''Creative Commons Public Copyright License Marks:''' Creative Commons licenses the use of its public copyright license marks (some of which are shown immediately to the right), which include the CC Logo, on the conditions that you use the marks solely to describe the Creative Commons license that applies to a particular work and include the URI or a hyperlink to the corresponding Commons deed on the Creative Commons server.<br />
<br />
:'''Public Domain Dedication Marks:''' Creative Commons licenses the use of its public domain dedication marks (one of which is shown immediately to the right), on the conditions that you use the mark solely to describe that the CC0 Public Domain Dedication applies to a particular work and include the URI or a hyperlink to the Commons deed on the Creative Commons server.<br />
<br />
:'''Public Domain Mark:''' Creative Commons licenses the use of its trademarked Public Domain Mark badge (shown immediately to the right) on the conditions that you use the mark solely to describe that the Creative Commons Public Domain Mark applies to a particular work and include the URI or hyperlink to the Public Domain Mark on the Creative Commons server.<br />
<br />
:'''Creative Commons License Buttons and Icons:''' Creative Commons licenses the use of its button marks that describe a particular legal tool and its icon marks that describe a key license element, such as BY, NC, ND, and SA, on the conditions that you use the mark solely to describe the Creative Commons legal tool that applies to a particular work and include the URI or hyperlink to the relevant Commons deed on the Creative Commons server.<br />
<br />
:'''Legacy marks:''' Creative Commons has retired some of its prior legal tools, all of which have associated trademarks, such as the Developing Nations License, the Sampling License, and Founder’s Copyright. Although these tools have been retired and are no longer recommended for use, they are still legally effective as to works to which they are applied. Therefore, those trademarks may only be used under the terms and conditions of this Trademark Policy. Creative Commons licenses the use of its legacy marks on the conditions that you use the mark solely to describe the Creative Commons legal tool that applies to the particular work and include the URI or hyperlink to the relevant Commons deed on the Creative Commons server. Note that legacy marks are not available for download on our website.<br />
<br />
:'''Offline works:''' When using one of our Public Domain Dedication Marks, the Public Domain Mark, or our Creative Commons License Buttons and Icons in an offline environment such as print media, the requirement that you include a hyperlink to the relevant Commons deed (or the Public Domain Mark if relevant) does not apply. Instead, identify the URI for the relevant page on our server in a place reasonably designed to be found by others seeking to reuse the work, such as in a copyright notice. <br />
<br />
:'''Additional permissions:''' In addition to the permissions granted in advance to the public as set forth above, Creative Commons may agree to grant additional permissions upon request. Please submit any such request to legal@creativecommons.org. Except as specifically stated above or otherwise set forth in a written agreement with you, no additional permissions are granted.<br />
<br />
'''Copyright Infringement Notification Policy'''<br />
<br />
If you have reason to believe that any material or activity on a site controlled or operated by Creative Commons (such as creativecommons.org, wiki.creativecommons.org, or open4us.org) is infringing the rights owned by you or someone else for whom you have authority to act, please follow our DMCA Notice & Takedown Procedure.<br />
<br />
PLEASE NOTE: Creative Commons provides public copyright licenses and legal tools that anyone may use. We do not, however, control the use of Creative Commons licenses and legal tools, or have knowledge of whether the use of our licenses or legal tools is authorized by the copyright owner. Additionally, Creative Commons has no control over third-party websites, or over content belonging to persons or organizations other than Creative Commons. Any content hosted on a third-party website is the responsibility of those sites, and not of Creative Commons, even if the content bears a Creative Commons license or is otherwise marked with one of CC’s logos or other trademarks. If you are the copyright owner of content hosted on a third party site in an unauthorized manner, please contact the administrator of that website directly to have the content removed.</div>CCID-diane petershttps://wiki.creativecommons.org/index.php?title=Updated_Policies_Page&diff=107396Updated Policies Page2015-01-27T15:11:12Z<p>CCID-diane peters: /* DRAFT: Full text of proposed policies page below */</p>
<hr />
<div>This page features a '''DRAFT''' revision of the policies page for the CC websites. Once approved, these policies will replace the [http://creativecommons.org/policies current policies page]. Please note that when the changes to this page go live, appropriate links will be inserted and exemplars of the relevant marks will be inserted as indicated.<br />
<br />
===Summary of changes from the existing policies:===<br />
# Added brief explanation about trademarks and the purposes they serve, for context.<br />
# Added permission in advance to change colors of the double-c logo and its background. Under our prior policy, users did not have explicit permission to change those. It became a frequent ask and we're comfortable granting this permission in advance.<br />
# Clarity that permission isn't needed for referential use. We receive a fair number of inquiries about whether permission is needed to refer to Creative Commons in a book or article or blog post. That's all perfectly fine of course, and couldn't be controlled via trademark in any event.<br />
# Improved language re prohibition on using our logos with modifications of our licenses or legal tools or deeds, whether directly in the text or indirectly through terms of service. Cross reference is made to our expanded explanation and our policy [https://wiki.creativecommons.org/Modifying_the_CC_licenses here], which is already posted.<br />
# Clarity about use of our legacy marks (for retired tools) -- that those remain subject to the policy even if retired, because works to which those have been applied remain under those terms.<br />
<br />
===DRAFT: Full text of proposed policies page below===<br />
<br />
'''Policies'''<br />
<br />
Creative Commons maintains and publishes policies that apply to the use of our websites, content and software that we publish, our trademarks, and our affiliates. Note that some of these policies are maintained on other website pages but can be viewed by clicking on the relevant link below.<br />
<br />
*Privacy Policy<br />
*Website Terms of Use<br />
*Copyright Licensing Policy for Content and Software Code<br />
*Creative Commons Trademark Policy<br />
*Copyright Infringement Notification Policy<br />
*Affiliate Policies (see Agreements and Policies)<br />
<br />
'''Copyright Licensing Policy for Content and Software Code'''<br />
<br />
Other than the Creative Commons trademarks (licensed subject to the Trademark Policy below) and the text of Creative Commons legal tools and human-readable Commons deeds (dedicated to the public domain as specified below), all content on this site is licensed under the Creative Commons Attribution 4.0 International license unless otherwise marked.<br />
<br />
:'''Software:''' All of the software code we create is free software. Please check our code repository for the specific license that applies to software code you wish to use.<br />
<br />
:'''Legal text (we call this legal code) and Commons deeds:''' Creative Commons makes the legal code of its licenses and the CC0 Public Domain Dedication available under the CC0 Public Domain Dedication. CC also makes the Commons deeds associated with its licenses, the CC0 Public Domain Dedication, and the Public Domain Mark available under the CC0 Public Domain Dedication. This allows anyone to reuse those texts for any purpose; however, CC reserves fully and unconditionally all trademark and branding rights associated with the licenses, the CC0 Public Domain Dedication, and the Commons deeds. See the Trademark Policy below for more detail.<br />
<br />
'''Creative Commons Trademark Policy'''<br />
<br />
Trademarks are words, graphic designs, or other indicia that identify the source of a product or service. Creative Commons uses a variety of trademarks. Some Creative Commons trademarks serve the purpose of (i) communicating the type of legal tool chosen by the rights holder and/or (ii) indicating that the creator has applied a Creative Commons license to her work. Our registered trademarks and other trademarks include CREATIVE COMMONS (regardless of stylization, capitalization, translation, or other presentation), CC (including the CC in a circle logo (the “CC Logo”) and CC standing alone), CC+ (within a circle or standing alone), CC0, all of the Creative Commons license and public domain buttons and icons, and any combination of the foregoing, whether integrated into a larger whole or standing alone.<br />
<br />
You are authorized to use our trademarks subject to this Trademark Policy, and only on the further condition that you download images of the trademarks directly from our website. You are not authorized to use any modified versions of our trademarks, except that you may use a different color for the CC logo and its background so long as the two colors chosen have a contrast ratio of at least 3:1.<br />
<br />
Creative Commons retains the right to revoke any trademark license for any reason or for no specified reason. Creative Commons is particularly likely to revoke a license if, in its sole discretion, it finds that your use of the trademark is likely to bring disrepute to Creative Commons or any of its trademarks, or confuses the public.<br />
For the avoidance of doubt, you do not need our permission to use our corporate logo for referential use (e.g., to refer to Creative Commons as an organization), provided that such use does not imply endorsement by or association with Creative Commons.<br />
<br />
:'''Modification of CC Licenses:''' To prevent confusion and maintain consistency, you are not allowed to use CREATIVE COMMONS, CC, the CC Logo, or any other Creative Commons trademarks with modified versions of any of our legal tools or Commons deeds, including modifications that do not modify the legal code directly but that further restrict or condition the rights granted by the particular legal tool. These modifications are often contained in a website’s terms of use, and where they are present you may not suggest that you are offering works under a Creative Commons legal tool. See this page for more information.<br />
<br />
:'''Creative Commons Public Copyright License Marks:''' Creative Commons licenses the use of its public copyright license marks (some of which are shown immediately to the right), which include the CC Logo, on the conditions that you use the marks solely to describe the Creative Commons license that applies to a particular work and include the URI or a hyperlink to the corresponding Commons deed on the Creative Commons server.<br />
<br />
:'''Public Domain Dedication Marks:''' Creative Commons licenses the use of its public domain dedication marks (one of which is shown immediately to the right), on the conditions that you use the mark solely to describe that the CC0 Public Domain Dedication applies to a particular work and include the URI or a hyperlink to the Commons deed on the Creative Commons server.<br />
<br />
:'''Public Domain Mark:''' Creative Commons licenses the use of its trademarked Public Domain Mark badge (shown immediately to the right) on the conditions that you use the mark solely to describe that the Creative Commons Public Domain Mark applies to a particular work and include the URI or hyperlink to the Public Domain Mark on the Creative Commons server.<br />
<br />
:'''Creative Commons License Buttons and Icons:''' Creative Commons licenses the use of its button marks that describe a particular legal tool and its icon marks that describe a key license element, such as BY, NC, ND, and SA, on the conditions that you use the mark solely to describe the Creative Commons legal tool that applies to a particular work and include the URI or hyperlink to the relevant Commons deed on the Creative Commons server.<br />
<br />
:'''Legacy marks:''' Creative Commons has retired some of its prior legal tools, all of which have associated trademarks, such as the Developing Nations License, the Sampling License, and Founder’s Copyright. Although these tools have been retired and are no longer recommended for use, they are still legally effective as to works to which they are applied. Therefore, those trademarks may only be used under the terms and conditions of this Trademark Policy. Creative Commons licenses the use of its legacy marks on the conditions that you use the mark solely to describe the Creative Commons legal tool that applies to the particular work and include the URI or hyperlink to the relevant Commons deed on the Creative Commons server. Note that legacy marks are not available for download on our website.<br />
<br />
:'''Additional permissions:''' In addition to the permissions granted in advance to the public as set forth above, Creative Commons may agree to grant additional permissions upon request. Please submit any such request to legal@creativecommons.org. Except as specifically stated above or otherwise set forth in a written agreement with you, no additional permissions are granted.<br />
<br />
:'''Offline works:'' When using one of our Public Domain Dedication Marks, the Public Domain Mark, or our Creative Commons License Buttons and Icons in an offline environment such as print media, the requirement that you include a hyperlink to the relevant Commons deed (or the Public Domain Mark if relevant) does not apply. Instead, identify the URI for the relevant page on our server in reasonable proximity to the trademark, such as in a copyright notice or other notice referring to the relevant legal tool. <br />
<br />
'''Copyright Infringement Notification Policy'''<br />
<br />
If you have reason to believe that any material or activity on a site controlled or operated by Creative Commons (such as creativecommons.org, wiki.creativecommons.org, or open4us.org) is infringing the rights owned by you or someone else for whom you have authority to act, please follow our DMCA Notice & Takedown Procedure.<br />
<br />
PLEASE NOTE: Creative Commons provides public copyright licenses and legal tools that anyone may use. We do not, however, control the use of Creative Commons licenses and legal tools, or have knowledge of whether the use of our licenses or legal tools is authorized by the copyright owner. Additionally, Creative Commons has no control over third-party websites, or over content belonging to persons or organizations other than Creative Commons. Any content hosted on a third-party website is the responsibility of those sites, and not of Creative Commons, even if the content bears a Creative Commons license or is otherwise marked with one of CC’s logos or other trademarks. If you are the copyright owner of content hosted on a third party site in an unauthorized manner, please contact the administrator of that website directly to have the content removed.</div>CCID-diane petershttps://wiki.creativecommons.org/index.php?title=Updated_Policies_Page&diff=107381Updated Policies Page2015-01-27T10:08:46Z<p>CCID-diane peters: /* DRAFT: Full text of proposed policies page below */</p>
<hr />
<div>This page features a '''DRAFT''' revision of the policies page for the CC websites. Once approved, these policies will replace the [http://creativecommons.org/policies current policies page]. Please note that when the changes to this page go live, appropriate links will be inserted and exemplars of the relevant marks will be inserted as indicated.<br />
<br />
===Summary of changes from the existing policies:===<br />
# Added brief explanation about trademarks and the purposes they serve, for context.<br />
# Added permission in advance to change colors of the double-c logo and its background. Under our prior policy, users did not have explicit permission to change those. It became a frequent ask and we're comfortable granting this permission in advance.<br />
# Clarity that permission isn't needed for referential use. We receive a fair number of inquiries about whether permission is needed to refer to Creative Commons in a book or article or blog post. That's all perfectly fine of course, and couldn't be controlled via trademark in any event.<br />
# Improved language re prohibition on using our logos with modifications of our licenses or legal tools or deeds, whether directly in the text or indirectly through terms of service. Cross reference is made to our expanded explanation and our policy [https://wiki.creativecommons.org/Modifying_the_CC_licenses here], which is already posted.<br />
# Clarity about use of our legacy marks (for retired tools) -- that those remain subject to the policy even if retired, because works to which those have been applied remain under those terms.<br />
<br />
===DRAFT: Full text of proposed policies page below===<br />
<br />
'''Policies'''<br />
<br />
Creative Commons maintains and publishes policies that apply to the use of our websites, content and software that we publish, our trademarks, and our affiliates. Note that some of these policies are maintained on other website pages but can be viewed by clicking on the relevant link below.<br />
<br />
*Privacy Policy<br />
*Website Terms of Use<br />
*Copyright Licensing Policy for Content and Software Code<br />
*Creative Commons Trademark Policy<br />
*Copyright Infringement Notification Policy<br />
*Affiliate Policies (see Agreements and Policies)<br />
<br />
'''Copyright Licensing Policy for Content and Software Code'''<br />
<br />
Other than the Creative Commons trademarks (licensed subject to the Trademark Policy below) and the text of Creative Commons legal tools and human-readable Commons deeds (dedicated to the public domain as specified below), all content on this site is licensed under the Creative Commons Attribution 4.0 International license unless otherwise marked.<br />
<br />
:'''Software:''' All of the software code we create is free software. Please check our code repository for the specific license that applies to software code you wish to use.<br />
<br />
:'''Legal text (we call this legal code) and Commons deeds:''' Creative Commons makes the legal code of its licenses and the CC0 Public Domain Dedication available under the CC0 Public Domain Dedication. CC also makes the Commons deeds associated with its licenses, the CC0 Public Domain Dedication, and the Public Domain Mark available under the CC0 Public Domain Dedication. This allows anyone to reuse those texts for any purpose; however, CC reserves fully and unconditionally all trademark and branding rights associated with the licenses, the CC0 Public Domain Dedication, and the Commons deeds. See the Trademark Policy below for more detail.<br />
<br />
'''Creative Commons Trademark Policy'''<br />
<br />
Trademarks are words, graphic designs, or other indicia that identify the source of a product or service. Creative Commons uses a variety of trademarks. Some Creative Commons trademarks serve the purpose of (i) communicating the type of legal tool chosen by the rights holder and/or (ii) indicating that the creator has applied a Creative Commons license to her work. Our registered trademarks and other trademarks include CREATIVE COMMONS (regardless of stylization, capitalization, translation, or other presentation), CC (including the CC in a circle logo (the “CC Logo”) and CC standing alone), CC+ (within a circle or standing alone), CC0, all of the Creative Commons license and public domain buttons and icons, and any combination of the foregoing, whether integrated into a larger whole or standing alone.<br />
<br />
You are authorized to use our trademarks subject to this Trademark Policy, and only on the further condition that you download images of the trademarks directly from our website. You are not authorized to use any modified versions of our trademarks, except that you may use a different color for the CC logo and its background so long as the two colors chosen have a contrast ratio of at least 3:1.<br />
<br />
Creative Commons retains the right to revoke any trademark license for any reason or for no specified reason. Creative Commons is particularly likely to revoke a license if, in its sole discretion, it finds that your use of the trademark is likely to bring disrepute to Creative Commons or any of its trademarks, or confuses the public.<br />
For the avoidance of doubt, you do not need our permission to use our corporate logo for referential use (e.g., to refer to Creative Commons as an organization), provided that such use does not imply endorsement by or association with Creative Commons.<br />
<br />
:'''Modification of CC Licenses:''' To prevent confusion and maintain consistency, you are not allowed to use CREATIVE COMMONS, CC, the CC Logo, or any other Creative Commons trademarks with modified versions of any of our legal tools or Commons deeds, including modifications that do not modify the legal code directly but that further restrict or condition the rights granted by the particular legal tool. These modifications are often contained in a website’s terms of use, and where they are present you may not suggest that you are offering works under a Creative Commons legal tool. See this page for more information.<br />
<br />
:'''Creative Commons Public Copyright License Marks:''' Creative Commons licenses the use of its public copyright license marks (some of which are shown immediately to the right), which include the CC Logo, on the conditions that you use the marks solely to describe the Creative Commons license that applies to a particular work and include the URI or a hyperlink to the corresponding Commons deed on the Creative Commons server.<br />
<br />
:'''Public Domain Dedication Marks:''' Creative Commons licenses the use of its public domain dedication marks (one of which is shown immediately to the right), on the conditions that you use the mark solely to describe that the CC0 Public Domain Dedication applies to a particular work and include the URI or a hyperlink to the Commons deed on the Creative Commons server.<br />
<br />
:'''Public Domain Mark:''' Creative Commons licenses the use of its trademarked Public Domain Mark badge (shown immediately to the right) on the conditions that you use the mark solely to describe that the Creative Commons Public Domain Mark applies to a particular work and include the URI or hyperlink to the Public Domain Mark on the Creative Commons server.<br />
<br />
:'''Creative Commons License Buttons and Icons:''' Creative Commons licenses the use of its button marks that describe a particular legal tool and its icon marks that describe a key license element, such as BY, NC, ND, and SA, on the conditions that you use the mark solely to describe the Creative Commons legal tool that applies to a particular work and include the URI or hyperlink to the relevant Commons deed on the Creative Commons server.<br />
<br />
:'''Legacy marks:''' Creative Commons has retired some of its prior legal tools, all of which have associated trademarks, such as the Developing Nations License, the Sampling License, and Founder’s Copyright. Although these tools have been retired and are no longer recommended for use, they are still legally effective as to works to which they are applied. Therefore, those trademarks may only be used under the terms and conditions of this Trademark Policy. Creative Commons licenses the use of its legacy marks on the conditions that you use the mark solely to describe the Creative Commons legal tool that applies to the particular work and include the URI or hyperlink to the relevant Commons deed on the Creative Commons server. Note that legacy marks are not available for download on our website.<br />
<br />
:'''Additional permissions:''' In addition to the permissions granted in advance to the public as set forth above, Creative Commons may agree to grant additional permissions upon request. Please submit any such request to legal@creativecommons.org. Except as specifically stated above or otherwise set forth in a written agreement with you, no additional permissions are granted.<br />
<br />
'''Copyright Infringement Notification Policy'''<br />
<br />
If you have reason to believe that any material or activity on a site controlled or operated by Creative Commons (such as creativecommons.org, wiki.creativecommons.org, or open4us.org) is infringing the rights owned by you or someone else for whom you have authority to act, please follow our DMCA Notice & Takedown Procedure.<br />
<br />
PLEASE NOTE: Creative Commons provides public copyright licenses and legal tools that anyone may use. We do not, however, control the use of Creative Commons licenses and legal tools, or have knowledge of whether the use of our licenses or legal tools is authorized by the copyright owner. Additionally, Creative Commons has no control over third-party websites, or over content belonging to persons or organizations other than Creative Commons. Any content hosted on a third-party website is the responsibility of those sites, and not of Creative Commons, even if the content bears a Creative Commons license or is otherwise marked with one of CC’s logos or other trademarks. If you are the copyright owner of content hosted on a third party site in an unauthorized manner, please contact the administrator of that website directly to have the content removed.</div>CCID-diane petershttps://wiki.creativecommons.org/index.php?title=Updated_Policies_Page&diff=107380Updated Policies Page2015-01-27T10:05:07Z<p>CCID-diane peters: /* DRAFT: Full text of proposed policies page below */</p>
<hr />
<div>This page features a '''DRAFT''' revision of the policies page for the CC websites. Once approved, these policies will replace the [http://creativecommons.org/policies current policies page]. Please note that when the changes to this page go live, appropriate links will be inserted and exemplars of the relevant marks will be inserted as indicated.<br />
<br />
===Summary of changes from the existing policies:===<br />
# Added brief explanation about trademarks and the purposes they serve, for context.<br />
# Added permission in advance to change colors of the double-c logo and its background. Under our prior policy, users did not have explicit permission to change those. It became a frequent ask and we're comfortable granting this permission in advance.<br />
# Clarity that permission isn't needed for referential use. We receive a fair number of inquiries about whether permission is needed to refer to Creative Commons in a book or article or blog post. That's all perfectly fine of course, and couldn't be controlled via trademark in any event.<br />
# Improved language re prohibition on using our logos with modifications of our licenses or legal tools or deeds, whether directly in the text or indirectly through terms of service. Cross reference is made to our expanded explanation and our policy [https://wiki.creativecommons.org/Modifying_the_CC_licenses here], which is already posted.<br />
# Clarity about use of our legacy marks (for retired tools) -- that those remain subject to the policy even if retired, because works to which those have been applied remain under those terms.<br />
<br />
===DRAFT: Full text of proposed policies page below===<br />
<br />
'''Policies'''<br />
<br />
Creative Commons maintains and publishes policies that apply to the use of our websites, content and software that we publish, our trademarks, and our affiliates. Note that some of these policies are maintained on other website pages but can be viewed by clicking on the relevant link below.<br />
<br />
*Privacy Policy<br />
*Website Terms of Use<br />
*Copyright Licensing Policy for Content and Software Code<br />
*Creative Commons Trademark Policy<br />
*Copyright Infringement Notification Policy<br />
*Affiliate Policies (see Agreements and Policies)<br />
<br />
'''Copyright Licensing Policy for Content and Software Code'''<br />
<br />
Other than the Creative Commons trademarks (licensed subject to the Trademark Policy below) and the text of Creative Commons legal tools and human-readable Commons deeds (dedicated to the public domain as specified below), all content on this site is licensed under the Creative Commons Attribution 4.0 International license unless otherwise marked.<br />
<br />
:'''Software:''' All of the software code we create is free software. Please check our code repository for the specific license that applies to software code you wish to use.<br />
<br />
:'''Legal text (we call this legal code) and Commons deeds:''' Creative Commons makes the legal code of its licenses and the CC0 Public Domain Dedication available under the CC0 Public Domain Dedication. CC also makes the Commons deeds associated with its licenses, the CC0 Public Domain Dedication, and the Public Domain Mark available under the CC0 Public Domain Dedication. This allows anyone to reuse those texts for any purpose; however, CC reserves fully and unconditionally all trademark and branding rights associated with the licenses, the CC0 Public Domain Dedication, and the Commons deeds. See the Trademark Policy below for more detail.<br />
<br />
'''Creative Commons Trademark Policy'''<br />
<br />
Trademarks are words, graphic designs, or other indicia that identify the source of a product or service. Creative Commons uses a variety of trademarks. Some Creative Commons trademarks serve the purpose of (i) communicating the type of legal tool chosen by the rights holder and/or (ii) indicating that the creator has applied a Creative Commons license to her work. Our registered trademarks and other trademarks include CREATIVE COMMONS (regardless of stylization, capitalization, translation, or other presentation), CC (including the CC in a circle logo (the “CC Logo”) and CC standing alone), CC+ (within a circle or standing alone), CC0, all of the Creative Commons license and public domain buttons and icons, and any combination of the foregoing, whether integrated into a larger whole or standing alone.<br />
<br />
You are authorized to use our trademarks subject to this Trademark Policy, and only on the further condition that you download images of the trademarks directly from our website. You are not authorized to use any modified versions of our trademarks, except that you may use a different color for the CC logo and its background so long as the two colors chosen have a contrast ratio of at least 3:1.<br />
<br />
Creative Commons retains the right to revoke any trademark license for any reason or for no specified reason. Creative Commons is particularly likely to revoke a license if, in its sole discretion, it finds that your use of the trademark is likely to bring disrepute to Creative Commons or any of its trademarks, or confuse the public.<br />
For the avoidance of doubt, you do not need our permission to use our corporate logo for referential use (e.g., to refer to Creative Commons as an organization), provided that such use does not imply endorsement by or association with Creative Commons.<br />
<br />
:'''Modification of CC Licenses:''' To prevent confusion and maintain consistency, you are not allowed to use CREATIVE COMMONS, CC, the CC Logo, or any other Creative Commons trademarks with modified versions of any of our legal tools or deeds, including modifications that do not modify the legal code directly but that further restrict or condition the rights granted by the particular legal tool. These modifications are often contained in a website’s terms of use, and where they are present you may not suggest that you are offering works under Creative Commons. See this page for more information.<br />
<br />
:'''Creative Commons Public Copyright License Marks:''' Creative Commons licenses the use of its public copyright license marks (some of which are shown immediately to the right), which include the CC Logo, on the conditions that you use the marks solely to describe the Creative Commons license that applies to a particular work and include the URI or a hyperlink to the corresponding Commons deed on the Creative Commons server.<br />
<br />
:'''Public Domain Dedication Marks:''' Creative Commons licenses the use of its public domain dedication marks (one of which is shown immediately to the right), on the conditions that you use the mark solely to describe that the CC0 Public Domain Dedication applies to a particular work and include the URI or a hyperlink to the Commons deed on the Creative Commons server.<br />
<br />
:'''Public Domain Mark:''' Creative Commons licenses the use of its trademarked Public Domain Mark badge (shown immediately to the right) on the conditions that you use the mark solely to describe that the Creative Commons Public Domain Mark applies to a particular work and include the URI or hyperlink to the Public Domain Mark on the Creative Commons server.<br />
<br />
:'''Creative Commons License Buttons and Icons:''' Creative Commons licenses the use of its button marks that describe a particular legal tool and its icon marks that describe a key license element, such as BY, NC, ND, and SA, on the conditions that you use the mark solely to describe the Creative Commons legal tool that applies to a particular work and include the URI or hyperlink to the relevant Commons deed on the Creative Commons server.<br />
<br />
:'''Legacy marks:''' Creative Commons has retired some of its prior legal tools, all of which have associated trademarks, such as the Developing Nations License, the Sampling License, and Founder’s Copyright. Although these tools have been retired and are no longer recommended for use, they are still legally effective as to works to which they are applied. Therefore, those trademarks may only be used under the terms and conditions of this Trademark Policy. Creative Commons licenses the use of its legacy marks on the conditions that you use the mark solely to describe the Creative Commons legal tool that applies to the particular work and include the URI or hyperlink to the relevant Commons deed on the Creative Commons server. Note that legacy marks are not available for download on our website.<br />
<br />
:'''Additional permissions:''' In addition to the permissions granted in advance to the public as set forth above, Creative Commons may agree to grant additional permissions upon request. Please submit any such request to legal@creativecommons.org. Except as specifically stated above or otherwise set forth in a written agreement with you, no additional permissions are granted.<br />
<br />
'''Copyright Infringement Notification Policy'''<br />
<br />
If you have reason to believe that any material or activity on a site controlled or operated by Creative Commons (such as creativecommons.org, wiki.creativecommons.org, or open4us.org) is infringing the rights owned by you or someone else for whom you have authority to act, please follow our DMCA Notice & Takedown Procedure.<br />
<br />
PLEASE NOTE: Creative Commons provides public copyright licenses and legal tools that anyone may use. We do not, however, control the use of Creative Commons licenses and legal tools, or have knowledge of whether the use of our licenses or legal tools is authorized by the copyright owner. Additionally, Creative Commons has no control over third-party websites, or over content belonging to persons or organizations other than Creative Commons. Any content hosted on a third-party website is the responsibility of those sites, and not of Creative Commons, even if the content bears a Creative Commons license or is otherwise marked with one of CC’s logos or other trademarks. If you are the copyright owner of content hosted on a third party site in an unauthorized manner, please contact the administrator of that website directly to have the content removed.</div>CCID-diane petershttps://wiki.creativecommons.org/index.php?title=Updated_Policies_Page&diff=107354Updated Policies Page2015-01-26T14:17:00Z<p>CCID-diane peters: /* DRAFT: Full text of proposed policies page below */</p>
<hr />
<div>This page features a '''DRAFT''' revision of the policies page for the CC websites. Once approved, these policies will replace the [http://creativecommons.org/policies current policies page]. Please note that when the changes to this page go live, appropriate links will be inserted and exemplars of the relevant marks will be inserted as indicated.<br />
<br />
===Summary of changes from the existing policies:===<br />
# Added brief explanation about trademarks and the purposes they serve, for context.<br />
# Added permission in advance to change colors of the double-c logo and its background. Under our prior policy, users did not have explicit permission to change those. It became a frequent ask and we're comfortable granting this permission in advance.<br />
# Clarity that permission isn't needed for referential use. We receive a fair number of inquiries about whether permission is needed to refer to Creative Commons in a book or article or blog post. That's all perfectly fine of course, and couldn't be controlled via trademark in any event.<br />
# Improved language re prohibition on using our logos with modifications of our licenses or legal tools or deeds, whether directly in the text or indirectly through terms of service. Cross reference is made to our expanded explanation and our policy [https://wiki.creativecommons.org/Modifying_the_CC_licenses here], which is already posted.<br />
# Clarity about use of our legacy marks (for retired tools) -- that those remain subject to the policy even if retired, because works to which those have been applied remain under those terms.<br />
<br />
===DRAFT: Full text of proposed policies page below===<br />
<br />
'''Policies'''<br />
<br />
Creative Commons maintains and publishes policies that apply to the use of our websites, content and software that we publish, our trademarks, and our affiliates. Note that some of these policies are maintained on other website pages but can be viewed by clicking on the relevant link below.<br />
<br />
*Privacy Policy<br />
*Website Terms of Use<br />
*Copyright Licensing Policy for Content and Software Code<br />
*Creative Commons Trademark Policy<br />
*Copyright Infringement Notification Policy<br />
*Affiliate Policies (see Agreements and Policies)<br />
<br />
'''Copyright Licensing Policy for Content and Software Code'''<br />
<br />
Other than the Creative Commons trademarks (licensed subject to the Trademark Policy below) and the text of Creative Commons legal tools and human-readable Commons deeds (dedicated to the public domain as specified below), all content on this site is licensed under the Creative Commons Attribution 4.0 International license unless otherwise marked.<br />
<br />
:'''Software:''' All of the software code we create is free software. Please check our code repository for the specific license that applies to software code you wish to use.<br />
<br />
:'''Legal text (we call this legal code) and Commons deeds:''' Creative Commons makes the legal code of its licenses and the CC0 Public Domain Dedication available under the CC0 Public Domain Dedication. CC also makes the Commons deeds associated with its licenses, the CC0 Public Domain Dedication, and the Public Domain Mark available under the CC0 Public Domain Dedication. This allows anyone to reuse those texts for any purpose; however, CC reserves fully and unconditionally all trademark and branding rights associated with the licenses, the CC0 Public Domain Dedication, and deeds. See the Trademark Policy below for more detail.<br />
<br />
'''Creative Commons Trademark Policy'''<br />
<br />
Trademarks are words, graphic designs, or other indicia that identify the source of a product or service. Creative Commons uses a variety of trademarks. Some Creative Commons trademarks serve the purpose of (i) communicating the type of legal tool chosen by the rights holder and/or (ii) indicating that the creator has applied a Creative Commons license to her work. Our registered trademarks and other trademarks include CREATIVE COMMONS (regardless of stylization, capitalization, translation, or other presentation), CC (including the CC in a circle logo (the “CC Logo”) and CC standing alone), CC+ (within a circle or standing alone), CC0, all of the Creative Commons license and public domain buttons and icons, and any combination of the foregoing, whether integrated into a larger whole or standing alone.<br />
<br />
You are authorized to use our trademarks subject to this Trademark Policy, and only on the further condition that you download images of the trademarks directly from our website. You are not authorized to use any modified versions of our trademarks, except that you may use a different color for the CC logo and its background so long as the two colors chosen have a contrast ratio of at least 3:1.<br />
<br />
Creative Commons retains the right to revoke any trademark license for any reason or for no specified reason. Creative Commons is particularly likely to revoke a license if, in its sole discretion, it finds that your use of the trademark is likely to bring disrepute to Creative Commons or any of its trademarks, or confuse the public.<br />
For the avoidance of doubt, you do not need our permission to use our corporate logo for referential use (e.g., to refer to Creative Commons as an organization), provided that such use does not imply endorsement by or association with Creative Commons.<br />
<br />
:'''Modification of CC Licenses:''' To prevent confusion and maintain consistency, you are not allowed to use CREATIVE COMMONS, CC, the CC Logo, or any other Creative Commons trademarks with modified versions of any of our legal tools or deeds, including modifications that do not modify the legal code directly but that further restrict or condition the rights granted by the particular legal tool. These modifications are often contained in a website’s terms of use, and where they are present you may not suggest that you are offering works under Creative Commons. See this page for more information.<br />
<br />
:'''Creative Commons Public Copyright License Marks:''' Creative Commons licenses the use of its public copyright license marks (some of which are shown immediately to the right), which include the CC Logo, on the conditions that you use the marks solely to describe the Creative Commons license that applies to a particular work and include the URI or a hyperlink to the corresponding Commons deed on the Creative Commons server.<br />
<br />
:'''Public Domain Dedication Marks:''' Creative Commons licenses the use of its public domain dedication marks (one of which is shown immediately to the right), on the conditions that you use the mark solely to describe that the CC0 Public Domain Dedication applies to a particular work and include the URI or a hyperlink to the Commons deed on the Creative Commons server.<br />
<br />
:'''Public Domain Mark:''' Creative Commons licenses the use of its trademarked Public Domain Mark badge (shown immediately to the right) on the conditions that you use the mark solely to describe that the Creative Commons Public Domain Mark applies to a particular work and include the URI or hyperlink to the Public Domain Mark on the Creative Commons server.<br />
<br />
:'''Creative Commons License Buttons and Icons:''' Creative Commons licenses the use of its button marks that describe a particular legal tool and its icon marks that describe a key license element, such as BY, NC, ND, and SA, on the conditions that you use the mark solely to describe the Creative Commons legal tool that applies to a particular work and include the URI or hyperlink to the relevant Commons deed on the Creative Commons server.<br />
<br />
:'''Legacy marks:''' Creative Commons has retired some of its prior legal tools, all of which have associated trademarks, such as the Developing Nations License, the Sampling License, and Founder’s Copyright. Although these tools have been retired and are no longer recommended for use, they are still legally effective as to works to which they are applied. Therefore, those trademarks may only be used under the terms and conditions of this Trademark Policy. Creative Commons licenses the use of its legacy marks on the conditions that you use the mark solely to describe the Creative Commons legal tool that applies to the particular work and include the URI or hyperlink to the relevant Commons deed on the Creative Commons server. Note that legacy marks are not available for download on our website.<br />
<br />
:'''Additional permissions:''' In addition to the permissions granted in advance to the public as set forth above, Creative Commons may agree to grant additional permissions upon request. Please submit any such request to legal@creativecommons.org. Except as specifically stated above or otherwise set forth in a written agreement with you, no additional permissions are granted.<br />
<br />
'''Copyright Infringement Notification Policy'''<br />
<br />
If you have reason to believe that any material or activity on a site controlled or operated by Creative Commons (such as creativecommons.org, wiki.creativecommons.org, or open4us.org) is infringing the rights owned by you or someone else for whom you have authority to act, please follow our DMCA Notice & Takedown Procedure.<br />
<br />
PLEASE NOTE: Creative Commons provides public copyright licenses and legal tools that anyone may use. We do not, however, control the use of Creative Commons licenses and legal tools, or have knowledge of whether the use of our licenses or legal tools is authorized by the copyright owner. Additionally, Creative Commons has no control over third-party websites, or over content belonging to persons or organizations other than Creative Commons. Any content hosted on a third-party website is the responsibility of those sites, and not of Creative Commons, even if the content bears a Creative Commons license or is otherwise marked with one of CC’s logos or other trademarks. If you are the copyright owner of content hosted on a third party site in an unauthorized manner, please contact the administrator of that website directly to have the content removed.</div>CCID-diane petershttps://wiki.creativecommons.org/index.php?title=Updated_Policies_Page&diff=107353Updated Policies Page2015-01-26T14:14:39Z<p>CCID-diane peters: </p>
<hr />
<div>This page features a '''DRAFT''' revision of the policies page for the CC websites. Once approved, these policies will replace the [http://creativecommons.org/policies current policies page]. Please note that when the changes to this page go live, appropriate links will be inserted and exemplars of the relevant marks will be inserted as indicated.<br />
<br />
===Summary of changes from the existing policies:===<br />
# Added brief explanation about trademarks and the purposes they serve, for context.<br />
# Added permission in advance to change colors of the double-c logo and its background. Under our prior policy, users did not have explicit permission to change those. It became a frequent ask and we're comfortable granting this permission in advance.<br />
# Clarity that permission isn't needed for referential use. We receive a fair number of inquiries about whether permission is needed to refer to Creative Commons in a book or article or blog post. That's all perfectly fine of course, and couldn't be controlled via trademark in any event.<br />
# Improved language re prohibition on using our logos with modifications of our licenses or legal tools or deeds, whether directly in the text or indirectly through terms of service. Cross reference is made to our expanded explanation and our policy [https://wiki.creativecommons.org/Modifying_the_CC_licenses here], which is already posted.<br />
# Clarity about use of our legacy marks (for retired tools) -- that those remain subject to the policy even if retired, because works to which those have been applied remain under those terms.<br />
<br />
===DRAFT: Full text of proposed policies page below===<br />
<br />
'''Policies'''<br />
<br />
Creative Commons maintains and publishes policies that apply to the use of our websites, content and software that we publish, our trademarks, and our affiliates. Note that some of these policies are maintained on other website pages but can be viewed by clicking on the relevant link below.<br />
<br />
*Privacy Policy<br />
*Website Terms of Use<br />
*Copyright Licensing Policy for Content and Software Code<br />
*Creative Commons Trademark Policy<br />
*Copyright Infringement Notification Policy<br />
<br />
'''Copyright Licensing Policy for Content and Software Code'''<br />
<br />
Other than the Creative Commons trademarks (licensed subject to the Trademark Policy below) and the text of Creative Commons legal tools and human-readable Commons deeds (dedicated to the public domain as specified below), all content on this site is licensed under the Creative Commons Attribution 4.0 International license unless otherwise marked.<br />
<br />
:'''Software:''' All of the software code we create is free software. Please check our code repository for the specific license that applies to software code you wish to use.<br />
<br />
:'''Legal text (we call this legal code) and Commons deeds:''' Creative Commons makes the legal code of its licenses and the CC0 Public Domain Dedication available under the CC0 Public Domain Dedication. CC also makes the Commons deeds associated with its licenses, the CC0 Public Domain Dedication, and the Public Domain Mark available under the CC0 Public Domain Dedication. This allows anyone to reuse those texts for any purpose; however, CC reserves fully and unconditionally all trademark and branding rights associated with the licenses, the CC0 Public Domain Dedication, and deeds. See the Trademark Policy below for more detail.<br />
<br />
'''Creative Commons Trademark Policy'''<br />
<br />
Trademarks are words, graphic designs, or other indicia that identify the source of a product or service. Creative Commons uses a variety of trademarks. Some Creative Commons trademarks serve the purpose of (i) communicating the type of legal tool chosen by the rights holder and/or (ii) indicating that the creator has applied a Creative Commons license to her work. Our registered trademarks and other trademarks include CREATIVE COMMONS (regardless of stylization, capitalization, translation, or other presentation), CC (including the CC in a circle logo (the “CC Logo”) and CC standing alone), CC+ (within a circle or standing alone), CC0, all of the Creative Commons license and public domain buttons and icons, and any combination of the foregoing, whether integrated into a larger whole or standing alone.<br />
<br />
You are authorized to use our trademarks subject to this Trademark Policy, and only on the further condition that you download images of the trademarks directly from our website. You are not authorized to use any modified versions of our trademarks, except that you may use a different color for the CC logo and its background so long as the two colors chosen have a contrast ratio of at least 3:1.<br />
<br />
Creative Commons retains the right to revoke any trademark license for any reason or for no specified reason. Creative Commons is particularly likely to revoke a license if, in its sole discretion, it finds that your use of the trademark is likely to bring disrepute to Creative Commons or any of its trademarks, or confuse the public.<br />
For the avoidance of doubt, you do not need our permission to use our corporate logo for referential use (e.g., to refer to Creative Commons as an organization), provided that such use does not imply endorsement by or association with Creative Commons.<br />
<br />
:'''Modification of CC Licenses:''' To prevent confusion and maintain consistency, you are not allowed to use CREATIVE COMMONS, CC, the CC Logo, or any other Creative Commons trademarks with modified versions of any of our legal tools or deeds, including modifications that do not modify the legal code directly but that further restrict or condition the rights granted by the particular legal tool. These modifications are often contained in a website’s terms of use, and where they are present you may not suggest that you are offering works under Creative Commons. See this page for more information.<br />
<br />
:'''Creative Commons Public Copyright License Marks:''' Creative Commons licenses the use of its public copyright license marks (some of which are shown immediately to the right), which include the CC Logo, on the conditions that you use the marks solely to describe the Creative Commons license that applies to a particular work and include the URI or a hyperlink to the corresponding Commons deed on the Creative Commons server.<br />
<br />
:'''Public Domain Dedication Marks:''' Creative Commons licenses the use of its public domain dedication marks (one of which is shown immediately to the right), on the conditions that you use the mark solely to describe that the CC0 Public Domain Dedication applies to a particular work and include the URI or a hyperlink to the Commons deed on the Creative Commons server.<br />
<br />
:'''Public Domain Mark:''' Creative Commons licenses the use of its trademarked Public Domain Mark badge (shown immediately to the right) on the conditions that you use the mark solely to describe that the Creative Commons Public Domain Mark applies to a particular work and include the URI or hyperlink to the Public Domain Mark on the Creative Commons server.<br />
<br />
:'''Creative Commons License Buttons and Icons:''' Creative Commons licenses the use of its button marks that describe a particular legal tool and its icon marks that describe a key license element, such as BY, NC, ND, and SA, on the conditions that you use the mark solely to describe the Creative Commons legal tool that applies to a particular work and include the URI or hyperlink to the relevant Commons deed on the Creative Commons server.<br />
<br />
:'''Legacy marks:''' Creative Commons has retired some of its prior legal tools, all of which have associated trademarks, such as the Developing Nations License, the Sampling License, and Founder’s Copyright. Although these tools have been retired and are no longer recommended for use, they are still legally effective as to works to which they are applied. Therefore, those trademarks may only be used under the terms and conditions of this Trademark Policy. Creative Commons licenses the use of its legacy marks on the conditions that you use the mark solely to describe the Creative Commons legal tool that applies to the particular work and include the URI or hyperlink to the relevant Commons deed on the Creative Commons server. Note that legacy marks are not available for download on our website.<br />
<br />
:'''Additional permissions:''' In addition to the permissions granted in advance to the public as set forth above, Creative Commons may agree to grant additional permissions upon request. Please submit any such request to legal@creativecommons.org. Except as specifically stated above or otherwise set forth in a written agreement with you, no additional permissions are granted.<br />
<br />
'''Copyright Infringement Notification Policy'''<br />
<br />
If you have reason to believe that any material or activity on a site controlled or operated by Creative Commons (such as creativecommons.org, wiki.creativecommons.org, or open4us.org) is infringing the rights owned by you or someone else for whom you have authority to act, please follow our DMCA Notice & Takedown Procedure.<br />
<br />
PLEASE NOTE: Creative Commons provides public copyright licenses and legal tools that anyone may use. We do not, however, control the use of Creative Commons licenses and legal tools, or have knowledge of whether the use of our licenses or legal tools is authorized by the copyright owner. Additionally, Creative Commons has no control over third-party websites, or over content belonging to persons or organizations other than Creative Commons. Any content hosted on a third-party website is the responsibility of those sites, and not of Creative Commons, even if the content bears a Creative Commons license or is otherwise marked with one of CC’s logos or other trademarks. If you are the copyright owner of content hosted on a third party site in an unauthorized manner, please contact the administrator of that website directly to have the content removed.</div>CCID-diane petershttps://wiki.creativecommons.org/index.php?title=Updated_Policies_Page&diff=107352Updated Policies Page2015-01-26T14:10:05Z<p>CCID-diane peters: /* DRAFT: Full text of proposed policies page below */</p>
<hr />
<div>This page features a '''DRAFT''' revision of the policies page for the CC websites. Once approved, these policies will replace the [http://creativecommons.org/policies current policies page]. <br />
<br />
===Summary of changes from the existing policies:===<br />
# Added brief explanation about trademarks and the purposes they serve, for context.<br />
# Added permission in advance to change colors of the double-c logo and its background. Under our prior policy, users did not have explicit permission to change those. It became a frequent ask and we're comfortable granting this permission in advance.<br />
# Clarity that permission isn't needed for referential use. We receive a fair number of inquiries about whether permission is needed to refer to Creative Commons in a book or article or blog post. That's all perfectly fine of course, and couldn't be controlled via trademark in any event.<br />
# Improved language re prohibition on using our logos with modifications of our licenses or legal tools or deeds, whether directly in the text or indirectly through terms of service. Cross reference is made to our expanded explanation and our policy [https://wiki.creativecommons.org/Modifying_the_CC_licenses here], which is already posted.<br />
# Clarity about use of our legacy marks (for retired tools) -- that those remain subject to the policy even if retired, because works to which those have been applied remain under those terms.<br />
<br />
===DRAFT: Full text of proposed policies page below===<br />
<br />
'''Policies'''<br />
<br />
Creative Commons maintains and publishes policies that apply to the use of our websites, content and software that we publish, our trademarks, and our affiliates. Note that some of these policies are maintained on other website pages but can be viewed by clicking on the relevant link below.<br />
<br />
*Privacy Policy<br />
*Website Terms of Use<br />
*Copyright Licensing Policy for Content and Software Code<br />
*Creative Commons Trademark Policy<br />
*Copyright Infringement Notification Policy<br />
<br />
'''Copyright Licensing Policy for Content and Software Code'''<br />
<br />
Other than the Creative Commons trademarks (licensed subject to the Trademark Policy below) and the text of Creative Commons legal tools and human-readable Commons deeds (dedicated to the public domain as specified below), all content on this site is licensed under the Creative Commons Attribution 4.0 International license unless otherwise marked.<br />
<br />
:'''Software:''' All of the software code we create is free software. Please check our code repository for the specific license that applies to software code you wish to use.<br />
<br />
:'''Legal text (we call this legal code) and Commons deeds:''' Creative Commons makes the legal code of its licenses and the CC0 Public Domain Dedication available under the CC0 Public Domain Dedication. CC also makes the Commons deeds associated with its licenses, the CC0 Public Domain Dedication, and the Public Domain Mark available under the CC0 Public Domain Dedication. This allows anyone to reuse those texts for any purpose; however, CC reserves fully and unconditionally all trademark and branding rights associated with the licenses, the CC0 Public Domain Dedication, and deeds. See the Trademark Policy below for more detail.<br />
<br />
'''Creative Commons Trademark Policy'''<br />
<br />
Trademarks are words, graphic designs, or other indicia that identify the source of a product or service. Creative Commons uses a variety of trademarks. Some Creative Commons trademarks serve the purpose of (i) communicating the type of legal tool chosen by the rights holder and/or (ii) indicating that the creator has applied a Creative Commons license to her work. Our registered trademarks and other trademarks include CREATIVE COMMONS (regardless of stylization, capitalization, translation, or other presentation), CC (including the CC in a circle logo (the “CC Logo”) and CC standing alone), CC+ (within a circle or standing alone), CC0, all of the Creative Commons license and public domain buttons and icons, and any combination of the foregoing, whether integrated into a larger whole or standing alone.<br />
<br />
You are authorized to use our trademarks subject to this Trademark Policy, and only on the further condition that you download images of the trademarks directly from our website. You are not authorized to use any modified versions of our trademarks, except that you may use a different color for the CC logo and its background so long as the two colors chosen have a contrast ratio of at least 3:1.<br />
<br />
Creative Commons retains the right to revoke any trademark license for any reason or for no specified reason. Creative Commons is particularly likely to revoke a license if, in its sole discretion, it finds that your use of the trademark is likely to bring disrepute to Creative Commons or any of its trademarks, or confuse the public.<br />
For the avoidance of doubt, you do not need our permission to use our corporate logo for referential use (e.g., to refer to Creative Commons as an organization), provided that such use does not imply endorsement by or association with Creative Commons.<br />
<br />
:'''Modification of CC Licenses:''' To prevent confusion and maintain consistency, you are not allowed to use CREATIVE COMMONS, CC, the CC Logo, or any other Creative Commons trademarks with modified versions of any of our legal tools or deeds, including modifications that do not modify the legal code directly but that further restrict or condition the rights granted by the particular legal tool. These modifications are often contained in a website’s terms of use, and where they are present you may not suggest that you are offering works under Creative Commons. See this page for more information.<br />
<br />
:'''Creative Commons Public Copyright License Marks:''' Creative Commons licenses the use of its public copyright license marks (some of which are shown immediately to the right), which include the CC Logo, on the conditions that you use the marks solely to describe the Creative Commons license that applies to a particular work and include the URI or a hyperlink to the corresponding Commons deed on the Creative Commons server.<br />
<br />
:'''Public Domain Dedication Marks:''' Creative Commons licenses the use of its public domain dedication marks (one of which is shown immediately to the right), on the conditions that you use the mark solely to describe that the CC0 Public Domain Dedication applies to a particular work and include the URI or a hyperlink to the Commons deed on the Creative Commons server.<br />
<br />
:'''Public Domain Mark:''' Creative Commons licenses the use of its trademarked Public Domain Mark badge (shown immediately to the right) on the conditions that you use the mark solely to describe that the Creative Commons Public Domain Mark applies to a particular work and include the URI or hyperlink to the Public Domain Mark on the Creative Commons server.<br />
<br />
:'''Creative Commons License Buttons and Icons:''' Creative Commons licenses the use of its button marks that describe a particular legal tool and its icon marks that describe a key license element, such as BY, NC, ND, and SA, on the conditions that you use the mark solely to describe the Creative Commons legal tool that applies to a particular work and include the URI or hyperlink to the relevant Commons deed on the Creative Commons server.<br />
<br />
:'''Legacy marks:''' Creative Commons has retired some of its prior legal tools, all of which have associated trademarks, such as the Developing Nations License, the Sampling License, and Founder’s Copyright. Although these tools have been retired and are no longer recommended for use, they are still legally effective as to works to which they are applied. Therefore, those trademarks may only be used under the terms and conditions of this Trademark Policy. Creative Commons licenses the use of its legacy marks on the conditions that you use the mark solely to describe the Creative Commons legal tool that applies to the particular work and include the URI or hyperlink to the relevant Commons deed on the Creative Commons server. Note that legacy marks are not available for download on our website.<br />
<br />
:'''Additional permissions:''' In addition to the permissions granted in advance to the public as set forth above, Creative Commons may agree to grant additional permissions upon request. Please submit any such request to legal@creativecommons.org. Except as specifically stated above or otherwise set forth in a written agreement with you, no additional permissions are granted.<br />
<br />
'''Copyright Infringement Notification Policy'''<br />
<br />
If you have reason to believe that any material or activity on a site controlled or operated by Creative Commons (such as creativecommons.org, wiki.creativecommons.org, or open4us.org) is infringing the rights owned by you or someone else for whom you have authority to act, please follow our DMCA Notice & Takedown Procedure.<br />
<br />
PLEASE NOTE: Creative Commons provides public copyright licenses and legal tools that anyone may use. We do not, however, control the use of Creative Commons licenses and legal tools, or have knowledge of whether the use of our licenses or legal tools is authorized by the copyright owner. Additionally, Creative Commons has no control over third-party websites, or over content belonging to persons or organizations other than Creative Commons. Any content hosted on a third-party website is the responsibility of those sites, and not of Creative Commons, even if the content bears a Creative Commons license or is otherwise marked with one of CC’s logos or other trademarks. If you are the copyright owner of content hosted on a third party site in an unauthorized manner, please contact the administrator of that website directly to have the content removed.</div>CCID-diane petershttps://wiki.creativecommons.org/index.php?title=Updated_Policies_Page&diff=107351Updated Policies Page2015-01-26T13:56:09Z<p>CCID-diane peters: /* DRAFT: Full text of proposed policies page below */</p>
<hr />
<div>This page features a '''DRAFT''' revision of the policies page for the CC websites. Once approved, these policies will replace the [http://creativecommons.org/policies current policies page]. <br />
<br />
===Summary of changes from the existing policies:===<br />
# Added brief explanation about trademarks and the purposes they serve, for context.<br />
# Added permission in advance to change colors of the double-c logo and its background. Under our prior policy, users did not have explicit permission to change those. It became a frequent ask and we're comfortable granting this permission in advance.<br />
# Clarity that permission isn't needed for referential use. We receive a fair number of inquiries about whether permission is needed to refer to Creative Commons in a book or article or blog post. That's all perfectly fine of course, and couldn't be controlled via trademark in any event.<br />
# Improved language re prohibition on using our logos with modifications of our licenses or legal tools or deeds, whether directly in the text or indirectly through terms of service. Cross reference is made to our expanded explanation and our policy [https://wiki.creativecommons.org/Modifying_the_CC_licenses here], which is already posted.<br />
# Clarity about use of our legacy marks (for retired tools) -- that those remain subject to the policy even if retired, because works to which those have been applied remain under those terms.<br />
<br />
===DRAFT: Full text of proposed policies page below===<br />
<br />
'''Policies'''<br />
<br />
Creative Commons maintains and publishes policies that apply to the use of our websites, content and software that we publish, our trademarks, and our affiliates. Note that some of these policies are maintained on other website pages but can be viewed by clicking on the relevant link below.<br />
<br />
*Privacy Policy<br />
*Website Terms of Use<br />
*Copyright Licensing Policy for Content and Software Code<br />
*Creative Commons Trademark Policy<br />
*Copyright Infringement Notification Policy<br />
<br />
'''Copyright Licensing Policy for Content and Software Code'''<br />
<br />
Other than the Creative Commons trademarks (licensed subject to the Trademark Policy below) and the text of Creative Commons legal tools and human-readable Commons deeds (dedicated to the public domain as specified below), all content on this site is licensed under the Creative Commons Attribution 4.0 International license unless otherwise marked.<br />
<br />
:'''Software:''' All of the software code we create is free software. Please check our code repository for the specific license that applies to software code you wish to use.<br />
<br />
:'''Legal text (we call this legal code) and Commons deeds:''' Creative Commons makes the legal code of its licenses and the CC0 Public Domain Dedication available under the CC0 Public Domain Dedication. CC also makes the Commons deeds associated with its licenses, the CC0 Public Domain Dedication, and the Public Domain Mark available under the CC0 Public Domain Dedication. This allows anyone to reuse those texts for any purpose; however, CC reserves fully and unconditionally all trademark and branding rights associated with the licenses, the CC0 Public Domain Dedication, and deeds. See the Trademark Policy below for more detail.<br />
<br />
'''Creative Commons Trademark Policy'''<br />
<br />
Trademarks are words, graphic designs, or other indicia that identify the source of a product or service. Creative Commons uses a variety of trademarks. Some Creative Commons trademarks serve the purpose of (i) communicating the type of legal tool chosen by the rights holder and/or (ii) indicating that the creator has applied a Creative Commons license to her work. Our registered trademarks and other trademarks include CREATIVE COMMONS (regardless of stylization, capitalization, translation, or other presentation), CC (including the CC in a circle logo (the “CC Logo”) and CC standing alone), CC+ (within a circle or standing alone), CC0, all of the Creative Commons license and public domain buttons and icons, and any combination of the foregoing, whether integrated into a larger whole or standing alone.<br />
<br />
You are authorized to use our trademarks subject to this Trademark Policy, and only on the further condition that you download images of the trademarks directly from our website. You are not authorized to use any modified versions of our trademarks, except that you may use a different color for the CC logo and its background so long as the two colors chosen have a contrast ratio of at least 3:1.<br />
<br />
Creative Commons retains the right to revoke any trademark license for any reason or for no specified reason. Creative Commons is particularly likely to revoke a license if, in its sole discretion, it finds that your use of the trademark is likely to bring disrepute to Creative Commons or any of its trademarks, or confuse the public.<br />
For the avoidance of doubt, you do not need our permission to use our corporate logo for referential use (e.g., to refer to Creative Commons as an organization), provided that such use does not imply endorsement by or association with Creative Commons.<br />
<br />
:'''Modification of CC Licenses:''' To prevent confusion and maintain consistency, you are not allowed to use CREATIVE COMMONS, CC, the CC Logo, or any other Creative Commons trademarks with modified versions of any of our legal tools or deeds, including modifications (often contained in a website’s terms of use) that do not modify the legal code directly but that further restrict or condition the rights granted by the particular legal tool. See this page for more information.<br />
<br />
:'''Creative Commons Public Copyright License Marks:''' Creative Commons licenses the use of its public copyright license marks (a few of which are shown immediately to the right), which include the CC Logo, on the conditions that you use the marks solely to describe the Creative Commons license that applies to a particular work and include the URI or a hyperlink to the corresponding Commons deed on the Creative Commons server.<br />
<br />
:'''Public Domain Dedication Marks:''' Creative Commons licenses the use of its public domain dedication marks (one of which is shown immediately to the right), on the conditions that you use the mark solely to describe that the CC0 Public Domain Dedication applies to a particular work and include the URI or a hyperlink to the Commons deed on the Creative Commons server.<br />
<br />
:'''Public Domain Mark:''' Creative Commons licenses the use of its trademarked Public Domain Mark badge (shown immediately to the right) on the conditions that you use the mark solely to describe that the Creative Commons Public Domain Mark applies to a particular work and include the URI or hyperlink to the Public Domain Mark on the Creative Commons server.<br />
<br />
:'''Creative Commons License Buttons and Icons:''' Creative Commons licenses the use of its button marks that describe a particular legal tool and its icon marks that describe a key license element (such as BY, NC, ND, and SA) on the conditions that you use the mark solely to describe the Creative Commons legal tool that applies to a particular work and include the URI or hyperlink to the relevant Commons deed on the Creative Commons server.<br />
<br />
:'''Legacy marks:''' Creative Commons has retired some of its prior legal tools, all of which had associated trademarks, such as the Developing Nations License, the Sampling License, and Founder’s Copyright. Although these tools have been retired, they are still legally effective as to works to which they were applied. Therefore, those trademarks may only be used under the terms and conditions of this Trademark Policy. Creative Commons licenses the use of its legacy marks on the conditions that you use the mark solely to describe the Creative Commons legal tool that applies to the particular work and include the URI or hyperlink to the relevant Commons deed on the Creative Commons server. Note that legacy marks are not available for download on our website, so the condition that you must download images of the marks from our website does not apply to these marks.<br />
<br />
:'''Additional permissions:''' In addition to the permissions granted in advance to the public as set forth above, Creative Commons may grant additional permissions upon request. Please submit any such request to info@creativecommons.org. Except as specifically stated above or otherwise set forth in a written agreement with you, no additional permissions are granted.<br />
<br />
'''Copyright Infringement Notification Policy'''<br />
<br />
If you have reason to believe that any material or activity on a site controlled or operated by Creative Commons (such as creativecommons.org, wiki.creativecommons.org, or open4us.org) is infringing the rights owned by you or someone else for whom you have authority to act, please follow our DMCA Notice & Takedown Procedure.<br />
<br />
PLEASE NOTE: Creative Commons provides public copyright licenses and legal tools that anyone may use. We do not, however, control the use of Creative Commons licenses and legal tools, or have knowledge of whether the use of our licenses or legal tools is authorized by the copyright owner. Additionally, Creative Commons has no control over third-party websites, or over content belonging to persons or organizations other than Creative Commons. Any content hosted on a third-party website is the responsibility of those sites, and not of Creative Commons, even if the content bears a Creative Commons license or is otherwise marked with one of CC’s logos or other trademarks. If you are the copyright owner of content hosted on a third party site in an unauthorized manner, please contact the administrator of that website directly to have the content removed.</div>CCID-diane petershttps://wiki.creativecommons.org/index.php?title=Updated_Policies_Page&diff=107350Updated Policies Page2015-01-26T13:39:58Z<p>CCID-diane peters: /* DRAFT: Full text of proposed policies page below */</p>
<hr />
<div>This page features a '''DRAFT''' revision of the policies page for the CC websites. Once approved, these policies will replace the [http://creativecommons.org/policies current policies page]. <br />
<br />
===Summary of changes from the existing policies:===<br />
# Added brief explanation about trademarks and the purposes they serve, for context.<br />
# Added permission in advance to change colors of the double-c logo and its background. Under our prior policy, users did not have explicit permission to change those. It became a frequent ask and we're comfortable granting this permission in advance.<br />
# Clarity that permission isn't needed for referential use. We receive a fair number of inquiries about whether permission is needed to refer to Creative Commons in a book or article or blog post. That's all perfectly fine of course, and couldn't be controlled via trademark in any event.<br />
# Improved language re prohibition on using our logos with modifications of our licenses or legal tools or deeds, whether directly in the text or indirectly through terms of service. Cross reference is made to our expanded explanation and our policy [https://wiki.creativecommons.org/Modifying_the_CC_licenses here], which is already posted.<br />
# Clarity about use of our legacy marks (for retired tools) -- that those remain subject to the policy even if retired, because works to which those have been applied remain under those terms.<br />
<br />
===DRAFT: Full text of proposed policies page below===<br />
<br />
'''Policies'''<br />
<br />
Creative Commons maintains and publishes policies that apply to the use of our websites, content and software that we publish, our trademarks, and our affiliates. Note that some of these policies are maintained on other website pages but can be viewed by clicking on the relevant link below.<br />
<br />
*Privacy Policy<br />
*Website Terms of Use<br />
*Copyright Licensing Policy for Content and Software Code<br />
*Creative Commons Trademark Policy<br />
*Copyright Infringement Notification Policy<br />
<br />
'''Copyright Licensing Policy for Content and Software Code'''<br />
<br />
Other than the Creative Commons trademarks (licensed subject to the Trademark Policy below) and the text of Creative Commons legal tools and human-readable Commons deeds (dedicated to the public domain as specified below), all content on this site is licensed under the Creative Commons Attribution 4.0 International license unless otherwise noted.<br />
<br />
:'''Software:''' All of the software code we create is free software. Please check our code repository for the specific license that applies to software code you wish to use.<br />
<br />
:'''Legal text (we call this legal code) and Commons deeds:''' Creative Commons makes the legal code of its licenses and the CC0 Public Domain Dedication available under the CC0 Public Domain Dedication. CC also makes the Commons deeds associated with its licenses, the CC0 Public Domain Dedication, and the Public Domain Mark available under the CC0 Public Domain Dedication. This allows anyone to reuse those texts for any purpose; however, CC reserves fully and unconditionally all trademark and branding rights associated with the licenses, the CC0 Public Domain Dedication, and deeds. See the Trademark Policy below for more detail.<br />
<br />
'''Creative Commons Trademark Policy'''<br />
<br />
Trademarks are words, graphic designs, or other indicia that identify the source of a product or service. Creative Commons uses a variety of trademarks. Some Creative Commons trademarks serve the purpose of (i) communicating the type of legal tool chosen by the rights holder and/or (ii) indicating that the creator has applied a Creative Commons license to her work. Our registered trademarks and other trademarks include CREATIVE COMMONS (regardless of stylization, capitalization, translation, or other presentation), CC (including the CC in a circle logo (the “CC Logo”) and CC standing alone), CC+ (within a circle or standing alone), CC0, all of the Creative Commons license and public domain buttons and icons, and any combination of the foregoing, whether integrated into a larger whole or standing alone.<br />
<br />
You are authorized to use our trademarks subject to this Trademark Policy, and only on the further condition that you download images of the trademarks directly from our website. You are not authorized to use any modified versions of our trademarks, except that you may use a different color for the CC logo and its background so long as the two colors chosen have a contrast ratio of at least 3:1.<br />
<br />
Creative Commons retains the right to revoke any trademark license for any reason or for no specified reason. Creative Commons is particularly likely to revoke a license if, in its sole discretion, it finds that your use of the trademark is likely to bring disrepute to Creative Commons or any of its trademarks, or confuse the public.<br />
For the avoidance of doubt, you do not need our permission to use our corporate logo for referential use (e.g., to refer to Creative Commons as an organization), provided that such use does not imply endorsement by or association with Creative Commons.<br />
<br />
:'''Modification of CC Licenses:''' To prevent confusion and maintain consistency, you are not allowed to use CREATIVE COMMONS, CC, the CC Logo, or any other Creative Commons trademarks with modified versions of any of our legal tools or deeds, including modifications (often contained in a website’s terms of use) that do not modify the legal code directly but that further restrict or condition the rights granted by the particular legal tool. See this page for more information.<br />
<br />
:'''Creative Commons Public Copyright License Marks:''' Creative Commons licenses the use of its public copyright license marks (a few of which are shown immediately to the right), which include the CC Logo, on the conditions that you use the marks solely to describe the Creative Commons license that applies to a particular work and include the URI or a hyperlink to the corresponding Commons deed on the Creative Commons server.<br />
<br />
:'''Public Domain Dedication Marks:''' Creative Commons licenses the use of its public domain dedication marks (one of which is shown immediately to the right), on the conditions that you use the mark solely to describe that the CC0 Public Domain Dedication applies to a particular work and include the URI or a hyperlink to the Commons deed on the Creative Commons server.<br />
<br />
:'''Public Domain Mark:''' Creative Commons licenses the use of its trademarked Public Domain Mark badge (shown immediately to the right) on the conditions that you use the mark solely to describe that the Creative Commons Public Domain Mark applies to a particular work and include the URI or hyperlink to the Public Domain Mark on the Creative Commons server.<br />
<br />
:'''Creative Commons License Buttons and Icons:''' Creative Commons licenses the use of its button marks that describe a particular legal tool and its icon marks that describe a key license element (such as BY, NC, ND, and SA) on the conditions that you use the mark solely to describe the Creative Commons legal tool that applies to a particular work and include the URI or hyperlink to the relevant Commons deed on the Creative Commons server.<br />
<br />
:'''Legacy marks:''' Creative Commons has retired some of its prior legal tools, all of which had associated trademarks, such as the Developing Nations License, the Sampling License, and Founder’s Copyright. Although these tools have been retired, they are still legally effective as to works to which they were applied. Therefore, those trademarks may only be used under the terms and conditions of this Trademark Policy. Creative Commons licenses the use of its legacy marks on the conditions that you use the mark solely to describe the Creative Commons legal tool that applies to the particular work and include the URI or hyperlink to the relevant Commons deed on the Creative Commons server. Note that legacy marks are not available for download on our website, so the condition that you must download images of the marks from our website does not apply to these marks.<br />
<br />
:'''Additional permissions:''' In addition to the permissions granted in advance to the public as set forth above, Creative Commons may grant additional permissions upon request. Please submit any such request to info@creativecommons.org. Except as specifically stated above or otherwise set forth in a written agreement with you, no additional permissions are granted.<br />
<br />
'''Copyright Infringement Notification Policy'''<br />
<br />
If you have reason to believe that any material or activity on a site controlled or operated by Creative Commons (such as creativecommons.org, wiki.creativecommons.org, or open4us.org) is infringing the rights owned by you or someone else for whom you have authority to act, please follow our DMCA Notice & Takedown Procedure.<br />
<br />
PLEASE NOTE: Creative Commons provides public copyright licenses and legal tools that anyone may use. We do not, however, control the use of Creative Commons licenses and legal tools, or have knowledge of whether the use of our licenses or legal tools is authorized by the copyright owner. Additionally, Creative Commons has no control over third-party websites, or over content belonging to persons or organizations other than Creative Commons. Any content hosted on a third-party website is the responsibility of those sites, and not of Creative Commons, even if the content bears a Creative Commons license or is otherwise marked with one of CC’s logos or other trademarks. If you are the copyright owner of content hosted on a third party site in an unauthorized manner, please contact the administrator of that website directly to have the content removed.</div>CCID-diane petershttps://wiki.creativecommons.org/index.php?title=ShareAlike_compatibility_analysis:_GPL&diff=106525ShareAlike compatibility analysis: GPL2015-01-22T20:23:10Z<p>CCID-diane peters: </p>
<hr />
<div>[http://www.gnu.org/licenses/gpl.html GPLv3] is a copyleft license primarily used for software, stewarded by the Free Software Foundation. Published in 2007, it is one of the most widely-used free software licenses, and the most widely used copyleft, as well as one of the influences on the Creative Commons licenses. It requires users of licensed material to share alike and to provide attribution to the author(s), and [http://freedomdefined.org/Licenses#Free_Art_License it does 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]]. <br />
<br />
GPL v3 and BY-SA 4.0 are similar licenses with similar aims. But because GPLv3 was written specifically for licensing software, it does have some differences from BY-SA, which are explained in more detail below. <br />
<br />
'''Summary of comparison: GPLv3 and BY-SA 4.0'''<br />
<br />
* The scope of licensed rights in the two licenses is similar but not identical. There are a few key differences: unlike BY-SA, GPL explicitly licenses patent rights where owned by the copyright holder, and addresses "copyright-like rights" (specifically including semiconductor mask rights), and does not explicitly mention sui generis database rights and neighboring rights. Moral rights are also not explicitly addressed in GPLv3. <br />
<br />
* The specific attribution and marking requirements vary slightly, including that GPLv3 addresses authorship information by requiring a copyright notice, while BY-SA requires authorship information even when a work has no copyright notice. <br />
<br />
* Source code, defined as the preferred form for modification of a work, must be conveyed with GPL works. Source must be sufficient to install, use, and modify the work. BY-SA has no source requirement. <br />
<br />
* Both licenses contain a reinstatement mechanism; GPLv3 is slightly more complicated. In some situations, reinstatement of rights may happen under BY-SA but not GPLv3 and vice versa. <br />
<br />
{| style="border-collapse: collapse;" border="1" cellpadding="10"<br />
|-<br />
! style="background-color:#CCCCCC;" | Features || style="background-color:#CCCCCC;" | BY-SA 4.0 || style="background-color:#CCCCCC;" | GPL 3.0<br />
|-<br />
| License scope || Copyright, neighboring rights and sui generis database rights (SGDRs) (''§1(d)'') || Copyright, copyright-like laws (including semiconductor masks) (''§2''), patent rights if owned by copyright holder (''§11'')<br />
|-<br />
| Attribution trigger || If there is applicable copyright in work, then when work or adaptation of work is shared. (''§3(a)'') <br />
<br><br />
If there are applicable SGDRs in work, then when all or a substantial portion of database contents is shared. (''§4(c)'') <br />
|| Action that implicates copyright in a manner that enables other parties to make or receive copies (''§§4-6''), except if giving to other party solely so they can run the works for you on their facilities or make modifications for you (''§2'')<br />
|-<br />
| Attribution removal clause || Yes (''§3(a)(3)'') || No <br />
|-<br />
| Attribution elements || <br />
#creator and attribution parties<br />
#copyright notice<br />
# license notice <br />
# disclaimer notice<br />
# URI or link to the licensed material<br />
# indicate and link to license <br />
(''§3(a)(1)'')<br />
<br><br />
|| <br />
#copyright notice<br />
#license notices and any notice of additional terms<br />
#notices about lack of warranty<br />
#copy of the license<br />
(''§4'')<br />
|-<br />
| Special marking requirement if work is modified || Yes (indicate if you modified and retain indication of previous modifications) (''§3(a)(1)(B)'')<br />
|| Yes (notice that you modified the work, with the relevant date; special notices for interactive user interfaces)(''§5'')<br />
|-<br />
| ShareAlike trigger || When adaptation is shared (''§3(b)'') || When the modified work is conveyed (''§5'')<br />
|-<br />
| ShareAlike scope || Must ShareAlike contributions to adaptations (''§3(b)''); <br />
<br><br />
Must ShareAlike database if it incorporates substantial portion of database contents (''§4(b)'') <br />
|| Must share entire work under GPL terms if copyright permission was needed to create the modified work.<br />
<br><br />
Compilation of licensed work with other separate and independent works permitted; compilation itself must be at least as free as licensed work.(''§5'')<br />
|-<br />
| Source requirement || No || Yes; source required if work not already distributed in preferred form for modification, may be provided in varying ways as specified by license. (''§6'')<br />
|-<br />
| Effective technological measures || May not be applied by licensees if they restrict access to the work or adaptations (''§2(a)(5)(C)'')<br />
<br><br />
Licensees have express permission to circumvent if applied by licensor (''§2(a)(4)'')<br />
|| No explicit mention, so implicitly permitted on non-source forms, though ability to forbid circumvention is waived (''§3''); Requirement for source to be conveyed in a publicly documented format without technical restrictions, which ensures no lockup by ETMs (''§6'').<br />
|-<br />
| Moral rights || Waived only to the extent necessary to allow the license to function. (''§2(b)(1)'') || No explicit mention<br />
|-<br />
| Termination || Automatic upon breach (''§6(a)'') || Automatic upon breach (''§8'')<br />
|-<br />
| Reinstatement after termination || Requires express permission unless cured within 30 days of discovery of violation (''§6(b)'') || Automatic upon cure of breach within 30 days of notice by licensor unless not first violation; also automatic upon cure if copyright holder fails to notify you of violation within 60 days of cure (''§8'')<br />
|-<br />
| Reps & warranties || Expressly disclaimed (''§5'') || Expressly disclaimed (''§§15-16'')<br />
|-<br />
| Choice of law || None || None<br />
|-<br />
| Option to comply with other license versions <br />
|| 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. <br />
(''§2(a)(5)(B)'', ''§(3)(b)(1)'')<br />
|| Compliance with any version automatically permitted if no version specified; otherwise no by default, but licensor may specify that later/other versions allowable. No additional obligations are imposed on authors where a reuser follows a later version. (''§§14'')<br />
|}</div>CCID-diane petershttps://wiki.creativecommons.org/index.php?title=Modifying_the_CC_licenses&diff=105221Modifying the CC licenses2015-01-21T16:26:10Z<p>CCID-diane peters: /* License Modification Policy */</p>
<hr />
<div>CC recognizes that we cannot control or prohibit separate agreements or understandings that involve or affect our standard licenses. After all, CC is not a party to the licenses – they are agreements between licensors and licensees. However, we have long insisted that CC trademarks and branding not be used in connection with separate agreements, understandings, and interpretations that may cause confusion for the public, or create any ambiguity in or inconsistency with the standard terms and conditions offered by a Creative Commons license.<br />
<br />
CC’s policy prohibiting use of our trademarks and branding in connection with such arrangements has been a long-standing part of our [http://creativecommons.org/policies Trademark Policy]. This page provides additional details on the scope of the policy, as well as guidelines for proper and improper use of our trademarks and branding in connection with any such separate agreements, understandings, or modifications. Note that this policy and guidelines also apply to CC’s other legal tools, such as the CC0 Public Domain Dedication.<br />
<br />
===License Modification Policy===<br />
<br />
<br />
'''1. If you make a change to the text of any CC license, you may no longer refer to it as a Creative Commons or CC license, and you must not use any CC trademarks (including the Creative Commons name) or branding in connection with the license.'''<br />
<br />
'''2. If you place any restriction on use of a CC-licensed work that has the effect of limiting or further conditioning the permissions granted to the public under the standard CC license, you must not use any CC trademarks (including the Creative Commons name) or branding in connection with the license or in any way that suggests the work is available under a CC license. These restrictions often appear in terms of use on websites where CC-licensed content is hosted, or as part of terms for downloading CC-licensed content.'''<br />
<br />
::*Example of impermissible extra restriction: You may not use our trademarks or branding if your terms of use provide an interpretation of a license term that contradicts the plain meaning of the standard CC terms, such as stating an interpretation of NonCommercial that hinges on the type of reuser (the definition of NonCommercial does not differentiate on this basis) as opposed to the purpose for which the work is used.<br />
<br />
:::::It is permissible, however, to have trademark guidelines that govern how your logo or other trademark may be used in connection with the CC-licensed work. It is also permissible to impose website terms of use that restrict access to the website by minors pursuant to applicable law. In neither case is use of CC’s trademarks or logo problematic so long as our [http://creativecommons.org/policies Trademark Policy] is followed.<br />
<br />
::*Example of impermissible extra restriction: You may not use our trademarks or branding if your terms of use prohibit sharing of the CC-licensed work in certain formats.<br />
<br />
:::::It is permissible, however, to distribute your own CC-licensed work in a format that is not easily shared (though CC strongly discourages this) or to put your CC-licensed content behind a paywall.<br />
<br />
::*Example of impermissible extra restriction: You may not use our trademarks or branding if your website terms of use impose attribution requirements that are more elaborate than those found in the standard CC license.<br />
<br />
:::::It is permissible, however, to impose terms of use that have the effect of increasing (or removing the conditions on) the permissions granted to the public under the standard terms, such as waiving the attribution condition or allowing translations of an ND-licensed work (see CC+)<br />
<br />
NOTE: While providing "clarification" of license terms can make sense intuitively, it often runs the risk of crossing the line to become a modification of how the licenses work. CC generally discourages this practice, other than creation of educational materials about how the licenses work. If you decide to try to clarify a license term on your website or elsewhere, please respect the guidelines above.<br />
<br />
=== Rationale for the CC policy: ‘‘the beauty of standardization’’ ===<br />
The above guidelines are designed to preserve the underlying principles and benefits of public licensing for licensors and licensees, by reducing conflicts and confusion that may ensue. One of the fundamental design principles of CC licensing is granting permission to the public in advance, thereby reducing transaction costs and facilitating reuse. CC licenses achieve this result through terms and conditions that are ‘’standard,’’ meaning the same terms and conditions apply for all content licensed under a particular CC license. The result is reduced friction for creators who want to allow certain reuses without negotiating and granting lots of individual permissions, and for reusers who want to make use the licensed content with minimal hassle.</div>CCID-diane petershttps://wiki.creativecommons.org/index.php?title=Intergovernmental_Organizations&diff=101919Intergovernmental Organizations2014-12-19T14:00:44Z<p>CCID-diane peters: /* European Space Agency */</p>
<hr />
<div>Intergovernmental organizations (IGOs) are using CC to share research, data, and educational materials they produce. IGOs, like all creators who want wide dissemination of their content, realize they can benefit greatly from the use of Creative Commons licenses--maximizing the impact of their resources and efforts. A number of IGOs believe that as publicly minded institutions, adopting an open licensing policy for at least some subset of their publications is the preferred mechanism for ensuring the broadest and most widespread use and reuse of the information they publish.<br />
<br />
This page explains some of the benefits for IGOs choosing to publish content under Creative Commons licenses, clarifies some unique legal considerations, provides case study of IGOs already using CC, aggregates relevant frequently asked questions, and addresses common licensing scenarios and options available to IGOs. <br />
<br />
<div style="padding:1.25em 1em; margin-left:-1em; margin-right:-1em; -moz-border-radius:5px; -webkit-border-radius:5px; background-color: #eaeaea; overflow: auto;"><br />
<br />
==Why Intergovernmental Organizations Benefit from Using CC==<br />
<br />
===IGOs' missions are aligned with sharing information and resources===<br />
<br />
Disseminating useful information globally is aligned with the mission and work of most IGOs. Sharing information and content -- ranging from education assessment metrics to cultural heritage resources to research studies on the environmental impact of fossil fuels to health information -- is central to the success of IGOs. Information and content that IGOs create can be made maximally useful to the diverse communities they serve, helping citizens, governments, civic institutions, and businesses across all sectors.<br />
<br />
===CC helps clarify rights to users in advance===<br />
Materials like reports, photographs and videos released under the default All Rights Reserved copyright require the end user to ask permission in order to use the resource in the absence of some applicable exception or limitation under applicable copyright law. This framework means IGOs must dedicate resources to review and approve those requests. From the user perspective, the time and effort required to obtain the permission can be significant. The result is that resources are less likely to be used, shared, or repurposed, significantly diminishing the potential impact of information published. (The Organization for Economic Co-operation and Development (OECD) has described the challenges to dissemination of information under the All Rights Reserved copyright framework as follows: "While information technology makes it possible to multiply and distribute content worldwide and almost at no cost, legal restrictions on the reuse of copyrighted material hamper its negotiability in the digital environment ... [T]he Creative Commons license is by far the best-known license for such content, the use of which is growing exponentially." [http://www.oecd.org/dataoecd/35/7/38654317.pdf OECD (2007) Giving Knowledge for Free: The Emergence of Open Educational Resources, p.13]. <br />
<br />
Creative Commons licenses offer a simple, standardized way to grant flexible copyright permissions in advance. The adoption of Creative Commons licenses increases the dissemination, discoverability, reuse, and translatability of research and education materials. CC licenses are the global standard for open content licenses, and are leveraged by corporations, institutions, and government bodies worldwide. Creative Commons licenses lower the transaction costs normally associated with seeking and granting permission to use resources by granting limited permission in advance.<br />
<br />
===CC helps ensure IGOs receive credit for the resources they create===<br />
IGOs who use CC licenses get the credit they deserve for the work they create. All CC licenses require that attribution be given to author in the manner specified. IGOs also need not worry about expending resources crafting custom terms of service specifying how their works can be used. Creative Commons licenses contain vetted, legally robust standard copyright terms and conditions. These common features serve as the baseline, on top of which IGOs can choose to grant additional permissions if desired.<br />
</div><br />
<br />
==FAQ: CC Licenses and IGOs==<br />
IGOs are unique in several respects from individuals and other organizations. Below are some common questions about how CC licenses work for IGOs. <br />
<br />
===Can intergovernmental organizations ("IGOs") use CC licenses?===<br />
Anyone may use CC licenses for works they own, including IGOs. The reasons for doing so vary, and often include a desire to maximize the impact and utility of works for educational and informational purposes, and to enhance transparency.<br />
<br />
Creative Commons published a 3.0 ported license suite specifically intended for use by IGOs. These ported licenses -- known as the 3.0 IGO ported licenses -- grant all of the same permissions as our international (unported) 3.0 licenses; however, they have two unique provisions. First, unlike all other 3.0 licenses, where the licensor is an IGO then unless otherwise mutually agreed, disputes are resolved by mediation or, if that is unsuccessful, through arbitration. This provision was included in response to the challenges IGOs face with enforcing their copyright. IGOs have privileges and immunities from national legal processes, including judicial processes. Waiving that immunity so they can bring suit in a national legal forum can be exceedingly difficult. Instead, IGOs typically use mediation and arbitration as the preferred means to resolve legal disputes.<br />
<br />
Second, unlike the other 3.0 licenses, the 3.0 IGO ported licenses contain a cure period just like CC's new 4.0 licenses. If a licensee fixes a license violation within 30 days of discovery, the license automatically reinstates. The inclusion of the provision is intended to help reduce the likelihood that mediation and arbitration become necessary.<br />
<br />
===What should I know before I use a work licensed under the IGO 3.0 ported licenses?===<br />
<br />
You should be aware of the dispute resolution mechanism in the license, which is contained in Section 8(h). Disputes involving works licensed by IGOs under the licenses are resolved by mediation and arbitration.<br />
<br />
Generally, [http://en.wikipedia.org/wiki/Mediation mediation] is a process used to avoid settling a dispute in court. The process typically involves a neutral third party (called a mediator) who tries to help the parties resolve the dispute. Mediation is not binding, however, unless the parties agree otherwise. [http://en.wikipedia.org/wiki/Arbitration Arbitration] is also used to avoid settling a dispute in court, but the third party (called an arbitrator) has authority to make a decision in favor of one party. Arbitration tends to be more formal than mediation.<br />
<br />
'''''Before using any work licensed by an IGO under the IGO 3.0 ported licenses, be sure you understand what the mediation and arbitration processes are that have been chosen by the IGO and know what they mean for you. IGOs typically designate those in the copyright notice attached to the work.'''''<br />
<br />
===How does the mediation and arbitration provision work?===<br />
<br />
Assuming a violation of the license has occurred and the dispute cannot be amicably resolved, the process starts with mediation. The IGO/licensor sends a notice of mediation to the licensee designating the mediation rules if those are not already identified in the copyright notice accompanying the work. If mediation is unsuccessful, then either the licensor or licensee can chose to commence arbitration. If arbitration becomes necessary, then those proceedings allow for remote participation (e.g., by teleconference, written submissions, etc.) whenever practicable.<br />
<br />
IGOs have the ability to designate the particular mediation and arbitration rules in the copyright notice attached to the work, though the licensor and user of the work can always agree otherwise. If none is designated and no agreement is reached, then the mediation rules will be those identified in the notice of mediation sent to the licensee. If the matter progresses to arbitration, then unless otherwise stated in the copyright notice the rules that apply are the current Arbitration Rules of the United Nations Commission on International Trade Law (known as the [http://www.uncitral.org/uncitral/uncitral_texts/arbitration.html UNCITRAL arbitration rules]). The UNCITRAL rules are widely used by IGOs and others.<br />
<br />
'''''Note that Creative Commons does not endorse any particular mediation or arbitration rules.'''<br />
''<br />
Creative Commons has published special deeds for the IGO 3.0 ported licenses that emphasize that disputes are resolved by mediation and arbitration. You should always take note '''before using a work by an IGO''' whether the license used is an IGO 3.0 ported license.<br />
<br />
===Do the 3.0 IGO ported licenses operate differently in other respects?===<br />
<br />
No, the only differences are the mediation and arbitration processes and the ability to cure a violation and regain your rights as a licensee. CC and the IGOs took great care to ensure that the interpretation of the licenses are no different otherwise than the 3.0 international licenses. The adjudicating body (the mediation or arbitration tribunal) will interpret the scope of the license and remaining obligations in accordance with general principles of international law. Exceptions and limitations remain unregulated by those licenses as well.<br />
<br />
Note that the IGO 3.0 port is designed so that only IGOs as defined in the license are able to use mediation and arbitration. It is not available to anyone else using the licenses.<br />
<br />
== Examples of CC License Use by Intergovernmental Organizations ==<br />
===Commonwealth of Learning===<br />
* The Commonwealth of Learning has incorpoated CC BY-SA as part of its open educational resources (OER) policy: http://creativecommons.org/weblog/entry/27703.<br />
* Interview with Sir John Daniel about the policy: http://creativecommons.org/weblog/entry/28384<br />
*COL's guidelines for open educational resources (OER) in higher education: http://www.col.org/resources/publications/Pages/detail.aspx?PID=364<br />
*[[Case_Studies/Commonwealth_of_Learning]]<br />
<br />
=== European Cultural Foundation ===<br />
* The [http://www.eurocult.org/ European Cultural Foundation's] project [http://www.labforculture.org/ Labforculture.org] releases materials under a CC BY-NC-ND license.<br />
<br />
=== European Funded ===<br />
<br />
* http://www.communia-project.eu/about COMMUNIA - The European Thematic Network on the Digital Public Domain, funded by the European Commission (the executive of the European Union), [http://creativecommons.org/licenses/by-sa/3.0/ CC BY-SA (Unported)].<br />
* European Organization for Nuclear Research (CERN) - [[Case_Studies/CERN|CERN]] publishes its book catalog online as open data using the CC0 public domain dedication and the results of some Large Hadron Collider (LHC) experiments are published under various Creative Commons licenses.<br />
<br />
===European Space Agency===<br />
<br />
* Rosetta NAVCAM Images Now Available Under a Creative Commons Licence: http://blogs.esa.int/rosetta/2014/11/04/rosetta-navcam-images-now-available-under-a-creative-commons-licence/<br />
<br />
* Mars Express HRSC images/videos under BY-SA 3.0 (IGO): http://blogs.esa.int/communication/2014/12/18/esa-mars-express-high-resolution-stereo-camera-hrsc-images-now-available-under-a-creative-commons-licence/, and the actual video/news release: http://www.esa.int/Our_Activities/Space_Science/Mars_Express/Flying_over_Becquerel<br />
<br />
=== Inter-American Development Bank ===<br />
<br />
* The [http://www.iadb.org/ Inter-American Development Bank] is requiring the adoption of Creative Commons by the organizations that receive funding from the Bank in the context of the FOMIN (Fondo Multiateral de Inversiones) initiatives, particularly the ICT4BUS, a fund that promotes the adoption of e-commerce in the American continent, which has financed more that thirty initiatives in Brazil, Argentina, Chile, Nicaragua and other Latin American countries. Banks require those initiative to use the GPL to license any software developed by organizations receiving support from the bank, and CC to license the documentation related with those computer programs, such as user manuals.<br />
<br />
=== International Institute for Democracy and Electoral Assistance ===<br />
<br />
* The [[Case_Studies/International_IDEA_Publishing|International Institute for Democracy and Electoral Assistance (International IDEA)]] is an IGO that supports sustainable democracy, and licenses selected publications under the Creative Commons Attribution-NonCommercial-Share Alike 3.0 Unported licence. <br />
<br />
=== United Nations ===<br />
<br />
* UNESCO OER documentation and toolkits - http://oerwiki.iiep-unesco.org/<br />
* United Nations University OpenCourseWare - http://ocw.unu.edu/Courses_listing<br />
* United Nations University Media Studio - http://mediastudio.unu.edu/en/about/<br />
* United Nations Development Programme (UNDP) Knowledge Platform - http://logosundp.org/; http://logosundp.org/about/terms<br />
* The UNDP Virtual School for Latin America and the Caribbean - http://www.escuelapnud.org/<br />
<br />
=== World Bank ===<br />
*The World Bank has incorporated CC BY into its Open Access Policy and as a default for Bank-produced research and knowledge products via its OPen Knowledge Repository: http://creativecommons.org/weblog/entry/32335.</div>CCID-diane petershttps://wiki.creativecommons.org/index.php?title=Legalcode_errata&diff=101567Legalcode errata2014-11-21T12:56:41Z<p>CCID-diane peters: /* IGO */</p>
<hr />
<div>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. <br />
<br />
=Errors by license=<br />
<br />
==4.0 international license suite (English)==<br />
===Validated HTML===<br />
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. <br />
<br />
==3.0 Unported (International) license suite==<br />
===Section 1===<br />
* '''Incorrect section reference.''' Section 1(b) of BY-SA cites Section 1(f); it should cite Section 1(h).<br />
** BY-SA 1(b)<br />
* '''Incorrect word.''' Section 1(b) of BY-SA says that Adaptation is defined "below"; this should read "above".<br />
** BY-SA 1(b)<br />
===Section 2===<br />
===Section 3===<br />
* '''Inconsistent language'''. In Section 3(d), BY-SA uses "described" instead of "set forth".<br />
** BY-NC-SA 3(d)<br />
* '''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. <br />
** BY-ND 3(c)(iii), BY-NC-ND 3(b).<br />
<br />
===Section 4===<br />
* '''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". <br />
**BY-SA 4(b), BY-NC-SA 4(b)<br />
* '''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". <br />
**BY-NC-SA 4(b)<br />
* '''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". <br />
**BY-NC-ND, 4(b)<br />
* '''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[...]") <br />
**BY-NC-SA 4(b)<br />
* '''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".<br />
** BY-NC-SA 4(b)<br />
* '''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".<br />
** BY-SA 4(b)<br />
* '''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)".<br />
** BY-NC 4(c), BY-NC-SA 4(d).<br />
* '''Extra hyphen.''' In Section 4(c) of BY-NC-SA, "con-nection" is an error, and should be written as "connection" instead. <br />
** BY-NC-SA 4(c)<br />
* '''Typographical error: "Ssection".''' In Section 4(c), BY-SA contains the text "consistent with Ssection 3(b)"; "Ssection" should be "Section". <br />
** BY-SA 4(c).<br />
* '''Incorrect subsection reference.''' Section 4(d)(iii) of BY-NC references 4(c). It should reference 4(b). <br />
** BY-NC 4(d)(iii)<br />
* '''Typographical error.''' In Section 4, several licenses refer to "a Adaptation"; this should be "an Adaptation". <br />
** BY 4(b), BY-NC, BY-SA 4(c), BY-NC-SA 4(d)<br />
<br />
=== Section 5 ===<br />
* '''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". <br />
** BY, BY-SA, BY-NC, BY-ND, BY-NC-ND<br />
* '''Omitted word ("to").''' In BY-NC-ND, "Unless Otherwise Mutually Agreed By the Parties" should read "Unless Otherwise Mutually Agreed To By the Parties".<br />
** BY-NC-ND<br />
* '''Spelling.''' "Merchantability" is misspelled as "Merchantibility" in five licenses. <br />
** BY, BY-NC, BY-SA, BY-ND, BY-NC-ND.<br />
* '''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".<br />
** BY-NC-SA<br />
* '''Typographical error.''' Section 5 contains the text "OR THE PRESENCE OF ABSENCE OF ERRORS". This should read "OR THE PRESENCE OF ERRORS". <br />
** All six licenses.<br />
<br />
=== Notice ===<br />
* '''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".<br />
<br />
==3.0 jurisdiction ports==<br />
===Australia===<br />
*'''Incorrect header color. ''' The heading for BY-NC-SA is green, and should be yellow.<br />
** BY-NC-SA<br />
<br />
===Czech Republic===<br />
*'''Typographical error.''' In the 2nd sentence of the final section ("Upozornění Creative Commons"), "Commos" should be "Commons".<br />
** All six licenses.<br />
<br />
===Ecuador===<br />
*'''Incorrect header color.''' The headings for these four licenses are green, and should be yellow.<br />
** BY-NC, BY-NC-ND, BY-NC-SA, BY-ND<br />
<br />
===Germany===<br />
*'''Incorrect word.''' In Section 8(e), the word "angeboteten" should be "angebotenen".<br />
** BY-SA, BY-NC-SA, BY-NC, BY-ND, BY-NC-ND<br />
<br />
===Greece===<br />
* '''Incorrect header color.''' The headings for these licenses are yellow, and should be green.<br />
** BY, BY-SA<br />
*'''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."<br />
** BY-SA 3(β)<br />
* '''Compatibility.''' In section 4(β), BY-NC-SA is erroneously listed as an example compatible port with BY-SA. <br />
** BY-SA 4(β)<br />
<br />
''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.'''<br />
<br />
===Guatemala===<br />
* '''Incorrect header color.''' The headings for these licenses are green, and should be yellow.<br />
** BY-NC, BY-NC-ND, BY-NC-SA, BY-ND<br />
<br />
===Hong Kong===<br />
* '''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.<br />
** BY-SA, BY-NC-SA 4(b)<br />
* '''Incorrect reference to "the applicable license".''' In section 4(b), a reference to "the applicable license" should instead be to "this license".<br />
** BY-SA, BY-NC-SA 4(b)<br />
* '''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[...]") <br />
**BY-NC-SA 4(b)<br />
<br />
===IGO===<br />
* '''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".<br />
** BY, BY-NC, BY-ND, and BY-NC-ND: 1(g); BY-SA, BY-NC-SA: 1(h)<br />
<br />
===Ireland===<br />
* '''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". <br />
* BY-SA 4(b), BY-NC-SA 4(b)<br />
<br />
===Luxembourg===<br />
* '''Incorrect header color.''' The headings for these licenses are green, and should be yellow.<br />
** BY-NC, BY-NC-ND, BY-NC-SA, BY-ND<br />
<br />
===Netherlands===<br />
* '''Spelling.''' In the last sentence of section 3, the word "beschikt" is misspelled as "beschickt".<br />
** All six licenses.<br />
<br />
===New Zealand===<br />
* '''Compatibility.''' "Unported" omitted from "Creative Commons Compatible License" clause. In section 1, "a Creative Commons ''Unported'' license" should be listed.<br />
** BY-SA<br />
<br />
===Norway===<br />
* '''Compatibility.''' "Unported" omitted from "Creative Commons Compatible License" clause. In section 1(c), "a Creative Commons ''Unported'' license" should be listed.<br />
** BY-SA 1(c)<br />
<br />
''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.''<br />
<br />
===Phillipines===<br />
* '''Compatibility.''' "Unported" omitted from "Creative Commons Compatible License" clause. In section 1(c), "a Creative Commons Unported license" should be listed.<br />
** BY-SA 1(c)<br />
* '''Compatibility.''' In section 4(b), BY-NC-SA is erroneously listed as an example compatible port with BY-SA.<br />
** BY-SA 4(b)<br />
* '''Incorrect reference to "the applicable license".''' In section 4(b), a reference to "the applicable license" should instead be to "this license".<br />
** BY-SA, BY-NC-SA 4(b)<br />
<br />
===Romania===<br />
* '''Compatibility.''' "Unported" omitted from "Creative Commons Compatible License" clause. In section 1(c), "a Creative Commons ''Unported'' license" should be listed.<br />
** BY-SA 1(c)<br />
<br />
''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.''<br />
<br />
===Singapore===<br />
* '''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.<br />
** BY-SA, BY-NC-SA 4(b)<br />
<br />
===Spain===<br />
* '''Missing jurisdiction flag.''' All licenses are missing the Spanish flag image in the header.<br />
** All six licenses.<br />
<br />
===Uganda===<br />
* '''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". <br />
**BY-SA 4(b), BY-NC-SA 4(b)<br />
<br />
===United States===<br />
*'''Typographical error." Section 3(b) includes two semicolons at the end of this section. Only one should be present.<br />
** BY 3(b)<br />
*'''Extra word.''' In Section 4(a), "exercise of the rights granted" should read simply "exercise the rights granted".<br />
** BY-SA 4(a)<br />
* '''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". <br />
** BY-SA 4(b), BY-NC-SA 4(b)<br />
<br />
==2.5 Generic license suite==<br />
===Section 5===<br />
* '''Typographical error.''' Section 5 contains the text "OR THE PRESENCE OF ABSENCE OF ERRORS". This should read "OR THE PRESENCE OF ERRORS". <br />
** All six licenses.<br />
<br />
==2.5 jurisdiction ports==<br />
===Canada===<br />
====English====<br />
* '''Compatibility.''' In section 4(b), BY-NC-SA is erroneously listed as an example compatible port with BY-SA.<br />
** BY-SA 4(b)<br />
====French====<br />
* '''Compatibility.''' In section 4(b), BY-NC-SA is erroneously listed as an example compatible port with BY-SA.<br />
** BY-SA 4(b)<br />
* '''Incorrectly included section.''' The last paragraph of Section 4(a) in BY-NC-ND was included in error and should be deleted.<br />
** BY-NC-ND 4(a)<br />
<br />
==2.0 Generic license suite==<br />
===Section 5===<br />
* '''Typographical error.''' Section 5 contains the text "OR THE PRESENCE OF ABSENCE OF ERRORS". This should read "OR THE PRESENCE OF ERRORS". <br />
** All six licenses.<br />
<br />
==2.0 Jurisdiction ports==<br />
===Austria===<br />
===Canada===<br />
====English====<br />
* '''Compatibility.''' In section 4(b), BY-NC-SA is erroneously listed as an example compatible port with BY-SA.<br />
** BY-SA 4(b)<br />
====French====<br />
* '''Compatibility.''' In section 4(b), BY-NC-SA is erroneously listed as an example compatible port with BY-SA.<br />
** BY-SA 4(b)<br />
===France===<br />
* '''Compatibility.''' In section 4(b), BY-NC-SA is erroneously listed as an example compatible port with BY-SA.<br />
** BY-SA 4(b)<br />
* '''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).<br />
** BY, BY-SA, BY-NC, BY-ND, BY-NC-ND<br />
<br />
===Germany===<br />
* '''Compatibility.''' In section 4(b), BY-NC-SA is erroneously listed as an example compatible port with BY-SA.<br />
** BY-SA 4(b)<br />
* '''Incorrect spacing.''' In the introduction, "UNTER DER VORAUSSETZUNGEIN, DASS" should instead read "UNTER DER VORAUSSETZUNG EIN, DASS". <br />
** BY <br />
* '''Repeated numbering.''' Section 1(f) is mistakenly labeled with "f. f."; there should be only one.<br />
** BY 1(f)<br />
* '''Repeated comma.''' In Section 5, "vereinbart,," should red "vereinbart,".<br />
* '''Repeated numbering.''' Section 8(a) is mistakenly labeled with "a. a."; there should be only one.<br />
** BY 8(a)<br />
* '''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". <br />
** All six licenses.<br />
<br />
===Italy===<br />
* '''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. <br />
** BY-SA 4(b)<br />
<br />
==Errors in the 1.0 license suite==<br />
===Generic===<br />
===Jurisdiction ports===<br />
====Israel====<br />
* '''Typographical error.''' In Section ח.1, the text is in the masculine but the pronoun is feminine; " בכל פעם שאת מפיץ" should instead be "בכל פעם שאתה מפיץ".<br />
<br />
==CC0 (1.0)==<br />
* '''Incorrect word.''' In Section 4(b), "the present or absence of errors" should read "the presence or absence of errors".<br />
<br />
==Deprecated licenses==<br />
=== Developing Nations 2.0===<br />
* '''Typographical error.''' In section 1(c), "enconomy" should read "economy".<br />
<br />
[[Category:Legal]]</div>CCID-diane petershttps://wiki.creativecommons.org/index.php?title=Intergovernmental_Organizations&diff=101384Intergovernmental Organizations2014-11-19T15:15:15Z<p>CCID-diane peters: /* European Funded */</p>
<hr />
<div>Intergovernmental organizations (IGOs) are using CC to share research, data, and educational materials they produce. IGOs, like all creators who want wide dissemination of their content, realize they can benefit greatly from the use of Creative Commons licenses--maximizing the impact of their resources and efforts. A number of IGOs believe that as publicly minded institutions, adopting an open licensing policy for at least some subset of their publications is the preferred mechanism for ensuring the broadest and most widespread use and reuse of the information they publish.<br />
<br />
This page explains some of the benefits for IGOs choosing to publish content under Creative Commons licenses, clarifies some unique legal considerations, provides case study of IGOs already using CC, aggregates relevant frequently asked questions, and addresses common licensing scenarios and options available to IGOs. <br />
<br />
<div style="padding:1.25em 1em; margin-left:-1em; margin-right:-1em; -moz-border-radius:5px; -webkit-border-radius:5px; background-color: #eaeaea; overflow: auto;"><br />
<br />
==Why Intergovernmental Organizations Benefit from Using CC==<br />
<br />
===IGOs' missions are aligned with sharing information and resources===<br />
<br />
Disseminating useful information globally is aligned with the mission and work of most IGOs. Sharing information and content -- ranging from education assessment metrics to cultural heritage resources to research studies on the environmental impact of fossil fuels to health information -- is central to the success of IGOs. Information and content that IGOs create can be made maximally useful to the diverse communities they serve, helping citizens, governments, civic institutions, and businesses across all sectors.<br />
<br />
===CC helps clarify rights to users in advance===<br />
Materials like reports, photographs and videos released under the default All Rights Reserved copyright require the end user to ask permission in order to use the resource in the absence of some applicable exception or limitation under applicable copyright law. This framework means IGOs must dedicate resources to review and approve those requests. From the user perspective, the time and effort required to obtain the permission can be significant. The result is that resources are less likely to be used, shared, or repurposed, significantly diminishing the potential impact of information published. (The Organization for Economic Co-operation and Development (OECD) has described the challenges to dissemination of information under the All Rights Reserved copyright framework as follows: "While information technology makes it possible to multiply and distribute content worldwide and almost at no cost, legal restrictions on the reuse of copyrighted material hamper its negotiability in the digital environment ... [T]he Creative Commons license is by far the best-known license for such content, the use of which is growing exponentially." [http://www.oecd.org/dataoecd/35/7/38654317.pdf OECD (2007) Giving Knowledge for Free: The Emergence of Open Educational Resources, p.13]. <br />
<br />
Creative Commons licenses offer a simple, standardized way to grant flexible copyright permissions in advance. The adoption of Creative Commons licenses increases the dissemination, discoverability, reuse, and translatability of research and education materials. CC licenses are the global standard for open content licenses, and are leveraged by corporations, institutions, and government bodies worldwide. Creative Commons licenses lower the transaction costs normally associated with seeking and granting permission to use resources by granting limited permission in advance.<br />
<br />
===CC helps ensure IGOs receive credit for the resources they create===<br />
IGOs who use CC licenses get the credit they deserve for the work they create. All CC licenses require that attribution be given to author in the manner specified. IGOs also need not worry about expending resources crafting custom terms of service specifying how their works can be used. Creative Commons licenses contain vetted, legally robust standard copyright terms and conditions. These common features serve as the baseline, on top of which IGOs can choose to grant additional permissions if desired.<br />
</div><br />
<br />
==FAQ: CC Licenses and IGOs==<br />
IGOs are unique in several respects from individuals and other organizations. Below are some common questions about how CC licenses work for IGOs. <br />
<br />
===Can intergovernmental organizations ("IGOs") use CC licenses?===<br />
Anyone may use CC licenses for works they own, including IGOs. The reasons for doing so vary, and often include a desire to maximize the impact and utility of works for educational and informational purposes, and to enhance transparency.<br />
<br />
Creative Commons published a 3.0 ported license suite specifically intended for use by IGOs. These ported licenses -- known as the 3.0 IGO ported licenses -- grant all of the same permissions as our international (unported) 3.0 licenses; however, they have two unique provisions. First, unlike all other 3.0 licenses, where the licensor is an IGO then unless otherwise mutually agreed, disputes are resolved by mediation or, if that is unsuccessful, through arbitration. This provision was included in response to the challenges IGOs face with enforcing their copyright. IGOs have privileges and immunities from national legal processes, including judicial processes. Waiving that immunity so they can bring suit in a national legal forum can be exceedingly difficult. Instead, IGOs typically use mediation and arbitration as the preferred means to resolve legal disputes.<br />
<br />
Second, unlike the other 3.0 licenses, the 3.0 IGO ported licenses contain a cure period just like CC's new 4.0 licenses. If a licensee fixes a license violation within 30 days of discovery, the license automatically reinstates. The inclusion of the provision is intended to help reduce the likelihood that mediation and arbitration become necessary.<br />
<br />
===What should I know before I use a work licensed under the IGO 3.0 ported licenses?===<br />
<br />
You should be aware of the dispute resolution mechanism in the license, which is contained in Section 8(h). Disputes involving works licensed by IGOs under the licenses are resolved by mediation and arbitration.<br />
<br />
Generally, [http://en.wikipedia.org/wiki/Mediation mediation] is a process used to avoid settling a dispute in court. The process typically involves a neutral third party (called a mediator) who tries to help the parties resolve the dispute. Mediation is not binding, however, unless the parties agree otherwise. [http://en.wikipedia.org/wiki/Arbitration Arbitration] is also used to avoid settling a dispute in court, but the third party (called an arbitrator) has authority to make a decision in favor of one party. Arbitration tends to be more formal than mediation.<br />
<br />
'''''Before using any work licensed by an IGO under the IGO 3.0 ported licenses, be sure you understand what the mediation and arbitration processes are that have been chosen by the IGO and know what they mean for you. IGOs typically designate those in the copyright notice attached to the work.'''''<br />
<br />
===How does the mediation and arbitration provision work?===<br />
<br />
Assuming a violation of the license has occurred and the dispute cannot be amicably resolved, the process starts with mediation. The IGO/licensor sends a notice of mediation to the licensee designating the mediation rules if those are not already identified in the copyright notice accompanying the work. If mediation is unsuccessful, then either the licensor or licensee can chose to commence arbitration. If arbitration becomes necessary, then those proceedings allow for remote participation (e.g., by teleconference, written submissions, etc.) whenever practicable.<br />
<br />
IGOs have the ability to designate the particular mediation and arbitration rules in the copyright notice attached to the work, though the licensor and user of the work can always agree otherwise. If none is designated and no agreement is reached, then the mediation rules will be those identified in the notice of mediation sent to the licensee. If the matter progresses to arbitration, then unless otherwise stated in the copyright notice the rules that apply are the current Arbitration Rules of the United Nations Commission on International Trade Law (known as the [http://www.uncitral.org/uncitral/uncitral_texts/arbitration.html UNCITRAL arbitration rules]). The UNCITRAL rules are widely used by IGOs and others.<br />
<br />
'''''Note that Creative Commons does not endorse any particular mediation or arbitration rules.'''<br />
''<br />
Creative Commons has published special deeds for the IGO 3.0 ported licenses that emphasize that disputes are resolved by mediation and arbitration. You should always take note '''before using a work by an IGO''' whether the license used is an IGO 3.0 ported license.<br />
<br />
===Do the 3.0 IGO ported licenses operate differently in other respects?===<br />
<br />
No, the only differences are the mediation and arbitration processes and the ability to cure a violation and regain your rights as a licensee. CC and the IGOs took great care to ensure that the interpretation of the licenses are no different otherwise than the 3.0 international licenses. The adjudicating body (the mediation or arbitration tribunal) will interpret the scope of the license and remaining obligations in accordance with general principles of international law. Exceptions and limitations remain unregulated by those licenses as well.<br />
<br />
Note that the IGO 3.0 port is designed so that only IGOs as defined in the license are able to use mediation and arbitration. It is not available to anyone else using the licenses.<br />
<br />
== Examples of CC License Use by Intergovernmental Organizations ==<br />
===Commonwealth of Learning===<br />
* The Commonwealth of Learning has incorpoated CC BY-SA as part of its open educational resources (OER) policy: http://creativecommons.org/weblog/entry/27703.<br />
* Interview with Sir John Daniel about the policy: http://creativecommons.org/weblog/entry/28384<br />
*COL's guidelines for open educational resources (OER) in higher education: http://www.col.org/resources/publications/Pages/detail.aspx?PID=364<br />
*[[Case_Studies/Commonwealth_of_Learning]]<br />
<br />
=== European Cultural Foundation ===<br />
* The [http://www.eurocult.org/ European Cultural Foundation's] project [http://www.labforculture.org/ Labforculture.org] releases materials under a CC BY-NC-ND license.<br />
<br />
=== European Funded ===<br />
<br />
* http://www.communia-project.eu/about COMMUNIA - The European Thematic Network on the Digital Public Domain, funded by the European Commission (the executive of the European Union), [http://creativecommons.org/licenses/by-sa/3.0/ CC BY-SA (Unported)].<br />
* European Organization for Nuclear Research (CERN) - [[Case_Studies/CERN|CERN]] publishes its book catalog online as open data using the CC0 public domain dedication and the results of some Large Hadron Collider (LHC) experiments are published under various Creative Commons licenses.<br />
<br />
===European Space Agency===<br />
<br />
* Rosetta NAVCAM Images Now Available Under a Creative Commons Licence: http://blogs.esa.int/rosetta/2014/11/04/rosetta-navcam-images-now-available-under-a-creative-commons-licence/<br />
<br />
=== Inter-American Development Bank ===<br />
<br />
* The [http://www.iadb.org/ Inter-American Development Bank] is requiring the adoption of Creative Commons by the organizations that receive funding from the Bank in the context of the FOMIN (Fondo Multiateral de Inversiones) initiatives, particularly the ICT4BUS, a fund that promotes the adoption of e-commerce in the American continent, which has financed more that thirty initiatives in Brazil, Argentina, Chile, Nicaragua and other Latin American countries. Banks require those initiative to use the GPL to license any software developed by organizations receiving support from the bank, and CC to license the documentation related with those computer programs, such as user manuals.<br />
<br />
=== International Institute for Democracy and Electoral Assistance ===<br />
<br />
* The [[Case_Studies/International_IDEA_Publishing|International Institute for Democracy and Electoral Assistance (International IDEA)]] is an IGO that supports sustainable democracy, and licenses selected publications under the Creative Commons Attribution-NonCommercial-Share Alike 3.0 Unported licence. <br />
<br />
=== United Nations ===<br />
<br />
* UNESCO OER documentation and toolkits - http://oerwiki.iiep-unesco.org/<br />
* United Nations University OpenCourseWare - http://ocw.unu.edu/Courses_listing<br />
* United Nations University Media Studio - http://mediastudio.unu.edu/en/about/<br />
* United Nations Development Programme (UNDP) Knowledge Platform - http://logosundp.org/; http://logosundp.org/about/terms<br />
* The UNDP Virtual School for Latin America and the Caribbean - http://www.escuelapnud.org/<br />
<br />
=== World Bank ===<br />
*The World Bank has incorporated CC BY into its Open Access Policy and as a default for Bank-produced research and knowledge products via its OPen Knowledge Repository: http://creativecommons.org/weblog/entry/32335.</div>CCID-diane peters