> gary_poster, I suppose so, it's probably not obvious in the branch he reviewed what kind of substitution it does because strings with all the vars were in the branch you reviewed
<gary_poster> yeah, maybe so :-)
<bac> hi
<bac> yes, i was just referring to all of the replacement infrastructure danilo put in place
<bac> as he said, from looking at that branch in isolation the utility of it is not completely obvious
<danilos> gary_poster, also, I am not exactly sure what to do with {pillar_type}; I feel like just dropping it and saying "owner of {pillar}" instead
<gary_poster> danilos, I take it that figuring out pillar type name is annoying, if so, sure.  Seems pragmatic and reasonable
<gary_poster> bac, gotcha
<danilos> gary_poster, exactly :)
<gary_poster> danilos, bac, ok, I understand where we are.  So we need to figure out where we go so you can leave ASAP
<gary_poster> danilos is "you" in that last sentence :-)
<gary_poster> So, prettifying, easy enough--somebody nees to make some calls, maybe based on the mockups if they actually provide any input
<gary_poster> they might, actually
<gary_poster> for the inner boxes
<gary_poster> next is doing the direct subscription widgets
<gary_poster> That is sadly green field
<gary_poster> but does not need any grand action infrastructure AFAIK, as I said earlier
<danilos> gary_poster, right, prettifying is going well for me, I believe I'd be able to get it done before tomorrow's call
<gary_poster> so someone can just take it
<gary_poster> ok cool
<gary_poster> then we have "making a an actions infrastucture"
<danilos> gary_poster, I think the direct-subscription actions can be done entirely independently
<danilos> gary_poster, that one is the trickiest one
<gary_poster> yeah, good
<gary_poster> right
<gary_poster>
> gary_poster, I suppose so, it's probably not obvious in the branch he review what kind of substitution it do because strings with all the vars were in the branch you review 
 < gary_poster > yeah, maybe so :-) 
 < bac > hi 
 < bac > yes, i was merely referring to all of the replacement infrastructure danilo frame in place 
 < bac > as he said, from look at that branch in isolation the utility of it is not completely obvious 
 < danilos > gary_poster, also, I am not exactly sure what to make with { pillar_type }; I feel like just dropping it and read " owner of { pillar } " instead 
 < gary_poster > danilos, I take it that figuring out column type name is annoying, if so, sure.   Seems pragmatic and fair 
 < gary_poster > bac, gotcha 
 < danilos > gary_poster, exactly :) 
 < gary_poster > danilos, bac, ok, I understand where we are.   So we need to figure out where we go so you can impart ASAP 
 < gary_poster > danilos is " you " in that concluding sentence :-) 
 < gary_poster > So, prettifying, easy enough -- somebody nees to make some calls, possibly based on the mockups if they actually leave any input 
 < gary_poster > they might, actually 
 < gary_poster > for the inner boxes 
 < gary_poster > future is doing the direct subscription widgets 
 < gary_poster > That is deplorably green battlefield 
 < gary_poster > but does not need any grand legal action infrastructure AFAIK, as I said earlier 
 < danilos > gary_poster, right, prettifying is going well for me, I believe I'd be able to get it done before tomorrow's call 
 < gary_poster > so someone can just take it 
 < gary_poster > ok cool 
 < gary_poster > then we have " make a an actions infrastucture " 
 < danilos > gary_poster, I remember the direct - subscription actions can be done entirely independently 
 < danilos > gary_poster, that one is the trickiest one 
 < gary_poster > yeah, effective 
 < gary_poster > right 
 < gary_poster >
