Point to Weblate in README and don't reference translations for PRs (#…

…247)

We now have a [Weblate project](https://hosted.weblate.org/projects/outertune/) where users can contribute with translations in a convenient and safer manner than PRs.

Weblate's Libre tier asks that the Weblate project is highlighted in the README: https://hosted.weblate.org/hosting/, so do that.

Also cleanup a crowdin.yml leftover file, Crowdin isn't used in upstream either, and the configuration isn't valid for this anymore anyway

.github/pull_request_template.md

@@ -4,10 +4,8 @@
 - [ ] New feature (user facing)
 - [ ] Update to existing feature (user facing)
 - [ ] Bugfix (user facing)
-- [ ] Translations
 - [ ] Codebase improvements or refactors (dev facing)
 - [ ] Other
-<!-- If you selected Translations, please this pull request only contains translations changes, and NO code changes (unless it is absolutely necessary, please provide a description of why). Please ensure your are able to build and run the app. You can simply delete the next 4 sections as they do not apply. -->
 
 #### Description of the changes in your PR
 <!-- While bullet points are the norm in this section, feel free to write free-form text instead of a list -->

CONTRIBUTING.md

@@ -57,7 +57,6 @@ To make everyone's life easier, there are a set of guidelines that are to be fol
 | github        | Github facing configs, ex. build scripts, templates, etc.                                           |
 | gradle        | Dependency/library updates                                                                          |
 | readme        | Readme changes                                                                                      |
-| translations  | Translations                                                                                        |
 | fixup         | Amendments to certain commits. this is generally done in the format `fixup: <old commit name here>` |
 
 | Tag (ui)    | Description                                                                        |
@@ -96,8 +95,3 @@ To make everyone's life easier, there are a set of guidelines that are to be fol
 - You are require to make sure migration works from the previous database version
 - Commits modifying the database version should be all be contained in that single commit
     - The generate json JSON, Entity classes, migration conflict resolution, etc.
-
-## Translations
-Follow the [instructions](https://developer.android.com/guide/topics/resources/localization) to add translation strings, and then
-create a pull request. **You are also required to build the app beforehand** and make sure there is no error
-before you create a pull request.

README.md

@@ -61,6 +61,16 @@ recommend [Pano Scrobbler](https://play.google.com/store/apps/details?id=com.arn
 
 We are looking for contributors, translators, and maintainers! If you would like to help out, or just wish to build the app yourself, please see the [building and contribution notes](./CONTRIBUTING.md).
 
+### Translating
+
+We use Weblate (thank you for the libre tier!) to translate OuterTune. You can help translate OuterTune with it!
+
+<a href="https://hosted.weblate.org/projects/outertune/">
+<img src="https://hosted.weblate.org/widget/outertune/multi-auto.svg" alt="Translation status" />
+</a>
+
+Thank you very much for helping to make OuterTune accessible to many people worldwide.
+
 ## Donate
 
 If you like OuterTune, you're welcome to send a donation. Donations will support the development,