[00:29] <hatch> juju.ubuntu.com is missing the css assets
[00:47] <rick_h_> hatch: css is working here, but a syntax error from the all-yui.js
[00:48] <rick_h_> woot for non-https assets
[00:48] <hatch> haha
[12:37] <frankban> hazmat: ping
[13:20] <bac> rick_h_: i'm an askubuntu junkie now!  :)
[13:22] <rick_h_> bac: hah
[13:23] <frankban> rick_h_: hi, how to convert a bundle:~... to a real URL to the YAML?
[13:25] <rick_h_> frankban: good question :)
[13:25] <rick_h_> frankban: frankban so everything after the : is the bundle id and should be appended to mjc/bundles/$id/json I think
[13:26] <rick_h_> frankban: sorry lied, bundle (no s)
[13:26] <rick_h_> frankban: http://manage.jujucharms.com/bundle/~jorge/wordpress/wordpress-simple/json for instance
[13:27] <frankban> rick_h_: so bundle:~frankban/wiki-bundle/1/wiki ->  http://manage.jujucharms.com/bundle/~frankban/wiki-bundle/1/wiki/json
[13:27] <rick_h_> frankban: rgr
[13:28] <frankban> rick_h_: cool thanks
[13:37] <bac> rick_h_: thanks for marking your bugs 'fix released'.  a reminder for me to do the same.
[13:38] <bac> frankban: does fusion initially give you the wrong display resolution?
[13:39]  * benji realized he wasn't on IRC.
[13:39] <rick_h_> we missed you!
[13:39] <gary_poster> :-)
[13:39] <rick_h_> bac: watch out, doing mass released from the kanban cards 
[13:39] <gary_poster> btw, hi everybody
[13:39] <frankban> bac: the display resolution seems ok
[13:40] <gary_poster> rick_h_, was going to wait till jujucharms.com, but all good
[13:40] <bac> frankban: huh, i can't get mine to come up the same between boots.  very mild annoyance.
[13:40] <rick_h_> gary_poster: oh, ok. I figured since users get it when they deploy I'd update
[13:40]  * rick_h_ hits the brakes
[13:43] <gary_poster> rick_h_, done-done not super clear, but since I think we ought to get this stuff to jujucharms.com, we ought to wait.  I need to make a card to test jujucharms.com deployment/migration, before we issue the rt.
[13:43] <gary_poster> currently wading through hundreds of mails...
[13:43] <rick_h_> gary_poster: cool, did we get the ok to not wait for the 'big annoucement' then?
[13:44] <gary_poster> rick_h_, I made an executive decision ;-)
[13:44] <gary_poster> jujucharms.com is just looking too sad
[13:45] <gary_poster> I'll clear with sally
[13:45] <rick_h_> gary_poster: yay
[13:45] <gary_poster> but I think we have to
[13:46] <hatch> morning
[13:46] <gary_poster> rick_h_, you made any secret progress on git for gui lately? :-)
[13:46] <gary_poster> morning hatch
[13:46] <rick_h_> gary_poster: :P 
[13:46] <rick_h_> gary_poster: just dreams
[13:47] <gary_poster> hatch, you running with  huwshimi's branch for first task?
[13:47] <gary_poster> rick_h_, :-) the killer is landing, right?
[13:47] <hatch> gary_poster: yep, I have it 3/4+ done
[13:47] <gary_poster> awesome thanks hatch
[13:47] <rick_h_> gary_poster: basically we'll need to write a plugin for stridercd to do per-merge CI on landing or dupe tarmac and setup jenkins for it. 
[13:47] <hatch> internet connection on the highway was very flaky unfortunately
[13:47] <gary_poster> hatch, :-)
[13:48] <rick_h_> gary_poster: exactly, everything else works, just need to write up processes and helpers for people
[13:48] <rick_h_> gary_poster: but nothing supports that "ci one more time before doing auto merge" that we expect
[13:48] <gary_poster> huh.  but stridercd gives us the hookpoint we need, as opposed to travis?
[13:49] <rick_h_> gary_poster: yea, stridercd is open source and I talked with the author and he's very interested in the idea. 
[13:49] <gary_poster> oh ok.  would we need to host it?
[13:49] <rick_h_> gary_poster: travis people think it falls outside of their 'job to do' and we can't patch it
[13:49] <gary_poster> oh, hosted beta
[13:49] <rick_h_> gary_poster: yes, probably. We could charm/run it. Now it has a hosted option, but it's not free and we'd probably have to get the patch in to work the way we want anyway
[13:50] <gary_poster> right :-/
[13:50] <gary_poster> k
[13:50] <rick_h_> which is why coming back to just replacing the tarmac bit in jenkins is almost the same thing at that point
[13:50] <rick_h_> we still have to run/setup something to do it
[13:50] <gary_poster> lol, old friend of mine is giving a stridecd quote at the bottom
[13:51] <gary_poster> " Strider's Selenium and Heroku support are killer features "
[13:51] <gary_poster> Casey Duncan, Pandora
[13:51] <gary_poster> benji, used to work at ZC ^^^
[13:51] <rick_h_> gary_poster: yea, it's actually kind of interesting and it's JS which we have some skills in house for
[13:51] <rick_h_> gary_poster: lol, small world
[13:52] <gary_poster> heroku might be free at the size we need?
[13:52] <benji> heh
[13:52] <rick_h_> gary_poster: definitely
[13:52] <gary_poster> hm
[13:52] <gary_poster> probably not something we'd want to advertise ;-)
[13:52] <rick_h_> gary_poster: I just assumed with the other teams wanting to do the same thing we'd end up wanting to charm/run it canonistack or something
[13:52] <gary_poster> yeah
[13:52] <rick_h_> gary_poster: yea, that was my instinct 
[13:52] <hatch> a few pics from my trip https://plus.google.com/u/0/+JeffPihach/posts/51jMuJDDGSY (let me know if you can't see them)
[13:53] <hatch> I'm in the blue :)
[13:53] <gary_poster> hatch, is that your nose in the blue jacket? :-)
[13:53] <gary_poster> heh
[13:54] <hatch> haha
[13:54] <hatch> twas a little cold at the top :)
[13:54] <gary_poster> yeah, I bet.  pretty tho
[13:55] <hatch> oh yeah
[13:55] <gary_poster> rick_h_, so...
[13:56] <gary_poster> rick_h_, our CI is busted now
[13:56] <gary_poster> rick_h_, ...I suppose we could have some kind of lightweight local tester as we do now...
[13:56]  * gary_poster has to step away
[13:59] <bac> frankban: how long should the charm ftest take to run?
[14:00] <bac> against ec2
[14:00] <rick_h_> bac: when I was trying to release it crossed an hour and wasn't done yet
[14:00] <frankban> ~1 hour IIRC
[14:00] <bac> gah
[14:01] <rick_h_> hatch: you good on huw's branch or need anything?
[14:01] <bac> i wish our startup messages logged the time of start
[14:01] <frankban> yeah, it deploys the charm several times, and the deployment is the slow one (download + upload)
[14:01] <rick_h_> bac: ps aux 
[14:01] <rick_h_> bac: :) it's how I was tracking time
[14:01] <bac> frankban: oh, right, and my super-fast pipe doesnt' help
[14:01] <rick_h_> bac: you can see the functional test runner start time
[14:01] <bac> rick_h_: +1
[14:01] <hatch> rick_h_: nope all good just doing some more cleanup and updating tests
[14:01] <rick_h_> hatch: coolio
[14:04] <rick_h_> frankban: looking at the card on the bundle deployment progress and it mentions a timeout will be implemented to clear old deployment info. Any idea what kind of timeout that'd be? XXseconds, minutes?
[14:04] <hazmat> frankban, pong
[14:05] <frankban> rick_h_: to be decided, hours sounds good, like 1 day, but that's really low priority
[14:06] <rick_h_> frankban: rgr, ok. Just want to make sure it's not some short time I need to worry about it leaving memory before I grab the status
[14:06] <frankban> hazmat: hey, the deployer branch I mentioned yesterday is ready for review. could you please take a look at https://code.launchpad.net/~frankban/juju-deployer/new-release-fixes/+merge/194851 ?
[14:07] <frankban> hazmat: I saw you integrated service annotations support, great!
[14:07] <hazmat> frankban, definitely already looked over, the only that give me pause is the bzrignore, wondering about *.egg in there
[14:08] <frankban> hazmat: yeah, maybe that's better, updating
[14:08] <hazmat> thanks
[14:10] <frankban> hazmat: the new diff is ready in lp
[14:19]  * gary_poster switched http://comingsoon.jujucharms.com/ back to mjc from sjc
[14:19] <gary_poster> (you may need to hard reload)
[14:20] <frankban> rick_h_: cool, thanks for taking care of that card. anyway, I suppose that clean up will be made (just to save some memory) not as cron job, but more like a callLater call when the deployment is completed, so, from the gui perspective, it should be safe
[14:20] <rick_h_> frankban: rgr, thanks
[14:24] <rick_h_> frankban: do you have a sec for a quick hangout? 
[14:25] <frankban> rick_h_: sure
[14:25] <rick_h_> frankban: https://plus.google.com/hangouts/_/76cpj35m02d9qkracsqqq5t3kc?hl=en
[14:33] <gary_poster> sometimes the best way to handle an email is a branch.  jujugui, very quick review of https://codereview.appspot.com/25220043 please?
[14:33] <rick_h_> gary_poster: looking
[14:33] <gary_poster> ty
[14:34] <benji> heh
[14:34] <benji> quote of the day
[14:34] <gary_poster> :-)
[14:40] <hatch> rick_h_: after finishing huw's branch I realize that it should be a plugin not a widget  because it doesn't actually handle rendering anything just enhancing a source node
[14:40] <hatch> any objection?
[14:41] <rick_h_> hatch: widgets can grab onto existing DOM. It's in their very nature with syncui and bindui
[14:41] <rick_h_> hatch: so maybe?
[14:41] <rick_h_> :)
[14:41] <hatch> right I've changed it to use srcNode
[14:41] <hatch> but typically a widget is a 'contained' feature with the ability to do PE
[14:42] <hatch> this can NEVER render itself
[14:42] <hatch> which pushes me to the plugin route
[14:42] <rick_h_> hatch: plugin to what though?
[14:43] <hatch> the 'dropdown' element. in this case #notifications and the help-dropdown template
[14:43]  * rick_h_ pulls up branch
[14:43] <hatch> Y.one('#notifications').plug(Y.juju.Dropdown);
[14:43] <hatch> it would then be a dropdown element
[14:43] <rick_h_> hatch: oh, the Node
[14:44] <hatch> unless at some point we want to have the widget rendering something
[14:44] <rick_h_> hatch: but then there's the ability to address it and update content, etc? call?
[14:44] <hatch> yeah sure
[14:44]  * hatch needs button in chrome to create hangout
[14:45] <rick_h_> https://plus.google.com/hangouts/_/7acpiurni6n9donhd3pfs96u0g?hl=en
[14:54]  * gary_poster disposed of emails...
[15:00] <hatch> gary_poster: after a discussion with rick_h_ we have come to the conclusion that this code needs to be refactored to be more usefull in the future
[15:01] <gary_poster> hatch, this is huw's?
[15:01] <hatch> yeah
[15:01] <rick_h_> be less of a painful to maintain in the future
[15:01] <gary_poster> hatch, k.  needs to happen now?  should I come handout to hear details?\
[15:01] <gary_poster> hangout :-P
[15:01] <hatch> sure I can run you through it
[15:01] <hatch> https://plus.google.com/hangouts/_/7acpjir38dla81ft5cqng44kvc?hl=en
[15:06] <jcastro> ok rick_h_
[15:06] <jcastro> today is the day, I can feel it!
[15:07]  * rick_h_ ducks
[15:07] <jcastro> all I really should be waiting on is the quickstart PPA to be updated?
[15:07] <rick_h_> jcastro: what's today? the day of what?
[15:07] <gary_poster> bac and rick_h_ thanks for manning askubuntu, cool
[15:07] <rick_h_> frankban: ^ ?
[15:07] <gary_poster> jcastro, what do you want there?
[15:08] <rick_h_> gary_poster: quickstart support for urls
[15:08] <jcastro> ^^^
[15:08] <rick_h_> gary_poster: it's in trunk, but not in the ppa 
[15:08] <gary_poster> oh
[15:08] <gary_poster> yeah
[15:08] <bac> gary_poster: on #juju they have a bot not listening for juju gui questions.  only way i knew about them.
[15:08] <rick_h_> gary_poster: that was the last thing we hit trying to get the 'bundle instrcutions' ready from friday
[15:08] <frankban> jcastro: working on adding bundle: support and then on a ppa release
[15:08] <rick_h_> bac: +1
[15:08] <bac> s/not/now/
[15:09] <frankban> jcastro: will ping when ready
[15:09] <jcastro> frankban, oh that makes it even easier for me
[15:09] <jcastro> awesome, thank you!
[15:09] <bac> gary_poster: and we have jcastro cleaning up after us on askubuntu.  :)
[15:09] <gary_poster> frankban, awesome thanks. when you get around to it, please also make sure the rest of us can kick to the PPA, andf know how to.  maybe doc in branch would be good
[15:10] <gary_poster> :-)
[15:10] <frankban> gary_poster: it's https://code.launchpad.net/~juju-gui-charmers/+recipe/juju-quickstart-daily owned by Juju GUI Charmers, so it should be available for everyone, correct?
[15:11] <gary_poster> frankban, definitely.  I just couldn't find it Friday when I was flailing around with a variety of things
[15:11] <frankban> gary_poster: cool, I'll add the link to the HACKING file in the branch
[15:12] <gary_poster> awesome thanks
[15:13] <hatch> frankban: I see in the emails that you got your new computer...which one did you end up getting?
[15:13] <gary_poster> frankban, fwiw next charm release should include 0.12.1 or 0.13.0 of GUI to include layout fixes (yours plus race condition I fixed Friday)
[15:14] <gary_poster> that needs to happen before jujucharms.com release
[15:14] <frankban> gary_poster: sounds good
[15:15] <frankban> hatch: macbook pro 13 2.6Ghz with 16G of memory
[15:15] <hatch> frankban: the late 2013?
[15:16] <hatch> as in .... 'new version' :)
[15:17] <frankban> yes, new version
[15:18] <hatch> awesome! have you tried to see how long the battery will last yet?
[15:25] <hatch> A microwave should calculate the time to run and make the platter end up at the same spot so that I don't have to reach for my coffee
[15:25] <hatch> *a-better-mouse-trap
[15:29] <gary_poster> rick_h_, idle thought as I mess with kanban (btw, cards that appear to disappear are usually simply moving to temporary location while I garden): high priority for me is to get CI working again, and I want to spend resources on this.  if we have a believable plan for getting this working reliably along with getting git transition, for the same cost or less than other CI work, then we have resources to work on git.  
[15:29] <gary_poster> Worth talking about later.
[15:30] <rick_h_> gary_poster: rgr, I grabbed this gui deployer status as it looked like next highest thing. I'm open to chat if something else is in fact higher
[15:31] <jcastro> gary_poster, when do you anticipate the quickstart stuff to land in a proper Juju release? (hand wavy vauge timeline is fine)
[15:31] <gary_poster> rick_h_, oh, no it is good.  my thought was "Rick wants git, and git transition would be cool even though low priority; if the hard thing is getting CI/tarmac/whatever working the way we want, then maybe we just slip Rick's existing work into that train"
[15:32] <rick_h_> gary_poster: +1 overall on the idea. 
[15:34] <gary_poster> jcastro, "landing" will be putting it in main Juju PPA, is the plan.  That works for you?  If so, we could do as soon as you like, but I wasn't planning on driving it until we had planned features and feedback.  OTOH deployer seems like it is kinda treating juju ppa as alpha/beta distribution channel, so can be sooner (now-ish) IMO
[15:35] <jcastro> you mean ppa:juju/devel?
[15:35] <gary_poster> jcastro, yes
[15:35] <gary_poster> uh
[15:35] <gary_poster> I think, checking
[15:35] <jcastro> hey so, having it in that PPA is one less PPA people would need to do a cloudfoundry one shot
[15:36] <jcastro> maybe we should toss it in there? But maybe towards the end of the week?
[15:36] <jcastro> that'll give me some time to put the bundle through its paces
[15:37] <gary_poster> jcastro, I meant ppa:juju/stable .  Yeah, we could definitely put it in ppa:juju/devel but...is that actually used by anyone? https://launchpad.net/~juju/+archive/devel
[15:37] <rick_h_> no, the proof and such aren't updated in there any more that I could tell
[15:38] <rick_h_> I ran into issues with that as I was tracking -devel and it was getting out of date packages
[15:38] <gary_poster> yeah, https://launchpad.net/~juju/+archive/stable has action
[15:44] <bac> gary_poster: please reject the expense report i just submitted.  i made an error
[15:45] <gary_poster> bac you want me to reject it, or do you want to tell me how to edit it?  if it is very small, just have me do it.  I have it open.
[15:46] <bac> gary_poster: i have two more months i missed.  would probably be easier to start over
[15:47] <gary_poster> bac, ack.  Done.
[15:48] <bac> gary_poster: do we categorize as cloud computing or misc?
[15:48] <gary_poster> bac...no idea.  I do cloud computing, I think.  checking
[15:49] <gary_poster> yeah I use cloud computing.  shrug?
[15:49] <Makyo> jujugui call in 10
[15:49] <gary_poster> thx
[15:53] <frankban> hazmat: any prevision about when my deployer branch can be merged into trunk?
[15:53] <hazmat> frankban, shouldn't be a problem, just backed up on some adhoc meetings/discussions atm
[15:53] <frankban> hazmat: ok, thanks
[15:53] <hazmat> frankban, it will get merged/released today (0.29)
[15:53] <frankban> hazmat: great!
[15:58] <gary_poster> jujugui call in 2
[15:59] <gary_poster> hatch are you leading or am I?
[15:59] <gary_poster> either is fine
[15:59] <hatch> I can
[15:59] <gary_poster> cool
[16:12] <rick_h_> frankban: linky me please?
[16:12] <frankban> rick_h_: in the cards
[16:12] <frankban> card even
[16:12] <rick_h_> frankban: rgr, thanks
[16:15] <benji> r*ck_h_: I would be glad to help you with ctags
[16:22] <Makyo> Bleh, sorry.
[16:22] <Makyo> frankban, lmk when you have time for call/card
[16:27] <frankban> Makyo: now is ok
[16:31] <Makyo> frankban,  https://plus.google.com/hangouts/_/76cpigg1rv0tkg38rclkrihns4?hl=en
[16:31] <Makyo> Maybe that works?
[16:34] <gary_poster> bac approved expenses
[16:42] <rick_h_> frankban: any reason to qa on ec2 vs lxc? 
[16:42] <frankban> rick_h_: quickstart does not support lxc (which requires sudo)
[16:42] <rick_h_> frankban: oh, it works if it's already bootstrapped though?
[16:43] <frankban> rick_h_: no, we have a card to make quickstart use a bootstrapped env
[16:43] <rick_h_> frankban: ah, ok then
[16:45] <rick_h_> benji: cool, I was trying a npm library that failed to work out. Then tried to do a custom ctags language for js, but ctags won't read the .ctags options file. 
[16:46] <benji> rick_h_: oh, I thought you were doing Python; I have only put a little effort into JS.  Maybe now is the time to do a bit more.
[16:47] <rick_h_> benji: yea, the scope of the go.js env file got me going "Man I wish I had that tag listing sidebar plugin going on here"
[16:47] <rick_h_> I don't normally use it, but somehow clicked today and ctags'ing things fell over 
[17:11] <gary_poster> hey benji, we have a card in bundles section that is "add a collection for metrics to charmworld."  You've done that, right?
[17:11] <benji> gary_poster: yep
[17:11] <gary_poster> cool thanks
[17:46] <gary_poster> jujugui, I just did a pretty harsh kanban rejiggering.  if you are looking for a pre-existing card that you think we need to handle soon, look in backlog (see link at top of kanban).  meanwhile, other cards are pretty streamlined.  Maintenance, Quickstart, and Multi-step maintenance task lanes all have good things to do.  Green "story" cards in maintenance should probably wait for the multi-step maintenance task lan
[17:46] <gary_poster> e to open up, and then only one green card at a time is active down there.  Lemme know if you have any questions.
[17:47] <gary_poster> hatch, any card out is good, or if you want to declare that another small bug card is a must-have, feel free. Meanwhile, there are some good cards in maintenance: high that I marked with the GUI icon for easy visual identification
[17:47] <gary_poster> (the monitor with a globe in it)
[17:48]  * gary_poster lunches
[17:50] <hatch> great thanks
[17:50] <hatch> I'm having issues lbixing for some reason so trying to land this branch
[17:50] <Makyo> jujugui easy quickstart review https://codereview.appspot.com/25340043
[17:53] <gary_poster> Makyo, did you and frankban consider an option to automatically remove juju-gui?  Would be easy and nice I'd argue, but it's an idea I'd prefer you all to evaluate the merits of.
[17:53] <gary_poster> (rather than you regarding this message as a request :-) )
[17:53] <gary_poster> maybe spelling is the hardest part.
[17:54]  * gary_poster really runs away now.
[17:54] <bac> jujugui: very small makefile change to charm: https://codereview.appspot.com/24790045
[17:54] <bac> Makyo: i'll look
[17:54] <hatch> bac: i'll take it
[17:54] <Makyo> bac, thanks.
[17:54] <frankban> gary_poster: I considered that, but it seems part of the interactive story, I suggested the current behavior as a first step. Also consider an evil bundle with a service named juju-gui but that's really another kind of service, with relations...
[17:55] <hatch> bac: lgtm'd
[17:56] <hatch> grrrr test failures when run together
[17:58] <bac> was that grrr aimed at me?
[17:58] <hatch> bac: nope, at our test suite
[17:59] <hatch> your all good to go :)
[18:02] <frankban> jcastro: quickstart v0.3.0 released on the ppa
[18:03] <hatch> gary_poster: wow that's quite the rejiggering! any chance we can clear out the Releasable column?
[18:05] <hatch> oo there are some juicy ones in High
[18:05]  * hatch pushes everyone away and grabs them all for himself
[18:05] <hatch> miiiiiiine alll miiiiiiine
[18:05] <Makyo> Go for it :P
[18:06] <hatch> it's a right triangle of GUI cards
[18:06] <hatch> how cute
[18:07] <jcastro> frankban, ok updating
[18:08] <jcastro> rick_h_, should I file a bug for the gui for using out of date instructions now?
[18:08] <jcastro> wget -O bundle.json https://manage.jujucharms.com/bundle/~jorge/cloudfoundry/3/cloudfoundry/json 
[18:08] <jcastro> and friends, we probably don't need to do that anymore?
[18:09] <jcastro> frankban, so how do I use this bundle: url, assuming this is the bundle I want to try
[18:09] <jcastro> http://comingsoon.jujucharms.com/sidebar/search/bundle/~jorge/cloudfoundry/3/cloudfoundry/?text=cloudfoundry#bws-deploy
[18:09] <frankban> jcastro: yeah, the quickstart instructions can be simplified.
[18:09] <rick_h_> jcastro: yea, we'll update the instructions to not use wget
[18:10] <frankban> jcastro: for example: "juju quickstart -e ec2 bundle:~hatch/wiki/7/TestBundle"
[18:10] <rick_h_> jcastro: so with the ppa it would just be juju quickstart bundle:~jorge/cloudfoundry/3/cloudfoundry
[18:10] <rick_h_> jcastro: that url is in the top of the window there by the icon as "Location"
[18:10] <rick_h_> jcastro: so we'll move that down to the quickstart command
[18:11] <jcastro> ahhh!
[18:11] <jcastro> wooo, it's working!
[18:12] <bac> Makyo: LGTM w/ QA
[18:12] <bac> one small request
[18:12] <rick_h_> jcastro: aseome, glad to hear
[18:12] <rick_h_> err, awesome
[18:12] <jcastro> this one works with constraints
[18:12] <Makyo> bac, Sure.
[18:12] <jcastro> so am I safe to add constraints to say, discourse? 
[18:12] <rick_h_> jcastro: yep, constraints should be fine now
[18:13] <frankban> jcastro: yes, it shoudl work with constraints
[18:13] <rick_h_> jcastro: yea, you should get an error now if the constraints are invalid
[18:13] <jcastro> and what about deploying --to one node?
[18:13] <rick_h_> jcastro: you can only use the gui supported constraints right now
[18:14] <rick_h_> hmmm, I thought there was a --to support in there. I don't think we support it via quickstart right now
[18:15] <frankban> jcastro: unit placement is supported by the new juju-deployer, that will be integrated soon (hopefully tomorrow) in the gui charm. that means bundles with unit placements should just work. that said, the GUI does not support unit placement, and AFAICT does not include placement info in the bundle exports
[18:16]  * jcastro nods
[18:16] <jcastro> ok so I can manually add it into the bundle in the meantime
[18:17] <frankban> jcastro: I think it's worth a try. I can test one bundle with placements, if you provide one, tomorrow or in two days, after the gui/guicharm are released
[18:18] <jcastro> ok
[18:21] <jcastro> heh, moved my environments.yaml out of the way to see what would happen
[18:21] <jcastro> but prompting for creds is for v2 of bundles right?
[18:22] <frankban> jcastro: not yet implemented. instead of moving your env.yaml you can also run, e.g. "JUJU_HOME=/tmp juju quickstart" ;-)
[18:22] <jcastro> ah, good tip!
[18:29] <rick_h_> bah, irc locked up
[18:29] <rick_h_> jcastro: you can manually add it, but quickstart won't support it. The raw deployer command looks like it would though
[18:33]  * hatch bouces head of desk....feels better than dealing with cascading test failures
[18:33] <gary_poster> hatch, "any chance we can clear out the Releasable column?": yeah.  wanted to do it after jujucharms.com release.  I wanted that annoyance (of the big column) to help push us to do so, and remind us that jujucharms is so far behind. But whatever, if everyone wants me to move 'em, we'll get it done either way. :-)
[18:33] <hatch> haha sounds good
[18:38] <hatch> note to self...manually removing a views container will trigger a test suite 20s later to fail with node.js errors *head....desk*
[18:39] <rick_h_> hatch: why was the view around 20s later?
[18:40] <hatch> rick_h_: now that's the question isn't it?
[18:40] <rick_h_> hatch: hehe
[18:49] <hatch> jujugui looking for a review of my refactoring from huw's branch https://codereview.appspot.com/25390043/
[18:49] <rick_h_> hatch: looking
[18:49] <hatch> thanks
[18:49] <hatch> I think it turned out pretty well
[19:06] <rick_h_> hatch: feedback inbound, few questions for you
[19:06] <rick_h_> hatch: please take a peek while I QA
[19:06] <hatch> alright
[19:14] <hatch> rick_h_: good catch on the fullscreen
[19:14] <hatch> because there is a card to remove that right away, should we bother with trying to prevent ti?
[19:14] <hatch> prevent/refactor to catch that
[19:15] <rick_h_> hatch: not sure, I mean if we do a release tomorrow/thurs it'll be a broken thing 
[19:15] <rick_h_> until the next release of jujucharms.com, I'm not a big fan of knowingly breaking it for some underterminate amount of time 
[19:15] <hatch> yeah....good point
[19:15] <hatch> damn I hate doing work that I know is goign to be deleted very soon :)
[19:16] <hatch> ok going to lunch then will fix
[19:16] <rick_h_> hatch: I'd say the quickest hack would be to navigate to the sidebar url and turn on the tour? 
[19:16] <rick_h_> e.g. if you click on 'show me the tour' it takes you to it?
[19:16] <hatch> yeah that's probably the easiest
[19:20] <rick_h_> hatch: heh, yea, since the first item in the turorial is to highlight the sidebar, which in fullscreen just gets you a nice grey bar down the side of the page
[19:20] <rick_h_> I was wondering if maybe the tutorial can just show on fullscreen as well, guess not :/
[19:44] <hatch> rick_h_: bleh I don't like anything I come up with for the sidebar
[19:44] <hatch> fix
[19:44] <rick_h_> hatch: :/
[19:44] <hatch> either I have to pass extra stuff in
[19:44] <hatch> or I have to add event listeners
[19:45] <rick_h_> hatch: so I'd vote we hide that link for now, just comment it out. Test it though. 
[19:45] <gary_poster> Makyo, hey.  I wanted to triage the bundle vis bug, so investigated.  This seems to address.  Could you see what you think?  http://paste.ubuntu.com/6407015/
[19:45] <hatch> rick_h_: I'll take that!
[19:45] <rick_h_> hatch: and then when adding the allview.js it can watch/be tied to the onboarding there
[19:45] <rick_h_> hatch: at least the events have a common place to work together there, agree?
[19:45] <hatch> right - when we are within a 'parent' view then it'll make more sense
[19:46] <rick_h_> hatch: right, and the parent can work on handling the nav or whatever needs to be done. 
[19:46] <hatch> yeah
[19:46] <rick_h_> though onboarding has to come out of browser.js for that :/
[19:47] <rick_h_> hatch: thoughts on making the help menu part of browser.js like the onboarding then?
[19:47] <Makyo> gary_poster, That will work, I think! I don't know that it will always work if called again if we plug in pan and zoom in, but if we only ever set the centroid once on load, then I guess that's the only time we need it to work.
[19:47] <hatch> well with fullscreen gone then the onboarding and help can go into the 'parent' view
[19:48] <rick_h_> hatch: right, but that's farther away than I want to count on for now tbh
[19:48] <rick_h_> we've been saying it was going away for a while now
[19:48] <rick_h_> making architecture decisions on that seems cheating
[19:48] <gary_poster> Makyo, ok cool, thanks.  I'll see what tests exist for this and run with it.
[19:49] <Makyo> gary_poster, awesome.  Guess it helps to have a fresh set of eyes on it.  Had my head in the sand about that stupid centroid problem, but if we want to just use a bounding box for statically positioned elements, then that should also work.
[19:50] <gary_poster> cool Makyo :-)
[19:54] <hatch> rick_h_: I'm using a navigate event because I didn't think that removing one of the features was ideal either....at least this is easy to remove later
[19:54] <rick_h_> hatch: rgr
[19:55] <bac> rick_h_, gary_poster: would either of you have a few minutes to chat?
[19:55] <rick_h_> bac: sure
[19:55] <bac> rick_h_: cool, i'll invite you
[19:56] <rick_h_> I can quit harrassing hatch for a minute :)
[19:56] <hatch> hah
[19:56] <gary_poster> I can too, bac.  tell me if you want me
[19:56] <hatch> the navigate isn't working properly either - edge cases
[19:56] <hatch> bleh
[19:56] <rick_h_> hatch: heh, well update the rest and push it up and we can take a look at it. There must be something that's not too horrible to do
[19:56] <rick_h_> hatch: what edge case did you hit?
[19:57] <hatch> if you land on a fullpage page from the url the onboarding instance is never created
[19:57] <rick_h_> bac: sec, chrome updated and wants a plugin there
[19:58] <bac> rick_h_: not letting you join?
[19:58] <rick_h_> bac: moving to FF
[20:00] <bac> rick_h_: you want to invite me (canonical me)
[20:00] <rick_h_> bac: ok, got in https://plus.google.com/hangouts/_/76cpjh1086s40kevifkj5fa1ng?hl=en
[20:02] <gary_poster> Makyo, https://codereview.appspot.com/25460043 ?
[20:03] <Makyo> Looking
[20:03] <gary_poster> thanks
[20:08] <bac> gary_poster: can you join a chat ?  https://plus.google.com/hangouts/_/76cpjh1086s40kevifkj5fa1ng?hl=en
[20:25] <rick_h_> hatch: ok, so thouoght on that
[20:25] <rick_h_> hatch: why not do something in the navigate to tell onboarding to 'force show'?
[20:25] <hatch> the instance doesn't exist
[20:25] <hatch> so it would need to be created then
[20:26] <hatch> and 'pushed' into the browser
[20:26] <hatch> I really think we can accept the 'highlight left bar which isnt' there' issue in fullscreen
[20:26] <hatch> they should have already seen it once
[20:26] <rick_h_> hatch: huh? you navigate and it hits the browser, the browser can check query strings and force show the onboarding 
[20:27] <rick_h_> huh? how is that? jujucharms.com forces to fullscreen by default. There's a reasonable chance they didn't see it
[20:27] <hatch> I suppose...
[20:27] <hatch> what if I remove fullscreen this week? lol
[20:27] <rick_h_> heh, have fun
[20:28] <hatch> parsing query strings requires a bunch of testing too
[20:28] <rick_h_> hatch: sure, it needs one test in the test_browser_app and one for a flag passed into the init of the onboarding view?
[20:28] <gary_poster> hatch, rick_h_ not really following along, but if you think I can try to eliminate requirements, I'm happy to try
[20:29] <rick_h_> gary_poster: well the first step is to remove the button to re-show the onboarding right now
[20:29] <gary_poster> ?
[20:29] <hatch> rick_h_: well that but also the 'renderOnboarding' method is only called in the sidebar method
[20:29] <rick_h_> gary_poster: but working around that, there's the issue of getting the browser-based "show only in sidebar" onboarding link working when clicked from the help menu in fullscreen
[20:29] <hatch> so browser doesn't even support it in fullscreen right now
[20:29] <rick_h_> hatch: right, and navigate will hit that
[20:29] <gary_poster> can we simply not show the linkl when in fullscreen?
[20:29] <rick_h_> hatch: call please? I feel like we're passing by on a step
[20:30] <gary_poster> are the links actually vauable in fullscreen?
[20:30] <rick_h_> gary_poster: no, the first stage of the onboarding is to highlight the sidebar charm view
[20:30] <hatch> yes it's rendered once on load
[20:30] <hatch> sure we can call
[20:30] <hatch> just logging in
[20:30] <hatch> I got logged out
[20:30] <rick_h_> hatch: right, and you'll hit that sidebar method on every load
[20:30] <gary_poster> rick_h_, ...right, but we already are supposed to have code that prevents onboarding when you start out in fullscreen
[20:30] <rick_h_> hatch: k, sec door
[20:31] <hatch> gary_poster: the dropdown bypasses that and shows it manually
[20:31] <hatch> because it accesses the onboarding instance directly
[20:31] <gary_poster> hatch, so don't either show dropdown when in fullscreen, or don't show that part of the dropdown (or gray it out) in fullscreen
[20:32] <hatch> it's rendered once
[20:32] <hatch> there is no 'if fullscreen'
[20:32] <hatch> I actually like that better though
[20:32] <gary_poster> and it doesn not respond to "display: none" ? :-P?
[20:32] <hatch> more to rip out soon but not as workaroundy
[20:32] <hatch> well nothing knows it's in fullscreen
[20:32] <gary_poster> events fire!
[20:32] <gary_poster> handlers handle!
[20:32] <gary_poster> excitement mounts!
[20:33] <hatch> I'm not sure the app knows if it's in fullscreen or not
[20:33] <rick_h_> hatch: k, sorry, wheels arrived yay
[20:33] <rick_h_> hatch: calling
[20:33] <hatch> link?
[20:33] <hatch> google hates me
[20:33] <gary_poster> pretty sure we fire events, and if not, +1 on adding events assuming this is fast
[20:34] <rick_h_> https://plus.google.com/hangouts/_/72cpinh2n9qbc8gp1jfl222g6c?hl=en
[20:34] <rick_h_> I think a hard coded navigate with a ?force-onboarding=true will work easy enoough
[20:35] <gary_poster> "easy" and reasonable enough UX is my interest.  we're ripping this out, so be open minded about solutions
[20:37] <hatch> gary_poster: rick_h_ convinced me of uglyness
[20:37] <hatch> :)
[20:37] <rick_h_> it's not that ugly :P and like you keep saying, fullscreen is going away
[20:37] <gary_poster> hatch, rick_h_ if fast, I'm ok.  if not fast, let me try to make a case :-)
[20:37] <hatch> it's fast
[20:37] <hatch> :)
[20:38] <rick_h_> gary_poster: yea, I think it's a few lines. < 10 + tests
[20:38] <gary_poster> awesome
[20:39] <hatch> for some reason google thinks gary and I have been in a call all day and won't let me join any more
[20:39] <rick_h_> lol, that's ok. Chrome is going nuts on me and won't load the hangout extension but FF will 
[20:39]  * rick_h_ is living on the edge
[20:39] <hatch> haha
[20:39] <rick_h_> drag-n-drag is borked in the new dev update from today wheeee
[20:40] <rick_h_> ok, my head is killing me. I'll check in later hatch to help get this unblocked. Thanks for working through getting it going
[20:40] <hatch> enjoy time away from the lcd :)
[20:42] <rick_h_> hatch: still confused on https://codereview.appspot.com/25390043/diff/1/test/test_dropdown_extension.js#newcode33
[20:42] <rick_h_> hatch: in looking at your reply 
[20:42] <hatch> looking
[20:42] <rick_h_> hatch: oh, the code isn't updated yet
[20:42] <rick_h_> ignore me
[20:42] <hatch> oh yeah
[20:42] <rick_h_> just going through your comments back
[20:43] <hatch> I was going to push it but will now when this linking is fixed
[20:43] <hatch> lboxing takes a long time on my laptop :)
[21:30] <hatch> being able to redo the kanban board like this is pretty cool, definitely wouldnt be doing that if it was on a wall :)
[21:34] <hatch> rick_h_: new version is up on codereview it'll require another qa unfortunately
[21:46] <rick_h_> hatch: will take a look
[21:47] <hatch> thx
[21:51] <gary_poster> bundle vis svg highlight is offset to left a bit in FF. :-/
[21:51] <hatch> blarg
[21:51] <gary_poster> not important enough to prioritize, but a shame
[21:51] <gary_poster> if you feel like tackling quickly feel free ;-) but not worth a lot of time
[21:51] <gary_poster> IMO
[21:52] <hatch> yeah that's kinda ugly
[21:52] <hatch> it almost looks like that's how it's supposed to be haha
[21:52] <gary_poster> heh
[21:53] <hatch> gary_poster: still not MBP review from anandtech yet hey? :/
[21:53] <gary_poster> hatch, :-)
[21:55] <gary_poster> hatch, may just wait till next.  trying not to spend 2-3K unnecessarily ;-)  Laptop is falling apart but mostly work on desktop.  Must...protect...bank balance...
[21:55] <hatch> haha yeah I'm in the same ballpark although it sure would be nice to have a better machine for the sprints and whatnot
[22:01] <rick_h_> hatch: ok, review is a lot nicer, a few comments, pulling down to qa now
[22:04] <rick_h_> hatch: LGTM aside from the small set of notes 
[22:04] <rick_h_> hatch: thanks for pushing it
[22:11] <gary_poster> night all
[22:11] <hatch> cya!
[22:12] <gary_poster> :-)
[22:12] <hatch> rick_h_: cool so are you going to lgtm on the review?
[22:12] <rick_h_> hatch: I did, but did you tweak the things in the review?
[22:13] <rick_h_> hatch: though note this requires two reviews
[22:13] <rick_h_> hatch: because it's over size
[22:13] <hatch> just about to finish
[22:13] <hatch> oh right
[22:13] <rick_h_> hatch: cool
[22:13] <rick_h_> maybe you can bribe Makyo :)
[22:14] <Makyo> Sure
[22:15] <hatch> Makyo: thanks - i'm just lboxing with the new changes
[22:15] <Makyo> Will keep an eye out then :_
[22:15] <Makyo> :)
[22:19] <hatch> ohhh lboxxxxx
[22:21] <hatch> Makyo: https://codereview.appspot.com/25390043/ thanks
[22:22] <hatch> +666 diff :O
[22:22] <Makyo> D:
[22:49] <hatch> hey gary_poster|away any chance you're around?
[23:11] <Makyo> hatch, the "show tutorial" link doesn't do anything for me; is that next iteration?
[23:11] <hatch> hmm it should...
[23:11] <hatch> sidebar or fullscreen?
[23:11] <Makyo> Sidebar.
[23:11] <hatch> ok checking
[23:12] <Makyo> It was the first link I clicked after just loading /
[23:12] <hatch> oh what the
[23:12] <hatch> :/
[23:12] <hatch> arg ok thanks I'll figure it out
[23:14] <hatch> weee
[23:18] <hatch> Makyo: ok I have no idea wth is going on sorry I'll have to figure this out
[23:19] <Makyo> hatch, okay, good luck.  Code otherwise LGTM, will re-qa when you're ready.
[23:19] <hatch> ok i think I got it
[23:19] <hatch> localstorage converts everything to a string
[23:21] <hatch> Makyo: ok re-proposing
[23:21] <hatch> when is your EOD?
[23:22] <Makyo> Half an hour, but no qualms about giving more time.
[23:22] <hatch> gary_poster|away: whenever you have a spare moment lp:~hatch/juju-gui/hide-on-relation create a relation and watch the inspector - I found 'hiding' it to jarring
[23:22] <Makyo> Dinner's already cooking.
[23:22] <hatch> :) my EOD was 20mins ago but I wanted to get these two branches done hah
[23:23] <hatch> I want to start off on a good note lol
[23:27] <hatch> Makyo: ok updated, should work now :)
[23:27]  * Makyo pulls.
[23:28] <Makyo> I'm REALLY sorry, hatch, but one more thing.  After opening onboarding from that link, I can't close it because force-onboarding is still in the URL.
[23:29] <rick_h_> Makyo: ooh, good call 
[23:29] <hatch> UGH!
[23:29] <Makyo> I wind up with http://localhost:8888/sidebar/?force-onboarding=true#/sidebar/?force-onboarding=true
[23:30]  * hatch rages on fullscreen
[23:30] <hatch> now I have to fire events from onboarding to navigate
[23:31] <rick_h_> hatch: or go to localstorage during navigate
[23:32] <rick_h_> hatch: it's dirty, but the navigate call can clear the localstorage, put a big XXX: GAHHHH in there
[23:32] <hatch> oh I see what the issue is
[23:32] <hatch> the cross handler is wakobuziness
[23:32] <rick_h_> cross handler?
[23:34] <hatch> well iunno what's going on
[23:35] <hatch> somehow clicking the X is triggering a navigate
[23:35] <hatch> button it is
[23:36] <hatch> there we go
[23:40] <hatch> Makyo: ok new fix coming down the line
[23:41]  * hatch shakes fist, it better work this time
[23:47] <hatch> Makyo: ok done
[23:47] <hatch> er up
[23:52] <Makyo> Hm.  Up to you on this one if you want to push it to another branch.
[23:54] <Makyo> Closing onboarding leaves 'force-onboarding' in the url.  Everything works, but if you navigate to fullscrean, when you navigate -back-, it opens onboarding.  Could additionally show up if someone bookmarks that URL. I would not be opposed to a smaller branch done soon after if you want to tackle that separately, though that depends on our release plans.
[23:55] <hatch> I'd rather not have this url stuff in there to begin with because it's just a hack to workaround fullscreen stuff
[23:55] <Makyo> Understood.
[23:55] <hatch> so....hmm
[23:55] <hatch> on close I could fire another navigate event to clear it out
[23:55] <Makyo> Fullscream.
[23:56] <rick_h_> hatch: ditch url param go with localStorage, session, something you can set/clear invisibly
[23:56] <hatch> lol yes
[23:56] <Makyo> Yeah?  Would it just be whatever the URL is minus the force-onboarding query?
[23:56] <hatch> rick_h_: good idea
[23:56] <Makyo> +1
[23:56] <hatch> I'll deal with that in the morning
[23:57] <hatch> right now I have a Go vs Javascript talk to prepare for Saturday