On Mon, Feb 13, 2012 at 04:20:46PM -0500, Tzu-Mainn Chen wrote:
Regarding b); I can see a reasonable use case where you might *not*
want Conductor to figure out which cloud to use on its own, so I'd be careful of
eliminating functionality there. If we were to allow both behaviours, perhaps the right
thing to do would be to create site-wide Conductor parameters, one of which would toggle
the above. Otherwise, I'd think that specific UIs would start getting too cluttered.
I definitely don't think we should *remove* any functionality; you can
use realms to lock down where an instance can be launched and we should
definitely preserve that.
What I'm thinking is that, if I have an image that's built and pushed to
EC2 and Rackspace and I go to launch it, we should do something more
intelligent than just push it to the first one on our list.
My own idea on what to focus on? Documentation. I think that we
should reorganize the wiki to a) provide documentation appropriate to different levels of
interest (high-level, CTO level, developer level), and to provide logical paths for people
to read and explore.
+1 billion (I'm being conservative)
We have new users, new developers, and people who want to kick the
tires... And all of them are going to want some sort of documentation.
Assuming that new users are going to intuitively grasp what realms do or
how to build and push an image is kind of silly, I think. I've tried to
drops lots of links in the wiki pages I've put together so we can try to
build some better documentation, but it's grossly inadequate right now.
In addition, I think that creating a "help" system within
Conductor would be of huge benefit in getting new users comfortable with the system.
Yes, this would be great, too. I know Andy Fitzsimon has talked about
integrating help into a new layout as well.
Though on that note, "Work with the Red Hat UX team to make our app more
usable" might be worthwhile, too. I have to admit that, even as someone
who works full-time on developing this app, I sometimes find myself
getting lost in our app, or I'll go to launch an instance without
remembering to set up a provider, and then I have to jump to a totally
separate part of the app.