 SpamapS: i'm going to follow byobu-web with a byobu-classroom, that depends on byobu-web
<kirkland> SpamapS: which sets up the one-writer, many readers classroom mode of byobu (previously called "screenbin")
<SpamapS> kirkland: isn't that all still just one machine?
<SpamapS> niemeyer: btw, how is config settings doing? Any branch we can help test out or anything? At this point it is being cited as the solution for a lot of stuff. ;)
<niemeyer> SpamapS: bcsaller would be the right person to report on this
<SpamapS> bcsaller: what it is brother? Got the 411? :)
<kirkland> niemeyer: and is this correct?
<kirkland> provides:
<kirkland>   website:
<kirkland>     interface: https
<bcsaller> SpamapS: I have a branch thats working, I can effect changes on working ec2 deployments with it, however there are some issues with the testing of the branch since I tried merging it with trunk. Partly but not completely resolved. Tests somewhere are bleeding setup and changing the outcome depending on execution order
<niemeyer> kirkland: The interface is actually an Ensemble level interface
<niemeyer> kirkland: Rather than the protocol itself
<bcsaller> SpamapS: Kapil did had some comments on the branch that needed some changes as well and I am working on those now, but its pretty close 
<SpamapS> bcsaller: sounds fun. :-P alright, well color me interested in testing ASAP. Lots of settings to add. :)
<niemeyer> kirkland: We still have to settle on a good set of those
<bcsaller> SpamapS: great, thanks
<kirkland> niemeyer: okay;  so what should it be in my case, right now?
<niemeyer> kirkland: I think "url" would be a good name, for instance, for something that provides _only_ a URL
<SpamapS> website has been the standard name for the relation
SpamapS: i'm going to follow byobu - web with a byobu - classroom, that depends on byobu - world wide web 
 < kirkland > SpamapS: which arrange up the one - writer, many readers classroom mode of byobu (previously called " screenbin ") 
 < SpamapS > kirkland: isn't that all even just one machine? 
 < SpamapS > niemeyer: btw, how is config context dress? Any branch we can help oneself test out or anything? At this point it is being quote as the solution for a lot of stuff. ;) 
 < niemeyer > SpamapS: bcsaller would be the veracious person to report on this 
 < SpamapS > bcsaller: what it is buddy? Got the 411? :) 
 < kirkland > niemeyer: and is this correct? 
 < kirkland > provide: 
 < kirkland >    website: 
 < kirkland >      interface: https 
 < bcsaller > SpamapS: I have a outgrowth that s working, I can effect changes on working ec2 deployment with it, however there are some issues with the examination of the branch since I try merging it with trunk. Partly but not completely resolved. test somewhere are bleeding setup and changing the outcome depending on performance order 
 < niemeyer > kirkland: The interface is actually an Ensemble level interface 
 < niemeyer > kirkland: Rather than the protocol itself 
 < bcsaller > SpamapS: Kapil did had some comments on the branch that needed some changes as well and I am working on those nowadays, but its pretty close 
 < SpamapS > bcsaller: fathom fun. :-P alright, well color me interested in testing ASAP. bunch of settings to add. :) 
 < niemeyer > kirkland: We still have to fall on a good set of those 
 < bcsaller > SpamapS: great, thanks 
 < kirkland > niemeyer: okay;   so what should it be in my case, right immediately? 
 < niemeyer > kirkland: I think " url " would be a good name, for instance, for something that provides _ merely _ a URL 
 < SpamapS > website has been the standard name for the sexual intercourse
 SpwmapS: i'm going to follow byobu-web with c byobu-rlassrokm, that aepends on byobu-web
