[Cosmo-dev] Re: Legal compliance features

[Jared Rhine]

Brian Moseley wrote:
> * the hub web site could present its own terms of service agreement
> workflow before providing a link to the cosmo signup dialog.

Feasible.  I think we want a nice, short, sweet signup though, so I'm 
reluctant, usability-wise, to go to multi-page process.  Do you think 
multi-page is good-enough for how you envision the service?

> * if that's not good enough, the hub could provide its own signup form
> that uses cmp to create the user account. to keep educated users from
> invoking the cosmo signup dialog, we could provide a server
> configuration option to disable the signup dialog.

Attractive (go non-AJAX/Dojo and speed up this page load to 
milliseconds).  There's worry about the resource hit to properly build a 
production-quality alternate signup.  I'd be capable of building one for 
Preview, but some other task would likely need to be dropped and Mimi 
would probably need to drop something else too.

> * we can provide one or more customizable areas in the ui layouts
> which you can fill in via message properties, where you can place a
> terms of service link.

This would be an helpful enhancement for all administrators of Cosmo and 
a preferred way to implement the TOS link on the PIM page.

> * we can potentially add a "content locked" flag to a user account and
> check that flag before any access to content, returning 403 if the
> account is content locked. or would you want this behavior any time an
> account is "access locked"?

I generally like fine-grained control, so more switches and knobs seems 
attractive.  Though in this case, I'm not sure whether "content locked" 
but "access unlocked" is a useful state.  Is this something you could 
see wanting as an administrator?

Given available resources, I think the most expedient thing to do for a 
TOS during signup would be a hacky addition properties to Cosmo SVN: the 
equivalent of "cosmo.ui.confirm_tos_during_signup" and one 
Message.properties for the text to output next to a checkbox, with some 
AJAX logic to confirm the checkbox is selected before sending a CMP 
signup request.

I'm sympathetic to code cleanliness issues, as something's not perfect 
in this implementation.  I'm hoping you can let that slide here :)

-- Jared