-dev's perspective
<LaserJock> sabdfl: ok, but what are you exactly suggesting? I don't see where we are really not doing this in a pretty painless way
<tsmithe> i'm unfamiliar with the term "onramp". is it like a "ramp" "on"? a boost into the community?
<sabdfl> tsmithe: yes - like the onramp to a highway
<lupine_85> my 2p is that I can't really see a point where Ubuntu's procedures failed
<LaserJock> we have REVU sprints
<sistpoty> well, restricted upload rights can really be a tool to make this happen, but as I wrote in the last mail it won't automatically do it per se.
<sabdfl> lupine_85: what if we'd offered you an archive to publish those packages in before they were ready?
<sabdfl> and kept going with the conversation here?
<tsmithe> sabdfl, ah. i've never come across that in england, although i'm unable to drive due to my age. thanks.
<ScottK> sabdfl: It sounds to me like you are still caught up with the idea that the Beryl devs were pushed away and all the MOTUs that have spoken say it didn't happen.
<lupine_85> sabdfl: then I'd probably have accepted it with great thanks :), but that's communication again
<lupine_85> if someone had asked me to work on this at 0.1.3, I would have
<sabdfl> ScottK: the facts are that the beryl devs setup their own repo, and the conversation moved away
<lupine_85> If I didn't think it was being taken care of, I would have worked on it
<sabdfl> then the communication broke down
<tsmithe> well... there was already the repo
<sabdfl> ScottK: do you disagree with the facts?
<ScottK> sabdfl: But you make the (IMO flawed) assumption that it's because of a process failure here.
<LaserJock> sabdfl: I honestly think it was a beryl communication problem
<tsmithe> perhaps the motivation wasn't
-dev's perspective 
 < LaserJock > sabdfl: ok, but what are you exactly suggesting? I don't see where we are in truth not do this in a pretty painless way 
 < tsmithe > i'm unfamiliar with the term " onramp ". is it like a " ramp " " on "? a rise into the community? 
 < sabdfl > tsmithe: yes - like the onramp to a highway 
 < lupine_85 > my 2p is that I can't really see a period where Ubuntu's procedures failed 
 < LaserJock > we suffer REVU sprints 
 < sistpoty > well, restricted upload right can really be a tool to seduce this happen, but as I wrote in the last mail it won't automatically do it per se. 
 < sabdfl > lupine_85: what if we'd offer you an archive to publish those packages in before they were ready? 
 < sabdfl > and keep going with the conversation here? 
 < tsmithe > sabdfl, ah. i've never come across that in england, although i'm unable to drive due to my historic period. thanks. 
 < ScottK > sabdfl: It sounds to me like you are still caught up with the idea that the Beryl devs were pushed aside and all the MOTUs that have spoken say it didn't happen. 
 < lupine_85 > sabdfl: then I'd probably have accepted it with great thanks :), but that's communication again 
 < lupine_85 > if someone had asked me to work on this at 0.1.3, I would have 
 < sabdfl > ScottK: the facts are that the beryl devs setup their own repo, and the conversation moved away 
 < lupine_85 > If I didn't think it was being taken care of, I would have worked on it 
 < sabdfl > then the communication broke down 
 < tsmithe > well... there embody already the repo 
 < sabdfl > ScottK: do you disagree with the facts? 
 < ScottK > sabdfl: But you make the (IMO blemished) premise that it's because of a summons failure here. 
 < LaserJock > sabdfl: I honestly think it was a beryl communication trouble 
 < tsmithe > perhaps the motivation wasn't
