Difference between revisions of "MOU and Policies Summary"
(→Leaving Feedback) |
(→Leaving Feedback) |
||
Line 9: | Line 9: | ||
At the top of each page, you will find a link to that document's discussion page. Please click the link and add your comments to the page. You may also email comments privately to CC's General Counsel, Diane Peters (diane [at] creativecommons [dot] org). | At the top of each page, you will find a link to that document's discussion page. Please click the link and add your comments to the page. You may also email comments privately to CC's General Counsel, Diane Peters (diane [at] creativecommons [dot] org). | ||
− | + | We hope you will contribute. | |
==Documents Available for Comment== | ==Documents Available for Comment== |
Revision as of 20:32, 15 October 2010
Welcome to the MOU and Polices Summary Page!
As Creative Commons works to improve its CC Affiliate Network, we want to ensure that our current Affiliates are part of the process. To this end, we invite you to read the updated Memorandum of Understanding (which will replace all existing MOUs and affiliate-related agreements) and our updated policies that particularly impact our Affiliates. We encourage you to leave feedback.
Contents
Leaving Feedback
To leave feedback, you will need to login to the wiki. You can login or create an account here. At the top of each page, you will find a link to that document's discussion page. Please click the link and add your comments to the page. You may also email comments privately to CC's General Counsel, Diane Peters (diane [at] creativecommons [dot] org).
We hope you will contribute.
Documents Available for Comment
Memorandum of Understanding (MOU)
Key Points:
- Detailing of responsibilities of CC and Affiliates for those activities
- Provides for license porting and translation of CC0
- Lightweight reporting structure for better collaboration and feedback
- Open communication channels
- Modularization (i.e., breakout) of different program-related activities, for clarity
-
- Modularization means that the different sections, or modules, in the sample MOU will be selected for inclusion in a specific MOU based on who is signing the MOU and what activities are important to the jurisdiction. Examples of how the modules work: Teams that have already ported the licenses to the jurisdiction will not have Section 1(a) "Adaption/Porting of CC Licenses"; Public Lead MOUs might not include Section 1(d) "Advisory on Law and Legal Developments"; etc.
Internet Services Policy
Key Points:
- Allows CC jurisdictions to manage and run their own websites, Facebook pages, Twitter ids and other internet services in order to better engage with their communities
- Clarifies who is responsible for which aspects of these services
- Provides detailed information for domain name registrations
- Will have an accompanying non-lawyer information sheet, breaking down the provisions in the policy for the people who actually set-up and maintain the internet services
Merchandising Policy
Key Points:
- Creative Commons trademarks and logos (CC Marks) are valuable and need to be protected. CC Marks include jurisdiction-specific marks designed by Affiliates.
- Affiliates may use the trademarks and logos in additional ways, beyond the permissions granted the general public, subject to conditions.
- CC will provide schwag to give away at launch parties.
- Affiliates may give away or sell merchandise using the CC Marks at CC-related events that are consistent with our mission and purpose.
- Proceeds from sales may only be used to recoup direct costs and thereafter to perform obligations under the MOU.
Other Documents and Policies
These are some of the other Creative Commons policies and documents that are being updated but are not formally submitted for review or comment by Affiliates. Of course, your comments and suggestions for improving these are always welcome - please email those to CC's General Counsel, Diane Peters (diane [at] creativecommons [dot] org).
Note that the Trademark Policy and License Porting Protocol are referenced in the updated MOU. Those will be posted for your reference soon, though the License Porting Protocol is only relevant to Affiliates who have not yet versioned to 3.0 or started the porting process.
The Roadmap Template will be of interest to Affiliates because all Affiliates will be expected (at or before signing a new MOU) to submit a Roadmap about the project(s) they agree to undertake in the MOU.
Trademark Policy (updated)
Forthcoming
License Porting Protocol
Forthcoming
Roadmap
Sample of a completed Roadmap