more list->forum, current version linking

bibliographic/index.markdown

@@ -10,7 +10,7 @@ wordpress_id: 388
 
 **Open** *bibliographic* data is material that is:
 
-  * "Open" as defined by this site's [Open Definition](/1.0/)-- in essence  freely usable, reusable and redistributable, subject, at most, to the requirements to attribute and sharealike.
+  * "Open" as defined by this site's [Open Definition](/od/{{site.od_current_version}}/en/)-- in essence  freely usable, reusable and redistributable, subject, at most, to the requirements to attribute and sharealike.
   * Data or metadata produced by the bibliographic (library) sector, in particular catalogue (and related) metadata.
 
 ### More information

government/index.markdown

@@ -10,7 +10,7 @@ wordpress_id: 264
 
 **Open** government data and content is material that is:
 
-  * "Open" as defined by this site's [Open Definition](/1.0/)-- in essence material (data) is open if it can be freely used, reused and redistributed by anyone.
+  * "Open" as defined by this site's [Open Definition](/od/{{site.od_current_version}}/en/)-- in essence material (data) is open if it can be freely used, reused and redistributed by anyone.
   * Produced or commissioned by government or government controlled entities.
 
 ### More information

licenses/process/index.markdown

@@ -10,15 +10,15 @@ wordpress_id: 513
 
 This pages outlines the process for submitting a license so that it can be checked for conformance against the [Open Definition](/od), and hence listed on the [Conformant Licenses page](/licenses) in the appropriate category (see license categories below).
 
-The [Advisory Council](/advisory-council) will make the final decision on whether or not a license conforms to the Open Definition and in which category to place the license. This decision will typically follow the consensus reached via discussion on the mailing list.
+The [Advisory Council](/advisory-council) will make the final decision on whether or not a license conforms to the Open Definition and in which category to place the license. This decision will typically follow the consensus reached via discussion on the forum.
 
 ##Submitting The License
 Submit the license to the Open Definition [forum](/contact) for discussion. **For a new license, this should occur before the license is finalized, so that you can revise based on the group's feedback.** While engagement by license's steward/creator is ideal, anyone may submit a license.
 
 To do this:
 
-* Sign up to the mailing list, so that you can participate in the discussion.
-* Send **all of the following information** to the list:
+* Sign up to the forum, so that you can participate in the discussion.
+* Send **all of the following information** to the forum:
   1. Link to the **full text the license**. If the license is not in English, also provide a translation to English (an autotranslation is adequate).
   2. State the rationale for the new license.
   3. Explain whether the license may be used by any licensor, or is specific to an organization/place/jurisdiction. We generally frown on the latter (see proliferation below), only making politically expedient exceptions (eg, the organization is a national government; and these are categorized as "non-reusable").
@@ -30,10 +30,10 @@ To do this:
 
 ##What Will Happen
 
