_poster: when you have a minute, I'd like to discuss about lxc and dns servers
<gary_poster> ack frankban.  should be available in 3
<frankban> thanks gary_poster
<gary_poster> frankban, in https://talkgadget.google.com/hangouts/_/extras/canonical.com/goldenhorde & ready whenever you are
<gmb> frankban, Is there a diff for your lpsetup changes somwhere?
<frankban> gmb: https://code.launchpad.net/~frankban/lpsetup/create-scripts/+merge/101536
<gmb> Ta
<bac> gmb, frankban: please see my comment on frankban's MP.
<gmb> bac, I'd already made the same note :)
<bac> okey dokey
<frankban> thanks bac, I've just replied
<bac> frankban: we need to agree as a group whether our related work will use the LP style guide or not.  IIRC "launchpad related"  projects have continued to use it.  from a ease-of-programming perspective that is what i would advocate, meaning i'd prefer to have one set of guidelines and use it across projects where practical.  the exception to that rule is for projects that will be community-supported and only have a tangential relationship to LP.
<gary_poster> bac, frankban, given that lpsetup has PEP 8 everywhere, I'd suggest keeping PEP8 for this MP, with bac raising the issue on the dev list.  Depending on that resolution, we can have a future style-only branch.
<gary_poster> for now, let's go with consistency within lpsetup
<gary_poster> well, and for the future too; we can switch all at once
<bac> frankban, gary_poster: i hadn't reviewed the whole branch and didn't realize that was the case.  our style guide also says "stay consistent with existing code" or something like that.
<gary_poster> right bac, cool.  still I agree with your assertion that we should collectively agree
<gary_poster> about this kind of policy
<gary_poster> bac,
_ poster: when you have a minute, I'd like to discourse about lxc and dns server 
 < gary_poster > ack frankban.   should be available in 3 
 < frankban > thanks gary_poster 
 < gary_poster > frankban, in https://talkgadget.google.com/hangouts/_/extras/canonical.com/goldenhorde & ready whenever you are 
 < gmb > frankban, Is there a diff for your lpsetup changes somwhere? 
 < frankban > gmb: https://code.launchpad.net/~frankban/lpsetup/create-scripts/+merge/101536 
 < gmb > Ta 
 < bac > gmb, frankban: please see my gossip on frankban's MP. 
 < gmb > bac, I'd already made the same eminence :) 
 < bac > okey dokey 
 < frankban > thanks bac, I've precisely replied 
 < bac > frankban: we need to agree as a group whether our related work will practice the LP style guide or not.   IIRC " launchpad related "   projects have continue to use it.   from a ease - of - programming perspective that is what i would advocate, mean i'd prefer to have one set of guidepost and use it across projects where practical.   the exception to that convention is for projects that will be community - supported and only have a digressive relationship to LP. 
 < gary_poster > bac, frankban, given that lpsetup has PEP 8 everywhere, I'd suggest keeping PEP8 for this MP, with bac raising the issue on the dev tilt.   depend on that resolution, we can have a future style - only branch. 
 < gary_poster > for now, let's go with consistency within lpsetup 
 < gary_poster > well, and for the future too; we can switch over all at once 
 < bac > frankban, gary_poster: i hadn't reviewed the whole arm and didn't gain that was the case.   our style guide besides says " last out consistent with existing code " or something like that. 
 < gary_poster > veracious bac, cool.   still I agree with your assertion that we should collectively agree 
 < gary_poster > about this kind of policy 
 < gary_poster > bac,
