For users who are not admins and not owners of a group, the group page shows a cut-down read-only view. In particular, the "Group Owner" column is omitted which means it is not possible for a non-owner to determine who the owners of the group are. That means they have no easy way to figure out who they should ask if they want to be granted membership. Additionally, I think the list of members should sort owners to the top, to make them easier to spot.
The cut-down read-only view also doesn't display the fact that a group is populated from LDAP, which is important for users to know.
Fwiw, the command line subcommand 'group-members' does identify the owners (http://beaker-project.org/docs-develop/man/bkr-group-members.html).
On Gerrit: http://gerrit.beaker-project.org/#/c/2172/
test on beaker-devel(2013.8.21)-->partly fail steps: 1. non-admin and non-owner user check the group ownership on group page.-->pass 2. non-admin and non-owner user check the page of group populated from LDAP.-->pass 3. the list of members should sort owners to the top, to make them easier to spot.-->fail
(In reply to wangjing from comment #6) > test on beaker-devel(2013.8.21)-->partly fail > steps: > 3. the list of members should sort owners to the top, to make them easier to > spot.-->fail Didn't realize that this was mandatory. Anyway, suggestions welcome for how this can be done.
Patch for showing the owners first: http://gerrit.beaker-project.org/#/c/2178/
verified on beaker-devel(2013.8.26)-->pass steps: 1. non-admin and non-owner user check the group ownership on group page.-->pass 2. non-admin and non-owner user check the page of group populated from LDAP.-->pass 3. the list of members should sort owners to the top, to make them easier to spot.-->pass
Beaker 0.15 has been released.
This change has been nominated to be back ported to the 0.14 branch, to be released as part of the next maintenance release 0.14.2. Adjusting target milestone to make the changes backported to 0.14.2 easier to identify. 0.15.0 has enough significant regressions that it shouldn't be used, so the change means that 0.15.1 can be effectively reidentified as the union of that tag and the 0.14.2 target milestone.
Closing as addressed in Beaker 0.14.2.