Custom Query (11 matches)

In one or more projects it may be useful to give anon access to reading the wiki and making tickets, whilst keeping tabs on repository access by giving the user group of permissions only to known registered users. So this would need another group of permissions "ticket". The "user" group of permissions would remain as is, and the "ticket" group of permissions would be the same, except that it gives no access to the repository. Typically, projects could then give the user anonymous the ticket group of permissions, while reserving the user permissions to known users. Although they could equally have three levels of access: developer, user, and ticket, each with known users only.

The developers on a project can use the web admin plugin to change which existing users can access the trac environment (including browsing the repository), but proper access to the svn repository via HTTPS/WebDAV is firmly under control of the superuser on the server.

Could the per-project group definitions in dav_svn.authz be collected automatically from projects rather than the whole file be edited centrally only by root@forge?

At least the main developer in each project needs to be able to configure at least the tracker. Not all software consists of "component1" and "component2". Haha. Some projects have three components, others might want to name their components in Gaelic.