Comment 7 for bug 399957

In order to support the "only admins should be able to move a community from
private to public", I had to go add a feature to our workflow machinery which
allows a permission to be attached to a transition. Currently, only one such
permission is used (the community transition from private to public is protected
by the "administer" permission).

Note that this policy is in effect for osi, eurasia and oxfam.

Currently the UI doesn't participate in this scheme however, so the radio
buttons are shown on the edit form to users regardless. A user without the
"administer" permission will receive a traceback when he attempts to transition
a community from private to public.

A method named "transition_info" exists on the workflow object which we can use
to populate the "private/public" radio buttons. It returns all transitions
available to the current user.

We might consider making each available security transition (from
"transition_info") into a dropdown "action" on the top bar rather than a dialog
on the edit page of communities (and all other content). This would probably
make more sense than making it part of the edit form from a "framework" perspective.

- C