Merge pull request #75 from TWTranslation/translation-crowdin

New Crowdin updates

Author: BatoolMM

book/translation/ara/book/website/afterword/afterword.md

@@ -0,0 +1,15 @@
+# الخاتمة
+
+الجزء الأخير من كتاب _ (The Turing Way) منهج تورينج _ يسمى **الخاتمة**. اتباعا لمبدأ تصميم الكتب القياسية، قمنا حتى الآن بإدراج {ref}`المَسرد`، {ref}` والمراجع ` و {ref}` وسجل المساهمين في الكتاب ` كمواد تكميلية لـ _Turing Way </1 >. </p>
+
+تمت كتابة جوانب التعاون المجتمعي والتنميةالمتعلقة بالكتاب في ملحق [دليل المجتمع](../community-handbook/community-handbook).
+
+```{figure} ../figures/road-to-reproducibility.*
+height: 400px
+name: road-to-reproducibility
+alt: Three hands holding magnifying glasses and varifying 'road to reproducibility' of The Turig Way.
+CONTEXTEDIT
+CONTEXTEDIT
+---
+الطريق إلى إمكانية التكرار. ---رسم توضيحي لمشروع  (The Turing Way) منهج تورينج  بواسطة Scriberia. يستخدم بموجب ترخيص CC-BY 4.0. DOI: [10.5281/zenodo.3332807](https://doi.org/10.5281/zenodo.3332807).
+```

book/translation/ara/book/website/collaboration/leadership/leadership-stories.md

