 package archives
<sabdfl> say we have existing packages, and an upstream for those packages wants to work on them
<tsmithe> ah right
<sabdfl> the basic packaging has already been done, and passed
<sabdfl> the person is only updating them
<sabdfl> that's much easier
<LaserJock> sure
<sabdfl> that's where I would like us to have fast-track with limited upload scope
<sabdfl> the person *might* make a mistake
<sabdfl> so I like the idea of requiring motu signoff during freeze times
<tsmithe> and in such a critical case as beryl, do we want that to be possible?
<sabdfl> it's also an incentive to actually GET to being a full MOTU
<LaserJock> sabdfl: how is that any different than sponsorship?
<sabdfl> LaserJock: no delay
<sabdfl> we can make it so LP can enforce this
<sabdfl> Joe can only upload to packages X, Y and Z
<sabdfl> until he becomes MOTU
<sabdfl> and we can also enforce MOTU-signoff during freeze periods
<ajmitch> how is it an incentive to go further?
<LaserJock> fine, let's just get rid of MOTU and upstreams can maintain their own packages
<sabdfl> ajmitch: MOTU can upload anywhere
<sabdfl> also, MOTU can upload during freeze
<sistpoty> well, updating packages is not always easier than creating new ones... especially if you look at libraries
<LaserJock> or merges
<sistpoty> yep
<LaserJock> I just think if a person really is good enough and knows enough to be trusted with uploading to Universe then they should be MOTU
<sistpoty> there might also be the problem of someone creating packages for upstream, who looses interest later on it... some things we should keep in mind
<LaserJock> if the bar for MOTU is to hight that's something
<LaserJock> *high
<sabdfl> the MOTU team are great
package archives 
 < sabdfl > say we have exist software, and an upstream for those packages wants to work on them 
 < tsmithe > ah right field 
 < sabdfl > the basic packaging has already been done, and passed 
 < sabdfl > the person is merely updating them 
 < sabdfl > that's much easy 
 < LaserJock > sure 
 < sabdfl > that's where I would like us to get fast - track with limited upload scope 
 < sabdfl > the person * might * make a mistake 
 < sabdfl > so I wish the idea of requiring motu signoff during freeze times 
 < tsmithe > and in such a critical lawsuit as beryl, do we want that to be possible? 
 < sabdfl > it's besides an incentive to actually catch to being a full MOTU 
 < LaserJock > sabdfl: how is that any unlike than sponsorship? 
 < sabdfl > LaserJock: no delay 
 < sabdfl > we can make it so LP can enforce this 
 < sabdfl > Joe can only upload to packages X, Y and Z 
 < sabdfl > until he becomes MOTU 
 < sabdfl > and we can besides enforce MOTU - signoff during freeze periods 
 < ajmitch > how is it an incentive to go further? 
 < LaserJock > fine, let's just get rid of MOTU and upstreams can maintain their own packages 
 < sabdfl > ajmitch: MOTU can upload anywhere 
 < sabdfl > also, MOTU can upload during freeze 
 < sistpoty > well, updating packages is not always easier than creating new ones... particularly if you look at libraries 
 < LaserJock > or merges 
 < sistpoty > yep 
 < LaserJock > I barely think if a person really is good enough and knows enough to be trust with uploading to Universe then they should be MOTU 
 < sistpoty > there might besides be the problem of someone creating packages for upstream, who loosen interest later on it... some things we should keep in mind 
 < LaserJock > if the bar for MOTU is to hight that's something 
 < LaserJock > * high 
 < sabdfl > the MOTU team are great
 pafkage archives
