Custom Query (11 matches)
Results (7 - 9 of 11)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #5 | fixed | remote user creation | ||
| Description |
The user access management per project by its developer (ticket #4) points the way to remote user account management also. We can have another Perl CGI script running as root, which checks out the passwd file from the ROEadmin repository. Any developer on the ROEadmin project can then remotely check out, modify and commit the passwd file, then invoke the CGI script to put the file where it has an effect. |
|||
| #6 | fixed | no e-mails | ||
| Description |
There are no e-mail notifications, even when an e-mail address is entered into the Cc field of a ticket. |
|||
| #8 | fixed | distinct admin access | ||
| Description |
Some projects will not want to give all their developers full admin access. Change to three levels of access: user (as now), developer (all but TRAC_ADMIN), TRAC_ADMIN. The admin access is irrelevant to svn and hence also to the script that composes the authz file from the trac permissions. All we need is to change the developer group of permissions to be user plus what they need, but not as much as to have the admin button in the wiki. |
|||
