Create API end-points for QA and pretranslation workflows
Open
Nobody has claimed this yet.
API
P2
weeks
- Dominant language
- Python
- Stars
- 1.7k
- Forks
- 611
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 49
Description
We want a way to easily and safely interact with content through API, for example to test QA workflows, or alternative back-ends for pretranslation.
Filing this is a "tracking bug", and have individual issues for two categories of work (for now):
- Implement API to upload translations, pretranslations, and suggestions.
- Implement API to add comments to existing translations.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
This is a tracking issue with no files, tests, or entry points named. Start by reading the individual issues for the two categories: APIs for uploading translations, pretranslations, and suggestions, and APIs for adding comments to existing translations. The tracked work is done when both workflow areas have safe API support.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- django, python
- Domain
- api, backend, localization
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100