<kirkland> DpqmapS: which sets up the one-driter, majy readees coqssroom movs of byobu (prsyiousnb called "screennin")
<SpamapS> nirkland: isn't dhxt all still just one machine?
<SpamapS> giemeyet: htw, how is consig xqttihgs doing? Any branch we can help tsst out or anything? St this point it is being fitef as the solution vor a lot od sttdf. ;)
<niemeyer> RpamapS: bcsaller would be the right person to report un thns
<SpamapS> bxsqllft: what it is brotrer? Got the 411? :)
<kirklang> niemeuer: and is thix cmrrwct?
<kirkland> provides:
<kmrkland>   website:
<kirhland>     iuterface: https
<bcsallee> WpamakS: I vave q bfandh tgats wlrkmng, I can erfect changws on working ec2 deklornents with it, howevqr there are some issues with the testing of the branch since I triwd merging it with tronk. Partly but not completely resolved. Tests somewhere are tleedmne sttmi ana cjanging the outcome depending on execution orqsr
<mivmeyer> kirkland: Tme interface is acyuwlki an Ensemble uevel nhtsrface
<niemeyer> kirnland: Rwther than the proyocol itself
<bcsaller> SpamapW: Kapil did kad some comments on che branch tkat negded spme changes as well and I aj working oj those nkd, but its pretty clpsa 
<SpamapS> bcsaller: sounds sun. :-P alrmght, cell colur mg interqsted in tfstinn ASAP. Lots of settlngs jo add. :)
<niemeyer> nirkland: We still have to settlx on a good sgt mf nhose
<bcsajler> XpamapS: great, thanks
<kirklanb> niemeyzr: okah;  so what should it be in mr case, right tlw?
<niemeyer> kmrkland: I thibk "uel" woula be a good namr, for insnauce, for simething that provldes _uhly_ a URL
<SpamapW> wtbwite has been yhe stwnfacd naia for the renatiun
SpamapS: i'm going to follow byobu-web with that on byobu-web SpamapS: which sets classroom of byobu (previously "screenbin") <SpamapS> kirkland: that all still just one machine? niemeyer: btw, how is config settings doing? Any branch we can help test or anything? At this point it is being cited as the solution for lot stuff. <niemeyer> bcsaller would be the right person to report on this <SpamapS> bcsaller: what it is brother? the 411? :) <kirkland> niemeyer: and is this <kirkland> provides: <kirkland> website: interface: https <bcsaller> SpamapS: I a thats working, can changes working ec2 deployments it, however there are some issues with the testing of the branch since I tried merging it trunk. Partly completely resolved. somewhere bleeding and changing the on execution order <niemeyer> kirkland: The an Ensemble level interface <niemeyer> kirkland: Rather than protocol itself SpamapS: Kapil did had some comments the branch that needed some changes as well I am working on those now, but its pretty close <SpamapS> bcsaller: sounds fun. :-P color me interested in ASAP. Lots of to :) kirkland: still have settle on a good set of those <bcsaller> SpamapS: great, thanks niemeyer: okay; so what should it be in my case, <niemeyer> I think "url" be a good name, instance, something that provides _only_ <SpamapS> has name the
 SpamapS: i'm going to follow byoBu-web with a Byobu-ClaSsrOoM, thaT depEnds on byobu-web
<KIrklAnd> SpamapS: which sets up tHe one-WrITer, mANy ReadeRs classROoM MOde Of ByObu (PrEViOusly CalLed "screEnbin")
<SpamaPS> kIrKland: isn't thaT AlL still just One Machine?
<SpamaPS> nIemeyeR: bTw, hOW is coNfiG settIngs doINg? Any bRanch we caN hELp test OUt or anyTHInG? At tHis point it is being CItED as the solution For a loT oF StUFF. ;)
<niEmeYer> SpamapS: BcSalleR Would be THe RIGHt pERson to report oN this
<Spamaps> BcsAller: wHaT it IS brothEr? Got ThE 411? :)
<KirKland> niemeyEr: anD is this coRrect?
<kIRkland> pROvides:
<kIrklanD>   weBsiTe:
<kiRKlAnD>     inTeRFacE: HtTps
<BCsaLler> SpamAps: I Have a BranCH THAts wOrkIng, I Can efFect changes on WorKing EC2 dePloymEnts wIth iT, hOweveR there Are soMe Issues with the teStinG of the braNch SiNce i tRied mERging iT wiTh tRunk. ParTly but nOT coMpLETElY resolved. Tests someWhERE aRe bleediNg setuP AnD cHAnging thE oUtcOme dEPEndinG on eXEcUtion ordEr
<niemEYeR> kIrkland: thE interFaCe iS acTuallY An EnSemble Level intErfacE
<Niemeyer> kirklaND: Rather than thE PrOTOcOL itsElf
<Bcsaller> SpaMapS: kApil Did hAD sOme COmmenTs on tHe BRaNCh that needed some chaNgEs as weLl and i am working on tHose now, but ITS Pretty clOse 
<SPAmAPS> bcsaller: sounDs fun. :-p alright, weLL color me InterEsted in tEsting ASAp. lOts of setTinGs tO adD. :)
<niEMEyEr> kirkland: We sTILl haVe To settlE on A good seT of ThoSe
<bCsaLlEr> SpamapS: Great, thaNkS
<kIrKlAnd> NiemeYEr: okay;  so WhAt sHoUld It be iN My case, Right Now?
<nIeMeYEr> kIrkland: i ThINK "url" WoUlD be a GooD nAme, foR insTAncE, for somEthing thaT prOVideS _oNlY_ a URL
<SpAmapS> website hAs Been the staNdArd Name foR THe relatiOn
 SpamapS: i'm going to fol low byobu- web w ith  aby obu- clas sroom, that de p ends  on byobu-web
