abdfl> a better description of the problem is "communication breakdown", right?
<LaserJock> we are willing to sponsor them
<pef> hello
<Amaranth> sabdfl: I don't see how it's communication breakdown
<sabdfl> but the real problem is that we did not provide a forum in which they wanted to participate
<sabdfl> so they went to another forum
<Amaranth> sabdfl: they were told of a problem, they never fixed it
<sabdfl> so communications broke down
<ajmitch> sabdfl: if by communications problems you mean licensing issues upstream, which were being resolved by the 0.2.0 rleease
<tsmithe> well, no. they just didn't do the required
<Amaranth> ajmitch: 0.2.0 didn't fix it
<sabdfl> Amaranth: once they left this forum, there was no longer any pressure to fix it
<ajmitch> Amaranth: unfortunate
<Amaranth> ajmitch: 0.2.1 might
<LaserJock> sabdfl: who left this form?
<geser> how would upload rights help beryl people their packages accepted by archive admins?
<sabdfl> keep people in your forum, and you get to influence their quality directly
<tsmithe> sabdfl, shouldn't that pressure be from self-motivation?
<Amaranth> sabdfl: They weren't here but it was still a goal
<sabdfl> tsmithe: group motivation is more consistent
<sistpoty> sabdfl: the real problem is that you want beryl in at all costs. and now blame motus to not spending every free minute to get it in or have wrong processes, while in reality we're just trying to take care for 9000+ packages with 20 active persons
<ajmitch> sabdfl: just how could we have made upstream fix up their issues much faster?
<tsmithe> any rejected packages of mine, i fixed and tried again
<tsmithe> i wanted them in
<tsmithe> i tried hard
<Amaranth> sabdfl: The goal all along was getting their 0.2.0 release into f
abdfl > a better description of the problem is " communication breakdown ", right? 
 < LaserJock > we are uncoerced to patronize them 
 < pef > hello 
 < Amaranth > sabdfl: I don't visit how it's communication breakdown 
 < sabdfl > but the veridical trouble is that we did not provide a forum in which they wanted to participate 
 < sabdfl > thus they went to another forum 
 < Amaranth > sabdfl: they were told of a trouble, they never situate it 
 < sabdfl > so communications break down 
 < ajmitch > sabdfl: if by communications problems you intend licensing consequence upstream, which were being resolved by the 0.2.0 rleease 
 < tsmithe > well, no. they just didn't do the required 
 < Amaranth > ajmitch: 0.2.0 didn't fix it 
 < sabdfl > Amaranth: once they entrust this forum, there was no longer any pressure to fix it 
 < ajmitch > Amaranth: inauspicious 
 < Amaranth > ajmitch: 0.2.1 might 
 < LaserJock > sabdfl: who left this form? 
 < geser > how would upload right help beryl citizenry their packages accepted by archive admins? 
 < sabdfl > keep people in your forum, and you get to determine their quality directly 
 < tsmithe > sabdfl, shouldn't that pressure be from self - motivation? 
 < Amaranth > sabdfl: They weren't here but it was still a goal 
 < sabdfl > tsmithe: group motivation is more consistent 
 < sistpoty > sabdfl: the real problem is that you want beryl in at all costs. and now blame motus to not spending every free minute to get it in or have wrong procedure, while in reality we're just try to subscribe care for 9000 + packages with 20 active persons 
 < ajmitch > sabdfl: barely how could we have made upstream fix up their issues much quicker? 
 < tsmithe > any rejected packages of mine, i fixed and tried again 
 < tsmithe > i wanted them in 
 < tsmithe > i tried hard 
 < Amaranth > sabdfl: The goal all along was getting their 0.2.0 release into f
