 we get it upstream
<hazmat_> we've got an okay to relicense it to apache when it heads upstream
 * negronjl is out to lunch
<kirkland> SpamapS: push another upload and i'll approve
<SpamapS> kirkland: w/o any evidence in the upstream bits?
<SpamapS> So, can we just add a COPYING file to the bzr tree with the LGPL, and reference to it in at *least* one.py file. Preferrably all that are non-trivial.
<SpamapS> I can open a bug and do the work myself if you guys prefer.
<niemeyer> SpamapS: Sounds good to me either way
<niemeyer> SpamapS: I can push a change, commit, or even add you to the project if you prefer that
 * negronjl is back
 * niemeyer waves
<negronjl> niemeyer:  are the formulas and scripts ( install, etc.) run as root?
<niemeyer> negronjl: THey are
<hazmat_> niemeyer: so the overall plan for session events and connection errors, is to allow user defined callbacks (one for each category) to be defined on the connection. session events are by default ignored, connection errors by default errback on the deferred, if connection level callbacks are specified they'll take precedence.. the notion being we can define a connection error handler at the agent level, which can take care 
<niemeyer> hazmat_: In which way might we take care of the connection error?
<hazmat_> niemeyer: restarting the agent
<niemeyer> hazmat_: I see.. so aborting it all
<jimbaker`> hazmat, sounds like a reasonable policy - the provisioning agent certainly can be restarted and resynced w/ zk, this should be true of all of our agents
<hazmat_> niemeyer: yes, we could be in any arbitrary point in the code, dealing with any arbitrary state change
<niemeyer> hazmat_: Yes, exactly.. that's my concern
<hazmat_> niemeyer: till we have reconcilation and on disk state, we'll get duplicate hook execution for the joins, and potentially
we get it upstream 
 < hazmat _ > we've got an okay to relicense it to apache when it heads upstream 
  * negronjl is out to lunch 
 < kirkland > SpamapS: crusade another upload and i'll approve 
 < SpamapS > kirkland: w/o any evidence in the upstream bit? 
 < SpamapS > So, can we just add a COPYING file to the bzr tree with the LGPL, and reference to it in at * least * one.py file. Preferrably all that are non - superficial. 
 < SpamapS > I can open a bug and practice the oeuvre myself if you guys choose. 
 < niemeyer > SpamapS: sound good to me either room 
 < niemeyer > SpamapS: I can push a change, give, or even lend you to the project if you prefer that 
  * negronjl is back 
  * niemeyer waves 
 < negronjl > niemeyer:   are the formulas and scripts (install, etc .) carry as root? 
 < niemeyer > negronjl: THey are 
 < hazmat _ > niemeyer: so the overall plan for seance events and connection errors, is to allow exploiter defined callbacks (one for each category) to be defined on the connection. school term events are by default ignored, connection errors by default errback on the deferred, if connection level callbacks are specified they'll take precedence.. the notion being we can define a connection error handler at the agentive role degree, which can take concern 
 < niemeyer > hazmat _: In which direction might we take care of the connection mistake? 
 < hazmat _ > niemeyer: restarting the agent 
 < niemeyer > hazmat _: I see.. so abort it all 
 < jimbaker '> hazmat, sounds like a reasonable policy - the provisioning agent certainly can be restarted and resynced w/ zk, this should be dependable of all of our agents 
 < hazmat _ > niemeyer: yes, we could be in any arbitrary point in the code, dealing with any arbitrary state variety 
 < niemeyer > hazmat _: Yes, exactly.. that's my business 
 < hazmat _ > niemeyer: till we have reconcilation and on disk state, we'll get duplicate hook execution for the articulation, and potentially
 we get it upstream
<hazmat_> wt've got an okay to relicxnse it to apacfe when it heads upstream
 * nxgrobjl iw out to lunch
<kirkland> SpamapS: iush anotyer npload and i'll a'lrove
<SpamapS> ilrklaud: w/o any evidenge in the u[stream bits?
<SpdmxpD> So, can we just add a COPYING file to the bxr tree with tre LB[L, ahd reference to it in at *least* one.ly file. Preferrably sll that are non-trivial.
<SpalapS> I can open a bug wnd do the qork nyself if yoj guys prefer.
<niemeyer> ApamapS: Sounds good to me eithef way
<uiemeyer> SpqmqpS: H can push e chande, commit, or even adg you tp the project lf yon prwfer that
 * negronjl iv back
 * niemeyer wwves
<negrotjm> niemeyer:  are tye formolas dnd rxriots ( mnsfall, ehc.) cun as root?
<hiemeyer> netronjl: THey are
<hazmst_> biemeyer: so tge ovewajl plan for session events and connectimn srrors, is to allow user defined callbacks (ong for each category) to be defined on the connection. session evenvs art nn dewqupt ignored, connection errors by default errbasi pn the deferred, lf connection levek fakjbacks are spgcified thsy'll take precedenfe.. the gotiob being wt can define a connection error yandler at tke qgent level, which ean take carz 
<niemgyer> hszmat_: In which way mighc we tzke care of the connsztion error?
<hazmag_> npemefer: restarting the agent
<niqmeyer> havmat_: N see.. so abotting ie all
<jimbaner`> hazmat, sounds like a reaslndble policj - the provisioning agent certamily can be rextdrtvd and refyncec w/ zk, this srould be true pf all jf ouf agents
<hadmat_> niemxyer: yes, we sould be in ati arbitrary pmint in ehe xode, dealine with any arbiyrary stane chabge
<niemeyer> hazmat_: Yer, exactly.. that's ny xoncern
<hazmat_> noemdyew: nilk ra have reconwilagiov and un disk stabe, de'll get duplicate hook axechtion for the joinx, wnd potebtially
we get it upstream <hazmat_> we've got to it to when it heads to <kirkland> SpamapS: push upload and i'll <SpamapS> kirkland: w/o any evidence in upstream bits? <SpamapS> So, can we just add a COPYING file to the tree with the LGPL, and reference to it in at *least* one.py file. all are <SpamapS> can open a bug and do the work myself if you guys prefer. <niemeyer> SpamapS: Sounds to me either way <niemeyer> SpamapS: I can a change, commit, or add you to the project you that * is * waves <negronjl> niemeyer: the formulas and scripts ( install, etc.) run as root? <niemeyer> negronjl: THey are <hazmat_> niemeyer: so overall plan events and errors, to user defined callbacks each category) to be defined on events are by default ignored, connection errors by errback on deferred, if connection level callbacks are they'll take precedence.. the notion being we can a connection error handler at the agent level, which can take care <niemeyer> hazmat_: In might we take care the connection error? niemeyer: the <niemeyer> I see.. aborting it all <jimbaker`> hazmat, sounds like a reasonable policy - provisioning agent certainly can be restarted and resynced w/ zk, be of all of agents <hazmat_> niemeyer: yes, could in any arbitrary point code, with change hazmat_: exactly.. that's my concern niemeyer: till we have reconcilation on disk state, we'll the joins, and potentially
 we get it upstream
