Your users, of course, do not need all of this explanation! In fact, one of the goals of this feature is that Gitolite users (as opposed to Gitolite administrators) should not be burdened with learning the nuances of RW, RW+, deny rules, and so on.

The example setup we have been using till now is the canonical example: it contains an owner (who is the only user allowed to rewind or delete branches), a set of writers (who can push/create but not rewind/delete), and a set of readers who cannot push at all.

The only thing left to do is to explain to the user what repositories she is allowed to create (most users do not know regular expressions very well, so it's best to keep your patterns simple enough to be explained in English), and that she can add or remove people from each of those lists of users.

The list names (in our example, READERS and WRITERS) should be supplied, and explained as representing what the users in each list can do.

Finally, show them three...