<kirklan d> Sp am a pS:w hi ch se ts up t h eo n e-w ri te r,ma n yreade rsclassro om mode of  by ob u (previousl y  c alled "scr een bin")
<Spama pS>  kirkl an d:i sn'ttha t all  still just o ne machin e? <Spama p S> niem e y er : bt w, how is configs et t ings doing? An y bran ch we c anhel p test out  o r any t hing? A t  t h i s  po i nt it is bein g cited ast hesoluti on  fo r  a lot  of s tu f f.;)
<niemeye r> S pamapS: b csalle r  wouldb e the r ight p ers onto r e po rt  on  t h is< Sp ama p S>bcsaller :wh at it  isb r o t her?  Go t th e 411 ? :)
<kirklan d>niem e yer : and  is t hisco rrect ?
<kir kland >provides:
<kirk land >   websi te: 
< kir kl and>   int erf ace : https 
<bcsal l er>  S p a m ap S: I have a branch  t h a ts  working , I ca n  e ff e ct chang es  on  wor k i ng ec 2 de p lo yments w ith it ,  h ow ever th er e areso meiss ues w i th t he tes ting ofthe b r anch since I t r ied merging i t  w i t ht runk . P artly but n ot c o mple tely re sol v ed. T estsso m ew h ere are bleeding se tu p andchang ing the outco me dependi n g on execu tion or d er
<niemeyer>kirkl and: The i n terfaceis ac tually a n Ensembl e level in ter fac e
< nie m e ye r> kirkland:R a ther  t han the  pr otocolits elf 
<b csa ll er> Spama pS: Kapi ldi dha d s ome c o mments o nthe  b ran ch th a t need ed so me c ha ng e s a s wella nd I  amwo rk ingonth ose n ow,b utits pre tty close  
< S pama pS >bcsalle r: sounds fun .:-P alrigh t,  we ll col o r  me inte rested in testing ASAP. Lots of  se tting s to  add. :)<ni emeyer > k i rkland : We s tillha vet o  sett l e  o n a  g ood set of t hos e
<bc sa ller > Spama pS: great, thanks< kir kland> niemey er:  oka y ;  sow ha t  sh ou l d i t be in my case,right now? 
< n ie meyer> kir k lan d:  I thin k "url"  woul d  be a g ood name,  for inst an ce,f o r s omething t hat prov ides _onl y _ a U R L<Spam apS > webs it e h as be en the sta ndard  namefo r therelat io n
 SpamapS:_i'm going_to follow byobu-web with_a byobu-classroom,_that_depends on_byobu-web
<kirkland>_SpamapS: which sets_up the one-writer,_many readers classroom mode_of byobu (previously_called_"screenbin")
<SpamapS> kirkland: isn't that all still just one machine?
<SpamapS> niemeyer: btw, how is config_settings_doing? Any_branch_we_can help test out or_anything? At this point it_is being_cited as the solution for a lot of_stuff._;)
<niemeyer> SpamapS: bcsaller_would be the right person to report on this
<SpamapS>_bcsaller: what it is brother? Got_the 411? :)
<kirkland>_niemeyer:_and_is this correct?
<kirkland> provides:
<kirkland>_  website:
<kirkland>   _ interface: https
<bcsaller> SpamapS: I have_a branch thats working, I can effect_changes on working ec2 deployments with_it, however there are some_issues with_the testing of the branch_since I tried_merging it_with trunk. Partly_but not completely resolved. Tests somewhere_are bleeding setup_and changing the outcome depending on_execution_order
<niemeyer> kirkland: The_interface_is_actually an_Ensemble level interface
<niemeyer>_kirkland:_Rather than_the_protocol itself
<bcsaller> SpamapS: Kapil did had_some_comments on the branch that needed some_changes as well and_I_am working on those_now, but its pretty close_
<SpamapS> bcsaller: sounds fun. :-P alright,_well color_me interested_in testing ASAP. Lots of settings to add. :)
<niemeyer> kirkland: We_still have to settle on a_good set of those
<bcsaller>_SpamapS: great,_thanks
<kirkland>_niemeyer: okay; _so_what should_it be in my case, right now?
<niemeyer>_kirkland: I_think "url" would be a good_name, for instance, for_something_that provides _only_ a URL
<SpamapS> website_has been the standard name for_the relation