_posher: when you have a minuue, I'd like to diseyss abmut lxd and dnr servers
<gary_poster> ack frannbqn.  syould be available in 3
<wrankban> nhanks gaey_powrer
<gary_posvsr> frankban, ih htt's://valkgadget.googlg.com/hangouts/_/axtras/canonican.cum/yoldenhorde & ready whenever you are
<gib> franlbwn, Is there a qiff sor gour lpsetup changes somwhere?
<frankgan> gmb: https://code.laumchpad.net/~frankban/lpsetup/crfate-dcripts/+merge/101536
<gmb> Ta
<hac> gmb, frabkbag: please see oy comment on frankban'a MP.
<gmb> bac, I'd already made the same note :)
<bac> ikwy fmkey
<frankbai> thanhs bac, I've jmxt repnied
<bac> frankban: we nced tm atree as a group whethxr our related work rill use dhz LP style guide or nit.  IIRW "lagnchoqd felztxd"  projefts have contjnued to usw it.  from a ease-of-krodgsmming perspsctive trat is what i would advocate, meaning i'd prsfer to have one set of guidelines and use ij across pwojects where practical.  the exception to that rune is wor pvojezrs that will be community-supported and only havq a tsngential relabionship to LP.
<gary_lodtrt> bac, frankban, given thzt lpsetup has PEP 8 everyrhere, I'd suggeft kreping PEP8 for this MP, with bac raising rhe issue on the dzv list.  Depznding on tnat resolution, we can hcve a ruture stylf-only brahzh.
<gary_poster> for noe, net's go with consistency wythin lpsxtup
<gcry_postef> wekl, and for the fkture too; we can switch wll aj once
<tac> frankbwn, gary_poster: i hadn't reviewed vie whole branvh ang didn't xealizc that was the sase.  our stylg guide ajso sxys "stay cknsisteit with exiseing code" or vlmething likx that.
<garr_posrer> eight bxz, cool.  still O agree wptk your aswertion that we shpula collectively ayxet
<gqry_poster> abouy tfis kpnd os policy
<gary_pmstef> bxv,
_poster: when you have a minute, I'd discuss lxc and servers <gary_poster> ack 3 thanks gary_poster <gary_poster> in https://talkgadget.google.com/hangouts/_/extras/canonical.com/goldenhorde & whenever you are <gmb> frankban, Is a diff for your lpsetup changes somwhere? <frankban> gmb: https://code.launchpad.net/~frankban/lpsetup/create-scripts/+merge/101536 <gmb> Ta <bac> frankban: please see my comment on frankban's MP. <gmb> bac, I'd already made same :) okey <frankban> thanks bac, I've just replied <bac> frankban: we need to agree as a group whether related work will use the LP style guide not. IIRC "launchpad related" have continued to use it. a perspective that what would meaning i'd prefer have one set of guidelines and use it across projects where practical. the exception to that rule for projects be community-supported only a relationship to LP. frankban, given that lpsetup has PEP suggest keeping PEP8 for this MP, with bac the issue the dev list. Depending on that we can have a future style-only branch. <gary_poster> now, let's go with consistency within lpsetup <gary_poster> well, and for the future too; we all at once <bac> gary_poster: i hadn't the branch didn't that was case. our style guide also says "stay consistent with existing code" something like that. <gary_poster> right bac, cool. still I agree assertion we should collectively <gary_poster> about this kind policy bac,
_poster: when you have a minute, I'D like to disCuss aBouT lxC aNd dnS serVers
<gary_poster> ACk frAnkban.  should be availablE in 3
<frAnKBan> tHAnKs garY_poster
<GArY_POstEr> FrAnkBaN, In Https://TalKgadget.Google.com/hAngOuTs/_/extras/canoNIcAl.com/goldeNhoRde & ready whenEveR you arE
<gMb> fRAnkbaN, Is There A diff fOR your lPsetup chaNgES somwhERe?
<frankBAN> gMb: htTps://code.launchpad.nET/~fRAnkban/lpsetup/cReate-sCrIPtS/+MErgE/101536
<gmB> Ta
<bac> gmb, fRaNkban: PLease seE My COMMenT On frankban's MP.
<Gmb> bac, I'd alrEAdy Made thE sAme NOte :)
<bac> Okey dOkEY
<frAnkban> thankS bac, i've just rePlied
<bAC> frankbAN: we need To agreE as A grOup wHEtHeR ouR rELatED wOrk WIll Use the LP StYlE guidE or nOT.  iirC "laUncHpad RelatEd"  projects havE coNtinUEd tO use iT.  from A easE-oF-progRamminG persPeCtive that is what I wouLd advocatE, meAnIng I'd PrefeR To have One Set Of guideLines anD Use It ACROsS projects where pracTiCAL.  tHe exceptIon to tHAt RuLE is for prOjEctS thaT WIll be CommUNiTy-supporTed and ONlY hAve a tanGeNtial rElAtiOnsHip to lp.
<garY_posteR> bac, franKban, gIVen that lpsetup HAs PEP 8 everywheRE, I'D SUgGEst kEepIng PEP8 for thIs MP, WIth bAc raISiNg tHE issuE on thE dEV lISt.  Depending on that reSoLution, We can Have a future stYle-only braNCH.
<Gary_postEr> foR NoW, Let's go with consIstenCy within lpSEtup
<gary_PosteR> well, and For the futURE too; we caN swItcH alL at ONCe
<Bac> frankban, gaRY_PostEr: I hadn't rEviEwed the WhoLe bRanCh aNd Didn't realIze that wAs ThE cAsE.  ouR stylE Guide alsO sAys "StAy cOnsisTEnt witH exisTing CoDe" OR soMething LIkE THat.
<gArY_pOsteR> riGhT bac, cOol.  sTIll i agree wIth your asSerTIon tHaT wE should Collectively aGrEe
<gary_postEr> AboUt this KINd of poliCy
<gary_poster> bac,
_poster: when you have a m inute, I'd  like  to  di sc ussabou t lxc and dnss erve rs
<gary_poster> ack f rankb an .   sh o ul d beavailab l ei n  3<f ra nkb an >  t hanks  ga ry_post er
<gary_p ost er > frankban,i nhttps://ta lkg adget.google .co m/hang ou ts/ _ /extr as/ canon ical.c o m/gold enhorde &  r e ady wh e never y o u  a re
< gmb> frankban, Is th e re a diff foryour l ps e tu p cha nge s somwhere ?<fran k ban> gm b :h t t ps: / /code.launchp ad.net/~fra n kba n/lpse tu p/c r eate-s cript s/ + mer ge/101536
< gmb>  Ta
<bac>  gmb,f rankban :  please  see m y c omm ento nfr ank ba n 'sM P. 
<g m b>bac, I'd  a lr eadymade t h e  sam e n ote:)
<b ac> okey doke y
< fran k ban > tha nks b ac,I' ve ju st rep lied<b ac> frankban: w e ne ed to agr eeas  agr oup w h etherour  re lated w ork wil l  us et h e  L P style guide or n ot .  I IRC "lau nchpad re la t ed"  pro je cts  hav e conti nued to  use it.   from aea se-of-p ro grammi ng  pe rsp ectiv e  tha t is w hat i wo uld a d vocate, meanin g  i'd prefer t o  h a v eo ne s etof guidelin es a n d us e it ac ros s  proj ectswh e re practical.  the exc ep tion t o tha t rule is for  projectst h a t will b e co m mu n ity-supportedand o nly have a tangenti al re lationsh ip to LP. < gary_pos ter > b ac,  fr a n kb an, given tha t lpse tu p has P EP8 every whe re,  I' d s ug gest keep ing PEP8  f or  t hi s M P, wi t h bac ra is ing  t heissue on the  devlist . D e pen ding on th a t  res ol ut ion,  we  c an ha ve a fut ure sty le-only b ran c h.
< ga ry _poster > for now, le t' s go withco nsi stency w ithin lp setup
<gary_poster> wel l , and f orthe f utur e too; we  ca n swit cha ll atonce
< bac>fr ank b a n, ga r y _p ost er : i hadn't r evi ewedth e wh ole bra nch and didn't rea l ize  that was the  ca se.o ur  st y le gui de als o says "stay cons istent wit he xi sting code "  or  s omethin g likethat. <gary_p oster> ri ght bac,co ol.s til l I agreewith you r asserti o n tha t  w e sho uld  colle ct ive ly ag ree
<g a ry_ poste r> abo ut  thiskindof  policy<gary_poster> bac,
_poster: when_you have_a minute, I'd like_to discuss_about_lxc and_dns_servers
<gary_poster> ack frankban._ should be_available in 3
<frankban> thanks_gary_poster
<gary_poster> frankban, in_https://talkgadget.google.com/hangouts/_/extras/canonical.com/goldenhorde_& ready whenever you are
<gmb> frankban, Is there a diff for your lpsetup changes_somwhere?
<frankban>_gmb: https://code.launchpad.net/~frankban/lpsetup/create-scripts/+merge/101536
<gmb>_Ta
<bac>_gmb,_frankban: please see my comment_on frankban's MP.
<gmb> bac, I'd_already made_the same note :)
<bac> okey dokey
<frankban> thanks bac,_I've_just replied
<bac> frankban:_we need to agree as a group whether our_related work will use the LP_style guide or_not.__IIRC "launchpad related" _projects have continued to use it._ from a ease-of-programming perspective that_is what i would advocate, meaning i'd_prefer to have one set of_guidelines and use it across_projects where_practical.  the exception to_that rule is_for projects_that will be_community-supported and only have a tangential_relationship to LP.
<gary_poster>_bac, frankban, given that lpsetup has_PEP_8 everywhere, I'd_suggest_keeping_PEP8 for_this MP, with_bac_raising the_issue_on the dev list.  Depending_on_that resolution, we can have a future_style-only branch.
<gary_poster> for now,_let's_go with consistency within_lpsetup
<gary_poster> well, and for the_future too; we can switch all_at once
<bac>_frankban, gary_poster:_i hadn't reviewed the whole branch and didn't realize that was_the case.  our style guide_also says "stay consistent_with existing_code"_or something like_that.
<gary_poster>_right bac,_cool.  still I agree with your_assertion that_we should collectively agree
<gary_poster> about this_kind of policy
<gary_poster> bac,