=== 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 [09:14] !meeting set TechBoard 1 Nov 20:00 === ..[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 [09:15] argh...a bug with Ubugtu. It doesn't sort months properly (Nov before Oct) === ..[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 [02:00] **Reminder** Edubuntu Update Meeting here, now. === mhz is present, Miss [02:01] :D === flint [n=flint@static-66-160-92-78.dsl.cavtel.net] has joined #ubuntu-meeting [02:01] watching :) [02:02] goog morning jane... [02:02] hi flint [02:02] is ogra in the house? === pips1 [n=philipp@241.1.203.62.cust.bluewin.ch] has joined #ubuntu-meeting [02:03] where the heck is ollie? morning ealden... === segfault [i=carlos@prognus.com.br] has joined #ubuntu-meeting [02:03] hi all [02:03] hello flint [02:03] whoops [02:03] ok well first things first... [02:03] Edubuntu 5.10 is out!!!! [02:04] yeah [02:04] congrats [02:04] woohoo! [02:04] Thanks to EVERYBODY who contributed [02:04] and we already have some fairly good press :) [02:04] :-) [02:04] absolutely a good thing... [02:04] we really appreciate it [02:04] and thanks especially to Mr Edubuntu himself ogra! [02:04] whoot whoot [02:04] heh, thanks :) [02:04] we'll start using Edubuntu here in Brazil, in the so called "Telecentros"! [02:04] indeed! [02:04] segfault: great! [02:05] ogra: so can you make a call on the CD? [02:05] are you happy that we press it as is? [02:05] hi [02:05] hi ajmitch [02:05] I am putting a copy up at the Arlington Housing Coalation. === ajmitch should *not* still be up & awake for this meeting :) [02:06] i'm not really 100% convinced we should do it, but the feedback seems to say different... so lets go for it === 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 [02:06] ogra: do you want to wait a few more days? [02:06] how much of that feedback is from people who would use the cd? [02:06] does anyone else want to comment? [02:06] and not just people wanting a free cd? [02:07] JaneW, how many requests like the one from madagascar i forwarded do you have until now ? does it cover some thousand ? [02:07] ogra: that's the only really direct one [02:07] hmm [02:07] asking for 100 [02:07] thats not really moch [02:07] *much [02:08] Regarding 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] flint, we have approval for some thousand CDs ... [02:08] flint, but ... [02:09] But? [02:09] we need to keep track exactly who got them, in which amount, and if it fails, we'll never get money for it again [02:09] and no one has bothered to submit anything to http://wiki.edubuntu.org/EdubuntuShippingPlans [02:09] JaneW: 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:10] which is a pre-req for our printing approval, sabdfl wants to review the plans. [02:10] flint, so if we have the option for only one CD in edubuntu's lifetime at all, i'd rather go with next release [02:10] mhz: sounds great [02:10] so wee need cd's:) [02:10] the german community saked me for some edubuntu talks on one of the 15 fairs they attend... [02:10] mhz: agreed [02:11] thx [02:11] ok kidos, then which educational segment are you going to target? primairy, secondary or college? [02:11] and or t-shirts :D [02:11] so the requirement seems to be there... but its hard to keep track who got how many Cds if you give them out on fairs [02:11] the 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 SHOW [02:11] ogra: agreed [02:11] flint, you were at the summit, you know what we target [02:12] flint: it seems primary with this release, as the reviews have mentioned its very junior school friendly [02:12] i think currently we dont really target colleg [02:12] e [02:12] ogra: 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's [02:12] secondary age students will possibly find it too juvenile...? [02:12] mhz: your approach is good, more hands on and more likley to result in something [02:13] mhz, but can this cover "some thousand CDs" ? [02:13] ogra: rem it;s no more than 500 per country [02:13] i think that the technology would facinate at any level. [02:13] we need to get them all out to somebody... else it wont happen again [02:14] I think a free CD should accompany every proposal delivered to a school adminsitration.... [02:14] so my concern is that this release is very young, even if people dont seem to notice... [02:14] guys 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/EdubuntuShippingPlans [02:14] ...note first use of the word proposal. [02:14] if we get that sorted we can press the CDs and I think we can easilly move them [02:14] the next one will have more gui tools more management software and be a lot more polished [02:14] Dear Jane, a lot of us have to work for a living... [02:15] ogra: 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] so, 500 cd tops sounds good [02:15] mhz, i understand... but still, if we fail we wont have the chance again [02:16] so i try to be very careful with this opportunity [02:16] ogra: 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:17] mhz, thats not the point.... [02:17] can you assure that 500 schools want a CD ? [02:17] nop. [02:17] 500 teachers and more? Yes [02:17] ok, lets tackle this as follows, if you want CDs, get the proposal in... [02:17] ollie, that is why you need proposals. This situation is different from ubuntu. it is about schools adminstrators not hackers... [02:17] and thats the hard part... we need to make sure that there are some thousand people in the world wanting a CD [02:18] we 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] if we fail with this, we'll loose the opportunity to do it with the more polished version [02:18] jane, 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] I think 100 cds limit is enough [02:19] segfault, 500 per country... [02:19] thats our limit that was set .... [02:19] nice, but 100 per person [02:19] heh [02:19] so 5 ppl per country :) [02:19] JaneW: current gov. is supporting Edulinux (rpm's) because nobody else has presented another alternative. That we'll do. [02:20] hehe [02:20] flint: Mark just wants to see a plan for WHAT THE CDS ARE INTENDED TO BE USED FOR === jsgotangco [n=jsg@202.138.168.170] has joined #ubuntu-meeting [02:21] janew, 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] haloo [02:21] drafting a proposal to approach a school with would be great, but I need ppl to justify why I should send them CDs to distribute [02:21] JaneW: ok. he'll have that from us no later than tuesday. [02:21] flint: no that's not what we are doing [02:22] flint: read the 2 wiki pages, we will distribute to one of our edubuntu LoCo memebers who has prepared a distribution plan for his country [02:23] the LoCo person will be the edubuntu hub in their country and will handle the distribution as they see fit, though school, demos, events etc [02:23] mhz: great thanks [02:23] JaneW: Does that mean I gotta become a LoCo memeber? [02:23] ouch i have no time for that :) [02:23] mhz: no not necessarily [02:23] janew, you are creating web documents faster than I can read in my spare time... === mhz relaxes a byte then [02:23] ok 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:24] flint, read them at work then :) [02:24] we'll take it from there === jsgotangco twiddles fingers [02:24] mhz: 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... === mhz agrees and understand JaneW and ogra 'S POV. [02:25] the good thing about all this publishing is I can ask Jane what url is a good t-shirt logo? [02:25] jsgotangco: you get your proposal in too! :P [02:25] in fact for germany it is the loco team that talked to me [02:25] flint: you making edubuntu shirts? [02:25] JaneW: errr...i just need around 100 i don't need that much.... [02:25] i'll poke them to fill out the wikipage [02:25] JaneW: even 10 will do for me...i got a burner :P [02:25] JaneW, you got a logo? [02:26] flint, its on the wiki [02:26] flint: did you see my edubuntu cake? http://www.flickr.com/photos/13916877@N00/52389874/ [02:26] ok let's move on... [02:26] JaneW: what IF we reduced CD's printing/shipping to only 200, top. BUT we invest the rest of $ on T-shirts ? [02:26] ollie, saying it is on the wiki is like saying it is on the computer... n:^) [02:27] mhz: I am not sure that's an option, but we can ask... [02:27] ok UBZ [02:27] I have now read your plans. jane, will this distribution method penetrate into school systems? [02:27] flint: search -> title should do :) plus it right on index page :D [02:27] mhz: not a good idea, you *can't* reproduce t-shirts for people [02:27] UBZ is fast approaching, we need to make sure we have all required BOF topics [02:28] well its not like we'll be there :P [02:28] i have listed my three main goals ... (centralized user management, thin client local devices, thin client sound) [02:28] jsgotangco: 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 teachers [02:28] we 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 completed [02:29] essentially the distribution method is a further constrained version of the ubuntu distribution method [02:29] I got a tee shirt company around the corner, give me the url for a logo. [02:29] ogra: will it be feasible to target an entire school architecture in 6.04? [02:29] JaneW, sure... [02:29] JaneW, that is a UBZ question and will require beer in the answer. [02:30] you can do that now if you want, but it involved knowledge [02:30] we have schooltool.... [02:30] JaneW: 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] its just shuffliny the pieces right and integrate them [02:30] http://wiki.edubuntu.org/EdubuntuLogo [02:30] don't start about schooltool i was on the kb with Tom yesterday. [02:30] AHHH [02:31] JaneW, Thanks!!! This way I get the logo correct (for once!) [02:31] Tom was less than nice about some of his comments about edubuntu... 'aesthetic disaster'! [02:31] gotta get an audio feed from the bof onto the net. any ideas ollie? [02:31] JaneW, the main point for school management is centralized usermanagement... if we got that in and working, we're 80% done... [02:32] ogra: great [02:32] ogra: is there any chance squeak will be sorted out for 6.04? [02:32] not really... i can add new images, but thats all, we cant ship it [02:32] people who live in grass housees should not get stoned jane, that is all i will say about that. [02:33] the license doesnt allow us to put it anywhere else than multiverse, so by default you have to do some manual work to even install it [02:33] its much easier to actually run squeak in windows [02:33] has everyone here seen our new site and wiki designs btw? [02:33] jsgotangco, yes... [02:34] ogra: are they not going to change their licensing stance? === Topslakr [n=Topslakr@24-54-42-180.lndnnh.adelphia.net] has joined #ubuntu-meeting [02:34] JaneW, squeak is nearly 10 years old, they didnt change it until now even many people requested the change... i doubt it [02:34] its not like its that easy... [02:34] JaneW, you mean http://www.edubuntu.org/ [02:34] yes [02:35] flint, and wiki.edubuntu.org [02:35] Edubuntu website look and feel is very good. Esp. considering is running Moin underneath [02:35] squeak rocks...what is the license problem? [02:35] flint, it forbids direct shipment [02:35] and it makes the fonts non-free [02:35] and i believe some of the fonts too [02:35] that is wierd... [02:35] yes [02:35] but unlikely to change [02:36] just 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] ogra, telepathic shippment is still ok then? [02:36] its well established and we're a tiny speck at the moment.. [02:36] http://wiki.edubuntu.org/EdubuntuCdAndSlip [02:36] This License allows you to copy, install and use the Apple Software on an unlimited number of computers under your direct control. [02:36] CD's/ yes, please comment on that so I can do changes and close that chapter :) [02:36] ^^^^ thats the main prob [02:37] we dont have direct control to any of our customers PCs... [02:38] ollie, these are not PCs they are servers... [02:38] there is an EXHIBIT A that allows distribution without shipping .... that why we can have it in multiverse but not on the CD [02:38] CD 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] ogra: anything packaging-related you want help with for dapper? [02:38] it is a pretty design, I gotta admit. cute kids and all. [02:39] ajmitch, sure, everything packaging related :) [02:39] thanks [02:39] heh [02:39] ;) [02:39] ollie, is there a live cd with edubuntu? [02:39] nope [02:39] ogra: are you already starting on dapper, or do you need input at UBZ? [02:39] ajmitch: stop lurking :) [02:40] ok why two cd overlays at the bottom of the page... [02:40] flint: there's no LiveCD with this release (nor PPC installer) [02:40] jsgotangco: I wasn't lurking, I said I was here at the start ;) [02:40] flint: I think we'll go with the plainer one [02:40] JaneW, 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 UBZ [02:40] ajmitch: was sleeping! [02:40] JaneW: I was? [02:40] I ought to be sleeping [02:40] no, I was sleeping!!! [02:40] it's nearly 2AM here :) [02:40] ajmitch: jokes [02:40] wow [02:40] ogra: ok [02:40] mhz: 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] and I have a MOTU meeting in ~7 hours to attend... [02:41] JaneW, on http://wiki.edubuntu.org/EdubuntuCdAndSlip, bottom of page are two CD screens. are both used? [02:41] mhz: see the website footer for details [02:41] flint: I discussed with mhz earlier and I told him I prefer the plainer one, esp as we need to add some text [02:41] jsgotangco: text/ sure. I just need to make sure the 'art' part is oke before editing texts :) [02:42] mhz: must I send you that text again?^^ [02:42] for a second I thought that one screen was for side 1 and the other for side 2, :^) [02:42] text should be easy, just rip form the edubuntu website theres loads [02:42] flint: these are just conceptual [02:42] JaneW: nop, thx [02:42] mhz: cool [02:43] does everyone like the cover? [02:43] yup [02:43] :) [02:43] aw, the security guy in me wants to screen both sides of the CD. extra secure that way... [02:43] we could call this sedubuntu [02:43] are YOU ALL sure you wouldn't prefer a white cd label with edubuntu logo (as it is on right) and red text? [02:44] it'll look like a blank cd === ajmitch wanders off to sleep now [02:44] mhz, i like it as it is shown... [02:44] mhz, the red clearly enrages I am for it. [02:44] please remember I chose white as symbol of end/begin of something new [02:44] flint: ok [02:44] asian countries associate white with death [02:44] :) [02:44] yes [02:45] jsgotangco: death is good, is begining [02:45] ickkk [02:45] mhz, I still want both sides of the cd screened :^) === JaneW kicks flint in the shin [02:45] jsgotangco: plus, the death of old system v/s born of edubuntu :D [02:45] ackkk spare me the poetic symbolism please... :P [02:45] mhz: white slip cover is nice, but with a red CD inside [02:46] flint: i can do it once you print 10.000 t-shirts and send 1.000 to me :) [02:46] JaneW: okidoki [02:46] I 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] jsgotangco: but you love documenting, dont you? [02:46] :) [02:46] flint: enjoy (as you clearly do...) [02:46] mhz, I will try to get some ts out the door... [02:46] flint, have fun :) [02:47] thanks jane. bye!!! === JaneW didn;t know flint enjoyed animals so much! [02:47] heh [02:47] flint: love what you do [02:47] thanks ollie see you all at UBZ, quiet down jane. [02:47] next meeting? [02:47] ? [02:47] next week ? === jsgotangco shrugs just lurking... [02:47] I won't be around this time next week (in plane) [02:48] yes, me too, as i just see [02:48] so it has to be monday, or without me, or deferred [02:48] just defer it [02:48] <\sh> or at ubz [02:48] votes? [02:48] ohhh [02:48] we'll be talking lots at UBZ [02:48] deferred ? [02:48] yeah [02:48] come to chile and we have it here [02:48] or spark a discussion on the list [02:48] but do we need anymore on-line meetings before 16 Nov? [02:48] yes [02:49] not so much i guess [02:49] lots of BOF'ing will happen [02:49] no time for meetings at all for sure [02:49] i think we wont have clear targets before UBZ (beyond my polish work on ltsp) [02:49] yes. When will we know if cd's get printed or not? [02:49] ok, so nothin official until 16 Nov, but we'll talk as necessary and may call meetings if we want/need to? [02:49] sure [02:49] yup [02:49] other matters, on the list [02:49] ok [02:49] put it on fire!!! [02:49] mhz: I'll try have a better idea by the end of the week, if not def during UBZ [02:49] heh [02:50] is there anything else to discuss now? [02:50] dunno [02:50] what i had for dinner? [02:50] not here [02:50] JaneW: what about local support? [02:50] jsgotangco: fascinating! :) [02:51] mhz: yes... === ..[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 [02:51] JaneW: pig intestines..in a murky soup base.... [02:51] jsgotangco: piuk! [02:51] jsgotangco: hotdog? [02:52] lol [02:52] ealden: isaw pre...hehhhe [02:52] jsgotangco: oh! haha [02:52] jsgotangco: are you on Fear Factor!? [02:52] JaneW: that's a local street food [02:53] jsgotangco: tasted it before.. its nice with vinegar hi hi [02:53] JaneW: we even eat duck eggs over here with the embryo [02:53] jsgotangco: I seen that on Fear Factor too! [02:53] JaneW: what they eat on fear factor is ordinary food for us.... [02:53] JaneW: I would like to talk about the Edubuntu Website ... Web team... ?! [02:54] mmm [02:54] too bad hno73 and highvoltage are not here... [02:54] Edubuntu WikiTeam [02:54] what 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 place [02:54] oh yes the web team [02:54] mhz: Edubuntu needs its own wiki team? [02:54] highvoltage couldn;t make it... [02:54] pips1: can you contact him? [02:55] JaneW: mmm local support interesting...are we taking SLAs? [02:55] jsgotangco: not really, but hno73 and highvoltage are the EdubuntuWikiTeam [02:55] mhz: actually henrik is Mr. Ubuntu Wiki himself [02:55] jsgotangco: we will ultimately hope to get a similar arrangement that ubuntu has ITO support infrastructure [02:55] however, on personal basis, I would prefer to help on Edubuntu wiki pages [02:56] JaneW: sure... by mail? [02:56] and then move to ubuntu ones [02:56] JaneW: oh ok....i'll still slave an 8 - 5 job then [02:56] I think we'll have one web/wiki team, there's very little HTML, most of what we have is wiki [02:56] pips1: yes, henrik=hno73= [02:57] JaneW: so it is ok if we start a #edubuntu-es? or at least a edubuntu-es ML? [02:57] well, I spent some time brainstorming about the website today... [02:57] pips1: highvoltage=Jonathan= [02:57] mhz: eh? [02:57] mhz: if you have a ton of people, sure === mhz prefers ML over # for support interaction and #irc for real life [02:57] I am currently putting stuff up for discussion in the wiki... [02:57] but if its just a few.... [02:57] mhz: do you think there's demand? [02:58] doubt it [02:58] mhz: 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] JaneW: not yet, but my concern is service. and so, we start demoing edubuntu next weeks, where should people who speak no english direct ot [02:58] ot = to [02:58] right [02:59] so far, no need at all, agred. but once people ask.. they need to go somewhere. [02:59] mhz: well I am more than happy for translations and local language support etc to happen... [03:00] ok, then: ThisPage, ThisPageEs, ThisPage/Es ? [03:00] this is an edubuntu meeting now? [03:00] sort of [03:01] sivang: yes just finioshing [03:01] just ending [03:01] jsgotangco: LOL [03:01] finishing even [03:01] :) [03:01] wasn't listed on the topic [03:01] mhz: um... dunno, who has an opinion jsgotangco ? [03:01] sivang: it was I removed it a few minutes ago when I added the next meeting date ;) [03:01] sivang: we're notorious gatecrashers :) [03:02] JaneW: sure, wiki entries on translations are always welcome... [03:02] JaneW: will that also mean that 'loco' teams should have their own servers? [03:02] mhz: edubuntu loco? [03:02] there is such? [03:02] jsgotangco: but should the pages be listed as: ThisPage, ThisPageEs, ThisPage/Es ? [03:02] oh [03:02] i dont know, just using what you guys mentioned a little ago [03:02] I would prefer ThisPage/Es === JaneW doesn;t know... this is all new to me *wail* [03:03] mhz: if there's no Ubuntu Chile, start one === JaneW will have to find out, but I am sure we'll get some kind of loco structure going [03:03] JaneW: i don't think its needed at the moment [03:03] mhz: ok ThisPage/Es then... [03:03] we're very niche.... [03:03] jsgotangco: ubuntu people concern is ubuntu, not edubuntu. [03:03] jsgotangco: I like to think of it as l33t :P [03:04] mhz: edubuntu is still ubuntu === JaneW must wrap up now [03:04] ubuntu people can support edubuntu/kubuntu/xubuntu whatever [03:04] feel free to carry on, just clean up and lock the door when you leave. [03:04] will see you all in #edubuntu in a bit [03:04] nahh im gonna start looking at bugzilla [03:05] jsgotangco: 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 tools [03:06] mhz: 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] ok [03:06] i would tend to think its more social rather than technology involved [03:06] hmmm, yes maybe. [03:06] http://wiki.edubuntu.org/EdubuntuWebsitePlan [03:07] more to follow... [03:07] :-) [03:07] jsgotangco: yesterday a guy asked me about mp3 conversion. For me, that is ubuntu channel [03:07] mhz: and a friend of mine installed edubuntu on a laptop...so... [03:08] hehehe [03:08] I use this laptop as an edubuntu server :) [03:08] 'demo mobile' [03:08] i got 3 ubuntu flavours here [03:09] ok moving to #edubuntu === jsgotangco [n=jsg@202.138.168.170] has left #ubuntu-meeting ["Konversation] === mhz [n=mhz_chil@moinmoin/fan/mhz] has left #ubuntu-meeting ["Leaving"] [03:10] pips1: awesome thanks!!! === 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 [04:34] hey everyone === 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 [09:52] <\sh> or out [09:52] Nafallo: that's useful at a CC meeting, perhaps... :) [09:52] <\sh> or on or off [09:53] that's ALWAYS useful to know when a meeting starts ;-) === ajmitch guesses the meeting will be nice & short [09:57] all we need to do is say 'bddebian is doing it' :) === siretart hopes so :) [09:57] hrhr [09:58] evening everybody [09:58] can't we say siretart are doing s/svn/bzr/g to? :-) [09:58] hi fabbione [09:58] nice to have you here [09:58] fabbione: evening dude :-). [09:58] dholbach: thanks my wife that falled asleep too fast and i am dead bored :P [09:58] hello fabbione [09:59] hehe [09:59] fabbione: that's a good excuse to hang out with motus! rock on! :) [09:59] Haha === 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 [10:00] alright, sounds like it's meeting time [10:00] bd, you got voted into doing everything. [10:00] fabbione: :-) [10:00] fabbione: absolutely [10:00] Loiosh: W00t, thanks [10:00] Welcome =) [10:00] right... here we go [10:00] meep [10:00] do we have an ogra? [10:00] we do! [10:01] :) [10:01] An Ogre? [10:01] oiii [10:01] first 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] motu meeting and I'm missing it :-)( [10:01] i'm sure \sh will tell us a bit about it [10:01] fabbione: useful that you're here then [10:01] ajmitch: that's why i am here [10:01] (the agenda is at https://wiki.ubuntu.com/MOTUMeeting ) [10:01] ok [10:02] \sh: can you please explain everybody what that entry exactly mean? === sistpoty [n=sistpoty@DSL01.83.171.160.112.NEFkom.net] has joined #ubuntu-meeting [10:02] or who proposed via \sh please speak up [10:02] hi sistpoty [10:02] fabbione, you know yourself that we had various requests for patched kernels... [10:02] bing [10:02] hi folks [10:03] fabbione: for example, we would like to have kernels with non-mainline patches, like grsec+PaX [10:03] low latency audio kernel etc... [10:03] ogra: that would be nice to have [10:03] ok [10:03] BenC and I did discuss this issue [10:03] and we do not agree to have kernels in universe for several reasons [10:03] so the point here today is to have a decision if we want to allow such specialized kernels in universe or not [10:03] or better [10:04] we do agree that we do not want kernels in universe [10:04] here is a list of reasons: [10:04] It does seem a little touchy [10:04] bddebian, it is... [10:04] <\sh> sry [10:04] - there are already too many kernel flavours around and users are already confused anough [10:05] \sh: no matter, I would have raised the question anyway [10:05] but you force people who want to base work on such kernels to use an external repo [10:05] - it will mean for the MOTU's to maintain a duplicate source [10:05] <\sh> ohone [10:05] fabbione, nope [10:05] please let me finish [10:05] <\sh> phone [10:05] if we are here talk, first i want to give out our explanations [10:06] otherwise if you already decided, my presence here is pointless [10:06] i'm eager to listen [10:06] so let's try again [10:06] - there are already too many kernel flavours around and users are already confused anough [10:06] - it will mean for the MOTU's to maintain a duplicate source [10:06] - universe kernel will be highly patches and very difficult to maintain even security wise [10:07] the problem is that if we start to create specialized kernels, we set a precedent that cannot be stopped [10:07] - if we create a kernel for each pet-project inside Ubuntu, we will explode in a thousands of kernels [10:07] everyone will want their special purpose kernel ot be a flavor in our repo [10:07] - the patches you want to apply are extremely intrusive [10:07] in the security case, it was something suggested in the proactive security BOFs at UDU, that we have universe kernels - better suggestions are welcome [10:07] we 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 patched [10:08] ogra: that does not work [10:08] fabbione, we didnt even talk about any patches yet [10:08] <\sh> damn [10:08] <\sh> phone company bla [10:08] its a discussion if we want to allow it generally [10:08] <\sh> ok..now [10:08] if universe kernel goes out of sync with main, you get 2 different feature sets [10:08] that pushes even more confusion to users [10:08] ogra: generally, I think any kernel flavors should be closely tied to our main source tree [10:09] ogra: that's why i am giving you detailed reasons on why we do not want to allow them [10:09] i 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] fabbione, 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 ambivalen [10:09] things start getting even more ugly if people want to use linux-restricted-modules with these special flavors [10:09] t [10:09] dholbach: its not so much testing, as specific patches people want that are too intrusive etc to be put in the main kernel [10:10] fabbione: 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 themselves [10:10] dholbach: pax, selinux, low latency audio, realtime, etc [10:10] grsecurity [10:10] siretart: such instrastructure has always been there [10:10] siretart: that's a goal of dapper [10:10] BenC: is there a wiki yet for that? [10:10] siretart: 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] siretart: + to see them maintaing one [10:10] siretart: when I say goal, I mean unofficially at this point :) [10:11] it 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 needed [10:11] fabbione, BenC, also note that sabdfls highest priority for universe is to have everything available without forcing users to add external repos [10:11] thats why we have to pull in apt-get.org every release... [10:11] <\sh> ogra: I didn't see dholbach pull in kernel repos [10:12] ogra: there is a reasonable balance of things we want and sanity of universe towards users [10:12] or just bake the modules for the current one... :-) [10:12] if we deny support for such kernels people will offer them externally [10:12] would 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 something [10:12] <\sh> the kernel is heart of all distributions [10:12] Nafallo: the patches usually aren't just modules [10:12] naf its nto always a matter of modules [10:12] ogra: people are already confused by having 5 falvours of kernels for i386 on main [10:12] Nafallo: lots of things are for more intrusive than that [10:12] ogra: 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] yup [10:12] however 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 patch [10:12] ogra: that list could explose exponentially for each pet kernel === seb128 [n=seb128@ANancy-151-1-23-253.w83-194.abo.wanadoo.fr] has joined #ubuntu-meeting [10:13] fabbione, it will.. surely [10:13] Lathiat, ajmitch: I know. but generally. some things probably can be modules, like trulux vsecurity :-). [10:13] ogra: and do you consider that good? [10:13] ogra: or dangerous for the user? [10:13] fabbione, i'm taking a role here... its not my opinion... [10:13] Nafallo: which is being shipped separately [10:13] ogra: also.. what will happen when a user ask feature foo+bar? [10:13] i dont consider the whole idea good... [10:14] ogra: are you going to create extra combinend kernels? [10:14] to what level of aggregation? [10:14] especially given the maintenance part of it: debian hast quite a lot of kernel-patch-bla packages which weren't touched for ages [10:14] fabbione, he has to found a team that cares for foo and bar [10:14] ogra: I can think of at least 3 different kernel patches that the hardened team would want [10:14] ajmitch: where? he has an external repo for them atm, no? [10:14] yeah, what if someone wants low-latency+grsec [10:14] Nafallo: yes [10:14] Nafallo: you've used them, right? [10:14] ajmitch, but they would go into one image, wouldnt they ? [10:14] ogra: no [10:14] ogra: up till now the MOTU team has always landed in #ubuntu-kernel to ask kernel related stuff.. [10:14] ajmitch: nope, I've only built them for amd64 when he called for help with that. [10:15] not necessarily :) [10:15] ogra: that means that none of the MOTU is dealing to take care of these pkgs [10:15] fabbione, yup [10:15] ogra: so from a MOTU point of view, you should be the first to say no [10:15] ajmitch: would only the kernel be affected or would userspace packages need to modified as well? [10:15] it would be a requirement to fully take care of it indeed [10:15] specially if people asking for these features can't maintain them themselves [10:15] <\sh> ogra: 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 years [10:16] fabbione, 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 discussion [10:16] sistpoty: usually just kernel, with some userland support for some of them [10:16] ogra: we could easily end up with > 50 kernel binary packages in dapper [10:17] I've an idea, how about people who want these kernels start managing them externally to universe to start [10:17] ogra: also.. do you all realize that these kernels will be obsoleted the day after the first USN? [10:17] BenC: ++ [10:17] it would require a good amount of consideration whichto allow and which not [10:17] it 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 idiots [10:17] if they get maintained well enough, and there aren't a lot of problems, then we an bring this back for consideration === Nafallo agrees with the kernel gods :-) [10:17] BenC,++ [10:18] what about packaging kernel-patches? [10:18] there wont be a kernel-patches for dapper [10:18] siretart: that will fail at the first USN [10:18] kernel source will become native [10:18] as dholbach pointed out, debian already has some of these [10:18] <\sh> ogra: 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 else [10:18] so what to do with the already existing ones in universe? [10:18] BenC++ [10:18] siretart: we do have different security release procedures than debian [10:18] siretart: i morgue'd all of them for hoary :) [10:19] dholbach: ah [10:19] siretart: let's make a simple example [10:19] siretart: kernel foo in main [10:19] kernel-patch feature bar in universe [10:19] we release [10:19] \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 it [10:19] all nice and dany [10:19] dandy [10:20] and i think BenC's suggestion is the best so far... [10:20] siretart: at the first security release for main [10:20] kernel-patch might not even apply anymoer === 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,....} [10:20] siretart: that will be the hell of the user [10:20] siretart: security or feature? [10:20] eeks [10:20] Lathiat: they most have come in in breezy and i didnt have the time to take care of them [10:20] dholbach: righto === TiMiDo [n=deb@unaffiliated/timido] has joined #ubuntu-meeting [10:20] fabbione: maybe updatable via -updates? === koke [n=koke@adsl229-164.unizar.es] has joined #ubuntu-meeting [10:21] fabbione: I perfectly see your point [10:21] hey everyone [10:21] <\sh> ogra: 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 b0rked [10:21] siretart, if its a security update, then via -security [10:21] siretart: i can ensure you that the maintainer will be too busy taking care of the last shiny code [10:21] ogra: nope.. for kernel-patch is -updates [10:21] fabbione: the thing is: there ARE people outside wanting these 'special feature' kernels. The question here is, what can WE do to support them? [10:22] \sh, no kernel in universe would ever be supported [10:22] <\sh> siretart: testing the features and implementing them in one of the next releases [10:22] we can support them by not letting them random foo into universe [10:22] so 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] siretart: answer: the dpatch system has been there forever, they can apply their patches with very little knowledge [10:22] Don't WE have enough problems supporting "I want the latest foo" ? :-) [10:22] hey people sorry for my rudness, i will love to join the motu team, =) [10:22] ogra: users still think that they are supported - see 2.6.11 fun [10:22] dholbach, do we actually *have* theye requests ? [10:22] these even [10:22] also [10:22] TiMiDo: Are you an Ubuntu Member yet? [10:22] <\sh> ogra: 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] siretart: I think we should support their efforts with docs and wiki entries pointing to their personal work [10:22] another important factor to take into account [10:22] ogra: i thought you had, because you "fought for the balance" :) [10:22] bddebiann nope [10:23] i thought thios discussion is rather hypothetical [10:23] TiMiDo: stop by #ubuntu-motu after the meeting [10:23] ok =) === TiMiDo is watching [10:23] siretart: the people who want these kernels in ubuntu need to take the first step [10:23] fabbione: this means they have to have some packaging skills for creating a dpatch and building the package. [10:23] what user base do these kernels have? [10:23] fabbione: but I personally am fine with that [10:23] siretart: a dpatch is a normal diff with 3 extra lines [10:23] if they claim to be kernel maintainers [10:23] jupp. I know [10:23] they know how to do that [10:23] or where to look [10:23] there is no need of a special infrastructure [10:23] dholbach, i gave hypothetical people a hypothetical voice ;) i was there when the audio taem died because they couldnt have their low latency kernel in universe [10:24] for baking stuff themselves [10:24] i do not believe somebody that claims to be a kernel maintainer cannot look into a package [10:24] well what kernel are we talking about? [10:24] TiMiDo, universe kernels [10:24] oh alright, [10:24] <\sh> TiMiDo: wiki.ubuntu.com/MOTUMeeting [10:25] TiMiDo: We are talking about allowing kernels into universe, ones with specalized patches, grsec, pax, vserver, low latency audio, etc, see the MOTUMeeting page [10:25] thnx \sh [10:25] ok... how much involvement and serious arguing do we want to allow *-patches? [10:25] so we can settle the matter reasonably [10:25] just 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] dholbach: we won't allow -patches for the reason i explained before.. [10:26] ok, 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] fabbione: alright, or custom kernels in universe [10:26] i think BenC idea of watching these kenrels activity in external repository first is a good first step [10:26] hm... 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 universe [10:26] <\sh> siretart: deb http://archive.ubuntu.com/ubuntu black-hole [10:26] I'd propose to tell him to put his kernel in some 'private' repo and advertise them there.. [10:26] so there would be no more then max 2 different flavors in universe [10:26] sistpoty: i think thats not really needed until we end up with the first idea suggested - someone who has one they maintained for a while [10:26] sistpoty: there is no MOTU-kernel.. as i said before.. [10:27] \sh: this requires more fiddling with dak. you don't really want elmo to do that ;) [10:27] dak? [10:27] <\sh> siretart: yes I don't want it...but you know what a black-hole is...;) [10:27] Lathiat: debian archive kit. ftpmaster software for ubuntu/debian [10:27] \sh: ah, now I see. [10:28] siretart: dak will be launchpad soon ;-) [10:28] sistpoty, the way to go is to offer tham in a external repo for some time and then come back and ask for new discussion [10:28] <\sh> I 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 else [10:28] atleast a lot of it from what I've seen :-) [10:28] ogra: what about the MOTU review archive? [10:28] ogra: ok... i agree fully for this... maybe when one "is ready" then, we even have some nice tools ;) [10:29] fabbione, thats not an archive [10:29] fabbione, BenC: do you want to have those guys (that might come up) working with the kernel team, review/discussion/involvement-wise? [10:29] ogra: can it be turned into one? [10:29] fabbione: you mean revu? [10:29] <\sh> and 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 stream [10:29] siretart: i think so [10:29] fabbione, why ? then motu will be responsible [10:29] fabbione: revu will be an archive, but even if, that would be a source only archive [10:29] <\sh> fabbione: no... [10:30] fabbione, if someone wants to offer such a kernel he should care for it himself... [10:30] dholbach: it depends.. we already have people coming there [10:30] dholbach: yeah, they'll need to keep in touch so they can follow our development cycle [10:30] why don't we just build a kernel from scratch? [10:30] if *we* adopt such a kernel we will care, help and offer the universe archive [10:30] dholbach: the main issue is that as soon as we tell them to prepare their own kernels, they all disappear [10:30] fabbione: i can, sadly, imagine [10:31] yeah, but that's the whole point of the excercise to have them maintain the kernels outside of universe first :) [10:31] yup [10:31] dholbach: so i am glad to see working people around [10:31] BenC: eeheh [10:31] yeah === TiMiDo wants to work for ubuntu (: [10:31] ok, i think the matter is settled then? [10:31] dholbach: but just askers.. we had plenty :) [10:31] yep [10:31] sounds like [10:31] dholbach: matter resolution: NO :) [10:31] fabbione: thanks for telling me... again - i got the pointer ;) [10:31] <\sh> I don't want to be responsible for non booting and oopsing kernels [10:32] dholbach: eheh :) [10:32] somebody added the 2nd item on the agenda: [10:32] Guidelines for using dpatch - many debian maintainers see our use of it as excessive, for the small patches we add. [10:32] dholbach: didn't you offer volunteer as kenrel maintainer? [10:32] "somebody": please speak up === ajmitch added that [10:32] I was going to add the infinity quote as well, but thought better of it :) === ogra would propose more usage of dpatch :) [10:32] fabbione: sure linux-image-2.6-crack-* [10:32] why crack? [10:32] <\sh> fabbione / BenC : Thx for coming around :) [10:32] ajmitch: put the quote here :) [10:33] no problem [10:33] yeah, thanks for taking the time [10:33] no problem [10:33] ogra: this is part of being polite & reasonable with debian === BenC parts the meeting [10:33] yeah, thank you very much, BenC, fabbione - it was a pleasure :) === fabbione takes off [10:33] bye [10:33] bye fabbione . and thanks for coming! [10:33] <\sh> fabbione: comfort your wife now :) [10:33] bye [10:33] ok... ajmitch, we're all ears [10:33] thanks for inviting us for input [10:33] \sh: she is sleeping [10:33] <\sh> fabbione: u should do the same :) [10:33] Hahaha [10:33] < infinity> Universe should ideally deviate from Debian as little as possible, or you guys will be up shit creek. [10:34] haha [10:34] that's excellent === siretart can really understand why DDs dislike dpatch [10:34] <\sh> fabbione: it's cold at my place...I would like to have a wife who is warming my feet ;) [10:34] bye BenC, thanks [10:34] that's something, seb128 had some words to say to, too [10:34] You guys.. =) [10:34] ajmitch, sabdfl sounde quite different todasy [10:34] \sh: did you lose cita again? [10:34] ogra: I know, but that's just sabdfl ;) [10:34] a really promising solution seem to me the wig and pen format, but it is not here yet :( [10:34] <\sh> fabbione: cita? [10:34] \sh, i couls offer some animals [10:34] *could [10:34] \sh: never heard of tarzan? [10:35] cheetah [10:35] siretart: what's wrong with dpatch? [10:35] I know that we use dpatch a lot, even for a tiny patch [10:35] dholbach: about dpatch or patching ? [10:35] <\sh> oh cheetah ;) [10:35] yeah, and the delta [10:35] dpatch [10:35] seb128: ajmitch < infinity> Universe should ideally deviate from Debian as little as possible, or you guys will be up shit creek. === seb128 thinks you patch/create too much diff for small changes [10:35] koke: it is really awfull to debdiff 2 source packages with dpatch [10:35] which annoys DDs when we go making intrusive changes like that, which we have to carry around for the rest of our lives... [10:35] <\sh> fabbione: well...no comment for now ;) [10:35] no, sending fixes at the right place and asking syncs is the way to go [10:35] most of the motu changes give extra work [10:35] the less delta we carry, the better [10:36] seb128: agreed [10:36] we keep on creating more work for ourselves [10:36] what are "small" changes? [10:36] up to how many lines a patch is small? [10:36] changes to .desktop files by example [10:36] and we don't forward small patches to the DDs enough [10:36] to take one [10:36] <\sh> seb128: dpatch includes plain diff -ur as well? [10:36] what about re-libtoolizing package? what about auto-reconfiguring stuff? [10:36] yep [10:36] at last count (with grep-dctrl), we had > 1200 packages in breezy universe with an *ubuntu* version [10:37] that's 1200 potential merges [10:37] *sigh* [10:37] siretart: anything that could be fixed upstream by upstream or Debian should have a patch send here to start [10:37] make a fix [10:37] send it to Debian/Upstream [10:37] wait for them [10:37] ajmitch, seb128, as sabdfl said, ubuntuX will be dropped as a version number :) [10:37] ask a sync or get it synced automatically [10:37] ogra: it will? [10:38] <\sh> seb128: who can we be sure, that debian/upstream are including our changes? [10:38] ogra: I don't care about that [10:38] ogra: what?! [10:38] please don't troll [10:38] STOP [10:38] thats his plan [10:38] <\sh> s/who/how/ [10:38] bah [10:38] don't start trolling [10:38] ogra: irrelvant to this [10:38] ok [10:38] And packages that have no .desktop. Or the stuff wrong with X11? [10:38] the meeting have enough to say without starting on that [10:38] ajmitch, even if i see it very relevant [10:38] bddebian: create a .desktop, send it upstream [10:38] ogra: it's versioning, not patching [10:38] so we get it translated [10:38] and no sync to do [10:38] lets just stay on the topic of dpatch usage [10:39] seb128: I have been asked if the paths are the same? [10:39] so, when i started out [10:39] <\sh> seb128: 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] people were recommending to integrate dpatch [10:39] for aptches [10:39] ajmitch, there is no difference we talk about debian<->ubuntu relationship here [10:39] even smallish ones [10:39] Lathiat: yes, and we've learnt since then [10:39] (i thought it was kind of silly) -- are we now sayign thats a bad idea [10:39] right [10:39] <\sh> seb128: so the question must be: diff.gz or dpatch/diff -ur [10:39] ogra: and I'm talking about the ever-increasing workload we make for ourselves [10:39] but if they already have a patch system, we should try to use that, right? [10:39] Lathiat: yes, definitely [10:40] \sh: dpatch needs to change debian/control,debian/rules .. that sucks [10:40] ajmitch, if my patches dont get accepted upstream or arent even relevant for them, i want to have a easy maintainable dpatch [10:40] \sh: you should be consistent with the existing packaging, in general [10:40] Lathiat: sure [10:40] that's been a rule of general sanity for QA work in Debian for years and years [10:40] seb128 has raised a good point about us failing to push enough upstream to debian [10:40] nice to have you here, Kamion :) [10:40] "do not mess with the maintainer's build system" [10:40] right [10:40] i agree that for a 10 line change n rules or something else done in the debian dir we shouldnt use dpatch [10:40] [22:36:49] what about re-libtoolizing package? what about auto-reconfiguring stuff? [10:40] <\sh> seb128: 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:41] but for changes on the source i'll always use it [10:41] quite, im thinking we should have a "motu send patches to debian" day [10:41] ogra: if you were patching rules from dpatch I'd have to worry ;) [10:41] ajmitch, you know what i mean... [10:41] <\sh> Kamion: if there is a dpatch system in maintainers package, -> dpatch is used [10:41] ogra: what if you have a 1 line source patch, and there is no patch system in the original package [10:41] \sh: sure, that's obviously sensible [10:41] Lathiat: every motu should send his patch before uploading something creating a delta [10:41] trivial changes in the debian dir... uudecoding a png for a .desktop file etc [10:41] what's not sensible is adding dpatch when it wasn't there to start with [10:41] seb128: right [10:41] seb128: what about when the debian guy is unresponsive ish === bddebian2 [n=bddebian@mail.ottens.com] has joined #ubuntu-meeting [10:42] e.g. say 4 weeks passed and still no ack [10:42] seb128, tahts something revu should provide [10:42] Lathiat: you can upload, I've not said to create 0 delta [10:42] seb128: just to try not to [10:42] seb128: I created a lot of deltas just by adjusting build dependencies for some strange transitions. There are tons of such 'modifications' :/ [10:42] but to send patches upstream or to Debian [10:42] <\sh> Kamion: 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:43] siretart: send upstream what can be send upstream (ie: new desktop files), send patches for crashers/etc to Debian [10:43] siretart: for the transitions we have to deal with, that's fine [10:44] \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 Debian [10: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] and we want to avoid complaints as much as possible [10:44] and it's making my relationship with them difficult because I'm having to apologise for things like that [10:44] the MOTU team doesn't have a great name in debian, sorry [10:44] <\sh> Kamion: I read joeys blog entries ;) [10:44] seb128 / Kamion: what would be the most gentle way to send these? directly to the maintainer or by bugs in BTS? [10:45] sistpoty: bug reports are the normal approach ... [10:45] sistpoty maintainer [10:45] sistpoty: BTS [10:45] ok, thx === TiMiDo remembers when i was a Debian developer [10:45] ajmitch: it's ok to be less-experienced, as long as people are willing to learn :-) [10:45] they can track patches in the BTS [10:45] there 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:46] Kamion: yes, I though this point needed to be raised, we don't want to be tainted :) [10:46] we just pick the deb version and send what we did upstream :-P. === ajmitch waits for a package for breezy-updates to build.. there was already dpatch there, thankfully :) [10:47] but i'd still like every motu hopeful to be able to cope with all patch systems [10:47] dholbach++ [10:47] Kamion: btw you or mdz will approve for -updates? [10:47] easy way is to put the patch to debian/ubuntu-patches and to apply it to the source package [10:47] (just raised the point, because i think that will go into review practices as well) [10:47] ajmitch: just mdz, at least unless the workload spikes a lot === ajmitch forgot to add breezy-updates to the agenda [10:47] Kamion: ok [10:47] so no need of change the packaging system and the maintainer has the patch if he wants it [10:48] seb128, with a straight patch -pX command ? [10:48] but 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] seb128: good idea [10:48] right [10:48] fine with me [10:48] so it's applied [10:48] and you don't have to read the .diff.gz to figure the change [10:48] as long as we still maintain the patches separately.. [10:48] <\sh> seb128: u mean instead of debian/patches ? [10:48] ogra: that would have them separately, just not applied at build time [10:48] \sh, yes [10:48] ogra: how do you mean? [10:48] \sh: just a way of keeping them apart [10:49] ajmitch, yup [10:49] I'll guess changes in debian/[rules,control] should just be documented correctly in debian/changelog, right? :-) [10:49] Nafallo right [10:49] Nafallo: of course [10:49] Nafallo: ++ [10:49] Nafallo, additionally [10:49] what part of the MOTU agenda is being discussed ? [10:49] \sh: I mean something not used by the packaging [10:49] good, no ubuntu-patch for that one :-P [10:49] we should be more disciplined about that [10:49] sivang: dpatch [10:49] sivang, second [10:49] <\sh> well...I don't see the real difference...it's a nono to mix up dpatch and plain diff -ur patches [10:50] \sh: if you have dpatch, use dpatch [10:50] ajmitch: thanks ;) [10:50] \sh: if dpatch is alrady there, use it! [10:50] \sh, if dpatch is there, use it... [10:50] :) [10:50] ok so if dpatch isnt there, and you need to patch the source [10:50] \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] Lathiat++ [10:50] \sh, if its cdbs, use cdbs [10:50] <\sh> thats what I said...is anybody doing it differently? [10:50] you should create a patch file and apply it with diff in rules? [10:50] else apply a normal patch [10:50] \sh: some guys introduced dpatch [10:50] if you have _any_ patchsystem in place, use it :-) [10:50] \sh: me amongst them (in some cases), so it's nice to see this discussion [10:50] seb128: if you copy it there, does it get applied automatically ? [10:50] yeh i had been too [10:51] me too in some cases where i certainly know the version wont survive this release [10:51] <\sh> dholbach: phew...so I'm on the right site ;) I used only diff -ur for orig.tar.gz patches ;) [10:51] so what, you add a patch < before build and diff -R in clean? [10:51] \sh: great [10:51] no, it doesn't get applied === bddebian [n=bddebian@mail.ottens.com] has joined #ubuntu-meeting === Lathiat is still confused on that part [10:51] Lathiat: no, not at build time [10:51] debian/ubuntu-patches will be informative only [10:51] its an add on [10:51] ajmitch: apply the patch, but include the diff in debian/ubuntu-patches/ for reference? [10:51] so how do we apply patches if we don't have any patches application system in place? manually? [10:51] Lathiat: yes [10:51] ok! [10:51] sivang: yes [10:51] that makes sense! [10:52] <\sh> so have it in diff.gz [10:52] i think i should go write a wiki page [10:52] detailing this [10:52] Lathiat: please do ;) [10:52] seb128: (since we lack pitti) we should follow that ubuntu-patch ida with security to in your opinion? :-) [10:52] Lathiat++ [10:52] <\sh> and debian/ubuntu-patches only for informational purposes [10:52] sivang, make your changes but keep a patch that reflects them [10:52] Lathiat: PackagingTips? MOTUWannabeSomething? [10:52] MOTUApplyingPatches or something [10:52] ogra: cool, understood [10:52] Lathiat: link it from everywhere :) [10:52] ogra: I wonder if this practice should be also followed in main ? [10:52] whwat about when we need to do things like update configure etc? [10:53] sivang, and use the existing patchsys if already available... [10:53] Lathiat: it's the same thing [10:53] Nafallo: no opinion on that [10:53] seb128: oki, I'll try to remember to ask pitti later :-) [10:53] doing ubuntu-patches would make for messy debdiffs ;) [10:53] security changes need to be as small as possible, generally [10:53] Lathiat: yes, but we can filter that part out [10:53] man filterdiff ;) [10:53] heh [10:53] ok [10:53] Lathiat: right [10:54] ok, do we have agreed? :) [10:54] dholbach: YES! [10:54] ROCK [10:54] <\sh> if someone summarize it [10:54] now onto my next 2 points... [10:54] I've to go, later guys [10:54] cool [10:54] next item on the agenda [10:54] ajmitch: should still show what we did, no? :-) [10:54] ok, thanks seb128 [10:54] <\sh> seb128: thx === sistpoty gains 100 XP [10:54] see you seb [10:54] # [10:54] Upstream Version Freeze & other milestones (AndrewMitchell) [10:54] * [10:54] We have a huge list of packages to merge, these should be finished right around UVF if not earlier. (AndrewMitchell) [10:54] bye seb128 thanks for coming === ajmitch has an agenda >:) [10:54] that means we'll not see new stuff probably [10:54] LoL sist =) === sivang thinks ajmitch rocks [10:55] ogra: depends on how much time we can spend reviewing [10:55] i second ajmitch's point [10:55] ajmitch, exactly... [10:55] and if UVF for universe lags main UVF [10:55] ogra: focus != only goal [10:55] but we had 200 merge packages in hoary [10:55] ajmitch: does anyone know about the UVF prosept date? [10:55] ogra: up to 1200 for breezy [10:55] sivang: thats still being thrown around like mad by the looks of it [10:55] <\sh> ogra: we will have more for dapper [10:55] dholbach, UVF *will apply* for universe this time [10:55] well breezy->dapper [10:55] sivang: no, will be discussed at UBZ, i guess [10:55] ogra: i know [10:55] where a lot is trasitions, no? :-) [10:56] <\sh> Nafallo: yes [10:56] just a small (but I think important question). How will be syncs handled for dapper? [10:56] we have far less transitions, far more merging [10:56] well, given the amount of work, maybe it would be beneficial to start bugging about it? [10:56] we should perfectly agree on making number one prio [10:56] will this go via elmo or launchpad? [10:56] sivang: ? [10:56] so time is very short to merge say 300 pkgs *and* get new stuff reviewed [10:56] <\sh> siretart: MoM will handle this bug list [10:56] siretart: there's a lot of confusion on the very topic [10:56] ogra: I think that most merges can be done in a few weeks [10:56] we should draw up a merging guide, we need to do things like, try reduce deltas etc, and filign bugs, etc [10:56] but we only have a few weeks [10:56] Lathiat: ++ [10:56] ajmitch: I mean, to start maybe tryin to get someone to think about it :) if we have so much work [10:56] \sh: mom is broken afaik [10:56] wow. universe are going to look clean after we've done this the right way (sending things upstream...) :-) [10:56] ajmitch, we only have a few weeks :) [10:56] sivang: why do you think I raised it here? [10:56] 09:56 < ajmitch> but we only have a few weeks === Lathiat volunteers again to draft up an initial version of MOTUHowToMerge [10:56] Nafallo: :)))) [10:56] ajmitch: :) [10:56] *cough* ;) [10:56] <\sh> dholbach: well...I don't have a mom actually...so I'll do it the normal hand-ish way === ajmitch has gotten used to doing manual 3-way merging :) [10:57] me too === sivang would like to know 1) What does the merge invovles. 2) How many NEW pakcages we need to do [10:57] MOM is a little questionable at times [10:57] :-) [10:57] mom is always questionable! [10:57] \sh: is MOM freely avbailable ? [10:57] \sh, hand-*ish* ? [10:57] err, [10:57] sivang: 2) we can't say that [10:57] sivang: a merge is taking the difference between debian and ubuntu packages [10:57] <\sh> ogra: manually [10:57] sivang: and fixing it up [10:57] ajmitch: spec up a guide for us on the wiki? :-) [10:57] sivang: you have 3 versions.. the original version, ubuntu changes, and debian changes [10:57] sivang: where they conflict [10:57] sivang: 1) getting new debian version in, applying our changes [10:57] Nafallo: sure... [10:57] \sh, like done at ish ? [10:57] <\sh> sivang: I searched for it..and I only found a commercial package [10:58] \sh: hehe [10:58] <\sh> ogra: *lol* [10:58] I could write a MoM clone if you really needed it :P === ivoks [n=ivoks@lns01-1373.dsl.iskon.hr] has joined #ubuntu-meeting [10:58] sivang, there is no use for MOM if the debian archives are broken [10:58] and put it on REVU [10:58] s/REVU/tiber/ [10:58] ok, do we all agree that merges are really important and we will all focus on that? [10:58] bddebian: maybe you can bug elmo for us to provide a local version of a MOM ? :-D [10:58] dholbach: YES! [10:58] yea, cause Keybuk would NEVER share the existing code? ;-) [10:58] <\sh> dholbach: we have to...it's first task we should focus on [10:58] dholbach: yeah [10:59] dholbach++ [10:59] Nafallo: I guess the code is fairly simple [10:59] dholbach++ [10:59] dholbach: how are you producing lists of packages that needs merges? [10:59] if i might add a suggestion: before uploading a package it might be prudent to examine the bugs for the package [10:59] uh [10:59] sivang: will be on bugzilla [10:59] i'm late [10:59] ajmitch: still no need to discover the wheel again? :-) [10:59] the problem is usually getting the debian package that we forked from === sivang feels that he should be getting a debian box for this works [10:59] so if we can make a tiny change to fix a bug, do that with the merge [10:59] dholbach, bah, who cares for bugs... [10:59] since snapshot.debian.net lost a lot of data [10:59] ogra: leave the channel, please ;) [10:59] :) [10:59] hehe [10:59] sivang: sid chroot [11:00] AND: [11:00] ajmitch: cool [11:00] and ? [11:00] we might have apt-get source -t by then [11:00] AND? [11:00] ROCK [11:00] -t ? [11:00] ? [11:00] elaborate ? [11:00] like in apt-get [11:00] so you can have ubuntu and debian sources [11:00] ah [11:00] oh right [11:00] target release? [11:00] and fetch the debian source just with apt-get [11:00] apt-get like in apt-get :-) [11:00] sivang: mvo has it on his harddisk [11:00] dholbach: please xplain :) === Nafallo understands less now ;-) [11:00] we *still* have the problem of getting the original debian source [11:00] ok [11:01] -t targets release [11:01] <\sh> mm... [11:01] 3-way merges need a base :) [11:01] yes, so you do apt-get source pornview -t sid [11:01] eek, that means i need to have debian soures in my sources.list ? [11:01] ivoks: yes, that what I saw with man apt-get /-t [11:01] you can have couple of releases [11:01] and pick whichever source you want [11:01] ogra: no you don't, but i think it's a worthwhile feature [11:01] I usually do apt-cache madison && apt-get package=version anyway :-P [11:01] dholbach: I just switch into my sid chroot with its bind-mounted dirs ;) [11:01] especially if you do apt-pinning [11:01] <\sh> I think the problem is more, when I'm thinking on our transitions, that the packages we touched are not done by DDs by now [11:01] i dont [11:01] do whatever you like [11:01] or apt-get source sid/pornview [11:01] i FANCY it [11:01] \sh: most are [11:01] i stay away from pinning as far as i can [11:01] iirc [11:01] dholbach: how does it know where to fetch the package from if you don't provide it with the sources? [11:02] sivang: you have to === ajmitch thinks we're straying off-topic [11:02] yes [11:02] i just liked the idea [11:02] however [11:02] we agreed already ;) [11:02] OK, BACK ON TOPIC [11:02] the last item on the agenda is: [11:02] dholbach: care to give me a session about that one afterwards? :) [11:02] i tought meeting is at 22:00UTC :( [11:02] Clean up and reorganization of MOTU wiki pages. (JordanMantha) [11:02] JordanMantha, are you there? === LaserJock is Jordan Mantha [11:02] Ping [11:02] dholbach: we need more agenda items, this meeting was meant to be about direction & discussion before UBZ [11:03] err, sorry [11:03] I'm getting a cup of tea, be right back [11:03] what was the resolution to point3? [11:03] to get input from the MOTU community who won't be at UBZ [11:03] siretart: get working ;) [11:03] siretart: we agreed to heavily focus on merging first (as soon as we have a merging list) [11:03] siretart, NO 1 prio is merges before UVF [11:03] ajmitch: i'm off [11:03] ajmitch: Why, you'll ignore it anyway.. ;-P [11:03] btw, quick question, are .desktop files fair game to go upstream to debian? [11:03] dholbach: I have a preliminary list [11:03] okay. thanks [11:03] bddebian: stop trolling [11:03] Lathiat: They SHOULD be :-) [11:03] ajmitch: do you want us to decide on them? [11:03] e.g. do debian care [11:03] I 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 wiki [11:04] dholbach: can I help out in writing a script to produce the merges list? (I take it you're doing it in python) [11:04] ajmitch: wouldn't it be better to collect the ideas on a wiki page? [11:04] (im writing up merge howto) [11:04] siretart: I've got one already [11:04] dholbach: maybe even a spec? [11:04] sivang: it should be already done, the stuff was on bugzilla (just search for merging) [11:04] s/siretart/sivang/ [11:04] *********** leave the stage to LaserJock please ************* === koke is quite busy and would love a ping if we talk about UBZ :) [11:04] its his topic [11:04] dholbach: I just wanted ideas raised [11:04] dholbach: ok [11:04] LaserJock: please :) [11:04] ok i want to do something [11:04] well, I am just a MOTU wannabe but I would like to help with wiki cleanup if I can [11:05] I just wanted input as to what would be good for you guys [11:05] LaserJock, what are your suggestions [11:05] thank you very much for that at first :) [11:05] I guess Lathiat is taking care of some stuff [11:05] what should get changed... whats missing, what needs improvement ? [11:05] Well, we have 3 wiki pages for recruits [11:05] yes [11:06] sadly [11:06] Aye [11:06] it should be only 1 [11:06] <\sh> 3? [11:06] wher does the third come from ? [11:06] maybe just 2 sorry [11:06] what 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] i only know dholbachs and mine === \sh just knows pbuilderhowto and developerresources [11:06] the Todo page has lots of notes for MOTU but it is a little hard for newbies to figure out [11:06] LaserJock: do you find the current instructions for packaging a source from scratch okay? [11:06] <\sh> but that's me ...forget about me [11:07] the recruitment pages can get merged or rewritten [11:07] well I think the packaging stuff could be improved [11:07] <\sh> sivang: IT'S NOT OKAY ;) [11:07] sivang: i think there is none [11:07] <\sh> dholbach: there r two [11:07] <\sh> dholbach: one was mine, the other one is kubuntu doc for cdbs stuff :( [11:07] lol [11:07] what about Unfrgivens developer docs ? [11:07] <\sh> dholbach: mine is incomplete [11:07] we should make sure that everything follows MOTU policy and is current (replace Hoary with Dapper or something more general) [11:07] \sh: well, kubuntu doc has some kde/kubuntu specific stuff [11:07] can we put them up somewhere ? [11:07] \sh: e.g. what to add to cdbs for kde [11:07] ogra: yes, they are getting put up [11:08] great [11:08] <\sh> Lathiat: which is wrong in my eyes [11:08] maybe we can get some of the more experienced folks in here to contribute on \sh's docs? [11:08] \sh: well, its needed [11:08] \sh: even if its a subset of a main page [11:08] make them more complete [11:08] ? [11:08] ajmitch, do they get in -updates ? [11:08] <\sh> sivang: no..it's too difficult...I need to rewrite it [11:08] we have fine "intro developer docs" [11:08] <\sh> Lathiat: yeah..for people who knows how debhelper works [11:09] how 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] they have been packaged but were to late for breezy [11:09] ogra: no way [11:09] ogra: they didn't pass NEW for breezy [11:09] What 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 wannabes [11:09] too late [11:09] i'd suggest we'd look over them and enhance if needed before we start new stuff [11:09] ajmitch, -updates ? [11:09] isnt that, what i said? [11:09] ajmitch, i'll go begging at mdz [11:09] wiki pages cover *way* more than packaging [11:10] ogra: good luck, I think he'll say no [11:10] fyi: https://wiki.ubuntu.com/CategoryMOTU [11:10] the wiki has to cover all the bits about getting involved, what we do, what there is TODO [11:10] ajmitch, i'm used to... you didnt see my bleeding knees yet that edubuntu brought me :) [11:10] one other thing that is confusing (at least for me) is that the MOTUTodo doesn't seem prioritized [11:10] IntroDeveloperDocs is targetted specifically at new packagers creating a package [11:10] LaserJock: ++ [11:10] MOTUTodo needs wiped & redone [11:11] yes [11:11] ok, how do we proceed, who wants to give LaserJock a hand? [11:11] there are many transition pages [11:11] we still have no RT [11:11] I'd propose to drop them [11:11] ogra: do we need RT? it can be setup easily on tiber [11:11] RT? [11:11] couldnt MOTUTodo be replaces with a RT instance on the revu server ? [11:11] launchpad! :) [11:11] request tracker? [11:11] Ah [11:11] siretart: yes [11:11] yes [11:11] <\sh> bddebian: RequestTracker a perl tool and a nice one [11:11] siretart++ go for ghc6-transition first :) [11:11] Reinhard Tartler? ;) [11:12] rt sucks :) [11:12] dholbach, ?? [11:12] for what would we need rt? [11:12] any one of the tiber admins can set it up if we agree [11:12] siretart, UniverseCandidates [11:12] <\sh> ajmitch: u r one ;) [11:12] siretart, a morgue list [11:12] an rt request for each package that needs love? [11:12] just think about UniverseFTBFS [11:12] but anyway [11:12] all the stuff we need lists for... [11:12] this gets a bit offtopic [11:13] why ? [11:13] we're here to organize our documents [11:13] wouldn't it make less work to create a python script installed on tiber than install rt? [11:13] that's more important than the workflow, at least for newcomers [11:13] dholbach: this IS about organizing documents [11:13] dholbach, or drop them in favor of something better ;) [11:13] siretart: such as? [11:13] documentation [11:13] sorry [11:13] siretart: what python script would you want? [11:13] dholbach: we are talking about potential replacing wiki pages by other means [11:13] this is about replacing sections of the wiki with other, better tools [11:13] ajmitch: morgue list [11:14] dholbach, MOTUTodo is a internal workflow page.. but wannabes will find it and get confused [11:14] ajmitch: and UniverseCandidate have been mentioned [11:14] unmetdeps [11:14] yes [11:14] ajmitch: SyncCandidates would be another candidate [11:14] ftbfs [11:14] ++ [11:14] tiber == internal workflow wiki? :-) [11:14] Nafallo, nope [11:14] no wiki there [11:14] I was working on an unmet deps resolver to keep the list fresh [11:14] *tools* [11:15] so we'll have an RT request for every package to fix? [11:15] ajmitch: that would really be great. it is quite high on my list.. [11:15] ogra: not now... but it would be a possibility if MOTUTodo is such a confusing page, no? :-) [11:15] so that it could scan the universe/main package list & generate a list of packages that wouldn't install [11:15] dholbach, that would obsolete maolne :) [11:15] code is about 75% written :) [11:15] ajmitch: my hero! :) [11:15] ajmitch++ [11:15] what about UniversePackageWithoutDesktopFile? [11:15] Nafallo, dont think its a good ide to replace a wiki with a wiki === ajmitch has had a few script ideas ;) [11:16] so could we agree on testing RT for our purposes? [11:16] yup [11:16] ogra: in most cases no, but it could be in this one. anyway, I'm fine with MOTUTodo whereever it is :-) [11:16] *sigh* [11:16] is it hard to set up? [11:16] and wipe all workflow stuff from the wiki eventually === siretart doesn't like the idea of rt that much [11:16] i don't have used it much [11:17] <\sh> dholbach: it's a bit of "frickeling" [11:17] so i'd like to see in action what we're talking about [11:17] <\sh> with perl and some alias lists [11:17] Nafallo, lists on wikis are unusable if they reach a certain size [11:17] wouldnt like [11:17] bugs in launchpad [11:17] ogra: how can rt assist with that? [11:17] assigned to some meta-user for this kind of things [11:17] be better? [11:17] dholbach, you havent used it much ? [11:17] Lathiat: we'd need mass-filing stuff [11:17] ogra: no [11:17] launchpad has an email interface [11:17] = easy mass filing [11:17] dholbach: malone email UI [11:17] dholbach, all internal canonical requests go over rt ... [11:17] ok [11:17] ogra: i know [11:18] ah well, nm :-) [11:18] ogra: how often did you use it? [11:18] ok, so what do you guys want me to do? [11:18] we can mass-file, do nearly everything to bugs that you can through the web UI [11:18] 2 times :) [11:18] actually it would be better filed against a meta-package [11:18] ogra: you see... [11:18] and then you can assign something to yourself [11:18] if you are working on it [11:18] OKOKOK, what are our proposals? [11:18] <\sh> I used it as support ticketing system for 3 ISPs [11:18] we cannot agree on something that's not there [11:18] where meta-package could just be some 'product' or whatever concept launchpad has [11:18] there's no transition, if we don't have something yet [11:18] <\sh> Lathiat: team not product [11:18] first lets give LaserJock something in his hands [11:18] i'd very much like to get back to documentation [11:18] ok, back to WIKI cleanup please :) [11:19] \sh: but can you file a bug *on* a team [11:19] Lathiat: shh :) [11:19] \sh: assigning is no good, then you cant assign it to yourself to work on [11:19] <\sh> Lathiat: later [11:19] because that's more important, even if not as appaling as tools to some of you :) [11:19] we agree that the wiki needs love [11:19] new contributors find the wiki confusing [11:19] LaserJock's point was that the wiki is useful for 'insiders' who already know their way around [11:19] i'd say lets first have a list which is workflow and which is doc... then clean up the doc pages [11:20] because that's who has written the wiki pages [11:20] who would give LaserJock a hand at looking at CategoryMOTU and merge, where we can? [11:20] ogra++ [11:20] anyone disagrees with removal of ghc6transition page? (it's done :) [11:20] workflow pages can probably be largely purged [11:20] sistpoty: trash it [11:20] sistpoty: all part of the cleanup [11:20] sistpoty, why is it still there ? [11:20] ogra: been lazy with the wiki *g* [11:20] ;) [11:21] historic reasons? ;-) [11:21] all of us have been lazy with the wiki [11:21] except maybe dholbach ;) [11:21] hehe [11:21] Speak for yourself :-) [11:21] so that we can look back in teen years and laugh? :-) [11:21] oh, and bddebian [11:21] LaserJock: how would you proceed? [11:21] our MOTU God [11:21] pfft === ogra hands LaserJock the mic [11:22] I think that we should have a wiki that has lists of wiki pages MOTU/Wannabes want to see [11:22] and ones we need to get rid of [11:22] yeah [11:22] great [11:22] Then I can work on them [11:23] I am willing to do work, I'm just want to make sure I don't mess up something important [11:23] LaserJock: you can always ask in the channel [11:23] LaserJock, its a wiki [11:23] and i'm quite happy you take that role [11:23] if you break it, you can unbreak it, i think [11:23] dholbach++ [11:23] it has version control as long as hno73 doent mess it up ;) [11:23] Heheh, yes [11:23] perhaps we can regroup all workflow pages under MOTU/Workflow/? [11:23] we can't leave it up to LaserJock alone [11:23] You can undo changes. [11:23] siretart: excellent idea [11:24] laserjock and whip other people === Lathiat will do some work [11:24] i wanted to do that too [11:24] wiki calls it a 'revert' [11:24] a directory structure [11:24] i gues that'd help [11:24] same for MOTU/Transition/ [11:24] MOTU/Doc [11:24] MOTU/Wannabe [11:24] yeah [11:24] MOTU/Process [11:24] <\sh> well...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 help [11:24] MOTU/Teams :-) [11:25] heh [11:25] yeah [11:25] especially as MOTU is seen as the entry point for ubuntu development [11:25] woohoo [11:25] ajmitch: ++ [11:25] so we need to make it as appealing as possible :) [11:25] it's a shame in which state some pages are === sistpoty hides [11:25] :) [11:25] lot's of them talk about hoary and warty still ;-) [11:25] yep [11:25] unfortunately the whole wiki is generally a mess [11:25] ok... LaserJock is that cool for you? [11:26] but if we want to get anywhere we will need to focus on MOTU stuff of course :) [11:26] and breezy is old news now ;) === ogra is happy he only has to care for wiki.edubuntu.org currently :) it small [11:26] dholbach: sounds good to me [11:26] LaserJock: excellent [11:26] ajmitch: do you still want to collect items for ubz? [11:26] ajmitch: or can we agree to announce the wiki page here? [11:26] I 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:27] dholbach, announce the wiki page ? [11:27] LaserJock: excellent, and thanks again [11:27] dholbach: as UBZ is Real Soon Now, I'd like to hear a few minutes of ideas [11:27] and put them on the wiki page [11:27] ogra: for IdeasForMOTUUBZ [11:27] ok [11:27] for those that cant attend :( [11:27] ajmitch: go ahead [11:27] since some discussion will help to get it going [11:27] it woudl be nice to get a drawup of new interaction in dapper [11:27] like with launchpad etc [11:27] dholbach, we have https://wiki.ubuntu.com/UbuntuBelowZero/BOFs, why not add it there ? [11:28] ogra: it's ajmitch's agenda item [11:28] that page is quite busy/crouded [11:28] koke: ping UBZ :) [11:28] <\sh> first idea: Every MOTU gets a lifetime support of Aspirin [11:28] Lathiat: MOTULaunchpadPackages? ;) [11:28] ivoks: thx [11:28] ajmitch: heh [11:28] ok [11:28] s/Packages/Processes/ [11:28] \sh: ++++ [11:28] ;) [11:28] ajmitch, why not use https://wiki.ubuntu.com/UbuntuBelowZero/BOFs ? [11:28] ogra: sure [11:29] <\sh> ajmitch: *g* [11:29] as we know, dapper is going to be supported for 3/5 years [11:29] what can we really focus on to make it rock? === Nafallo has still not figured out what will be left the last 2 years ;-) [11:29] i think first and foremost should be cleaning things up [11:29] gettin gmerges out of the way [11:29] first up is how to get new people involved.. [11:29] trying to fix as many leftover unmet deps as possible [11:29] and doing the merge & bug work [11:29] getting rid of as many merges as possible / simplifying them [11:30] and try do them ASAP, instead of last-week rush [11:30] I'd like to work with someone else in the Ruby team === ajmitch waits for some radical suggestions from the floor [11:30] Lathiat++ [11:30] koke: we have a ruby team [11:30] stop including new packages [11:30] Lathiat: that was on the agenda ;) [11:30] koke: we havent really done much yet [11:30] and only fix remaning [11:30] Lathiat, we wont have a choice in dapper, th relese schedule will fully apply to universe [11:30] I know, but I'm not sure if someone from the team will be at UBZ [11:30] \sh: will we have time with everything? :-P [11:30] ogra: "last week before UVF rush" [11:30] ogra: etc [11:30] so merges have to be done at a certain date [11:30] ivoks: that's an option [11:31] Lathiat: so start on merges asap [11:31] <\sh> Nafallo: I don't think that our spec will be a dapper "goal"...so it's deferred by default ;) [11:31] ajmitch: with new i'm thinking on REVU :) not new versions [11:31] ajmitch: when merges happen! ;) [11:31] \sh: baah :-P [11:31] but that will scare people away... new people want to include new stuff... dholbach and i had this discussion plenty of times [11:31] Yeah but some merges come back to "just syncing Debian" ;-P === bddebian hides [11:31] ivoks: I think that we need to get new packages to attract new developers [11:32] at least up until UVF [11:32] <\sh> as I said, at sometime we have to split the strength of the team... [11:32] after that we have to say no [11:32] ajmitch: but definitive no [11:32] or no, with exceptions ;) [11:32] ajmitch: no "just this one" [11:32] unlike the non-UVF that we had with breezy [11:32] yup [11:32] yeah... [11:32] I think it can still be worth getting packages in after UVF, if they're well done [11:33] uploads in last hour [11:33] ajmitch, depends... [11:33] ogra: sure [11:33] one more thing [11:33] if i see it correctly, the release process for dapper for main isnt even clear yet [11:33] when dapper+1 opens [11:33] ajmitch, if we need mdz/Kamion approval at least *i* wont bother them with it [11:33] ogra: I'm just arguing that a blanket NO can be detrimental :) [11:33] we have to do more backports than now... [11:34] <\sh> ivoks: backports are a special topic [11:34] ivoks, thats Mez's job [11:34] we dont have to care.. [11:34] :) [11:34] <\sh> ivoks: we need all motus to help us for merges and other things...where merges*1000 prio [11:34] ok [11:34] ogra: yes, I don't think mdz & kamion will take on the universe burden as well [11:34] but we should get jdong into motu finally [11:34] ajmitch, exactly [11:34] ogra: perhaps you'll end up being the MOTU in charge of approvals ;) [11:34] or dholbach [11:34] Hahaha [11:34] heh [11:34] <\sh> ivoks: because for breezy we were only a few [11:34] ajmitch, surely not... else edubuntu will suffer === Loiosh offers ogra aspirin. [11:35] Loiosh, i cant [11:35] ogra: ok, some other community member like \sh [11:35] yup, good suggestion :) [11:35] Heh [11:35] <\sh> what? [11:35] if (member != ogra) echo good suggestion [11:35] <\sh> ajmitch: what u want from me? [11:35] \sh: you'll do all the work :) === LaserJock thinks ajmitch might just volunteer himself === Loiosh offers \sh aspirin. [11:35] probably ogra AND dholbach :-) [11:35] erm.... === ogra orders a truck with aspirine for \sh's address [11:36] can't we make a list of topics, briefly? :) [11:36] LaserJock: no, I'm not going to volunteer myself, I'd have to be nominated by others :) [11:36] dholbach: please :) [11:36] dholbach, UVF exception approvals... [11:36] this is going OT again ;) [11:36] yes === \sh needs a house in durban, sea side, near coconut grove and a big fat pipe for uploading..that's all...possible? [11:36] ogra: i'm not taking notes :) === bddebian nominates ajmitch [11:36] we were ever on topic? ;) [11:36] dholbach, me neither [11:36] i will have a presentation to prepare [11:37] i thik exception should be stuff like ipod support etc [11:37] so i'd like to wrap up, if we can't agree on how to handle pre-ubz-business [11:37] what IS the topic? :-) [11:37] since apple has tenedency to change stuff periodicly [11:37] Nafallo: UBZ suggestions [11:37] I was asking for people to (briefly) suggest topics for UBZ, that we'll put on the wiki [11:38] the briefly part got lost somewhere under my desk [11:38] and how many do we have? :-) [11:38] :) [11:38] Nafallo: about 1/2 [11:38] hmm, that must be \sh's aspirin then... [11:39] ok. shall we agree on a wiki page for "brief ideas" and agree on a time and date for next meeting? [11:39] Nominate a member to be considered for post-UVF approval? [11:39] well, I already now what I'm going to do in dapper so... ;-) [11:39] dholbach: yes [11:39] Loiosh, that should be absolute exceptions... [11:39] next meeting will be during or after UBZ [11:39] ok, suggestions? [11:39] oh [11:39] dholbach: what is the presentation about? [11:39] quick Q [11:39] s/approval/absolute exceptions/g [11:39] can we irc mirror the ubz meeting? :) [11:40] sivang: berlinux, ubuntu community [11:40] dholbach: make clones of mdz and Kamion. [11:40] Lathiat, that was the plan iirc [11:40] or does anyone have a spare few grand lying around to send me? ;p [11:40] Lathiat: if needed, but we'll have quite a few BOFs [11:40] <\sh> Lathiat: if there is a motu bof or meeting we will pushit via irc, i think [11:40] dholbach: atleast there role for main should be someone in Universe :-) [11:40] sorry, I blew my last bit of cash to send myself ;) [11:40] ogra: that would be nice, since some of us can't attend ubz [11:40] <\sh> Nafallo: choose one of 4 ... dholbach , ogra, ajmitch , \sh [11:40] ivoks, yes [11:40] dholbach: ah, intersting, UBZ spec? [11:41] \sh: yes, those sounds fine :-) === sivang googles for berlinux [11:41] <\sh> Nafallo: exclude me ;) [11:41] \sh: noway dude! ;-) [11:41] <\sh> Nafallo: I'm not compatible with TB ;) [11:41] ogra: just conclusions would be enough [11:41] \sh: and of those, ogra & dholbach & \sh & ajmitch are very busy ;) [11:41] \sh, hewy, you only have KDE to care for, we others have important tasks :) [11:41] ajmitch: but mdz and Kamion isn't? ;-) [11:41] ok, what about the name for the wiki page for the suggestions? [11:41] <\sh> ogra: *lol* [11:41] and what about the time and date for next meeting? [11:42] dholbach, at UBZ ? === sivang voulenteers for approving exceptions :-D [11:42] i think we said that lats time [11:42] <\sh> ogra: I think I had more != KDE uploads to main then expected [11:42] ogra: yes! [11:42] at ubz! [11:42] how about some means of enforcing approval? [11:42] ok, time and date? [11:42] ogra: yes, at beer o'clock in 2 weeks? :) [11:42] siretart: a big stick? [11:42] dholbach, probably dynamically or do *you* know the schedule yet ? [11:42] not in the end of ubz [11:43] no, that's why i ask [11:43] dholbach: so... the MOTU core team as exception approvers for Universe please :-) [11:43] you seemed to know :) [11:43] siretart: enforcing approval is hard, we can't upload to a frozen queue that someone can moderate [11:43] we should announce a date if we are there and know the schedule [11:43] siretart: not unless we do some fast talking with mdz & kamion [11:43] ok [11:43] ogra: good idea [11:43] dholbach ogra somewhere in the middle, so rest of us can make some suggestions [11:43] ajmitch: perhaps this is something for your ubz list, then [11:43] ajmitch: do that talking with them on UBZ then? [11:43] so between oct 26th and nov 7th [11:43] siretart: ok === ajmitch writes beer with ogra, dholbach & others on his list [11:44] <\sh> Novembre 1st? [11:44] :< [11:44] ogra: not on 7th, I'm leaving on the 6th :-/ [11:44] <\sh> ogra: 6th [11:44] but the suggestions with the big stick seems fine to me [11:44] ogra: oct 26th? that's far too early [11:44] <\sh> ogra: siretart and I are leaving on the 6th [11:44] \sh, do *you* know what we'll have ion schedule on Nov 1st ? [11:44] \sh: msot people check out about the 6th [11:44] let's announce it on the mailing list [11:44] or on the irc topic === ajmitch doesn't arrive till the 29th [11:44] ogra: my birthday ? :-) [11:44] <\sh> ogra: well...the night dude ;) [11:44] dholbach++ [11:44] we're not getting somewhere now :) [11:44] 1st is my birthday [11:45] dholbach: good idea [11:45] dholbach: :) [11:45] <\sh> dholbach: of course...to bed ;) [11:45] and i'm pretty tired and have to get on with work :) [11:45] dholbach: I *really* have to get off to work & my real-life job [11:45] dholbach: /me prefers mailing list ;) [11:45] ajmitch: me too [11:45] it's nearly 11AM here, I'm about 2 hours late [11:45] ok, we'll put it in the topic of -motu [11:45] sistpoty: we can do both [11:45] once we know the schadule [11:45] dbboth [11:45] dholbach: both [11:45] ok [11:45] yeehaa... i almost never look at the topic :( [11:45] wrap it up [11:46] ok, thanks everybody for coming [11:46] have a nice day [11:46] night [11:46] thank you all for coming DONT FORGET UBUNTU BUG DAY [11:46] sistpoty, you'll do then [11:46] too [11:46] ok :) [11:46] :) [11:46] Lathiat: what day? ;) [11:46] ogra: I'm not on UBZ ;) [11:46] Lathiat: when? [11:46] Lathiat: Ubuntu WHAT? ;-) [11:46] now/tomorrow [11:46] sivang: #ubuntu-bugs, now! [11:46] sistpoty, thats why you'll look at the topic then :) [11:46] http://wiki.ubuntu.com/UbuntuBugDay [11:46] ogra: or do you mean looking at the topic *g* [11:46] bye [11:46] hehe [11:46] bye [11:46] ok, who wants to write up the meeting summary this week? [11:46] anyone who doesn't give at least 20 bugs attention gets stared at evilly === dolmen [n=dolmen@cho94-1-81-57-157-99.fbx.proxad.net] has joined #ubuntu-meeting [11:47] does someone feel eager to write up the minutes ? [11:47] ogra: I can if you want [11:47] would be nice... === ajmitch will get the evil stare, only touched 1 bug today [11:47] I can't unfortunately, I've been too distracted with RL work. :-( [11:47] but take as much time as you need :) [11:47] Lathiat: read the wiki page :) [11:47] ogra: will look at it in weekend then [11:47] Lathiat: you're taking the wrong approach [11:47] ajmitch, take your time [11:47] ok guys... see you [11:47] dholbach: heh [11:47] bye dholbach [11:47] grrr. disconnect without noticing :/ [11:47] gn8 dholbach [11:48] ogra: long weekend for me :) === dholbach [n=daniel@i577B0EAC.versanet.de] has left #ubuntu-meeting ["Ex-Chat"] [11:48] ok, meeting closed :) [11:48] yay [11:48] thanks all for attending [11:48] <\sh> well... [11:48] LOL [11:48] hug day! [11:48] hrhr [11:48] i like the evil stares option personally === \sh will have the next days a lot of RL work to do :( [11:48] bye folks === ajmitch will bbl [11:49] <\sh> 26th is my last day of RL stress work :( [11:49] \sh: I had time like this 2 weeks ago, was icky :-/ [11:49] bye siretart [11:49] night sistpoty [11:49] night siretart [11:49] Gnight folks [11:49] <\sh> sivang: well...we're preparing for a new channel line up for two german counties [11:49] Wow [11:49] <\sh> sivang: digital television :( [11:50] <\sh> sivang: and our german pay tv company named premiere wants to change to hdtv as well during these days... [11:50] <\sh> it's a mess [11:50] bah, too much transitions eg? [11:51] <\sh> sivang: yeah...cxx trans + ftbfs in 3 days [11:51] <\sh> and a bunch of meetings with all those people who don't have a clue..but wants to have a say [11:52] Heh [11:52] <\sh> shit...this channel is logged...but I never mentioned ISH ,-> [11:52] :-) [11:53] <\sh> ogra: help...I'm playing with my career [11:54] \sh, good :) [11:55] <\sh> hmm.. [11:55] \sh: lol [11:55] <\sh> ogra: u didn't push klaus onto my back, to give me good piece of advises to leave the company? ,-) [11:55] <\sh> pieces of advise even [11:56] \sh: this is SO much known , for me as well :-/ [11:57] \sh, not yet... thats still to come... my last resort if you want :) [12:03] <\sh> ogra: he starts already since I know that he is leaving... [12:03] <\sh> anyways...