Speech-To-Text and Machine Translation providers with user context

[andrey18106]

Describe provider with userId usage for Machine Translation (nextcloud/server#42649) and Speech-To-Text (nextcloud/server#42761), similar to Text Processing for consistency between them.

🖼️ Screenshots

Speech-To-Text

Machine Translation

[nickvergessen]

Please also add to https://docs.nextcloud.com/server/latest/developer_manual/app_publishing_maintenance/app_upgrade_guide/upgrade_to_29.html#id1

[ChristophWurst]

Please also add to https://docs.nextcloud.com/server/latest/developer_manual/app_publishing_maintenance/app_upgrade_guide/upgrade_to_29.html#id1

IMO upgrade docs are not necessary for a new API. If you have an existing app you don't need to do anything about this to keep the app alive.

[nickvergessen]

IMO upgrade docs are not necessary for a new API. If you have an existing app you don't need to do anything about this to keep the app alive.

My understanding of that thing was to have a "quick overview" of things you could add to your app, without having to grep the docs repo for "New in version 29" or checking all files touch-date.
Maybe you considered implementing a STT provider but the missing context prevented you from doing so?

[ChristophWurst]

Fair point

My inspiration was https://laravel.com/docs/9.x/upgrade. If we list everything, the important changes can be hard to find. We could have a dedicated section for announcements of new APIs?

[bigcat88]

Can we not add this time to the “new APIs”, we are not sure how long these classes will be there, this will be decided by team and Marcel, perhaps in the near future we will make a system where providers are immediately located in exApp and will move away from using these classes through the process of deprication.

[nickvergessen]

Can we not add this time to the “new APIs”, we are not sure how long these classes will be there, this will be decided by team and Marcel, perhaps in the near future we will make a system where providers are immediately located in exApp and will move away from using these classes through the process of deprication.

It's OCP, so our deprecation period is 3 years?

[bigcat88]

Can we not add this time to the “new APIs”, we are not sure how long these classes will be there, this will be decided by team and Marcel, perhaps in the near future we will make a system where providers are immediately located in exApp and will move away from using these classes through the process of deprication.

It's OCP, so our deprecation period is 3 years?

unfortunately yes, it will not be as quick as we wish.
Anyway, if you want we will add to documentation in any additional place where you want

[github-actions]

Hello there,
Thank you so much for taking the time and effort to create a pull request to our Nextcloud project.

We hope that the review process is going smooth and is helpful for you. We want to ensure your pull request is reviewed to your satisfaction. If you have a moment, our community management team would very much appreciate your feedback on your experience with this PR review process.

Your feedback is valuable to us as we continuously strive to improve our community developer experience. Please take a moment to complete our short survey by clicking on the following link: https://cloud.nextcloud.com/apps/forms/s/i9Ago4EQRZ7TWxjfmeEpPkf6

Thank you for contributing to Nextcloud and we hope to hear from you soon!