=== elarson_ is now known as elarson [03:48] * arosales finally getting to some review time. [03:54] * marcoceppi_ as well arosales [03:55] * arosales waves to marcoceppi_ === mup_ is now known as mup === uru_ is now known as urulama === SP33D_ is now known as SP33D === Tribaal_ is now known as Tribaal === jcsackett_ is now known as jcsackett === ming is now known as Guest50175 === jseutter_ is now known as jseutter === psivaa is now known as psivaa-off === ev_ is now known as ev === yo61_ is now known as yo61 === yo61_ is now known as robinbowes === beisner- is now known as beisner === FourDollars_ is now known as FourDollars === uru_ is now known as urulama === ev_ is now known as ev === urulama_ is now known as urulama === BradCrittenden is now known as bac === beuno_ is now known as beuno === mthaddon` is now known as mthaddon === carlas is now known as carlasouza [14:43] mbruzek: are you working on a community doc for reviews? [14:44] arosales, Yes I am in a hangout with JoshStrobl [14:44] perhaps with JoshStrobl ? [14:44] ah cool. [14:44] o/ [14:44] mbruzek: JoshStrobl one idea I had was to make the charm authoring docs a little more robust on commong things ~charmers catch in a review [14:44] so I made https://docs.google.com/a/canonical.com/document/d/1El7011q-DlaouSlkMLCiMOtWOjWu0ZX9bMva6AuVfq8/edit#heading=h.fql3tpkqjkg [14:45] so in addition to what can be caught in a review one idea I wanted to pitch was being preemtive on designing out a charm from learning in charm reviews [14:45] JoshStrobl: o/ Hello [14:46] JoshStrobl: mbruzek: just some food for thought. To JoshStrobl point I have been thinking about how to make the review time shorter in addition to getting more eyes on reviews [14:47] arosales, This document looks different than what we were working on. [14:47] https://docs.google.com/a/canonical.com/document/d/1QpKWUE4bVtwBg3bSxy0mdz7q2wMbXDBqjIfKs_TR8pY/edit [14:47] you should be able to edit that doc [14:47] mbruzek: understood [14:47] arosales, if you want to join the hangout -> https://plus.google.com/hangouts/_/g7rb4acvbvhcmeb6jdix7djwiea [14:47] We were taking the approach of the community charmer, what specific steps do they need to take to review a charm. [14:47] no obligation ;) [14:48] mbruzek: ya let me refill on coffee and join for a a few === hatch__ is now known as hatch === tris- is now known as tris === timfreun1 is now known as timfreund === ashipika1 is now known as ashipika === CyberJacob|Away is now known as CyberJacob [17:23] arosales, first draft up on the Charm Review Process doc: https://github.com/JoshStrobl/docs/blob/master/src/en/charm-review-process.md [17:25] JoshStrobl: good stuff. Thanks for working on it with mbruzek [17:25] JoshStrobl: I'll be taking a look this afternoon === mup_ is now known as mup [18:03] lazyPower_: greetings from the subway charm [18:15] hi, is there a way to re-run a relation-joined hook? i had to resolve some hooks so queued upgrade-charm could happen, but now i missed out on those relation-joined hooks [18:16] i though juju run was originally meant to re-run hooks, can it do that? [18:45] Hi mattrae_ You can run juju debug-hooks charm-name/0 [18:49] mattrae_, you can run juju resolved --retry name/0 [18:49] That will put you in a charm context where you can rerun the hook if you like. [18:56] mattrae_: not really, no, if you've already passed the hook context. I opened a bug about this === cmagina_ is now known as cmagina === scuttlemonkey is now known as scuttle|afk === urulama_ is now known as urulama-afk === cmagina_ is now known as cmagina [21:20] hey aisrael, mind a quick PM? :) [21:22] Sure thing === mup_ is now known as mup [22:48] anyone around? I'm having some troubles bootstrapping === mhall119_ is now known as mhall119 === lifeless1 is now known as lifeless === CyberJacob is now known as CyberJacob|Away === perrito6` is now known as perrito666