GNOME Bugzilla – Bug 567394
[vertimus]Display more status if it has the necessary role
Last modified: 2009-01-20 22:20:54 UTC
I found it tedious to not be able to just add a file and mark a module as translated and then just inform of the file being committed. Since I have a committer role I should be able to directly mark a translation as already committed. Or if a reviewer reviews a file he/she should be able to mark as ready for submission. Maybe for big teams makes sense to: - Reserve for translation - Upload the new translation - Reserve for proofreading [1] - Ready for submission - Reserve for submission - Inform of submission But for small teams, being able to directly mark as "Inform of submission" or "Upload the new translation" and "Inform of submission" would be sufficient. Obviously, each role just needs to see its roles. [1] Doesn't make sense also to be able to select "reserve for translation maybe?
This feature is already available in the code but not activated, in the old Vertimus only coordinators are able to choose the action they want. This behaviour has a drawback, the interface is cluttered with too many options (in the dropdown list) so I'm looking for an alternative solution (a new personal setting or an advanced view).
Maybe the advanced options can be added at the bottom like: - normal option - normal option - normal option - Extra options -- extra option -- extra option -- extra option
IMHO, we should not add as many options as old Vertimus, but at least the "Inform of submission" should be enabled for committers/coordinators in each state.
Created attachment 126849 [details] [review] Add 'Inform of submission' for all committers Tests have not been updated. Will do if the patch is approved.
2009-01-20 Stéphane Raimbault <stephane.raimbault@gmail.com> * vertimus/models.py: * vertimus/tests/__init__.py: Add 'Inform of submission' for all committers (and coordinators). Fixes bug #567394 but some cases aren't perfect so we intend to provide a better version later.
*** Bug 566650 has been marked as a duplicate of this bug. ***