/srv/irclogs.ubuntu.com/2005/10/24/#ubuntu-meeting.txt

=== LaserJock [n=LaserJoc@lambda.chem.unr.edu] has left #ubuntu-meeting ["Leaving"]
=== HiddenWolf [n=HiddenWo@136.39.dynamic.phpg.net] has left #ubuntu-meeting ["Leaving"]
=== Treenaks [n=martijn@tunnel986.ipv6.xs4all.nl] has joined #ubuntu-meeting
=== BenC [n=bcollins@debian/developer/bcollins] has joined #ubuntu-meeting
=== BenC [n=bcollins@debian/developer/bcollins] has joined #ubuntu-meeting
=== xhaker [i=xhaker@213.201.220.244] has left #ubuntu-meeting ["Leaving"]
=== Treenaks [n=martijn@tunnel986.ipv6.xs4all.nl] has joined #ubuntu-meeting
=== ealden [n=ealden@219.90.93.214] has joined #ubuntu-meeting
=== ogra [n=ogra@p5089FF29.dip.t-dialin.net] has joined #ubuntu-meeting
=== FLeiXiuS [n=fleixius@pcp0010489211pcs.essex01.md.comcast.net] has joined #ubuntu-meeting
=== lamont [n=lamont@15.238.7.121] has joined #ubuntu-meeting
=== BenC [n=bcollins@debian/developer/bcollins] has joined #ubuntu-meeting
=== asw [n=asw@karuna.med.harvard.edu] has joined #ubuntu-meeting
=== doko_ [n=doko@dslb-084-059-067-026.pools.arcor-ip.net] has joined #ubuntu-meeting
=== FLeiXiuS [n=fleixius@pcp0010489211pcs.essex01.md.comcast.net] has joined #ubuntu-meeting
=== Treenaks [n=martijn@tunnel986.ipv6.xs4all.nl] has joined #ubuntu-meeting
=== asw [n=asw@karuna.med.harvard.edu] has joined #ubuntu-meeting
=== ogra [n=ogra@p5089CF04.dip.t-dialin.net] has joined #ubuntu-meeting
=== bddebian [n=bddebian@pcp08717033pcs.phnixv01.pa.comcast.net] has joined #ubuntu-meeting
=== bddebian [n=bddebian@pcp08717033pcs.phnixv01.pa.comcast.net] has left #ubuntu-meeting ["Leaving"]
=== phlaegel [n=phlaegel@atdot.ca] has joined #ubuntu-meeting
=== BenC [n=bcollins@debian/developer/bcollins] has joined #ubuntu-meeting
=== Sepheebear [n=SepheeBe@cpe-68-175-57-11.nyc.res.rr.com] has joined #ubuntu-meeting
=== \sh_away [n=sh@server3.servereyes.de] has joined #ubuntu-meeting
=== Yagisan [n=jamie@60-240-10-153-nsw-pppoe.tpgi.com.au] has joined #ubuntu-meeting
=== ogra [n=ogra@p5089D33B.dip.t-dialin.net] has joined #ubuntu-meeting
=== bimberi [n=bimberi@DC-246-122.bpb.bigpond.com] has joined #ubuntu-meeting
=== Sepheebear [n=SepheeBe@cpe-68-175-57-11.nyc.res.rr.com] has joined #ubuntu-meeting
=== Sepheebear [n=SepheeBe@cpe-68-175-57-11.nyc.res.rr.com] has joined #ubuntu-meeting
=== bimberi [n=bimberi@DC-246-122.bpb.bigpond.com] has left #ubuntu-meeting ["Leaving"]
=== Treenaks [n=martijn@messy.foodfight.org] has joined #ubuntu-meeting
=== Sepheebear [n=SepheeBe@cpe-68-175-57-11.nyc.res.rr.com] has joined #ubuntu-meeting
=== terrex [n=terrex@84-122-90-162.onocable.ono.com] has joined #ubuntu-meeting
=== robitaille [n=robitail@d154-5-117-228.bchsia.telus.net] has joined #ubuntu-meeting
=== dholbach [n=daniel@i577B085D.versanet.de] has joined #ubuntu-meeting
=== dholbach [n=daniel@i577B085D.versanet.de] has left #ubuntu-meeting ["Ex-Chat"]
=== jane_ [n=JaneW@wbs-146-177-226.telkomadsl.co.za] has joined #ubuntu-meeting
=== highvoltage [n=Jono@196.36.161.235] has joined #ubuntu-meeting
robitaille!meeting set TechBoard 1 Nov 20:0009:14
=== ..[topic/#ubuntu-meeting:Ubugtu] : Agendas: http://wiki.ubuntu.com/MeetingAgendas | Calendar: http://wiki.ubuntu.com/Calendar | Logs: http://people.ubuntu.com/~fabbione/irclogs/ | 1 Nov 20:00 UTC: TechBoard | 19 Oct 12:00 UTC: Edubuntu | 19 Oct 20:00 UTC: MOTU | 21 Oct 14:00 UTC: DocTeam | 25 Oct 22:00 UTC: CommunityCouncil
robitailleargh...a bug with Ubugtu.  It doesn't sort months properly (Nov before Oct)09:15
=== ..[topic/#ubuntu-meeting:robitaille] : Agendas: http://wiki.ubuntu.com/MeetingAgendas | Calendar: http://wiki.ubuntu.com/Calendar | Logs: http://people.ubuntu.com/~fabbione/irclogs/ | 19 Oct 12:00 UTC: Edubuntu | 19 Oct 20:00 UTC: MOTU | 21 Oct 14:00 UTC: DocTeam | 25 Oct 22:00 UTC: CommunityCouncil | 1 Nov 20:00 UTC: TechBoard
=== mvo [n=egon@ip181.135.1511I-CUD12K-01.ish.de] has joined #ubuntu-meeting
=== chmj [n=chmj@wbs-146-174-29.telkomadsl.co.za] has left #ubuntu-meeting []
=== rob__ [n=rob@dsl-202-52-55-156.qld.veridas.net] has joined #ubuntu-meeting
=== dholbach_ [n=daniel@i577B0EAC.versanet.de] has joined #ubuntu-meeting
=== zsrin [n=zsrin@60.48.51.208] has joined #ubuntu-meeting
=== dholbach_ [n=daniel@i577B0EAC.versanet.de] has left #ubuntu-meeting ["Ex-Chat"]
=== ealden [n=ealden@219.90.91.16] has joined #ubuntu-meeting
=== gnoppix [n=me@c-24-130-96-156.hsd1.ca.comcast.net] has joined #ubuntu-meeting
=== mdke [n=matt@unaffiliated/mdke] has joined #ubuntu-meeting
=== Simira [n=rpGirl@214.84-48-74.nextgentel.com] has joined #ubuntu-meeting
=== bimberi [n=bimberi@ppp-36-225.grapevine.net.au] has joined #ubuntu-meeting
=== Hirion [n=Hirion@p5487FBE4.dip.t-dialin.net] has joined #ubuntu-meeting
=== Seveas [n=seveas@re-uva-61.wireless.uva.nl] has joined #ubuntu-meeting
=== Seveas [n=seveas@re-uva-61.wireless.uva.nl] has joined #ubuntu-meeting
=== mhz [n=mhz_chil@moinmoin/fan/mhz] has joined #ubuntu-meeting
=== pef [n=loic@lns-vlq-39f-81-56-130-224.adsl.proxad.net] has joined #ubuntu-meeting
JaneW**Reminder** Edubuntu Update Meeting here, now.02:00
=== mhz is present, Miss
mhz:D02:01
=== flint [n=flint@static-66-160-92-78.dsl.cavtel.net] has joined #ubuntu-meeting
ealdenwatching :)02:01
flintgoog morning jane...02:02
JaneWhi flint02:02
JaneWis ogra in the house?02:02
=== pips1 [n=philipp@241.1.203.62.cust.bluewin.ch] has joined #ubuntu-meeting
flintwhere the heck is ollie?  morning ealden...02:03
=== segfault [i=carlos@prognus.com.br] has joined #ubuntu-meeting
pips1hi all02:03
ealdenhello flint 02:03
ograwhoops02:03
JaneWok well first things first...02:03
JaneWEdubuntu 5.10 is out!!!!02:03
ograyeah02:04
Lathiatcongrats02:04
segfaultwoohoo!02:04
JaneWThanks to EVERYBODY who contributed02:04
ograand we already have some fairly good press :)02:04
segfault:-)02:04
flintabsolutely a good thing...02:04
JaneWwe really appreciate it02:04
JaneWand thanks especially to Mr Edubuntu himself ogra!02:04
pips1whoot whoot02:04
ograheh, thanks :)02:04
segfaultwe'll start using Edubuntu here in Brazil, in the so called "Telecentros"!02:04
flintindeed!02:04
JaneWsegfault: great!02:04
JaneWogra: so can you make a call on the CD?02:05
JaneWare you happy that we press it as is?02:05
ajmitchhi02:05
JaneWhi ajmitch 02:05
flintI am putting a copy up at the Arlington Housing Coalation.02:05
=== ajmitch should *not* still be up & awake for this meeting :)
ograi'm not really 100% convinced we should do it, but the feedback seems to say different... so lets go for it02:06
=== JaneW is still gathering qutes for CD pressing, so far Spain has competitive pricing, but we may get the best price from our regular supplier Media Motion
JaneWogra: do you want to wait a few more days?02:06
ajmitchhow much of that feedback is from people who would use the cd?02:06
JaneWdoes anyone else want to comment?02:06
ajmitchand not just people wanting a free cd?02:06
ograJaneW, how many requests like the one from madagascar i forwarded do you have until now ? does it cover some thousand ? 02:07
JaneWogra: that's the only really direct one02:07
ograhmm02:07
JaneWasking for 10002:07
ograthats not really moch02:07
ogra*much02:07
flintRegarding the CD.  Keep in mind the market for edubuntu is the educational institiution.  While they have burners and bandwidth, they often do not have the resolve to use them.  We need a CD run.  How much can this cost?02:08
ograflint, we have approval for some thousand CDs ...02:08
ograflint, but ...02:08
flintBut?02:09
ograwe need to keep track exactly who got them, in which amount, and if it fails, we'll never get money for it again02:09
JaneWand no one has bothered to submit anything to http://wiki.edubuntu.org/EdubuntuShippingPlans02:09
mhzJaneW: we want and are planning to have an Edubuntu Tour in some educational instoitutions (about 15, to start). Also, we are shceduling meetings with teachers to invite them to become testers before implemnting.02:09
JaneWwhich is a pre-req for our printing approval, sabdfl wants to review the plans.02:10
ograflint, so if we have the option for only one CD in edubuntu's lifetime at all, i'd rather go with next release02:10
JaneWmhz: sounds great02:10
mhzso wee need cd's:)02:10
ograthe german community saked me for some edubuntu talks on one of the 15 fairs they attend...02:10
JaneWmhz: agreed02:10
mhzthx02:11
flintok kidos, then which educational segment are you going to target?  primairy, secondary or college?02:11
mhzand or t-shirts :D02:11
ograso the requirement seems to be there... but its hard to keep track who got how many Cds if you give them out on fairs02:11
JaneWthe thing is if we want to drum up support and enthusiasm with this release and raise awareness before the next it would halp to have something to SHOW02:11
mhzogra: agreed02:11
ograflint, you were at the summit, you know what we target02:11
JaneWflint: it seems primary with this release, as the reviews have mentioned its very junior school friendly02:12
ograi think currently we dont really target colleg02:12
ograe02:12
mhzogra: what we are planning is "invite to demos", "enter a database", we visit you and demo it in front of Principals and Teachers. There, we provide cd's02:12
JaneWsecondary age students will possibly find it too juvenile...?02:12
JaneWmhz: your approach is good, more hands on and more likley to result in something02:12
ogramhz, but can this cover "some thousand CDs" ?02:13
JaneWogra: rem it;s no more than 500 per country02:13
flinti think that the technology would facinate at any level.02:13
ograwe need to get them all out to somebody... else it wont happen again02:13
flintI think a free CD should accompany every proposal delivered to a school adminsitration....02:14
ograso my concern is that this release is very young, even if people dont seem to notice...02:14
JaneWguys if we want this to happen we need to flesh out our distribution plans - see  http://wiki.edubuntu.org/EdubuntuCDPrintingPlans and http://wiki.edubuntu.org/EdubuntuShippingPlans02:14
flint...note first use of the word proposal.02:14
JaneWif we get that sorted we can press the CDs and I think we can easilly move them02:14
ograthe next one will have more gui tools more management software and be a lot more polished02:14
flintDear Jane, a lot of us have to work for a living...02:14
mhzogra: it all depends on resources. Unfortunatelly, we can't afford to travel all around Chile (we'd love to demo all over, but we just can't yet). Actually, 6th Encuentro Linux (linux gathering) starts tomorrow and we couldn't afford the travel and we did not have CD's to give put to people from education.02:15
mhzso, 500 cd tops sounds good02:15
ogramhz, i understand... but still, if we fail we wont have the chance again02:15
ograso i try to be very careful with this opportunity02:16
mhzogra: yes. I can assure the hard work from us in Chile. I cannot assure you that after 500 meetings, 500 schools will be using edubuntu :(02:16
ogramhz, thats not the point.... 02:17
ogracan you assure that 500 schools want a CD ?02:17
mhznop.02:17
mhz500 teachers and more? Yes02:17
JaneWok, lets tackle this as follows, if you want CDs, get the proposal in...02:17
flintollie, that is why you need proposals.  This situation is different from ubuntu.  it is about schools adminstrators not hackers...02:17
ograand thats the hard part... we need to make sure that there are some thousand people in the world wanting a CD 02:17
JaneWwe can also speak to sabdfl and get his opinion on whether he thinks the release is mature enough to press to CD (or wait till 6.04)02:18
ograif we fail with this, we'll loose the opportunity to do it with the more polished version02:18
flintjane, you do not get proposals you write proposals.  you got them going in the wrong way.  You generate proposals for use of edubuntu in schools.02:18
segfaultI think 100 cds limit is enough02:18
ograsegfault, 500 per country...02:19
ograthats our limit that was set ....02:19
segfaultnice, but 100 per person02:19
ograheh02:19
ograso 5 ppl per country :)02:19
mhzJaneW: current gov. is supporting Edulinux (rpm's) because nobody else has presented another alternative. That we'll do.02:19
segfaulthehe02:20
JaneWflint: Mark just wants to see a plan for WHAT THE CDS ARE INTENDED TO BE USED FOR02:20
=== jsgotangco [n=jsg@202.138.168.170] has joined #ubuntu-meeting
flintjanew, imagine a web site where you write in which school you are from, give some information about the school, and a proposal is printed and is used to wrap a CD which is mailed to the institution.02:21
jsgotangcohaloo02:21
JaneWdrafting a proposal to approach a school with would be great, but I need ppl to justify why I should send them CDs to distribute02:21
mhzJaneW: ok. he'll have that from us no later than tuesday.02:21
JaneWflint: no that's not what we are doing02:21
JaneWflint: read the 2 wiki pages, we will distribute to one of our edubuntu LoCo memebers who has prepared a distribution plan for his country02:22
JaneWthe LoCo person will be the edubuntu hub in their country and will handle the distribution as they see fit, though school, demos, events etc02:23
JaneWmhz: great thanks02:23
mhzJaneW: Does that mean I gotta become a LoCo memeber?02:23
jsgotangcoouch i have no time for that :)02:23
jsgotangcomhz: no not necessarily02:23
flintjanew, you are creating web documents faster than I can read in my spare time...02:23
=== mhz relaxes a byte then
JaneWok ogra, the powers that be and I will discuss the merits of printing now with what we have and you guys must motivate why you need/want CDs and what you'll do with them.02:23
ograflint, read them at work then :)02:24
JaneWwe'll take it from there02:24
=== jsgotangco twiddles fingers
JaneWmhz: I am using the term LoCo loosely here ... it;s basically the ppl who are involved in edubuntu such was al those who are here...02:24
=== mhz agrees and understand JaneW and ogra 'S POV.
flintthe good thing about all this publishing is I can ask Jane what url is a good t-shirt logo?02:25
JaneWjsgotangco: you get your proposal in too! :P02:25
ograin fact for germany it is the loco team that talked to me02:25
JaneWflint: you making edubuntu shirts?02:25
jsgotangcoJaneW: errr...i just need around 100 i don't need that much....02:25
ograi'll poke them to fill out the wikipage02:25
jsgotangcoJaneW: even 10 will do for me...i got a burner :P02:25
flintJaneW, you got a logo?02:25
ograflint, its on the wiki02:26
JaneWflint: did you see my edubuntu cake? http://www.flickr.com/photos/13916877@N00/52389874/02:26
JaneWok let's move on...02:26
mhzJaneW: what IF we reduced CD's printing/shipping to only 200, top. BUT we invest the rest of $ on T-shirts ?02:26
flintollie, saying it is on the wiki is like saying it is on the computer... n:^)02:26
JaneWmhz: I am not sure that's an option, but we can ask...02:27
JaneWok UBZ02:27
flintI have now read your plans. jane, will this distribution method penetrate into school systems?02:27
mhzflint: search -> title should do :) plus it right on index page :D02:27
jsgotangcomhz: not a good idea, you *can't* reproduce t-shirts for people02:27
JaneWUBZ is fast approaching, we need to make sure we have all required BOF topics02:27
jsgotangcowell its not like we'll be there :P02:28
ograi have listed my three main goals ... (centralized user management, thin client local devices, thin client sound)02:28
mhzjsgotangco: good point. But, for instance, yesterday I was at a university in which I was invited to go back next weeks to demo edubuntu. I'd love to give at least 3 t-shirts to the more motivated teachers02:28
JaneWwe also need those that will be present to volunteer to lead BOF and to do pre work and get some of the braindump work of the spec completed02:28
flintessentially the distribution method is a further constrained version of the ubuntu distribution method02:29
flintI got a tee shirt company around the corner, give me the url for a logo.02:29
JaneWogra: will it be feasible to target an entire school architecture in 6.04?02:29
ograJaneW, sure... 02:29
flintJaneW, that is a UBZ question and will require beer in the answer.02:29
ograyou can do that now if you want, but it involved knowledge02:30
jsgotangcowe have schooltool....02:30
mhzJaneW: yesterday, ogra pointed me to a very interesting BOF regarding wiki and doc stuff. However, my wife did not allow me to invest on such an expensive trip :( , sorry.02:30
ograits just shuffliny the pieces right and integrate them02:30
JaneWhttp://wiki.edubuntu.org/EdubuntuLogo02:30
flintdon't start about schooltool i was on the kb with Tom yesterday.02:30
jsgotangcoAHHH02:30
flintJaneW, Thanks!!!  This way I get the logo correct (for once!)02:31
JaneWTom was less than nice about some of his comments about edubuntu... 'aesthetic disaster'!02:31
flintgotta get an audio feed from the bof onto the net.  any ideas ollie?02:31
ograJaneW, the main point for school management is centralized usermanagement... if we got that in and working, we're 80% done...02:31
JaneWogra: great02:32
JaneWogra: is there any chance squeak will be sorted out for 6.04?02:32
ogranot really... i can add new images, but thats all, we cant ship it02:32
flintpeople who live in grass housees should not get stoned jane, that is all i will say about that.02:32
ograthe license doesnt allow us to put it anywhere else than multiverse, so by default you have to do some manual work to even install it02:33
jsgotangcoits much easier to actually run squeak in windows02:33
JaneWhas everyone here seen our new site and wiki designs btw?02:33
ograjsgotangco, yes... 02:33
JaneWogra: are they not going to change their licensing stance?02:34
=== Topslakr [n=Topslakr@24-54-42-180.lndnnh.adelphia.net] has joined #ubuntu-meeting
ograJaneW, squeak is nearly 10 years old, they didnt change it until now even many people requested the change... i doubt it02:34
jsgotangcoits not like its that easy...02:34
flintJaneW, you mean http://www.edubuntu.org/02:34
JaneWyes02:34
ograflint, and wiki.edubuntu.org02:35
mhzEdubuntu website look and feel is very good. Esp. considering is running Moin underneath 02:35
flintsqueak rocks...what is the license problem?02:35
ograflint, it forbids direct shipment02:35
ograand it makes the fonts non-free02:35
jsgotangcoand i believe some of the fonts too02:35
flintthat is wierd...02:35
ograyes02:35
ograbut unlikely to change02:35
JaneWjust to digress a little to the CD topic, I forgot to mention that mhz arranged the folloing designs for the CD packaging, please have a look and place comments at the bottom of the page.02:36
flintogra, telepathic shippment is still ok then?02:36
jsgotangcoits well established and we're a tiny speck at the moment..02:36
JaneWhttp://wiki.edubuntu.org/EdubuntuCdAndSlip02:36
ograThis License allows you to copy, install and use the Apple Software on an unlimited number of computers under your direct control.02:36
mhzCD's/ yes, please comment on that so I can do changes and close that chapter :)02:36
ogra^^^^ thats the main prob02:36
ograwe dont have direct control to any of our customers PCs...02:37
flintollie, these are not PCs they are servers...02:38
ograthere is an EXHIBIT A that allows distribution without shipping .... that why we can have it in multiverse but not on the CD02:38
JaneWCD PACKAGING:  mhz contributed these designs for the CD packaging http://wiki.edubuntu.org/EdubuntuCdAndSlip, please have a look and place comments at the bottom of the page.02:38
ajmitchogra: anything packaging-related you want help with for dapper?02:38
flintit is a pretty design, I gotta admit. cute kids and all.02:38
ograajmitch, sure, everything packaging related :)02:39
JaneWthanks02:39
ajmitchheh02:39
ogra;)02:39
flintollie, is there a live cd with edubuntu?02:39
ogranope02:39
JaneWogra: are you already starting on dapper, or do you need input at UBZ?02:39
jsgotangcoajmitch: stop lurking :)02:39
flintok why two cd overlays at the bottom of the page...02:40
JaneWflint: there's no LiveCD with this release (nor PPC installer)02:40
ajmitchjsgotangco: I wasn't lurking, I said I was here at the start ;)02:40
JaneWflint: I think we'll go with the plainer one02:40
ograJaneW, i have enough stuff to polish to start right through (in fact i'm just merging the new login manager into ltsp) but i need input from the ltsp guys at UBZ02:40
JaneWajmitch: was sleeping!02:40
ajmitchJaneW: I was?02:40
ajmitchI ought to be sleeping02:40
flintno, I was sleeping!!!02:40
ajmitchit's nearly 2AM here :)02:40
JaneWajmitch: jokes02:40
JaneWwow02:40
JaneWogra: ok02:40
jsgotangcomhz: add a red stripe or whatever at the bottom of the cd slip at the back, it should add some stuff about Edubuntu, copyright, Canonical, etc.02:40
ajmitchand I have a MOTU meeting in ~7 hours to attend...02:40
flintJaneW,  on http://wiki.edubuntu.org/EdubuntuCdAndSlip, bottom of page are two CD screens.  are both used?02:41
JaneWmhz: see the website footer for details02:41
JaneWflint: I discussed with mhz earlier and I told him I prefer the plainer one, esp as we need to add some text02:41
mhzjsgotangco: text/ sure. I just need to make sure the 'art' part is oke before editing texts :)02:41
JaneWmhz: must I send you that text again?^^02:42
flintfor a second I thought that one screen was for side 1 and the other for side 2, :^)02:42
jsgotangcotext should be easy, just rip form the edubuntu website theres loads02:42
JaneWflint: these are just conceptual02:42
mhzJaneW: nop, thx02:42
JaneWmhz: cool02:42
JaneWdoes everyone like the cover?02:43
ograyup02:43
JaneW:)02:43
flintaw, the security guy in me wants to screen both sides of the CD.  extra secure that way...02:43
flintwe could call this sedubuntu02:43
mhzare YOU ALL sure you wouldn't prefer a white cd label with edubuntu logo (as it is on right) and red text?02:43
jsgotangcoit'll look like a blank cd02:44
=== ajmitch wanders off to sleep now
ogramhz, i like it as it is shown...02:44
flintmhz, the red clearly enrages I am for it.02:44
mhzplease remember I chose white as symbol of end/begin of something new02:44
mhzflint: ok02:44
jsgotangcoasian countries associate white with death02:44
jsgotangco:)02:44
mhzyes02:44
mhzjsgotangco: death is good, is begining02:45
jsgotangcoickkk02:45
flintmhz, I still want both sides of the cd screened :^)02:45
=== JaneW kicks flint in the shin
mhzjsgotangco: plus, the death of old system v/s born of edubuntu :D02:45
jsgotangcoackkk spare me the poetic symbolism please... :P02:45
JaneWmhz: white slip cover is nice, but with a red CD inside02:45
mhzflint: i can do it once you print 10.000 t-shirts and send 1.000 to me :)02:46
mhzJaneW: okidoki02:46
flintI gotta go scan a data center, an activity I place up there with having rough sex with bad animals.  so I got to go.02:46
mhzjsgotangco: but you love documenting, dont you?02:46
mhz:)02:46
JaneWflint: enjoy (as you clearly do...)02:46
flintmhz, I will try to get some ts out the door...02:46
ograflint, have fun :)02:46
flintthanks jane.  bye!!!02:47
=== JaneW didn;t know flint enjoyed animals so much!
ograheh02:47
mhzflint: love what you do02:47
flintthanks ollie see you all at UBZ, quiet down jane.02:47
JaneWnext meeting?02:47
mhz?02:47
ogranext week ?02:47
=== jsgotangco shrugs just lurking...
JaneWI won't be around this time next week (in plane)02:47
ograyes, me too, as i just see02:48
JaneWso it has to be monday, or without me, or deferred02:48
jsgotangcojust defer it02:48
\shor at ubz02:48
JaneWvotes?02:48
mhzohhh02:48
JaneWwe'll be talking lots at UBZ02:48
ogradeferred ?02:48
jsgotangcoyeah02:48
mhzcome to chile and we have it here02:48
jsgotangcoor spark a discussion on the list02:48
JaneWbut do we need anymore on-line meetings before 16 Nov?02:48
ograyes02:48
jsgotangconot so much i guess02:49
jsgotangcolots of BOF'ing will happen02:49
jsgotangcono time for meetings at all for sure02:49
ograi think we wont have clear targets before UBZ (beyond my polish work on ltsp)02:49
mhzyes. When will we know if cd's get printed or not?02:49
JaneWok, so nothin official until 16 Nov, but we'll talk as necessary and may call meetings if we want/need to?02:49
jsgotangcosure02:49
ograyup02:49
jsgotangcoother matters, on the list02:49
mhzok02:49
jsgotangcoput it on fire!!!02:49
JaneWmhz: I'll try have a better idea by the end of the week, if not def during UBZ02:49
JaneWheh02:49
JaneWis there anything else to discuss now?02:50
jsgotangcodunno02:50
jsgotangcowhat i had for dinner?02:50
ogranot here02:50
mhzJaneW: what about local support?02:50
JaneWjsgotangco: fascinating! :)02:50
JaneWmhz: yes...02:51
=== ..[topic/#ubuntu-meeting:JaneW] : Agendas: http://wiki.ubuntu.com/MeetingAgendas | Calendar: http://wiki.ubuntu.com/Calendar | Logs: http://people.ubuntu.com/~fabbione/irclogs/ | 19 Oct 20:00 UTC: MOTU | 21 Oct 14:00 UTC: DocTeam | 25 Oct 22:00 UTC: CommunityCouncil | 1 Nov 20:00 UTC: TechBoard | 16 Nov 12:00 UTC: Edubuntu
jsgotangcoJaneW: pig intestines..in a murky soup base....02:51
mhzjsgotangco: piuk!02:51
ealdenjsgotangco: hotdog?02:51
mhzlol02:52
jsgotangcoealden: isaw pre...hehhhe02:52
ealdenjsgotangco: oh! haha02:52
JaneWjsgotangco: are you on Fear Factor!?02:52
jsgotangcoJaneW: that's a local street food02:52
ealdenjsgotangco: tasted it before.. its nice with vinegar hi hi02:53
jsgotangcoJaneW: we even eat duck eggs over here with the embryo02:53
JaneWjsgotangco: I seen that on Fear Factor too!02:53
jsgotangcoJaneW: what they eat on fear factor is ordinary food for us....02:53
pips1JaneW: I would like to talk about the Edubuntu Website ... Web team... ?!02:53
jsgotangcommm02:54
jsgotangcotoo bad hno73 and highvoltage are not here...02:54
mhzEdubuntu WikiTeam02:54
JaneWwhat are we doing about local support though? There's nothing formal and it;s all in formal and voluntary at this point, we only have support throug forum and IRC for now, if we polish 6.04 we can hope to get some more formal agreements in place02:54
JaneWoh yes the web team02:54
jsgotangcomhz: Edubuntu needs its own wiki team?02:54
JaneWhighvoltage couldn;t make it...02:54
JaneWpips1: can you contact him?02:54
jsgotangcoJaneW: mmm local support interesting...are we taking SLAs?02:55
mhzjsgotangco: not really, but hno73 and highvoltage are the EdubuntuWikiTeam02:55
jsgotangcomhz: actually henrik is Mr. Ubuntu Wiki himself02:55
JaneWjsgotangco: we will ultimately hope to get a similar arrangement that ubuntu has ITO support infrastructure02:55
mhzhowever, on personal basis, I would prefer to help on Edubuntu wiki pages02:55
pips1JaneW: sure... by mail?02:56
mhzand then move to ubuntu ones02:56
jsgotangcoJaneW: oh ok....i'll still slave an 8 - 5 job then 02:56
JaneWI think we'll have one web/wiki team, there's very little HTML, most of what we have is wiki02:56
JaneWpips1: yes, henrik=hno73=<henrik@ubuntu.com>02:56
mhzJaneW: so it is ok if we start a #edubuntu-es? or at least a edubuntu-es ML?02:57
pips1well, I spent some time brainstorming about the website today...02:57
JaneWpips1: highvoltage=Jonathan=<jonathan@shuttleworthfoundation.org>02:57
jsgotangcomhz: eh?02:57
jsgotangcomhz: if you have a ton of people, sure02:57
=== mhz prefers ML over # for support interaction and #irc for real life
pips1I am currently putting stuff up for discussion in the wiki...02:57
jsgotangcobut if its just a few....02:57
JaneWmhz: do you think there's demand?02:57
jsgotangcodoubt it02:58
JaneWmhz: ogra please voice an opinion too, I am happy for 'loco' teams to start up, but bare in mind that we can offer support in those languages so you will need to self manage them...02:58
mhzJaneW: not yet, but my concern is service. and so, we start demoing edubuntu next weeks, where should people who speak no english direct ot02:58
mhzot = to02:58
JaneWright02:58
mhzso far, no need at all, agred. but once people ask.. they need to go somewhere.02:59
JaneWmhz: well I am more than happy for translations and local language support etc to happen...02:59
mhzok, then: ThisPage, ThisPageEs, ThisPage/Es ?03:00
sivangthis is an edubuntu meeting now?03:00
jsgotangcosort of03:00
JaneWsivang: yes just finioshing03:01
jsgotangcojust ending03:01
mhzjsgotangco: LOL03:01
JaneWfinishing even03:01
sivang:)03:01
sivangwasn't listed on the topic03:01
JaneWmhz: um... dunno, who has an opinion jsgotangco ?03:01
JaneWsivang: it was I removed it a few minutes ago when I added the next meeting date ;)03:01
jsgotangcosivang: we're notorious gatecrashers :)03:01
jsgotangcoJaneW: sure, wiki entries on translations are always welcome...03:02
mhzJaneW: will that also mean that 'loco' teams should have their own servers?03:02
jsgotangcomhz: edubuntu loco?03:02
jsgotangcothere is such?03:02
JaneWjsgotangco: but should the pages be listed as: ThisPage, ThisPageEs, ThisPage/Es ?03:02
jsgotangcooh03:02
mhzi dont know, just using what you guys mentioned a little ago03:02
jsgotangcoI would prefer ThisPage/Es03:02
=== JaneW doesn;t know... this is all new to me *wail*
jsgotangcomhz: if there's no Ubuntu Chile, start one03:03
=== JaneW will have to find out, but I am sure we'll get some kind of loco structure going
jsgotangcoJaneW: i don't think its needed at the moment03:03
JaneWmhz: ok ThisPage/Es then...03:03
jsgotangcowe're very niche....03:03
mhzjsgotangco: ubuntu people concern is ubuntu, not edubuntu.03:03
JaneWjsgotangco: I like to think of it as l33t :P03:03
jsgotangcomhz: edubuntu is still ubuntu03:04
=== JaneW must wrap up now
jsgotangcoubuntu people can support edubuntu/kubuntu/xubuntu whatever03:04
JaneWfeel free to carry on, just clean up and lock the door when you leave.03:04
JaneWwill see you all in #edubuntu in a bit03:04
jsgotangconahh im gonna start looking at bugzilla03:04
mhzjsgotangco: yes and no. If we talk about ubuntu, I can then ask and support for linux generla stuff (kernel, hw, etc) If we discuss about edubuntu is focused on educational tools03:05
jsgotangcomhz: whatever its not like the tools are complex, they're quit easy actually but then i am not an educator i wouldnt know how things run so....03:06
mhzok03:06
jsgotangcoi would tend to think its more social rather than technology involved03:06
mhzhmmm, yes maybe.03:06
pips1http://wiki.edubuntu.org/EdubuntuWebsitePlan03:06
pips1more to follow... 03:07
pips1:-)03:07
mhzjsgotangco: yesterday a guy asked me about mp3 conversion. For me, that is ubuntu channel03:07
jsgotangcomhz: and a friend of mine installed edubuntu on a laptop...so...03:07
mhzhehehe03:08
mhzI use this laptop as an edubuntu server :)03:08
mhz'demo mobile'03:08
jsgotangcoi got 3 ubuntu flavours here03:08
jsgotangcook moving to #edubuntu03:09
=== jsgotangco [n=jsg@202.138.168.170] has left #ubuntu-meeting ["Konversation]
=== mhz [n=mhz_chil@moinmoin/fan/mhz] has left #ubuntu-meeting ["Leaving"]
JaneWpips1: awesome thanks!!!03:10
=== terrex [n=terrex@84-122-90-162.onocable.ono.com] has joined #ubuntu-meeting
=== pips1 [n=philipp@241.1.203.62.cust.bluewin.ch] has left #ubuntu-meeting ["Leaving"]
=== terrex [n=terrex@84-122-90-162.onocable.ono.com] has joined #ubuntu-meeting
=== cyphase [n=cyphase@adsl-69-106-43-235.dsl.pltn13.pacbell.net] has joined #ubuntu-meeting
cyphasehey everyone04:34
=== Yagisa1 [n=jamie@60-240-123-154.tpgi.com.au] has joined #ubuntu-meeting
=== Hirion [n=Hirion@p5487FBE4.dip.t-dialin.net] has joined #ubuntu-meeting
=== guillaumeB [n=guillaum@HSE-Toronto-ppp3487064.sympatico.ca] has joined #ubuntu-meeting
=== Unfrgive1 [n=ankur@202.76.176.94] has joined #ubuntu-meeting
=== Loiosh [n=loiosh@c-67-187-98-56.hsd1.tx.comcast.net] has joined #ubuntu-meeting
=== dholbach [n=daniel@i577B0EAC.versanet.de] has joined #ubuntu-meeting
=== BenC [n=bcollins@debian/developer/bcollins] has joined #ubuntu-meeting
=== terrex [n=terrex@84-122-90-162.onocable.ono.com] has joined #ubuntu-meeting
=== siretart [i=siretart@tauware.de] has joined #ubuntu-meeting
=== slomo_ [n=slomo@p5487FBE4.dip.t-dialin.net] has joined #ubuntu-meeting
=== segfault [i=carlos@prognus.com.br] has left #ubuntu-meeting []
=== vicks [n=chatzill@c83-248-59-130.bredband.comhem.se] has joined #ubuntu-meeting
=== vicks [n=chatzill@c83-248-59-130.bredband.comhem.se] has left #ubuntu-meeting []
=== LaserJock [n=LaserJoc@lambda.chem.unr.edu] has joined #ubuntu-meeting
=== Nafallo [n=nafallo@unaffiliated/nafallo] has joined #ubuntu-meeting
=== ajmitch waits patiently for MOTU to dribble in...
=== dholbach is here
=== Nafallo is Nafallo Bjlevik :-)
=== \sh is always in
\shor out09:52
ajmitchNafallo: that's useful at a CC meeting, perhaps... :)09:52
\shor on or off 09:52
Nafallothat's ALWAYS useful to know when a meeting starts ;-)09:53
=== ajmitch guesses the meeting will be nice & short
ajmitchall we need to do is say 'bddebian is doing it' :)09:57
=== siretart hopes so :)
siretarthrhr09:57
fabbioneevening everybody09:58
Nafallocan't we say siretart are doing s/svn/bzr/g to? :-)09:58
dholbachhi fabbione 09:58
dholbachnice to have you here09:58
Nafallofabbione: evening dude :-).09:58
fabbionedholbach: thanks my wife that falled asleep too fast and i am dead bored :P09:58
ajmitchhello fabbione 09:58
Nafallohehe09:59
dholbachfabbione: that's a good excuse to hang out with motus! rock on! :)09:59
LoioshHaha09:59
=== bddebian3 [n=bddebian@mail.ottens.com] has joined #ubuntu-meeting
=== fabbione had other plans for the evening.. MOTU's aren't actractive as wife's boobies
ajmitchalright, sounds like it's meeting time10:00
Loioshbd, you got voted into doing everything.10:00
bddebian3fabbione: :-)10:00
dholbachfabbione: absolutely10:00
bddebian3Loiosh: W00t, thanks10:00
LoioshWelcome =)10:00
dholbachright... here we go10:00
ogrameep10:00
ajmitchdo we have an ogra?10:00
ajmitchwe do!10:00
ogra:)10:01
bddebian3An Ogre?10:01
sivangoiii10:01
dholbachfirst item on the agenda is: Is there a need of Kernels in Universe? If so, what are the problems with his, are there any problems at all? I think it would be good, to have BenC or fabbione as (Ex-) Kernel Maintainers for Ubuntu with us in this discussion. (StephanHermann)10:01
sivangmotu meeting and I'm missing it :-)(10:01
dholbachi'm sure \sh will tell us a bit about it10:01
ajmitchfabbione: useful that you're here then10:01
fabbioneajmitch: that's why i am here10:01
dholbach(the agenda is at  https://wiki.ubuntu.com/MOTUMeeting )10:01
ajmitchok10:01
fabbione\sh: can you please explain everybody what that entry exactly mean?10:02
=== sistpoty [n=sistpoty@DSL01.83.171.160.112.NEFkom.net] has joined #ubuntu-meeting
fabbioneor who proposed via \sh please speak up10:02
ajmitchhi sistpoty 10:02
ografabbione, you know yourself that we had various requests for patched kernels...10:02
Lathiatbing10:02
sistpotyhi folks10:02
ajmitchfabbione: for example, we would like to have kernels with non-mainline patches, like grsec+PaX10:03
ogralow latency audio kernel etc...10:03
sivangogra: that would be nice to have10:03
fabbioneok10:03
fabbioneBenC and I did discuss this issue10:03
fabbioneand we do not agree to have kernels in universe for several reasons10:03
ograso the point here today is to have a decision if we want to allow such specialized kernels in universe or not10:03
fabbioneor better10:03
fabbionewe do agree that we do not want kernels in universe10:04
fabbionehere is a list of reasons:10:04
bddebianIt does seem a little touchy10:04
ograbddebian, it is...10:04
\shsry10:04
fabbione- there are already too many kernel flavours around and users are already confused anough10:04
ajmitch\sh: no matter, I would have raised the question anyway10:05
ograbut you force people who want to base work on such kernels to use an external repo10:05
fabbione- it will mean for the MOTU's to maintain a duplicate source10:05
\shohone10:05
ografabbione, nope10:05
fabbioneplease let me finish10:05
\shphone10:05
fabbioneif we are here talk, first i want to give out our explanations10:05
fabbioneotherwise if you already decided, my presence here is pointless10:06
dholbachi'm eager to listen10:06
fabbioneso let's try again10:06
fabbione- there are already too many kernel flavours around and users are already confused anough10:06
fabbione- it will mean for the MOTU's to maintain a duplicate source10:06
fabbione- universe kernel will be highly patches and very difficult to maintain even security wise10:06
BenCthe problem is that if we start to create specialized kernels, we set a precedent that cannot be stopped10:07
fabbione- if we create a kernel for each pet-project inside Ubuntu, we will explode in a thousands of kernels10:07
BenCeveryone will want their special purpose kernel ot be a flavor in our repo10:07
fabbione- the patches you want to apply are extremely intrusive10:07
ajmitchin the security case, it was something suggested in the proactive security BOFs at UDU, that we have universe kernels - better suggestions are welcome10:07
ograwe wouldnt touch them, the person who brought them in would be tied to them since they would have special purposes i.e. audio team low latency patched10:07
fabbioneogra: that does not work10:08
ografabbione, we didnt even talk about any patches yet10:08
\shdamn10:08
\shphone company bla10:08
ograits a discussion if we want to allow it generally10:08
\shok..now10:08
fabbioneif universe kernel goes out of sync with main, you get 2 different feature sets10:08
fabbionethat pushes even more confusion to users10:08
BenCogra: generally, I think any kernel flavors should be closely tied to our main source tree10:08
fabbioneogra: that's why i am giving you detailed reasons on why we do not want to allow them10:09
dholbachi tend to agree with fabbione, i believe, the workload that benc and fabbione cope with could hardly be accomplished within motu, wouldn't work an testing with the kernel team make more sense?10:09
ografabbione, also i'm not against you but try to take position for people that are not here or not MOTU yet but would want such patches... personally i agree, but as a MOTU guy i'm ambivalen10:09
BenCthings start getting even more ugly if people want to use linux-restricted-modules with these special flavors10:09
ograt10:09
Lathiatdholbach: its not so much testing, as specific patches people want that are too intrusive etc to be put in the main kernel10:09
siretartfabbione: we had a suggestions earlier on #ubuntu-motu. Would it be possible to provide infrastructure to faciliate users to patch and bake kernels themselves? we could put some *-patches packages in universe and point people to some documentation how to do that themselves10:10
Lathiatdholbach: pax, selinux, low latency audio, realtime, etc10:10
Lathiatgrsecurity10:10
fabbionesiretart: such instrastructure has always been there10:10
BenCsiretart: that's a goal of dapper10:10
siretartBenC: is there a wiki yet for that?10:10
fabbionesiretart: if people keep asking for it, it means that they have no clue on how to build a kernel, and that scares me even more 10:10
fabbionesiretart: + to see them maintaing one10:10
BenCsiretart: when I say goal, I mean unofficially at this point :)10:10
Lathiatit would definately seem it'd be much cleaner to have people roll their own kernels so they can keep them up to date etc themselves as needed10:11
ografabbione, BenC, also note that sabdfls highest priority for universe is to have everything available without forcing users to add external repos10:11
ograthats why we have to pull in apt-get.org every release...10:11
\shogra: I didn't see dholbach pull in kernel repos10:11
fabbioneogra: there is a reasonable balance of things we want and sanity of universe towards users10:12
Nafalloor just bake the modules for the current one... :-)10:12
ograif we deny support for such kernels people will offer them externally10:12
Lathiatwould it be possible to provide linux-patch-2.6.12-grsec or something, that was a grsec vX patch, but that applied cleanly to our source trees (this being the key difference to the upstream patch).. some people may be able to maintain that much or something10:12
\shthe kernel is heart of all distributions10:12
ajmitchNafallo: the patches usually aren't just modules10:12
Lathiatnafits nto always a matter of modules10:12
fabbioneogra: people are already confused by having 5 falvours of kernels for i386 on main10:12
LathiatNafallo: lots of things are for more intrusive than that10:12
BenCogra: think of it this way, if someone wants a grsec kernel, even if they base it on our kernel repo, they still to maintain atleast 3 arch's and ~4 flavors on each one of those (cpu and smp flavors)10:12
ograyup10:12
Lathiathowever if we have the patch thing, it needs to be maintained and kept up to scratch with the current kernel, and people lose interest, etc, and it would suck having an out of date patch10:12
fabbioneogra: that list could explose exponentially for each pet kernel10:12
=== seb128 [n=seb128@ANancy-151-1-23-253.w83-194.abo.wanadoo.fr] has joined #ubuntu-meeting
ografabbione, it will.. surely10:13
NafalloLathiat, ajmitch: I know. but generally. some things probably can be modules, like trulux vsecurity :-).10:13
fabbioneogra: and do you consider that good?10:13
fabbioneogra: or dangerous for the user?10:13
ografabbione, i'm taking a role here... its not my opinion... 10:13
ajmitchNafallo: which is being shipped separately10:13
fabbioneogra: also.. what will happen when a user ask feature foo+bar?10:13
ograi dont consider the whole idea good...10:13
fabbioneogra: are you going to create extra combinend kernels?10:14
fabbioneto what level of aggregation?10:14
dholbachespecially given the maintenance part of it: debian hast quite a lot of kernel-patch-bla packages which weren't touched for ages10:14
ografabbione, he has to found a team that cares for foo and bar10:14
ajmitchogra: I can think of at least 3 different kernel patches that the hardened team would want10:14
Nafalloajmitch: where? he has an external repo for them atm, no?10:14
BenCyeah, what if someone wants low-latency+grsec10:14
ajmitchNafallo: yes10:14
ajmitchNafallo: you've used them, right?10:14
ograajmitch, but they would go into one image, wouldnt they ? 10:14
ajmitchogra: no10:14
fabbioneogra: up till now the MOTU team has always landed in #ubuntu-kernel to ask kernel related stuff.. 10:14
Nafalloajmitch: nope, I've only built them for amd64 when he called for help with that.10:14
ajmitchnot necessarily :)10:15
fabbioneogra: that means that none of the MOTU is dealing to take care of these pkgs10:15
ografabbione, yup10:15
fabbioneogra: so from a MOTU point of view, you should be the first to say no10:15
sistpotyajmitch: would only the kernel be affected or would userspace packages need to modified as well?10:15
ograit would be a requirement to fully take care of it indeed10:15
fabbionespecially if people asking for these features can't maintain them themselves10:15
\shogra: this is impossible...someone who asks for a kernel in universe, has to know what he's doing...and if so, he can provide the patched source to the world...because we (and I personally don't) can't support them...thinking of dapper this is really danguerous if we provide more kernels then the main one...and even this is quite difficult to support over 5 years10:15
ografabbione, nobody here will take the role of the people who would want these kernels, thats why i do it to try to give a balance in the discussion10:16
ajmitchsistpoty: usually just kernel, with some userland support for some of them10:16
ajmitchogra: we could easily end up with > 50 kernel binary packages in dapper10:16
BenCI've an idea, how about people who want these kernels start managing them externally to universe to start10:17
fabbioneogra: also.. do you all realize that these kernels will be obsoleted the day after the first USN?10:17
fabbioneBenC: ++10:17
ograit would require a good amount of consideration whichto allow and which not10:17
Lathiatit seems to be it would definately be much more sane for people who need these kinds of features to do them themselves.. i mean the patches i've heard of (low latency audio, grsec, vserver) all seem pretty specific and for people who generally know what their doing, not something to be used by idiots10:17
BenCif they get maintained well enough, and there aren't a lot of problems, then we an bring this back for consideration10:17
=== Nafallo agrees with the kernel gods :-)
ograBenC,++10:17
siretartwhat about packaging kernel-patches?10:18
BenCthere wont be a kernel-patches for dapper10:18
fabbionesiretart: that will fail at the first USN10:18
BenCkernel source will become native10:18
siretartas dholbach pointed out, debian already has some of these10:18
\shogra: as I explained in -motu: people who wants to have some things in the kernel, which is not there already, will build their own stuff...when they can...if not, they will ask someone...and we shouldn't be the people (as team and bound to ubuntu as name) who are doing this...if I do it in my sparetime and under my own name, and provide a kernel with this and that in it, it's something else10:18
siretartso what to do with the already existing ones in universe?10:18
LoioshBenC++10:18
fabbionesiretart: we do have different security release procedures than debian10:18
dholbachsiretart: i morgue'd all of them for hoary :)10:18
siretartdholbach: ah10:19
fabbionesiretart: let's make a simple example10:19
fabbionesiretart: kernel foo in main10:19
fabbionekernel-patch feature bar in universe10:19
fabbionewe release10:19
ogra\sh, nope, but if we would allow such kernels we'd need a very clear policy to avoid 50 binarys ... but it seems pretty clear that we all dont want it10:19
fabbioneall nice and dany10:19
fabbionedandy10:19
ograand i think BenC's suggestion is the best so far...10:20
fabbionesiretart: at the first security release for main10:20
fabbionekernel-patch might not even apply anymoer10:20
=== Lathiat eyes kernel-patch-{2.4-lids,2.6.10-hppa,atopacct,debian-*,evms,nfs-ngroups,evms,ppsci-2.4,ppscsi-2.6,skas,speakup,....}
fabbionesiretart: that will be the hell of the user10:20
fabbionesiretart: security or feature?10:20
bddebianeeks10:20
dholbachLathiat: they most have come in in breezy and i didnt have the time to take care of them10:20
Lathiatdholbach: righto10:20
=== TiMiDo [n=deb@unaffiliated/timido] has joined #ubuntu-meeting
siretartfabbione: maybe updatable via -updates?10:20
=== koke [n=koke@adsl229-164.unizar.es] has joined #ubuntu-meeting
siretartfabbione: I perfectly see your point10:21
TiMiDohey everyone10:21
\shogra: I'm really afraid of thinking that universe-kernel-main_rev-with-patches-for-foo is being regarded as supported kernel...which happens tfom time to time with packages out of universe, because the communication about supported main/restricted and unsupported universe/multiverse is sometimes b0rked10:21
ograsiretart, if its a security update, then via -security10:21
fabbionesiretart: i can ensure you that the maintainer will be too busy taking care of the last shiny code10:21
fabbioneogra: nope.. for kernel-patch is -updates10:21
siretartfabbione: the thing is: there ARE people outside wanting these 'special feature' kernels. The question here is, what can WE do to support them?10:21
ogra\sh, no kernel in universe would ever be supported10:22
\shsiretart: testing the features and implementing them in one of the next releases10:22
Lathiatwe can support them by not letting them random foo into universe10:22
dholbachso what is the best solution for this? try to postpone all these requests until we have a proper infrastructure (i refer to BenC's unofficial goal)?10:22
fabbionesiretart: answer: the dpatch system has been there forever, they can apply their patches with very little knowledge10:22
bddebianDon't WE have enough problems supporting "I want the latest foo" ? :-)10:22
TiMiDohey people sorry for my rudness, i will love to join the motu team, =)10:22
ajmitchogra: users still think that they are supported - see 2.6.11 fun10:22
ogradholbach, do we actually *have* theye requests ? 10:22
ograthese even10:22
fabbionealso10:22
bddebianTiMiDo: Are you an Ubuntu Member yet?10:22
\shogra: u see, but the kernel must be very reliable, and therefor I would like to see (as user) a special work on those packages...because kernel has to be healthy 10:22
BenCsiretart: I think we should support their efforts with docs and wiki entries pointing to their personal work10:22
fabbioneanother important factor to take into account10:22
dholbachogra: i thought you had, because you "fought for the balance" :)10:22
TiMiDobddebiann nope10:22
ograi thought thios discussion is rather hypothetical10:23
LathiatTiMiDo: stop by #ubuntu-motu after the meeting10:23
TiMiDook =)10:23
=== TiMiDo is watching
BenCsiretart: the people who want these kernels in ubuntu need to take the first step10:23
siretartfabbione: this means they have to have some packaging skills for creating a dpatch and building the package. 10:23
fabbionewhat user base do these kernels have?10:23
siretartfabbione: but I personally am fine with that10:23
fabbionesiretart: a dpatch is a normal diff with 3 extra lines10:23
fabbioneif they claim to be kernel maintainers10:23
siretartjupp. I know10:23
fabbionethey know how to do that10:23
fabbioneor where to look10:23
fabbionethere is no need of a special infrastructure10:23
ogradholbach, i gave hypothetical people a hypothetical voice ;) i was there when the audio taem died because they couldnt have their low latency kernel in universe10:23
dholbachfor baking stuff themselves10:24
fabbionei do not believe somebody that claims to be a kernel maintainer cannot look into a package10:24
TiMiDowell what kernel are we talking about?10:24
ograTiMiDo, universe kernels10:24
TiMiDooh alright,10:24
\shTiMiDo: wiki.ubuntu.com/MOTUMeeting10:24
LathiatTiMiDo: We are talking about allowing kernels into universe, ones with specalized patches, grsec, pax, vserver, low latency audio, etc, see the MOTUMeeting page10:25
TiMiDothnx \sh10:25
dholbachok... how much involvement and serious arguing do we want to allow *-patches?10:25
dholbachso we can settle the matter reasonably10:25
siretartjust theoretically. Some MOTU (or MOTUWannabe) wants to create and support a feature patched kernel like linux vserver or something. What should we tell him? What if he promises to give some support to his kernels?10:25
fabbionedholbach: we won't allow -patches for the reason i explained before.. 10:25
ograok, so the conclusion is we'll not allow kernels in universe for dapper but will review this if someone comes up with a well maintained kernel he offered in a external repo for some time ??10:26
dholbachfabbione: alright, or custom kernels in universe10:26
fabbionei think BenC idea of watching these kenrels activity in external repository first is a good first step10:26
sistpotyhm... what about the idea to form a motu-kernel team... members of this should then be the only team to allow foo-bar kernel stuffs or eternally deny them to come to universe10:26
\shsiretart: deb http://archive.ubuntu.com/ubuntu <distroname> black-hole10:26
siretartI'd propose to tell him to put his kernel in some 'private' repo and advertise them there..10:26
sistpotyso there would be no more then max 2 different flavors in universe10:26
Lathiatsistpoty: i think thats not really needed until we end up with the first idea suggested - someone who has one they maintained for a while10:26
fabbionesistpoty: there is no MOTU-kernel.. as i said before..10:26
siretart\sh: this requires more fiddling with dak. you don't really want elmo to do that ;)10:27
Lathiatdak?10:27
\shsiretart: yes I don't want it...but you know what a black-hole is...;)10:27
siretartLathiat: debian archive kit. ftpmaster software for ubuntu/debian10:27
siretart\sh: ah, now I see.10:27
Nafallosiretart: dak will be launchpad soon ;-)10:28
ograsistpoty, the way to go is to offer tham in a external repo for some time and then come back and ask for new discussion10:28
\shI see it like this: As a "ubuntu official team" we should avoid support work for not main maintained kernel packages...what we're doing as private people..is really something else10:28
Nafalloatleast a lot of it from what I've seen :-)10:28
fabbioneogra: what about the MOTU review archive?10:28
sistpotyogra: ok... i agree fully for this... maybe when one "is ready" then, we even have some nice tools ;)10:28
ografabbione, thats not an archive10:29
dholbachfabbione, BenC: do you want to have those guys (that might come up) working with the kernel team, review/discussion/involvement-wise?10:29
fabbioneogra: can it be turned into one?10:29
siretartfabbione: you mean revu? 10:29
\shand if there is a possibilty, because one MOTU or someone else with enough kernel knowledge, is providing a good report for a special kernel feature, main kernel dev can think about including them into main kernel stream10:29
fabbionesiretart: i think so 10:29
ografabbione, why ? then motu will be responsible10:29
siretartfabbione: revu will be an archive, but even if, that would be a source only archive10:29
\shfabbione: no...10:29
ografabbione, if someone wants to offer such a kernel he should care for it himself...10:30
fabbionedholbach: it depends.. we already have people coming there10:30
BenCdholbach: yeah, they'll need to keep in touch so they can follow our development cycle10:30
TiMiDowhy don't we just build a kernel from scratch?10:30
ograif *we* adopt such a kernel we will care, help and offer the universe archive10:30
fabbionedholbach: the main issue is that as soon as we tell them to prepare their own kernels, they all disappear10:30
dholbachfabbione: i can, sadly, imagine10:30
BenCyeah, but that's the whole point of the excercise to have them maintain the kernels outside of universe first :)10:31
ograyup10:31
fabbionedholbach: so i am glad to see working people around10:31
fabbioneBenC: eeheh10:31
dholbachyeah10:31
=== TiMiDo wants to work for ubuntu (:
dholbachok, i think the matter is settled then?10:31
fabbionedholbach: but just askers.. we had plenty :)10:31
Lathiatyep10:31
ograsounds like10:31
siretartdholbach: matter resolution: NO :)10:31
dholbachfabbione: thanks for telling me... again - i got the pointer ;)10:31
\shI don't want to be responsible for non booting and oopsing kernels10:31
fabbionedholbach: eheh :)10:32
dholbachsomebody added the 2nd item on the agenda:10:32
dholbach Guidelines for using dpatch - many debian maintainers see our use of it as excessive, for the small patches we add.10:32
fabbionedholbach: didn't you offer volunteer as kenrel maintainer?10:32
dholbach"somebody": please speak up10:32
=== ajmitch added that
ajmitchI was going to add the infinity quote as well, but thought better of it :)10:32
=== ogra would propose more usage of dpatch :)
dholbachfabbione: sure linux-image-2.6-crack-*10:32
TiMiDowhy crack?10:32
\shfabbione / BenC : Thx for coming around :)10:32
dholbachajmitch: put the quote here :)10:32
BenCno problem10:33
ograyeah, thanks for taking the time10:33
fabbioneno problem10:33
ajmitchogra: this is part of being polite & reasonable with debian10:33
=== BenC parts the meeting
dholbachyeah, thank you very much, BenC, fabbione - it was a pleasure :)10:33
=== fabbione takes off
dholbachbye10:33
siretartbye fabbione . and thanks for coming!10:33
\shfabbione: comfort your wife now :)10:33
ograbye10:33
dholbachok... ajmitch, we're all ears10:33
BenCthanks for inviting us for input10:33
fabbione\sh: she is sleeping10:33
\shfabbione: u should do the same :) 10:33
LoioshHahaha10:33
ajmitch< infinity> Universe should ideally deviate from Debian as little as possible, or you guys will be up shit creek.10:33
dholbachhaha10:34
dholbachthat's excellent10:34
=== siretart can really understand why DDs dislike dpatch
\shfabbione: it's cold at my place...I would like to have a wife who is warming my feet ;)10:34
ajmitchbye BenC, thanks10:34
dholbachthat's something, seb128 had some words to say to, too10:34
LoioshYou guys.. =)10:34
ograajmitch, sabdfl sounde quite different todasy10:34
fabbione\sh: did you lose cita again?10:34
ajmitchogra: I know, but that's just sabdfl ;)10:34
siretarta really promising solution seem to me the wig and pen format, but it is not here yet :(10:34
\shfabbione: cita?10:34
ogra\sh, i couls offer some animals10:34
ogra*could10:34
fabbione\sh: never heard of tarzan?10:34
ogracheetah10:35
kokesiretart: what's wrong with dpatch?10:35
ajmitchI know that we use dpatch a lot, even for a tiny patch10:35
seb128dholbach: about dpatch or patching ?10:35
\shoh cheetah ;)10:35
dholbachyeah, and the delta10:35
Loioshdpatch10:35
dholbachseb128: ajmitch < infinity> Universe should ideally deviate from Debian as little as possible, or you guys will be up shit creek.10:35
=== seb128 thinks you patch/create too much diff for small changes
siretartkoke: it is really awfull to debdiff 2 source packages with dpatch10:35
ajmitchwhich annoys DDs when we go making intrusive changes like that, which we have to carry around for the rest of our lives...10:35
\shfabbione: well...no comment for now ;)10:35
seb128<seb128> no, sending fixes at the right place and asking syncs is the way to go10:35
seb128<seb128> most of the motu changes give extra work10:35
ajmitchthe less delta we carry, the better10:35
ajmitchseb128: agreed10:36
ajmitchwe keep on creating more work for ourselves10:36
siretartwhat are "small" changes?10:36
siretartup to how many lines a patch is small?10:36
seb128changes to .desktop files by example10:36
dholbachand we don't forward small patches to the DDs enough10:36
seb128to take one10:36
\shseb128: dpatch includes plain diff -ur as well?10:36
siretartwhat about re-libtoolizing package? what about auto-reconfiguring stuff?10:36
seb128yep10:36
ajmitchat last count (with grep-dctrl), we had > 1200 packages in breezy universe with an *ubuntu* version10:36
ajmitchthat's 1200 potential merges10:37
siretart*sigh*10:37
seb128siretart: anything that could be fixed upstream by upstream or Debian should have a patch send here to start10:37
seb128make a fix10:37
seb128send it to Debian/Upstream10:37
seb128wait for them10:37
ograajmitch, seb128, as sabdfl said, ubuntuX will be dropped as a version number :)10:37
seb128ask a sync or get it synced automatically10:37
Lathiatogra: it will?10:37
\shseb128: who can we be sure, that debian/upstream are including our changes?10:38
ajmitchogra: I don't care about that10:38
siretartogra: what?!10:38
seb128please don't troll10:38
seb128STOP10:38
ograthats his plan10:38
\shs/who/how/10:38
Lathiatbah10:38
seb128don't start trolling10:38
ajmitchogra: irrelvant to this10:38
ograok10:38
bddebianAnd packages that have no .desktop.  Or the stuff wrong with X11?10:38
seb128the meeting have enough to say without starting on that10:38
ograajmitch, even if i see it very relevant10:38
seb128bddebian: create a .desktop, send it upstream10:38
ajmitchogra: it's versioning, not patching10:38
seb128so we get it translated 10:38
seb128and no sync to do10:38
ajmitchlets just stay on the topic of dpatch usage10:38
bddebianseb128: I have been asked if the paths are the same?10:39
Lathiatso, when i started out10:39
\shseb128: many of my changes I send to debian or upstream are "dropped because no use" or "not included, because upstream dev doesn't want it"10:39
Lathiatpeople were recommending to integrate dpatch10:39
Lathiatfor aptches10:39
ograajmitch, there is no difference we talk about debian<->ubuntu relationship here10:39
Lathiateven smallish ones10:39
ajmitchLathiat: yes, and we've learnt since then10:39
Lathiat(i thought it was kind of silly) -- are we now sayign thats a bad idea10:39
Lathiatright10:39
\shseb128: so the question must be: diff.gz or dpatch/diff -ur10:39
ajmitchogra: and I'm talking about the ever-increasing workload we make for ourselves10:39
Lathiatbut if they already have a patch system, we should try to use that, right?10:39
ajmitchLathiat: yes, definitely10:39
seb128\sh: dpatch needs to change debian/control,debian/rules .. that sucks10:40
ograajmitch, if my patches dont get accepted upstream or arent even relevant for them, i want to have a easy maintainable dpatch10:40
Kamion\sh: you should be consistent with the existing packaging, in general10:40
dholbachLathiat: sure10:40
Kamionthat's been a rule of general sanity for QA work in Debian for years and years10:40
ajmitchseb128 has raised a good point about us failing to push enough upstream to debian10:40
dholbachnice to have you here, Kamion :)10:40
Kamion"do not mess with the maintainer's build system"10:40
seb128right10:40
ograi agree that for a 10 line change n rules or something else done in the debian dir we shouldnt use dpatch10:40
sistpoty[22:36:49]  <siretart> what about re-libtoolizing package? what about auto-reconfiguring stuff?10:40
\shseb128: and I like a clean orig.tar.gz where the patch is included during build time...so I know what is being patched without grepping down a big diff.gz e.g.10:40
ograbut for changes on the source i'll always use it10:41
Lathiatquite, im thinking we should have a "motu send patches to debian" day10:41
ajmitchogra: if you were patching rules from dpatch I'd have to worry ;)10:41
ograajmitch, you know what i mean...10:41
\shKamion: if there is a dpatch system in maintainers package, -> dpatch is used10:41
Lathiatogra: what if you have a 1 line source patch, and there is no patch system in the original package10:41
Kamion\sh: sure, that's obviously sensible10:41
seb128Lathiat: every motu should send his patch before uploading something creating a delta10:41
ogratrivial changes in the debian dir... uudecoding a png for a .desktop file etc10:41
Kamionwhat's not sensible is adding dpatch when it wasn't there to start with10:41
Lathiatseb128: right10:41
Lathiatseb128: what about when the debian guy is unresponsive ish10:41
=== bddebian2 [n=bddebian@mail.ottens.com] has joined #ubuntu-meeting
Lathiate.g. say 4 weeks passed and still no ack10:42
ograseb128, tahts something revu should provide10:42
seb128Lathiat: you can upload, I've not said to create 0 delta10:42
Lathiatseb128: just to try not to10:42
siretartseb128: I created a lot of deltas just by adjusting build dependencies for some strange transitions. There are tons of such 'modifications' :/10:42
seb128but to send patches upstream or to Debian10:42
\shKamion: when there is no patch at all, and I had to patch the orig source, I used most of the time diff -ur...and debian/* stuff i did without diff -ur/dpatch bla...10:42
seb128siretart: send upstream what can be send upstream (ie: new desktop files), send patches for crashers/etc to Debian10:43
seb128siretart: for the transitions we have to deal with, that's fine10:43
Kamion\sh: ok, I don't know what you personally have been doing, it's just something I've been getting complaints about from people I work with on a regular basis in Debian10:44
\sh(and we have to be carefull during the next universe/main sync process if some packags are not CXX trans  ready ) ;)10:44
ajmitchand we want to avoid complaints as much as possible10:44
Kamionand it's making my relationship with them difficult because I'm having to apologise for things like that10:44
ajmitchthe MOTU team doesn't have a great name in debian, sorry10:44
\shKamion: I read joeys blog entries ;)10:44
sistpotyseb128 / Kamion: what would be the most gentle way to send these? directly to the maintainer or by bugs in BTS?10:44
Kamionsistpoty: bug reports are the normal approach ...10:45
TiMiDosistpoty maintainer10:45
seb128sistpoty: BTS10:45
sistpotyok, thx10:45
=== TiMiDo remembers when i was a Debian developer
Kamionajmitch: it's ok to be less-experienced, as long as people are willing to learn :-)10:45
ajmitchthey can track patches in the BTS10:45
Nafallothere is a good opportunity for us to bring the delta down now that mom starts again I guess, some extra work. but I'm positive we will survive that :-).10:45
ajmitchKamion: yes, I though this point needed to be raised, we don't want to be tainted :)10:46
Nafallowe just pick the deb version and send what we did upstream :-P.10:46
=== ajmitch waits for a package for breezy-updates to build.. there was already dpatch there, thankfully :)
dholbachbut i'd still like every motu hopeful to be able to cope with all patch systems10:47
ogradholbach++10:47
ajmitchKamion: btw you or mdz will approve for -updates?10:47
seb128easy way is to put the patch to debian/ubuntu-patches and to apply it to the source package10:47
dholbach(just raised the point, because i think that will go into review practices as well)10:47
Kamionajmitch: just mdz, at least unless the workload spikes a lot10:47
=== ajmitch forgot to add breezy-updates to the agenda
ajmitchKamion: ok10:47
seb128so no need of change the packaging system and the maintainer has the patch if he wants it10:47
ograseb128, with a straight patch -pX command ?10:48
sistpotybut I still didn't get the conclusion on when to use patch system... 1) only when there from dd 2) on large patches (define large!) 3) s.th. else?10:48
ajmitchseb128: good idea10:48
seb128right10:48
ografine with me10:48
seb128so it's applied10:48
seb128and you don't have to read the .diff.gz to figure the change10:48
ograas long as we still maintain the patches separately..10:48
\shseb128: u mean instead of debian/patches ? 10:48
ajmitchogra: that would have them separately, just not applied at build time10:48
ogra\sh, yes10:48
Lathiatogra: how do you mean?10:48
ajmitch\sh: just a way of keeping them apart10:48
ograajmitch, yup10:49
NafalloI'll guess changes in debian/[rules,control]  should just be documented correctly in debian/changelog, right? :-)10:49
TiMiDoNafallo right10:49
ajmitchNafallo: of course10:49
dholbachNafallo: ++10:49
ograNafallo, additionally10:49
sivangwhat part of the MOTU agenda is being discussed ?10:49
seb128\sh: I mean something not used by the packaging10:49
Nafallogood, no ubuntu-patch for that one :-P10:49
dholbachwe should be more disciplined about that10:49
ajmitchsivang: dpatch10:49
ograsivang, second10:49
\shwell...I don't see the real difference...it's a nono to mix up dpatch and plain diff -ur patches 10:49
dholbach\sh: if you have dpatch, use dpatch10:50
sivangajmitch: thanks ;)10:50
Lathiat\sh: if dpatch is alrady there, use it!10:50
ogra\sh, if dpatch is there, use it...10:50
dholbach:)10:50
Lathiatok so if dpatch isnt there, and you need to patch the source10:50
seb128\sh: the package don't use a packaging system, don't change it to use one. Just copy your patch to debian/ubuntu-patches and apply it 10:50
sivangLathiat++10:50
ogra\sh, if its cdbs, use cdbs10:50
\shthats what I said...is anybody doing it differently?10:50
Lathiatyou should create a patch file and apply it with diff in rules?10:50
ograelse apply a normal patch10:50
dholbach\sh: some guys introduced dpatch10:50
Nafalloif you have _any_ patchsystem in place, use it :-)10:50
dholbach\sh: me amongst them (in some cases), so it's nice to see this discussion10:50
sivangseb128: if you copy it there, does it get applied automatically ?10:50
Lathiatyeh i had been too10:50
ograme too in some cases where i certainly know the version wont survive this release10:51
\shdholbach: phew...so I'm on the right site ;) I used only diff -ur for orig.tar.gz patches ;)10:51
Lathiatso what, you add a patch < before build and diff -R in clean?10:51
ajmitch\sh: great10:51
seb128no, it doesn't get applied10:51
=== bddebian [n=bddebian@mail.ottens.com] has joined #ubuntu-meeting
=== Lathiat is still confused on that part
ajmitchLathiat: no, not at build time10:51
ajmitchdebian/ubuntu-patches will be informative only10:51
ograits an add on10:51
Lathiatajmitch: apply the patch, but include the diff in debian/ubuntu-patches/ for reference?10:51
sivangso how do we apply patches if we don't have any patches application system in place? manually?10:51
ajmitchLathiat: yes10:51
Lathiatok!10:51
ajmitchsivang: yes10:51
Lathiatthat makes sense!10:51
\shso have it in diff.gz 10:52
Lathiati think i should go write a wiki page10:52
Lathiatdetailing this10:52
ajmitchLathiat: please do ;)10:52
Nafalloseb128: (since we lack pitti) we should follow that ubuntu-patch ida with security to in your opinion? :-)10:52
sistpotyLathiat++10:52
\shand debian/ubuntu-patches only for informational purposes10:52
ograsivang, make your changes but keep a patch that reflects them10:52
dholbachLathiat: PackagingTips? MOTUWannabeSomething?10:52
LathiatMOTUApplyingPatches or something10:52
sivangogra: cool, understood10:52
dholbachLathiat: link it from everywhere :)10:52
sivangogra: I wonder if this practice should be also followed in main ?10:52
Lathiatwhwat about when we need to do things like update configure etc?10:52
ograsivang, and use the existing patchsys if already available...10:53
ajmitchLathiat: it's the same thing10:53
seb128Nafallo: no opinion on that10:53
Nafalloseb128: oki, I'll try to remember to ask pitti later :-)10:53
Lathiatdoing ubuntu-patches would make for messy debdiffs ;)10:53
ajmitchsecurity changes need to be as small as possible, generally10:53
ajmitchLathiat: yes, but we can filter that part out10:53
ajmitchman filterdiff ;)10:53
Lathiatheh10:53
Lathiatok10:53
sivangLathiat: right10:53
dholbachok, do we have agreed? :)10:54
ajmitchdholbach: YES!10:54
dholbachROCK10:54
\shif someone summarize it10:54
ajmitchnow onto my next 2 points...10:54
seb128I've to go, later guys10:54
ogracool10:54
dholbachnext item on the agenda10:54
Nafalloajmitch: should still show what we did, no? :-)10:54
ajmitchok, thanks seb128 10:54
\shseb128: thx10:54
=== sistpoty gains 100 XP
dholbachsee you seb10:54
dholbach#10:54
dholbachUpstream Version Freeze & other milestones (AndrewMitchell)10:54
dholbach    *10:54
dholbach      We have a huge list of packages to merge, these should be finished right around UVF if not earlier. (AndrewMitchell)10:54
ograbye seb128 thanks for coming10:54
=== ajmitch has an agenda >:)
ograthat means we'll not see new stuff probably10:54
LoioshLoL sist =)10:54
=== sivang thinks ajmitch rocks
ajmitchogra: depends on how much time we can spend reviewing10:55
dholbachi second ajmitch's point10:55
ograajmitch, exactly...10:55
ajmitchand if UVF for universe lags main UVF10:55
dholbachogra: focus != only goal10:55
ograbut we had 200 merge packages in hoary10:55
sivangajmitch: does anyone know about the UVF prosept date?10:55
ajmitchogra: up to 1200 for breezy10:55
Lathiatsivang: thats still being thrown around like mad by the looks of it10:55
\shogra: we will have more for dapper10:55
ogradholbach, UVF *will apply* for universe this time10:55
ajmitchwell breezy->dapper10:55
dholbachsivang: no, will be discussed at UBZ, i guess10:55
dholbachogra: i know10:55
Nafallowhere a lot is trasitions, no? :-)10:55
\shNafallo: yes10:56
siretartjust a small (but I think important question). How will be syncs handled for dapper?10:56
ajmitchwe have far less transitions, far more merging10:56
sivangwell, given the amount of work, maybe it would be beneficial to start bugging about it?10:56
dholbachwe should perfectly agree on making number one prio10:56
siretartwill this go via elmo or launchpad?10:56
ajmitchsivang: ?10:56
ograso time is very short to merge say 300 pkgs *and* get new stuff reviewed10:56
\shsiretart: MoM will handle this bug list10:56
dholbachsiretart: there's a lot of confusion on the very topic10:56
ajmitchogra: I think that most merges can be done in a few weeks10:56
Lathiatwe should draw up a merging guide, we need to do things like, try reduce deltas etc, and filign bugs, etc10:56
ajmitchbut we only have a few weeks10:56
ajmitchLathiat: ++10:56
sivangajmitch: I mean, to start maybe tryin to get someone to think about it :) if we have so much work10:56
dholbach\sh: mom is broken afaik10:56
Nafallowow. universe are going to look clean after we've done this the right way (sending things upstream...) :-)10:56
ograajmitch, we only have a few weeks :)10:56
ajmitchsivang: why do you think I raised it here?10:56
ajmitch09:56 < ajmitch> but we only have a few weeks10:56
=== Lathiat volunteers again to draft up an initial version of MOTUHowToMerge
dholbachNafallo: :))))10:56
sivangajmitch:  :)10:56
ajmitch*cough* ;)10:56
\shdholbach: well...I don't have a mom actually...so I'll do it the normal hand-ish way10:56
=== ajmitch has gotten used to doing manual 3-way merging :)
dholbachme too10:57
=== sivang would like to know 1) What does the merge invovles. 2) How many NEW pakcages we need to do
bddebianMOM is a little questionable at times10:57
bddebian:-)10:57
Lathiatmom is always questionable!10:57
sivang\sh: is MOM freely avbailable ?10:57
ogra\sh, hand-*ish* ?10:57
sivangerr,10:57
dholbachsivang: 2) we can't say that10:57
Lathiatsivang: a merge is taking the difference between debian and ubuntu packages10:57
\shogra: manually10:57
Lathiatsivang: and fixing it up10:57
Nafalloajmitch: spec up a guide for us on the wiki? :-)10:57
ajmitchsivang: you have 3 versions.. the original version, ubuntu changes, and debian changes10:57
Lathiatsivang: where they conflict10:57
dholbachsivang: 1) getting new debian version in, applying our changes10:57
ajmitchNafallo: sure...10:57
ogra\sh, like done at ish ? 10:57
\shsivang: I searched for it..and I only found a commercial package10:57
sivang\sh: hehe10:58
\shogra: *lol*10:58
ajmitchI could write a MoM clone if you really needed it :P10:58
=== ivoks [n=ivoks@lns01-1373.dsl.iskon.hr] has joined #ubuntu-meeting
ograsivang, there is no use for MOM if the debian archives are broken10:58
ajmitchand put it on REVU10:58
ajmitchs/REVU/tiber/10:58
dholbachok, do we all agree that merges are really important and we will all focus on that?10:58
sivangbddebian: maybe you can bug elmo for us to provide a local version of a MOM ? :-D10:58
ajmitchdholbach: YES!10:58
Nafalloyea, cause Keybuk would NEVER share the existing code? ;-)10:58
\shdholbach: we have to...it's first task we should focus on10:58
sivangdholbach: yeah10:58
ogradholbach++10:59
ajmitchNafallo: I guess the code is fairly simple10:59
sistpotydholbach++10:59
sivangdholbach: how are you producing lists of packages that needs merges?10:59
dholbachif i might add a suggestion: before uploading a package it might be prudent to examine the bugs for the package10:59
ivoksuh10:59
dholbachsivang: will be on bugzilla10:59
ivoksi'm late10:59
Nafalloajmitch: still no need to discover the wheel again? :-)10:59
ajmitchthe problem is usually getting the debian package that we forked from10:59
=== sivang feels that he should be getting a debian box for this works
dholbachso if we can make a tiny change to fix a bug, do that with the merge10:59
ogradholbach, bah, who cares for bugs... 10:59
ajmitchsince snapshot.debian.net lost a lot of data10:59
dholbachogra: leave the channel, please ;)10:59
ogra:)10:59
sivanghehe10:59
ajmitchsivang: sid chroot10:59
dholbachAND:11:00
sivangajmitch: cool11:00
ograand ?11:00
dholbachwe might have   apt-get source -t   by then11:00
ajmitchAND?11:00
dholbachROCK11:00
ajmitch-t ?11:00
sivang?11:00
ograelaborate ? 11:00
dholbachlike in apt-get11:00
dholbachso you can have ubuntu and debian sources11:00
ograah11:00
ajmitchoh right11:00
sivangtarget release?11:00
dholbachand fetch the debian source just with apt-get11:00
Nafalloapt-get like in apt-get :-)11:00
dholbachsivang: mvo has it on his harddisk11:00
sivangdholbach: please xplain :)11:00
=== Nafallo understands less now ;-)
ajmitchwe *still* have the problem of getting the original debian source11:00
dholbachok11:00
ivoks-t targets release11:01
\shmm...11:01
ajmitch3-way merges need a base :)11:01
dholbachyes, so you do      apt-get source pornview -t sid11:01
ograeek, that means i need to have debian soures in my sources.list ?11:01
sivangivoks: yes, that what I saw with man apt-get /-t11:01
ivoksyou can have couple of releases11:01
ivoksand pick whichever source you want11:01
dholbachogra: no you don't, but i think it's a worthwhile feature11:01
NafalloI usually do apt-cache madison && apt-get package=version anyway :-P11:01
ajmitchdholbach: I just switch into my sid chroot with its bind-mounted dirs ;)11:01
dholbachespecially if you do apt-pinning11:01
\shI think the problem is more, when I'm thinking on our transitions, that the packages we touched are not done by DDs by now11:01
ograi dont11:01
dholbachdo whatever you like11:01
ivoksor apt-get source sid/pornview11:01
dholbachi FANCY it11:01
ajmitch\sh: most are11:01
ograi stay away from pinning as far as i can11:01
ivoksiirc11:01
sivangdholbach: how does it know where to fetch the package from if you don't provide it with the sources?11:01
dholbachsivang: you have to11:02
=== ajmitch thinks we're straying off-topic
dholbachyes11:02
dholbachi just liked the idea11:02
dholbachhowever11:02
dholbachwe agreed already ;)11:02
ograOK, BACK ON TOPIC11:02
dholbachthe last item on the agenda is:11:02
sivangdholbach: care to give me a session about that one afterwards? :)11:02
ivoksi tought meeting is at 22:00UTC :(11:02
dholbach Clean up and reorganization of MOTU wiki pages. (JordanMantha) 11:02
dholbachJordanMantha, are you there?11:02
=== LaserJock is Jordan Mantha
LoioshPing11:02
ajmitchdholbach: we need more agenda items, this meeting was meant to be about direction & discussion before UBZ11:02
siretarterr, sorry11:03
sivangI'm getting a cup of tea, be right back11:03
siretartwhat was the resolution to point3?11:03
ajmitchto get input from the MOTU community who won't be at UBZ11:03
ajmitchsiretart: get working ;)11:03
dholbachsiretart: we agreed to heavily focus on merging first (as soon as we have a merging list)11:03
ograsiretart, NO 1 prio is merges before UVF11:03
ivoksajmitch: i'm off11:03
bddebianajmitch: Why, you'll ignore it anyway.. ;-P11:03
Lathiatbtw, quick question, are .desktop files fair game to go upstream to debian?11:03
ajmitchdholbach: I have a preliminary list11:03
siretartokay. thanks11:03
ajmitchbddebian: stop trolling11:03
bddebianLathiat: They SHOULD be :-)11:03
dholbachajmitch: do you want us to decide on them?11:03
Lathiate.g. do debian care 11:03
LaserJockI just was noticing that the MOUTU was sort of newbie unfriendly and since we got done with Breezy I was wondering what might be done with cleaning/improving the wiki11:03
sivangdholbach: can I help out in writing a script to produce the merges list? (I take it you're doing it in python)11:04
dholbachajmitch: wouldn't it be better to collect the ideas on a wiki page?11:04
Lathiat(im writing up merge howto)11:04
ajmitchsiretart: I've got one already11:04
sivangdholbach: maybe even a spec?11:04
dholbachsivang: it should be already done, the stuff was on bugzilla (just search for merging)11:04
ajmitchs/siretart/sivang/11:04
ogra*********** leave the stage to LaserJock please *************11:04
=== koke is quite busy and would love a ping if we talk about UBZ :)
ograits his topic11:04
ajmitchdholbach: I just wanted ideas raised11:04
sivangdholbach: ok11:04
dholbachLaserJock: please :)11:04
TiMiDook i want to do something11:04
LaserJockwell, I am just a MOTU wannabe but I would like to help with wiki cleanup if I can11:04
LaserJockI just wanted input as to what would be good for you guys11:05
ograLaserJock, what are your suggestions11:05
dholbachthank you very much for that at first :)11:05
LaserJockI guess Lathiat is taking care of some stuff11:05
ograwhat should get changed... whats missing, what needs improvement ?11:05
LaserJockWell, we have 3 wiki pages for recruits11:05
ograyes11:05
ograsadly11:06
bddebianAye11:06
LaserJockit should be only 111:06
\sh3?11:06
ograwher does the third come from ? 11:06
LaserJockmaybe just 2 sorry11:06
dholbachwhat i wanted to take care of, for ages, is: having a "round trip" through all the pages, explaining what they are for, LaserJock, would that make sense?11:06
ograi only know dholbachs and mine11:06
=== \sh just knows pbuilderhowto and developerresources
LaserJockthe Todo page has lots of notes for MOTU but it is a little hard for newbies to figure out 11:06
sivangLaserJock: do you find the current instructions for packaging a source from scratch okay?11:06
\shbut that's me ...forget about me11:06
ograthe recruitment pages can get merged or rewritten11:07
LaserJockwell I think the packaging stuff could be improved11:07
\shsivang: IT'S NOT OKAY ;)11:07
dholbachsivang: i think there is none11:07
\shdholbach: there r two11:07
\shdholbach: one was mine, the other one is kubuntu doc for cdbs stuff :(11:07
Lathiatlol11:07
ograwhat about Unfrgivens developer docs ? 11:07
\shdholbach: mine is incomplete11:07
LaserJockwe should make sure that everything follows MOTU policy and is current (replace Hoary with Dapper or something more general)11:07
Lathiat\sh: well, kubuntu doc has some kde/kubuntu specific stuff11:07
ogracan we put them up somewhere ?11:07
Lathiat\sh: e.g. what to add to cdbs for kde11:07
ajmitchogra: yes, they are getting put up11:07
ogragreat11:08
\shLathiat: which is wrong in my eyes11:08
sivangmaybe we can get some of the more experienced folks in here to contribute on \sh's docs?11:08
Lathiat\sh: well, its needed11:08
Lathiat\sh: even if its a subset of a main page11:08
sivangmake them more complete11:08
sivang?11:08
ograajmitch, do they get in -updates ? 11:08
\shsivang: no..it's too difficult...I need to rewrite it 11:08
ograwe have fine "intro developer docs" 11:08
\shLathiat: yeah..for people who knows how debhelper works11:08
dholbachhow about this: we go and categorize MOTUCategory pages and merge stuff that can be merged and write a general page, which should be part of /MOTU, that describes what is in each category?11:09
ograthey have been packaged but were to late for breezy11:09
ajmitchogra: no way11:09
ajmitchogra: they didn't pass NEW for breezy11:09
LaserJockWhat I would like to see is a self consistent, easily navigatible, and non-redundant set of wiki pages that has info for not only MOTUs but also MOTU wannabes11:09
ajmitchtoo late11:09
ograi'd suggest we'd look over them and enhance if needed before we start new stuff11:09
ograajmitch, -updates ? 11:09
dholbachisnt that, what i said?11:09
ograajmitch, i'll go begging at mdz11:09
ajmitchwiki pages cover *way* more than packaging11:09
ajmitchogra: good luck, I think he'll say no11:10
dholbachfyi: https://wiki.ubuntu.com/CategoryMOTU11:10
ajmitchthe wiki has to cover all the bits about getting involved, what we do, what there is TODO11:10
ograajmitch, i'm used to... you didnt see my bleeding knees yet that edubuntu brought me :)11:10
LaserJockone other thing that is confusing (at least for me) is that the MOTUTodo doesn't seem prioritized 11:10
ajmitchIntroDeveloperDocs is targetted specifically at new packagers creating a package11:10
dholbachLaserJock: ++11:10
ajmitchMOTUTodo needs wiped & redone11:10
ograyes11:11
dholbachok, how do we proceed, who wants to give LaserJock a hand?11:11
siretartthere are many transition pages11:11
ograwe still have no RT 11:11
siretartI'd propose to drop them11:11
ajmitchogra: do we need RT? it can be setup easily on tiber11:11
bddebianRT?11:11
ogracouldnt MOTUTodo be replaces with a RT instance on the revu server ?11:11
dholbachlaunchpad! :)11:11
siretartrequest tracker?11:11
bddebianAh11:11
ajmitchsiretart: yes11:11
ograyes11:11
\shbddebian: RequestTracker a perl tool and a nice one11:11
sistpotysiretart++ go for ghc6-transition first :)11:11
siretartReinhard Tartler? ;)11:11
dholbachrt sucks :)11:12
ogradholbach, ??11:12
siretartfor what would we need rt?11:12
ajmitchany one of the tiber admins can set it up if we agree11:12
ograsiretart, UniverseCandidates11:12
\shajmitch: u r one ;)11:12
ograsiretart, a morgue list11:12
dholbachan rt request for each package that needs love?11:12
dholbachjust think about UniverseFTBFS11:12
dholbachbut anyway11:12
ograall the stuff we need lists for...11:12
dholbachthis gets a bit offtopic11:12
ograwhy ? 11:13
dholbachwe're here to organize our documents11:13
siretartwouldn't it make less work to create a python script installed on tiber than install rt?11:13
dholbachthat's more important than the workflow, at least for newcomers11:13
siretartdholbach: this IS about organizing documents11:13
ogradholbach, or drop them in favor of something better ;)11:13
ajmitchsiretart: such as?11:13
dholbachdocumentation11:13
dholbachsorry11:13
ajmitchsiretart: what python script would you want?11:13
siretartdholbach: we are talking about potential replacing wiki pages by other means11:13
ajmitchthis is about replacing sections of the wiki with other, better tools11:13
siretartajmitch: morgue list11:13
ogradholbach, MOTUTodo is a internal workflow page.. but wannabes will find it and get confused11:14
siretartajmitch: and UniverseCandidate have been mentioned11:14
sistpotyunmetdeps11:14
ograyes11:14
siretartajmitch: SyncCandidates would be another candidate11:14
dholbachftbfs11:14
ogra++11:14
Nafallotiber == internal workflow wiki? :-)11:14
ograNafallo, nope11:14
ograno wiki there11:14
ajmitchI was working on an unmet deps resolver to keep the list fresh11:14
ogra*tools*11:14
dholbachso we'll have an RT request for every package to fix?11:15
siretartajmitch: that would really be great. it is quite high on my list..11:15
Nafalloogra: not now... but it would be a possibility if MOTUTodo is such a confusing page, no? :-)11:15
ajmitchso that it could scan the universe/main package list & generate a list of packages that wouldn't install11:15
ogradholbach, that would obsolete maolne :)11:15
ajmitchcode is about 75% written :)11:15
siretartajmitch: my hero! :)11:15
sistpotyajmitch++11:15
LaserJockwhat about UniversePackageWithoutDesktopFile?11:15
ograNafallo,  dont think its a good ide to replace a wiki with a wiki11:15
=== ajmitch has had a few script ideas ;)
dholbachso could we agree on testing RT for our purposes?11:16
ograyup11:16
Nafalloogra: in most cases no, but it could be in this one. anyway, I'm fine with MOTUTodo whereever it is :-)11:16
siretart*sigh*11:16
dholbachis it hard to set up?11:16
ograand wipe all workflow stuff from the wiki eventually11:16
=== siretart doesn't like the idea of rt that much
dholbachi don't have used it much11:16
\shdholbach: it's a bit of "frickeling"11:17
dholbachso i'd like to see in action what we're talking about11:17
\shwith perl and some alias lists11:17
ograNafallo, lists on wikis are unusable if they reach a certain size11:17
Lathiatwouldnt like11:17
Lathiatbugs in launchpad11:17
siretartogra: how can rt assist with that?11:17
Lathiatassigned to some meta-user for this kind of things11:17
Lathiatbe better?11:17
ogradholbach, you havent used it much ? 11:17
dholbachLathiat: we'd need mass-filing stuff11:17
dholbachogra: no11:17
Lathiatlaunchpad has an email interface11:17
Lathiat = easy mass filing11:17
ajmitchdholbach: malone email UI11:17
ogradholbach, all internal canonical requests go over rt ...11:17
dholbachok11:17
dholbachogra: i know11:17
Nafalloah well, nm :-)11:18
dholbachogra: how often did you use it?11:18
LaserJockok, so what do you guys want me to do?11:18
ajmitchwe can mass-file, do nearly everything to bugs that you can through the web UI11:18
ogra2 times :)11:18
Lathiatactually it would be better filed against a meta-package11:18
dholbachogra: you see...11:18
Lathiatand then you can assign something to yourself11:18
Lathiatif you are working on it11:18
dholbachOKOKOK, what are our proposals?11:18
\shI used it as support ticketing system for 3 ISPs11:18
dholbachwe cannot agree on something that's not there11:18
Lathiatwhere meta-package could just be some 'product' or whatever concept launchpad has11:18
dholbachthere's no transition, if we don't have something yet11:18
\shLathiat: team not product11:18
ografirst lets give LaserJock something in his hands11:18
dholbachi'd very much like to get back to documentation11:18
ajmitchok, back to WIKI cleanup please :)11:18
Lathiat\sh: but can you file a bug *on* a team11:19
ajmitchLathiat: shh :)11:19
Lathiat\sh: assigning is no good, then you cant assign it to yourself to work on11:19
\shLathiat: later11:19
dholbachbecause that's more important, even if not as appaling as tools to some of you :)11:19
ajmitchwe agree that the wiki needs love11:19
ajmitchnew contributors find the wiki confusing11:19
ajmitchLaserJock's point was that the wiki is useful for 'insiders' who already know their way around11:19
ograi'd say lets first have a list which is workflow and which is doc... then clean up the doc pages11:19
ajmitchbecause that's who has written the wiki pages11:20
dholbachwho would give LaserJock a hand at looking at CategoryMOTU and merge, where we can?11:20
Nafalloogra++11:20
sistpotyanyone disagrees with removal of ghc6transition page? (it's done :)11:20
Lathiatworkflow pages can probably be largely purged11:20
dholbachsistpoty: trash it11:20
ajmitchsistpoty: all part of the cleanup11:20
ograsistpoty, why is it still there ? 11:20
sistpotyogra: been lazy with the wiki *g*11:20
ogra;)11:20
Nafallohistoric reasons? ;-)11:21
ajmitchall of us have been lazy with the wiki11:21
ajmitchexcept maybe dholbach ;)11:21
sistpotyhehe11:21
bddebianSpeak for yourself :-)11:21
Nafalloso that we can look back in teen years and laugh? :-)11:21
ajmitchoh, and bddebian 11:21
dholbachLaserJock: how would you proceed?11:21
ajmitchour MOTU God11:21
bddebianpfft11:21
=== ogra hands LaserJock the mic
LaserJockI think that we should have a wiki that has lists of wiki pages MOTU/Wannabes want to see11:22
LaserJockand ones we need to get rid of11:22
dholbachyeah11:22
ogragreat11:22
LaserJockThen I can work on them11:22
LaserJockI am willing to do work, I'm just want to make sure I don't mess up something important11:23
dholbachLaserJock: you can always ask in the channel11:23
ograLaserJock, its a wiki11:23
dholbachand i'm quite happy you take that role11:23
Lathiatif you break it, you can unbreak it, i think11:23
Lathiatdholbach++11:23
ograit has version control as long as hno73 doent mess it up ;)11:23
LoioshHeheh, yes11:23
siretartperhaps we can regroup all workflow pages under MOTU/Workflow/<TOPIC>?11:23
ajmitchwe can't leave it up to LaserJock alone11:23
LoioshYou can undo changes.11:23
dholbachsiretart: excellent idea11:23
Lathiatlaserjock and whip other people11:24
=== Lathiat will do some work
dholbachi wanted to do that too11:24
Loioshwiki calls it a 'revert'11:24
dholbacha directory structure11:24
dholbachi gues that'd help11:24
siretartsame for MOTU/Transition/<TOPIC>11:24
dholbachMOTU/Doc11:24
dholbachMOTU/Wannabe11:24
ograyeah11:24
dholbachMOTU/Process11:24
\shwell...it would be nice to see some real documentation work for motu pages...finally I'll ping some of the german wiki guys and ask for help11:24
NafalloMOTU/Teams :-)11:24
ograheh11:25
dholbachyeah11:25
ajmitchespecially as MOTU is seen as the entry point for ubuntu development11:25
dholbachwoohoo11:25
dholbachajmitch: ++11:25
ajmitchso we need to make it as appealing as possible :)11:25
dholbachit's a shame in which state some pages are11:25
=== sistpoty hides
ajmitch:)11:25
Nafallolot's of them talk about hoary and warty still ;-)11:25
ajmitchyep11:25
Lathiatunfortunately the whole wiki is generally a mess11:25
dholbachok... LaserJock is that cool for you?11:25
Lathiatbut if we want to get anywhere we will need to focus on MOTU stuff of course :)11:26
ajmitchand breezy is old news now ;)11:26
=== ogra is happy he only has to care for wiki.edubuntu.org currently :) it small
LaserJockdholbach: sounds good to me11:26
dholbachLaserJock: excellent11:26
dholbachajmitch: do you still want to collect items for ubz?11:26
dholbachajmitch: or can we agree to announce the wiki page here?11:26
LaserJockI think I will make an organizational wikipage and link to it on the MOTU page so you guys can add/remove stuff you want, OK?11:26
ogradholbach, announce the wiki page ? 11:27
dholbachLaserJock: excellent, and thanks again11:27
ajmitchdholbach: as UBZ is Real Soon Now, I'd like to hear a few minutes of ideas11:27
ajmitchand put them on the wiki page11:27
dholbachogra: for IdeasForMOTUUBZ11:27
dholbachok11:27
Lathiatfor those that cant attend :(11:27
dholbachajmitch: go ahead11:27
ajmitchsince some discussion will help to get it going11:27
Lathiatit woudl be nice to get a drawup of new interaction in dapper11:27
Lathiatlike with launchpad etc11:27
ogradholbach, we have https://wiki.ubuntu.com/UbuntuBelowZero/BOFs, why not add it there ? 11:27
dholbachogra: it's ajmitch's agenda item11:28
siretartthat page is quite busy/crouded11:28
ivokskoke: ping UBZ :)11:28
\shfirst idea: Every MOTU gets a lifetime support of Aspirin11:28
ajmitchLathiat: MOTULaunchpadPackages? ;)11:28
kokeivoks: thx11:28
Lathiatajmitch: heh11:28
Lathiatok11:28
ajmitchs/Packages/Processes/11:28
ajmitch\sh: ++++11:28
ajmitch;)11:28
ograajmitch, why not use https://wiki.ubuntu.com/UbuntuBelowZero/BOFs ?11:28
ajmitchogra: sure11:28
\shajmitch: *g*11:29
ajmitchas we know, dapper is going to be supported for 3/5 years11:29
ajmitchwhat can we really focus on to make it rock?11:29
=== Nafallo has still not figured out what will be left the last 2 years ;-)
Lathiati think first and foremost should be cleaning things up11:29
Lathiatgettin gmerges out of the way11:29
ajmitchfirst up is how to get new people involved..11:29
Lathiattrying to fix as many leftover unmet deps as possible11:29
ajmitchand doing the merge & bug work11:29
Lathiatgetting rid of as many merges as possible / simplifying them11:29
Lathiatand try do them ASAP, instead of last-week rush 11:30
kokeI'd like to work with someone else in the Ruby team11:30
=== ajmitch waits for some radical suggestions from the floor
NafalloLathiat++11:30
Lathiatkoke: we have a ruby team11:30
ivoksstop including new packages11:30
ajmitchLathiat: that was on the agenda ;)11:30
Lathiatkoke: we havent really done much yet11:30
ivoksand only fix remaning11:30
ograLathiat, we wont have a choice in dapper, th relese schedule will fully apply to universe11:30
kokeI know, but I'm not sure if someone from the team will be at UBZ11:30
Nafallo\sh: will we have time with everything? :-P11:30
Lathiatogra: "last week before UVF rush"11:30
Lathiatogra: etc11:30
ograso merges have to be done at a certain date11:30
ajmitchivoks: that's an option11:30
ajmitchLathiat: so start on merges asap11:31
\shNafallo: I don't think that our spec will be a dapper "goal"...so it's deferred by default ;)11:31
ivoksajmitch: with new i'm thinking on REVU :) not new versions11:31
Lathiatajmitch: when merges happen! ;)11:31
Nafallo\sh: baah :-P11:31
ograbut that will scare people away... new people want to include new stuff... dholbach and i had this discussion plenty of times11:31
bddebianYeah but some merges come back to "just syncing Debian" ;-P11:31
=== bddebian hides
ajmitchivoks: I think that we need to get new packages to attract new developers11:31
ajmitchat least up until UVF11:32
\shas I said, at sometime we have to split the strength of the team...11:32
ajmitchafter that we have to say no11:32
ivoksajmitch: but definitive no11:32
ajmitchor no, with exceptions ;)11:32
ivoksajmitch: no "just this one"11:32
ajmitchunlike the non-UVF that we had with breezy11:32
ograyup11:32
ivoksyeah...11:32
ajmitchI think it can still be worth getting packages in after UVF, if they're well done11:32
ivoksuploads in last hour11:33
ograajmitch, depends...11:33
ajmitchogra: sure11:33
ivoksone more thing11:33
dholbachif i see it correctly, the release process for dapper for main isnt even clear yet11:33
ivokswhen dapper+1 opens11:33
ograajmitch, if we need mdz/Kamion approval at least *i* wont bother them with it11:33
ajmitchogra: I'm just arguing that a blanket NO can be detrimental :)11:33
ivokswe have to do more backports than now...11:33
\shivoks: backports are a special topic11:34
ograivoks, thats Mez's job11:34
ograwe dont have to care..11:34
ivoks:)11:34
\shivoks: we need all motus to help us for merges and other things...where merges*1000 prio11:34
ivoksok11:34
ajmitchogra: yes, I don't think mdz & kamion will take on the universe burden as well11:34
ograbut we should get jdong into motu finally11:34
ograajmitch, exactly11:34
ajmitchogra: perhaps you'll end up being the MOTU in charge of approvals ;)11:34
ajmitchor dholbach 11:34
LoioshHahaha11:34
bddebianheh11:34
\shivoks: because for breezy we were only a few 11:34
ograajmitch, surely not... else edubuntu will suffer11:34
=== Loiosh offers ogra aspirin.
ograLoiosh, i cant 11:35
ajmitchogra: ok, some other community member like \sh 11:35
ograyup, good suggestion :)11:35
LoioshHeh11:35
\shwhat?11:35
Lathiatif (member != ogra) echo good suggestion11:35
\shajmitch: what u want from me?11:35
ivoks\sh: you'll do all the work :)11:35
=== LaserJock thinks ajmitch might just volunteer himself
=== Loiosh offers \sh aspirin.
Nafalloprobably ogra AND dholbach :-)11:35
dholbacherm....11:35
=== ogra orders a truck with aspirine for \sh's address
dholbachcan't we make a list of topics, briefly? :)11:36
ajmitchLaserJock: no, I'm not going to volunteer myself, I'd have to be nominated by others :)11:36
ajmitchdholbach: please :)11:36
ogradholbach, UVF exception approvals...11:36
ajmitchthis is going OT again ;)11:36
ograyes11:36
=== \sh needs a house in durban, sea side, near coconut grove and a big fat pipe for uploading..that's all...possible?
dholbachogra: i'm not taking notes :)11:36
=== bddebian nominates ajmitch
Lathiatwe were ever on topic? ;)11:36
ogradholbach, me neither11:36
dholbachi will have a presentation to prepare11:36
ivoksi thik exception should be stuff like ipod support etc11:37
dholbachso i'd like to wrap up, if we can't agree on how to handle pre-ubz-business11:37
Nafallowhat IS the topic? :-)11:37
ivokssince apple has tenedency to change stuff periodicly11:37
ajmitchNafallo: UBZ suggestions11:37
ajmitchI was asking for people to (briefly) suggest topics for UBZ, that we'll put on the wiki11:37
ajmitchthe briefly part got lost somewhere under my desk11:38
Nafalloand how many do we have? :-)11:38
ivoks:)11:38
ajmitchNafallo: about 1/211:38
Nafallohmm, that must be \sh's aspirin then...11:38
dholbachok. shall we agree on a wiki page for "brief ideas" and agree on a time and date for next meeting?11:39
LoioshNominate a member to be considered for post-UVF approval?11:39
Nafallowell, I already now what I'm going to do in dapper so... ;-)11:39
ajmitchdholbach: yes11:39
ograLoiosh, that should be absolute exceptions...11:39
ajmitchnext meeting will be during or after UBZ11:39
dholbachok, suggestions?11:39
Lathiatoh11:39
sivangdholbach: what is the presentation about?11:39
Lathiatquick Q11:39
Loioshs/approval/absolute exceptions/g11:39
Lathiatcan we irc mirror the ubz meeting? :)11:39
dholbachsivang: berlinux, ubuntu community11:40
Nafallodholbach: make clones of mdz and Kamion.11:40
ograLathiat, that was the plan iirc11:40
Lathiator does anyone have a spare few grand lying around to send me? ;p11:40
ajmitchLathiat: if needed, but we'll have quite a few BOFs11:40
\shLathiat: if there is a motu bof or meeting we will pushit via irc, i think11:40
Nafallodholbach: atleast there role for main should be someone in Universe :-)11:40
ajmitchsorry, I blew my last bit of cash to send myself ;)11:40
ivoksogra: that would be nice, since some of us can't attend ubz11:40
\shNafallo: choose one of 4 ... dholbach , ogra, ajmitch , \sh11:40
ograivoks, yes11:40
sivangdholbach: ah, intersting, UBZ spec?11:40
Nafallo\sh: yes, those sounds fine :-)11:41
=== sivang googles for berlinux
\shNafallo: exclude me ;)11:41
Nafallo\sh: noway dude! ;-)11:41
\shNafallo: I'm not compatible with TB ;)11:41
ivoksogra: just conclusions would be enough11:41
ajmitch\sh: and of those, ogra & dholbach & \sh & ajmitch are very busy ;)11:41
ogra\sh, hewy, you only have KDE to care for, we others have important tasks :)11:41
Nafalloajmitch: but mdz and Kamion isn't? ;-)11:41
dholbachok, what about the name for the wiki page for the suggestions?11:41
\shogra: *lol*11:41
dholbachand what about the time and date for next meeting?11:41
ogradholbach, at UBZ ?11:42
=== sivang voulenteers for approving exceptions :-D
ograi think we said that lats time11:42
\shogra: I think I had more != KDE uploads to main then expected 11:42
ivoksogra: yes!11:42
ivoksat ubz!11:42
siretarthow about some means of enforcing approval?11:42
dholbachok, time and date?11:42
ajmitchogra: yes, at beer o'clock in 2 weeks? :)11:42
ajmitchsiretart: a big stick?11:42
ogradholbach, probably dynamically or do *you* know the schedule yet ? 11:42
ivoksnot in the end of ubz11:42
dholbachno, that's why i ask11:43
Nafallodholbach: so... the MOTU core team as exception approvers for Universe please :-)11:43
dholbachyou seemed to know :)11:43
ajmitchsiretart: enforcing approval is hard, we can't upload to a frozen queue that someone can moderate11:43
ograwe should announce a date if we are there and know the schedule11:43
ajmitchsiretart: not unless we do some fast talking with mdz & kamion11:43
dholbachok11:43
ajmitchogra: good idea11:43
ivoksdholbach ogra somewhere in the middle, so rest of us can make some suggestions11:43
siretartajmitch: perhaps this is something for your ubz list, then11:43
Nafalloajmitch: do that talking with them on UBZ then?11:43
ograso between oct 26th and nov 7th11:43
ajmitchsiretart: ok11:43
=== ajmitch writes beer with ogra, dholbach & others on his list
\shNovembre 1st?11:44
ivoks:<11:44
sivangogra: not on 7th, I'm leaving on the 6th :-/11:44
\shogra: 6th11:44
siretartbut the suggestions with the big stick seems fine to me11:44
ajmitchogra: oct 26th? that's far too early11:44
\shogra: siretart and I are leaving on the 6th11:44
ogra\sh, do *you* know what we'll have ion schedule on Nov 1st ?11:44
ajmitch\sh: msot people check out about the 6th11:44
dholbachlet's announce it on the mailing list11:44
dholbachor on the irc topic11:44
=== ajmitch doesn't arrive till the 29th
sivangogra: my birthday ? :-)11:44
\shogra: well...the night dude ;)11:44
sistpotydholbach++11:44
dholbachwe're not getting somewhere now :)11:44
Loiosh1st is my birthday11:44
ajmitchdholbach: good idea11:45
ivoksdholbach: :)11:45
\shdholbach: of course...to bed ;)11:45
dholbachand i'm pretty tired and have to get on with work :)11:45
ajmitchdholbach: I *really* have to get off to work & my real-life job11:45
sistpotydholbach: /me prefers mailing list ;)11:45
dholbachajmitch: me too11:45
ajmitchit's nearly 11AM here, I'm about 2 hours late11:45
ograok, we'll put it in the topic of -motu 11:45
dholbachsistpoty: we can do both11:45
ograonce we know the schadule11:45
ivoksdbboth11:45
ivoksdholbach: both11:45
dholbachok11:45
sistpotyyeehaa... i almost never look at the topic :(11:45
ivokswrap it up11:45
dholbachok, thanks everybody for coming11:46
dholbachhave a nice day11:46
ivoksnight11:46
Lathiatthank you all for coming DONT FORGET UBUNTU BUG DAY11:46
ograsistpoty, you'll do then11:46
ivokstoo11:46
ajmitchok :)11:46
ivoks:)11:46
ajmitchLathiat: what day? ;)11:46
sistpotyogra: I'm not on UBZ ;)11:46
sivangLathiat: when?11:46
NafalloLathiat: Ubuntu WHAT? ;-)11:46
dholbachnow/tomorrow11:46
Lathiatsivang: #ubuntu-bugs, now!11:46
ograsistpoty, thats why you'll look at the topic then :)11:46
dholbachhttp://wiki.ubuntu.com/UbuntuBugDay11:46
sistpotyogra: or do you mean looking at the topic *g*11:46
ivoksbye11:46
sistpotyhehe11:46
dholbachbye11:46
ajmitchok, who wants to write up the meeting summary this week?11:46
Lathiatanyone who doesn't give at least 20 bugs attention gets stared at evilly11:46
=== dolmen [n=dolmen@cho94-1-81-57-157-99.fbx.proxad.net] has joined #ubuntu-meeting
ogradoes someone feel eager to write up the minutes ?11:47
ajmitchogra: I can if you want11:47
ograwould be nice...11:47
=== ajmitch will get the evil stare, only touched 1 bug today
bddebianI can't unfortunately, I've been too distracted with RL work. :-(11:47
ograbut take as much time as you need :)11:47
dholbachLathiat: read the wiki page :)11:47
ajmitchogra: will look at it in weekend then11:47
dholbachLathiat: you're taking the wrong approach11:47
ograajmitch, take your time11:47
dholbachok guys... see you11:47
Lathiatdholbach: heh11:47
ajmitchbye dholbach 11:47
siretartgrrr. disconnect without noticing :/11:47
sistpotygn8 dholbach11:47
ajmitchogra: long weekend for me :)11:48
=== dholbach [n=daniel@i577B0EAC.versanet.de] has left #ubuntu-meeting ["Ex-Chat"]
ograok, meeting closed :)11:48
ajmitchyay11:48
ograthanks all for attending11:48
\shwell...11:48
LathiatLOL11:48
Lathiathug day!11:48
siretarthrhr11:48
Lathiati like the evil stares option personally11:48
=== \sh will have the next days a lot of RL work to do :(
siretartbye folks11:48
=== ajmitch will bbl
\sh26th is my last day of RL stress work :(11:49
sivang\sh: I had time like this 2 weeks ago, was icky :-/11:49
sistpotybye siretart11:49
sivangnight sistpoty 11:49
sivangnight siretart 11:49
bddebianGnight folks11:49
\shsivang: well...we're preparing for a new channel line up for two german counties11:49
LoioshWow11:49
\shsivang: digital television :( 11:49
\shsivang: and our german pay tv company named premiere wants to change to hdtv as well during these days...11:50
\shit's a mess11:50
sivangbah, too much transitions eg?11:50
\shsivang: yeah...cxx trans + ftbfs in 3 days11:51
\shand a bunch of meetings with all those people who don't have a clue..but wants to have a say11:51
LoioshHeh11:52
\shshit...this channel is logged...but I never mentioned ISH ,->11:52
bddebian:-)11:52
\shogra: help...I'm playing with my career 11:53
ogra\sh, good :)11:54
\shhmm..11:55
sivang\sh: lol11:55
\shogra: u didn't push klaus onto my back, to give me good piece of advises to leave the company? ,-)11:55
\shpieces of advise even11:55
sivang\sh: this is SO much known , for me as well :-/11:56
ogra\sh, not yet... thats still to come... my last resort if you want :)11:57
\shogra: he starts already since I know that he is leaving...12:03
\shanyways...12:03

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!