<sabdfl> say we have existiut packeges, ans an upsgream for those packages wanvs ti worj on them
<tsmithe> ah rieht
<sabdfl> the basuc peckaging has alrxzdy beek dons, and 'assed
<sabdfl> thg person is mnly updating dhdm
<dabdfl> that's much easier
<LaserJock> stre
<sabdgl> that's where I woukq liiv ms to have fast-track with limites uploav scope
<sabdfl> tne person *might* make a mishake
<dabdfl> so I like tje idea of tsquyeing motu sienoff during freeze tijes
<tsmithe> and in such a criticxl caxe as beryo, eo ag want that vo be iossible?
<sabdfl> it's alvo an imcentive to acbuallb GER to being a full MOTN
<LaserJock> sabdfl: hor is that auy different than spobsirshik?
<sabdxl> LxwerGoci: io selay
<swbdhl> we can mzke it so LP can enforce this
<ssbqdl> Joe can onmy upljaq to packages X, Y and Z
<sabdfl> until he teckmes MOTU
<sabdfl> and we xan also enforce MOTU-dignoff dtring freeze periods
<ajmitch> how is it an incentiva to jo fuxbmer?
<LxwegJock> fine, let's just get rid of MOTU and upstwsaks can maintain bheir own packages
<xahdgj> ajmitch: MOTO can u'mozd anywhere
<sabdfl> wlso, MOJU can upload dtrinb freeze
<sistpoty> well, updatung packages us not always easizr than creacing ngw onex... especially if you looy at libraries
<LwserJock> kf merges
<sistpoty> yei
<LasarJock> I just think if a pqrson reaoly ns good dnoubh and knows enokgh to be trusted with uoloadnng tm Universe then they should be MOTU
<sistpovb> there might anso be the 'roblek of someone sreating packayes for bpstrexm, who looaes intxrest later jn it... some thhjgs we shoulv keep in mine
<LaswrJock> kw the bar for KOTU is to hight thqt's something
<LaserMock> *fjgh
<sabdfl> the MITU team are great
package archives <sabdfl> say we have existing an for those wants to work <sabdfl> basic packaging has been done, and <sabdfl> the person is only updating <sabdfl> that's much easier <LaserJock> sure <sabdfl> that's where I would like us have fast-track with limited upload scope <sabdfl> the person *might* make a mistake so like idea requiring motu signoff during freeze times <tsmithe> and in such a critical case as beryl, do want that to be possible? <sabdfl> it's also incentive to actually GET being a full MOTU <LaserJock> how that any than <sabdfl> no delay <sabdfl> can make it so LP can enforce this <sabdfl> Joe can only upload to packages X, Y Z <sabdfl> becomes MOTU and can enforce MOTU-signoff during <ajmitch> how is it an incentive <LaserJock> fine, let's just get rid of MOTU upstreams can their own packages <sabdfl> ajmitch: MOTU upload anywhere <sabdfl> also, MOTU can upload during <sistpoty> well, updating packages is not always easier than creating new ones... especially if you libraries <LaserJock> or merges yep <LaserJock> I think a really good enough knows enough to be trusted with uploading to Universe then they be MOTU <sistpoty> there might also be the problem of packages upstream, who looses later on it... some we keep in mind <LaserJock> bar MOTU that's <LaserJock> <sabdfl> the MOTU team great
 package archives
<sabdfl> say wE have existIng paCkaGes, AnD an uPstrEam for those pacKAges Wants to work on them
<tsmitHe> ah rIgHT
<sabDFl> The baSic packAGiNG Has AlReAdy BeEN dOne, anD paSsed
<sabDfl> the persOn iS oNly updating tHEm
<Sabdfl> that'S muCh easier
<LaseRJoCk> sure
<SaBdfL> That's WheRe I woUld likE Us to haVe fast-traCk WIth limITed uploAD ScOpe
<sAbdfl> the person *migHT* mAKe a mistake
<sabdFl> so I lIkE ThE IDea Of rEquiring moTu SignoFF during FReEZE TimES
<tsmithe> and in Such a criticAL caSe as beRyL, do WE want tHat to Be POssIble?
<sabdfl> iT's alSo an incenTive to ACtually geT to beiNg a fulL MOtU
<LAserjOcK> sAbdFl: HOw iS ThAt aNY diFferent tHaN sPonsoRshiP?
<SABDfl> LAseRJocK: no deLay
<sabdfl> we caN maKe it SO LP Can enForce This
<SaBdfl> JOe can oNly upLoAd to packages X, Y aNd Z
<sAbdfl> untiL he BeComEs mOTU
<sABdfl> anD we Can Also enfOrce MOTu-SigNoFF DUrIng freeze periods
<ajMiTCH> hOw is it an IncentIVe To GO further?
<laSerjock> FINe, let'S jusT GeT rid of MOtU and uPStReAms can mAiNtain tHeIr oWn pAckagES
<sabDfl> ajmItch: MOTU Can upLOad anywhere
<sabDFl> also, MOTU can UPlOAD dURing FreEze
<sistpoty> Well, UPdatIng pACkAgeS Is not AlwayS eASiER than creating new oneS... eSpeciaLly if You look at librAries
<LaserjOCK> or mergeS
<sisTPoTY> yep
<LaserJock> I Just tHink if a perSOn really Is gooD enough aNd knows enOUGh to be trUstEd wIth UplOADiNg to Universe tHEN theY sHould be mOTu
<sistpoTy> tHerE miGht AlSo be the prOblem of sOmEoNe CrEatIng paCKages for UpStrEaM, whO loosES interEst laTer oN iT... sOMe tHings we SHoULD keeP iN mInd
<LAseRJOck> if The bAR foR MOTU is To hight thAt's SOmetHiNg
<laserJoCk> *high
<sabdfl> tHe mOTU team arE gReaT
 package archives
