Tasks

[Gary Poster]

Hi all.

We are blocked on the GoJuju story and the Landscape story.  We are 
partially blocked on the IE 10/FF story until we have developer access 
to Win 8.

We do have some things that we can work on though.  Please read all the 
way to the end: there are some juicy ones at the bottom of the email.

I do think we've made some good progress on tests and refactorings. 
Thank you! I hope you feel that things are a bit better in that regard.

Although I'm open to proposals on specific test improvements to make, in 
general I'd like us to pivot back towards working towards delivering our 
13.04 goals.  Please run new test cards past me before starting them.

(Nicola, you and I already talked about one refactoring option, so if 
you want to pursue that, please consider that pre-approved, despite its 
vagueness.  Do time box it to a day though, please.)

Without further ado, here are the things that can be done.  I rearranged 
the kanban board as well, so this should line up with what you see there.

- We need a release soon!  Anybody up for it?  QA is the only really 
time consuming bit, to be honest.  Brad and Francesco have done releases 
before, so you can ask them for help or advice.  docs/process.rst should 
have everything you need, though, and if it doesn't, we should fix it.

- [IN PROGRESS] Bug 1099921 is being fixed by Makyo.  It also inspired 
some related refactoring from Ben that is in review now.

- Our IE 10/FF story is not entirely blocked.  We have a few avenues 
that we can explore.
   * [IN PROGRESS] We all need copies of Win 8.  Antonio is pursuing that.
   * [IN PROGRESS] We need to have a IE10/FF CI story.  Benji is working 
on that, per his email earlier today.
   * You could make the charm able to optionally start up and expose the 
test server.  We will want to be able to write Selenium tests that 
verify that the unit tests pass on all supported browsers.  See 
https://bugs.launchpad.net/juju-gui/+bug/1110816 .
   * If you have an available copy of Win 8/IE 10, you could make some 
progress with it.  Brad is pursuing this, but lots of people can play 
here simultaneously.
     > As mentioned above, we want to be able to run our unit tests on 
our CI platform, even though that won't be delivered immediately. 
Therefore, you could verify that the unit tests pass on  IE 10, and fix 
them if they do not.
     > If you see a problem for the GUI in IE 10, you could file a bug 
for it.  Tag them "ie10," please.  I messed around with the GUI briefly 
using a remote-access IE 10, and saw two problems, which I filed as bugs 
1110723 and 1110727.
     > If an IE 10-specific bug can be tested with a unit test, you 
could go ahead and try to fix it.  Maybe you can provoke bug 1110727 in 
a unit test?

- [IN PROGRESS] Bug 1104098 is about getting the GUI working over https 
on a self-signed cert in Firefox.  Francesco is handling this with his 
haproxy work.  He made an haproxy deb in a PPA today, and tomorrow he 
will be changing the charm to work with the new haproxy and the proper 
configuration to make it all work.

- Source maps would be cool.  Bug 1110823 [1] has the meat from Benji's 
recent email.  Let's do it!  Please consult with Benji before starting.

- Orange squad will be working on the charm browser integration.  To 
prepare for that work, they need a few things done.  If we did the 
preparation for them, that would be great for a lot of reasons.  Here's 
what needs to happen.
   * Ghosts: https://bugs.launchpad.net/juju-gui/+bug/1110715
   * We need to solve bug 1075654 [2] and bug 1075656 [3] in such a way 
that Orange squad has a more solid foundation to work from when they add 
a new left panel.  The bug about the paths has some special new wrinkles 
because we will, at least for a while, have three separate areas that 
may want to have state in the URL bar: left panel, environment/center, 
and right panel.  A pre-imp with Ben might be a good choice here.
   * In-browser env: https://bugs.launchpad.net/juju-gui/+bug/1110832

- Bug 1091273 [4], having to do with different CSS ordering in prod and 
debug/devel is still interesting and potentially important.

- Bug 1104105 [5], which will let our users know directly in the GUI 
when they are using an unsupported browser, will be ready for work soon, 
once Nick has gotten a UX plan for it.

- Bug 1110515 [6], about the initial blank screen, also needs some input 
from Nick.

Do what you will, and pair when you can!

Thanks

Gary


[1] https://bugs.launchpad.net/juju-gui/+bug/1110823
[2] https://bugs.launchpad.net/juju-gui/+bug/1075654
[3] https://bugs.launchpad.net/juju-gui/+bug/1075656
[4] https://bugs.launchpad.net/juju-gui/+bug/1091273
[5] https://bugs.launchpad.net/juju-gui/+bug/1104105
[6] https://bugs.launchpad.net/juju-gui/+bug/1110515