The current OD version is 2.1. Numerous translations are available
on the website. The ideal way to submit new translations is by adding
-an `od/2.1/{language code}/index.markdown` file and sending a pull request on the `gh-pages` branch.
+an `od/2.1/{language code}/index.markdown` file and sending a pull request on the `gh-pages` branch. See <http://opendefinition.org/participate/#translation> for additional guidance.
Many pages in the repository are related definitions and domain-specific
guides which are not highlighted in the site navigation; there's a
list at <http://opendefinition.org/participate/>. These are all still
of interest but in need of review and updating. Feel most welcome
-to file issues, submit pull requests, and discuss on our [mailing
-list](http://lists.okfn.org/mailman/listinfo/od-discuss) or [forum](https://discuss.okfn.org/c/projects/OpenDefinition).
+to file issues, submit pull requests, and discuss on our
-If you have any questions, comments or suggestions about the Open Definition, please contact us. You can do so either by sending and email or writing to the mailing list (you will need to sign up to the list first).
+If you have any questions, comments or suggestions about the Open Definition, please contact us. You can do so either by sending and email or writing on the forum.
-We aim to translate the Definition into many other languages. If you would like to help out with [translating](/participate/) the Definition into a language not already listed, please get in touch either via email or on the mailing list.
+We aim to translate the Definition into many other languages. If you would like to help out with [translating](/participate/) the Definition into a language not already listed, please get in touch either via email or on the forum.
@@ -13,7 +13,7 @@ This pages outlines the process for submitting a license so that it can be check
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.
##Submitting The License
-Submit the license to the Open Definition [mailing list](/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.
+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:
@@ -31,7 +31,7 @@ To do this:
##What Will Happen
1. After submission, the Open Definition community will discuss on the mailing list and reach consensus.
-2. 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](https://lists.okfn.org/mailman/listinfo/okfn-discuss) at a minimum.
+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.
0 comments on commit
bd39b14