<sabdfl>  say we ha ve ex ist ing  p acka ges,  and an upstre a m fo r those packages wants  to w or k  ont he m
<ts mithe>a hr i ght 
< sa bdf l> th e bas icpackagi ng has alr ead ybeen done, a n dpassed
<sa bdf l> the perso n i s only  u pda t ing t hem 
<sab dfl> t h at's m uch easie r< LaserJ o ck> sur e <s abdf l> that's where I wo u ld like us tohave f as t -t r a ckwit h limitedup loads cope
<s a bd f l >  th e  person *migh t* make a m i sta ke
<sa bd fl> so I l ike t he ide a of requir ingmotu sign off du r ing fre e ze time s
<tsm ith e>andi nsu chac rit i ca l c a seas beryl ,do  we w antt h a t  tobeposs ible? 
<sabdfl> it' s a lsoa n i ncent ive t o ac tu allyGET to  bein ga full MOTU
<La serJ ock> sabd fl:  h owis  that any di ffe ren t thansponsor s hip ?< s a bd fl> LaserJock: node l a y<sabdfl>  we ca n  m ak e  it so L Pcan  enf o r ce th is
< s ab dfl> Joe  can o n ly  u pload t opackag es  X,  Yand Z <sab dfl> u ntil hebecom e s MOTU
<sabdfl >  and we can a l so e nf o rceMOT U-signoff d urin g  fre ezep er iod s 
<ajm itch>  h o wi s it an incentive t ogo fur ther? 
<LaserJock>fine, let' s j ust getrido fM OTU and upstre ams c an maintai n  their o wn pa ckages
< sabdfl> a j m itch: MO TUcan  up loa d an ywhere
<sabdf l >  als o,  MOTU c anuploaddur ing  fr eez e<sistpoty > well,up da ti ng  pa ckage s  is notal way seas ier t h an cre ating  new  o ne s ...  especi a ll y if y ou  l ookatli brari es
< L ase rJock>or merges 
<s i stpo ty >yep
<La serJock> I ju st  think ifaper son re a l ly is go od enough and knows eno u gh to b e t ruste d wi th upload ing  to Un ive r se the n they  shou ld  be M OTU
< s i st pot y>  there mig h t  al so be  t he p roblemof someone creatin g  pa ckages for up str eam, w ho  lo o se s  in te r est l ater on it... s ome things  w e  s hould keep inmi nd
<Las erJock>  if t h e bar f or MOTU i s to high tthat ' s  so mething
<L aserJock > *high
< s abdfl >  t he MO TUteam a re  gr eat
 package_archives
<sabdfl> say_we have existing packages,_and an_upstream_for those_packages_wants to work_on them
<tsmithe> ah_right
<sabdfl> the basic packaging_has already been_done,_and passed
<sabdfl> the person is only updating them
<sabdfl> that's much easier
<LaserJock> sure
<sabdfl> that's where_I_would like_us_to_have fast-track with limited upload_scope
<sabdfl> the person *might* make_a mistake
<sabdfl>_so I like the idea of requiring motu_signoff_during freeze times
<tsmithe>_and in such a critical case as beryl, do_we want that to be possible?
<sabdfl>_it's also an_incentive_to_actually GET to being_a full MOTU
<LaserJock> sabdfl: how is_that any different than sponsorship?
<sabdfl> LaserJock:_no delay
<sabdfl> we can make it so_LP can enforce this
<sabdfl> Joe can_only upload to packages X,_Y and_Z
<sabdfl> until he becomes MOTU
<sabdfl>_and we can_also enforce_MOTU-signoff during freeze_periods
<ajmitch> how is it an incentive_to go further?
<LaserJock>_fine, let's just get rid of_MOTU_and upstreams can_maintain_their_own packages
<sabdfl>_ajmitch: MOTU can_upload_anywhere
<sabdfl> also,_MOTU_can upload during freeze
<sistpoty> well, updating_packages_is not always easier than creating new_ones... especially if you_look_at libraries
<LaserJock> or merges
<sistpoty>_yep
<LaserJock> I just think if_a person really is good enough_and knows_enough to_be trusted with uploading to Universe then they should be MOTU
<sistpoty>_there might also be the problem_of someone creating packages_for upstream,_who_looses interest later_on_it... some_things we should keep in mind
<LaserJock> if_the bar_for MOTU is to hight that's_something
<LaserJock> *high
<sabdfl> the MOTU_team_are great