Return to Summary page

This template is to be used by members of the CC Affiliate Network to create an Affiliate Team Roadmap for their jurisdiction. By "Affiliate Team" we mean all institutions and individuals with whom CC has executed a Memorandum of Understanding (MOU) within each jurisdiction.

The purpose of the roadmap is to identify activities and goals for the upcoming months and year. All roadmaps will be posted on the jurisdiction wiki page (wiki.creativecommons.org/Jurisdiction#Roadmap). We ask that only one Affiliate Team Roadmap be created for each jurisdiction. Please collaborate and coordinate with other Affiliates in your jurisdiction. Sample of a completed Roadmap.

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

---

Affiliate Team Roadmap

• Date submitted:
• Timespan of this roadmap:

Team information

• Jurisdiction:

• Complete list of all members of the Affiliate Team, their roles, and field(s) of expertise

• Date of earliest MOU in jurisdiction

• Self-Identified Region(s), i.e. Europe, Africa, Asia-Pacific, Latin America, North America, Arab world:
  • Why do you identify yourself as being part of the listed region(s)?

Vision

• Why is Creative Commons important for the jurisdiction?

• What do you think makes a successful jurisdiction project?

• How do you see the jurisdiction project contributing to the CC Affiliate Network?

Community

• Describe the communities that are currently active in the project.
  • How will you continue to engage with these communities?

• Describe the communities (existing or new) that you plan to focus on during the timeframe covered by this roadmap?
  • How do you plan to engage with these communities?

Priority Goals

• What are the three most important focus areas on which the Affiliate Team will work during this time period? Please consider community building and adoption goals among your priorities.

1. Focus-area:

• • Why is it important?
  • Which communities will benefit?

2. Focus-area:

• • Why is it important?
  • Which communities will benefit ?

3. Focus-area:

• • Why is it important?
  • Which communities will benefit?

Project Outputs

• Detail tangible project outputs (e.g., events, papers, blog posts, video/films, etc.) for each focus area including an expected date of completion. See also Timeline.

The outputs we plan to complete are as follows:

1. Focus-area
   1. Project Output
   2. Expected start date - Expected date of completion
   3. Team Member(s) Responsible
   4. How will this output help achieve your goals?
2. Focus-area
   1. Project Output
   2. Expected start date - Expected date of completion
   3. Team Member(s) Responsible
   4. How will this output help achieve your goals?
3. Focus-area
   1. Project Output
   2. Expected start date - Expected date of completion
   3. Team Member(s) Responsible
   4. How will this output help achieve your goals?

Metrics

Please consider using trackable statistics (such as web traffic or number of license adoptions) when applicable, but only if meaningful.

• How will you measure and evaluate your impact on focus-area 1?
• How will you measure and evaluate your impact on focus-area 2?
• How will you measure and evaluate your impact on focus-area 3?

Resources Required

People

• What human resources or expertise must the team seek out or add to your existing resources, if any, in order to achieve your priority goals?
  • How will you involve these people?

Technology

• What technology resources must the team seek out or add to your existing resources, if any, in order to achieve your priority goals?
  • How will you obtain these technology resources?

Materials

• What material resources must the team seek out or add to your existing resources, if any, in order to achieve your priority goals?
  • How will you obtain these material resources?

Other

• What other resources must the team seek out or add to all the other resources, if any, in order to achieve your priority goals?
  • How will you obtain these other resources?

Sustainability and Scalability

• How will you ensure your goals will be completed if unforeseen circumstances interrupt the project, such as changes in the leadership of the project or outputs taking longer to complete than anticipated?

• How will you communicate the project's on-going progress and setbacks within the jurisdiction and the CC Affiliate Network? (e.g. email list updates, meetings, press releases)

• How will you document the project so that others may replicate or learn from your efforts?

Collaboration

• Please have a look at other roadmaps.
  • How could the jurisdiction's plans help drive or support other jurisdictions' activities?
  • What are other jurisdictions doing that might support or contribute to the project?

• Would you be interested in mentoring new jurisdiction teams?

• Conversely, would you be interested in having a mentor from a more experienced jurisdiction team?

Regional

• Suggest three possible projects on which you can collaborate with other teams on a regional level. If you are not yet involved with the regional network, please contact the regional spokesperson (if any) or notify CC HQ to put you in touch with others.

• • How do you plan to contribute to these projects?

Translation

• In what language(s) will you promote CC in the jurisdiction and why?
  • In which of these languages are licenses already available? CC0?
  • Into which of the remaining languages do you intend to translate the licenses? CC0?

• How will you involve the local language(s) community?

Misc.

• Any additional comments?

---

(Optional) Timeline 2010-2011

1st Quarter (Sep / Oct / Nov)

1. Activity; (Person/Resources)
2. Activity; (Person/Resources)
3. Activity; (Person/Resources)

2nd Quarter (Dec / Feb / Mar)

1. Activity; (Person/Resources)
2. Activity; (Person/Resources)
3. Activity; (Person/Resources)

3rd Quarter (Apr / May / Jun)

1. Activity; (Person/Resources)
2. Activity; (Person/Resources)
3. Activity; (Person/Resources)

4th Quarter (Sep / Oct / Nov)

1. Activity; (Person/Resources)
2. Activity; (Person/Resources)
3. Activity; (Person/Resources)

'Remarks:'