/srv/irclogs.ubuntu.com/2007/06/29/#ubuntu-meeting.txt

=== blenderhead001 [n=blenderh@adsl-068-209-133-121.sip.jax.bellsouth.net] has joined #ubuntu-meeting
=== licio [n=licio@ubuntu/member/licio] has joined #ubuntu-meeting
=== Ju` is now known as Ju
=== doko_ [n=doko@dslb-088-073-091-187.pools.arcor-ip.net] has joined #ubuntu-meeting
=== doko__ [n=doko@dslb-088-073-096-158.pools.arcor-ip.net] has joined #ubuntu-meeting
=== hoora_ [i=ariel@gateway/tor/x-3917fcd00b4be3d4] has joined #ubuntu-meeting
=== neversfelde|mobi [n=neversfe@nrbg-4d071327.pool.mediaWays.net] has joined #ubuntu-meeting
=== licio_ [n=licio@c9500471.bhz.virtua.com.br] has joined #ubuntu-meeting
=== licio_ [n=licio@c9500471.bhz.virtua.com.br] has joined #ubuntu-meeting
=== mjg59 [n=mjg59@cavan.codon.org.uk] has joined #ubuntu-meeting
=== karimfayez [n=karim@196.219.129.102] has joined #ubuntu-meeting
=== jsgotangco [n=jsg123@ubuntu/member/jsgotangco] has joined #ubuntu-meeting
=== Admiral_Chicago_ [n=Freddy@adsl-76-223-80-221.dsl.chcgil.sbcglobal.net] has joined #ubuntu-meeting
=== Admiral_Chicago_ [n=Freddy@ubuntu/member/admiral-chicago] has left #ubuntu-meeting []
=== merriam_ [n=merriam@85-211-239-240.dyn.gotadsl.co.uk] has joined #ubuntu-meeting
=== neversfelde|mobi [n=neversfe@nrbg-4d07149f.pool.mediaWays.net] has joined #ubuntu-meeting
=== zul_ [n=chuck@mail.edgewater.ca] has joined #ubuntu-meeting
=== licio [n=licio@ubuntu/member/licio] has joined #ubuntu-meeting
=== lfittl [n=lfittl@2001:6f8:107e:30:216:36ff:fe17:3cef] has joined #ubuntu-meeting
=== never|mobi [n=neversfe@nrbg-4d07149f.pool.mediaWays.net] has joined #ubuntu-meeting
=== Shely [n=huahua@60.20.49.26] has joined #ubuntu-meeting
=== cynics [n=cynics@123.116.101.251] has joined #ubuntu-meeting
=== jsgotangco [n=jsg123@ubuntu/member/jsgotangco] has joined #ubuntu-meeting
=== Admiral_1hicago_ [n=Freddy@adsl-76-223-80-221.dsl.chcgil.sbcglobal.net] has joined #ubuntu-meeting
=== Admiral_Chicago_ [n=Freddy@ubuntu/member/admiral-chicago] has left #ubuntu-meeting []
=== anibal [n=anibal@debian/developer/anibal] has joined #ubuntu-meeting
=== anibal [n=anibal@debian/developer/anibal] has left #ubuntu-meeting ["Leaving"]
=== Hobbsee [n=Hobbsee@ubuntu/member/hobbsee] has joined #ubuntu-meeting
=== asac_ [n=asac@debian/developer/asac] has joined #ubuntu-meeting
=== hjmf_ [n=hjmf@150.Red-83-44-175.dynamicIP.rima-tde.net] has joined #ubuntu-meeting
=== AndyP [n=andyp@ubuntu/member/welshbyte] has joined #ubuntu-meeting
=== Burgundavia [n=corey@ubuntu/member/burgundavia] has joined #ubuntu-meeting
=== oxxa [n=axxo@83.217.70.247] has joined #ubuntu-meeting
=== zakame [n=zakame@ubuntu/member/zakame] has joined #ubuntu-meeting
=== Fujitsu [n=fujitsu@ubuntu/member/fujitsu] has joined #ubuntu-meeting
=== Hobbsee [n=Hobbsee@ubuntu/member/hobbsee] has joined #ubuntu-meeting
=== oxxa_ [n=axxo@83.217.70.247] has joined #ubuntu-meeting
=== zul_ [n=chuck@mail.edgewater.ca] has joined #ubuntu-meeting
=== highvoltage [n=highvolt@196.1.61.44] has joined #ubuntu-meeting
=== bashelier [n=bashelie@srv122.hosteur.com] has joined #ubuntu-meeting
=== oxxa [n=axxo@gentoo/developer/axxo] has joined #ubuntu-meeting
=== pkl_ [n=phillip@unaffiliated/pkl/x-764568] has joined #ubuntu-meeting
=== gouki [n=gouki@ubuntu/member/gouki] has joined #ubuntu-meeting
=== [PUPPETS] Gonzo [i=gonzo@80.69.47.16] has joined #ubuntu-meeting
=== _[PUPPETS] Gonzo [i=gonzo@80.69.47.16] has joined #ubuntu-meeting
=== pkl__ [n=phillip@lougher.demon.co.uk] has joined #ubuntu-meeting
=== gouki_ [n=gouki@ubuntu/member/gouki] has joined #ubuntu-meeting
=== zul [n=chuck@mail.edgewater.ca] has joined #ubuntu-meeting
=== highvoltage [n=highvolt@196.1.61.44] has joined #ubuntu-meeting
=== bashelier [n=bashelie@srv122.hosteur.com] has joined #ubuntu-meeting
=== thekorn_ [n=thekorn@a89-182-133-18.net-htp.de] has joined #ubuntu-meeting
=== dholbach [n=daniel@i59F77EBF.versanet.de] has joined #ubuntu-meeting
=== juliux [n=juliux@ubuntu/member/juliux] has joined #ubuntu-meeting
Hobbsee@schedule sydney08:43
ubotuSchedule for Australia/Sydney: 29 Jun 21:00: MOTU Team | 04 Jul 05:00: Technical Board | 05 Jul 06:00: Edubuntu | 06 Jul 06:00: Ubuntu Development Team | 11 Jul 01:00: Kernel Team | 11 Jul 22:00: Edubuntu08:43
=== allee [n=ach@dialin-212-144-131-137.pools.arcor-ip.net] has joined #ubuntu-meeting
=== tkjacobsen [n=tkjacobs@h59ec0f85.c45-01-03.dyn.perspektivbredband.net] has joined #ubuntu-meeting
=== lionel [n=lionel@ip-211.net-81-220-127.rev.numericable.fr] has joined #ubuntu-meeting
=== slomo [n=slomo@ubuntu/member/slomo] has joined #ubuntu-meeting
=== emonkey-m [n=emonkey@static-pro-212-101-27-121.adsl.solnet.ch] has joined #ubuntu-meeting
=== asac_ [n=asac@debian/developer/asac] has joined #ubuntu-meeting
=== PriceChild [n=pricechi@ubuntu/member/pricechild] has joined #ubuntu-meeting
=== mc44 [n=mc44@unaffiliated/mc44] has joined #ubuntu-meeting
cynics@schedule shanghai11:05
ubotuSchedule for Asia/Shanghai: 29 Jun 19:00: MOTU Team | 04 Jul 03:00: Technical Board | 05 Jul 04:00: Edubuntu | 06 Jul 04:00: Ubuntu Development Team | 10 Jul 23:00: Kernel Team | 11 Jul 20:00: Edubuntu11:05
=== neversfelde|mobi [n=neversfe@nrbg-4d07149f.pool.mediaWays.net] has joined #ubuntu-meeting
=== tkjacobsen [n=tkjacobs@h59ec0f85.c45-01-03.dyn.perspektivbredband.net] has joined #ubuntu-meeting
=== mvo [n=egon@p54A6725F.dip.t-dialin.net] has joined #ubuntu-meeting
=== geser [i=mb@ubuntu/member/geser] has joined #ubuntu-meeting
=== persia [n=persia@ubuntu/member/persia] has joined #ubuntu-meeting
=== persia [n=persia@ubuntu/member/persia] has joined #ubuntu-meeting
=== relix [n=david@d51A403D1.access.telenet.be] has joined #ubuntu-meeting
=== ranf [n=ralfm@dslb-084-058-096-068.pools.arcor-ip.net] has joined #ubuntu-meeting
=== sky_walki [i=czzhrd02@xdsl-563.lodz.dialog.net.pl] has joined #ubuntu-meeting
=== sky_walkie [i=czzhrd02@xdsl-563.lodz.dialog.net.pl] has joined #ubuntu-meeting
=== afflux [i=fnord@pentabarf.de] has joined #ubuntu-meeting
=== emonkey-m [n=emonkey@static-pro-212-101-27-121.adsl.solnet.ch] has joined #ubuntu-meeting
=== emonkey-m [n=emonkey@static-pro-212-101-27-121.adsl.solnet.ch] has joined #ubuntu-meeting
=== anibal [n=anibal@debian/developer/anibal] has joined #ubuntu-meeting
=== sky_walkie [i=czzhrd02@xdsl-563.lodz.dialog.net.pl] has left #ubuntu-meeting []
=== lfittl [n=lfittl@2001:6f8:107e:30:216:36ff:fe17:3cef] has joined #ubuntu-meeting
=== anibal [n=anibal@debian/developer/anibal] has left #ubuntu-meeting ["Leaving"]
bashelier@schedule Paris12:48
ubotuSchedule for Europe/Paris: 29 Jun 13:00: MOTU Team | 03 Jul 21:00: Technical Board | 04 Jul 22:00: Edubuntu | 05 Jul 22:00: Ubuntu Development Team | 10 Jul 17:00: Kernel Team | 11 Jul 14:00: Edubuntu12:48
=== ..[topic/#ubuntu-meeting:ubotu] : Current meeting: MOTU Team | Calendar: http://fridge.ubuntu.com/event | Logs: https://wiki.ubuntu.com/MeetingLogs/ | 03 Jul 19:00 UTC: Technical Board | 04 Jul 20:00 UTC: Edubuntu | 05 Jul 20:00 UTC: Ubuntu Development Team | 10 Jul 15:00 UTC: Kernel Team | 11 Jul 12:00 UTC: Edubuntu
=== Lutin [n=Lutin@ubuntu/member/lutin] has joined #ubuntu-meeting
bashelierhey Lutin12:57
=== Zic [n=Zic@Final-Fantasy.FF-IRC.net] has joined #ubuntu-meeting
Zic@now12:57
ubotuCurrent time in Etc/UTC: June 29 2007, 10:57:27 - Current meeting: MOTU Team12:57
Lutinheya bashelier12:57
Zico/ Lutin :)12:57
Lutinhi Zic12:57
dholbachhiya12:59
geserHi12:59
ajmitchhello12:59
dholbachwho else from the MOTU crew do we have here?12:59
=== ajmitch is sort of here, if I count
=== persia is present
Adri2000hi12:59
=== TheMuso [n=luke@ubuntu/member/themuso] has joined #ubuntu-meeting
ScottKScottK here01:00
=== StevenK [n=stevenk@14.5.233.220.exetel.com.au] has joined #ubuntu-meeting
=== TheMuso is here.
=== Hobbsee [n=Hobbsee@ubuntu/member/hobbsee] has joined #ubuntu-meeting
StevenKHrm. Wonder if ScottK is here this time.01:00
dholbachto get some rotation going on, who would like to run today's meeting?01:00
dholbachagenda is here: https://wiki.ubuntu.com/MOTU/Meetings01:00
lionelhi01:00
dholbachto get some rotation going on, who would like to write up the minutes of today's meeting?01:00
=== persia volunteers to chair, if nobody else wants it
=== pygi [n=mario@83-131-1-43.adsl.net.t-com.hr] has joined #ubuntu-meeting
ScottKStevenK: Yes.  You can quit wondering.01:01
=== TheMuso would do the minutes, but he is going away for a week tomorrow.
=== persia retracts volunteering after reviewing the agenda
StevenKScottK: :-P01:01
TheMusoSO I can't be sure of getting them out before I go01:01
dholbachok, I'll run the meeting - if somebody could just take a very few notes, that'd be nice01:02
dholbachpersia's item is the first on the agenda: Should setting a date for REVU days be a Fixed topic?01:02
=== man-di [n=mkoch@dyndsl-080-228-194-004.ewe-ip-backbone.de] has joined #ubuntu-meeting
dholbachI personally think that's a great idea01:02
persiaIn the last couple MOTU meetings, there have been discussions of REVU days.  Should this be a standard part of the Fixed Topics?  That wold save anyone remembering each time.01:02
=== ScottK too. Lets do it. Next item... ;-)
dholbachexcellent idea01:03
dholbachrock on - thanks persia - somebody please add it01:03
StevenKMaybe not setting a date, but at least discussing it.01:03
TheMuso+101:03
persiaStevenK: I'd rather set a date each time.01:03
persia(or attempt to do so)01:03
dholbachyes, I think it's good to settle on it and get moving quickly01:03
ScottKStevenK: Maybe we set a date like two months from today....01:03
StevenKFair enough.01:04
Hobbseepersia: good idea01:04
=== crimsun [n=crimsun@pdpc/supporter/silver/crimsun] has joined #ubuntu-meeting
dholbachok cool, moving on01:04
dholbachpersia's second item is: Does the Sponsorship Process need adjustment for SRUs?01:04
dholbachhi crimsun01:04
dholbachpersia: what is the problem that you're seeing with sponsoring and SRUs?01:04
persiaThe sponsorship queue seems to be working very well for bugs against gutsy, but SRUs are not being processed as quickly.  Should there be a different procedure for these?01:04
persiadholbach: Right.  The SRUs aren't attracting as much sponsorship attention, and I'm wondering if a process change or a team would help.01:05
=== Hobbsee doesnt do SRU's.
ScottKpersia: My generic problem with the UUS queue is I have a hard time telling if something's ready to be sponsored if I only have time to deal with one or two.01:06
ScottKSo I look and throw up my hands.01:06
ScottKAnd move on.01:06
ScottKThis is true for SRU or not.01:06
dholbachso if I want to do a SRU, I file a bug, subscribe ubuntu-universe-sponsors to it and nobody will upload because it's feisty-proposed instead of gutsy in the upload target?01:06
StevenKI think the problem is that sponsors might go, "Ooh, an SRU. I'm not qualified/care enough to deal with it, since SRUs are Big and Scary"01:06
persiaScottK: My method is to grab the first couple and take a quick look.  If something is funny, I invalidate and otherwise upload.01:06
ScottKI did an SRU this week because it was one I hit that was ready.01:06
TheMusoc01:07
TheMusough01:07
persiadholbach: Some of them are being processed, but it doesn't happen as quickly.01:07
=== persia seconds StevenK
crimsunwhat seems to be the mean lag order on SRU processing?  Weeks?  Months?01:08
Hobbseeand you usually get shot down if the fix doesnt actually fix the problem, etc.01:08
=== ScottK tends to think along the lines of it's really broken now (or it wouldn't qualify for SRU), so how much worse can I make it..
=== TheMuso hasn't done SRUs simply because he hasn't aquainted himself properly with the procedure, which is just a amtter of reading.
dholbachwhat could we do to request more reassurement?01:08
persiacrimsun: I haven't calculated that, but there are at least a couple that are from May.01:08
StevenKMaybe an SRU should adopt a REVU like solution. Two ACKs for it to be okay, and the second one uploads it.01:08
dholbachStevenK: that'd revert some parts of the universe sru process - we'd have a team that'd evaluate it again - I personally don't think that's wrong at all01:09
ScottKMaybe people needing sponsoring for an SRU should add a tag for SRU and release (like sru edgy)01:09
StevenKdholbach: I don't see that as being a bad thing, speaking as a former member of motu-sru. :-)01:09
=== afflux [i=fnord@pentabarf.de] has left #ubuntu-meeting []
persiaI think it would be better to have the ACK be optional, rather than required, just to not interfere with the security processing.01:09
ScottKOnce someone's reviewed it they add a tag like motu.01:10
StevenKSRU isn't security. And shouldn't be.01:10
ScottKStevenK: +101:10
dholbachI think it'd help if people just verified it and asked in #ubuntu-motu or in the mailing list for a second opinion01:10
=== jhansonxi [n=jhansonx@d24.as1.lnng1.mi.core.com] has joined #ubuntu-meeting
StevenKWhich is informally my suggestion anyway01:10
=== ScottK would join a team looking at SRUs.
dholbachok, so how would we go about codifying it?01:11
crimsunmaybe it's a simple lack of publicity01:11
persiaThe value to formalisation is that the docs will point people to the right thing (if someone writes a doc), whereas informal may not become part of out collective knowledge.01:11
StevenKScottK: We played that game, and then stopped01:11
=== ScottK knows
dholbachmaybe just add a tag needs-sru-verification or something?01:11
=== ScottK prefers the tag approach.
persiaStevenK: Is there a reason there couldn't be a volunteer team that worked on them, despite the lack of a formal requirement for ACK?01:12
crimsunI'm not convinced that throwing more overhead into it really helps; people seemed unhappy with collecting ACKs01:12
=== ScottK would help on a team, but doesn't think it's the best way.
StevenKcrimsun: Agreed01:12
TheMusocrimsun: +101:12
dholbachit wouldn't be a necessity01:12
dholbachjust asking for another opinion01:12
dholbach(in case you're unsure)01:12
dholbachthat tag would say "I'm happy with it, but please make sure and upload if you think it's ok too"01:13
persiaAlternately, with -proposed in place, should there be a strong gatekeeper?  Is there any reason not to upload if it looks sane, and let the standard SRU process filter?01:14
StevenKWhereas you don't have to set it and can just upload it if you think it's okay as well01:14
crimsundoes LP have an interface for say, a weekly cron executed from tiber (or elsewhere) that would search for tagged SRU bug reports and send an email to ubuntu-motu@ ?01:14
ScottKOne process clarification....  If I sponsor someone's SRU, am I responsible for writing the mail to the mailing list/setting tags/etc or are they?01:14
persiaScottK: currently, you are (I prefer the sponsoree to be responsible).01:14
ScottKpersia: That's what I thought.01:15
ScottKThat might also be a barrier to getting SRUs uploaded.01:15
dholbachhttps://bugs.launchpad.net/ubuntu/+bugs?field.tag=motu-sru-verification01:15
dholbachor something01:15
ScottKMaybe we should change that.  After all the one that wrote the fix is most familiar/cares.01:15
=== sistpoty|work [n=potyra@faui31w.informatik.uni-erlangen.de] has joined #ubuntu-meeting
TheMusoAfter reading the procedure, SRUs are now clearer to me, and are easier than I thought.01:16
dholbachI think it'd be ok for the sponsor to tell the fix author to write the mail or for them to agree on a procedure01:16
dholbachso they can figure it out on their own01:16
persiaIs there a mechanism (other than IRC) for removing the uploads from -proposed if the author doesn't follow-up?01:17
ScottKpersia: Unless they are known to be broken, I don't see a harm in leaving them there.01:17
crimsunpersia: the normal "file a bug, subscribe ubuntu-archive"01:17
dholbachbug reports with ubuntu-archive subscribed?01:17
dholbachdoes anybody object adding a tag to ask for a second opinion and making the sponsor-mails-the-lists rule more lax and wiki-ing and announcing it?01:20
persiaSo, unless there is more discussion, I'll update the sponsor queue processing guide to indicate that SRUs should be uploaded to -proposed if sane, that MOTUs are welcome to use the motu-sru-verification tag if they aren't sure, and that the author may be responsible for the notifications and follow-up if so agreed in advance.01:20
siretarthi! (sorry for being late)01:20
StevenKpersia: +101:20
=== Hobbsee requests keybuk's presence here for the MoM/DaD discussion
dholbachpersia: great01:20
ScottKpersia: +101:20
=== Pici [n=pcmacman@unaffiliated/pici] has joined #ubuntu-meeting
dholbachthanks a lot persia01:20
TheMuso+101:20
geser+101:20
ScottKsiretart: Thanks for volunteering to be in charge of the revised SRU process.01:20
dholbachScottK: wants to talk about clamav01:21
ScottK;-)01:21
ScottKdholbach: Let Adri2000 go first.01:21
StevenKPurge clamav from the archive.01:21
siretartScottK: huh? sorry?01:21
dholbachok, I'm happy with that01:21
=== ScottK understands he/lutin have to run.
StevenKLet's move on.01:21
ScottKsiretart: Just kidding.01:21
=== StevenK smirks.
dholbachLutin, Adri2000: your stage01:21
dholbachhttps://wiki.ubuntu.com/DaDandMoM01:21
Adri2000okay01:21
basheliermay I go ?01:21
Adri2000I think bashelier has a quick intro01:22
Adri2000ho01:22
Adri2000go01:22
bashelierUbuntu is a free and open-source distribution, then it seems normal to develop an open-source tool to replace a proprietary one. This is the case for MoM and DaD, and moreover when both tool, one free and one non-free, we usually use the free one. But the fact to have two merge tools is quite confusing, especially that MoM is supported by Canonical and DaD is not.01:22
bashelierBut the fact is that DaD seems to be, at least for universe, very used, see comments in http://dad.dunnewind.net/universe.php for example. Then there are several possible issue to this problem, see the wiki page https://wiki.ubuntu.com/DaDandMoM for further informations.01:22
Adri2000after a discussion in -motu, we set up this wikipage in order to solve this issue01:23
Hobbseewhat are we attempting to acheieve out of this?  a recommendation on which to use?  a way to find out if and how DaD/MoM can integrate?01:23
Hobbseei'm finding this slightly unclear01:23
StevenK"MoM isn't free, ours is and apparently better, so let's use it for everything." is what I can see.01:24
Adri2000Hobbsee: avoid confusion, especially for newcomers, about which one to use, why there are two merge systems01:24
persiaStevenK: See Proposal #301:24
bashelier3. Add DaD's features to MoM, and keep MoM closed01:25
dholbachI think it's better to send the proposal to ubuntu-devel@ and CC keybuk01:25
dholbachas the scope of the proposal is not just universe01:25
dholbachand motu01:25
siretartmy 2 : the killer feature of DaD are the comments. they might not be as necessary for main, but I think they help a lot in universe.01:25
TheMusoagreed. Core devs have to feel comfortable with this as well.01:25
Hobbseedholbach: i can do that.  i was speaking to sabdfl about this earlier anyway, and he asked to be CC'd01:25
dholbachnice01:26
Hobbseewhihc things of DaD do we want added to MoM?01:26
ScottKBut someone should e-mail keybuck first so he doesn't get blindsided.01:26
Adri2000dholbach: but I haven't seen any core-dev using DaD, so I'm not sure they are very well aware of the problem01:26
=== persia likes comments
bashelierHobbsee: comments01:26
siretartsince it is used a lot in universe, I think we can settle on DaD for universe01:26
Hobbseesorry, i meant apart from the comments01:26
dholbachAdri2000: we all agree that there should be one solution and comments are good01:26
Hobbseeis there anything *apart* from them?01:26
=== ScottK thinks the fact that it runs more often is good.
=== ScottK also like that it'll do the maintainer mangling for you.
persiaI thought MoM ran every 15 minutes now.01:26
Adri2000Hobbsee: open-source, automatic maintainer update01:27
HobbseeAdri2000: auto maintainer update?01:27
=== ScottK also likes the open source part.
TheMusoI'm not so sure that auto maintainer update is the best thing in the world01:27
Hobbseeoh, maintainer mangling01:27
persiaI don't like the implementation of the auto-maintainer-update - it sometimes breaks things.01:27
siretartHobbsee: having active and responsive maintainers01:27
=== Keybuk [n=scott@quest.netsplit.com] has joined #ubuntu-meeting
Hobbseehi Keybuk01:27
Adri2000Hobbsee: yes, DaD automagically updates the maintainer field if it isn't yet an @ubuntu.com address01:27
dholbachKeybuk: https://wiki.ubuntu.com/DaDandMoM is the proposal we're talking about01:27
Adri2000using the update-maintainer script from Lutin01:28
=== gnomefreak [n=gnomefre@ubuntu/member/gnomefreak] has joined #ubuntu-meeting
Lutinpersia: please mails me about that with examples, will have a look asap01:28
Adri2000hi Keybuk01:28
=== Nicke_ [n=niclasa@ua-83-227-140-135.cust.bredbandsbolaget.se] has joined #ubuntu-meeting
HobbseeKeybuk: the upshot of this is, MoM is missing the comments field and maintainer mangling.  The attempt is to find which one to use and recommend to prospective developers, looking into doing merging.01:28
Lutinheya Keybuk01:28
persiaLutin - it's the same class of bugs we discussed before for which I said I'd hunt a patch.  No worries.01:28
HobbseeKeybuk: do you have any thoughts on this?01:29
=== tkjacobsen [n=tkjacobs@h59ec0f85.c45-01-03.dyn.perspektivbredband.net] has joined #ubuntu-meeting
KeybukMoM also fulfils our obligations to Debian about returning patches, which DaD doesn't01:29
Lutinpersia: ok, cool01:29
sistpoty|workKeybuk: but that's unrelated with displaying stuff for merges, right?01:30
Keybukno01:30
siretartKeybuk: espc. in universe land the commenting feature of DaD have been very helpful. Is there any possibility to 'free mom' (or at least the relevant parts) so that we can send you patches which implement them?01:31
Keybukit's part of the same process and tool01:31
Keybuksiretart: that is a question for sabdfl01:31
sistpoty|workKeybuk: the same tool, I can see, but in what way the same process?01:31
Adri2000Keybuk: I didn't know returning patches was MoM's job, but could have I known since MoM is closed? :)01:31
KeybukAdri2000: that is not a useful comment01:32
Adri2000that was just to introduce proposal #101:32
Keybukfrom what I can see01:33
=== crimsun [n=crimsun@pdpc/supporter/silver/crimsun] has left #ubuntu-meeting []
KeybukDaD has many of the problems we fixed with MoM a long time ago01:33
Keybuk(reliance on snapshot.dn, for example)01:33
Keybukbut has a prettier web interface01:33
KeybukMoM is pretty reliable and rock-solid, but has a web interface written by someone who hates HTML (me)01:33
ScottKSo isn't there some way we can take the best of both and (ironically) merge them?01:34
Adri2000Keybuk: how does MoM get the base version when it's not available on snapshot.d.n?01:34
persiaKeybuk: Could others help with the interface?01:34
bashelierthat's proposal #401:34
bashelierFree only part(s) of MoM, such as the UI01:34
Keybukthe UI isn't non-free01:34
Keybukit's exactly what you see there, an HTML page that's written out by some crappy python01:34
KeybukMoM could write out a list of packages available for merging, and useful information about them, (such as URLs, version numbers, etc.) to a machine-parseable file01:35
Keybukthat the DaD UI could pick up and use for tracking01:35
dholbachwhat do you think about taking this to ubuntu-devel@ and also including sabdfl in the discussions?01:36
persiaLet's call that proposal #501:36
dholbachat the moment, I don't see us coming to a conclusion in this meeting01:37
bashelierKeybuk: DaD UI is generated from something like http://dad.dunnewind.net/tomerge-universe, then it would be simple yes01:37
=== ScottK thinks it should all be opened up unless there is a strong reason not.
sistpoty|workwhat if MoM will be out again during the next merge cycle?01:38
=== ScottK also agrees with dholbach that it's not going to get completely solved here.
KeybukScottK: Canonical would like to be able to pay its developers, and would like to be able to offer tools such as MoM as a paid service to other distros01:38
Keybukthat is the fundamental rationale for why we've never released the code01:38
ScottKKeybuk: I understand there's a balance here.01:38
=== Pici [n=pcmacman@unaffiliated/pici] has left #ubuntu-meeting []
Keybuksistpoty|work: it won't?01:39
sistpoty|workgood :)01:39
Keybukit was down due to hardware issues; which are unrelated to the software01:39
sistpoty|workbut not unrelated to the freeness :P01:39
ScottKFrom a user of the service perspective though, the why is irrelevant.01:39
Keybuktotally unrelated01:39
Keybukif the source were open, you'd still need someone with good bandwidth and .5TB of risk01:40
Keybukuh, of disk01:40
Keybuk:p01:40
TheMusohahaha01:40
siretartbashelier: Adri2000: what do you think about MoM giving status about available packages to merge, and make DaD a frontend to that?01:40
ScottKYes.  Getting that didn't seem to be a problem.01:40
basheliersiretart: I also have a proposal #601:40
basheliersiretart: why not to keep both DaD and MoM, and join the comments, I mean have unique comments for the two tools, which would help to avoid duplicated work, and let the choice for the favorite tool.01:41
bashelierbut use DaD as an UI, why not.01:41
Adri2000siretart: I think it's a good idea01:41
dholbachok great01:41
dholbachlet's see how that works out01:41
ScottKIt's certainly a start.01:41
KeybukI have no problem with somebody implementing a UI for MoM (I can hardly call the current report html a UI :p)01:41
KeybukI can ensure that the appropriate data is available01:41
dholbachnice :-)01:41
Adri2000Keybuk: and put this UI on merges.ubuntu.com?01:41
AndyPlike launchpad is closed but still accepts bug reports from it's users (good thing), is MoM open to bug reports/feature requests too?01:42
KeybukWe also have no problem if a community member wishes access to the MoM source under an NDA, and can hack on it themselves01:42
KeybukAndyP: of course01:42
KeybukAdri2000: depending on what it's written in, sure01:42
TheMusoI would like to see if any core devs have an opinion, as the new UI could effect them as well.01:42
geseris MoM all python?01:42
Keybukgeser: yes;01:43
LutinTheMuso: indeed01:43
TheMusoOr at the least, get some core dev's thoughts.01:43
Keybukthe usual theory with core-dev is that MoM implements the minimum necessary01:43
TheMusoRight.01:43
Keybukwe don't tend to care so much about claims, or treading on people's toes01:43
Keybuksince we're a smaller team with a much smaller based of packages01:43
dholbachok, are there any more open questions about this item?01:44
TheMusoNevertheless, if the UI is going to change, wider opinions should be considered.01:44
persiaI'd like to see comments on main, if only to say (as a MOTU) - I'll be a while on this one - someone should grab it if they're interested.01:44
Keybukon the options on the wiki:01:45
Keybuk#1 is probably untenable, unless you can persuade sabdfl of the benefits since it's his call01:45
ScottKThe DaD team working the UI should also consider the new/updated merges split that MoM has (and explain the difference somewhere).01:45
Keybuk#2 is also untenable, since MoM does more than just "merges"; not to mention is a much more mature solution than DaD01:45
Keybuk#3 seems reasonable from a UI POV.01:45
KeybukScottK: hah01:45
KeybukScottK: the DaD team could do a *much* better job <g>01:46
Keybukthe difference between new/updated is "does the top entry in debian/changelog say 'gutsy'?"01:46
ScottKRight.01:46
Keybukit assumes that if the package has ever been uploaded to the current distro, it is "updated"01:46
=== ScottK only recently figured that out.
Keybukso often updated things have never been merged01:46
dholbachthanks a lot Lutin, bashelier and Adri2000 for working on this01:47
dholbachis it ok to discuss the implications of the UI changes on the mailing list?01:48
TheMuso+101:48
bashelierdholbach: yes01:48
Adri2000yep01:48
Lutinyep01:48
persiaSounds good to me.01:48
dholbachthanks a lot - please write also to the mailing list once people can test the UI01:48
siretartwell, we need help from the MoM side01:49
Lutinwell, gotta run. see you later01:49
dholbachbye Lutin - have a nice day01:49
Keybuksiretart: scott@ubuntu.com :-)01:49
dholbachshall we move on to ScottK's item?01:49
Keybuk(well, when I have my mail server running again <g>)01:49
TheMusoThanks for your time Keybuk.01:49
dholbachthanks Keybuk01:49
dholbachScottK: https://lists.ubuntu.com/archives/ubuntu-motu/2007-June/001747.html - your stage01:50
ScottKWhen last we met (that I was here) there was a move to go look at the API differences between libclamav1 and libclamav2 and see how big a deal they are.  I asked for volunteers to work on that (I'm hopelessly unqualified) and got zero volunteers.  The next idea I have for clamav and rdepends support is here: https://lists.ubuntu.com/archives/ubuntu-motu/2007-June/001747.html - I'll give everyone a minute to read ...01:50
ScottKIt's clear we need to do something, particularly for server LTS support.01:50
Hobbseethankyou Keybuk01:50
ScottKComments?01:50
ajmitchas it is, clamav won't be getting updated definitions with 0.8x01:50
=== Keybuk [n=scott@quest.netsplit.com] has left #ubuntu-meeting [""]
persiaI don't think a separate project works well, unless there is strong repository support.  Also, it breaks things if volunteers don't step up for all the rdepends.  Lastly, is makes security updates harder.01:51
ScottKThe trick is that by backporting just clamav, we can give the appearance of coverage, without the actuality.  If you doubt me, go try and find a test virus with the version of clamtk released for Feisty.01:52
ajmitchpersia: that's ok, as it stands clamav can't get security fixes anyway :)01:52
ScottKMy thought is to have a team to test and then have a wiki to describe what's been tested/works/is broken so people know what they are getting into.01:52
ajmitchScottK: using PPAs?01:53
persiaScottK: I like the idea of a team, but why not use normal SRUs for it all?  It's a lot of things to push at once, but I'd rather see it in the normal archive.01:53
ScottKajmitch: I'm open on the exact mechanism.  I'd envisioned repositories similar to -backports, but that would get the archive admins off the critical path.01:53
dholbachI just checked - the diff between libclamav from dapper to gutsy is around 62K lines01:54
ScottKpersia: If there were enough resources to SRU everything that needed changing, we wouldn't be here.01:54
ajmitchdholbach: that's just the library, right?01:54
TheMusoouch01:54
persiaScottK: True.01:54
ScottKclamav has a painful number of rdepends.01:54
dholbachyes clamav*/libclamav01:54
ScottKWe won't get all of them.01:54
ajmitcha lot of applications would need significant changes (new upstream versions) to work with the newer clamav01:55
=== ScottK will do the stuff I use.
ScottKajmitch: Yes.  Definitely.01:55
ScottKThat's why the current clamav doesn't qualify for regular backports even.01:55
dholbachup until now, it looks like added API (which is no trouble) and changed return values01:55
=== juliux [n=juliux@ubuntu/member/juliux] has joined #ubuntu-meeting
dholbachit's not feasible to make a wiki page with lists of changes01:56
TheMuso~/c01:56
TheMusough01:56
=== ogra [n=ogra@ubuntu/member/ogra] has joined #ubuntu-meeting
dholbachI think it'd take trial&error just trying to compile older versions with the newer clamav01:56
ScottKdholbach: I was thinking more like a list of known to work/known not to work.01:56
dholbachif we were to patch things01:57
=== Hobbsee_ [n=mystery@ubuntu/member/hobbsee] has joined #ubuntu-meeting
ScottKI think patching things just isn't going to get there as you couldn't backport the newer clamav until you had patches for ALL the rdepends.01:57
ScottKHeat death of the Universe would happen first.01:57
=== ajmitch imagines the pain if clamav was in main
dholbachwe had 21 source package or something?01:57
TheMusoajmitch: I was thinking about that earlier.01:58
dholbach({build-,}depending on it?01:58
geseryes, something like that01:58
lioneldo we know how they manage it in volatile.debian.net ? Here there are latest version of clamav. It may break things (I did not dig in it)01:58
ajmitchTheMuso: at least then it'd be Not Our Problem :)01:58
TheMusoajmitch: heh01:58
ScottKlionel: That's just the latest upstream.01:58
ScottKIt'll break things.01:58
Hobbsee_ajmitch: try not to think about it01:59
lionelah, thanks ScottK01:59
dholbachScottK: is dapper -> gutsy what we're looking at atm (regarding API breakage)?01:59
ScottKNo, Feisty.01:59
ScottKDapper -> Feisty.01:59
=== Hobbsee [n=Hobbsee@ubuntu/member/hobbsee] has joined #ubuntu-meeting
dholbachok01:59
ScottKFeisty is good until the next API change...01:59
dholbachwhat if we all grabbed a source package or two each and at least tried building it and see how it goes?01:59
ScottKBut as an example of the kinds of problems backporting the newer clamav's would cause, the clamtk in Feisty can't find virus.02:00
TheMusoCould we try and encourage upstream to make it easier to support older versions with defs etc?02:00
dholbachI won't pretend I hadn't other things to do, but I see it as the only realistic option atm02:00
siretartScottK: did you talk to upstream about the problem? how do they think about it?02:00
dholbachfor some build problems you could even find patches in the upstream cvs02:00
ScottKsiretart: Upgrade to the latest version.02:00
dholbachmost projects will have adapted to the new clam api02:00
ajmitchtrying to get those patches to apply to the older versions could be interesting02:02
ScottKThe basic clamav perspective, as I understand it, is there is no promise of API stability until they get to 1.0 and whatever happens in the mean time is a personal problem.02:02
TheMusohmpf02:02
siretartScottK: so they are not helpful at all. interesting02:03
dholbachnot pretty, but this might be a start for a clamtk patch: http://clamtk.cvs.sourceforge.net/clamtk/clamtk/clamtk?r1=1.45&r2=1.40&view=patch02:03
=== ScottK thinks something needs to be done separate repo (or PPA) wise as otherwise everything needs to be upgraded in synch.
dholbachI still think that backporting clamav + fixing apps is not impossible02:04
ScottKdholbach: But you need that for all the rdpends published at the same time you publish the new clamav02:04
ScottKdholbach: It's the synchronization that'll be the problem.02:04
dholbachyou can add Breaks: for that02:05
dholbachso people won't upgrade until the new version is in02:05
=== persia likes the idea of 10 people each grabbing 2 packages, say Tuesday, and preparing a bundle.
dholbachit's ugly, but possible02:05
ScottKOh?02:05
=== ScottK didn't know about that one.
dholbachassuming we had 'breaks:' in dapper already02:05
ajmitchI don't think we did02:06
dholbachadding conflicts for things like that is rather discouraged02:06
persiaReal Breaks: support is new for Gutsy, isn't it?02:06
ScottKIf you can do that, then it'd be doable.02:06
ajmitch"The dpkg in edgy now supports a new kind of dependency relationship, `Breaks'"02:06
ajmitchso, edgy02:06
dholbachedgy, ok - hrm02:06
ScottKSo need to backport that first.02:06
dholbachnot going to happen02:06
dholbachwe won't upload a dpkg/apt with new features02:07
ScottKThen that leaves the LTS release stil screwed.02:07
dholbachwe should discuss that point on the list02:07
=== ScottK thinks that is a good idea for LTS +1
dholbachprimarily we should try fixing the stuff02:07
dholbacheven if the deployment of the fix is still an open issue02:08
=== Hobbsee_ [n=mystery@ubuntu/member/hobbsee] has left #ubuntu-meeting []
ScottKdholbach: But without Breaks, we'd still need fixes for everything before we backport.  That's never gonna happen.02:08
dholbachScottK: can you make a wiki page of the affected packages and ask for help in backporting them to work with the new clamav?02:08
dholbachI'd sign up for one or two02:08
=== Zic [n=Zic@Final-Fantasy.FF-IRC.net] has left #ubuntu-meeting ["Quitte"]
ScottKFirst I guess we need to do testing.02:09
dholbachI think we should offer a complete transition and attack the backport problem as a team02:09
=== karimfayez [n=karim@196.202.64.204] has joined #ubuntu-meeting
ScottKOK.02:09
dholbachsome might be easy, for some we might find upstream patches, some might be real work02:09
dholbachbut we'll never find out otherwise02:09
=== ScottK can make a wiki page with a list of rdepends and people can mark it up as they test stuff.
=== Czessi [n=Czessi@dslb-088-073-033-036.pools.arcor-ip.net] has joined #ubuntu-meeting
dholbachgreat02:09
dholbachtrying to build them in a chroot is of real help already02:10
ScottKOne related point is that the unmodified source package for clamav won't build on Dapper.02:10
ScottKIt needs the Edgy dpgk.02:10
sistpoty|worksorry, need to be off again... cya02:10
dholbachsee you sistpoty|work02:10
dholbachScottK: we should work around that02:10
ScottKIt's a two line change in debian/control.02:11
dholbachthat's fine02:11
ScottKOK.02:11
dholbachok, shall we move on?02:11
ScottKdholbach: So the action out of the meeting is for me to make a wiki page.02:11
dholbachyes and announce it on the mailing list02:12
TheMuso~02:12
TheMuso~02:12
TheMusough02:12
dholbachScottK: thanks a lot for insisting on making a solution happen02:12
ScottKdholbach: One sec02:12
ScottKI also think we should make a team of interested people.02:12
=== ScottK will do that too.
dholbachok cool02:12
ScottKOK, now move on...02:12
dholbachthanks again ScottK02:12
dholbachwe have a few dates to agree on02:13
dholbachnext MOTU meeting?02:13
dholbach2 weeks from now? same time?02:13
TheMusoSounds good.02:13
dholbachany objections?02:13
Hobbseethat works02:13
dholbachok cool - who will announce it?02:13
persiaI'd like to see a time rotation, to be fair to those who haven't attended in a month.  +/- 12 hours?02:13
StevenKNo objections, works for me.02:13
Hobbseemy only objection is that two weeks aftre that, which will be the next proposed meeting, is likely during SLUG02:13
Hobbseewhich various members are planning to actually attend02:14
StevenKThe SLUG meeting is happening now, too02:14
Hobbseetrue02:14
dholbachok then thursday - move by 12h?02:14
ScottKdholbach: Could we have it an hour or two later.02:14
dholbachsure we can - we just need to agree02:15
ajmitchdholbach: 12h earlier than now?02:15
ScottKMake the next one +14 and then go +12 after that02:15
dholbachScottK: so time and date would be?02:15
Hobbseecan you give absolute times please?  not everyone lives on your timezone02:15
dholbach(it'll be too late for me in europe, but that's fine)02:15
ScottKOK, then maybe one hour.02:15
=== slomo [n=slomo@ubuntu/member/slomo] has joined #ubuntu-meeting
ScottK1200 UTC Friday, whicher date it is02:16
ScottKErr02:16
ScottK0000 UTC Saturday02:16
ScottKThen 1200 UTC after that02:16
dholbachI won't be around - as I'll be in london at that time, but that's fine with me if others can agree on it02:17
ScottKAnyone?02:17
persiaI like 0 UTC (as part of rotation).02:17
ScottK0/12000 UTC.  Any objections?02:18
TheMusoNo.02:18
Hobbseeshould be OK here, 10am02:18
dholbachso that'd be two meetings?02:18
persiadholbach: No.  0 UTC is proposed for now + 2 weeks, with 12 UTC sugggested for now L 4 weeks (we'll review in 2 weeks).02:19
dholbachok fine with me02:19
dholbachwho announces it?02:19
dholbachcome on02:20
=== persia volunteers for week-in-advance email, but would likely again forget the day-in-advance email.
dholbachpersia: thanks02:20
dholbachnext Universe HUG DAY?02:20
dholbachI'd like us to make an effort to tag bugs and offer mentoring for them02:20
dholbachI get a lot of requests of people who don't know where to start helping out02:20
dholbachwe should make an effort to help newcomers into the team :)02:21
=== BuffaloSoldier [n=firdaus@ubuntu/member/BuffaloSoldier] has joined #ubuntu-meeting
dholbachso what about friday next week?02:21
ajmitchsounds ok02:22
TheMusonext week?02:22
=== TheMuso won't be here.
dholbachwho of you will help out?02:22
=== ajmitch probably can, since it'll be saturday
=== ScottK will be around, but working so can help some.
ajmitchnothing better to do on a friday night :)02:22
dholbachok, if there's no other proposal, let's go with that, I'll announce it02:23
dholbachnext Q&A sessions?02:23
dholbachwas anybody of you there yesterday?02:23
ajmitchnope02:23
dholbachwould it be ok to do them in #ubuntu-motu?02:24
Hobbseei'd suggest that's a good idea02:24
=== TheMuso thinks so
dholbachok02:24
persiaThat seems a better place.02:24
AndyPi think it was forgotten about, and no one turned up in #ubuntu-classroom looking for Q&A... perhaps better advertising next time :)02:24
dholbachshall we do them in thursday two weeks at 0 and 12 utc?02:24
dholbachif you have a blog, please blog about all the events we do02:24
dholbachI'll do that too and announce the Q&A sessions, if we agree on the date and time02:25
dholbachok, I take that as no objections02:25
dholbachmoving on02:25
dholbachnext REVU day?02:25
dholbachas the situation is rather desperate.... what about monday? :-)02:26
=== persia wonders if there is a good definition of expected activities for a REVU day.
TheMusoI'd rather not have it in the next week, as I'd like to help, but won't be around.02:26
dholbachTheMuso: we'll do another revu day the week after that - how about that?02:26
dholbachso best to agree on two dates02:26
TheMusodholbach: I'm easy, but would like to help02:26
dholbachpersia: working through the lists of REVU and ubuntu-{main,universe}-sponsors?02:27
persiaSo two days?  I like Tuesdays or Thursdays.02:27
dholbachTheMuso: cool02:27
dholbachoh, I mean a day each in next week and the one after that02:27
persiadholbach: Ah.  I wonder if there shouldn't be a wiki page or something.02:27
ScottKWed next week is a major holiday in the US.02:27
dholbachpersia: MOTU/Reviewing? :)02:27
dholbachScottK: so you think it'd be a good thing to do it on wednesday?02:28
ScottKdholbach: No.  Stay away from it.02:28
dholbachok02:28
dholbachthe next two mondays then?02:28
ScottKIndependence Day generally has a lot of people outside and away from computers here.02:28
persiadholbach: Cluttered namespace, but I'll add a note on REVU days to https://wiki.ubuntu.com/MOTU/Packages/Reviewing02:29
ScottKMany people travel too, so Monday is good.02:29
dholbachpersia: thanks02:29
dholbachok cool02:29
dholbachI'll make sure to announce it02:29
dholbachand please blog about it, if you can - it's good to stir up some interest in the activities we do, they deserve it :)02:29
=== TheMuso needs to get a blog first.
dholbachI think that's all from our agenda02:29
TheMuso:p02:30
dholbachdo we have anything else?02:30
jhansonxiI have a question about Wine desktop files02:30
=== ScottK thinks congratulations are in order for our two new MOTUs.
dholbachjhansonxi: would it be ok to ask it in #ubuntu-motu?02:30
dholbachScottK: absolutely02:30
ScottKjust a note for the minutes02:30
ScottKSince I don't think either is present.02:31
ajmitchare we up to date with new MOTU applications?02:31
dholbachthanks calc and nixternal for all the work you put into Ubuntu :-)02:31
ScottKActually, congrats nixternal02:31
dholbachajmitch: no, bluekuja and YokoZar and one core-dev application are in the loop02:31
dholbachok, that's that then02:32
dholbachthanks all for coming - have a nice day02:32
TheMusonp02:32
=== ajmitch presumes that they can be approved with 3 or 4 out of 5 giving a response
dholbachajmitch: bluekuja and yokozar don't have any vote02:33
ajmitchok02:33
=== GNUdog_ [n=GNUdog@218.28.13.157] has joined #ubuntu-meeting
=== ajmitch should sleep now anyway
=== GNUdog_ is now known as GNUdog
=== persia wonders if welcome of new MOTUs and status of pending applications should be a regular item.
dholbachwelcoming new MOTUs should be02:34
=== TheMuso [n=luke@ubuntu/member/themuso] has left #ubuntu-meeting []
dholbachI already sent mails to ubuntu-devel@ about it02:34
dholbachbut it'd be nice to welcome them in the meeting also02:34
dholbachfor status of pending applications I'm not sure02:35
dholbachI mean I'm happy to give a statement on it, but I don't know if it helps much02:35
persiaRight.  I withdraw that - it's properly MOTU Council.02:35
ajmitchand we don't have separate MC meetings02:35
persiaajmitch: But you deliberate in other forums, no?02:36
ajmitchonly the mailing list02:36
persiaHmm.  I stand by my withdrawl, but wouldn't oppose another suggesting it.02:37
ajmitchok, meeting over, let's all go home :)02:37
ScottKBye all.02:38
=== ScottK [n=ScottK@ubuntu/member/scottk] has left #ubuntu-meeting ["Konversation]
=== jhansonxi [n=jhansonx@d24.as1.lnng1.mi.core.com] has left #ubuntu-meeting ["Konversation]
=== thekorn [n=thekorn@a89-182-76-198.net-htp.de] has joined #ubuntu-meeting
=== calc [n=ccheney@conr-adsl-209-169-124-200.consolidated.net] has joined #ubuntu-meeting
=== mdz [i=mdz@nat/canonical/x-2123366bc3cab201] has joined #ubuntu-meeting
=== StevenK [n=stevenk@14.5.233.220.exetel.com.au] has left #ubuntu-meeting []
=== geser [i=mb@ubuntu/member/geser] has left #ubuntu-meeting ["Liberate]
=== jsgotangco [n=jsg123@ubuntu/member/jsgotangco] has joined #ubuntu-meeting
=== ash211 [n=andrew@adsl-074-184-018-011.sip.asm.bellsouth.net] has joined #ubuntu-meeting
=== persia [n=persia@ubuntu/member/persia] has left #ubuntu-meeting []
=== dholbach_ [n=daniel@i59F75DB3.versanet.de] has joined #ubuntu-meeting
=== licio [n=licio@ubuntu/member/licio] has joined #ubuntu-meeting
=== ..[topic/#ubuntu-meeting:ubotu] : Calendar: http://fridge.ubuntu.com/event | Logs: https://wiki.ubuntu.com/MeetingLogs/ | 03 Jul 19:00 UTC: Technical Board | 04 Jul 20:00 UTC: Edubuntu | 05 Jul 20:00 UTC: Ubuntu Development Team | 10 Jul 15:00 UTC: Kernel Team | 11 Jul 12:00 UTC: Edubuntu | 12 Jul 15:00 UTC: Ubuntu Development Team
=== fernando [n=fernando@unaffiliated/musb] has joined #ubuntu-meeting
=== juliux [n=juliux@ubuntu/member/juliux] has joined #ubuntu-meeting
=== gnomefreak [n=gnomefre@ubuntu/member/gnomefreak] has joined #ubuntu-meeting
=== DBO [n=DBO@unaffiliated/dbo] has joined #ubuntu-meeting
=== BuffaloSoldier [n=firdaus@ubuntu/member/BuffaloSoldier] has joined #ubuntu-meeting
=== DBO [n=DBO@unaffiliated/dbo] has joined #ubuntu-meeting
=== _MMA_ [n=mma@cpe-071-070-203-016.nc.res.rr.com] has joined #ubuntu-meeting
=== _MMA_ [n=mma@cpe-071-070-203-016.nc.res.rr.com] has left #ubuntu-meeting []
=== j_ack [n=j_ack@p508D848A.dip0.t-ipconnect.de] has joined #ubuntu-meeting
=== asac_ [n=asac@debian/developer/asac] has joined #ubuntu-meeting
=== Zic [n=Zic@Final-Fantasy.FF-IRC.net] has joined #ubuntu-meeting
=== GNUdog [n=GNUdog@218.28.13.157] has joined #ubuntu-meeting
=== finalbeta [n=gggggggg@d54C6865D.access.telenet.be] has joined #ubuntu-meeting
=== sfair [n=sfair@200.145.13.81] has joined #ubuntu-meeting
=== rraphink [i=raphink@ubuntu/member/raphink] has joined #ubuntu-meeting
asac@schedule06:03
ubotuSchedule for Etc/UTC: 03 Jul 19:00: Technical Board | 04 Jul 20:00: Edubuntu | 05 Jul 20:00: Ubuntu Development Team | 10 Jul 15:00: Kernel Team | 11 Jul 12:00: Edubuntu | 12 Jul 15:00: Ubuntu Development Team06:03
=== Zic [n=Zic@Final-Fantasy.FF-IRC.net] has joined #ubuntu-meeting
=== rraphink [i=raphink@ubuntu/member/raphink] has joined #ubuntu-meeting
=== sacater [n=sacater@ubuntu/member/colchester-lug.sacater] has joined #ubuntu-meeting
=== avoine [n=avoine@69.70.0.36] has joined #ubuntu-meeting
=== lbm [n=lbm@0x555373ab.adsl.cybercity.dk] has joined #ubuntu-meeting
=== jean1 [n=jeang@dsl-244-141-212.telkomadsl.co.za] has joined #ubuntu-meeting
=== jean1 [n=jeang@dsl-244-141-212.telkomadsl.co.za] has left #ubuntu-meeting []
=== ipa [n=ipa@163.13.246.206] has joined #ubuntu-meeting
=== juliux [n=juliux@ubuntu/member/juliux] has joined #ubuntu-meeting
=== ompaul [n=ompaul@freenode/staff/gnewsense.ompaul] has joined #ubuntu-meeting
=== j_ack [n=j_ack@p508D848A.dip0.t-ipconnect.de] has joined #ubuntu-meeting
=== cjwatson_ [n=cjwatson@82-69-40-219.dsl.in-addr.zen.co.uk] has joined #ubuntu-meeting
=== doko_ [n=doko@BAEe6ea.bae.pppool.de] has joined #ubuntu-meeting
=== Zic [n=Zic@Final-Fantasy.FF-IRC.net] has joined #ubuntu-meeting
=== thekorn_ [n=thekorn@a89-182-23-30.net-htp.de] has joined #ubuntu-meeting
=== Mez [n=Mez@ubuntu/member/mez] has joined #ubuntu-meeting
=== hoora_ [i=ariel@gateway/tor/x-dcf136413f9656d9] has joined #ubuntu-meeting
=== gpocentek [i=gauvain@sd-10791.dedibox.fr] has joined #ubuntu-meeting
=== bryce [n=bryce@c-67-169-207-235.hsd1.or.comcast.net] has joined #ubuntu-meeting
=== coreymon77 [n=coreymon@unaffiliated/coreymon77] has joined #ubuntu-meeting
=== lbm [n=lbm@0x555373ab.adsl.cybercity.dk] has joined #ubuntu-meeting
=== Mez [n=Mez@ubuntu/member/mez] has joined #ubuntu-meeting
=== hjmf [n=hjmf@150.Red-83-44-175.dynamicIP.rima-tde.net] has joined #ubuntu-meeting
=== gouki_ [n=gouki@ubuntu/member/gouki] has joined #ubuntu-meeting
=== pygi [n=mario@83-131-1-43.adsl.net.t-com.hr] has joined #ubuntu-meeting
=== pygi [n=mario@83-131-1-43.adsl.net.t-com.hr] has joined #ubuntu-meeting
=== lfittl [n=lfittl@2001:6f8:107e:30:216:36ff:fe17:3cef] has joined #ubuntu-meeting
=== hjmf [n=hjmf@150.Red-83-44-175.dynamicIP.rima-tde.net] has joined #ubuntu-meeting
=== tkjacobsen [n=tkjacobs@h59ec0f85.c45-01-03.dyn.perspektivbredband.net] has joined #ubuntu-meeting
=== ogra [n=ogra@ubuntu/member/ogra] has joined #ubuntu-meeting
=== ToonArmy [n=chris@88-105-205-46.dynamic.dsl.as9105.com] has joined #ubuntu-meeting
=== gnomefreak [n=gnomefre@ubuntu/member/gnomefreak] has joined #ubuntu-meeting

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