# Translations of AGILE Reproducible Paper Guidelines Translations into other languages than English are highly welcome. They open up the topic of reproducibility for a broader and more diverse audience who can enrich the AGILE community and contribute to scientific progress. If you are interested in translating the guidelines, please consider following these steps: 1. Check the *Components* section of the [guidelines OSF project](https://osf.io/cb7z8/) to see if the language you're interested in already has a translation. If there is one, your review is very welcome! 2. If there is no existing translation, check the [*Translations of Reproducible Paper Guidelines*](https://discourse.agile-online.org/t/translations-of-reproducible-paper-guidelines/25/3) discussion thread on the AGILE discourse server: Has someone else already announced her/his interest on the language in question? Hast work already started? If yes, reach out to the person - your contributions are surely helpful! 3. If the language is not mentioned in the thread - *congrats, your the first!* Please introduce yourself and your plan in the discussion thread linked above. 4. Create a copy of the Google Document in the current version of the [English Guidelines](https://osf.io/agjp9/). Click on the _"View this file on Google Drive."_ link. You can find the current version by looking for the last manually named version in the document matching the version in the top left corner of the document, e.g. `Release July 2019`. Feel free to reach out to Daniel if you're unsure which version of the document you should start with! 5. Rename the document by appending the [two letter language code](https://en.wikipedia.org/wiki/List_of_ISO_639-1_codes) in brackets to its name, e.g. "AGILE Reproducible Paper Guidelines (DE)". 6. **Translate!** 1. Give the translation feature (Tools > Translate) a try, too. 1. It would be great if you can advertise your progress and work on the discourse server from time to time (e.g. open a new thread if you want to coordinate with collaborators) and on social media using the hashtag `#agilegis`. 1. You may make small formatting adjustments (like reducing the header font sizes a little bit) if that allows you to stay closer to the layout of the English translation. Avoid adding new paragraphs or pages. 2. Do not translate terms that will be in English in final texts, e.g. the "Data- and Software Availability" section name, or that are commonly used English terms in the target language, e.g. "Checklist". 3. Please add comments to the current development version of the Guidelines in the English language, because the process of translation does bring out inconsistencies and errors in the source document. You can help improve the "main" guidelines greatly this way. _Thank you!_ 8. When the translation is done, coordinate with Daniel to complete the following steps: 1. Create an new component in the [guidelines OSF project](https://osf.io/cb7z8/) following the existing naming scheme, e.g. "AGILE Reproducible Paper Guidelines - Spanish translation" and storage location Europe/Frankfurt. 2. Adjust the collaborators to list all translators as bibliographic contributors - Daniel needs the OSF profile links of all authors and is thankful if you provide them. 3. Move the document to a subfolder following the existing naming convention, e.g. "Italian translation", in the [Google Drive folder for the guidelines](https://drive.google.com/drive/folders/17KyF7CttdSNevmGhJrQLhO6QfJYKQ4i2). 4. Add that folder to the OSF component 5. Add a named version to the document matching the translated version. 8. Publish the OSF project, mint a DOI. 9. Put the DOI in the document header. 10. Download a PDF from the document, because the PDF created by OSF does not preserve the page formatting well. 7. Upload the PDF to the file storage of the OSF component (future versions should keep the file name and use OSF's file versioning). 9. **Celebrate 🎉 and tell everyone!**