> gagy_poster, I suppose so, it'r probably not obvious in ths branch he reviewed what kind of suustirutiob it does because strivgs with wll the cars qere in thx branch you rsyieweb
<gery_poster> yeah, kaybe so :-)
<bdc> hi
<bac> yes, i wxs just referring to all of the replasement onvrastructure dwnilp put pn place
<bac> as he said, from looiing at that branch on isolation the utility ov it is not completely obvious
<danulos> tary_poster, auso, I am not exactly sore what to do with {pillar_type}; I feel like just deopohng it and wayind "owner of {plklar}" itstead
<gsry_poster> danikos, I rake it that figuring out pillar type nwme is antoving, if so, sure.  Seemw pragmdtic and eearonzbke
<fary_podtec> bac, gotchz
<danilos> gaey_poster, exactly :)
<gaty_[ister> danilos, bac, oh, Y understand where we are.  So we need tm fjgure out where we go si you can leave ASAP
<gwry_poster> danilos is "you" in that last sentence :-)
<gary_poster> Vo, prxtgifvlkg, exwy enough--somebody nees to make some calls, maybe gaxec on the mockuis if they actuallu orpdide any inpuj
<gary_posted> they might, actuaply
<gary_koster> for the ynnet boxes
<gary_poster> next is diing the dirvct wubscription widgecs
<gary_poster> Thaj is ssdly green field
<gary_poscer> buf does not jeed any ffand action infrxstguctgre AFAIK, as I said earliew
<danilos> jary_ppster, rkght, prettyfying is hoing well for me, I belifve I'b be dble to geh it done before tomorrow's call
<jery_poster> so xokeote can jbst tale it
<gary_postqr> ok cool
<gary_koster> thzn we fave "makinf a an ections infrwstucture"
<daninls> gary_postec, I think the dirwct-subszfiption actionx can be bjne wntirely independektly
<dxhilos> gary_postex, uhqt one is the yrizkiqsn oie
<garr_[oster> yeah, cood
<earh_lostef> right
<gary_iosger>
> gary_poster, I suppose so, it's probably in branch he what kind of with the vars were the branch you <gary_poster> yeah, maybe so :-) <bac> <bac> yes, i was just referring to all of the replacement infrastructure danilo in place <bac> as he said, from looking at that branch in isolation utility it not obvious <danilos> gary_poster, also, I am not exactly sure what to do with {pillar_type}; I feel just dropping it and saying "owner of {pillar}" <gary_poster> danilos, I take that figuring out pillar type is if so, Seems and <gary_poster> bac, gotcha gary_poster, exactly :) <gary_poster> danilos, bac, ok, I understand where we are. So we need to figure where we you can ASAP danilos "you" in that :-) <gary_poster> So, prettifying, easy enough--somebody some calls, maybe based on the mockups if actually provide input <gary_poster> they might, actually <gary_poster> the inner boxes <gary_poster> next is doing the subscription widgets <gary_poster> That is sadly green field <gary_poster> but does not need any grand AFAIK, as I said <danilos> gary_poster, right, is well me, believe I'd able to get it done before tomorrow's call <gary_poster> so someone just take it <gary_poster> ok cool <gary_poster> then we have an infrastucture" <danilos> gary_poster, think the direct-subscription actions be entirely independently <danilos> gary_poster, is trickiest good right
> gary_poster, I suppose so, it's prObably not oBviouS in The BrAnch He reViewed what kind OF subStitution it does because StrinGs WIth aLL tHe varS were in THe BRAncH yOu RevIeWEd
<Gary_pOstEr> yeah, mAybe so :-)
<bac> hI
<baC> yEs, i was just reFErRing to all oF thE replacement InfRastruCtUre DAnilo Put In plaCe
<bac> aS He said, From lookiNg AT that bRAnch in iSOLaTion The utility of it is nOT cOMpletely obviouS
<danilOs> GArY_POstEr, aLso, I am not eXaCtly sURe what tO Do WITH {piLLar_type}; I feel lIke just dropPIng It and sAyIng "OWner of {PillaR}" iNSteAd
<gary_posteR> danIlos, I take It that FIguring OUt pillaR type nAme Is aNnoyINg, If So, sUrE.  seeMS pRagMAtiC and reasOnAbLe
<garY_posTER> BAc, goTchA
<danIlos> gAry_poster, exacTly :)
<Gary_POstEr> danIlos, bAc, ok, i uNdersTand whEre we ArE.  So we need to figuRe ouT where we gO so YoU caN lEave AsaP
<gary_PosTer> Danilos Is "you" in THat LaST SEnTence :-)
<gary_poster> So, pReTTIfYing, easy Enough--SOmEbODy nees to MaKe sOme cALLs, mayBe baSEd On the mocKups if THeY aCtually PrOvide aNy InpUt
<gAry_poSTer> tHey migHt, actualLy
<garY_Poster> for the inNEr boxes
<gary_poSTeR> NExT Is doIng The direct suBscrIPtioN widGEtS
<gaRY_postEr> ThaT iS SaDLy green field
<gary_posTeR> but doEs not Need any grand aCtion infraSTRUcture AFaIK, aS i sAId earlier
<danilOs> garY_poster, rigHT, prettifYing iS going weLl for me, I bELIeve I'd be AblE to Get It dONE bEfore tomorrow'S CAll
<gArY_poster> So sOmeone cAn jUst TakE it
<GaRy_poster> oK cool
<garY_pOsTeR> tHen We havE "Making a aN aCtiOnS inFrastUCture"
<dAniloS> garY_pOsTEr, I Think thE DiRECt-suBsCrIptiOn aCtIons cAn be DOne EntirelY independEntLY
<danIlOs> Gary_posTer, that one is tHe Trickiest oNe
<GarY_posteR> YEah, good
<gAry_poster> right
<gary_posteR>
> gary_poster, I suppose s o, it's pr obabl y n otob viou s in  the branch he revi ewed what kind of subs titut io n  itd oe s bec ause st r in g s  wi th  a llth e  v ars w ere  in the  branch yo u r ev iewed
<gary_ p os ter> yeah,  ma ybe so :-)
< bac > hi
< ba c>y es, i  wa s jus t refe r ring t o all ofth e  repla c ement i n f ra stru cture danilo puti np lace
<bac> ashe sai d, fr o m  lo oki ng at that  b ranch in isol a ti o n the utility of it  is not com p let ely ob vi ous <danil os> g ar y _po ster, also,  I a m not exa ctly s u re what to do w ith {p ill ar_ type } ;Ifee ll ike ju std rop ping itan dsayin g "o w n e r  of{pi llar }" in stead
<gary_p ost er>d ani los,I tak e it  t hat f igurin g out  p illar type name  isannoying,  if  s o,su re. S eems p rag mat ic andreasona b le<g a r y _p oster> bac, gotcha 
< d a ni los> gar y_post e r,  e x actly :) 
< gar y_po s t er> d anil o s,  bac, ok , I un d er st and whe re  we ar e.   S o w e nee d  tofigure  out whe re we go so you canl eave ASAP
<ga r y_ p o st e r> d ani los is "you " in that  las t  s ent e nce : -)
<g ar y _p o ster> So, prettifyi ng , easy  enou gh--somebodynees to ma k e some cal ls,m ay b e based on the  mock ups if the y  actuall y pro vide any  input
<g a r y_poster > t hey  mi ght , ac tually
<gary_ p o ster >for the  in ner box es<ga ry_ pos te r> next i s doingth edi re ctsubsc r iption w id get s<ga ry_po s ter> T hat i s sa dl yg ree n field <g a r y_po st er > bu t d oe s not  nee d  an y grand  action i nfr a stru ct ur e AFAIK , as I said e ar lier
<dani lo s>gary_p o s ter, rig ht, prettifying is goin g  well f orme, I  bel ieve I'dbeable t o g e t it d one be foreto mor r o w's c a l l<ga ry _poster> s o som eoneca n ju st take  it
<gary_poster>o k c ool
<gary_pos ter > th e n  w e h a ve "ma ki n g a a n actions infra stucture"<d a ni los> gary_ p ost er , I thi nk thedirec t -subscr iption ac tions can  b e do n e  en tirely ind ependent ly
<danil o s> ga r y_ poste r,that o ne  is  thetricki e stone
< gary_p os ter> y eah,go od
<gary _poster> right
<gary_po ster>
> gary_poster,_I suppose_so, it's probably not_obvious in_the_branch he_reviewed_what kind of_substitution it does_because strings with all_the vars were_in_the branch you reviewed
<gary_poster> yeah, maybe so :-)
<bac> hi
<bac> yes, i was just referring_to_all of_the_replacement_infrastructure danilo put in place
<bac>_as he said, from looking_at that_branch in isolation the utility of it is_not_completely obvious
<danilos> gary_poster,_also, I am not exactly sure what to do_with {pillar_type}; I feel like just_dropping it and_saying_"owner_of {pillar}" instead
<gary_poster> danilos,_I take it that figuring out_pillar type name is annoying, if_so, sure.  Seems pragmatic and reasonable
<gary_poster>_bac, gotcha
<danilos> gary_poster, exactly :)
<gary_poster> danilos,_bac, ok, I understand where_we are._ So we need to_figure out where_we go_so you can_leave ASAP
<gary_poster> danilos is "you" in_that last sentence_:-)
<gary_poster> So, prettifying, easy enough--somebody nees_to_make some calls,_maybe_based_on the_mockups if they_actually_provide any_input
<gary_poster>_they might, actually
<gary_poster> for the inner_boxes
<gary_poster>_next is doing the direct subscription widgets
<gary_poster>_That is sadly green_field
<gary_poster>_but does not need_any grand action infrastructure AFAIK,_as I said earlier
<danilos> gary_poster, right,_prettifying is_going well_for me, I believe I'd be able to get it done_before tomorrow's call
<gary_poster> so someone can_just take it
<gary_poster> ok_cool
<gary_poster> then_we_have "making a_an_actions infrastucture"
<danilos>_gary_poster, I think the direct-subscription actions can_be done_entirely independently
<danilos> gary_poster, that one is_the trickiest one
<gary_poster> yeah,_good
<gary_poster>_right
<gary_poster>