13 | | 1. Ticket access. This is a different name for read access, but "read access" does not |
14 | | quite hit the spot as this includes the permission to create and comment on tickets. |
15 | | This excludes read access to the svn repository. |
16 | | 1. User access. This is the same as ticket access, but also includes read access to |
17 | | the svn repository. |
18 | | 1. Developer access. This is a different name for read/write access. The permissions |
| 13 | 1. Read access. This is designed for anonymous read access. It allows only read access |
| 14 | to the trac environment, not to the repository. Compared to the next level, ticket |
| 15 | access, this level does not allow the creation or adding to tickets. There is a |
| 16 | genuine problem allowing anonymous ticket creation or adding to, as this will eventually |
| 17 | be used by spammers to put hyperlinks onto public web pages (the ticket). |
| 18 | 2. Ticket access. This is designed for the case where certain users (or anonymous users) |
| 19 | should be able to make full use of the ticketing system, but should not have access |
| 20 | to the repository. |
| 21 | 3. User access. This is the original minimum access level (other than no access). It allows |
| 22 | to read the trac environment, to make full use of the ticketing system, and to read the |
| 23 | repository. |
| 24 | 4. Developer access. This is a different name for read/write access. The permissions |