Internal administration and Timeline - Revision history

CCID-georgeharipopescu: Updated the page to reflect the new Global Network structure

2018-05-26T06:20:03Z

Updated the page to reflect the new Global Network structure

CCID-diane peters: /* Developing a Timeline */

2011-09-28T16:25:52Z

‎Developing a Timeline

CCID-diane peters: /* Developing a Timeline */

2011-09-28T16:25:24Z

‎Developing a Timeline

CCID-diane peters: /* Developing a Timeline */

2011-09-28T16:13:17Z

‎Developing a Timeline

CCID-diane peters: /* Developing a Timeline */

2011-09-28T16:12:09Z

‎Developing a Timeline

CCID-diane peters: /* Developing a Timeline */

2011-09-28T16:10:40Z

‎Developing a Timeline

CCID-diane peters: /* Developing a Timeline */

2011-09-28T16:08:40Z

‎Developing a Timeline

CCID-diane peters at 16:07, 28 September 2011

2011-09-28T16:07:58Z

CCID-diane peters: /* Developing a timeline */

2009-08-19T00:46:11Z

‎Developing a timeline

CCID-diane peters: /* Internal Administration */

2009-08-19T00:45:26Z

‎Internal Administration

@@ Line 1: / Line 1: @@
 Back to [[Worldwide Overview]] >> Step II. [[Project Leads sign a Memorandum of Understanding (MOU) with Creative Commons]]
 =Internal Administration=
@@ Line 5: / Line 7: @@
 ==Mailing Lists==
