-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upcoming 1.0 and renaming #23
Comments
OK good to know, your help would be greatly appreciated! What do you have in mind in terms of renaming the binding? |
Other binding switched to use |
Did they rename their repo as well? |
I dont think they acted yet, and it really depends on you and your users, if you think its okay to rename your repo or if it's going to be too much of a mess. We will rename ours, though. |
OK, I won't rename the repo for now. I'll wait for your PR then |
I created a PR for this so we can finally close this issue. Thanks for the fantastic work guys! |
? I don't understand your request. |
@lissyx on this How is Coqui STT implemented? page the golang bindings are still mentioned but the link to this repo has disappeared. |
I am not working on Coqui, you should ask @reuben |
We'll be happy to re-link to the bindings once the PR is reviewed and merged! |
FYI I've merged the PR. URL to the repo is https://github.com/asticode/go-asticoqui Thanks in advance for any re-link ❤️ |
Hello,
1.0 is close, and part of the work for that involves one painful change: we need to rename the project to Mozilla Voice STT.
It also means library itself and the API need to get renamed:
libdeepspeech.so
->libmozilla_voice_stt.so
and APIDS_*
becomesSTT_*
.Besides this renaming, there should be no other change. I can help and prepare a PR to update once we have completed some painful renaming on our side (CI, packages everywhere).
For clarity, it might be good if you could rename your binding as well, but we do not want to force you as well.
The text was updated successfully, but these errors were encountered: