[13:50] <hatch> busy here today!
[13:50] <rick_h__> wheeee
[13:55] <hatch> rick_h__ any idea what the best way is to pull down a branch from a merge request for qa?
[13:55] <rick_h__> hatch: git checkout -b qa-something
[13:56] <hatch> right, except the pr page doesn't include the full paths anywhere does it?
[13:56] <rick_h__> actually it's in the pull request notes
[13:56] <rick_h__> look at the block with the "Merge pull request" button
[13:56] <rick_h__> there's a not about "on the command line"
[13:56] <rick_h__> skip step 1, just go to develop, create a new branch to qa into
[13:56] <hatch> ahhh, I totally missed that link
[13:57] <rick_h__> and do step 2
[13:57] <rick_h__> qa, and then comment on the pull request
[13:57] <rick_h__> obvious skip step 3 since that's a landing step
[13:57] <hatch> yup, I just didn't want to go and get the url myself :)
[13:57] <hatch> <--- lazy today
[13:58] <rick_h__> there's another way
[13:58] <rick_h__> if you do a git fetch, and you've got pull reqests in your refspec
[13:58] <rick_h__> it'll note them and you can git pull origin/$huwsbranch I think
[13:58] <rick_h__> sec
[13:59] <hatch> hmm right but I have uncommitted changes in my active branch and have to stash them
[13:59] <hatch> I will make a qa'ing repo
[14:00] <rick_h__> hatch: k, so git stash
[14:00] <rick_h__> hatch: and then git co develop
[14:00] <hatch> right
[14:00] <rick_h__> git co -b qz
[14:00] <rick_h__> qa 
[14:00] <hatch> git stash makes sublime over ssh go crazy
[14:00] <hatch> it like loses track of the file references or something
[14:01] <rick_h__> hatch: looks like really good http://www.somethingorothersoft.com/2012/05/22/pulling-github-pull-requests-with-git/
[14:01] <gary_poster> rick_h__, git make distfile conversation after standup?
[14:01] <rick_h__> gary_poster: sure thing
[14:01] <gary_poster> ok thanks
[14:02] <hatch> our repo is large
[14:08] <hatch> the qa of huws branch is pretty cool
[14:10] <frankban> wow, new kanban... it has card subtasks, seems interesting
[14:11] <hatch> looks the same to me :(
[14:11] <rick_h__> heh yea. It took me a while to find the external card id this weekend
[14:11] <frankban> guihelp: I need two review for https://codereview.appspot.com/39380043 (python/quickstart). Anyone available? Thanks!
[14:11] <rick_h__> frankban: I've got a call, but can look later in the day
[14:12] <hatch> maybe I've got to log out and log back in
[14:12]  * gary_poster on calls till a lot later
[14:12] <frankban> rick_h__: thanks
[14:16]  * bac hi
[14:16] <bac> frankban: i'll look
[14:17] <frankban> bac: thank you
[14:23]  * frankban bbiab
[14:26] <hatch> wow...so Microsoft is issuing takedown notices for Ubuntu now...
[14:34]  * benji issues a takedown notice to Mondays
[14:35] <rick_h__> hatch: so I tried out the shortcut in that blog post and you can git checkout pr/6
[14:35] <rick_h__> hatch: works nice
[14:35] <hatch> rick_h__ so `git clone <juju-gui-repo>` then `git checkout pr/6` ?
[14:35] <rick_h__> hatch: hmm, actually no. Well it adds a fetch-pr command
[14:36] <hatch> rick_h__ so I made a new folder called qa
[14:36] <hatch> cloned juju-gui into that
[14:37] <hatch> made a branch for his stuff
[14:37] <hatch> then pulled his branch into that
[14:37] <hatch> took a while, but future branches should be faster
[14:39] <rick_h__> ah there we go
[14:40] <rick_h__> hatch: ok, so with that fetch-pr the process would be http://paste.ubuntu.com/6546053/
[14:40] <rick_h__> oh wait, that final checkout should be a merge
[14:40]  * rick_h__ starts over with a fresh repo
[14:40] <hatch> is co 'checkout' ?
[14:40] <hatch> ok that's more steps than I did
[14:40] <hatch> :)
[14:41] <rick_h__> hatch: yes, but fast
[14:42] <hatch> it looks like a good candidate for an alias method
[14:42] <hatch> :)
[14:42] <rick_h__> hatch: yes, although you need names for the branch and the pull request number
[14:43] <hatch> I was sure you could create methods in git
[14:43] <rick_h__> but git qa-pr 6 qa-sticky-headers would work
[14:43] <hatch> yeah
[14:43] <rick_h__> hatch: definitely, it's what this link is doing
[14:43] <rick_h__> the fetch-pr is a new helper as an alias
[14:44] <rick_h__> hah alias = "!sh -c '[ $# = 2 ] && git config --global alias.\"$1\" \"$2\" && exit 0 || echo \"usage: git alias <new alias> <original command>\" >&2 && exit 1' -"
[14:52] <rick_h__> hatch: http://paste.ubuntu.com/6546113/
[14:52] <rick_h__> hatch: changes it to be 
[14:52] <rick_h__> git qa-pr juju 6 qa-stick-headers
[14:53] <rick_h__> juju is the remote of the official juju repository (vs your fork since the pr is there) and 6 is the pr number and finally the name of the qa branch to create
[14:56] <hatch> marcoceppi so does it usually take a couple weeks to get a charm approved for the store? Anything I can do to speed up the process of getting that Ghost charm in there? 
[14:57] <marcoceppi> hatch: do my work for me
[14:57] <hatch> haha well you can just approve it
[14:57] <hatch> it passes proof
[14:57] <marcoceppi> I'm the only reviewing charmer atm
[14:57] <hatch> ohh
[14:58] <marcoceppi> hatch: proof != passing review
[14:58] <marcoceppi> hatch I'll review tonight
[14:58] <hatch> ok cool - I'm more concerned that outsiders are in the same boat
[14:58] <hatch> I'm not blaming you btw
[14:59] <hatch> just that we may need to figure out a more streamlined process 
[15:00] <hatch> marcoceppi I know - make me a reviewer, I'll review it :D
[15:03] <marcoceppi> hatch: feel free to apply :)
[15:03] <hatch> oh man I gotta apply? 
[15:03] <hatch> :P
[15:04] <marcoceppi> yeah, I know right? Such barrier
[15:04] <hatch> ╯□）╯︵-┻━┻
[15:08] <hatch> rick_h__ curious - when I make edits to posts do you get emails of each edit? 
[15:09] <rick_h__> hatch: yea, I've been getting double emails
[15:09] <hatch> sorry :)
[15:09] <hatch> I'll remember that
[15:09] <rick_h__> hatch: all good, "delete thread" :)
[15:09] <hatch> haha
[15:09] <hatch> now that I've done that, back to fighting with d3
[15:10] <rick_h__> hatch: did you try the alias? ^
[15:10] <hatch> negative
[15:10] <hatch> I have it open though
[15:10] <rick_h__> note it for next one?
[15:10] <hatch> I'll set it up for the next time
[15:10] <hatch> yep
[15:10] <rick_h__> paste the two commands into your .gitconfig :)
[15:20] <hatch> this weekend I wrote a js solution to the Secret Santa Dart Dare https://gist.github.com/hatched/7873759 I think it's the most performant way, maybe someone else has a better solution 
[15:23] <bac> review done frankban
[15:24] <hatch> rick_h__ get your light installed this weekend?
[15:24] <rick_h__> hatch: yep
[15:24] <hatch> so you found the right breaker then? :)
[15:24] <rick_h__> kitchen looks nice. Now the only issue is that I've gone with the 53k daylight led bulbs and the other areas are looking odd with their yellow-ish tint
[15:24] <rick_h__> hatch: hah, I flipped a few off. Never can be too safe :)
[15:25] <rick_h__> sorry, 5300 not 53k
[15:25] <hatch> yeah my house is like that too, half the lights are white and the rest are yellow...I'm slowly converting them to LED's but damn they are pricey 
[15:25] <rick_h__> yea, I've gotten 20 of these white leds in the last month. :/ 
[15:26] <hatch> a few years ago I picked up one of these http://www.fluke.com/fluke/caen/digital-multimeters/Fluke-170.htm?PID=56027 
[15:27] <rick_h__> heh, I've got the Fluke 117 
[15:27] <hatch> and one of those circuit breaker tester things
[15:27] <hatch> trying to find a link but I can't :/
[15:27] <rick_h__> ah, cool
[15:28] <hatch> the ones where you attach things to the wires and then the tool thing tells you which breaker it's hooked too
[15:28] <rick_h__> yep
[15:28] <hatch> my house wiring wasn't labeled -at-all-
[15:28] <hatch> there wasn't a SINGLE label on the panel lol
[15:30] <bac> hatch: i had them run all of the phone/data to a central closet so i could hook it all up to a router/panel.  none of it was labeled.  infuriating.
[15:31] <hatch> lol ugh that's the worst! I don't even know of a way to test those....trial and error?
[15:31] <rick_h__> they make tone tools to check
[15:31] <hatch> oh cool
[15:35] <hatch> the more I work on d3, the more I'm convinced it was not designed for our usecase lol
[15:36] <hatch> academically, it's approach to problems is pretty interesting.....
[15:36] <frankban> bac: thanks
[15:50] <Makyo> jujugui call in 10, kanban now.
[15:50] <hatch> Makyo after the call mind pairing on this perf branch? I'm running into some d3 funnyness that I'm at a total loss on what's going on
[15:51] <Makyo> hatch, sure.
[15:51] <hatch> thx
[15:58] <Makyo> jujugui call in 2
[16:00] <bac> coming
[16:19] <bac> gary_poster: if you have a suggested next card speak now.  :)
[16:21] <gary_poster> bac, :-) any non-blocked card is good.  you could take point on jujucharms or you could fix that new charm bug or you could fixthe charmworld bug, or...lotsa things
[16:22] <bac> gary_poster: ok, cool
[16:22] <bac> gary_poster: forgot to mention i'll probably have to go about 4 to retrieve post-op jojo
[16:25] <Makyo> hatch, https://plus.google.com/hangouts/_/7acpibqvsna48s50l5ibn5eci0?hl=en
[16:27] <gary_poster> bac, ok.  hope he is ok
[16:28] <bac> gary_poster: should be.  "just" quilting his ear to get rid of a hematoma.  not like a lung transplant or anything.
[16:28] <gary_poster> ok cool-ish
[16:29] <bac> he probably isn't so cavalier about it, since it is his ear
[16:30] <gary_poster> :-) yeah
[16:36] <hatch> gary_poster Makyo figures he knows what the problem is but isn't sure of a workaround so I'm going to pass it off in hopes that it's a trivial fix
[16:36] <gary_poster> ack thanks hatch & Makyo
[16:36] <Makyo> gary_poster, hatch going to land current SSH keys branch first, + call with rick_h__ when free.
[16:36] <hatch> yeah that
[16:36] <gary_poster> sounds good
[16:39] <hatch> Makyo https://github.com/hatched/juju-gui/tree/inspector-performance thanks
[16:40] <hatch> here is the commit of this branch https://github.com/hatched/juju-gui/commit/8a9b79b36da3a39b7dd6f7dccdc882ad4712416a
[16:41] <hatch> gary_poster any preference for cards for me? Shall I start on the fullscreen removal?
[16:41] <gary_poster> sure hatch sounds good :-)
[16:45] <hatch> rick_h__ there appears to be an issue with our gitignore.... it throws an error when I try and use `git add *` instead of adding the changed files not in the .gitignore it fails with a 'fatal' error
[16:45] <hatch> not sure if you have seen the same
[16:45] <rick_h__> hatch: otp, sec
[16:50] <Makyo> rick_h__, http://pastebin.ubuntu.com/6546619/ for later.
[16:51] <hazmat> why did branch commits make it over on the gh migration? as opposed to mainline..
[17:12] <rick_h__> hazmat: it's what bzr fastimport did. I didn't see a lot of material on exporting from bzr into git and getting to tweak it. 
[17:12] <rick_h__> hazmat: there's a *~ in there already?
[17:12] <rick_h__> sorry, hatch ^
[17:13] <rick_h__> hatch: maybe that's throwing it off? I don't know tbh. I just moved the bzr one over and it 'worked' by trial so left it alone
[17:13] <rick_h__> Makyo: thanks for the paste. 
[17:14] <hatch> rick_h__ yeah ok cool something to take a look at sometime
[17:14] <rick_h__> hatch: k, works here so have fun :)
[17:14] <rick_h__> hatch: why did you want to ignore *?
[17:14] <hatch> I want to add *
[17:15] <hatch> say I have 10 changed files
[17:15] <hatch> I want to add all of them to the commit
[17:15] <rick_h__> hatch: oic, git add -A :)
[17:15] <rick_h__> or --all
[17:15] <hatch> oh crap right
[17:16] <hatch> that was bzr that had `add *`
[17:20] <Makyo> hatch, https://twitter.com/horse_js/status/410094798062628864
[17:20] <hatch> HAHAHAHA
[17:20]  * hatch looks around
[17:20] <hatch> is the horse in here???
[17:21] <Makyo> Hah, well, it's not me!
[17:25] <hatch> wow I really forgot a lot of git stuff in the past year
[17:33] <hatch> jujugui could I get a really quick review of a doc update branch https://github.com/juju/juju-gui/pull/8
[17:34] <bac> hatch: sure
[17:34] <hatch> thanks
[17:37] <bac> hatch: your branch, the words flow together and seem to form something akin to English. but for the life of me i'm not sure what i would do with them.  this coming from a total git-dummy.
[17:38] <bac> so that package, i download it and put it somewhere?
[17:38] <bac> and the aliases, they go somewhere too?
[17:38] <bac> i wonder where
[17:38] <hatch> bac lol, so you're saying you want documentation on how to add aliases? the Git Remote Branch has installation instructions on their repo
[17:39] <bac> oh, ok
[17:39] <hatch> sorry it's not really clear that the code is aliases
[17:39] <hatch> I can clean that up
[17:39] <bac> yeah, maybe just "stuff the following aliases in your ~/.git/aliases file"  (i made that up.  was i close?)
[17:40] <hatch> ~/.gitconfig
[17:40] <hatch> :)
[17:40] <hatch> close
[17:43] <bac> hatch: ok, so i added two comments in-line and wrote a top-level comment that said everything was good.  is that all we're doing for reviews in github?
[17:43] <rick_h__> bac: so once you've reviewed it and you're ok, add a LGTM comment
[17:44] <bac> ok
[17:44] <bac> oops, i guess closing it is bad
[17:44] <hatch> bac https://gist.github.com/hatched/7876600 here are the new changes.....look good?
[17:44] <rick_h__> bac: hah! close all hatch's pull requests
[17:45] <rick_h__> bac: yea, he can re-open it I think
[17:45] <bac> lovely
[17:45] <hatch> lol
[17:45] <bac> hatch: yes those changes are fine
[17:45] <hatch> we'll get this figured eventually :D
[17:46] <hatch> I for one think that this new process is pretty darn cool
[17:46] <hatch> just need to figure out all the proper commands :D
[17:48] <hatch> I'm going to need a shortcut for 'refresh folders' in sublime if I keep switching between branches heh
[17:48] <hatch> Makyo if you have any questions about my changes on my branch just lemme know 
[17:48] <Makyo> hatch, will do; trying to find a better test for SSH keys now.
[17:48] <hatch> Dolla Dolla MERGE YO!
[17:49] <Makyo> jujugui researching, but in the meantime, if anyone has suggestions for checking for valid ssh keys that does not rely on a) find, or b) ssh-agent, I'd be interested to hear :)
[17:50] <hatch> rick_h__ If I click this HUGE green 'Merge pull request' button, does that bypass our CI?
[17:50] <Makyo> jujugui (or uses ssh-agent atomically)
[17:51]  * gary_poster does not; sorry
[17:52] <frankban> Makyo: what's wrong with just searching for an id_rsa.pub?
[17:52] <hatch> probably slow
[17:52] <hatch> TWAG though
[17:52] <bac> i wonder if landscape would accept our browser sniffer/intercept code?  they only support firefox but happily let you have a diminished experience if you don't know that.
[17:54] <Makyo> frankban, that leaves out id_dsa.pub and id_ecdsa.pub, and identity files can be specified in other locations using ssh config.  I'm fine with that as a last resort, but would like something that actually checks for ssh identity availability.
[17:55] <frankban> Makyo: ack
[17:56] <Makyo> frankban, want to just go with that for now and land this, then see if we need to investigate further?
[17:57] <Makyo> Up to you ¯＼(º_o)/¯
[17:57] <rick_h__> hatch: your branch failed to land. You have to delete the comment about it being 'merge request accepted' to get another run
[17:59] <hatch> rick_h__ hmm how did you know that it failed?
[18:00] <rick_h__> hatch: was looking
[18:00] <rick_h__> hatch: eventually it should add a new comment on failure, but it's not hooked up yet
[18:00] <frankban> Makyo: +1
[18:00] <Makyo> frankban, ack, on it.
[18:00] <frankban> Makyo: thanks
[18:10] <hatch> rick_h__ ohh ok so the issue here is that it commented after I typed $$merge$$ ?
[18:11] <rick_h__> hatch: right, the system adds a comment saying the merge request has been accepted, so that it won't run it more than 1 time in case it takes a while to get to your merge
[18:12] <rick_h__> hatch: say 3 branches all get the request to merge at once, the cron job runs every 2min, so it has to be able to know "these 3 are already queued, don't add them again"
[18:13] <rick_h__> hatch: so remove that comment and the system will re-queue on the next 2min cron run
[18:14] <hatch> ok so saying $$merge$$ again won't help?
[18:14] <Makyo> frankban, worth another quick look just for completeness' sake? https://codereview.appspot.com/36080044/diff/20001/quickstart/app.py
[18:15] <rick_h__> hatch: no
[18:15] <frankban> Makyo: on it
[18:15] <rick_h__> hatch: it's looping and looking for the command once. 
[18:15] <hatch> ohh ok
[18:15] <rick_h__> the one cancels the other out
[18:20] <rick_h__> hatch: cool worked
[18:21] <hatch> yup - so that was just an unfortunate race condition there then?
[18:21] <frankban> Makyo: looks good, even if I hoped we were able to use python to check for ssh keys (e.g. os.walk, glob.glob etc) <shrug>. Perhaps you can follow up in another card?
[18:21] <rick_h__> hatch: right, and I'm proposing a branch right now to get around that. Will be looking for review shortly
[18:21] <hatch> cool - and about the butt
[18:21] <hatch> on
[18:21] <hatch> if I press the merge button will it bypass the CI?
[18:22] <rick_h__> hatch: yes, and I get angry with you
[18:22] <Makyo> frankban, understood; it just still seems fragile, as we're not checking on actual identities , just whether or not files following a certain name exist.  If someone snags a public key to add to authorized_keys and forgets to clean up after themselves, this will false-positive.
[18:23] <hatch> rick_h__ haha, can we disable that somehow?
[18:23] <rick_h__> hatch: not that I know of atm
[18:23] <Makyo> That's why  I went with ssh-add at first.
[18:23] <Makyo> I thought `ssh-agent ssh-add -l` might work, but that just always fails :P
[18:26] <frankban> Makyo: ok right, you intend this as a temporary solution. ok then, added a new LGTM. please create another card to investigate further
[18:26] <Makyo> frankban, Yep, thank you.
[18:30] <rick_h__> hatch: care to peek at https://github.com/juju/juju-gui/pull/7 please?
[18:30] <hatch> sure
[18:32] <hatch> I love how github keeps the diffs up to date
[18:36] <hatch> rick_h__ lgtm'd with some notes
[18:37] <rick_h__> hatch: rgr, replied to one
[18:37] <rick_h__> hatch: well, replied to both in the end
[18:37] <hatch> cool - yeah I figured the caching would be a followup
[18:38] <rick_h__> well, post-ci stuff :)
[18:38] <hatch> right
[18:38] <hatch> yeah
[18:38] <hatch> so the 'failure' stuff is going to be done soonish?
[18:39] <hatch> the 'bug' which I ran into previously? Or do we need to keep our eye on the merges for now?
[18:39] <rick_h__> hatch: yea, I've got to find a post-build plugin and figure out how to wire it up. jenking-github-lander supports posting the failure notices already
[18:39] <rick_h__> hatch: keep an eye on merges for now
[18:39] <hatch> cool gotcha
[18:39] <hatch> oh cool github gives the option to delete merged branches
[18:40] <rick_h__> yea, button to help keep things clenaed
[18:41] <hatch> rick_h__ possible idea for disabling the 'merge' green button - allow only the jujugui user to merge stuff in then the button should be hidden?
[18:41] <rick_h__> hatch: yea, but we're all in the org
[18:41] <rick_h__> so it gets into tricky perms of "you can do stuff, but not this one thing" and haven't looked too closely at it
[18:41] <rick_h__> just trusting out devs
[18:41] <hatch> ahh ok 
[18:42] <rick_h__> e.g. the idea to do a release is you checkout just the juju project, merge develop into master, push up the updated master as a release
[18:43] <rick_h__> so if you can't do the merge button, you can't do a release
[18:43] <hatch> ok wtf google, I said "about" into hangouts, and it typed "a boot" lol!!!!
[18:43] <hatch> damnit I'm not THAT Canadian
[18:43] <hatch> lol
[18:44] <bac> rick_h__: trusting devs may be dangerous at least until we're all up to speed
[18:44] <bac> big green buttons are so tempting
[18:45] <hatch> bac the good thing about git is you can always roll back from anyones repo
[18:45] <rick_h__> bac: understand. Like I said though, there's not a ton I can do about it for now
[18:45] <hatch> there is nothing 'special' about the github repo vs anyones local one
[18:45] <hatch> well that's a lie
[18:45] <hatch> but on face value :)
[18:45] <bac> i'm just apologizing in advance...  :)
[18:45] <hatch> haha
[18:45] <hatch> bac feel free to ask
[18:46] <rick_h__> bac: let me konw if you'd like a walk through or anything. I'm not aware of everyone's git levels so I left 'training' out to some notes/docs but happy to help walk anyone through things
[18:46] <hatch> just don't push upstream with -f :D
[18:46] <bac> rick_h__: did you write a getting started guide?  if so i missed it but would like to read if available
[18:47] <hatch> rick_h__ it might be best to also add `git remote add upstream ...` and `git fetch upstream` for updating the local fork
[18:47] <rick_h__> bac: in the email linked the repo with a README
[18:47] <rick_h__> hatch: it's in the notes
[18:47] <hatch> ohh ok 
[18:47] <hatch> I mised that line I guess heh
[18:47] <rick_h__> hatch: the notes have you add a remote juju, and git pull juju origin when starting a new branch
[18:47] <rick_h__> bac: sec, will PM you think linke
[18:47] <rick_h__> link
[18:48] <hatch> ugh my email is a mess
[18:48] <hatch> I need to set up filters
[18:48] <hatch> I am the antitheses of inbox-0 
[18:48] <hatch> haha
[18:52] <hatch> so for our christmas party do we just sit in-front of our computers in a hangout drinking rum and eggnog? 
[18:52] <hatch> playing virtual beer pong
[18:52] <gary_poster> antithesis: inbox infinity?
[18:52] <Makyo> CO-Canonicalites have a party next Thursday, so there.
[18:52] <bac> hatch: i can see the bacardi distillery from my patio.  :)
[18:52] <hatch> gary_poster I'm working towards it...haha
[18:52] <Makyo> !
[18:53] <hatch> Makyo lol lucky
[18:53] <gary_poster> :-)
[18:53] <rick_h__> Makyo: MI-Canonicalites always party! right jcastro?
[18:53] <hatch> bac haha nice
[18:53] <Makyo> HP used to have their open source lab here, so there's a few of us (and a few RH folk, too)
[18:54] <hatch> do you shun them when you get together?
[18:54] <hatch> they need to execute a proper apt-get command to get in the door
[18:54] <hatch> lol
[18:54] <hatch> its the shibboleth 
[18:54] <Makyo> Pff.
[18:54] <Makyo> We just don't invite them :)
[18:54] <hatch> hahaha
[18:54] <Makyo> It's a company holiday party, after all.
[18:55]  * bac recalls the one Canonical-NC party that was a huge success
[18:55] <hatch> I'm going to host the biggest Canonical-SK party EVER this year
[18:55] <bac> working remotely makes company parties actually fun.
[18:55] <bac> the brick-and-mortar company parties just seemed like a continuation of the work day
[18:56] <hatch> http://deadlygeek.myshopify.com/
[18:56] <hatch> bac - sounds like a lame party to me
[18:56] <Makyo> :/
[18:57] <bac> hatch: the existence of that belt buckle is why i am opposed to any gift giving.  :)
[18:57] <hatch> lol damnit I'm buying myself one!
[19:04] <hatch> rick_h__ do you have time for a discussion on removing fullscreen and followup direction?
[19:06] <rick_h__> hatch: yea, second
[19:07] <hatch> https://plus.google.com/hangouts/_/7ecpj8dfhvb68a9eaplojbk1bg?hl=en
[19:07] <hatch> crap it crashed
[19:08] <hatch> I'll try inviting you directly
[19:39] <jcastro> I can't find my own bundles in the store
[19:39] <jcastro> I am trying to find the cloudfoundry bundle
[19:41] <rick_h__> https://jujucharms.com/fullscreen/search/?text=jorge don't see cloudfoundry atm though
[19:41] <rick_h__> jcastro: did you update it recently and maybe it failed proof?
[19:41] <jcastro> http://manage.jujucharms.com/bundle/~jorge/cloudfoundry/cloudfoundry
[19:42] <jcastro> it's just not in jujucharms.com the non-manage part afaict
[19:42] <rick_h__> looking
[19:45] <rick_h__> jcastro: hmm, it's showing on staging so something is up between staging/production http://staging.jujucharms.com/search?search_text=cloudfoundry&op=
[19:45] <rick_h__> jcastro: will have to look into it
[19:45] <jcastro> oh cool, so I found a real bug?
[19:45] <rick_h__> jcastro: or a mis-configure or something. 
[19:55] <rick_h__> jcastro: updating my local env and doing a fresh pull of data. I'll have to chase it down, will get back to you tomorrow
[19:55] <jcastro> no worries
[19:55] <jcastro> I wonder how long it's been broken
[19:55] <jcastro> I don't suppose we can add a "bundles" category?
[19:55] <rick_h__> yea, not sure. I only seem to see it missing. Others look fine. So something is up with that one bundle
[19:56] <rick_h__> jcastro: yea, there's a todo to figure out something, but not sure where it's at. 
[20:28]  * bac -> vet
[20:44] <hatch> bug #1217383
[20:44] <_mup_> Bug #1217383: inspector should be the default <juju-gui:Triaged> <https://launchpad.net/bugs/1217383>
[20:44] <hatch> thanks mup
[20:45] <hatch> rick_h__ ""This is horrible and we know it"" lol
[20:47] <rick_h__> :)
[21:12] <hatch> Makyo hey, curious if you're making any headway on that d3 stuff? 
[21:13]  * hatch is curious what the solution (if any) there is :)
[21:13] <Makyo> hatch, git problems, just getting started, have an idea.
[21:13] <hatch> ahh ok cool np
[21:13] <hatch> git is a problem until you understand how it works hah
[21:13]  * hatch does not understand it
[21:13] <hatch> :P
[21:18] <Makyo> I just had some weirdness left over from setting up 2fa.  Helped to switch to ssh urls.
[21:20] <hatch> jujugui looking for a smallish review/qa https://github.com/juju/juju-gui/pull/9
[21:21] <hatch> I still can't decide what kind of laptop to get so my whole setup is a mess - I feel your pain haha
[21:21] <hatch> doh
[21:22] <hatch> jujugui remember to make lint && make test-debug before issuing a PR :)
[21:22] <Makyo> How about make check?
[21:22] <hatch> yeah that's fine too I SUPPOSE :P
[21:23] <Makyo> It's almost like it's there for a reason... :)
[21:23] <hatch> I know right?
[21:23] <hatch> crazyyyyy
[21:24] <hatch> woah, apple.com has a huge picture of Nelson Mandela
[21:27] <hatch> unfortunately the apple.ca financing deals aren't nearly as good as the US ones :(
[21:29] <hatch> US financing is always so much better than in Canada :(
[21:35] <gary_poster> hatch, you still want review?
[21:35] <hatch> yup I do
[21:35] <gary_poster> k on it
[21:35] <hatch> I'm trying to remove this in as many atomic pieces as possible
[21:35] <hatch> it's very.....connected heh
[21:36] <gary_poster> :-) I believe it
[21:37] <gary_poster> ok, this is really I time for me to set up a decent git qa pattern...
[21:37] <hatch> gary_poster I created a new clone of the repo then run the two aliases that I added to the HACKING docs
[21:37] <hatch> the aliases were thanks to rick_h__ 
[21:37] <gary_poster> yeah was just stealing those myself :-)
[21:39] <hatch> man I REALLY want to buy a MBP with 18mo 0% interest financing
[21:40] <hatch> anyone want to buy it for me and trust that I'll pay you back? ;)
[21:43] <gary_poster> ai-yai-yai, I need a cheat sheet
[21:43] <hatch> haha yeah
[22:02] <huwshimi> Morning
[22:06] <gary_poster> hey huwshimi 
[22:07] <huwshimi> gary_poster: Hey
[22:11] <hatch> hey huwshimi 
[22:11]  * Makyo dogwalks before it gets too cold.
[22:17] <hatch> huwshimi if you need some help moving forward with your sticky branch lemme know
[22:17] <huwshimi> hatch: heh, yeah, I'm not quite sure what to do with that branch
[22:17] <hatch> you just want it to die don't you?
[22:18] <gary_poster> hatch, LGTM etc
[22:18] <hatch> thanks
[22:18] <huwshimi> hatch: Yes, please
[22:19] <hatch> lol
[22:19] <huwshimi> hatch: it or me
[22:19] <huwshimi> either would be acceptable at this point
[22:19] <hatch> hey at least we are using your code haha
[22:19] <gary_poster> huwshimi, :-) and :-P
[22:20] <huwshimi> hatch: And your browser test is not so promising either
[22:20] <gary_poster> hatch, huwshimi is it worth strategizing together about next steps?
[22:20] <gary_poster> huwshimi, I mean, deep unhappiness is always valuable, but...
[22:20] <hatch> lol!
[22:20] <huwshimi> haha
[22:21] <hatch> I'm sure any of us JS peeps could take over to resolve the issues
[22:21] <hatch> I'm a little deep in fullscreen removal land right now however
[22:21] <huwshimi> gary_poster: We can, I'm in a land of uncertainty right now so it might be good to figure out what to do with it
[22:21] <huwshimi> hatch: Ooh, nice!
[22:22] <gary_poster> ok.  hatch, you available for a hangout as well?  
[22:22] <hatch> sure lemme turn on my anti-bark machine
[22:23] <gary_poster> huwshimi, hatch https://plus.google.com/hangouts/_/72cpi8bsiur2s17hpkf800rcfg?hl=en
[22:34] <rick_h__> gary_poster: let me konw if there's any specific set of cribs for workflows you'd like written up
[22:35] <rick_h__> hatch: woot for landing on first try
[22:35] <gary_poster> thanks rick_h__ .  want more of proposed process from https://gist.github.com/mitechie/c0183e567d81aa92b5e3in hacking doc.  we have some of that
[22:35] <gary_poster> but not all
[22:35] <gary_poster> and I want all :-P
[22:36] <rick_h__> gary_poster: want more as in more types of that? Or more details written in to flesh that out?
[22:36] <gary_poster> rick_h__, I want all of that in hacking doc
[22:37] <gary_poster> I don't want to have to keep link to gist :-)
[22:37] <gary_poster> and then maybe could elaborate on it
[22:37] <gary_poster> but even as is would make me happy
[22:37] <rick_h__> gary_poster: ah, gotcha. Ok yea I figured it would pollute the hacking doc a bit, but happy to move it over
[22:37] <gary_poster> +1
[22:37] <rick_h__> gary_poster: ok cool, works for me
[22:37] <gary_poster> rick_h__, or process
[22:37] <gary_poster> divided up by tasks
[22:38] <gary_poster> as you think
[22:38] <rick_h__> gary_poster: yea, as hatch hit the qa stuff today I was thinking of adding a qa process
[22:38] <gary_poster> +1
[22:38] <rick_h__> but beyond qa and submitting a branch wasn't sure what other processes to make sure to cover 
[22:38] <rick_h__> release, but that's in the works and in the process doc
[22:43] <huwshimi> gary_poster, hatch: Thanks!
[22:43] <gary_poster> thank you huwshimi !  will be great to have
[22:44] <hatch> huwshimi http://www.git-tower.com/blog/git-cheat-sheet/ :)
[22:46] <hatch> rick_h__ yup the process worked well
[22:48] <hatch> it's darn fast too
[22:48] <hatch> the QA must not be running any python tests :P
[22:57] <hatch> WOAH
[22:57] <hatch> new MDN
[23:01] <rick_h__> not yet, the hope is that we'll get that in soon from benji's branch/work
[23:02] <hatch> and then sauce labs
[23:02] <hatch> and there goes our fast CI
[23:02] <hatch> lol
[23:12] <rick_h__> yea, it's doomed to go, but at least we could bring it up on a faster machine if that helps :)
[23:17] <hatch> haha truth
[23:17] <hatch> it would be nice if we could spin up multiple sauce labs instances and run them in parallel