-At this time, CC will announce the Project Leads and the Affiliate Institution on our mailing list and on our website. There are other recommended Creative Commons mailing lists, which you may choose to join and contribute to as well.
+At this time, CC will announce the Project Leads and the individual and institutional members on our mailing list and [https://network.creativecommons.org/ on our website]. There are other recommended Creative Commons mailing lists, which you may choose to join and contribute to as well.
-Furthermore, we will provide your jurisdiction with its own mailing list, which can be used to host discussions about the license drafts and coordinate events. Please invite to your list interested and valuable stakeholders in your region. Examples of key stakeholders include prominent commentators on copyright in your jurisdiction, Wikipedia leaders in relevant region or language, and potential license adaptors  in your area.
+Furthermore, we will provide your Chapter with its own mailing list, which can be used to host discussions about the license drafts and coordinate events. Please invite to your list interested and valuable stakeholders in your region. Examples of key stakeholders include prominent commentators on copyright in your jurisdiction, Wikipedia leaders in relevant region or language, and potential license adaptors in your area.
-We encourage you use the mailing list as tool to involve and consult the members of your community, and also keep them informed about developments in Creative Commons projects, both local and worldwide.
+We encourage you to use the mailing list as a tool to involve and consult the members of your community, and also keep them informed about developments in Creative Commons projects, both local and worldwide.
 ==Developing a Timeline==
-If license porting is an approved activity for your team, the next step is to develop a timeline collaboratively with CC headquarters.  Each step, especially the launch date, must be coordinated closely with CC.  It is important to understand that the timeline serves as a guideline only.  We often find it necessary to extend deadlines in order to have a full opportunity to discuss legal and porting issues with your team.  Please do not announce expected launch dates for the licenses without first obtaining the approval of CC.
+If license translation is an approved activity for your team, the next step is to develop a timeline collaboratively with CC headquarters. Each step, especially the launch date, must be coordinated closely with CC Legal.  It is important to understand that the timeline serves as a guideline only. We often find it necessary to extend deadlines in order to have a full opportunity to discuss legal and translation issues with your team. Please do not announce expected launch dates for the licenses without first obtaining the approval of CC.
 Please find below a suggested timeframe:
-* Legal Project Lead produces a first draft of BY-NC-SA, including re-translation into English (when ported licenses will be in another language) and chart of substantial legal changes detailing the reasons why changes to the unported are necessary: '''''one month'''''
+* Legal Project Lead produces the first draft of BY-NC-SA and chart of substantial legal changes detailing the reasons why changes are necessary: '''''one month'''''
 * CC reviews the first draft: '''''one month'''''
 * CC returns comments to the team, and further drafts and comments are exchanged: '''''one to two months'''''
@@ Line 24: / Line 26: @@
 * Legal Project Lead produces draft incorporating comments (if any) from the public discussion process: '''''two weeks'''''
 * CC reviews draft: '''''two weeks'''''
-*  Legal Project Lead produces the five other licenses, reviewed and proofed with CC:  '''''one month'''''
+* Legal Project Lead produces the five other licenses, reviewed and proofed with CC:  '''''one month'''''
-* Project Leads arrange any necessary translation and customization of the Commons Deed, the FAQs, and other related content:  '''''one mont'''h''
+* Project Leads arrange any necessary translation and customization of the Commons Deed, the FAQs, and other related content:  '''''one month'''''
-* Ported Licenses are posted on creativecommons.org: '''''one week'''''
+* Licenses are posted on creativecommons.org: '''''one week'''''
 * The Launch is celebrated!
 ----
-Next: Step IV. [[Legal Project Lead produces a first draft]]
+Next: Step IV. [[Legal Project Lead produces the first draft]]

@@ Line 18: / Line 18: @@
 * Legal Project Lead produces a first draft of BY-NC-SA, including re-translation into English (when ported licenses will be in another language) and chart of substantial legal changes detailing the reasons why changes to the unported are necessary: '''''one month'''''
-* CC reviews the first draft: '''one month'''''Italic text''
+* CC reviews the first draft: '''''one month'''''
 * CC returns comments to the team, and further drafts and comments are exchanged: '''''one to two months'''''
 * Public discussion, once a final version of BY-NC-SA has been agreed upon: '''''one month'''''

@@ Line 18: / Line 18: @@
 * Legal Project Lead produces a first draft of BY-NC-SA, including re-translation into English (when ported licenses will be in another language) and chart of substantial legal changes detailing the reasons why changes to the unported are necessary: '''''one month'''''
-* CC reviews the first draft: "'''one month'''"
+* CC reviews the first draft: '''one month'''''Italic text''
 * CC returns comments to the team, and further drafts and comments are exchanged: '''''one to two months'''''
 * Public discussion, once a final version of BY-NC-SA has been agreed upon: '''''one month'''''

@@ Line 17: / Line 17: @@
 Please find below a suggested timeframe:
-* Legal Project Lead produces a first draft of BY-NC-SA, including re-translation into English (when ported licenses will be in another language) and chart of substantial legal changes detailing the reasons why changes to the unported are necessary: ''one month''
+* Legal Project Lead produces a first draft of BY-NC-SA, including re-translation into English (when ported licenses will be in another language) and chart of substantial legal changes detailing the reasons why changes to the unported are necessary: '''''one month'''''
-* CC reviews the first draft: "one month"
+* CC reviews the first draft: "'''one month'''"
-* CC returns comments to the team, and further drafts and comments are exchanged: ''one to two months''
+* CC returns comments to the team, and further drafts and comments are exchanged: '''''one to two months'''''
-* Public discussion, once a final version of BY-NC-SA has been agreed upon: ''one month''
+* Public discussion, once a final version of BY-NC-SA has been agreed upon: '''''one month'''''
-* Legal Project Lead produces a public discussion report detailing feedback:  ''two weeks''
+* Legal Project Lead produces a public discussion report detailing feedback:  '''''two weeks'''''
-* Legal Project Lead produces draft incorporating comments (if any) from the public discussion process: ''two weeks''
+* Legal Project Lead produces draft incorporating comments (if any) from the public discussion process: '''''two weeks'''''
-* CC reviews draft: ''two weeks''
+* CC reviews draft: '''''two weeks'''''
-*  Legal Project Lead produces the five other licenses, reviewed and proofed with CC:  ''one month''
+*  Legal Project Lead produces the five other licenses, reviewed and proofed with CC:  '''''one month'''''
-* Project Leads arrange any necessary translation and customization of the Commons Deed, the FAQs, and other related content:  ''one month''
+* Project Leads arrange any necessary translation and customization of the Commons Deed, the FAQs, and other related content:  '''''one mont'''h''
-* Ported Licenses are posted on creativecommons.org: ''one week''
+* Ported Licenses are posted on creativecommons.org: '''''one week'''''
 * The Launch is celebrated!

@@ Line 19: / Line 19: @@
 * Legal Project Lead produces a first draft of BY-NC-SA, including re-translation into English (when ported licenses will be in another language) and chart of substantial legal changes detailing the reasons why changes to the unported are necessary: ''one month''
 * CC reviews the first draft: "one month"
-* CC returns comments to the team, and further drafts and comments are exchanged: "one to two months"
+* CC returns comments to the team, and further drafts and comments are exchanged: ''one to two months''
-* Public discussion, once a final version of BY-NC-SA has been agreed upon: "one month"
+* Public discussion, once a final version of BY-NC-SA has been agreed upon: ''one month''
-* Legal Project Lead produces a public discussion report detailing feedback:  "two weeks"
+* Legal Project Lead produces a public discussion report detailing feedback:  ''two weeks''
-* Legal Project Lead produces draft incorporating comments (if any) from the public discussion process: "two weeks"
+* Legal Project Lead produces draft incorporating comments (if any) from the public discussion process: ''two weeks''
-* CC reviews draft: "two weeks"
+* CC reviews draft: ''two weeks''
-*  Legal Project Lead produces the five other licenses, reviewed and proofed with CC:  "one month"
+*  Legal Project Lead produces the five other licenses, reviewed and proofed with CC:  ''one month''
-* Project Leads arrange any necessary translation and customization of the Commons Deed, the FAQs, and other related content:  "one month"
+* Project Leads arrange any necessary translation and customization of the Commons Deed, the FAQs, and other related content:  ''one month''
-* Ported Licenses are posted on creativecommons.org: "one week"
+* Ported Licenses are posted on creativecommons.org: ''one week''
 * The Launch is celebrated!

@@ Line 2: / Line 2: @@
 =Internal Administration=
 ==Mailing Lists==
-At this time, CC will announce the Project Leads and the Affiliate Institution on our mailing list and on our website under the column "Upcoming Jurisdictions". There are other recommended Creative Commons mailing lists, which you may choose to join and contribute to as well.
+At this time, CC will announce the Project Leads and the Affiliate Institution on our mailing list and on our website. There are other recommended Creative Commons mailing lists, which you may choose to join and contribute to as well.
 Furthermore, we will provide your jurisdiction with its own mailing list, which can be used to host discussions about the license drafts and coordinate events. Please invite to your list interested and valuable stakeholders in your region. Examples of key stakeholders include prominent commentators on copyright in your jurisdiction, Wikipedia leaders in relevant region or language, and potential license adaptors  in your area.
@@ Line 15: / Line 11: @@
 We encourage you use the mailing list as tool to involve and consult the members of your community, and also keep them informed about developments in Creative Commons projects, both local and worldwide.
-=Developing a timeline=
+=Developing a Timeline=
-After the internal administration has been completed, the jurisdiction's project leads will propose a timeline for the porting process. Each step, especially the launch date, should be coordinated with the CC porting team. Please find below a suggested timeframe:
+Please find below a suggested timeframe:
-* Legal Project Lead produces first draft, including re-translation into English and chart of substantial legal changes: <i> one month </i>
+* Legal Project Lead produces a first draft of BY-NC-SA, including re-translation into English (when ported licenses will be in another language) and chart of substantial legal changes detailing the reasons why changes to the unported are necessary: <i> one month </i>
 * CC reviews the first draft: <i> one month </i>
-* Public discussion: <i> one month </i>
+* CC returns comments to the team, and further drafts and comments are exchanged:  <i> one to two months <i>
-* Legal Project Lead produces second draft: <i> two weeks </i>
+* Public discussion, once a final version of BY-NC-SA has been agreed upon: <i> one month </i>
-* CC reviews second draft: <i> one month </i>
+* Legal Project Lead produces a public discussion report detailing feedback
-* Project Leads arrange necessary translation and customization of the Commons Deed, the FAQs, and other related content:  <i> one-two months </i>
+* Legal Project Lead produces draft incorporating comments (if any) from the public discussion process: <i> two weeks </i>
 * Ported Licenses are posted on creativecommons.org: <i> one week </i>
 * The Launch is celebrated!