🎉 Outreachy spring 2022: Applicants tasks/contributions #1
Comments
|
Hello everyone, My name is Oluwaseun, I just joined Crowdin. |
|
Hi @oluwaseunlijoka, you should be able to join the project through this link: https://turingway.crowdin.com/u/signup?hash=3d0624a322db57a403a7ece3ccce900a24. Let me know if you have a problem accessing it! |
|
Hello @BatoolMM, Thank you, I just joined now. I guess you are mentor now. Please can lead me through how I can start, I am from https://www.outreachy.org/. Thank you |
|
@oluwaseunlijoka I added a few screenshots and details - let me know here if you struggle with anything! |
|
Hello @BatoolMM , my name is Thana. I just joined the project by following the link you provided. |
|
Hi, Thana - you've been added to Crowdin, feel free to follow the steps and let me know if you have any questions! |
|
Hello @BatoolMM, I am Ahmed an engineering student from Egypt, and an outreachy applicant for this spring. |
I just joined the project, do i have to wait to be a manger before starting to contribute ? |
|
Hi Ahmed, thank you for joining - you don't have to wait, you should be able to use Crowdin now. Let me know if you have any questions about crowdin. |
|
Hi @BatoolMM my name is Fatima I am oureachy applicant I have joined the crowdin what next |
|
. hi @BatoolMM I added issue here ,please review and advice |
|
Hello @BatoolMM , My name is Asma. I'm from Tunisia it's a small country in the north of Africa. I'm a Telecommunication engineering student and an Outreachy applicant. I am |
|
Hi @AsmaKacem1 @nancyalaswad90 @Nizahra2038, thank you for joining - please follow the steps in this issue - if any of you have any questions, please add them here under this issue (don't open a new issue). Here is more info on how to use Crowdin Editor. |
|
Hello @BatoolMM, I am Boutaina from Morocco. I am an outreachy applicant. I have joined crowdin, and I am super excited to contribute to your organization and be a part of your community. |
|
Hi Boutaina! Let me know if you struggle with anything in Crowdin. |
|
We will hold a video call in Elements to answer any questions you have. This could be a problem using Crowdin editor or understanding any of the tasks in the internship. This will be on Friday, the 1st of April at 10 am UTC. Follow this link for invitation to Element! |
I'm trying to click on 'go to the editor', but I can't find it. Could you please help me?
|
|
Hi @BatoolMM , I'm Alaa, an aspiring Outreachy intern, looking forward to be working with you. |
|
Thank you @Boutainaelatbaoui for the question. If Go to editor isn't visible, choose Proofreading and you will end up with something similar to this screenshot.
You’ll see the list of source strings and their translations that you can approve or correct. The strings with the QA checks issues will be highlighted in this mode. You’ll also see the strings that were translated with the help of Translation Memory or Machine Translation engine. You can still change the complete translation. Let me know if this works for you! Hi @amj1337, you are welcome to go through the steps and post your questions here! |
|
All individuals who commented on this issue are granted Manager access so they can get access to all features of the Crowdin editor! Let me know if you still don't see Go to editor option. |
|
. I made some script , will you please give your opinion about it . |
|
Hello, Could you please explain to us about the video of OLS2 and OLS1? |
|
Thank you @AsmaKacem1 for adding the translation. Please work in one single markdown file and completely finish it before moving to another file. Can you kindly focus on translating I see that you also added a few terms to the Glossary. That's really good - but some terms like def are repeated with two different meanings. If you are adding the English word between brackets, please keep space between the bracket and the word - e.g. GitHub : (GitHub) منصة جيت هب - not (GitHub)جيتهاب. With space between brackets and the word. Once you complete a file or a couple of paragraphs from the same file, I'll add comments in Crowdin for you (like below).
@nancyalaswad90 Your translation is good, I added some comments on Crowdin - please go through them. You should be able to access the comments tab in Crowdin similar to the screenshot above (on the right)! Let me know if you have any questions! |
|
Thanks @BatoolMM for your feedback I will do the update and send you |
|
Thank you @BatoolMM . I took these notes and I will do the necessary change you mentioned. |
|
Thanks @BatoolMM for your explanation comments Just finished some updates in my translation and added a few terms to the Glossary. , will you please give your opinion about it. |
|
In terms of the glossary. The Glossary is supposed to contain terminology that has a purpose of explaining some specific terms or the ones often used in the project to be translated consistently and adequately, such as (e.g. open science, open access, open hardware, ...etc). It's not supposed to include names of initiatives. There are some issues in the Glossay below:
|
|
Hi @BatoolMM when reading the book I came across words that look similar in their general meaning like "Reproducible" and "Replicable" but they were defined to have different meanings in the book, is it right for those words to be added to the Glossary with their definitions from the Turing way book itself ? even thought they are not defined in the file that I chose to translate but some of them are used in it. |
|
Thank you @amj1337 for this question
Absolutely! |
|
Dear @BatoolMM Please advise , what should I do now ? and what is the assessment for my previous updates ? |
Done! |
|
@BatoolMM Thank you for your quick feedback I made some changes , I wish you provide me with your feedback |
|
Hi @BatoolMM , I have finished the open-hardware.md |
|
Marhba. @BatoolMM I did some translations so far. it would be great if you give me a feedback |
|
Hi @BatoolMM , I have finished the open-access.md I wish you provide me with your feedback |
|
@nancyalaswad90 @AsmaKacem1 @ThanaMeri I added feedback to all of you in Crowdin - the next round of feedback will be given by the 9th of April. |
|
@ThanaMeri - there are comments, just checked them now and tagged you. Let me know if you couldn't find them! |
|
Hi @BatoolMM , I have finished the open-access.md Please provide me with your feedback |
|
Good evening @BatoolMM , if available , would you please check my translation of the overview-barriers.md file and provide me with feedback on what is approved and what needs rectification. |
|
@amj1337 @nancyalaswad90 I went through the translation and added a few comments. Please feel free to start the 2nd part by submitting a PR. I updated the instructions (above). If you have any questions, please let me know! |
|
Hi, everyone! I just wanted to introduce myself in this issue, and say hello 👋! I'm Anne Lee Steele (@aleesteele), the Community Manager of The Turing Way. Together with @malvikasharan and @KirstieJane (who are co-leads of the project), we just wanted to say that we're so excited to follow the work you're doing with The Turing Way and with the amazing @BatoolMM! Translation is such important work that extends far beyond The Turing Way alone (as you all are well aware of - much moreso than me!)... and has much broader effects in the wider open source and open science communities. Best of luck with the application process, and if you have any questions about the project more broadly, please feel free to send me a message at asteele@turing.ac.uk. Congratulations again to you all! 🎉 🎉 🎉 |
|
Thank you @aleesteele for introducing yourself, that's very thoughtful of you 🌷 . I'd encourage everyone who has contributed so far in Crowdin to record their contribution in Outreachy regardless if they completed their PRs or not. If you have any questions about how to record your contribution, please feel free to ask! |
Hi @BatoolMM , really grateful for your support and here is my work in previous two days
. |
|
Hi @BatoolMM
. Thanks for your guidance , please review. . |
|
All PRs are merged, please don't forget to submit your final contribution through Outreachy. We have many strong candidates but we'll only take one intern so we would like to remind you to work on a minimum of 2-3 projects simultaneously so that they are not completely relying on their selection in OSCSA if we end up not selecting them! If you have any questions, please feel free to ask! |
|
@BatoolMM Do I still have time to post my PR ? I thought the deadline is April 22 ? |
|
@ThanaMeri of course, you are very welcome to submit your PR, the deadline is the 22nd of April! |
|
@BatoolMM will you please give me a feedback on my PR ? |
|
Hi @BatoolMM I have just sent my PR, when available would you please check it out, thank you. |
|
Thank you for submitting PR #8 - please go through the comments I added! |
|
The intership has ended and this issue will be closed! |
🎊 Welcome Outreachy 2022 Contributors! We're excited that you're here 🎉
Outreachy provides paid remote, three-month internships to support diversity in Free and Open Source Software (FOSS). For more information about what Outreachy is, follow this link.
Outreachy internships are:
💵 Paid - $7,000 USD total internship stipend
🌍 Remote - both interns and mentors work remotely
🕰 3 months - internships run May to August.
For those interested, this process is described here.
Summary
Open Science Community Saudi Arabia (OSCSA) aims to introduce open educational resources (OERs) for Open Science in Arabic to facilitate learning of Open science practices to novice learners. Therefore, we work with other Open Science communities such as the Turing Way and Open Life Science to localise their open educational resources (OER) using Crowdin, GitHub and Zenodo.
We use GitHub as a version control system for all the translations and to acknowledge all contributors. Crowdin is used as a translation management system (or TMS) to make contributions smooth. Any changes made to Crowdin will be reflected on GitHub using automation and continuous integration (CI). Crowdin provides Translation Memory (TM), Glossary, Machine Translation (MT) and QA checks.
In Outreachy spring 2022, we are accepting applicants to localise specific chapters of The Turing Way. The Turing Way is a handbook to reproducible, ethical and collaborative data science. It supports a diverse community of contributors to make data science accessible, comprehensible and effective for everyone. You can find more information about it, in the TW repository.
Successful candidates will improve the localisation process by adding documentation in Arabic, enriching the glossary, moderating the translation, using screenshots to improve the translation and collecting feedback.
How to start?
Join OSCSA community here
You will need to create an account in Crowdin and join our project here. Once you join, you have to comment on this issue, so we follow your work in Crowdin.
Navigate to the Project home and click on Arabic
reproducibale_reserachand then toopen. Translate one the topics in this task in Crowdin.Using the Main menu in the top left corner, you can switch between files for translations, change translation language, contact manager, switch the view, get help or quit the editor. For more information, follow the docs here. If you have questions, please add them to this issue!
Glossary
The Glossary is supposed to contain terminology that has a purpose of explaining some specific terms or the ones often used in the project to be translated properly and consistently such as (e.g. open science, open access, open hardware, ...etc). It's not supposed to include names of people, books, ...etc.
You should add a specific term add to the glossary if:
1- It's commonly used in the project, but translators can translate it differently. For example, open access can be translated الوصول الحر أو الوصول المفتوح أو النفاذ الحر but we want to keep consistency throughout the project when it's translated by many contributors - so they can use the same translation, not multiple ones.
2- Some English terminology doesn't exist in Arabic. Once you translate them, you include them in Glossary (e.g. Git, GitHub, repository,..etc).
The Glossary should be consistent in style. The Arabic translation should contain the Arabic translation followed on the left the English terms between brackets with spaces between brackets. For example, the Arabic for Open access should be (Open Access) الوصول الحر with space between brackets and the Arabic word.
If you have questions about the glossary،, ask under this issue.
Submission
Once you finish a very small part of the translation, submit a PR for a markdown file called
NAME_docs.mdin/docsin this repo to include brief documentation in Arabic ( around 500 words or more using Markdown) about the translation process of the project in Crowdin. This should include (Getting started with Crowdin, tips, ..etc) using images and GIFs.If you have any questions throughout the process, add your question to this issue!
Tasks for Intern Selection:
Tasks during the internship
Meetings
We will lead a video call in Elements to answer any questions you have. This could be a problem using Crowdin editor or understanding any of the tasks in the internship. This will be on Friday, the 1st of April at 10 am UTC. Follow this link for invitation to Element!
Assessing Candidates
Resources
The text was updated successfully, but these errors were encountered: