Make Brainhack Accessible WorldWide: Translation of Brainhack Glossary into Different Languages

Project info

Title: Make Brainhack Accessible WorldWide: Translation of Brainhack Glossary into Different Languages

Project lead: Valentina Borghesani

Project collaborators: Valentina Borghesani @valentinaborghesani Johanna Bayer @likeajumprope Selim Atay @i-am-mel-dev Franco Pestilli @francopestilli Jose Pedro Manzano Patron @josepman Malin Sandström @malinINCF Yasmin Basille @yasminebassil Isil Bilgin @complexbrains

Registered Brainhack Global 2020 Event: Brainhack Montreal

Project Description: The project aims to bring together Brainhack and Open Science terminologies together in one glossary to help the newcomers to guide them through with their quick integration with the community tools and resources and provide a centralized glossary for the main community to be used for the future references.

In this project, we would like to make the glossary a step further and make it accessible by removing the language barriers and translate it to the as possible different languages with the help of the community.

Data to use: The glossary itself and references listed at the bottom of the glossary and any other community developed open science glossaries to match the references.

Link to project repository/sources: https://github.com/brainhackorg/brainhack_jupyter_book

Goals for Brainhack Global 2020: Making the glossary completed with the all necessary terminologies to serve the best of the community and translate it into different languages to make it more accessible to the communities around the world.

Good first issues:

• Complete the glossary with the missing terminologies
• Add necessary/missing terminologies.
• Translate the glossary into different languages
• Implementing the translated versions to the Jupyter Book.

Skills: The native or advanced level speaker in the language of being translated. Basic knowledge in using Git/Github/Commit/opening a PR might be helpful but not necessary.

Tools/Software/Methods to Use: Github repository Google docs

Communication channels: https://mattermost.brainhack.org/brainhack/channels/brainhack_paper_jupyterbook

Project labels

• Type of project: #data_management, #documentation

• Project development status: #0_concept_no_content, #1_basic structure

• Tools skill level required to enter the project (more than one possible): #familiar, #no_skills_required

• Programming language used in the project: #documentation

• Git skills reuired to enter the project (more than one possible): #0_no_git_skills, #1_commit_push, #2_branches_PRs, #3_continuous_integration

• I added all of the labels I want an associate to my project

Project Submission

Submission checklist

Once the issue is submitted, please check items in this list as you add under ‘Additional project info’

• Link to your project: could be a code repository, a shared document, etc.
• Goals for Brainhack Global 2020: describe what you want to achieve during this brainhack.
• Flesh out at least 2 “good first issues”: those are tasks that do not require any prior knowledge about your project, could be defined as issues in a GitHub repository, or in a shared document.
• Skills: list skills that would be particularly suitable for your project. We ask you to include at least one non-coding skill. Use the issue labels for this purpose.
• Chat channel: A link to a chat channel that will be used during the Brainhack Global 2020 event. This can be an existing channel or a new one. We recommend using the Brainhack space on Mattermost.

Optionally, you can also include information about:

• Number of participants required.
• Twitter-sized summary of your project pitch.
• Provide an image of your project for the Brainhack Global 2020 website.

We would like to think about how you will credit and onboard new members to your project. If you’d like to share your thoughts with future project participants, you can include information about:

• Specify how you will acknowledge contributions (e.g. listing members on a contributing page).
• Provide links to onboarding documents if you have some: