Creative Commons - User contributions [en]

OpenOfficeOrg Addin

2018-03-07T02:53:10Z

CCID-rob: Deprecation notice.

== As the state of this page indicates, this project is not currently supported by Creative Commons. The plugin is no longer available or supported. ==

{{Software Project
|Description=The Creative Commons Add-in for [[OpenOffice.org]] ([http://extensions.services.openoffice.org/project/ccooo OOo Extension Page]) allows license information to be embedded in OpenOffice.org Writer, Impress, Draw and Calc documents.
|Bug tracker=http://code.creativecommons.org/issues/issue?status=-1,1,2,3,4,5,6,7&@sort=-activity&@search_text=&@dispname=CC%20OOo%20Addin&@filter=status,project&@group=priority&project=7&@columns=id,activity,title,creator,assignedto,status&@pagesize=50&@startwith=0
|Code repository=http://code.creativecommons.org/viewsvn/ccooo/
|Mailing list=http://lists.ibiblio.org/mailman/listinfo/cc-devel
}}

<gallery widths=352px heights=400px perrow=2 caption="Set Sharing & Reuse Permissions">
Image:Ccooo_menu.png|''Creative Commons Menu''
Image:CC_tab.png|''Creative Commons Tab''
Image:CC0_tab.png|''CC0 Tab''
Image:PD_tab.png|''Public Domain Tab''
</gallery>

<gallery widths=352px heights=400px perrow=2 caption="Insert Image">
Image:Image_menu.png|''Insert Image Menu''
Image:Image_dialog.png|''Insert Image Dialog''
</gallery>

== Installation ==

The latest version of the plugin is 0.7.0, available for download from the [http://extensions.services.openoffice.org/en/project/ccooo OpenOffice.org Extension site].

To install:

# Download the plugin
# Open OpenOffice.org
# Go to the '''Tools''' menu and select '''Extension Manager'''. Click '''Add''' and select the file you downloaded.
# After the installation process completes, restart OpenOffice.org. The Creative Commons menu options will be located at the bottom of the '''Insert''' menu.

Debian/Ubuntu (& other variants) users:
# Debian/Ubuntu (& other variants) users may have problems if the plugin installed using the Extension Manager.
# They may need to install the plugin using the terminal.
# To install use /usr/lib/openoffice/program/unopkg gui -f ccooo.oxt

To upgrade:

# Open OpenOffice.org
# Go to the '''Tools''' menu and select '''Extension Manager'''. Select ''ccooo.oxt'' and click the '''Updates...''' button. OpenOffice.org will check for updates and prompt you to download the new version, if available.

== Development ==

* Browse code at http://code.creativecommons.org/viewsvn/ccooo/ or checkout from http://code.creativecommons.org/svnroot/ccooo/
* [[OpenOfficeOrg_Addin/Changes|Changes]]

=== Known Issues ===

* This plugin may not work with Mac OS X
* In Ubuntu (& other variants) if the plugin is installed using the extension manager the menus will not show or they will be inactive
* Issues should be added to http://code.creativecommons.org/issues

=== Future Features ===

* Internationalization.
* Support for Mac OS X.

== See also ==

* [[Microsoft Office Addin]]

== External links ==
* [http://labs.creativecommons.org/category/openoffice/ CC Labs blog posts on this add-in]
* [http://techblog.creativecommons.org/2007/04/14/summer-of-code-project-%e2%80%9copenofficeorg-writer-add-in-for-publishing-cc-licensed-documents%e2%80%9d/ Summer of Code Project: “OpenOffice.org Writer Add-in for Publishing CC Licensed Documents”]
* [http://www.openoffice.org/ OpenOffice.org]
* thread on cc-devel from January 2006: [http://lists.ibiblio.org/pipermail/cc-devel/2006-January/000068.html Adding CC License to open office as part of Open Office menu options], [http://lists.ibiblio.org/pipermail/cc-devel/2006-January/000069.html]
* [http://yergler.net/projects/cc-oasis/ccoasis.html CreativeCommons OASIS Open Office Module]
* thread on cc-metadata from February 2004: [http://lists.ibiblio.org/pipermail/cc-metadata/2004-February/000303.html CC metadata in OpenOffice.org/OASIS documents], [http://lists.ibiblio.org/pipermail/cc-metadata/2004-February/000304.html], [http://lists.ibiblio.org/pipermail/cc-metadata/2004-February/000305.html], [http://lists.ibiblio.org/pipermail/cc-metadata/2004-February/000306.html], [http://lists.ibiblio.org/pipermail/cc-metadata/2004-February/000307.html], [http://lists.ibiblio.org/pipermail/cc-metadata/2004-February/000308.html], [http://lists.ibiblio.org/pipermail/cc-metadata/2004-February/000309.html]
* thread on cc-metadata from March 2004: [http://lists.ibiblio.org/pipermail/cc-metadata/2004-March/000310.html CC OASIS Open Office draft updated], [http://lists.ibiblio.org/pipermail/cc-metadata/2004-March/000311.html]
* Issues on OO.o bug tracker: [http://qa.openoffice.org/issues/show_bug.cgi?id=29404 #29404], [http://qa.openoffice.org/issues/show_bug.cgi?id=66656 #66656]

{{Challenge Enabled}}

{{Translations
| articles = Ru:OpenOfficeOrg_Addin
}}

[[Category:Technology]]
[[Category:Metadata]]
[[Category:Tools]]
[[Category:OpenOffice.org]]
__NOTOC__

Metadata Scraper

2018-01-08T18:44:19Z

CCID-rob: Decommissioning the scraper.

{{Software Project
|Description=The Creative Commons Metadata Scraper is a simple crawler used by the license engine to detect metadata stored in pages.
|Bug tracker=https://github.com/cc-archive/metadata_scraper/issues/
|Code repository=https://github.com/cc-archive/metadata_scraper
|Mailing list=https://creativecommons.email/mailman/listinfo/cc-devel
}}

== Decommissioned ==

The Creative Commons Metadata Scraper was decommissioned on Monday 8th January 2018. Due to the changing nature of the web, in particular the widespread adoption of HTTPS, the Scraper had seen greatly reduced use. For potential future directions in metadata presentation, see Creative Commons' [https://github.com/creativecommons/open-ledger Open Ledger] project.

== What it Did ==

The metadata scraper was used by the license deeds to extract embedded metadata from pages. It scanned the page for [[RDFa]] using [http://pypi.python.org/pypi/rdfadict rdfadict] and [http://www.w3.org/2007/08/pyRdfa/ pyRdfa].

== When it Happened ==

When a creator or copyright holder [http://creativecommons.org/license selects a license], they have the opportunity to provide additional metadata about their work. This includes information such as creator and medium, as well as how the creator would like to be attributed. If this information is provided, it is encoded in the HTML generated using [[RDFa]].

In order to provide more context relevant information for visitors, the license deeds loaded a script which looks at the referring page for metadata. If found, the metadata was used to update the deed and display additional attribution or CC+ details.

== Developer Information ==

Metadata Scraper was implemented in Python using the [http://cherrypy.org CherryPy] web framework. The source code is available on GitHub at https://github.com/cc-archive/metadata_scraper .

== Contact ==

Contact [[User:CCID-rob|Rob Myers]] with questions about the scraper.

[[Category:Developer]]

Slack

2017-10-11T23:22:48Z

CCID-rob: Back to auto-invite.

=Slack for Creative Commons=

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

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

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

==How to join Slack==

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

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

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

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

==How to suggest a new channel==

We create channels based on how discussions are shaped around specific topics. Any channel with fewer than 10 users and little to no discussion in 30 days will be deleted.
'''Please do not make a channel without staff approval! It will be deleted.'''
If you would like to suggest a channel via email, please email Jennie [mailto:jennie@creativecommons.org jennie@creativecommons.org]

==Channel naming conventions==

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

==Current Channels and their uses==
* cc-africa
** For discussion of cc-africa and activities
* cc-developers
** For development related chat
* cc-latinamerica
** For discussion of cc-latinamerica and activities
* awesomefund
** For discussions of the CC awesome fund
* cc-announcements
** For official Creative Commons announcements. Watch this channel for news that everyone should know
* cc-europe
** For discussion of cc-europe and activities
* cc-music
** For CC musicians
* cc-opened
** For OER and related
* cc-reads
** Creative Commons reads
* cc-summit
** For summit related discussion
* general
** For saying hello and where all new users begin
* random
** For non-CC related chatter

==Slack Tips==

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

==Frequently used emoji==

:check: = I did this or verified it was done

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

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

:thumbsup: = Sounds good

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

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

:raised_hand: = I volunteer

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

:facepalm: = Disbelief, shame, or exasperation.

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

==Shortcuts==

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

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

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

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

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

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

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

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

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

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

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

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

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

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

==Code of Conduct==

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

==Attribution==

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

Slack

2017-10-11T02:02:28Z

CCID-rob: Change to new sign-up procedure.

=Slack for Creative Commons=

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

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

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

==How to join Slack==

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

2. Fill out this form and we will email you an invitation: https://docs.google.com/forms/d/1F3ywt8kArA57S_BQQ2R4DWjmv1ePv4xtU2nzq2T3zcc/

3. Accept your email invitation.

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

==How to suggest a new channel==

We create channels based on how discussions are shaped around specific topics. Any channel with fewer than 10 users and little to no discussion in 30 days will be deleted.
'''Please do not make a channel without staff approval! It will be deleted.'''
If you would like to suggest a channel via email, please email Jennie [mailto:jennie@creativecommons.org jennie@creativecommons.org]

==Channel naming conventions==

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

==Current Channels and their uses==
* cc-africa
** For discussion of cc-africa and activities
* cc-developers
** For development related chat
* cc-latinamerica
** For discussion of cc-latinamerica and activities
* awesomefund
** For discussions of the CC awesome fund
* cc-announcements
** For official Creative Commons announcements. Watch this channel for news that everyone should know
* cc-europe
** For discussion of cc-europe and activities
* cc-music
** For CC musicians
* cc-opened
** For OER and related
* cc-reads
** Creative Commons reads
* cc-summit
** For summit related discussion
* general
** For saying hello and where all new users begin
* random
** For non-CC related chatter

==Slack Tips==

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

==Frequently used emoji==

:check: = I did this or verified it was done

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

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

:thumbsup: = Sounds good

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

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

:raised_hand: = I volunteer

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

:facepalm: = Disbelief, shame, or exasperation.

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

==Shortcuts==

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

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

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

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

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

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

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

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

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

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

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

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

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

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

==Code of Conduct==

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

==Attribution==

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

Main Page

2017-08-09T18:11:09Z

CCID-rob: Change accont activation instructions

<div style="font-size:125%; line-height:1.75em; margin-bottom:1.75em;"><strong>Welcome to the CC Wiki!</strong> The purpose of this wiki is to help you learn more about CC and give you a chance to collaborate with us. CC relies on its community of users to keep it strong, so now is your chance to '''get involved'''! To learn more about wikis and how to edit them, visit our [[Getting Started]] page.</div>

<div style="color: #d00; margin-bottom:1.75em;"><strong>Please login with your CCID by clicking the log in link above</strong> -- If you have any questions or problems, please write to info@creativecommons.org.</div>

<div style="color: #d00; margin-bottom:1.75em;"><strong>Accounts must be approved before you can edit the CC Wiki</strong> -- Please write to info@creativecommons.org providing your CCID and something to prove you are a real person who wants to edit the Wiki.</div>

<div class="row">
<div class="col-md-6">
<h2 style="padding-top:0px;margin-top:15px;">More about CC</h2>

=== [[Frequently_Asked_Questions | FAQ]] ===
Page of Frequently Asked Questions, with information on all aspects of Creative Commons licensing.

=== [[Developers]] ===
Resources for software developers interested in developing tools to facilitate the use and growth of Creative Commons licenses and standards.

=== [[Marking]] ===
List of best practices for marking content with CC licenses.

=== [[Web Integration]] ===
Everything a web-based (media) hosting site needs to know to integrate CC and CC-related features.

=== [[CC_Affiliate_Network|Affiliate Network]] ===
The CC Affiliate Network consists of 100+ affiliates working in over 79 jurisdictions to support and promote CC activities around the world.

=== [[OER|Open Educational Resources]] ===
Read about Open Educational Resources (OER) and how Creative Commons supports the movement.
</div>
<div class="col-md-6 well">
<h2 style="padding-top:0px;margin-top:15px;">Wiki Projects</h2>

===[[4.0|Version 4.0 of the CC License Suite]]===
CC has released a new version of its core license suite, version 4.0.

=== [[Case Studies]] ===
Past, present, and future "CC success stories" to help measure the impact of Creative Commons around the world. Everyone is encouraged to contribute!

=== [[Content Directories]] ===
A list of organizations and projects powered with Creative Commons licenses.

===[[Events]]===
Upcoming Creative Commons-relevant events around the world: get details, add an event, learn how to start a ccSalon, and sign up for our events mailing list.

=== [[OER Project]] ===
Contribute to CC's OER wiki-databases and pages.

=== [[Documentation]] ===
Large-scale CC specifications, recommendations, white papers, tutorials.

=== [[Translate]] ===
Help us translate our wiki, web content, videos and more.

</div>
</div>

[[Category:Volunteer]]
[[Category:Role]]
[[Category:Project]]
[[Category:Developer]]
[[Category:Creator]]
[[Category:Lawyer]]
[[Category:Guide]]
[[Category:Help]]

__NOTOC__
__NOEDITSECTION__

Platforms

2017-06-15T17:10:25Z

CCID-rob: Link to Slack as Slack.

Platforms are how we organize areas of work for the Creative Commons community. They are working spaces for individuals and institutions to organize and coordinate themselves across the CC Global Network.

Platforms are the way we will create and communicate spaces of strategic collaboration to have worldwide impact. It is the way our network works collaboratively.

The platforms are open to anyone willing to contribute and develop usable, vibrant and collaborative global commons.

== Open Education Platform ==

* [https://docs.google.com/document/d/1-HPog_7pPUXrECzne1t6X7eKwo8TzpYBZ8iC8FfASoE/edit?usp=sharing Working Document]<br/>
* [https://groups.google.com/forum/#!forum/cc-openedu Open Education Platform Mailing List]<br/>
* [https://docs.google.com/document/d/1X-OtHjOx4hD9Ef6s_sAe3B8PrK7aNhcYRAdraexFAqI/edit?usp=sharing Meeting Minutes]<br/>

* IM channel: sign up here: https://slack-signup.creativecommons.org/ it will send you an invitation email. You can then sign up to the [https://creativecommons.slack.com/messages/C2S2MFAJW #cc-openedu] channel.

* Open Source IM option (IRC): To join the #creativecommons-openedu IRC channel, just connect via Freenode.
If you have any questions, ask “robmyers” on slack or IRC.

== Copyright Reform Platform ==

* [https://docs.google.com/document/d/1Dag0KnmSZ0kUm3jf5CWhGm-jmkXBszzLxN5l8trigtk/edit?usp=sharing Working Document]
* IM channel: sign up here: https://slack-signup.creativecommons.org/ it will send you an invitation email. You can then sign up to the [https://creativecommons.slack.com/messages/C5B3EE4G6 #cc-copyrightreform] channel.

== Community Development Platform ==

* [https://docs.google.com/document/d/1KaqPonAvmtocxV27qqbQ7YEBBDWr-VVOodHW3f98eSU/edit?usp=sharing Working Document]
* [https://creativecommons.email/mailman/listinfo/community-development Community Development Platform Mailing List]<br/>
* IM channel: sign up here: https://slack-signup.creativecommons.org/ it will send you an invitation email. You can then sign up to the [https://creativecommons.slack.com/messages/C57CA2KEK #cc-culture-club] channel.

== Open Glam Platform ==

* [https://docs.google.com/document/d/1KaqPonAvmtocxV27qqbQ7YEBBDWr-VVOodHW3f98eSU/edit?usp=sharing Working Document]
* [https://creativecommons.email/mailman/listinfo/openglam Open GLAM Mailing List]<br/>
* IM channel: sign up here: https://slack-signup.creativecommons.org/ it will send you an invitation email. You can then sign up to the [https://creativecommons.slack.com/messages/C57MTL8F7 #cc-openglam] channel.

----

There’s more ways to be engaged with the Creative Commons Global Network. Join us on [https://slack-signup.creativecommons.org Slack] or by email at network@creativecommons.org

Platforms

2017-06-15T17:09:08Z

CCID-rob: Reverted edits by CCID-rob (talk) to last revision by CCID-jennierosehalperin

Platforms are how we organize areas of work for the Creative Commons community. They are working spaces for individuals and institutions to organize and coordinate themselves across the CC Global Network.

Platforms are the way we will create and communicate spaces of strategic collaboration to have worldwide impact. It is the way our network works collaboratively.

The platforms are open to anyone willing to contribute and develop usable, vibrant and collaborative global commons.

== Open Education Platform ==

* [https://docs.google.com/document/d/1-HPog_7pPUXrECzne1t6X7eKwo8TzpYBZ8iC8FfASoE/edit?usp=sharing Working Document]<br/>
* [https://groups.google.com/forum/#!forum/cc-openedu Open Education Platform Mailing List]<br/>
* [https://docs.google.com/document/d/1X-OtHjOx4hD9Ef6s_sAe3B8PrK7aNhcYRAdraexFAqI/edit?usp=sharing Meeting Minutes]<br/>

* IM channel: sign up here: https://slack-signup.creativecommons.org/ it will send you an invitation email. You can then sign up to the [https://creativecommons.slack.com/messages/C2S2MFAJW #cc-openedu] channel.

* Open Source IM option (IRC): To join the #creativecommons-openedu IRC channel, just connect via Freenode.
If you have any questions, ask “robmyers” on slack or IRC.

== Copyright Reform Platform ==

* [https://docs.google.com/document/d/1Dag0KnmSZ0kUm3jf5CWhGm-jmkXBszzLxN5l8trigtk/edit?usp=sharing Working Document]
* IM channel: sign up here: https://slack-signup.creativecommons.org/ it will send you an invitation email. You can then sign up to the [https://creativecommons.slack.com/messages/C5B3EE4G6 #cc-copyrightreform] channel.

== Community Development Platform ==

* [https://docs.google.com/document/d/1KaqPonAvmtocxV27qqbQ7YEBBDWr-VVOodHW3f98eSU/edit?usp=sharing Working Document]
* [https://creativecommons.email/mailman/listinfo/community-development Community Development Platform Mailing List]<br/>
* IM channel: sign up here: https://slack-signup.creativecommons.org/ it will send you an invitation email. You can then sign up to the [https://creativecommons.slack.com/messages/C57CA2KEK #cc-culture-club] channel.

== Open Glam Platform ==

* [https://docs.google.com/document/d/1KaqPonAvmtocxV27qqbQ7YEBBDWr-VVOodHW3f98eSU/edit?usp=sharing Working Document]
* [https://creativecommons.email/mailman/listinfo/openglam Open GLAM Mailing List]<br/>
* IM channel: sign up here: https://slack-signup.creativecommons.org/ it will send you an invitation email. You can then sign up to the [https://creativecommons.slack.com/messages/C57MTL8F7 #cc-openglam] channel.

----

There’s more ways to be engaged with the Creative Commons Global Network. Join us on https://slack-signup.creativecommons.org or by email at network@creativecommons.org

Platforms

2017-06-15T17:08:29Z

CCID-rob: Test edit for spam filter problem diagnosis.

Platforms are how we organize areas of work for the Creative Commons community. They are working spaces for individuals and institutions to organize and coordinate themselves across the CC Global Network.

Platforms are the way we will create and communicate spaces of strategic collaboration to have worldwide impact. It is the way our network works collaboratively.

The platforms are open to anyone willing to contribute and develop usable, vibrant and collaborative global commons.

== Open Education Platform ==

* [https://docs.google.com/document/d/1-HPog_7pPUXrECzne1t6X7eKwo8TzpYBZ8iC8FfASoE/edit?usp=sharing Working Document]<br/>
* [https://groups.google.com/forum/#!forum/cc-openedu Open Education Platform Mailing List]<br/>
* [https://docs.google.com/document/d/1X-OtHjOx4hD9Ef6s_sAe3B8PrK7aNhcYRAdraexFAqI/edit?usp=sharing Meeting Minutes]<br/>

* IM channel: sign up here: https://slack-signup.creativecommons.org/ it will send you an invitation email. You can then sign up to the [https://creativecommons.slack.com/messages/C2S2MFAJW #cc-openedu] channel.

* Open Source IM option (IRC): To join the #creativecommons-openedu IRC channel, just connect via Freenode.
If you have any questions, ask “robmyers” on slack or IRC.

== Copyright Reform Platform ==

* [https://docs.google.com/document/d/1Dag0KnmSZ0kUm3jf5CWhGm-jmkXBszzLxN5l8trigtk/edit?usp=sharing Working Document]
* IM channel: sign up here: https://slack-signup.creativecommons.org/ it will send you an invitation email. You can then sign up to the [https://creativecommons.slack.com/messages/C5B3EE4G6 #cc-copyrightreform] channel.

== Community Development Platform ==

* [https://docs.google.com/document/d/1KaqPonAvmtocxV27qqbQ7YEBBDWr-VVOodHW3f98eSU/edit?usp=sharing Working Document]
* [https://creativecommons.email/mailman/listinfo/community-development Community Development Platform Mailing List]<br/>
* IM channel: sign up here: https://slack-signup.creativecommons.org/ it will send you an invitation email. You can then sign up to the [https://creativecommons.slack.com/messages/C57CA2KEK #cc-culture-club] channel.

== Open Glam Platform ==

* [https://docs.google.com/document/d/1KaqPonAvmtocxV27qqbQ7YEBBDWr-VVOodHW3f98eSU/edit?usp=sharing Working Document]
* [https://creativecommons.email/mailman/listinfo/openglam Open GLAM Mailing List]<br/>
* IM channel: sign up here: https://slack-signup.creativecommons.org/ it will send you an invitation email. You can then sign up to the [https://creativecommons.slack.com/messages/C57MTL8F7 #cc-openglam] channel.

----

There’s more ways to be engaged with the Creative Commons Global Network. Join us on https://slack-signup.creativecommons.org or by email at network@creativecommons.org

Test edit by Rob

Global Network Strategy

2017-02-17T21:10:47Z

CCID-rob: Link to the consultation

=What is it?=
The Creative Commons Global Network Strategy Committee’s role was to identify the relevant issues, suggest areas of research and inquiry, provide analysis, and make a set of recommendations to the affiliate community. In May, the committee met for three days to identify issues and opportunities. At the time, they asked for additional research. Anna Mazgal, an independent researcher, was hired, who designed a series of interviews with affiliate teams, and wrote six reports, along with a global summary report. This is the first time CC has ever looked so deeply into the network and tried to understand how it works, and how best to grow and support it.

Based on the research, and many days of discussions, the committee has drafted a series of recommendations to help create a stronger, more active and engaged community, along with the proper supports to be sustainable. The final draft is now available for comment.

=How Can I Give Feedback?=

The final draft of the Global Network Strategy is available for comment here -

https://consultation.creativecommons.org/

=Who is working on it?=
Carolina Botero (Colombia), Claudia Cristiani (El Salvador), Claudio Ruiz (Chile, RC), Delia Browne (Australia), Kelsey Wiens (Canada, SA), Muid Latif (Malaysia), Naeema Zarif (Turkey, Lebanon, RC), Nic Suzor (Australia), Paul Keller (Netherlands, CC board), Evelin Heidel (Argentina), Simeon Oriko (Kenya), Soohyun Pae (South Korea). The committee was co-chaired by Alek Tarkowski (Poland) and Ryan Merkley (Canada/HQ).

=Meetings=

[[Global_Network_Strategy/DC_Meeting | Washington, DC, United States - May 2016]]

[[Global_Network_Strategy/DE_Meeting | Berlin, Germany - November 2016 ]]

=Research=

==Executive Summaries==

[[Media:Exec_Summary_Global_Report.pdf | Global Summary]], [[Media:Exec_Summary_Global_Report_français_traduction_FINALE.pdf | Français]], [[Media:Exec_Summary_Global_Report_AR.pdf | Arabic]], [[Media:Resumen_global_foc.pdf | Spanish]]

[[Media:Exec_Summary_ArabWorld.pdf | Arab World Summary‎]], [[Media:Exec_Summary_ArabWorld-Arabic.pdf | Arabic]]

[[Media:Exec_Summary_AsiaPacific.pdf | Asia Pacific Summary ‎]]

[[Media:Exec_Summary_CentralAmerica.pdf | Central America Summary]]

[[Media:Exec_Summary_Europe.pdf | Europe Summary ‎]]

[[Media:Exec_Summary_LatinAmerica.pdf| Latin America Summary]], [[Media:Resumen_latam_foc.pdf | Spanish]]

==Regional Reports==

[[Media: FoC_Global_Report.pdf | Global Report]], [[Media: FoC_Global_Report_French.pdf| Français]], [[Media:FOC_reporte_global_SPA.pdf | Spanish]]

[[Media: Final_Africa_Regional_Report.pdf | Africa Report]], [[Media: Final_Africa_Regional_Report_French.pdf | Français]]

[[Media: Final_Arab_World_Regional_Report.pdf | Arab World Report]], [[Media: Final_Arab_World_Regional_Report-Arabic.pdf| Arabic]]

[[Media: Final_AsiaPacific_Regional_Report.pdf | Asia Pacific Report]]

[[Media: Final_Central_America_Regional_Report.pdf | Central America Report]]

[[Media: Final_Europe_Regional_Report.pdf | Europe Report]]

[[Media: Final_LatinAmerica_Regional_Report.pdf | Latin America Report]], [[Media:FOC_reporte_LatAm.pdf | Spanish]]

Main Page

2016-10-24T20:41:40Z

CCID-rob: Remove account upgrade offer.

<div style="font-size:125%; line-height:1.75em; margin-bottom:1.75em;"><strong>Welcome to the CC Wiki!</strong> The purpose of this wiki is to help you learn more about CC and give you a chance to collaborate with us. CC relies on its community of users to keep it strong, so now is your chance to '''get involved'''! To learn more about wikis and how to edit them, visit our [[Getting Started]] page.</div>

<div style="color: #d00; margin-bottom:1.75em;"><strong>Please login with your CCID by clicking the log in link above</strong> -- If you have any questions or problems, please write to info@creativecommons.org.</div>

<div style="color: #d00; margin-bottom:1.75em;"><strong>Accounts must be approved before you can edit the CC Wiki</strong> -- Affiliates, please write to your RC. Otherwise, please write to info@creativecommons.org providing your CCID and something to prove you are a real person who wants to edit the Wiki.</div>

<div class="row">
<div class="col-md-6">
<h2 style="padding-top:0px;margin-top:15px;">More about CC</h2>

=== [[Frequently_Asked_Questions | FAQ]] ===
Page of Frequently Asked Questions, with information on all aspects of Creative Commons licensing.

=== [[Developers]] ===
Resources for software developers interested in developing tools to facilitate the use and growth of Creative Commons licenses and standards.

=== [[Marking]] ===
List of best practices for marking content with CC licenses.

=== [[Web Integration]] ===
Everything a web-based (media) hosting site needs to know to integrate CC and CC-related features.

=== [[CC_Affiliate_Network|Affiliate Network]] ===
The CC Affiliate Network consists of 100+ affiliates working in over 79 jurisdictions to support and promote CC activities around the world.

=== [[OER|Open Educational Resources]] ===
Read about Open Educational Resources (OER) and how Creative Commons supports the movement.
</div>
<div class="col-md-6 well">
<h2 style="padding-top:0px;margin-top:15px;">Wiki Projects</h2>

===[[4.0|Version 4.0 of the CC License Suite]]===
CC has released a new version of its core license suite, version 4.0.

=== [[Case Studies]] ===
Past, present, and future "CC success stories" to help measure the impact of Creative Commons around the world. Everyone is encouraged to contribute!

=== [[Content Directories]] ===
A list of organizations and projects powered with Creative Commons licenses.

===[[Events]]===
Upcoming Creative Commons-relevant events around the world: get details, add an event, learn how to start a ccSalon, and sign up for our events mailing list.

=== [[OER Project]] ===
Contribute to CC's OER wiki-databases and pages.

=== [[Documentation]] ===
Large-scale CC specifications, recommendations, white papers, tutorials.

=== [[Translate]] ===
Help us translate our wiki, web content, videos and more.

</div>
</div>

[[Category:Volunteer]]
[[Category:Role]]
[[Category:Project]]
[[Category:Developer]]
[[Category:Creator]]
[[Category:Lawyer]]
[[Category:Guide]]
[[Category:Help]]

__NOTOC__
__NOEDITSECTION__

Web Integration

2016-08-30T23:49:11Z

CCID-rob: De-SMW.

[[Category:Integration]]
[[Category:Documentation]]
[[Category:Guide]]
[[Category:Developer]]
{{Best Practice}}
__NOTOC__
<div style="font-size:125%; line-height:1.75em; margin-bottom:1.75em;">
This is a page describing ''everything'' a web-based (media) hosting site could do to integrate CC and CC-related features. From simple blogs to elaborate user-generated content communities, there are easy ways to share website content by publishing it under a Creative Commons license. Below we provide a basic overview of how you may integrate Creative Commons licensing into your website.
</div>

<div style="padding:1.25em 1em; margin-left:-1em; margin-right:-1em; -moz-border-radius:5px; -webkit-border-radius:5px; background-color: #eaeaea; overflow: auto;">
== Tools of the Trade ==
{{PageColumn|
== [[Web Integration/HowTo | HowTo Guide]] ==
While knowing about the various tools Creative Commons provides to integrate CC licenses in your web application, seeing examples of implementations is even better!

== [[LicenseChooser.js]] ==

LicenseChooser.js provides a lightweight method for integrating license selection into web applications. The widget is used by TypePad, as well as WpLicense.

== [[Partner Interface]] ==
This interface provides another method of integrating CC license choice in your web application using an <code>iframe</code> or HTML popup.
}}

{{PageColumn|
== [[Web Services | Web Services (API)]] ==
The web services are designed to be a more flexible option for building a custom, fully integrated solution.

== ThirdParty Tools ==
* [[Acts As License]] is a Ruby on Rails plugin that allows for integrating of CC license choice in your Rails web application as a server application building tool.
}}

<br clear="all"/>

== Underlying Technology ==

{{PageColumn|
=== [[RDFa]] ===

RDFa is a way of expressing RDF in XHTML. Creative Commons uses RDFa to express license and other information about works for the semantic web.
}}

{{PageColumn|
=== [[CcREL]] ===
A specification describing how license information may be described and attached to works.
}}

</div>

Developers

2016-08-24T17:10:32Z

CCID-rob: Undo revision 115417 by CCID-rob (talk)

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

== Get Involved ==

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

; E-mail
: Join our [http://lists.ibiblio.org/mailman/listinfo/cc-devel mailing list]
; IRC
: Chat with us real-time on [[IRC]]
; Active Projects
: See [[Hackspace]]

== Older projects ==

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

== Core Technologies ==

; [[RDFa]]
: Standard for adding machine-readable statements to web pages.
; [[CcREL]]
: Language for adding licensing information to web pages.
; [[LRMI]]
: Language for describing educational resources on the web.
; [[Liblicense]] (outdated)
: Library for embedding licensing metadata into files of various formats.

<br clear="all"/>

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

[[Category:Developer]]

__NOTOC__

Developers

2016-08-24T17:10:05Z

CCID-rob:

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

== Get Involved ==

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

; E-mail
: Join our [http://lists.ibiblio.org/mailman/listinfo/cc-devel mailing list]
; IRC
: Chat with us real-time on [[IRC]]
; Active Projects
: See [[Hackspace]]

== Older projects ==

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

== Core Technologies ==

; [[RDFa]]
: Standard for adding machine-readable statements to web pages.
; [[CcREL]]
: Language for adding licensing information to web pages.
; [[LRMI]]
: Language for describing educational resources on the web.
; [[Liblicense]] (outdated)
: Library for embedding licensing metadata into files of various formats.

<br clear="all"/>

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

[[Category:Developer]]

__NOTOC__

CC Affiliate Network

2016-07-19T19:13:49Z

CCID-rob: Changed protection level for "CC Affiliate Network": Editable by staff only. ([Edit=<protect-level-staff>] (indefinite) [Move=<protect-level-staff>] (indefinite))

__NOTOC__

'''[https://wiki.creativecommons.org/wiki/Category:CC_Affiliate_Locale List Affiliates by Jurisdiction]'''

The CC Affiliate Network consists of 100+ affiliates working in over 79 jurisdictions to support and promote CC activities around the world.

The teams have a wide range of responsibilities, including public outreach, community building, translating information and tools, fielding inquiries, conducting research, communicating with the public, maintaining resources for CC users, and in general, promoting sharing and our mission. These teams have a formal relationship with Creative Commons via an agreement between organizations, universities or individuals in the jurisdiction and CC HQ. Unaffiliated volunteers are also welcome to organize events and promote Creative Commons locally, regionally, and globally.

If you would like learn more or contribute in one of these jurisdictions, please click on the flag below or email [mailto:affiliate-program@creativecommons.org affiliate-program@creativecommons.org]. The [[Affiliates]] page on the CC wiki contains more information, including regional activities and history of our work.

== The Licensing Suite ==

[[File:License_3_layers_diagram_intl.gif|right]]

Creative Commons offers a core suite of six copyright licenses written to conform to international treaties governing copyright. The international licenses, as well as existing ported licenses, are all intended to be effective anywhere in the world, with the same effect. In the past, when it was demonstrated that a ported license was needed, Creative Commons worked with experts to craft a localized version of its six, core international licenses. Over 50 ported license suites exist. These ported licenses are based on and compatible with the international license suite, differing only in that they have been modified to reflect local nuances in how terms and conditions are expressed, drafting protocols and, of course, language. They are effective worldwide, as is the international license suite. The most recent international license suite available is [[Version_4|4.0]]. Version 4.0 will not be ported absent compelling circumstances; CC will begin considering requests to port the 4.0 suite in mid-2014.

__NOEDITSECTION__
{{Translations
| articles = De:Netzwerk der Partnerorganisationen
}}

CC0 FAQ

2016-07-19T19:13:21Z

CCID-rob: Changed protection level for "CC0 FAQ": Restrict editing to staff. ([Edit=<protect-level-staff>] (indefinite) [Move=<protect-level-staff>] (indefinite))

[[Category:CC0]]
[[Category:FAQ]]
[[Category:Public domain]]

These FAQs contain information that you should familiarize yourself with before using CC0. The information provided below is not exhaustive – it may not cover important issues that may affect you.

__TOC__

The FAQs are intended to supplement, not replace, our existing [[FAQ|FAQs]]. You are encouraged to review those FAQs as well as our list of [[Considerations for licensors and licensees|issues to consider]] before using CC0 or any of our other legal tools or licenses. You should also read the CC0 legal code carefully and understand what it means before applying it to your work or using a CC0’d work.

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

=== Questions about CC0 generally ===

==== What is CC0? ====

<div style="float: left; margin-right: 1em;">http://i.creativecommons.org/p/zero/1.0/88x31.png</div> Copyright and other laws throughout the world automatically extend copyright protection to works of authorship and databases, whether the author or creator wants those rights or not. CC0 gives those who want to give up those rights a way to do so, to the fullest extent allowed by law. Once the creator or a subsequent owner of a work applies CC0 to a work, the work is no longer his or hers in any meaningful sense under copyright law. Anyone can then use the work in any way and for any purpose, including commercial purposes, subject to other laws and the rights others may have in the work or how the work is used. Think of CC0 as the "no rights reserved" option.

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

A person using CC0 (called the “affirmer” in the legal code) dedicates a work to the public domain by waiving all of his or her copyright and neighboring and related rights in a work, to the fullest extent permitted by law. If the waiver isn’t effective for any reason, then CC0 acts as a license from the affirmer granting the public an unconditional, irrevocable, non exclusive, royalty free license to use the work for any purpose.

==== What is the difference between CC0 and the Public Domain Mark ("PDM")?====

CC0 and PDM differ in important respects and have distinct purposes. CC0 is intended for use only by authors or holders of copyright and related or neighboring rights (including sui generis database rights), in connection with works that are still subject to those rights in one or more jurisdictions. PDM, on the other hand, can be used by anyone, and is intended for use with works that are already free of known copyright restrictions throughout the world. The tools also differ in terms of their effect when applied to a work. CC0 is legally operative in the sense that when it is applied, it changes the copyright status of the work, effectively relinquishing all copyright and related or neighboring rights worldwide. PDM is not legally operative in any respect – it is intended to function as a label, marking a work that is already free of known copyright restrictions.

Review a [http://wiki.creativecommons.org/CC0_PDM_comparison_chart chart comparing the attributes of CC0 and PDM], and Learn more about the [http://wiki.creativecommons.org/PDM_FAQ Public Domain Mark].

=== Questions for those thinking about applying CC0 to their work(s) ===

==== Who can use CC0? ====

Anyone who owns copyright and neighboring and related rights (such as database rights) in a work can use CC0 to give up those rights. But please be careful. CC0 is a one-way street. Once you apply CC0 to your work you can’t change your mind later and re-assert copyright or database rights over the work. In some cases, it’s hard to decide if something qualifies for copyright protection (for example, a database of mostly factual data). Even then, CC0 can be a useful way to assure others that you have committed to surrendering any possible copyright protection you may have.

Even though are you not making any warranties of copyright ownership under CC0, keep in mind that you are still responsible to any third parties who may have existing rights in your work when you distribute the work. For example, if your work contains another person’s work made available under a CC Attribution license, you will need to identify that work separately, attribute the author and provide the license. Likewise, for any other license(s), you will need to ensure that you are in compliance before distributing the work. Of course, if you do not have permission to distribute a work belonging to someone else, you will need to seek appropriate permission from the copyright owner before you use CC0.

==== How do I apply CC0 to my work? ====

Our [http://creativecommons.org/choose/zero/ chooser] will lead you through process. When completed, you will be provided with HTML code that you can copy and paste into your website. Please be aware that it is up to you, the affirmer, to publish your work using CC0 by posting it to your website or elsewhere. Creative Commons does not publish any works and cannot accept responsibility for doing so.

====What are the benefits of including the information requested by the CC0 chooser?====

Any information you provide when using the chooser will be included in the rendered CC0 text placed on the work as well as included in the machine-readable code. Potential users of your work can then use that information to find out more about your work. Particularly valuable to potential users is the jurisdiction from which you are offering the work under CC0, and we encourage you provide that information whenever possible. Please keep in mind, however, that the jurisdiction you select is not a choice of law or forum selection clause (there are no choice of law or forum selection clauses in CC0).

====May I apply CC0 to computer software? If so, is there a recommended implementation?====

Yes, CC0 is suitable for dedicating your copyright and related rights in computer software to the public domain, to the fullest extent possible under law. [[Frequently_Asked_Questions#Can_I_use_a_Creative_Commons_license_for_software.3F|Unlike CC licenses, which should not be used for software]], CC0 is compatible with many software licenses,
[http://www.gnu.org/licenses/license-list.html#CC0 including the GPL]. However, CC0 has not been approved by the [http://opensource.org/ Open Source Initiative] and does not license or otherwise affect any patent rights you may have. You may want to consider using an approved OSI license that does so instead of CC0, such as [http://opensource.org/licenses/GPL-3.0 GPL 3.0] or [http://opensource.org/licenses/Apache-2.0 Apache 2.0].

CC and the Free Software Foundation suggest that if you choose to apply CC0 to software, you include the following notice at the top of each file:

:<PROGRAM NAME> - <DESCRIPTION>

: Written in <YEAR> by <AUTHOR NAME> <AUTHOR E-MAIL ADDRESS>

: [other author/contributor lines as appropriate]

:To the extent possible under law, the author(s) have dedicated all copyright and related and neighboring rights to this software to the public domain worldwide. This software is distributed without any warranty.

:You should have received a copy of the CC0 Public Domain Dedication along with this software. If not, see <http://creativecommons.org/publicdomain/zero/1.0/>.

It is also recommended that you include a file called COPYING (or COPYING.txt) containing the [http://creativecommons.org/publicdomain/zero/1.0/legalcode.txt CC0 legalcode as plain text].

==== Does CC0 require others who use my work to give me attribution? ====

No, and that's a big difference between CC0 and our licenses. Unlike our licenses, there are no conditions contained in CC0. Just like anything in the public domain, it will be possible for others to use or adapt it however they wish without attribution. However, this does not mean that you cannot request attribution in accordance with community or professional norms and standards.

When you choose CC0, requests for attribution are not binding through legal requirements (i.e., as a condition of a copyright license) but can be based on ethical and professional norms, such as those that apply to scholarship and science. These norms can be well articulated, widely held, and self-policing, as is the case with citation standards in the academic community (which are based on ethics and professional reputation, not legal conditions). However, in some instances, as with new technologies or emerging disciplines, the exact implementation of these norms in a particular context requires further consensus-building and articulation.

==== Does CC0 really eliminate all copyright and related rights, everywhere? ====

Please don’t take the 0 (zero) in the name “CC0” literally – no legal instrument can ever eliminate all copyright interests in a work in every jurisdiction.

CC0 doesn’t affect two very important categories of copyright and related rights. First, just like our licenses, CC0 does not affect '''''other persons’ rights''''' in the work or in how it is used, such as publicity or [[Frequently_Asked_Questions#When_are_publicity_rights_relevant.3F|privacy rights]]. Second, the laws of some jurisdictions don’t allow authors and copyright owners to waive all of their own rights, such as moral rights. When the waiver doesn’t work for any reason CC0 acts as a free public license replicating much of intended effect of the waiver, although sometimes even licensing those rights isn’t effective. It varies jurisdiction by jurisdiction.

While we can't be certain that all copyright and related rights will indeed be surrendered everywhere, we are confident that CC0 lets you sever the legal ties between you and your work to the greatest extent legally permissible.

==== What kinds of rights am I surrendering when I use CC0? ====

You are surrendering your copyright and neighboring and related rights in a work, including any database rights you may have. You are also surrendering your own publicity and privacy rights. If your image is captured in the work, for example, you cannot later complain that someone is using it in violation of those rights. In other jurisdictions, you may not be able to waive all of your copyright and neighboring and related rights. Moral rights and unknown rights are two examples of rights that may be difficult to waive in some jurisdictions. When waiver isn’t possible, those rights are licensed under CC0 to the extent allowed by law, although again, sometimes those rights cannot be licensed in advance or at all.

==== What are neighboring rights? ====

Neighboring rights consist of a hodgepodge of rights granted by statute in addition to traditional copyright. Performing artists, record producers and those involved in radio and television broadcasting are often holders of neighboring rights, which may include distribution, performance and/or exploitation rights. Some jurisdictions extend copyright to protect these rights; other jurisdictions offer those protections by separate statute as neighboring or related rights.

When you surrender your neighboring rights using CC0, you do not impact the copyrights or related rights of others, though. For example, if you apply CC0 to a sound recording to which you hold copyright, you surrender your exclusive right to digitally perform that sound recording. But your use of CC0 would not affect the copyright, if any, retained by the composer of the music. Neighboring rights differ from jurisdiction to jurisdiction.

==== What are database rights? ====

Databases may contain facts that, in and of themselves, are not protected by copyright law. The copyright laws of some jurisdictions cover database design and structure, however, and some jurisdictions like the European Union have enacted special laws to protect databases when they are not protected under applicable copyright law. CC0 is intended to cover all copyright and database laws, so that however database rights are protected (under copyright or otherwise), those rights are all surrendered.

==== Can I control how my work is being used once I publish it using CC0? ====

Not really. CC0 is about achieving the effect of placing works in the public domain. Just like anything already in the public domain today, anybody will be able to use your work for any purpose, even in ways you may find distasteful or objectionable. They can also make money off of your work, and they may give you credit or they may not. One aspect you retain control over, however, is the use of the work by others with your trademarks. CC0 does not surrender any trademark rights you have. If others want to associate your trademark with a work you distribute under CC0, they need to ask your permission first as required by trademark law.

If you are worried about how your work will be used, if you want to legally require attribution, or if you don't want people to make money off of your work, then you should not use CC0 and instead consider using one of our licenses.

==== What about other IP related rights, such as trademark and patent rights? ====

CC0 very clearly states that trademark and patent rights of the affirmer are not affected – CC0’s sole reach is copyright and related and neighboring rights, including database rights. Trademarks rights are not affected because creators who use CC0 should be able to protect the quality of products that are associated with their trademark (for example, by preventing a subsequent user of the work from leading others to believe the work in its subsequent use and/or form is associated with or endorsed by the affirmer). So if your primary concern is to ensure the quality and integrity of products associated with your name or your project, then trademark, combined with CC0, may be an option for you.

Patents are fundamentally more challenging. One of our goals at Creative Commons is to encourage use and dissemination of information in a way that encourages others to build upon it, sometimes in surprising and unexpected ways. We can accomplish that objective through a copyright-only solution, without introducing the complexities associated with patent rights. We also wanted to keep CC0 as simple as possible, consistent with its original design goals. We concluded that any perceived benefits of including a patent waiver were significantly outweighed by the downsides of its inclusion.

==== Does using CC0 affect my ability to disclaim warranties? ====

No. CC0 explicitly disclaims "representations or warranties of any kind" (see 4(b)). This is not affected by CC0's abandonment of all copyright-related rights to the extent legally possible. Disposing of an asset (whether or not gratis) often involves a statement by the prior owner as to the state of the asset disposed of such that the owner has no responsibility/liability for things that may go wrong once the asset is no longer theirs. As with a quit claim used with real property, with CC0 a copyright holder abandons or quits their interest without any further obligation, including without warranty.

=== Questions for those thinking about using a CC0’d work ===

==== Can anyone use a work that is distributed under CC0? ====

Yes. CC0 doesn’t restrict who can use a CC0’d work. Once applied, anyone can use the work in any way and for any purpose, including commercial purposes, subject to rights others may have in the work or how it’s used, as well as subject to any other laws or restrictions that may apply.

==== Do I have to attribute the person who applied CC0 to their work? ====

No, there is no legal requirement that you attribute the affirmer, only an expectation that you will voluntarily do so if requested. The CC0 deed provides HTML code that can be copy and pasted into your webpage to easily cite the author and the work, if that information has been provided by the affirmer.

==== Why do some works indicate the jurisdiction from which the work is being published? ====

The CC0 license chooser gives affirmers the opportunity to indicate the jurisdiction from which the work is being offered. If provided by the affirmer, this information is included in the rendered CC0 text that is placed on the work as well as included in the machine-readable code.

The jurisdiction from which the work is being offered is one fact that helps users know what they can and cannot do with a CC0'd work. There are other important facts that impact what rights the affirmer is surrendering and what rights the user has (another, for example, is where the user is located), but the jurisdiction from which the work is offered is one of the more important pieces of information that helps users usefully take advantage of a CC0’d work.

Be careful, though. The jurisdiction, if selected by the affirmer, is not a choice of law or forum selection clause (there are no choice of law or forum selection clauses in CC0). Nor should it be relied upon as definitive for purposes of determining what rights you, as a user of the CC0’d work, may have. It is just one of many facts (if properly selected by the affirmer) that you should take into account before using a work dedicated to the public domain using CC0. Whether or not the affirmer indicated the jurisdiction from which the work was published, you may wish to contact the affirmer to learn more about the work as well as consult your own legal advisor about your rights.

==== What rights do I need to use a CC0’d work? ====

That depends. If you want to use the affirmer’s trademark, you need to get permission first since CC0 doesn’t affect trademark rights. You may also need to get permission from other people who have rights in the work, such as privacy or publicity rights of persons whose likeness or image appear in a photograph or in another work.

==== How can I be sure that I have all the rights I need to use the work? ====

CC0 contains a disclaimer of warranties just like our licenses, so there is no assurance whatsoever that the affirmer (the person who applied CC0 to the work) has all the necessary rights to grant permission to use the CC0’d work. The person applying CC0 to their work is not guaranteeing anything about it, including whether she owns the copyright or has cleared any uses of third-party content that her work may be based on or incorporate. If you are in doubt, then we strongly recommend you not use the work until you have taken all the steps and precautions you feel you need to before doing so, which may include contacting the person who applied CC0 to the work and consulting legal counsel.

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

CC0 FAQ

2016-07-19T18:53:48Z

CCID-rob: Changed protection level for "CC0 FAQ": The new registration system makes spam less of a problem, and legal needs to edit this. ([Edit=Allow only autoconfirmed users] (indefinite) [Move=Allow only autoconfirmed users] (indefinite))

CC Affiliate Network

2016-07-19T18:19:05Z

CCID-rob: Changed protection level for "CC Affiliate Network": The new registration system makes spam less of a problem, and the RCs need to edit this. ([Edit=Allow only autoconfirmed users] (indefinite) [Move=Allow only autoconfirmed users] (indefinite))

Äventyrsgruvan i Tuna Hästberg v. Gunnarsson

2016-05-13T18:06:13Z

CCID-rob: Add Äventyrsgruvan i Tuna Hästberg v. Gunnarsson ( https://github.com/creativecommons/creativecommons.org/issues/246 )

{{Case Law
|title=Äventyrsgruvan i Tuna Hästberg v. Gunnarsson
|region=Sweden
|court=SVEA HOVRÄTT
|date=2016-02-25
|description=Swedish court dismissed photo attribution claim as plaintiff could not demonstrate they held the rights.
|summary='''BACKROUND'''

Photographer licensed a photo using the Swedish port of CC BY-NC-ND version 2.5. When the photo was reused by the defendant, he attributed the company that published the photograph but not the original photographer.

'''RESULT'''

The case was dismissed because the plaintiff was unable to demonstrate that they owned rights to the photograph. The decision was upheld on appeal.
}}
[[Category:Sweden]]

Case Law

2016-05-13T18:00:51Z

CCID-rob: Add Äventyrsgruvan i Tuna Hästberg v. Gunnarsson ( https://github.com/creativecommons/creativecommons.org/issues/246 )

There is a [[:Category:Case_Law|a listing of court decisions]] that discuss or are directly relevant to Creative Commons licenses. The decisions can come from any jurisdiction around the world. It is a list of decisions, not cases.

== Cases ==
{|

|-
| [[09-1684-A_(Lichôdmapwa_v._L'asbl_Festival_de_Theatre_de_Spa)]]
|

|-
| [[Äventyrsgruvan i Tuna Hästberg v. Gunnarsson]]
|
|-
| [[Chang v. Virgin Mobile]]
|

|-
| [[Curry v. Audax]]
|

|-
| [[Gerlach vs. DVU]]
|

|-
| [[Internet Brands v. Holliday]]
| Litigation involving ownership of wiki material contributed by a broad community and licensed under CC BY-SA. At no point in either case was the validity of the CC license contested.

|-
| [[Jacobsen v. Katzer]]
|

|-
| [[No. 71036 N. v. Newspaper]]
| Photographer who used BY-SA licenses on his photographs had some photographs used in a Newspaper. The newspaper did not provide proper attribution. The newspaper had also used Wikipedia text without proper attribution.

|-
| [[SGAE v. Fernandez]]
|

|-
| [[SGAE v. Luis]]
|

|-
| [[TA 3560/09, 3561/09, Avi Re'uveni v. Mapa inc. ישראל: לראשונה, ביהמ"ש אכף רישיון קריאייטיב קומונס]]
|

|}
To add a new court decision to [[:Category:Case_Law|the list]], create a new page here on the wiki and add a copy of [[Template:Case_Law|the Case Law template]] and edit it to contain details of the case. Then add a link to the case to the list above.

If you are unfamiliar with creating pages, [https://www.mediawiki.org/wiki/Help:Starting_a_new_page instructions are available] There are also [https://www.mediawiki.org/wiki/Help:Templates comprehensive guides] and [https://en.wikipedia.org/wiki/Help:A_quick_guide_to_templates quick start instructions] for working with wiki templates. If you are unfamiliar with creating Wiki tables, [https://www.mediawiki.org/wiki/Help:Tables instructions are available for this as well].

For cases taking place across multiple courts, add separate pages for each decision.

Musica Digitale

2016-03-23T23:28:48Z

CCID-rob: Freshdesk ticket 26637

{{ContentDirectory|
mainurl= https://musicadigitale.net/|
ccportal= https://musicadigitale.net/forums/canzone-del-mese.115/|
format=Sound|
size= Around 10000|
}}

MusicaDigitale is the biggest Italian community of computer music. Every registered user has the ability to share his or her music for free, adding a CC license to the song.

ValidateReminder

2016-03-22T00:18:15Z

CCID-rob: Create validation reminder page.

It looks like you've registered at login.creativecommons.org but you haven't yet followed the instructions in the confirmation email.

''Remember that you cannot use the wiki until you have followed the instructions in the confirmation email''

If you haven't seen the confirmation email yet, please check your spam folder.

If it's not there either, please follow this link and follow the instructions there to receive another confirmation email:

'''[https://login.creativecommons.org/pass.php Reset your password]'''

If you have followed the instructions in the confirmation email but you're still seeing this page, we're very sorry! Please contact us and we'll investigate:

[mailto:webmaster@creativecommons.org?Subject=Wiki%20Validation%20Problem webmaster@creativecommons.org]

CcPublisher 2 2

2016-01-19T00:00:11Z

CCID-rob: Note end of development.

== NOTE ==

'''CC Publisher is no longer developed or supported, and is not available for download. This page is for historical reference only.'''

== ccPublisher 2.2 ==

ccPublisher 2.2 will be released at the [http://icommons.org/ iSummit] in Rio De Janeiro, Brazil. The focus of this release is bug fixes and internationalization support. This page documents releases in the 2.2 series in reverse chronological order. The newest release is always at the top.

* '''Windows''' http://prdownload.berlios.de/cctools/ccPublisher-2.2.1.0-setup.exe
* '''Mac OS X''' http://prdownload.berlios.de/cctools/ccPublisher-2.2.1.zip
* '''Linux''' http://prdownload.berlios.de/cctools/ccPublisher-2.2.1.tar.gz

=== ccPublisher 2.2.1 ===

'''22 June 2006'''

This release fixes a crash-inducing bug related to uploading works to the Internet Archive. Mac OS X builds released 29 June 2006.

=== ccPublisher 2.2.0 ===

'''21 June 2006'''

This release fixes some minor bugs found in the final release candidate and contains updated Chinese (Taiwan) translation information. This release includes the same set of translations found in the 2.1.3 release candidate.

Issues, bug reports and feature requests may be logged in the [http://roundup.creativecommons.org/ccpublisher ccPublisher Issue Tracker]. Translation information may be found [[Translating ccPublisher|here]].

=== ccPublisher 2.1.3 (Release Candidate) ===

'''20 June 2006'''

This release corrects many issues found in previous betas, and completes the i18n implementation targeted for 2.2.

This release includes the following translations:

* Catalan (ca_ES)
* Chinese - Taiwan (zh_TW)
* Croation (hr_HR)
* English (en_US)
* Polish (pl_PL)
* Spanish (es_ES)

=== ccPublisher 2.1.2 ===

'''10 June 2006'''

This release corrects several issues found in the previous beta release.

Regressions, bug reports, feature requests and suggestions should be reported in the [http://roundup.creativecommons.org ccPublisher Tracker].

=== ccPublisher 2.1.1 ===

'''9 June 2006'''

This release corrects several issues found in the first beta release (2.1.0). In particular:

* when starting the app with a new translation a crash immediately occurs
* I/O errors which occur during Internet Archive upload are now caught (file not found, permission denied, etc)
* Additional bug fixes reported during the 2.0.x cycle have been applied to this release

The translation catalog templates included with this release have been extensively updated since the previous release. These updates include strings which were missed, as well as additional strings introduced during bug fixes (error messages, etc). See [[Translating ccPublisher]] for details on using msgmerge to update your translation files. The "How Does This Work" window is still untranslated; instructions for translating that window should be available shortly.

This release also contains new file selector and license selector code which has been extensively refactored. Regressions, bug reports, feature requests and suggestions should be reported in the [http://roundup.creativecommons.org ccPublisher Tracker].

Questions regarding internationalization or translation can be directed to the [http://lists.berlios.de/mailman/listinfo/cctools-i18n cctools-i18n] mailing list. As a reminder, translations to be included in the final release are due by 20 June 2006.

=== ccPublisher 2.1.0 ===

'''6 June 2006'''

This is the first beta release of ccPublisher 2.2. This is still pre-release software and there are issues outstanding. See the [http://roundup.creativecommons.org/ccpublisher ccPublisher Tracker] for bug details. This release is provided for people interested in testing ccPublisher and as a resource for translators to begin their work. Information on translating ccPublisher can be found [[Translating ccPublisher|here]]. This release has the following known issues:

* labels in the user interface are not wrapped correctly [http://roundup.creativecommons.org/ccpublisher/issue317 Issue 317]
* errors which occur during the upload process are not caught [http://roundup.creativecommons.org/ccpublisher/issue263 Issue 263]

See [http://roundup.creativecommons.org/ccpublisher/ the tracker] for a complete list of issues currently slated to be addressed.

Bugs, feature requests and feedback may be directed to the [[Mailing Lists|cc-devel]] mailing list or filed in [http://roundup.creativecommons.org/ccpublisher/ Roundup].

[[Category:CcPublisher]]

CC Publisher

2016-01-18T23:59:35Z

CCID-rob: Make end of development notice more prominent.

== NOTE ==
'''CC Publisher is no longer developed or supported, and is not available for download. This page is for historical reference only.'''


[[Category:CcPublisher]]
[[Category:opensource]]
[[Category:Technology]]
[[Category:Choose_license_implementations]]

==Installing CC Publisher==

Installing the application is as simple as downloading the appropriate package below. Once downloaded simply double click the installer (Windows) or drag the application file to your Applications directory (Mac), then run the program. The latest [[ccPublisher 2 Releases|release]] is [[CcPublisher 2 2|2.2.1]]. See the [[CcPublisher System Requirements]] for supported platforms.

'''Windows'''<br />
[http://download.berlios.de/cctools/ccPublisher-2.2.1.0-setup.exe ccPublisher-2.2.1.0-setup.exe] (Windows XP/2000 Installer; MD5 checksum: 2e8f1c96433476668dd4eb511a16dc4d)

'''Mac'''<br />
[http://download.berlios.de/cctools/ccPublisher-2.2.1.zip ccPublisher-2.2.1.zip] (Mac OS X Zip file)

'''Linux'''<br />
[http://download.berlios.de/cctools/ccPublisher-2.2.1.tar.gz ccPublisher-2.2.1.tar.gz] (Source Tarball for Linux)
See [[ccPublisher on Linux]] for information on running ccPublisher on Linux.

==Using ccPublisher==

[[Image:ccp2_screenshot_1.png]]

===Step one: Dragging your songs/videos into ccPublisher===

[[Image:ccp2_screenshot_2.png]

Start the ccPublisher application and hit Next on the introductory screen. The process starts by adding your files to be tagged/uploaded. You can use the browse function to find the files, or simply drag and drop as many files that you would like to license (all with the same license) and upload (all into the same collection at Internet Archive).

===Step two: Adding information about your works===

[[Image:ccp_Screenshot_3.png]]

The next screen will ask for information about your work, which will help others find it at the Internet Archive.

Es simplemente una cancion que espero disfruteis tanto como yo de ella un abrazo

===Step three: Choose your license===
[[Image:ccp2_screenshot_4.png]]

ccPublisher lets you choose one of several license types and the options for each.

===Step four: Specify format information===
[[Image:ccp2_screenshot_5.png]]

Format information helps the Internet Archive

===Step five: Select your destination===
[[Image:ccp2_screenshot_6.png]]

ccPublisher lets you upload your work to the Internet Archive or generate some HTML for use when hosting it yourself. Select your destination and click Next. For details on self-hosting, see [[CcPublisher Self-Hosting]].

===Step six: Logging into the Internet Archive===
[[Image:ccp2_screenshot_7.png]]

To upload your works to the Internet Archive, you'll need an account there to associate your files with. If you don't have an account there, you can go to http://archive.org and create one.

===Step seven: Start your upload to the Archive===
[[Image:ccp2_screenshot_8.png]]

The final step is to upload your works to the Internet Archive. Depending on your connection and the size of files you are uploading, this step can take anywhere from a few seconds to several hours.

===Step eight: All done!===
[[Image:ccp2_screenshot_9.png]]

When your upload is complete, click Next and the Publisher application will furnish you with a URL that should be live within 24 hours at the Archive. If you'd like to use a file-sharing application or add the files to your own website, the file can be found in its original location on your computer, which you can upload to a site or move into a shared downloads folder for P2P (for more info, see [http://creativecommons.org/audio/publish-morpheus our tutorial for sharing your CC music via Morpheus]).

== Support ==

If you have problems with ccPublisher, or just questions or suggestions, you can do one of two things:

* email software@creativecommons.org (good)
* file a bug or feature request in the [http://code.creativecommons.org/issues ccPublisher Tracker] (better)

== Developers ==

ccPublisher developer information is located on the [[CcPublisher Developer|ccPublisher Developer]] page. Discussion about feature requests and development takes place on the [[Mailing Lists|cc-devel]] mailing list.

OER Policy Registry

2016-01-11T21:33:55Z

CCID-rob: Add Romania and the Slovak Republic. ( https://github.com/creativecommons/techstuff/issues/32 )

==Welcome==
Welcome to the Open Educational Resources ([https://creativecommons.org/education OER]) Policy Registry, a database of [https://wiki.creativecommons.org/index.php?title=Special%3ASearch&profile=default&search=%22OER+Policy%22+%22OER+Policy+Status%3DCurrent%22&fulltext=Search current] and [https://wiki.creativecommons.org/index.php?title=Special%3ASearch&profile=default&search=%22OER+Policy%22+%22OER+Policy+Status%3DProposed%22&fulltext=Search proposed] open education policies from around the world. Here, anyone can easily share, update, and browse open education policies and legislation. In addition, we host '''[[OER_Policy_Registry/Supporting_Documents|supporting policy resources]]''' such as case studies and guides.

The OER Policy Registry is being upgraded and migrated away from the CC Wiki. Please be patient while we make the transition.

==Scope==
We define OER policies as legislation, institutional policies, and/or funder mandates that lead to the creation, increased use, and/or support for improving OER. This registry is not a list of open projects, terms of use, or a registry of [http://roarmap.eprints.org open access policies].

==Popular Searches==
<table>
<tr>
<td width=15% valign=top style="padding-right:2%; vertical-align: top; margin-top: 12px;">

====By Status====
* [https://wiki.creativecommons.org/index.php?title=Special%3ASearch&profile=default&search=%22OER+Policy%22+%22OER+Policy+Status%3DProposed%22&fulltext=Search Proposed]
* [https://wiki.creativecommons.org/index.php?title=Special%3ASearch&profile=default&search=%22OER+Policy%22+%22OER+Policy+Status%3DCurrent%22&fulltext=Search Current]

</td>

<td width=15% valign=top style="padding-right:2%; vertical-align: top; margin-top: 12px;">
====By Jurisdiction Type====
* [https://wiki.creativecommons.org/index.php?title=Special%3ASearch&profile=default&search=%22OER+Policy%22+%22OER+Policy+Jurisdiction%3DGlobal%22&fulltext=Search Global]
* [https://wiki.creativecommons.org/index.php?title=Special%3ASearch&profile=default&search=%22OER+Policy%22+%22OER+Policy+Jurisdiction%3DNational%22&fulltext=Search National]
* [https://wiki.creativecommons.org/index.php?title=Special%3ASearch&profile=default&search=%22OER+Policy%22+%22OER+Policy+Jurisdiction%State%22&fulltext=Search State]
* [https://wiki.creativecommons.org/index.php?title=Special%3ASearch&profile=default&search=%22OER+Policy%22+%22OER+Policy+Jurisdiction%3DInstitution+-+Primary%22&fulltext=Search Insitituion - Primary]
* [https://wiki.creativecommons.org/index.php?title=Special%3ASearch&profile=default&search=%22OER+Policy%22+%22OER+Policy+Jurisdiction%3DInstitution+-+Secondary%22&fulltext=Search Institution- Secondary]
* [https://wiki.creativecommons.org/index.php?title=Special%3ASearch&profile=default&search=%22OER+Policy%22+%22OER+Policy+Jurisdiction%3DInstitution+-+Tertary%22&fulltext=Search Institution - Tertiary]
* [https://wiki.creativecommons.org/index.php?title=Special%3ASearch&profile=default&search=%22OER+Policy%22+%22OER+Policy+Jurisdiction%3DSystem%22&fulltext=Search System]
</td>

<td width=15% valign=top style="padding-right:2%; vertical-align: top; margin-top: 12px;">
====By Country====
* [https://wiki.creativecommons.org/index.php?title=Special%3ASearch&profile=default&search=%22OER+Policy%22+%22Country%3DGlobal%22&fulltext=Search Global]
* [https://wiki.creativecommons.org/index.php?title=Special%3ASearch&profile=default&search=%22OER+Policy%22+%22Country%3DArgentina%22&fulltext=Search Argentina]
* [https://wiki.creativecommons.org/index.php?title=Special%3ASearch&profile=default&search=%22OER+Policy%22+%22Country%3DAustralia%22&fulltext=Search Australia]
* [https://wiki.creativecommons.org/index.php?title=Special%3ASearch&profile=default&search=%22OER+Policy%22+%22Country%3DBrazil%22&fulltext=Search Brazil]
* [https://wiki.creativecommons.org/index.php?title=Special%3ASearch&profile=default&search=%22OER+Policy%22+%22Country%3DCanada%22&fulltext=Search Canada]
* [https://wiki.creativecommons.org/index.php?title=Special%3ASearch&profile=default&search=%22OER+Policy%22+%22Country%3DColombia%22&fulltext=Search Colombia]
* [https://wiki.creativecommons.org/index.php?title=Special%3ASearch&profile=default&search=%22OER+Policy%22+%22Country%3DFrance%22&fulltext=Search France]
* [https://wiki.creativecommons.org/index.php?title=Special%3ASearch&profile=default&search=%22OER+Policy%22+%22Country%3DGhana%22&fulltext=Search Ghana]
* [https://wiki.creativecommons.org/index.php?title=Special%3ASearch&profile=default&search=%22OER+Policy%22+%22Country%3DIndia%22&fulltext=Search India]
* [https://wiki.creativecommons.org/index.php?title=Special%3ASearch&profile=default&search=%22OER+Policy%22+%22Country%3DIndonesia%22&fulltext=Search Indonesia]
* [https://wiki.creativecommons.org/index.php?title=Special%3ASearch&profile=default&search=%22OER+Policy%22+%22Country%3DKenya%22&fulltext=Search Kenya]
* [https://wiki.creativecommons.org/index.php?title=Special%3ASearch&profile=default&search=%22OER+Policy%22+%22Country%3DLithuania%22&fulltext=Search Lithuania]
* [https://wiki.creativecommons.org/index.php?title=Special%3ASearch&profile=default&search=%22OER+Policy%22+%22Country%3DMauritius%22&fulltext=Search Mauritius ]
* [https://wiki.creativecommons.org/index.php?title=Special%3ASearch&profile=default&search=%22OER+Policy%22+%22Country%3DMexico%22&fulltext=Search Mexico]
* [https://wiki.creativecommons.org/index.php?title=Special%3ASearch&profile=default&search=%22OER+Policy%22+%22Country%3DNetherlands%22&fulltext=Search Netherlands]
* [https://wiki.creativecommons.org/index.php?title=Special%3ASearch&profile=default&search=%22OER+Policy%22+%22Country%3DNew+Zealand%22&fulltext=Search New Zealand]
* [https://wiki.creativecommons.org/index.php?title=Special%3ASearch&profile=default&search=%22OER+Policy%22+%22Country%3DPoland%22&fulltext=Search Poland]
* [https://wiki.creativecommons.org/index.php?title=Special%3ASearch&profile=default&search=%22OER+Policy%22+%22Country%3DRomania%22&fulltext=Search Romania]
* [https://wiki.creativecommons.org/index.php?title=Special%3ASearch&profile=default&search=%22OER+Policy%22+%22Country%3DScotland%22&fulltext=Search Scotland]
* [https://wiki.creativecommons.org/index.php?title=Special%3ASearch&profile=default&search=%22OER+Policy%22+%22Country%3DSlovak+Republic%22&fulltext=Search Slovak Republic]
* [https://wiki.creativecommons.org/index.php?title=Special%3ASearch&profile=default&search=%22OER+Policy%22+%22Country%3DSlovenia%22&fulltext=Search Slovenia]
* [https://wiki.creativecommons.org/index.php?title=Special%3ASearch&profile=default&search=%22OER+Policy%22+%22Country%3DSouth+Africa%22&fulltext=Search South Africa]
* [https://wiki.creativecommons.org/index.php?title=Special%3ASearch&profile=default&search=%22OER+Policy%22+%22Country%3DSpain%22&fulltext=Search Spain]
* [https://wiki.creativecommons.org/index.php?title=Special%3ASearch&profile=default&search=%22OER+Policy%22+%22Country%3DUnited+Kingdom%22&fulltext=Search United Kingdom]
* [https://wiki.creativecommons.org/index.php?title=Special%3ASearch&profile=default&search=%22OER+Policy%22+%22Country%3DUnited+States+of+America%22&fulltext=Search United States of America]
* [https://wiki.creativecommons.org/index.php?title=Special%3ASearch&profile=default&search=%22OER+Policy%22+%22Country%3DWales%22&fulltext=Search Wales]
</td>

</tr>
</table>

==Every Policy==

To see a list of all the policies, [https://wiki.creativecommons.org/wiki/Category:OER_Policy_Registry click here].

==Contribute==
We have begun to enter OER policies into the registry, but we need your help to make it a truly useful global resource. Sharing our collective knowledge of existing OER policies, in the same way we believe in sharing educational resources, will help advocates and policymakers further open policies worldwide.

To add a new policy, please create a page on the Wiki with the name of the policy and include its information formatted using the OER Policy Template.

See here for the template to copy, and for further instructions: [https://wiki.creativecommons.org/wiki/Template:OER_Policy OER Policy Template].

__NOTOC__

Case Law

2015-12-15T01:39:30Z

CCID-rob: Copy editing for easier comprehension.

There is a [[:Category:Case_Law|a listing of court decisions]] that discuss or are directly relevant to Creative Commons licenses. The decisions can come from any jurisdiction around the world. It is a list of decisions, not cases.

== Cases ==
{|

|-
| [[09-1684-A_(Lichôdmapwa_v._L'asbl_Festival_de_Theatre_de_Spa)]]
|

|-
| [[Chang v. Virgin Mobile]]
|

|-
| [[Curry v. Audax]]
|

|-
| [[Gerlach vs. DVU]]
|

|-
| [[Internet Brands v. Holliday]]
| Litigation involving ownership of wiki material contributed by a broad community and licensed under CC BY-SA. At no point in either case was the validity of the CC license contested.

|-
| [[Jacobsen v. Katzer]]
|

|-
| [[No. 71036 N. v. Newspaper]]
| Photographer who used BY-SA licenses on his photographs had some photographs used in a Newspaper. The newspaper did not provide proper attribution. The newspaper had also used Wikipedia text without proper attribution.

|-
| [[SGAE v. Fernandez]]
|

|-
| [[SGAE v. Luis]]
|

|-
| [[TA 3560/09, 3561/09, Avi Re'uveni v. Mapa inc. ישראל: לראשונה, ביהמ"ש אכף רישיון קריאייטיב קומונס]]
|

|}
To add a new court decision to [[:Category:Case_Law|the list]], create a new page here on the wiki and add a copy of [[Template:Case_Law|the Case Law template]] and edit it to contain details of the case. Then add a link to the case to the list above.

If you are unfamiliar with creating pages, [https://www.mediawiki.org/wiki/Help:Starting_a_new_page instructions are available] There are also [https://www.mediawiki.org/wiki/Help:Templates comprehensive guides] and [https://en.wikipedia.org/wiki/Help:A_quick_guide_to_templates quick start instructions] for working with wiki templates. If you are unfamiliar with creating Wiki tables, [https://www.mediawiki.org/wiki/Help:Tables instructions are available for this as well].

For cases taking place across multiple courts, add separate pages for each decision.

Case Law

2015-12-15T01:38:27Z

CCID-rob: Recreate table of cases by hand.

There is a [[:Category:Case_Law|a listing of court decisions]] that discuss or are directly relevant to Creative Commons licenses. The decisions can come from any jurisdiction around the world. It is a list of decisions, not cases.

== Cases ==
{|

|-
| [[09-1684-A_(Lichôdmapwa_v._L'asbl_Festival_de_Theatre_de_Spa)]]
|

|-
| [[Chang v. Virgin Mobile]]
|

|-
| [[Curry v. Audax]]
|

|-
| [[Gerlach vs. DVU]]
|

|-
| [[Internet Brands v. Holliday]]
| Litigation involving ownership of wiki material contributed by a broad community and licensed under CC BY-SA. At no point in either case was the validity of the CC license contested.

|-
| [[Jacobsen v. Katzer]]
|

|-
| [[No. 71036 N. v. Newspaper]]
| Photographer who used BY-SA licenses on his photographs had some photographs used in a Newspaper. The newspaper did not provide proper attribution. The newspaper had also used Wikipedia text without proper attribution.

|-
| [[SGAE v. Fernandez]]
|

|-
| [[SGAE v. Luis]]
|

|-
| [[TA 3560/09, 3561/09, Avi Re'uveni v. Mapa inc. ישראל: לראשונה, ביהמ"ש אכף רישיון קריאייטיב קומונס]]
|

|}
To add a new court decision to [[:Category:Case_Law|the list]], create a new page here on the wiki and add a copy of [[Template:Case_Law|the Case Law template]] and edit it to contain details of the case.

If you are unfamiliar with creating pages, [https://www.mediawiki.org/wiki/Help:Starting_a_new_page instructions are available] There are also [https://www.mediawiki.org/wiki/Help:Templates comprehensive guides] and [https://en.wikipedia.org/wiki/Help:A_quick_guide_to_templates quick start instructions] for working with wiki templates.

For cases taking place across multiple courts, add separate pages for each decision.

Then add a link to the case to the list above.

If you are unfamiliar with creating Wiki tables, [https://www.mediawiki.org/wiki/Help:Tables instructions are available for this as well].

Template:Case Law Upload

2015-12-15T01:13:01Z

CCID-rob: De-SMW.

<noinclude></noinclude>
<includeonly>
<div style="display:block;margin-bottom:10px;clear:both;">
<div style="display:block;background-color:#c0c0c0;padding-left:5px;padding:3px;margin:0px;font-size:1.1em;">'''File'''</div>
<div style="padding:15px;background-color:#f4f4f4;border:1px solid #c0c0c0;">
<div style="font-size:0.9em;">{{{file description|}}}</div><br />
'''Submitting party:''' {{{related party|}}}<br />
<span style="font-size:1.3em;margin-top:10px;display:block;">'''[{{filepath:{{{uploaded|}}}}} Download]'''</span></div></div>
</includeonly>

Jacobsen v. Katzer

2015-12-15T01:11:23Z

CCID-rob: Reverted edits by CCID-rob (talk) to last revision by Rob Williams

{{Case Law
|title=Jacobsen v. Katzer
|region=United States
|court=United States Court of Appeals for the Federal Circuit
|date=2010/02/22
|description=Open source software case involving the Artistic License, involving alleged violation of the license that results in copyright infringement rather than contract violation
|summary=NOTE: This summary needs to be updated for the Feb. 2010 decision by the Federal Circuit. In an unpublished order, the Federal Circuit dismissed the case by agreement of the parties on February 22, 2010, without reaching the merits.

'''CC DIMENSION:'''

A model train hobbyist who had developed open source software brought suit against an individual and company using the software in competing proprietary software. The proprietary software did not contain the attribution information required by the Artistic license under which the open source software was released.

The District Court held that the Artistic license was a contract between the parties, and remedies for breach of the contract could only sound in contract law, not as copyright infringement. This holding was appealed to the US Court of Appeals for the Federal Circuit. Creative Commons participated in the submission of an amicus brief, asking the Court of Appeals to reverse the District Court.

The Court of Appeals found that the the terms in the Artistic license were conditions and not covenants, and that suit could be brought seeking remedies for violation of copyright rather than the more limited remedies available under contract. The appellate court remanded the case to the district court.

'''BACKGROUND ON OTHER ISSUES:'''

The case involved other issues at the district court level, including a request for a preliminary injunction against the proprietary software makers to prevent them from accusing the plaintiff of patent infringement over patents the plaintiff claimed were invalid.

'''PARTIES:'''

Plaintiff: Robert Jacobsen<br>
Defendants: Matthew Katzer, KAM Industries, Kevin Russell<br>
Amici Curiae: Creative Commons, The Linux Foundation, The Open Source Initiative, Software Freedom Law Center, The Perl Foundation, and Wikimedia Foundation<br>

'''COURTS:'''

; CC Related Issue : United States Court of Appeals for the Federal Circuit
: Judges: Michel, Prost and Faith S. Hochberg
; All Matters of the Case: United States District Court for the Northern District of California San Francisco Division
: Judge: Jeffery White

'''DATES:'''

Complaint filed 13 March 2006<br>
First District Court Order granting and denying various motions 17 August 2007<br>
Defendants Second Motion to Dismiss 21 December 2007<br>
Amici Curiae brief submitted 28 December 2007<br>
Defendants file Disclaimer in Patent 1 February 2008<br>
Court of Appeals Decision 13 August 2008<br>
Second District Court Order granting and denying various motions 5 January 2009<br>
Next scheduled in District Court for 9:00AM 30 October 2009<br>

'''CLAIMS:''' (Plead in Plaintiff’s Complaint and Plaintiff’s Amended Complaint)

CC Related Claims
* Copyright Infringement
** Plaintiff argued Defendant used Plaintiff’s software and stripped it of its Artistic license information, thereby modifying the software and violating the license.
** Plaintiff asked for statutory damages and attorneys’ fees.
** Defendant argued Plaintiff was not eligible for statutory damages or attorneys fees because the software was not registered with the US Copyright Office until after the alleged infringement occurred.
** Amici Curiae argued that violation of the Artistic license must be copyright infringement and not a contractual issue because a many people have chosen to use public licenses with the understanding that a violation of the license results in copyright infringement.
*** Used an analogy between property with trespassing by an invited guest and copyright infringement by a public license user.
* Breach of Contract
** Defendants argued there can be no breach of contract claim because there are no damages caused by breaching the Artistic License.
* Violation of the Digital Millennium Copyright Act (DMCA)
** Plaintiff argued the license identification metadata in the software files constituted copyright management information under the DMCA and that Defendants violated the DMCA when they removed this information.
** Defendants argued that a New Jersey court held that similar information in the form of a company’s logo did not constitute copyright management information so this metadata does not count under the DMCA.

Remainder of Claims
* Unenforceability of several patents
** Plaintiff claimed that frauduantly obtained a number of patents on model railroad software by intentionally not disclosing prior art in applications submitted to the USPTO.
* Non-infringement of patents
** Plaintiff asked the court for a declaratory judgment stating that Plaintiff was not infringing Defendant’s patents because the patents were invalid.
* Anti-Trust Violation of Sherman Act
** Plaintiff claimed Defendant violated the Sherman Act; (a Federal Statute that limits monopolies) by attempting to harass and frighten their competitors out of business.
* Unfair Competition
** Plaintiff claimed Defendant engaged in unfair competition (in violation of California State Law) by attempting to monopolize the market through the use of invalid patents to harass competitors out of business.
* Cybersquatting
** Plaintiff claimed Defendant was cybersquatting on a trademark associated with Plaintiff’s open source project by registering the trademark as a domain name and then transferring that domain name with a prohibition of further transfer.
* Libel
** Plaintiff claimed Defendant falsely accused Plaintiff of patent infringement and sent letters requesting information to Plaintiff’s employer and the US Department of Energy.
* Unjust Enrichment

'''ISSUES ADDRESSED BY COURT:'''

CC Issue
<div style="margin-left: 2em">
Court of Appeals Ruling
* Copyright Infringement
** The court looked at “the ability of a copyright holder to dedicate certain work to free public use and yet enforce an ‘open source’ copyright license to control the future distribution and modification of that work.”
** Court vacated the District Courts denial of the preliminary injunction for copyright infringement.
** The court held that the lack of monetary exchange in open source licensed projects does not mean there are no benefits for the copyright holder.
** The court held that the terms in the license are conditions under which the license is granted not covenants that are part of a contract.
** The court held that the Artistic License is enforceable under copyright infringement.
District Court’s 17 August 2007 Ruling (Prior to Court of Appeals)
* Copyright Infringement
** Court denied preliminary injunction for copyright infringement.
*** The court held that the matter was a contractual issue and not copyright infringement because the software was licensed under an open source license.
*** The court held that a promise not to sue for copyright infringement is implicit in the open source license.
** Court dismissed the claim for attorneys’ fees and statutory damages because the Plaintiff did not register the software with the US Copyright Office until after the infringement occurred.
District Court’s 5 January 2009 Ruling (After remanded by Court of Appeals)
* Copyright Infringement
** Court denied plaintiff’s motion for preliminary injunction because the plaintiff did not meet the required burden of showing a specific and actual harm suffered as the result of the copyright infringement.
</div>
Remainder of Issues
<div style="margin-left: 2em">
District Court’s 17 August 2007 Ruling
* Unfair Competition
** Court dismissed the claim for unfair competition. Unfair competition requires the Plaintiff to have lost money or property, but the Plaintiff did not have any expectation of receiving money or property for his software programs because they were given away for free on the internet.
** Claim is preempted by Federal Copyright Law.
*** The US Copyright Act specifically says it overrides all formerly existing common law and State statutes relating to copyright. 17 U.S.C. § 301.
* Unjust Enrichment
** Court dismissed the claim for unjust enrichment. Unjust enrichment requires that both parties expect compensation for the services rendered. Benefits received from using open source software cannot be unjust because open source software is distributed freely.
** There is no separate cause of action for unjust enrichment in California.
** Claim is preempted by Federal Copyright Law.
* Cybersquatting
** Court dismissed the claim for cybersquatting as moot. Plaintiff submitted documentation showing that WIPO had transferred the domain name to Plaintiff.
District Court’s 5 January 2009 Ruling (After Court of Appeals Remand)
[This order was a response to a motion by the plaintiff for preliminary injunction against the defendant and a motion by defendant to dismiss a number of the plaintiff’s claims. Therefore, most of the rulings in this order are only whether or not an issue can stay in the case.]
* Unenforceability of Patents
** Court dismissed the claims regarding the unenforceability of patents for mootness because the defendant had already filed a Disclaimer in Patent.
* Breach of Contract
** Court dismissed the breach of contract claim for failure to state a specific harm; the plaintiff was unable to show any damages stemming from breach of the Artistic license.
** Court dismissed the breach of contract claim also on grounds of federal preemption because the matters from which the claim arose are covered by the US Copyright Act and therefore cannot be litigated under state law claims.
* DMCA Violation
** Court held that the claim for violation of the DMCA could stand, because it appeared from the pleadings that the information required by the Artistic license could qualify as copyright management information under the DMCA.
* Attorney Fees
** Court refused to strike plaintiff’s claim for attorneys’ fees because at this point it was not clear that plaintiff’s work was not infringed after the plaintiff registered his work.
</div>

'''HOLDING:'''

Violations of open source and public licenses are enforceable through copyright infringement claims, not just as breaches of contract.
}}
{{Case Law Upload
|uploaded=Jacobson v katzer fed cir ct of appeals decision.pdf
|file description=535 F.3d 1373 (Fed. Cir. 2008)
|related party=Other
}}
{{Case Law Upload
|uploaded=Jacobson v katzer cc brief.pdf
|file description=CC's Amicus brief
|related party=Other
}}
{{Case Law Upload
|uploaded=Jacobson v katzer complaint for declaratory judgment.pdf
|file description=Plaintiff's complaint for declaratory judgement
|related party=Plaintiff
}}
[[Category:USA]]

Template:Case Law

2015-12-15T01:11:08Z

CCID-rob: Tag typo

<noinclude>
This is the 'Case Law' template. Edit the page to see the template text.
</noinclude>
<includeonly>
<div style="overflow-y:auto;display:block;">
<div style="float:right;padding:15px;padding-bottom:0px;background-color:#f4f4f4;margin-bottom:10px;margin-left:20px;display:inline-block;width:33%">
<b>Country/Region</b><br />
{{{region|}}}

<b>Court name</b><br />
{{{court|}}}

<b>Published</b><br />
{{{date|}}}

<b>More decisions in this case</b><br />
{{{related decision|}}}


</div>

<h2>Description</h2>
{{{description|}}}

<h2>Case summary</h2>
{{{summary|}}}

[[Category:Case Law]]
</div></includeonly>

Template:Case Law

2015-12-15T01:10:31Z

CCID-rob: Improve design.

<noinclude>
This is the 'Case Law' template. Edit the page to see the template text.
</noinclude>
<includeonly>
<div style="overflow-y:auto;display:block;">
<div style="float:right;padding:15px;padding-bottom:0px;background-color:#f4f4f4;margin-bottom:10px;margin-left:20px;display:inline-block;width:33%">
<b>Country/Region</b><br />
{{{region|}}}

<b>Court name</b><br />
{{{court|}}}

<b>Published</b><br />
{{{date|}}}

<b>More decisions in this case</b><br />
{{{related decision|}}}


</div>

</h2>Description</h2>
{{{description|}}}

<h2>Case summary</h2>
{{{summary|}}}

[[Category:Case Law]]
</div></includeonly>

Template:Case Law

2015-12-15T01:09:02Z

CCID-rob: Clean up de-SMWing.

<noinclude>
This is the 'Case Law' template. Edit the page to see the template text.
</noinclude>
<includeonly>
<div style="overflow-y:auto;display:block;">
<div style="float:right;padding:15px;padding-bottom:0px;background-color:#f4f4f4;margin-bottom:10px;margin-left:20px;display:inline-block;width:33%">
<b>Country/Region</b><br />
{{{region|}}}

<b>Court name</b><br />
{{{court|}}}

<b>Published</b><br />
{{{date|}}}

<b>More decisions in this case</b><br />
{{{related decision|}}}


</div>
</h3>Case description|Description</h3>
{{{description|}}}

<h3>Case summary</h3>
{{{summary|}}}

[[Category:Case Law]]
</div></includeonly>

Jacobsen v. Katzer

2015-12-15T01:07:16Z

CCID-rob: Template rebuild.

Template:Case Law

2015-12-15T01:05:56Z

CCID-rob: De-mediawiki.

<noinclude>
This is the 'Case Law' template. Edit the page to see the template text.
</noinclude>
<includeonly>
<div style="overflow-y:auto;display:block;">
<div style="float:right;padding:15px;padding-bottom:0px;background-color:#f4f4f4;margin-bottom:10px;margin-left:20px;display:inline-block;width:33%">
<b>Country/Region</b><br />
{{{region|}}}

<b>Court name</b><br />
{{{court|}}}

<b>Published</b><br />
{{{date|}}}

<b>More decisions in this case]</b><br />
{{{related decision|}}}

'''[[Property:Related case law|Related cases]]'''<br />
{{{related cases|}}}
</div>
</h3>Case description|Description</h3>
{{{description|}}}

<h3>Case summary</h3>
{{{summary|}}}

[[Category:Case Law]]
</div></includeonly>

Template:OER Policy

2015-11-10T22:46:43Z

CCID-rob: Fix formatting in image.

<noinclude>
This is the "OER Policy" template.
It should be called in the following format:
<pre>
{{OER Policy
|OER Policy Title=
|OER Policy URL=
|Description=
|Author=
|OER Policy Date=
|OER Policy Status=
|Language code=
|OER Policy Jurisdiction=
|Country=
|OER Policy Institution=
|Tag=
|License short name=
}}
</pre>
To create a new OER Policy, first search for its name using the search box on this page.

If it has already been created, you can edit it by going to that page and clicking on the "Edit" tab.

If it does not already exist you can click on the "Create the page" link at the top of the search results page:

[[File:Create-new-page.png]]

Paste a copy of this template onto that page, and fill out its fields:

[[File:Creating-new-policy2.png]]

Then save it by clicking the "Save Page" button at the bottom of the page:

[[File:Saving-new-policy.png]]

If you need help with this, please contact us via our GitHub issues page - https://github.com/creativecommons/wiki/issues .
</noinclude><includeonly>
__NOTOC__
<div style="position: relative;">
'''[[OER Policy Registry|OER Policy Registry Home]]''' :: '''[http://wiki.creativecommons.org{{localurl:{{PAGENAME}}|action=edit}} Edit this policy]''' :: '''[{{fullurl:Special:ExportRDF/{{PAGENAME}}}} RDF]'''
<div style="max-width:25%; position: relative; top: 0; float: left; padding: 15px;margin-top: 0px;border: 1px solid #c0c0c0;background:#f0f0f0;overflow:hidden; display:inline-block;margin-left:20px;margin-bottom:10px;">
<span title="Year the policy or legislation was: first Introduced (Bill); enacted (Legislation - e.g. Act or Regulation); and published (Institution policy)."><strong>Date</strong></span>: {{{OER Policy Date|}}}<br />
<span title="The status of the policy: proposed, current, replaced or revoked"><strong>Policy Status</strong></span>: {{{OER Policy Status|}}}<br />
<span title="Language code"><strong>Language</strong></span>: {{{Language code|}}}<br />
<span title="The jurisdiction the policy applies to."><strong>Jurisdiction</strong></span>: {{{OER Policy Jurisdiction|}}}<br />
<span title="The country of origin for the policy"><strong>Country</strong></span>: {{{Country|}}}<br />
<span title="The Government or Institution that has proposed or passed the legislation or policy."><strong>Institution</strong></span>: {{{OER Policy Institution|}}}<br />
<span title="The license of the policy itself"><strong>Policy license</strong></span>: {{{License short name|}}}<br />
<span title="Searchable keywords that relate to the policy."><strong>Tags</strong>:</span> {{{Tag|}}}<br /></div>
<div style="width: 58%; position: relative left; top: 0; text-align:left; padding: 8px;overflow: auto;">
<span title="Key identifier of the policy or legislation (eg: name, legislative number, etc.)"><strong>Policy Title:</strong> </span>{{{OER Policy Title|}}} -
<strong>[{{{OER Policy URL|}}} Go to the policy]</strong><br />
<span title="The name of the person(s) who drafted the policy and/or are associated with the policy."><strong>Author(s):</strong> </span>{{{Author|}}}<br />
<span><strong>Description:</strong> </span>{{{Description|}}}</div>
<div style="width: 58%; padding: 8px; overflow: auto;">
<strong>Policy Comments</strong>:
[[Category:OER Policy Registry]]
</includeonly>

File:Creating-new-policy2.png

2015-11-10T22:33:02Z

CCID-rob:

File:Creating-new-policy.png

2015-11-10T22:31:13Z

CCID-rob: CCID-rob uploaded a new version of File:Creating-new-policy.png

Template:OER Policy

2015-11-10T22:17:41Z

CCID-rob: Add illustrations to help clarify instructions.

<noinclude>
This is the "OER Policy" template.
It should be called in the following format:
<pre>
{{OER Policy
|OER Policy Title=
|OER Policy URL=
|Description=
|Author=
|OER Policy Date=
|OER Policy Status=
|Language code=
|OER Policy Jurisdiction=
|Country=
|OER Policy Institution=
|Tag=
|License short name=
}}
</pre>
To create a new OER Policy, first search for its name using the search box on this page.

If it has already been created, you can edit it by going to that page and clicking on the "Edit" tab.

If it does not already exist you can click on the "Create the page" link at the top of the search results page:

[[File:Create-new-page.png]]

Paste a copy of this template onto that page, and fill out its fields:

[[File:Creating-new-policy.png]]

Then save it by clicking the "Save Page" button at the bottom of the page:

[[File:Saving-new-policy.png]]

If you need help with this, please contact us via our GitHub issues page - https://github.com/creativecommons/wiki/issues .
</noinclude><includeonly>
__NOTOC__
<div style="position: relative;">
'''[[OER Policy Registry|OER Policy Registry Home]]''' :: '''[http://wiki.creativecommons.org{{localurl:{{PAGENAME}}|action=edit}} Edit this policy]''' :: '''[{{fullurl:Special:ExportRDF/{{PAGENAME}}}} RDF]'''
<div style="max-width:25%; position: relative; top: 0; float: left; padding: 15px;margin-top: 0px;border: 1px solid #c0c0c0;background:#f0f0f0;overflow:hidden; display:inline-block;margin-left:20px;margin-bottom:10px;">
<span title="Year the policy or legislation was: first Introduced (Bill); enacted (Legislation - e.g. Act or Regulation); and published (Institution policy)."><strong>Date</strong></span>: {{{OER Policy Date|}}}<br />
<span title="The status of the policy: proposed, current, replaced or revoked"><strong>Policy Status</strong></span>: {{{OER Policy Status|}}}<br />
<span title="Language code"><strong>Language</strong></span>: {{{Language code|}}}<br />
<span title="The jurisdiction the policy applies to."><strong>Jurisdiction</strong></span>: {{{OER Policy Jurisdiction|}}}<br />
<span title="The country of origin for the policy"><strong>Country</strong></span>: {{{Country|}}}<br />
<span title="The Government or Institution that has proposed or passed the legislation or policy."><strong>Institution</strong></span>: {{{OER Policy Institution|}}}<br />
<span title="The license of the policy itself"><strong>Policy license</strong></span>: {{{License short name|}}}<br />
<span title="Searchable keywords that relate to the policy."><strong>Tags</strong>:</span> {{{Tag|}}}<br /></div>
<div style="width: 58%; position: relative left; top: 0; text-align:left; padding: 8px;overflow: auto;">
<span title="Key identifier of the policy or legislation (eg: name, legislative number, etc.)"><strong>Policy Title:</strong> </span>{{{OER Policy Title|}}} -
<strong>[{{{OER Policy URL|}}} Go to the policy]</strong><br />
<span title="The name of the person(s) who drafted the policy and/or are associated with the policy."><strong>Author(s):</strong> </span>{{{Author|}}}<br />
<span><strong>Description:</strong> </span>{{{Description|}}}</div>
<div style="width: 58%; padding: 8px; overflow: auto;">
<strong>Policy Comments</strong>:
[[Category:OER Policy Registry]]
</includeonly>

File:Saving-new-policy.png

2015-11-10T22:16:42Z

CCID-rob:

File:Creating-new-policy.png

2015-11-10T22:15:48Z

CCID-rob:

File:Create-new-page.png

2015-11-10T22:11:35Z

CCID-rob:

Giving A User Edit Permission

2015-11-05T19:29:34Z

CCID-rob: Fix images and link.

If you are an RC or a creativecommons.org member of staff, you have the ability to grant other users edit permission on wiki.creativecommons.org .

Please only do this for affiliates or for people who have contacted you with evidence of their desire to edit the wiki in good faith. Prior to instituting this system we had a lot of trouble with spam and vandalism.

To grant someone edit permission on the wiki:

[[File:Ccid-at-top-right-of-page.png ]]

1. Get the user's wiki.creativecommons.org login name. If they have an account on Wikipedia or another wiki, this is different to that.The user can find their login name by logging in to the wiki using their CCID and checking the top right of the page.

2. Log in to the wiki yourself.

[[File:User-rights-management-form.png ]]

3. Go to: [[Special:UserRights]]

4. Enter the user's wiki login name in the "Enter a username" field. **This is case sensitive**.

5. Press the "Edit user groups" button. This will take you to the "Manage user groups" page, or complain that the user cannot be found. If the user cannot be found, check that you entered the user's login name correctly (remember that it is case sensitive), and ask the user to confirm its spelling and capitalization.

[[File:Groups-you-can-change.png]]

6. On the "Manage user groups" page, select the checkbox for either the "affiliate" or "approved" group. For affiliates, add them to the "affiliate" group. For other people, add them to the "approved" group. You do not need to select both.

7. In the "Reason" field, provide information on why the user is being added to the group. e.g. "New member of the CC Cagliostro team" or "Emailed Rob with proof of involvement in the Open Information Institute" or "See CC helpdesk ticket #12345678". **Remember that this is publicly viewable, so do not place sensitive information here**.

8. Press the "Save user groups" button.

9. Contact the user to let them know there are now able to edit the wiki.

If you or they have any problems, please [http://labs.creativecommons.org/contact/ contact the tech team].

File:Ccid-at-top-right-of-page.png

2015-11-05T19:27:54Z

CCID-rob:

File:User-rights-management-form.png

2015-11-05T19:26:33Z

CCID-rob:

Giving A User Edit Permission

2015-11-05T19:21:17Z

CCID-rob: Initial instructions.

If you are an RC or a creativecommons.org member of staff, you have the ability to grant other users edit permission on wiki.creativecommons.org .

Please only do this for affiliates or for people who have contacted you with evidence of their desire to edit the wiki in good faith. Prior to instituting this system we had a lot of trouble with spam and vandalism.

To grant someone edit permission on the wiki:

[[File:Where-to-find-ccid.png ]]

1. Get the user's wiki.creativecommons.org login name. If they have an account on Wikipedia or another wiki, this is different to that.The user can find their login name by logging in to the wiki using their CCID and checking the top right of the page.

2. Log in to the wiki yourself.

[[File:User-rights-management-page.png]]

3. Go to: [https://wiki.creativecommons.org/wiki/Special:UserRights](https://wiki.creativecommons.org/wiki/Special:UserRights)

4. Enter the user's wiki login name in the "Enter a username" field. **This is case sensitive**.

5. Press the "Edit user groups" button. This will take you to the "Manage user groups" page, or complain that the user cannot be found. If the user cannot be found, check that you entered the user's login name correctly (remember that it is case sensitive), and ask the user to confirm its spelling and capitalization.

[[File:Groups-you-can-change.png]]

6. On the "Manage user groups" page, select the checkbox for either the "affiliate" or "approved" group. For affiliates, add them to the "affiliate" group. For other people, add them to the "approved" group. You do not need to select both.

7. In the "Reason" field, provide information on why the user is being added to the group. e.g. "New member of the CC Cagliostro team" or "Emailed Rob with proof of involvement in the Open Information Institute" or "See CC helpdesk ticket #12345678". **Remember that this is publicly viewable, so do not place sensitive information here**.

8. Press the "Save user groups" button.

9. Contact the user to let them know there are now able to edit the wiki.

If you or they have any problems, please [http://labs.creativecommons.org/contact/ contact the tech team].

File:Where-to-find-ccid.png

2015-11-05T19:16:35Z

CCID-rob: CCID-rob uploaded a new version of File:Where-to-find-ccid.png

File:Where-to-find-ccid.png

2015-11-05T18:55:32Z

CCID-rob:

File:Groups-you-can-change.png

2015-11-05T18:53:48Z

CCID-rob:

Translating CC Deeds

2015-10-01T21:11:30Z

CCID-rob: Fix Transifex link (Freshdesk 15523).

The license engine, deeds and legal code hosted at creativecommons.org are all translated directly by CC [http://creativecommons.org/international/ jurisdiction partner institutions]. While there are usually people at the partner institutions who handle these translations, you can request to become a member of the translation team for any given language using the directions below under '''For Translators'''.

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

=== For CC Project Leads ===
To set up translations for your jurisdiction's language(s), please:
# Select one or more people to manage your translations
# Each translator should create an account as described below

=== For Translators ===
To translate to the language that interests you, please:
# Go to [http://www.transifex.net/accounts/register/ Transifex.net] and create an account. Once you have validated your email address, log in.
# Go to the [https://www.transifex.com/nkinkade/CC/ Translation Teams] tab for the Creative Commons project.
#* If a team already exists for the language that interestes you, then click on that language and then click the "Join this team" button, which will allow you to send a message to the coordinator for that language asking then to allow you to become a member of that team.
#* If a team doesn't yet exist for the language that interests you then simply click the "Request a new team" button at the bottom of the list of available teams. This will send an email to the administrator for the Creative Commons project requesting the new team.

=== General Notes About Translating ===

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

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

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

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

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

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

==== Whitespace Characters ====

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

==== Wiki Links ====

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

[[Category:Translation Project]]

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

'''<tt>staging.creativecommons.org</tt>''' is updated with the newest translations every 15 minutes.

The live site however is updated manually. Updates get pushed periodically with other software updates. If you would like to have your translations updated at any time, email <tt>webmaster AT creativecommons DOT org</tt>.

{{Translations
| articles = Pt:Traduzir os Resumos Para Leigos CC
}}

[[Category:Legal]]

Main Page

2015-09-30T00:34:58Z

CCID-rob: Affiliates should ask RCs for edit approval.

<div style="font-size:125%; line-height:1.75em; margin-bottom:1.75em;"><strong>Welcome to the CC Wiki!</strong> The purpose of this wiki is to help you learn more about CC and give you a chance to collaborate with us. CC relies on its community of users to keep it strong, so now is your chance to '''get involved'''! To learn more about wikis and how to edit them, visit our [[Getting Started]] page.</div>

<div style="color: #d00; margin-bottom:1.75em;"><strong>Please login with your CCID by clicking the log in link above</strong> -- If you have any questions or problems, please write to info@creativecommons.org. Until January 1st, 2016 we will convert your old CC Wiki account to your CCID account.</div>

<div style="color: #d00; margin-bottom:1.75em;"><strong>Accounts must be approved before you can edit the CC Wiki</strong> -- Affiliates, please write to your RC. Otherwise, please write to info@creativecommons.org providing your CCID and something to prove you are a real person who wants to edit the Wiki.</div>

<div class="row">
<div class="col-md-6">
<h2 style="padding-top:0px;margin-top:15px;">More about CC</h2>

=== [[Frequently_Asked_Questions | FAQ]] ===
Page of Frequently Asked Questions, with information on all aspects of Creative Commons licensing.

=== [[Developers]] ===
Resources for software developers interested in developing tools to facilitate the use and growth of Creative Commons licenses and standards.

=== [[Marking]] ===
List of best practices for marking content with CC licenses.

=== [[Web Integration]] ===
Everything a web-based (media) hosting site needs to know to integrate CC and CC-related features.

=== [[CC_Affiliate_Network|Affiliate Network]] ===
The CC Affiliate Network consists of 100+ affiliates working in over 79 jurisdictions to support and promote CC activities around the world.

=== [[OER|Open Educational Resources]] ===
Read about Open Educational Resources (OER) and how Creative Commons supports the movement.
</div>
<div class="col-md-6 well">
<h2 style="padding-top:0px;margin-top:15px;">Wiki Projects</h2>

===[[4.0|Version 4.0 of the CC License Suite]]===
CC has released a new version of its core license suite, version 4.0.

=== [[Case Studies]] ===
Past, present, and future "CC success stories" to help measure the impact of Creative Commons around the world. Everyone is encouraged to contribute!

=== [[Content Directories]] ===
A list of organizations and projects powered with Creative Commons licenses.

===[[Events]]===
Upcoming Creative Commons-relevant events around the world: get details, add an event, learn how to start a ccSalon, and sign up for our events mailing list.

=== [[OER Project]] ===
Contribute to CC's OER wiki-databases and pages.

=== [[Documentation]] ===
Large-scale CC specifications, recommendations, white papers, tutorials.

=== [[Translate]] ===
Help us translate our wiki, web content, videos and more.

</div>
</div>

[[Category:Volunteer]]
[[Category:Role]]
[[Category:Project]]
[[Category:Developer]]
[[Category:Creator]]
[[Category:Lawyer]]
[[Category:Guide]]
[[Category:Help]]

__NOTOC__
__NOEDITSECTION__

Work-lookup

2015-09-24T20:29:18Z

CCID-rob: Remove CC Network mentions (except those of historical interest).

This page describes the work-lookup service that was implemented by the [[CC Network]]. This service allowed software to look up a work registration based on the URI.

See the [https://web.archive.org/web/20140214102313/http://labs.creativecommons.org/~nathan/oscri/describing-registrations.html draft specification] for details.

{{lowercase}}
[[Category:CC Network]]