Tasks to complete: - Contact Admin as an action on the Help page - admin/coordinator page to add/remove coordinators from language team - security rule so that coordinators are translators - Contact Coordinator(s) - send arbitrary email to language co-ordinator(s) - available to any logged-in user - emails all coordinators for the language team - sends to system-configured email address if no coordinator - emails to have link directly to language team page - coordinator page to list/add/remove users from language team - the above two pages' functionality may be combined with existing team page - Ask to Join Language Team - generate template email when joining team - Join Language Team - now only enabled for admin
Remaining tasks: - Contact Coordinator(s) - send arbitrary email to language co-ordinator(s) - available to any logged-in user - emails all coordinators for the language team - sends to system-configured email address if no coordinator - emails to have link directly to language team page - Ask to Join Language Team - generate template email when joining team
Merged into 1.4 branch
- admin/coordinator page to add/remove coordinators from language team - security rule so that coordinators are translators Which one does it means? 1. Once assigned as coordinators, the user automatically gains "translator" role. 2. A user need to have translator role to be able to be added as coordinator (and be able to be shown in "Find Users To Add" dialog). The other are VERIFIED with Zanata version 1.4.2-SNAPSHOT (20111014-1722)
Number 1, more or less. We should write security rules (in security.drl) so that language coordinators will be allowed to add/modify/upload translations for their languages. While we're at it, we should refactor some of the existing security checks to go through security.drl.
Added security rules to allow language team coordinators to add/modify translations. Also refactored all the tags that render conditionally based on permissions to use the security rules instead of business logic (Only for the language team page). We should probably do a sweep of the whole application looking for places where we can use security rules instead of manually validating access via business methods.
Merged into 1.4 branch.
On Zanata version 1.4.2-SNAPSHOT (20111021-1030) The non-admin team member still cannot translate. RE-ASSIGNED
Corrected security check in the Translation Unit Handler to do a check based on the language memberships. Merged into 1.4 branch.
VERIFIED with Zanata version 1.4.2-SNAPSHOT (20111021-1207)