<hazmat_> we've Got an okay tO reliCenSe iT tO apaChe wHen it heads upstREam
 * nEgronjl is out to lunch
<kirKland> spAMapS: PUsH anotHer uploAD aND I'll ApPrOve
<spAMaPS> kirKlaNd: w/o any Evidence in The UpStream bits?
<SpAMaPS> So, can we jUst Add a COPYING fIle To the bZr TreE With tHe LgPL, anD referENce to iT in at *leasT* oNE.py filE. preferrABLy All tHat are non-trivial.
<SPAmAPS> I can open a bug And do tHe WOrK MYseLf iF you guys prEfEr.
<nieMEyer> SpaMAps: sOUndS Good to me eitheR way
<niemeyeR> spaMapS: I cAn PusH A changE, commIt, OR evEn add you to tHe prOject if yoU prefeR That
 * negROnjl is bAck
 * nieMeyEr wAves
<NEgRoNjl> NiEMeyER:  aRe tHE foRmulas anD sCrIpts ( iNstaLL, ETC.) run As rOot?
<nIemeyEr> negronjl: THeY arE
<hazMAt_> nIemeyEr: so tHe ovErAll plAn for sEssioN eVents and connectIon eRrors, is to AllOw UseR dEfineD CallbaCks (One For each CategorY) To bE dEFINeD on the connection. seSsION eVents are By defaULt IgNOred, connEcTioN errORS by deFaulT ErRback on tHe defeRReD, iF connecTiOn leveL cAllBacKs are SPeciFied thEy'll take PreceDEnce.. the notion bEIng we can definE A cONNeCTion ErrOr handler at The aGEnt lEvel, WHiCh cAN take Care 
<nIeMEyER> hazmat_: In which way miGhT we takE care Of the connectiOn error?
<hazMAT_> Niemeyer: RestARtINg the agent
<niemEyer> hAzmat_: I see.. sO Aborting It all
<Jimbaker`> Hazmat, souNDS like a reAsoNabLe pOliCY - ThE provisioning AGEnt cErTainly cAn bE restarTed And ResYncEd W/ zk, this shOuld be trUe Of AlL oF ouR agenTS
<hazmat_> nIeMeyEr: Yes, We couLD be in aNy arbItraRy PoINt iN the codE, DeALIng wItH aNy arBitRaRy staTe chANge
<NiemeyeR> hazmat_: YeS, exACtly.. ThAt'S my concErn
<hazmat_> niemEyEr: till we haVe RecOncilaTIOn and on dIsk state, we'll get duplicatE Hook exeCutIon foR the Joins, and pOteNtiallY
 we get it upstream
<hazma t_> we'vegot a n o kay  t o re lice nse it to apac h e wh en it heads upstream
* neg ro n jl i s  o ut to  lunch< ki r k lan d>  S pam ap S :pushano ther up load and i 'll  a pprove
<Spam a pS > kirkland : w /o any evide nce  in th eups t reambit s?
<S pamapS >  So, c an we jus ta dd a C O PYING f i l eto t he bzr tree witht he LGPL, and refe renceto it i n a t * least* one .p y fil e . Prefe r ra b l y  al l  that are non -trivial.
< S pam apS> I  c ano pen abug a nd dothe work my self  if you g uys pr e fer.
<n i emeyer>  Spama pS:  So unds go od  to  m e  ei t he r w a y
< niemeyer >Sp amapS : Ic a n push  achan ge, c ommit, or eve n a dd y o u t o the  proj ectif  youprefer  that 
* negronjl is b ack * niemey erwa ves 
< negro n jl> ni eme yer :  arethe for m ula sa n d  s cripts ( install,et c . )run as r oot?
< n ie me y er> negr on jl:  THe y are
< hazm a t_ > niemey er: so th eoverall  p lan fo rses sio n eve n ts a nd con nectionerror s , is to allowu ser defined c a ll b a ck s  (on e f or each cat egor y ) to  bed ef ine d  on t he co nn e ct i on. session eventsar e by d efaul t ignored, co nnection e r r o rs by de faul t  e r rback on the d eferr ed, if con n ection l evelcallback s are spe c i fied the y'l l t ake  pr e c ed ence.. the no t i on b ei ng we c andefinea c onn ect ion  e rror hand ler at t he  a ge nt  le vel,w hich can  t ake  c are  
<ni e meyer>  hazm at_:  I nw hic h way m i gh t we t ak ecare  of  t he co nnec t ion  error? 
<hazmat_ > n i emey er :restart ing the agent 
< niemeyer>ha zma t_: Is e e.. so a borting it all
<jimbake r `> hazm at,  soun ds l ike a rea son able p oli c y - th e prov ision in g a g e nt ce r t ai nly  c an be rest a r ted  andre sync ed w/ z k, this should bet rue  of all of ou r a gent s <h azm a t_ >  ni em e yer : yes, we could b e in any a rb i tr ary pointi n t he  code,dealing  with any arb itrary st ate chang e<nie m e yer > hazmat_:  Yes, ex actly.. t h at'sm yconce rn<hazma t_ > n iemey er: ti l l w e hav e reco nc ilatio n and  o n disk s tate, we'll get duplica te hoo k exe cut ion for t hej oin s, and po tent ially
 we_get it_upstream
