At the moment an administrator can "Create a project".
However, there is no provision for an authenticated user to request a project.
Can we add a link for authenticated, non-administrative users to "Request a project".
We would also need a server-configurable parameter for "administration queue email".
When requesting a project, the user will fill in a form specifying details such as Project Name, requestor email contact, user names of maintainers (optional), etc.
On form submission, the form contents will be emailed to the configured administration queue email for administrator attention.
Assigning to Scrum product owner for prioritisation.
Maybe we're better off allowing anyone to create a project, and then
restricting it if it turns out to be a problem.
That would eliminate a bottleneck and a lot of administration overhead
and use friction.
Separately, but related: we could make it that the creator of a project
can delete it. It wouldn't be deleted, it would just become invisible.
"administration queue email" could use "Contact Admin Address" in the current server configuration page. This is the list of email addresses that will be the recipient for anything sent through Help -> Contact Admin or through Languages -> <Language> -> Contact Team Coordinators / Request To Join Team if there is no coordinator for the language team.
Adding Projects -> Request A Project should be fairly straightforward.
We really need the ability for users to add projects. It's a bottleneck, and it really ruins the flow of getting people in there.
Added a feature to allow any authenticated user to create a project. The project creator will automatically become the project's maintainer.
These changes also correct bug 730199.
I have logged in as a non-admin/an admin to test the new feature over several testing machines but errors always occurred after following actions.
step 1 log in
step 2 click “project”
step 3 click “create project”
step 4 fill in “Project ID”,”Name”,”Description”
step 5 click “save”
Project “XXXX” successfully created
HTTP Status 404 - /error.seam.seam
type Status report
description The requested resource (/error.seam.seam) is not available.
verified in Zanata version 1.6-SNAPSHOT (20120320-1641).
Joyce, can you please retest with 1.5.1-SNAPSHOT?
I tested 1.5 version by logging in as admin and non-admin both, following is what happened after testing
step1 login as a non-admin user/admin
step2 click "Projects"
step3 Click "Create Projects"
Step4 Fill in Project Id, Project Name,Project Description and Project Content
step3 Click "Save"
Project was successfully created
non admin user/admin will automatically be maintainer after project creation
non admin user creating the project and admin will be able to edit project
Project was successfully created
return "Unexpected error. Please try again." after clicking "Edit project"
return "Unexpected error. Please try again." after clicking "project name" of the project just created
one more is missing
non admin user/admin becomes project maintainer after project creation
Worked in all 1.5 test servers with exception of autotest. Redeployed to autotest and issue seems to have gone away. Please retry verification.
verified in Zanata version 1.5.1-SNAPSHOT (20120403-1100)
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
Creating a new translation project required server administrator privileges.
Users had to request a translation project through a ticketing system and wait for a server administrator to create the project on their behalf.
The ability to create a project was granted to any user with a valid account on the server, and the user interface was modified to make this ability accessible.
Users can now create a translation project by following these steps:
1. Log in
2. Click “Project”
3. Click “Create project”
4. Fill in “Project ID”,”Name”,”Description”
5. Click “Save”
Note that the user who creates the project becomes the project's owner.