On Tuesday, November 18, 2014 10:17:28 PM UTC-8, Patrick Schaaf wrote: > > > Am 18.11.2014 22:23 schrieb "RjOllos" <[email protected] <javascript:>>: > > > > Proposed change to allow groups to be specified in the `set_owner` > attribute in #11839: > > http://trac.edgewall.org/ticket/11839 > > Yeah! :) > > One question after looking at that change: is it established convention > now that everything starting with an uppercase letter, is a permission, and > everything else is not? In other words, permission "groups" might NOT start > with an uppercase letter? > > In our deployment, we use the convention > * usernames are all lower case > * Group_Names are mixed case > * PER_MISSIONS are ALL uppercase > which would clash a bit with the scheme as you implemented it. No big > deal, should we ever get around to upgrading to a current trac version we > could easily change our scheme. Just saying. > > best regards > Patrick >
I believe the only constraint in the Trac code should be that all-uppercase are permission names. That's specified on the TracPermissions page (1). "Use at least one lowercase character in user names, as all-uppercase names are reserved for permissions." The "if not perm[1].isupper()" condition in in the list comprehension for all_groups says that any permission that is not all uppercase is a group name. Permission groups can therefore be all lowercase or mixed-case. I think your scheme should work fine with the patch. (1) http://trac.edgewall.org/wiki/TracPermissions#GraphicalAdminTab -- You received this message because you are subscribed to the Google Groups "Trac Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
