=== kadams54 is now known as kadams54-away === kadams54-away is now known as kadams54 === kadams54 is now known as kadams54-away === kadams54-away is now known as kadams54 === kadams54 is now known as kadams54-away === kadams54 is now known as kadams54-away === kadams54-away is now known as kadams54 === kadams54 is now known as kadams54-away === kadams54 is now known as kadams54-away === kadams54 is now known as kadams54-away === kadams54-away is now known as kadams54 [15:14] hey rick_h_ [15:14] the bug link on new jujucharms.com points to juju-website [15:14] is that where you want all the bugs? === kadams54 is now known as kadams54-away [15:33] jcastro: yep [15:56] uiteam kanban please call in 4 === kadams54-away is now known as kadams54 [15:57] jcastro: no, we've got that updated in trunk but not released yet [15:57] jcastro: https://github.com/CanonicalLtd/jujucharms.com/issues [15:57] oh, I filed in the wrong place then. :-/ [15:58] jcastro: sorry for the confusion. [15:58] jcastro: what was the bug you filed? I'll copy it over and get it set up [15:58] are you guys going to resolve the old bugs before the "move" to the link? [15:58] some still appear valid [15:59] jcastro: where are you looking? [15:59] https://bugs.launchpad.net/juju-website/+bug/1398870 [15:59] Bug #1398870: Share button should use microdata [15:59] jcastro: I'm not aware of what 'juju-website' is [15:59] the footer on a charm's page links there [16:00] http://jujucharms.com/trusty/owncloud for example [16:00] ok yea, I'll go through these today [16:00] thanks for the heads up [16:00] at the very bottom === tvan-afk is now known as tvansteenburgh [16:20] rick_h_: So it looks like Huw's branch has been fixed but the new update that he pushed never triggered a ci build [16:20] I'll trigger one manually then it should be good to land if it passes [16:21] hatch: k thx [16:52] jcastro: what charm did you try to share? We have G+ microdata currently maybe we missed something [16:53] oh hmm, will look at updating it. Looks like it treats things different if I do a post and add the link vs hitting the G+ link and such [17:05] rick_h_, yeah [17:06] I was thinking if we seeded it with the charm logo [17:06] that would look slick [17:06] so like, it's all about sharing the service [17:32] jcastro: right, I thought we had that, will get it fixed up [17:33] hatch: http://www.sunnyskyz.com/uploads/2014/11/7adso-states10.jpg [17:33] FREE HEALTHCARE + BEARS [17:34] lol - no it's not free [17:34] we pay for it in our income taxes :) [17:34] From: http://www.sunnyskyz.com/blog/563/People-In-London-Tried-To-Label-The-50-US-States-On-A-Map-These-Are-The-Hilarious-Results [17:35] So: it's as free as the UK health care system [17:37] :) [17:39] however there is a very good consequence of the 'national health care' is that the hospitals and such can buy items in bulk meaning better prices [17:39] whereas in the US each place is essentially on it's own for negotiations [17:39] saw a pretty good documentary on that [17:39] of course it was on....cable....so I can't link it or anything lol [17:41] headline: Saskatoon's St. Paul's Hospital has highest rate of in-facility deaths [17:41] quote: Morrison said patients coming to St. Paul's shouldn't be concerned. [17:41] umm.... [17:41] http://www.mysask.com/portal/site/main/template.MAXIMIZE/?javax.portlet.tpst=59fea5a22cbb130bab9e3c1070315ae8_ws_MX&javax.portlet.prp_59fea5a22cbb130bab9e3c1070315ae8_viewID=story&javax.portlet.prp_59fea5a22cbb130bab9e3c1070315ae8_topic_display_name=Health%20News&javax.portlet.prp_59fea5a22cbb130bab9e3c1070315ae8_topic_name=Health&javax.portlet.prp_59fea5a22cbb130bab9e3c1070315ae8_news_item_id_key=30954886&javax.portlet.begCacheTok=com [17:41] .vignette.cachetoken&javax.portlet.endCacheTok=com.vignette.cachetoken [17:41] yeah....look at THAT url [17:41] lol [17:56] It's bad when the url exceeds the maxlength of an IRC message. [18:05] lol [18:13] hatch: any chance you can drive-by https://bugs.launchpad.net/bugs/1398891 ? seems like a small target mismatch [18:13] Bug #1398891: The change version close button closes the inspector [18:14] hatch: if not adding a card/etc but curious if it's a one-liner [18:14] looking [18:15] [18:15] heh [18:15] it's probably going to be more than a one liner because it's using the sprite class as the trigger [18:15] it'll be a small cart [18:15] card [18:16] but need test and all that [18:16] so... :) [18:16] hatch: ok adding a acrd [18:19] hatch: what's the diff in your current card and the one in the ready to code around using serach with the bug attached? [18:20] umm [18:20] I didn't see that one when I made my current one [18:20] :) [18:21] ok === kadams54 is now known as kadams54-away === kadams54-away is now known as kadams54 === kadams54 is now known as kadams54-away [22:00] Morning [22:06] morning huwshimi [22:06] your branch was landed [22:06] hatch: Hey, thanks for that [22:07] no problemo [22:13] hatch: Do you happen to know how env/go.js actually interacts with juju? [22:13] I do [22:14] what's your question [22:14] or is that the question? [22:14] :) [22:15] hatch: No I just wanted to know if anyone ACTUALLY UNDERSTOOD IT! [22:16] no I don't understand it, but I know how it works [22:16] lol [22:16] huwshimi: it's weird because we need a way to switch between backends [22:16] sandbox, juju-core, (pyjuju) [22:17] but also the way it was set up initially makes it very hard to follow heh [22:17] hatch: So I want to have a feature that changes depending on juju version. So I need to add what amounts to 'juju --version' on the console [22:18] hmm [22:19] huwshimi: I'd probably do this in the charm and then have it update the config files [22:19] unless you think the juju version will change out from under the gui? [22:19] I suppose that's possible... [22:21] I have no idea [22:21] ok lets chat about it a bit more [22:22] hatch: There's a card under Project 1 titled "lock down username as 'admin' if juju < 1.21" [22:24] thx [22:25] huwshimi: I talked with Makyo about this today [22:25] hatch, huwshimi version is returned in env info, but we need that beforehand. rick_h_ and I discussed having the charm put it in config [22:25] ^^ [22:25] huwshimi: we're not sure if juju exposes it [22:26] heh yeah I was just saying that in the other chan :) [22:26] Sorry, I couldn't figure it out there, seemed like only half of a conversation :) [22:27] Makyo: It was only half a conversion :) [22:27] :) [22:27] http://bazaar.launchpad.net/~juju-gui-charmers/charms/trusty/juju-gui/trunk/view/head:/hooks/utils.py#L347 [22:27] there we go [22:27] knew it was there somewhere [22:27] The Makyos are easily confused. [22:28] Yeah, it'd just go in there. [22:29] might want to do the js side first, see how you want it to work out then update the charm [22:29] forget that...just add the version to the config and call it a day :) [22:29] hatch, huwshimi I've got a test branch with some of those changes in it already Should be simple. [22:30] oh cool [22:31] huwshimi: Makyo and by all means please feel free to update the cards to do based on new info and such [22:31] huwshimi: Makyo those were just my initial stabs/guesses looking at the task to be done and how it looked at first [22:32] Makyo: Do you want me to leave that one with you then? Sounds like you're on it... [22:33] rick_h_: Are we doing all this under a feature flag? [22:34] huwshimi, rick_h_ I don't know that we need to, since the feature should be complete within a release cycle, right? [22:34] huwshimi: if needed. If each branch keeps the old system working then I'd not worry abou tit? [22:34] Makyo: well, I was thinking most of this should still enable logging in right? [22:34] Makyo: if not, then yes we should FF just in case we need a release before it's done [22:34] Sure, that sounds fine. [22:35] huwshimi, I'll pull what I have together into a branch worth proposing and it can at least be an incremental step. [22:35] Makyo: OK, sounds goo [22:35] *good [23:15] rick_h_: so I don't think I can actually get all of these bundles to be converted back to their old versions [23:15] old id's [23:16] basket: mongodb [23:16] version: 5 [23:16] bundle: cluster [23:16] cs:~jorge/bundle/mongodb-5 [23:16] lp:~jorge/charms/bundles/mongodb/bundle [23:18] I suppose I could parse the bundle.yaml.orig but that might be overkill for a temporary fix :) [23:21] unless of course it's not going to be very temporary [23:22] :) === kadams54-away is now known as kadams54 === kadams54 is now known as kadams54-away === kadams54-away is now known as kadams54