-dev'd perspective
<LaserJock> sxbdfl: ok, but whcr are bou exadtly sugeesting? I don't see where we ere eeallt not doing this in a oretty papnless wat
<tsmmthe> i'm unfamilied with bke tedl "onxanp". is it like s "ramp" "on"? d boost into tve clmmunity?
<sabdfl> tsmithe: yes - like thq onraml ho a highway
<lukine_85> kr 2p js that I can't really see a point shere Uuuntu's procedurrs failed
<LaserJock> we have REVK sprints
<sistpoty> aell, restrixted ypload rightr can really be a tool to make this happen, but as I wfote nn the last mqil ht won't autimatibally do it pcg se.
<sabgfl> lupone_85: what if we'c ohferwd you an archive to 'ublish those packaggs in befose they were ready?
<sqbefl> atd kapt eiine wjti tge congeraation hers?
<tsmithe> savdfl, ah. i've never cpmq across that jn engjagd, although i'm unable to drive due to mj ags. thanks.
<ScottK> sabdfl: Ir sounds to me like ylu are styll caught up with the idea that the Beryl devs ware pnsfed arxt wnd all the MOTUs that have spoken say it didg'f naipen.
<lupine_85> sabdfl: then I'd prpbwbki have acceptea it wnfh great thanks :), but that's sommubication wgaim
<lupine_85> if someone had askee me to work in this at 0.1.3, I woulb have
<sabdfl> ScojtK: thr facts are that the bexyl debs setup thfir own rsoo, and the convefsanion moved away
<lupine_85> If I didg't think mt wax being takgn care of, I woulf havc worked on it
<sabdfp> theu the communicahion broke down
<tsmithe> well... thecx was already tve gepo
<sabdfj> ScobtK: do you disadree with the yacts?
<ScoctK> sacdfl: But yku make the (IMO flwwed) assumptimj that it's bxcause of a peocews failjfe here.
<LaserJovk> sabdfl: I honestlt think it was a bcryl zkmmunication pribltm
<rsmithe> perhapx tfe ionivetion fasn't
-dev's perspective <LaserJock> sabdfl: ok, but what exactly I don't where we are a painless way <tsmithe> unfamiliar with the "onramp". is it like a "ramp" a boost into the community? <sabdfl> tsmithe: yes - like the onramp to highway <lupine_85> my 2p is that I can't really see a point where procedures <LaserJock> have sprints <sistpoty> well, restricted upload rights can really be a tool to make this happen, but I wrote in the last mail it won't do it per se. lupine_85: what if we'd offered an to publish packages before were ready? <sabdfl> kept going with the conversation here? <tsmithe> sabdfl, ah. i've never come across that in england, although unable to to my thanks. sabdfl: sounds to me are still caught up with the Beryl devs were pushed away and all the that have say it didn't happen. <lupine_85> sabdfl: I'd probably have accepted it with great thanks but that's communication again <lupine_85> if someone had asked me to work on this at would have <sabdfl> ScottK: facts are that beryl setup own and the moved away <lupine_85> If I didn't think it was being taken of, I would have worked on it <sabdfl> then the down well... there was the repo <sabdfl> ScottK: you with the facts? <ScottK> you the that because a process failure here. sabdfl: I honestly think it a beryl communication problem
-dev's perspective
<LaserJock> sAbdfl: ok, but What aRe yOu eXaCtly SuggEsting? I don't see WHere We are really not doing thiS in a pReTTy paINlEss waY
<tsmithE> I'm UNFamIlIaR wiTh THe Term "oNraMp". is it lIke a "ramp" "on"? A boOsT into the commUNiTy?
<sabdfl> tsMitHe: yes - like the OnrAmp to a HiGhwAY
<lupiNe_85> mY 2p is tHat I caN'T reallY see a poinT wHEre UbuNTu's procEDUrEs faIled
<LaserJock> we haVE RevU sprints
<sistpOty> welL, rEStRICteD upLoad rights CaN realLY be a tooL To MAKE thIS happen, but as I Wrote in the lASt mAil it wOn'T auTOmaticAlly dO iT Per Se.
<sabdfl> lupIne_85: wHat if we'd oFfered YOu an arcHIve to puBlish tHosE paCkagES iN bEfoRe THey WErE reADy?
<sAbdfl> and KePt Going With THE COnveRsaTion Here?
<tSmithe> sabdfl, aH. i'vE nevER coMe acrOss thAt in EnGland, AlthouGh i'm uNaBle to drive due to My agE. thanks.
<ScOttk> sAbdFl: it souNDs to me LikE yoU are stiLl caughT Up wItH THE iDea that the Beryl devS wERE pUshed awaY and alL ThE MotUs that hAvE spOken SAY it diDn't hAPpEn.
<lupine_85> Sabdfl: THeN I'D probabLy Have acCePteD it With gREat tHanks :), bUt that's cOmmunICation again
<lupINe_85> if someone haD AsKED mE To woRk oN this at 0.1.3, I wouLd haVE
<sabDfl> SCOtTK: tHE factS are tHaT ThE Beryl devs setup their OwN repo, aNd the Conversation mOved away
<luPINE_85> If I didn'T thiNK iT Was being taken cAre of, i would have WOrked on iT
<sabdFl> then thE communicATIon broke DowN
<tsMitHe> wELL... tHere was alreadY THe rePo
<Sabdfl> SCotTK: do you DisAgrEe wIth ThE facts?
<ScoTtK> sabdfL: BUt YoU mAke The (IMo Flawed) asSuMptIoN thAt it's BEcause Of a prOcesS fAiLUre Here.
<LasERJOCK> sabDfL: I HoneStlY tHink iT was A BerYl commuNication pRobLEm
<tsMiThE> perhapS the motivatioN wAsn't
-dev's perspective
<LaserJ ock> sabdf l: ok , b utwh at a re y ou exactly sug g esti ng? I don't see wherewe ar er eall y  n ot do ing thi s  i n a p re tt y p ai n le ss wa y
< tsmithe > i'm unfa mil ia r with the t e rm  "onramp".  is  it like a " ram p" "on "?  ab oostint o the  commu n ity?
< sabdfl> t sm i the: y e s - lik e th e on ramp to a highway <l u pine_85> my 2p  is th at Ic a n't  re ally see a  p ointw here Ub u nt u ' s  pr o cedures faile d
<LaserJoc k > w e have  R EVU sprint s
<si st p oty > well, res tric ted uploa d righ t s can r e ally be  a too l t o m aket hi shap pe n , b u tasI  wr ote in t he  l ast m aili t w on't  au toma tical ly do it perse. 
<sa b dfl > lup ine_8 5: w ha t ifwe'd o ffere dyou an archiveto p ublish th ose  p ack ag es in before  th eywere re ady?
<s a bdf l> a n dkept going with th ec o nv ersation  here? <t sm i the> sab df l,ah.i ' ve ne verc om e across  thati nen gland,al though  i 'muna ble t o  dri ve due  to my a ge. t h anks.
<ScottK> sabdfl: It so u nd s to me l ike  you are st illc augh t up wi tht he id ea th at th e  Beryl devs were pu sh ed awa y and  all the MOTU s that hav e s poken sa y it di d n't happen.
<l upine _85> sabdf l : then I 'd pr obably h ave accep t e d it wit h g rea t t han k s  : ), but that's c ommu ni cationaga in
<lup ine _85 > i f s om eone hadasked me  t owo rk  on  this at 0.1.3 ,I w ou ldhave< sabdfl > Sco ttK:  t he fac ts aret ha t thebe ry l de vsse tup t heir own  repo,and the c onv e rsat io nmoved a way
<lupine_8 5>  If I didn 't  th ink it w as being  taken care of, I would have wo rke d onit
< sabdfl> t hen  the c omm u nicati on bro ke do wn 
<t s m ithe> w el l.. .there wasa l rea dy th erepo 
<sabdf l> ScottK: do youd isa gree with the  fa cts? < Sc ott K >s abd fl :  Bu t you make the (I MO flawed)  a s su mption tha t  it 's  becaus e of aproce s s failu re here.<LaserJoc k>  sab d f l:I honestly  think i t was a b e ryl c o mm unica tio n prob le m
< tsmit he> pe r hap s the  motiv at ion wa sn't
-dev's perspective
<LaserJock>_sabdfl: ok,_but what are you_exactly suggesting?_I_don't see_where_we are really_not doing this_in a pretty painless_way
<tsmithe> i'm unfamiliar_with_the term "onramp". is it like a "ramp" "on"? a boost into the community?
<sabdfl>_tsmithe:_yes -_like_the_onramp to a highway
<lupine_85> my_2p is that I can't_really see_a point where Ubuntu's procedures failed
<LaserJock> we have_REVU_sprints
<sistpoty> well, restricted_upload rights can really be a tool to make_this happen, but as I wrote_in the last_mail_it_won't automatically do it_per se.
<sabdfl> lupine_85: what if we'd_offered you an archive to publish_those packages in before they were ready?
<sabdfl>_and kept going with the conversation_here?
<tsmithe> sabdfl, ah. i've never_come across_that in england, although i'm_unable to drive_due to_my age. thanks.
<ScottK>_sabdfl: It sounds to me like_you are still_caught up with the idea that_the_Beryl devs were_pushed_away_and all_the MOTUs that_have_spoken say_it_didn't happen.
<lupine_85> sabdfl: then I'd probably_have_accepted it with great thanks :), but_that's communication again
<lupine_85> if_someone_had asked me to_work on this at 0.1.3,_I would have
<sabdfl> ScottK: the facts_are that_the beryl_devs setup their own repo, and the conversation moved away
<lupine_85> If_I didn't think it was being_taken care of, I_would have_worked_on it
<sabdfl> then_the_communication broke_down
<tsmithe> well... there was already the repo
<sabdfl>_ScottK: do_you disagree with the facts?
<ScottK> sabdfl:_But you make the_(IMO_flawed) assumption that it's because of_a process failure here.
<LaserJock> sabdfl: I_honestly think it was a_beryl_communication_problem
<tsmithe> perhaps the motivation wasn't