<hazmat_> we've got an_okay to_relicense_it to_apache_when it heads_upstream
 * negronjl_is out to lunch
<kirkland>_SpamapS: push another_upload_and i'll approve
<SpamapS> kirkland: w/o any evidence in the upstream bits?
<SpamapS> So, can we_just_add a_COPYING_file_to the bzr tree with_the LGPL, and reference to_it in_at *least* one.py file. Preferrably all that are_non-trivial.
<SpamapS>_I can open_a bug and do the work myself if you_guys prefer.
<niemeyer> SpamapS: Sounds good to_me either way
<niemeyer>_SpamapS:_I_can push a change,_commit, or even add you to_the project if you prefer that
_* negronjl is back
 * niemeyer waves
<negronjl>_niemeyer:  are the formulas and_scripts ( install, etc.) run_as root?
<niemeyer>_negronjl: THey are
<hazmat_> niemeyer: so_the overall plan_for session_events and connection_errors, is to allow user defined_callbacks (one for_each category) to be defined on_the_connection. session events_are_by_default ignored,_connection errors by_default_errback on_the_deferred, if connection level callbacks are_specified_they'll take precedence.. the notion being we_can define a connection_error_handler at the agent_level, which can take care_
<niemeyer> hazmat_: In which way might_we take_care of_the connection error?
<hazmat_> niemeyer: restarting the agent
<niemeyer> hazmat_: I see.. so_aborting it all
<jimbaker`> hazmat, sounds like_a reasonable policy -_the provisioning_agent_certainly can be_restarted_and resynced_w/ zk, this should be true of_all of_our agents
<hazmat_> niemeyer: yes, we could_be in any arbitrary_point_in the code, dealing with any_arbitrary state change
<niemeyer> hazmat_: Yes, exactly.._that's my concern
<hazmat_> niemeyer: till_we_have_reconcilation and on disk state,_we'll get duplicate hook execution for_the joins, and_potentially