-1. After submission, the Open Definition community will discuss on the mailing list and reach consensus.
+1. After submission, the Open Definition community will discuss on the forum and reach consensus.
 2. The Open Definition Advisory Council chair will summarize the consensus to the Advisory Council on the forum and to other relevant venues, [okfn-discuss](https://lists.okfn.org/mailman/listinfo/okfn-discuss) at a minimum.
 3. If over next two weeks issues are raised which indicate a different consensus or further discussion needed, chair will step process back to first or second step as appropriate. Otherwise, chair calls for formal approval of consensus by Advisory Council.
-4. If after two weeks at least three Advisory Council members approve the consensus summary on-list, and at least 75% of Advisory Council members expressing an opinion on the summary if any dissent, the website will be updated, and announcements made to public, submitter, and wider lists as appropriate.  Wider lists includes the okfn-discuss@lists.okfn.org and local@lists.okfn.org lists.
+4. If after two weeks at least three Advisory Council members approve the consensus summary on theforum, and at least 75% of Advisory Council members expressing an opinion on the summary if any dissent, the website will be updated, and announcements made to public, submitter, and wider lists as appropriate.  Wider lists includes the okfn-discuss@lists.okfn.org and local@lists.okfn.org lists.
 
 This process will also apply to acceptance of new versions of the Open
 Definition itself.

participate/index.markdown

@@ -21,7 +21,7 @@ If you aren't familiar with git, download the [current version](https://raw.gith
 
 There is also membership of the [Advisory Council](/advisory-council) which is the group which ultimately determines the content of the Definitions and conformance with their principles. New members of the Council can be appointed at any time by agreement of the existing members of the Advisory Council (this requires consensus: namely at least one supporter and no objectors).
 
-If you are interested in becoming an Advisory Council member we recommend joining the public list and contributing there first. This is a chance for other members of the community to get to know you and for you to establish your knowledge and competency. You can then request membership of the Council.
+If you are interested in becoming an Advisory Council member we recommend joining the public forum and contributing there first. This is a chance for other members of the community to get to know you and for you to establish your knowledge and competency. You can then request membership of the Council.
 
 You or a nominating Council member should provide your brief bio at this time. All existing Council members will be queried for support or objection, and after two weeks there is at least one supporter and no objectors, per above, you will be warmly welcomed to the council.
 

source/open-definition-revision-process-dev.markdown

@@ -2,19 +2,19 @@
 Definition Revision Approval Process _- draft_
 ====================================
 
-1. Issues with the current Open Definition are identified.  The Open Definition community will disucss on the mailing list and decide which issues are to be dealt with in the next release reach consensus on each of these issues.
+1. Issues with the current Open Definition are identified.  The Open Definition community will disucss on the [forum](/contact/) and decide which issues are to be dealt with in the next release reach consensus on each of these issues.
 
-2. A new draft document is started.  Chair notifies the list and other relevant fora that a new draft document has been started summarizing the issues that the upcoming release is to address and inviting participation.
+2. A new draft document is started.  Chair notifies the forum and other relevant venues that a new draft document has been started summarizing the issues that the upcoming release is to address and inviting participation.
 
-3. Issues with the current Open Definition are identified.  The Open Definition community will discuss on the mailing list and decide which issues are to be dealt with in the next release reach consensus on each of these issues.  The draft document is updated to relfect current consensus.
+3. Issues with the current Open Definition are identified.  The Open Definition community will discuss on the forum and decide which issues are to be dealt with in the next release reach consensus on each of these issues.  The draft document is updated to relfect current consensus.
 
-4. The Open Definition Advisory Council chair will summarize the consensus to the Advisory Council on the mailing list and to other relevant fora, okfn-discuss at a minimum.
+4. The Open Definition Advisory Council chair will summarize the consensus to the Advisory Council on the forum and to other relevant venues, okfn-discuss at a minimum.
 
-5. If over next two weeks issues are raised which indicate a different consensus or further discussion needed, chair will step process back to step 2 or 3 as appropriate.  If no further issues are raised, the chair notifies the list and other relevant fora that the draft is ready for voting, establishing a release candidate, and informing contributors that only typo corrections will be accepted from this point forward.
+5. If over next two weeks issues are raised which indicate a different consensus or further discussion needed, chair will step process back to step 2 or 3 as appropriate.  If no further issues are raised, the chair notifies the forum and other relevant venues that the draft is ready for voting, establishing a release candidate, and informing contributors that only typo corrections will be accepted from this point forward.
 
-6. If over next two weeks issues are raised which indicate the release candidate is not acceptable, chair will step process back to step 2.  If no further issues are raised, the chair notifies the list and other relevant fora that a vote will occur within one week.
+6. If over next two weeks issues are raised which indicate the release candidate is not acceptable, chair will step process back to step 2.  If no further issues are raised, the chair notifies the forum and other relevant venues that a vote will occur within one week.
 
-7. Chair calls for formal approval of release candidate by Advisory Council on mailing list.
+7. Chair calls for formal approval of release candidate by Advisory Council on the forum.
 
-8. If after two weeks at least three Advisory Council members approve the consensus summary on-list, and at least 75% of Advisory Council members expressing an opinion on the summary if any dissent, the website will be updated, and announcements made to public and wider lists as appropriate. Wider lists includes the okfn-discuss@lists.okfn.org and local@lists.okfn.org lists.  If the motion does not pass the chair notifies the list and steps the process back to step 2.
+8. If after two weeks at least three Advisory Council members approve the consensus summary on the forum, and at least 75% of Advisory Council members expressing an opinion on the summary if any dissent, the website will be updated, and announcements made to public and wider lists as appropriate. Wider lists includes the okfn-discuss@lists.okfn.org and local@lists.okfn.org lists.  If the motion does not pass the chair notifies the list and steps the process back to step 2.