Skip to content

Latest commit

 

History

History
48 lines (28 loc) · 3.16 KB

CONTRIBUTING_en.md

File metadata and controls

48 lines (28 loc) · 3.16 KB
Raw

🇦🇷 Leer en español

How to contribute to Pilas Bloques

Thanks for your support! ❤️. If you hadn't done it yet, please read the project README. There you'll find our app's main goals and instructions to get started with the development environment. In Pilas Bloques we work using Pull Requests and feature branches. So if you want to contribute, fork the project, make your changes in a branch, and make a Pull Request to the original repo. You can check the first good issues or also the Pilas Bloques Github Projects for hints on what is there to do.

Issues

If you found a bug and you want to report it, or if you have an idea for a feature for Pilas Bloques, create an issue describing it.

Pull Requests

  • Link the solved issue in your PR description using Fixes #<issue number>.
  • If you make visual changes, you are encouraged to include a screen capture showing the change.
  • Include unit or integration tests for each feature or fix you make.
  • Every test in the app should pass.
  • Every new code should be writen in English. The long-term objective is that every Pilas Bloques file is in English. See "About the language" section below.

Example of a good PR: #147

Translations

  • If you want to improve or complete an already existing translation you can do so by editing the proper translation file in the locales folder and making a pull request with your proposed changes.

  • If you want to start the translation to a language that Pilas Bloques doesn't support yet, you can do so by creating a translation file in the locales folder and making a pull request with your proposed translation.

Do you have any questions?

You can tag us in Github with @pilasbloqueros or you can also send us an email to pilasbloques@program.ar

Thank you so much for wanting to collaborate with Pilas Bloques!!! ❤️ ❤️

About the language

Pilas Bloques has a user and developer community that are mainly spanish-speakers. That's why the documentation and PRs are mainly written in spanish, as well as part of the code.

However, in order to broaden these communities we are beggining to accept english as a secondary language for our issues and discussions and we already have our first english docs.

Furthermore we have a very ambitious goal: we're starting to translate app code to english. That's why:

  • Every newly added code in the pull request should be written in English. 🇬🇧
  • Pilas Bloques team will eagerly help you with any issues with the existing or new code. 👍
  • If a PR does extensive changes to a component, you are encouraged to translate the entire component to English. 🦾