Default user feedback

[Tim Penhey]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 02/04/13 22:15, John Arbash Meinel wrote:
> I'd like to open up a discussion about how much user-feedback to
> give while running the "juju" client, and how we go about providing
> that feedback internally.
> 
> Right now, juju commands are generally silent by default (no
> output unless --debug or --verbose[1] is supplied, unless there is
> a one line error report).

I agree with Dave and William that we should chat about this in
Oakland, but I'd like to voice my opinion first :-)

tl;dr I agree with John with user focus first.

I'm very much aligned with John on this.  The default output of the
command should give some terse output indicating success.  Often just
a line is enough to tell the user what is going on.

For scripting where silence is the preferred option, I think a '-q' or
'--quiet' would work well, and there is a lot of precedence for this
in other programs.

To me '-v' or '--verbose' does not mean I want to see logging output,
but to see more information about the steps that the command is going
through.

- --debug is fine to get the logging information shown as well.

Happy to defer this conversation until Oakland (prefer this actually),
but just wanted to put this out there for people to think about before
we get there.

Tim
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlFbPQAACgkQd1fvI4G7WRD2iQCgogxpUuFGTCdLjgiGk9sRAOaI
ZX8AoJyKdoQTNJns+D9IO8e2gJkJi0JM
=nA8B
-----END PGP SIGNATURE-----