-
Notifications
You must be signed in to change notification settings - Fork 5
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
85e9aca
commit aaa1635
Showing
1 changed file
with
58 additions
and
16 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -5,37 +5,42 @@ order: 2 | |
layout: "translation/single" | ||
--- | ||
|
||
**Our mission:** *Make CRediT more inclusive by translating it into other languages and making those in various language communities aware of it* π | ||
|
||
## Contributing to translations | ||
# π Contributing | ||
|
||
Anyone fluent in a language not already translated can help provide a new translation, or propose a change to an existing translation. | ||
We invite all interested to contribute to the project. | ||
|
||
Before starting on a new translation: | ||
**General:** | ||
|
||
* [Check the current status]() of translation for your language. | ||
* Fill out [our Google Form](https://docs.google.com/forms/d/e/1FAIpQLSfdhqlnk4sw61MkkDuufZyqO1SKmnp--QE6vEG1_7qnP9MzJg/viewform?usp=sf_link) so we have a record of your interest and potentially to help match you with another translator or project contributor. | ||
* Follow the instructions in the below [translation section](#-Creating-a-translation). | ||
1. Fill in the [Expression Of Interest (EOI) form](https://docs.google.com/forms/d/e/1FAIpQLSfdhqlnk4sw61MkkDuufZyqO1SKmnp--QE6vEG1_7qnP9MzJg/viewform?usp=sf_link), so we hae your names and contact details. Demogrphic questions are optional, but would be helpful. | ||
1. To enable broad global participation, we will mostly work asynchroniously online until we complete all stages of the project. | ||
1. We expect all project contributors to familiarise themselves and follow our CODE OF CONDUCT. | ||
1. If you would like to comment on this project or provide suggestions to improve this project, feel free to open an issue on GitHub or reach directly to us via | ||
Slack (invites will be sent to project participants who filled in the [EOI form](https://docs.google.com/forms/d/e/1FAIpQLSfdhqlnk4sw61MkkDuufZyqO1SKmnp--QE6vEG1_7qnP9MzJg/viewform?usp=sf_link)) or email ([email protected]). | ||
1. We will post updates on project progress on [the blog](https://contributorshipcollaboration.github.io/blog/), as well as the [language status table](https://github.com/contributorshipcollaboration/credit-translation/blob/main/language_status.md) | ||
1. All contributions to this project are voluntary. We will not provide financial remuneration for any contributions (we have no funding). | ||
1. You can withdraw from the project at any time. | ||
|
||
Contributors will be recognized in that their names will appear in the attribution for the translation they helped create. For example, see the [draft human-readable page for German](https://github.com/contributorshipcollaboration/credit-translation/blob/main/md_files/credit_translation_de.md). | ||
## 𧱠Translation contributions | ||
|
||
Anyone fluent in a language not already translated can help provide a new translation, or propose a change to an existing translation. | ||
|
||
## Contributing to other facets of the project (we'd love your help!) | ||
Before starting on a new translation: | ||
|
||
* Code: check the Github issues or email us | ||
* Outreach and implementation | ||
* Contact scientific societies and scientific publishers who publish in these languages | ||
* Help us organise a hackathon ad hoc or at a scientific conference | ||
* [Check the current status](progress.md) of translation for your language. | ||
* Follow the instructions in the below [translation section](#-Creating-a-translation). | ||
|
||
## Creating a translation | ||
### Creating a translation | ||
|
||
* We have created a Google Sheet for entering your translation work and seeing how others did it. Contact us for access to the Google Sheet. | ||
* First, one speaker fluent in both languages translates the English into the target language and enters that on the Google Sheet. | ||
* A second speaker, ideally one not familiar with CRediT, back-translates the translation into English. | ||
* Feel free to use Google Translate to assist, just don't rely on it, for example don't use it for both the forward and back-translation. | ||
* Discrepancies between the original English and the back-translated English can tip one off to parts of the translation that deserve attention, where one should consider alternative phrasings. So, the two speakers confer and resolve any discrepancies. | ||
* To make your translation machine-readable, you must create a JSON file, following the format of the [schema](). See instructions below. | ||
* To make your translation machine-readable, we can help you create a JSON file, following the format of the [schema](). See instructions below. | ||
* To see if a .json file already exists, look [here]() for a file with the [two-letter abbreviation](https://en.wikipedia.org/wiki/List_of_ISO_639_language_codes) for your language. | ||
|
||
### If a .json file for your language does NOT already exist: | ||
|
||
Download one of the existing JSON files, such as [the German one]() and change all the German text to your target language. Then send it to us. | ||
|
@@ -57,4 +62,41 @@ Download one of the existing JSON files, such as [the German one]() and change a | |
* If you're not familiar with Github, send us the .json file | ||
* If you're familiar with Github, | ||
* Create the json file if it doesn't already exist | ||
* Create the pull request | ||
* Create the pull request | ||
|
||
## Contributing to other facets of the project (we'd love your help!) | ||
|
||
* Code: check the Github issues or email us | ||
* Outreach and implementation | ||
* Contact scientific societies and scientific publishers who publish in these languages | ||
* Help us organise a hackathon ad hoc or at a scientific conference | ||
* | ||
|
||
# π Acknowledgement of contributions | ||
|
||
## Translation contributors | ||
|
||
Contributors will be recognized in that their names will appear in the attribution for the translation they helped create. For example, see the [draft human-readable page for German](https://github.com/contributorshipcollaboration/credit-translation/blob/main/md_files/credit_translation_de.md). | ||
|
||
<!-- All project participants who contributed any amount of work, and provided their details, will be acknowledged as project contributors on the project page, report, presentations, and manuscript. We will mainly use a CRediT-like statement format, but we will also keep a more detailed record of individual contributions to specific tasks within the stages of the project. This record will be also made publicly availabe as part of the open project materials (as a publicly available dataset). You can request to have your details removed or obscured at any time. --> | ||
|
||
## π Co-authorship | ||
Project participants with substantial and high-quality contributions (as defined below) will become co-authors of the manuscript. | ||
They will contribute to any or all of these: translation, checking, website code, coordination, and/or report drafting. | ||
|
||
A substantial contribution can be achieved by performing any X or more of the tasks listed below | ||
|
||
IMPORTANT: Authorship is also coditional on reading and approving the final manuscript draft before submission and providing all personal information (e.g., name, affiliation, email) needed for the submission. | ||
|
||
Additional contribution oportunities may be available. | ||
|
||
In the manuscript, first and last authorship positions will be reserved to the project leads (they could be co-first and co-last positions). Subsequent authorship positions will be determined by the total amount and quality of contributions, as in the project records. For equal contributions the order of mid-authorship will be alphabetic. All authors must read and approve the final manuscript draft before submission. The manuscript will contain a CRediT statement detailing the roles of individual authors and contributors. | ||
|
||
# π Final notes | ||
Project leads reserve the right to interpret and change the contribution rules at any time, if such need arises. In case of any disputes decisions of project leads will be final. | ||
|
||
# π§ Maintainer(s) | ||
* [Alex Holcombe](https://github.com/alexholcombe). | ||
|
||
# ποΈ License | ||
This work is licensed under a [Creative Commons Attribution 4.0 International License (cc-by)](/LICENSE.md). |