@@ -0,0 +1,39 @@
+# قصص شخصية عن القيادة
+
+## Diving into Leadership: lessons from leading a hacktahon project
+
+_The following blog post was written by The Turing Way contributor [Sarah Gibson](https://www.turing.ac.uk/people/researchers/sarah-gibson)._
+
+Hackathons can be quite intimidating scenarios to put yourself into. You're probably meeting a whole load of new people and getting to grips with a new project or programming language. On top of that, you probably only have a couple of days or less to demonstrate your skills by producing something that is either a prototype or a mock-up version of a product.
+
+Now imagine if you were to lead and coordinate a group of people to work on your project idea?
+
+Yeah! That is challenging for many! I've been there, and I was intimidated too! So let me share some of the things I learned the first time I led a hackathon project at the [first Microsoft Research Software Reactor sprint](https://research-software-reactor.github.io/blog/sprint0).
+
+## Don't just focus on the code
+
+There are lots of different things that go into making a project, beyond the code itself. Similarly, there are lots of different people with different skills who may join your hackathon project - not just programmers! Good leaders can identify the strengths of their team, specifically where different skills can be put to best use on a project.
+
+Things like documentation are often left until the last moments of a project even though it's just as important, if not more so, than the code itself! If you have someone on your team who likes to write, documentation can be kept up-to-date as your codebase changes through the hackathon.
+
+The largest benefit of having a well-documented piece of software at the end of the hackathon is that it will be much easier for your team to continue to contribute to the project after the event is over. The last phase of getting a project into a production ready state takes the most time and effort, but luckily you've already documented your scoping process and pathway to getting there! 😉
+
+## Find your style of leadership
+
+Given this was my first hackathon as a project lead, I found it very beneficial to be operating as an overseer of the project, rather than taking a deep dive into the code.
+
+I felt much more able to keep track of the project as a whole and could more easily identify if everyone's skills were being utilised on appropriate tasks. I also found it much easier to mentally switch gears if a team member asked for help or input because I didn't have to disentangle myself from a coding mindset.
+
+Hackathons can also turn GitHub repositories into a the Wild West of version control 🤠 - so it's not a bad idea to have someone managing issues and pull requests as new work comes in.
+
+Now just because this leadership style worked for me, that's not to say it's right for you. It may take some time but it's important to test and find a style you're most comfortable with.
+
+## ملخص توضيحي لإنشاء سجلات المشروع
+
+In short, I think hackathons put a lot of emphasis on the coding aspect of project development (helped along by the [unfortunate naming convention](https://github.com/hackseq/October_2016/issues/24), check out the last paragraph of the [Bio-IT Hackathon blog](https://grp-bio-it.embl-community.io/blogs/posts/2019-08-29-hackathon-report/)), but this is not the sole pillar on which a good project stands.
+
+So my advice to you if you feel nervous about leading a hackathon project is: break the mould. Your project doesn't have to follow the rules of a typical hack event! Work on and in whatever manner is most suited to your teammates and the task at hand. And most importantly, _have fun!_
+
+Happy hacking! (Or not!)
+
+_To read a longer version of this blog, please see the [original post on Medium](https://blog.jupyter.org/diving-into-leadership-to-build-push-button-code-df2a075c9914)._

book/translation/ara/book/website/collaboration/new-community.md

@@ -0,0 +1,22 @@
+(cl-new-community)=
+# Managing a New Community and Team
+
+As researchers, scientists and 'techies' we look for ways to use our skills to solve pressing, current issues.
+
+The most recent example is the COVID-19 pandemic and related events {cite:ps}`WHO2020Jul` worldwide including the global lockdown that started in February 2020. The research communities responded with a sudden surge of hackathons, data modelling projects, task forces, and working groups to find effective and immediate technical solutions to combat this health crisis.
+
+```{figure} ../figures/decolonising-knowledge.*
+---
+الاسم: ادارة المجتمع
+البديل : مثال توضيحي للعديد من الناس الذين يقفون على منصة أكاديمية. وبعضها يساعد أناسا آخرين على الانضمام إليهم في العمل معا.
+---
+إنهاء الاستعمار في المعرفة من خلال نهج شاملة وتعاونية. _مجتمع طرق الشحن_ & سكريبيريا. (2020، تشرين الثاني/نوفمبر). أمثلة توضيحية من شرائع كتاب "طريق التودين". Zenodo. http://doi.org/10.5281/zenodo.4323154
+```
+
+وهذه الجهود ذات المنحى العملي ناتجة عن دافع إلى توحيد معارفنا العلمية لمعالجة حالات لم يسبق لها مثيل، وهي بالتأكيد طريقة مثالية للمضي قدما. Nevertheless, forming effective collaborations is a challenging process, even in the best of times. Keeping a team engaged is a continuous activity that requires regular checking in and evaluation. Based on each evaluation we can change and improve our workflow and community practices. ومع ذلك، فعندما نعجل في إنشاء مشروع لمعالجة مشكلة عاجلة في متناول اليد، وليس لدينا الوقت الكافي لإجراء مثل هذا التقييم. Therefore it is even more important to be intentional when creating teams and communities and apply the tried and tested best practices from the beginning.
+
+So, how can we ensure that the teams and research communities we form during the time of urgency are built on the foundation of excellent science and community practices? • مساعدة الباحثين على معالجة هذه المسألة، لا سيما عند بدء مشروع مجتمعي أو جماعي المنحى في وقت قصير (مثل الوباء)، وقد جمعنا توصيات مستمدة من تجارب الخبراء المجتمعيين والتقنيين. وفي هذا الفصل، نناقش الجوانب الهامة التي تساعد على جعل المشروع مثمرا حقا، بينما يكون موجها نحو المجتمعات المحلية بنجاح. ونناقش أيضا السبل المفيدة لمعالجة المسائل التقنية التي يمكن أن تنشأ في مشروع ما. In the third subchapter, we urge our readers to identify their stakeholders, actively invite them to participate and value the differences that exist in their teams and communities.
+
+ونأمل أن توفر الممارسات الموصى بها في هذا الفصل نقطة انطلاق جيدة لبناء تعاون ناجح مع فريقكم ومجتمعكم. We want to prompt everyone to think critically not just about the technicalities of the work, but also the social environment in which it is being conducted.
+
+*This chapter was originally discussed and written in [an online post](https://www.software.ac.uk/blog/2020-05-26-cw20-speed-blog-bootstrapping-development-team-during-time-crisis) by Malvika Sharan, Yo Yehudi, Colin Sauze, Raniere Silva, Caroline Jay, Robert Haines and Claire Wyatt as a part of the [Collaboration Workshop 2020](https://www.software.ac.uk/cw20) speed blog series hosted by [Software Sustainability Institute](https://www.software.ac.uk).*

book/translation/ara/book/website/collaboration/new-community/new-community-teamwork.md

@@ -0,0 +1,27 @@
+(العمل الجماعي المجتمعي الجديد)=
+# العمل الجماعي
+كان المعيار الواسع الانتشار في الأوساط الأكاديمية ولا يزال يعمل بشكل فردي في أغلب الأوقات. غير أن العمل في فريق يمكن أن يكون أكثر متعة، وأكثر إنتاجية، وأكثر فعالية. وهناك فوائد وسلبيات في آن واحد للعمل في أفرقة، والمفتاح هو العمل معا بطريقة تفوق فيها المزايا العيوب على العيوب.
+
+```{figure} ../../figures/new-community.png
+---
+الاسم: مجتمع جديد
+البديل: مثال توضيحي لشخصين يعملان معا ومناقشة مخطط بيانات.
+---
+جعل الفريق يعمل فعالا. [صورة خالية من الملكية من العديد من البكسل](https://www.manypixels.co/gallery/)
+```
+
+## إطار عمل الفريق
+
+وهناك العديد من الأطر الشعبية التي توفر توجيها مفيدا بشأن أفضل طريقة للعمل في إطار الأفرقة. الأمثلة الشائعة هي [كانبان](https://www.atlassian.com/agile/kanban)و [سكوم](https://www.scrum.org/)و وكلاهما من التطبيقات العملية لـ [بيان الأغنية](https://agilemanifesto.org/). وهناك العديد من الخصائص التي ينبغي العمل بها في إطار علم البيانات مما يجعل تطبيق هذه الأطر أمرا صعبا.
+
+## دروس عن العمل الجماعي لتطوير البرمجيات البحثية
+
+[العمل الجماعي لتطوير برمجيات البحث](https://nlesc.github.io/teamwork-for-research-software-development/) هو درس مستقل مع دروس في العمل الجماعي. • إطار العمل المتعلق بالكفاءة والمخطوط، ومجلس المشاريع مثل كانبان والتحديات والتوصيات العملية. 3 - كفالة أن يكون لدى جميع أعضاء الأفرقة فهم مشترك لسبل العمل، ويمكن لأي باحث يقود فريقاً على فهم هذه الموضوعات.
+
+هذا البرنامج التعليمي الذي وضعه الباحثون في المركز الهولندي للعلوم الإلكترونية موجه في المقام الأول نحو الأشخاص الذين يصنعون برامج بحثية في إطار أكاديمي. غير أن ممارسات العمل الجماعي التي تناقش هنا مفيدة بوجه عام لأي شخص يحاول العمل في فريق في المشاريع العلمية.
+
+## توصيات أخرى
+
+دليل *طريق التدوين* للتعاون، كما أننا وفرنا موارد مفيدة لـ {ref}`لتسهيل التعاون عن بعد<remote-collab>`. تحديداً، تحقق من التوصيات لـ {ref}`تنظيم<remote-collab-meetings>`، {ref}`قائمة الأدوات<remote-collab-tools>` و {ref}`إدارة الفرق البعيدة<remote-collab-management>`.
+
+لدى أتلسانيا [مجموعة كبيرة من المدونات](https://www.atlassian.com/blog/teamwork) لـ أفكار ونصائح جميلة عن العمل الجماعي. انظر على سبيل المثال [7 مهارات العمل الجماعي الأساسية](https://www.atlassian.com/blog/teamwork/teamwork-skills-accelerate-career)أو أو [كيفية إدارة اجتماعات فعالة وازدهار](https://www.atlassian.com/blog/teamwork/how-to-run-effective-meetings).

book/translation/ara/book/website/collaboration/shared-ownership.md

@@ -0,0 +1,20 @@
+(cl-shared-ownership)=
+# Shared Ownership in Open Source Projects
+
+Open source or open research movement allows anybody to use, study, modify, and distribute software or research projects freely and for any purpose ([reference](https://opensource.org/osd)). As much as open source is about sharing and distribution of software, it is equally important to highlight practices that support people’s interactions with the project as well as the communities that are built around a common interest and mission. Volunteer contributions are central to the success of open source projects who use frameworks for project peer-production and collaborations. These contributions can be witnessed in the context of coding, reviewing, documenting, error reporting, bug fixing, method selection, mentorship, training, project maintenance and other community interactions. In this chapter, we explore the “shared ownership” models to highlight that the open source projects should be owned by the community of contributors who work to ensure their development and sustainability.
+
+```{figure} ../figures/open-source-collaboration.*
+---
+name: open-source-collaboration
+alt: This illustration shows that closed source projects are driven by the needs of the institution or the individuals whereas the open source community allows different people to interact, exchange ideas, collaborate and build resources using “by the community - for the community” principles
+---
+Open source collaborative pathway compared to closed source projects that are driven by institute's personal motivation. Picture credit: _The Turing Way_ Community, & Scriberia. (2020, November). Illustrations from the Turing Way book dashes. زينودو (Zenodo) http://doi.org/10.5281/zenodo.4323154
+```
+
+## Motivation
+
+A shared sense of ownership is important for motivating contributors to collaborate in a project as they align their interests with the project’s goals. The concept of shared or collective ownership is widely practised in open source (see definition for [collective ownership](https://www.agilealliance.org/glossary/collective-ownership/)), but unfortunately, it is not always described in the projects. Often it is vaguely communicated or assumed either based on the contributors’ time or the scale of their contributions. In the long term, it is not helpful for most contributors who don’t know if their contributors are valued, acknowledged or rewarded in the project.
+
+In the subchapter {ref}`cl-shared-ownership-projects`, we explore what project ownership means in an open source world, in the subchapter {ref}`cl-shared-ownership-models`, we discuss different models that are out there and in the subchapter {ref}`cl-shared-ownership-challenges`, we discuss challenges that exist in adopting them in open source projects. Ultimately, in the subchapter {ref}`cl-shared-ownership-defaults`, we nudge researchers to apply good practices for establishing shared ownership in their open source projects.
+
+*This chapter was originally discussed and written in an online post by Malvika Sharan, Warrick Ball, Ben Krikler, and Andrew Brown as a part of the [Collaboration Workshop 2021](https://www.software.ac.uk/cw21) speed blog series hosted by [Software Sustainability Institute](https://www.software.ac.uk).*