Documentation: Administrator

[laszewsk]

Revisit the review of the README to see if the README is actually the documentation for the Administrator.

How is the administrator interfacing in the workflow for users, committee members?

[avaradha]

My assumption for this command line tool was that it would be solely used by an administrator to setup and manage users.

I can visualize an workflow when we use an GUI kind where user will apply for an account and the request goes into a queue for a committee member picks up to review the request. But not able to visualize similar approach for a command line tool...

[laszewsk]

The value of this framework is beyond admin usage, e.g. two additional roles are part of the project

a) a user role

how does a user actually apply for an account and project and how does he interact with it.

this could have been done via a commandline tool, a gui would not have been needed

b) a comittee role

e.g. how is a project reviewed by a comittee. This could have been done by a commandline tool, a gui would have not been needed

In general it seems that this framework misses the role management that can be implemented either via using the flask role modules as used in cloudmesh, or via a specific authentication request to a backend service that allows to identify if I am an administrator, user, or comittee member. There is no reason that this could not have been implemented in the command line tool.

On May 6, 2015, at 1:32 PM, Aravindh Varadharaju notifications@github.com wrote:

My assumption for this command line tool was that it would be solely used by an administrator to setup and manage users.

I can visualize an workflow when we use an GUI kind where user will apply for an account and the request goes into a queue for a committee member picks up to review the request. But not able to visualize similar approach for a command line tool...

—
Reply to this email directly or view it on GitHub #11 (comment).

[avaradha]

Have updated the code set to fix the issue..