Developers » History » Revision 26
Revision 25 (Dan Smith, 02/09/2023 02:18 AM) → Revision 26/33 (Dan Smith, 07/03/2023 03:46 PM)
# Developers Welcome! CHIRP is open source software and contributions are welcomed! Submissions are accepted via [github](https://github.com/kk7ds/chirp) . ## Resources * Join the [chirp_devel mailing list](http://intrepid.danplanet.com/mailman/listinfo/chirp_devel) * Get the code at [github](https://github.com/kk7ds/chirp). See [PR Guidelines](https://github.com/kk7ds/chirp/blob/master/.github/pull_request_template.md). [github](https://github.com/kk7ds/chirp) * [[Developers/Add_a_Radio]] * [[Developers/ToneModes]] * Get a new Python3 development environment setup with [[DevelopersPython3Environment]] * chirp-legacy OUTDATED Windows Python2 development environment instructions: [[LegacyDevelopersWin32Environment]] ## How you can help * Test new changes and releases * Triage bug tickets * Write or update documentation * Find and fix bugs * Add or extend support for new radio models * Add features to the UI ## Translating CHIRP ### New Languages If you want to help translate CHIRP into another language, please follow these steps: 1. Create a [new issue](http://chirp.danplanet.com/projects/chirp/issues/new) for the language and include the language code. Here is a [helpful list](http://www.science.co.il/Language/Codes.asp). 1. Someone will create an empty template `.po` file and attach it to your issue 1. Translate the file. Generally, [poedit](http://poedit.net/) is the best way to do this. Be sure to fill out the translator meta-details. 1. Attach the resulting translated `.po` file to the ticket 1. A developer will check it over and then submit it for inclusion ### Updating an existing language If you want to update a translation, grab the latest from [the repo](https://github.com/kk7ds/chirp/tree/master/chirp/locale), update it and attach it to an issue for a developer to include. Use [poedit](http://poedit.net/) to update the translations