The process by which translation teams can better handle collaboration
Registered by
Og Maciel
Every day (literally) hundreds of translation suggestions and/or modifications are generated in Rosetta. Due to some current limitations in Rosetta, it is fairly hard for translation teams members to keep up with the flood of information or even know about contributions awaiting for review/approval. My intent is to describe a mechanism by which translation teams can better administrate the contributions sent by Rosetta users, provide useful feedback and take a first step toward a better relationship with upstream projects.
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- None
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- Obsolete
- Series goal:
- None
- Implementation:
- Unknown
- Milestone target:
- None
- Started by
- Completed by
- Curtis Hovey
Whiteboard
(?)