Skip to content

Latest commit

 

History

History
70 lines (43 loc) · 5.08 KB

contributing.md

File metadata and controls

70 lines (43 loc) · 5.08 KB
Raw

Contribution Guide

Simple steps for your feedback

1. As eSpeak NG is open source software, you can get it working from many different sources, some of which may provide quite old version. Before registering new issue, test that issue can be reproduced with latest development version at eSpeak NG online site.

2. Review known eSpeak NG issues, particularly about languages and add your comments on existing issues.

3. Look at and subscribe to eSpeakNG mailing list to view and discuss other related topics.

4. If you decide to create new issue, look at guide here and provide following information:

  1. example of text, which demonstrates and allows to reproduce spelling error;
  2. explanation, why produced spelling is wrong and how it should be corrected.

5. Close issue when it is resolved.

Steps for your contribution

1. Get familiar with additive speech synthesis.

2. Create fork of espeak-ng repository as it is described here.

3. Clone and set up your development environment on your computer , or clone it online. For some easy fixes you may change files just through browser of yor forked github project. Make necessary changes, commit them and issue pull request as described in step 9.

4. Get familiar with text to phoneme translation and how to add or improve language.

5. Get familiar with voice files and phoneme tables configuration files.

6. Make your improvements (i.e. additions or modifications) and check your project with make check command. Fix issues if necessary.

7. If you contribute to an existing language, find language maintainer in language configuration file located in espeak-ng-data/lang folder1 and ask him to review your changes. If you can't find language maintainer, you can review list of all contributors2 and contact them. You can also volunteer to become language maintainer just by updating language configuration file and submitting your changes as it is described in step 9.

8. If you contribute to the core of espeak-ng engine (i.e. source files of software), look at eSpeak NG roadmap. In this case you just issue pull requests as described in step 9, to make changes easier for review.

Note that:

  1. Pull request can have one or many commits, but it should have single problem solved, which should be properly described in commits and in description of the pull request.
  2. make check on your local computer and remote checks of the pull request on the server must pass.
  3. There shouldn't be merging conflicts indicated.
  4. For new/extended functionality new automated tests should be created.
  5. There shouldn't be trivial changes only like code indentation, fixed typos, language style changes etc.

9. Push your changes to GitHub and create pull request. You can also send changed files by email to eSpeakNG mailing list, but then inlusion of them may take more time.

10. Wait for feedback of current espeak-ng maintainers3.

11. When you are ready to take responsibility, ask current maintainers to get promoted as a maintainer of the project.

1. You can get list of all language maintainers with following commands in your espeak-ng folder:

cd espeak-ng-data;grep -ri -A2 -B2 maintainer *

2. You can get list of all contributors with following commands in your espeak-ng folder:

git log --pretty="%an %ae%n%cn %ce" | sort|uniq -c|sort -nr

3. Currently eSpeak NG is maintained only by volunteers in their free time, therefore expected reaction time is one, two weeks.