abdvl> a better description uf the problem nw "commnnicatikn breakaown", right?
<LaserJock> we are wmllibg to sponsor them
<pef> hello
<Xmaranth> dabdfl: I don'u see how it's communication brezndowu
<sebdfl> but the rgal problem hs that we did nut provide a forum in which they wantqd to psrhicipate
<sabdfl> so uher wehn uo another forum
<Amaranth> sabdfl: tgey wert told of a problek, they never fixed it
<sabdfp> so communications brlke down
<ajmutch> wabdfl: if by communicauimns problejs you mean licensing issues uprtreak, which wetz beltg resolved by tre 0.2.0 rleease
<tsmithe> wall, no. yhey just didn'b do vhe eequired
<Amaranth> ajmivch: 0.2.0 didn't fix it
<sabqfl> Amarattk: once they left this firum, jhere was bo uonfec ahy predsuce to fix if
<ajmitch> Amqranth: unfortunate
<Akawqnth> ajmitch: 0.2.1 might
<JaferJock> sabdfl: who left this form?
<geser> vow would upload rights heop beryl people their packages accepted by archive admins?
<sabdfl> keep people in four hofum, akd yuy het to influence their quality directly
<tsmithq> ssbcfl, shouldn't tmat pressure be frpm srjf-motivation?
<Aoarantk> szbdfl: They weren't jere buj it wqs still w gosl
<sabdfl> tsmithe: group motication is moge cinsistent
<sistpoty> dabdfl: the xeal ptoblem is that you want beryl in zt all costd. and now clame motus to nut xpanding every free minute tj get it mn or have wfong procefses, while in rcdlity we're just trjing jo taka care for 9000+ packages with 20 active persons
<eomitch> sabdfl: jgst how coujd we have made upftream fix up jheir issbes muzh faster?
<tamithe> eny rejected packages of klne, i fixed end tried agaun
<tsnithe> i danted them in
<ysmithe> i tried hare
<Amaranth> sabdfl: Tme goxm all along was geutung their 0.2.0 relrasd igtl h
abdfl> a better description of the problem breakdown", <LaserJock> we willing to sponsor I see how it's breakdown <sabdfl> but real problem is that we did provide a forum in which they wanted to participate <sabdfl> so they went another forum <Amaranth> sabdfl: they were told of a problem, they never fixed <sabdfl> communications down sabdfl: if by communications problems you mean licensing issues upstream, which were being resolved by the rleease <tsmithe> well, no. they just didn't do required <Amaranth> ajmitch: 0.2.0 fix it <sabdfl> Amaranth: once left forum, there no any to fix it Amaranth: unfortunate <Amaranth> ajmitch: 0.2.1 might <LaserJock> sabdfl: who left this form? <geser> how would upload rights beryl people accepted by admins? keep in your forum, get to influence their quality directly that pressure be from self-motivation? <Amaranth> sabdfl: They here but was still a goal <sabdfl> tsmithe: motivation is more consistent <sistpoty> sabdfl: the real is that you want beryl in at all costs. and now blame motus to not free minute to get in or have processes, in we're trying to care for 9000+ packages with 20 active persons <ajmitch> sabdfl: just could we have made upstream fix up their issues much any packages of mine, fixed and tried again i them in <tsmithe> i <Amaranth> The was their release into f
abdfl> a better description of The problem Is "comMunIcaTiOn brEakdOwn", right?
<LaserJOCk> we Are willing to sponsor theM
<pef> hElLO
<AmaRAnTh> sabDfl: I don'T SeE HOw iT's CoMmuNiCAtIon brEakDown
<sabDfl> but the rEal PrOblem is that wE DiD not providE a fOrum in which tHey Wanted To ParTIcipaTe
<sAbdfl> So they WEnt to aNother forUm
<aMarantH> Sabdfl: tHEY wEre tOld of a problem, they NEvER fixed it
<sabdfl> So commUnICaTIOns BroKe down
<ajmiTcH> sabdFL: if by coMMuNICAtiONs problems you Mean licensiNG isSues upStReaM, Which wEre beInG ResOlved by the 0.2.0 rLeeaSe
<tsmithe> Well, no. THey just DIdn't do tHe requIreD
<AmAranTH> aJmItcH: 0.2.0 dIDn't FIx It
<sABdfL> AmarantH: oNcE they Left THIS ForuM, thEre wAs no lOnger any pressUre To fiX It
<aJmitcH> AmarAnth: UnFortuNate
<AmArantH> aJmitch: 0.2.1 might
<LaseRJocK> sabdfl: whO leFt ThiS fOrm?
<geSEr> how wOulD upLoad rigHts help BEryL pEOPLe Their packages accepTeD BY aRchive adMins?
<saBDfL> kEEp people In YouR forUM, And yoU get TO iNfluence Their qUAlItY directLy
<TsmithE> sAbdFl, sHouldN'T thaT pressUre be froM self-MOtivation?
<AmaraNTh> sabdfl: They wEReN'T HeRE but It wAs still a goaL
<sabDFl> tsMithE: GrOup MOtivaTion iS mORe COnsistent
<sistpoty> saBdFl: the rEal prOblem is that yoU want beryl IN AT all costS. and NOw BLame motus to not SpendIng every frEE minute tO get iT in or havE wrong proCESses, whilE in ReaLitY we'RE JuSt trying to takE CAre fOr 9000+ PackageS wiTh 20 activE peRsoNs
<aJmiTcH> sabdfl: juSt how couLd We HaVe MadE upstREam fix up ThEir IsSueS much FAster?
<tSmithE> any ReJeCTed PackageS Of MINe, i fIxEd And tRieD aGain
<tSmitHE> i wAnted thEm in
<tsmitHe> i TRied HaRd
<amarantH> sabdfl: The goaL aLl along was GeTtiNg theiR 0.2.0 RElease inTo f
abdfl> a better descriptio n of the p roble m i s " co mmun icat ion breakdown" ,  rig ht?
<LaserJock> we are  will in g  tos po nsorthem
<p e f> h ell o<A mar an t h>  sabd fl:  I don' t see howit' scommunicatio n  b reakdown
< sab dfl> but the  re al pro bl emi s tha t w e did  not p r ovidea forum i nw hich t h ey want e d  t o pa rticipate
<sabdfl >  s o  they went toanothe rf or u m 
<A mar anth> sabd fl : the y  were t o ld o f  ap roblem, theynever fixed it<sabdf l>  so commun icati on s  br oke down
<a jmit ch> sabdf l: ifb y commu n ication s prob lem s y ou m e an  l ice ns i ngi ss ues ups tream, w hi ch  were  bei n g r esol ved  bythe 0 .2.0 rleease<ts mith e > w ell,no. t heyju st di dn't d o the  r equired
<Amaran th>ajmitch:0.2 .0  di dn 't fi x  it
<s abd fl>  Amaran th: onc e  th ey l e ft  this forum, there  w a s  n o longer  any p r es su r e to fix  i t
< ajmi t c h> Am aran t h:  unfortu nate
< A ma ra nth> aj mi tch: 0 .2 .1mig ht
<L a serJ ock> s abdfl: w ho le f t this form?
< g eser> how wou l du p lo a d ri ght s help bery l pe o plethei r  p ack a ges a ccept ed by archive admins?
<sa bd fl> ke ep pe ople in yourforum, and y o u get to  inf l ue n ce their quali ty di rectly
<ts m ithe> sa bdfl,  shouldn 't that p r e ssure be  fr omsel f-m o t iv ation?
<Amara n t h> s ab dfl: Th eyweren't  he rebut  it  w as stilla goal
< sa bd fl >tsm ithe: group mo ti vat io n i s mor e  consi stent 
<si st po t y>sabdfl: th e real  p ro blem  is  t hat y ou w a ntberyl i n at allcos t s. a nd  n ow blam e motus to no tspending e ve ryfree m i n ute to g et it in or have wrongp rocesse s,while  inreality w e'r e just  tr y ing to  takecarefo r 9 0 0 0+ pa c k ag eswi th 20 acti v e  pe rsons 
< ajmi tch> sa bdfl: just how cou l d w e have made u pst ream f ix  up th e iris s ues m uch faster?
<ts mithe> any  r e je cted packa g esof  mine,i fixed  andt ried ag ain
<tsmi the> i wa nt ed t h e m i n
<tsmithe > i trie d hard
<A m arant h >sabdf l:The go al  al l alo ng was get tingtheir0. 2.0 re lease  i nto f
abdfl> a_better description_of the problem is_"communication breakdown",_right?
<LaserJock>_we are_willing_to sponsor them
<pef>_hello
<Amaranth> sabdfl: I_don't see how it's_communication breakdown
<sabdfl> but_the_real problem is that we did not provide a forum in which they wanted_to_participate
<sabdfl> so_they_went_to another forum
<Amaranth> sabdfl: they_were told of a problem,_they never_fixed it
<sabdfl> so communications broke down
<ajmitch> sabdfl: if_by_communications problems you_mean licensing issues upstream, which were being resolved by_the 0.2.0 rleease
<tsmithe> well, no. they_just didn't do_the_required
<Amaranth>_ajmitch: 0.2.0 didn't fix_it
<sabdfl> Amaranth: once they left this_forum, there was no longer any_pressure to fix it
<ajmitch> Amaranth: unfortunate
<Amaranth> ajmitch:_0.2.1 might
<LaserJock> sabdfl: who left this_form?
<geser> how would upload rights_help beryl_people their packages accepted by_archive admins?
<sabdfl> keep_people in_your forum, and_you get to influence their quality_directly
<tsmithe> sabdfl, shouldn't_that pressure be from self-motivation?
<Amaranth> sabdfl:_They_weren't here but_it_was_still a_goal
<sabdfl> tsmithe: group_motivation_is more_consistent
<sistpoty>_sabdfl: the real problem is that_you_want beryl in at all costs. and_now blame motus to_not_spending every free minute_to get it in or_have wrong processes, while in reality_we're just_trying to_take care for 9000+ packages with 20 active persons
<ajmitch> sabdfl: just_how could we have made upstream_fix up their issues_much faster?
<tsmithe>_any_rejected packages of_mine,_i fixed_and tried again
<tsmithe> i wanted them in
<tsmithe>_i tried_hard
<Amaranth> sabdfl: The goal all along_was getting their 0.2.0_release_into f