File-sharing vs. Casual Collaborator is a distinction we're drawing kind
of arbitrarily, isn't it? I imagine there could be people who start as
Casual Collaborators, but learn about file sharing, and decide they want
to use it. Putting access to the home collection browser into a dropdown
menu just gets it out of people's way. If they have no interest in the
feature, they don't have to look at a button or nav link for it.
As the Cosmo UI matures, I suspect there will be more things like that,
that only certain groups want to use (the so-called 80% rule -- but of
course everybody has a different 80%), and putting stuff into menus is
an easy way of giving people easy access to all the features, but not
forcing everyone to see a link or button for everything.
The home collection browser is just the first example of this kind of
"everybody probably won't want that" functionality.
And, if administrators decide they actually want to keep people from
using the home collection browser, of course it would be easy to switch
that item off in the menu based on a server-wide setting, as BCM said.
Matthew
Mimi Yin wrote:
Ah ic. Yup these are reasonable assumptions. We can certainly do this
for admins. But how will we tell the difference between file-sharing
users versus Casual Collaborator users?
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design
