/srv/irclogs.ubuntu.com/2007/03/16/#ubuntu-meeting.txt

=== yharrow [n=sysadmin@h-68-164-34-22.nycmny83.dynamic.covad.net] has joined #ubuntu-meeting
=== licio [n=licio@ubuntu/member/licio] has joined #ubuntu-meeting
=== Czessi [n=Czessi@dslb-088-073-021-021.pools.arcor-ip.net] has joined #ubuntu-meeting
=== ogra_ [n=ogra@p548AEDA3.dip.t-dialin.net] has joined #ubuntu-meeting
=== _czessi [n=Czessi@dslb-088-073-038-187.pools.arcor-ip.net] has joined #ubuntu-meeting
=== _czessi [n=Czessi@dslb-088-073-047-067.pools.arcor-ip.net] has joined #ubuntu-meeting
=== mc44 [n=mc44@unaffiliated/mc44] has left #ubuntu-meeting ["Exit,]
=== mdz [n=mdz@cpe-76-173-8-128.socal.res.rr.com] has joined #ubuntu-meeting
=== czessi_ [n=Czessi@dslb-088-073-020-142.pools.arcor-ip.net] has joined #ubuntu-meeting
=== ogra_ [n=ogra@p548AD448.dip.t-dialin.net] has joined #ubuntu-meeting
=== Mez [n=Mez@ubuntu/member/mez] has joined #ubuntu-meeting
=== j_ack [n=rudi@p508DB79B.dip0.t-ipconnect.de] has joined #ubuntu-meeting
=== freeflying_ [i=root@gobstopper.dreamhost.com] has joined #ubuntu-meeting
=== jsgotangco [n=jsg123@ubuntu/member/jsgotangco] has joined #ubuntu-meeting
=== firephoto [n=tom@pool-71-115-214-25.spknwa.dsl-w.verizon.net] has joined #ubuntu-meeting
=== Burgwork [n=corey@S010600502c03205f.gv.shawcable.net] has joined #ubuntu-meeting
=== Burgundavia [n=corey@S010600502c03205f.gv.shawcable.net] has joined #ubuntu-meeting
=== beuno [n=martin@200.127.67.148] has joined #ubuntu-meeting
=== Burgundavia [n=corey@S010600502c03205f.gv.shawcable.net] has joined #ubuntu-meeting
=== slomo__ [n=slomo@pD954775A.dip0.t-ipconnect.de] has joined #ubuntu-meeting
=== mruiz [n=mruiz@ubuntu/member/mruiz] has joined #ubuntu-meeting
=== mruiz [n=mruiz@ubuntu/member/mruiz] has left #ubuntu-meeting ["Bye!"]
=== effie_jayx [n=valles@190.37.175.250] has joined #ubuntu-meeting
=== licio [n=licio@ubuntu/member/licio] has joined #ubuntu-meeting
=== gouki_ [n=gouki@bl4-198-120.dsl.telepac.pt] has joined #ubuntu-meeting
=== fernando_ [n=fernando@189.0.128.78] has joined #ubuntu-meeting
=== robitaille [n=daniel@ubuntu/member/robitaille] has joined #ubuntu-meeting
=== besonen_mobile [n=besonen_@71-220-225-182.eugn.qwest.net] has joined #ubuntu-meeting
=== rtg [n=rtg@rtg.theglobal.net] has joined #ubuntu-meeting
=== fernando [n=fernando@unaffiliated/musb] has joined #ubuntu-meeting
=== iGraphite [n=iGraphit@203-206-254-33.dyn.iinet.net.au] has joined #ubuntu-meeting
=== iGraphite [n=iGraphit@203-206-254-33.dyn.iinet.net.au] has left #ubuntu-meeting []
=== j_ack [n=rudi@p508DB79B.dip0.t-ipconnect.de] has joined #ubuntu-meeting
=== asac [n=asac@debian/developer/asac] has joined #ubuntu-meeting
=== gnomefreak [n=gnomefre@ubuntu/member/gnomefreak] has joined #ubuntu-meeting
=== Hobbsee [n=Hobbsee@ubuntu/member/hobbsee] has joined #ubuntu-meeting
Hobbsee@schedule sydney07:24
UbugtuSchedule for Australia/Sydney: 16 Mar 21:00: MOTU Council | 18 Mar 02:00: Xubuntu | 20 Mar 02:00: Kernel Team | 20 Mar 10:00: IRC Operators | 21 Mar 05:00: Community Council | 21 Mar 23:00: Edubuntu07:24
ajmitchHobbsee: going to join the MC meeting?07:33
Hobbseeajmitch: hrm...i could do that07:33
Hobbseeargh!  the library closes early tonight!07:34
ajmitchthat's silly07:34
Hobbseeyes.07:34
ajmitcheveryone knows that the library is the most favoured place to be on a friday night07:34
=== Hobbsee grins
Hobbseeof course!07:34
=== gnomefreak [n=gnomefre@ubuntu/member/gnomefreak] has joined #ubuntu-meeting
=== freeflying [i=root@ubuntu/member/freeflying] has joined #ubuntu-meeting
imbrandon@schedule us/chicago07:54
imbrandon@schedule us\chicago07:54
imbrandon@schedule chicago07:54
imbrandon@schedule07:54
UbugtuSchedule for America/Chicago: 16 Mar 05:00: MOTU Council | 17 Mar 10:00: Xubuntu | 19 Mar 10:00: Kernel Team | 19 Mar 18:00: IRC Operators | 20 Mar 13:00: Community Council | 21 Mar 07:00: Edubuntu07:54
UbugtuSchedule for Etc/UTC: 16 Mar 10:00: MOTU Council | 17 Mar 15:00: Xubuntu | 19 Mar 15:00: Kernel Team | 19 Mar 23:00: IRC Operators | 20 Mar 18:00: Community Council | 21 Mar 12:00: Edubuntu07:54
=== Hobbsee [n=Hobbsee@ubuntu/member/hobbsee] has joined #ubuntu-meeting
=== Lure [n=lure@external-7.hermes.si] has joined #ubuntu-meeting
=== Sp4rKy [n=Sp4rKy@ubuntu/member/sp4rky] has joined #ubuntu-meeting
=== arualavi [n=Iva@67.Red-83-33-5.dynamicIP.rima-tde.net] has joined #ubuntu-meeting
=== arualavi [n=Iva@67.Red-83-33-5.dynamicIP.rima-tde.net] has joined #ubuntu-meeting
=== sky_walkie [n=hrdlo@193.85.244.121] has joined #ubuntu-meeting
=== zenrox [i=zenrox@pool-71-115-197-231.spknwa.dsl-w.verizon.net] has joined #ubuntu-meeting
=== dholbach [n=daniel@i59F70BDC.versanet.de] has joined #ubuntu-meeting
=== mvo [n=egon@p54A67F5B.dip.t-dialin.net] has joined #ubuntu-meeting
=== hjmf [n=hjmf@140.Red-217-125-227.dynamicIP.rima-tde.net] has joined #ubuntu-meeting
=== BackwardsDown [n=niels@5351BB29.cable.casema.nl] has joined #ubuntu-meeting
=== jsgotangco [n=jsg123@ubuntu/member/jsgotangco] has joined #ubuntu-meeting
=== asac [n=asac@debian/developer/asac] has joined #ubuntu-meeting
=== finalbeta [n=finalbet@d54C689F7.access.telenet.be] has joined #ubuntu-meeting
=== pochu [n=pochu@ubuntu/member/pochu] has joined #ubuntu-meeting
=== gpocentek [n=gauvain@ubuntu/member/gloubiboulga] has joined #ubuntu-meeting
=== dennda [n=dennda@ubuntu/member/dennda] has joined #ubuntu-meeting
=== Lure [n=lure@external-7.hermes.si] has joined #ubuntu-meeting
=== firephoto [n=tom@pool-71-120-244-121.spknwa.dsl-w.verizon.net] has joined #ubuntu-meeting
=== ogra [n=ogra@ubuntu/member/ogra] has joined #ubuntu-meeting
=== lmanul [n=manu@194.230.53.149] has joined #ubuntu-meeting
=== sistpoty [n=sistpoty@ubuntu/member/sistpoty] has joined #ubuntu-meeting
=== finalbeta [n=finalbet@d54C689F7.access.telenet.be] has joined #ubuntu-meeting
=== ajmitch pokes Ubugtu
dholbach. o O { The bell tolls 11 times in Berlin... }11:00
=== TheMuso [n=luke@ubuntu/member/themuso] has joined #ubuntu-meeting
sistpotyhi everyone11:01
dholbachdoes that mean we start without the smokers? :)11:01
ajmitchhehe11:01
dholbachLet's start off then11:02
sistpotyI can live suppress my addiction for some time :P11:02
sistpotys/live//11:02
dholbachI added a comment on "Need some advise about becoming MOTU of the claws-mail program! (?TuxCrafter)"11:02
dholbachbecause I think we can deal with this pretty easily11:02
=== TheMuso vaguely remembers seeing that,
dholbachdo we have anybody who'd like to be mentor for TuxCrafter and help him with getting things done?11:02
sistpotyTuxCrafter around?11:02
TheMusoActually, I do remember seeing that.11:03
gpocentekdholbach: I'll take care of this11:03
dholbachhttps://wiki.ubuntu.com/MOTU/Council/Meetings is the agenda for everybody who's around11:03
=== ajmitch reloads the agenda
dholbachgpocentek: thank you very much11:03
gpocentekit's Xubuntu related, so...11:03
sistpotyyay, thanks11:03
dholbachsistpoty and siretart wanted to discuss RFP bugs11:03
sistpotywell, the Candidates page is a little bit messy imo, could we use lp bugs for it?11:04
sistpotys.th. like file against ubuntu, tag with RFP?11:04
dholbachsounds good to me11:04
TheMusowhT is rfp?11:04
gpocentekI like the idea11:04
dholbachTheMuso: request for package11:04
TheMusoOh.11:04
=== TheMuso practically never looks at that page. :)
sistpoty(that way we could also link to debian rfps/itps)11:04
dholbachonce assigned, we could regularly ping the assignee and track how it's going11:05
ajmitchtalk to laserjock about that please11:05
dholbachok, I'm going to announce the 'rfp' tag and the idea in general and link it from the bugs page11:05
sistpotyajmitch: yep, good idea11:05
ajmitchhe's been talking with the LP guys about what would best be used there11:05
=== imbrandon returns
dholbachneat-o :)11:05
dholbachmove on?11:05
ajmitchin his role as LP contact :)11:05
ajmitchah, the charter11:06
imbrandonajmitch, rfp/itp ?11:06
sistpotyok, I'll contact laserjock, and see what he's for us... ok?11:06
dholbachimbrandon: both - once it's turned into an itp, the bug would just have an assignee11:06
sistpotyhe has even11:06
siretartdholbach: re: 'rfp' idea: this also means that the 'Candidates' Page gets removed from the wiki, right?11:06
imbrandondholbach, great11:06
dholbachI'm happy to write some documentation on it11:06
dholbachsiretart: after a short while, I wouldn't want it to be just purged11:07
dholbach... just purged like that11:07
imbrandonsiretart, well not removed, but turned more into an explination of how to file a rfp on LP ;)11:07
siretartdholbach: d'accord11:07
dholbachalso, we'd need to update Bugs/Responses11:07
siretartimbrandon: jupp11:07
dholbachI'll take care of that11:07
dholbachok, moving on to the charter11:08
sistpotymaybe we could move to the last point... might make sense to have crimsun around for charter?11:08
dholbachok11:08
sistpotythis is really just a silly question from my side, as I get bounces quite often... can we do s.th. and what?11:08
dholbachregarding ml bounces, I deactivated sending mail to doomrunner and mailed him about it (found a different address in LP)11:08
dholbachusually that's only for people whose mail account is full, etc11:09
sistpotyok, great :)11:09
dholbachso after a few bounces you can take action on it11:09
=== ajmitch doesn't moderate often because the mailman folder is low down in the mutt config :)
dholbachit's manual, but easy to deal with11:09
dholbachajmitch: pffffft :)11:09
=== lmanul_ [n=manu@194.230.53.149] has joined #ubuntu-meeting
sistpotyok... I guess I'll look at the mailman thingy a little bit more in detail :)11:09
ajmitchtoo easy to forget about the mail piling up...11:09
dholbachsistpoty: in the membership page, just click the 'nomail' thingie for that person and you're set11:10
sistpotyah... cool. thx11:10
dholbachok, let's move on to KDE4 and the charter11:11
sistpotyok11:11
dholbachi personally feel that they both describe problems with "where does the MC stand"11:11
dholbach... in the MOTU world11:11
sistpotyyep11:11
dholbachyou might have read my latest response to the kde4 thread and I think we should have been quicker about escalaiting this to the TB11:12
dholbachas the TB can do an ultimate decision and they approved the kde4 spec11:12
dholbachRiddell: are you there?11:12
imbrandonwell not exactly, this should be treated just as any other UVFe request, only in that instead of one person asking for the UVFe you have a group11:12
Riddellabend11:12
dholbachimbrandon: what do you mean by "not exactly"?11:13
dholbachRiddell: :-)11:13
sistpotyhehe, just wanted to write that I also think we need some kind of escalation path, in case such problems occur later11:13
imbrandonin either case MC shouldent have a say in what is or isnt in the universe imho, only if to grant a uvfe or not11:13
ajmitchthough motu-uvf gets its policy set by MC, etc11:13
ajmitch3 of the team overlap with the MC anyway :)11:14
imbrandonright11:14
dholbachwhat do you all think about moving the thread to ubuntu-devel and CC the TB?11:14
imbrandonwell my big thing here is why is this set of packages gettign diffrent treatment than any other set of packages asking for a UVFe ?11:14
dholbachI think that will resolve the issue quickly and we can all move on11:14
dholbachimbrandon: why a different treatment?11:14
dholbachimbrandon: it was asked for a general exception for it11:15
ajmitchwe have't given out any general exceptions for a set of packages11:15
imbrandonwell all this "todo" about it , i mean it boils down to if you need more information to grant or deny the uvfe then ask, if not move on11:15
imbrandonwhy all the TB etc11:15
ajmitchbecause this was initially presented as "we're doing this, unless the MC overrides"11:15
ajmitchconfusion as to what team does what, etc11:16
dholbachuntil now there was no decision yet, but people voiced their concerns/approval on a general exception11:16
imbrandonright, i'm not saying it was presented in the best way, but alot of things arent, just like any bug, there is a "more info" choice11:16
imbrandon;)11:16
ajmitchfor every other package, it's being done on a package-by-package basis, for each version11:16
ajmitchrather than a blanket exception for new packages & new versions11:16
sistpotyactually I'm not too happy to continue this thread... it imo caused enough harm already. and since we've been unable to come to a decision (I guess that's kinda our fault) I'd say that means we didn't object11:17
ajmitchso there's no precedent, hence the slow decision11:17
=== ajmitch would think that the best way to get them useful is to stick them in universe & aggressively update in feisty-backports
imbrandonagrees with ajmitch11:18
dholbachto resolve the issue quickly, I'd suggest to contact the TB to get a final ACK and briefly mention the pros and cons that were pointed out, so we can move on11:18
imbrandonand voiced or not i know that is the intentions of those of us that work on them11:18
sistpotydholbach: ok, with me11:19
imbrandondholbach, see thats just it, can the MC not grant a UVFe? why ........ never mind, i guess only the "easy" decisions are ...... /me shushes11:19
dholbachimbrandon: can you elaborate?11:19
imbrandonnot without being so frank that i'm affraid to offend someone11:19
dholbachmove on, that's what we're all here for11:20
ajmitchgo ahead anyway11:20
sistpotyimbrandon: better break toes know than kill persons later ;)11:20
dholbachI'm sure we can make a rational decision and learn from the situation11:20
dholbachRiddell: I guess you're quite busy atm, but what is your view on this?11:20
imbrandonok, then imho MC should stepup and say yes or no, dont fall back to TB because its a hard decesion, if the awnser is no then we have to deal with it, if you need more info , then ask11:20
ajmitchimbrandon: that's hardly offensive :)11:21
imbrandonbut falling to the TB i feel is a step back for the MC11:21
imbrandonnot just this situation11:21
Riddellmy view is the same as that of the kubuntu council, the packages should go in.  there's no point in having development packages any older than we have to and they have already solved some significant problems upstream by having them11:21
ajmitchthe reason for falling back to the TB, so to speak, is to get a clear understanding of where our reponsibilities extend to11:21
ajmitchie whether other teams would need to go through the policies set by the MC for anything in universe11:22
ajmitchin this case it was a preapproved spec that we'd be blocking if we didn't let it in11:22
imbrandonajmitch, right, and as i said, the KC is asking for a UVFe , not telling since the spec went over time11:22
imbrandonbut imho its justified11:23
sistpotyand falling back to TB is sane if we end up with conflicting interests from teams11:23
ajmitchimbrandon: right, but this is a different UVFe, up until release day :)11:23
sistpoty(since I guess we also need a clear escalation path)11:23
imbrandonok11:23
dholbachI agree with sistpoty - it'd be nice to hear what gpocentek and crimsun have to say11:23
dholbach(crimsun might be a bit late)11:24
gpocentekwell...11:24
ajmitchhopefully crimsun gets to the office (without a speeding ticket)11:24
sistpotyhehe11:24
gpocentekI'd be happy to see KDE4 in universe, but not really happy to see that it won't be maintained11:24
gpocentekand I really understand why the Kubuntu wants it11:24
imbrandonit will be maintained, through feisty-backports11:24
TheMusoc/11:25
TheMusogah11:25
Riddellwhy does Kubuntu want to help the development of the next version of our desktop?11:25
Riddellseems pretty obvious to me11:25
dholbachdo apps in -backports build against libs in -backports?11:25
ajmitchgpocentek: do you feel happy with letting the kubuntu guys do what they will with the KDE4 stuff in feisty, given that there's already some of it there?11:25
imbrandoni'm both on the KDE team and -backports and will personaly see that it is backported in a timely manner11:25
imbrandondholbach, yes11:25
dholbachgood to know11:25
sistpotyimbrandon: that's great to hear11:26
gpocentekajmitch: I'm sure they won't do "what they want"11:26
crimsun(present, sorry for tardiness)11:26
gpocentekRiddell: "I really understand"11:26
sistpotywb crimsun11:27
ajmitchgpocentek: that's what's being asked for - permission for new packages (kde4 apps), and updating the snapshots until release time11:27
Riddellgpocentek: ooh, oops, my bad11:27
ajmitchcrimsun: welcome11:27
imbrandonwb crimsun11:27
gpocentekwe've gone with svn snapshot of Xfce until the last dapper development's day11:28
=== jsgotangco [n=jsg123@ubuntu/member/jsgotangco] has joined #ubuntu-meeting
ajmitchthat was pre-4.2?11:28
dholbachshall we do a tentative vote and see where we stand? how would the result look in +1, +0,5, 0, -0,5 and -1 votes?11:29
ajmitchdholbach: you forgot complex numbers11:29
imbrandonyou might also note too that feisty+1 will likely see a stable release of kde4 , this will GREATLY help the next version stableize11:29
imbrandonas we are pretty much one of the top KDE4 development platforms for upstream KDE11:30
sistpotydholbach: sure11:30
=== ajmitch puts in a +1
ajmitchimbrandon: that's interesting11:30
ajmitchI didn't realise kubuntu was so popular now in the developer community11:30
imbrandonin the kde developer community it is , 50/50 kubuntu/suse11:31
ajmitchit used to be a lot of mandrake, back in the day :)11:31
imbrandon:)11:31
dholbachI'd vote with: +0,5 as I think that it's vaiuable and somewhat taken care of (through backports - bear in mind that not all people have activated them), but I'm not convinced that there will be enough manpower to feed those bugs upstream, to be really useful - also I think it's not good to have old delveopment snapshots11:31
sistpoty+1... because imbrandon will take care for backports (which was my main opposition), and because UVF-team seemed happy with it (at least from my memory of the thread)11:31
gpocentek(sorry, boken connection)11:31
crimsunRE: KDE 4 snaps in feisty, precedence definitely has been set with Xfce for the past two stable releases in _main_. I've also already mailed about my feeling that the Kubuntu community wants these snapshots, and because they exist already in edgy, we really have no reason to not have such in feisty. Ultimately, however, I honestly don't feel the MC has the "powah" here to say yay or nay.11:33
dholbachgpocentek: we were just conducting a tentative vote to see where we stand -- we're at +2,5 at the moment :)11:33
ajmitchcrimsun: right, the kubuntu guys seem happy for now if MC approves it :)11:33
dholbachcrimsun: I tend to agree with your last point and we should discuss that in the next agenda point, when it comes to the charter.11:34
gpocentekdholbach: thanks11:34
gpocentek+1 from if the backports are available11:34
crimsunI'm happy to say +1 for it based not on "geez, enough already" but on precedence.11:34
dholbachimbrandon: (and I guess that's why we ultimately lagged behind on making a decision)11:34
imbrandon:)11:34
gpocentek(My fear what to see a development snapshot quite unusable and not updated in the repos)11:35
dholbachOk, shall we move on, announce the outcome? Any conditions?11:35
dholbachI don't think we need further discussion now.11:35
ajmitchimbrandon: see, that was mostly painless ;)11:35
imbrandonhehe yes11:35
ajmitchno throwing chairs involved11:36
imbrandoni just dident wanna step on toes but knew you all could pull it off11:36
ajmitchpart of the problem is what we'll discuss now11:36
ajmitchwhat responsibilities MC has11:36
sistpotyyep11:36
dholbachwhat do you all think about having a weekly update on ubuntu-motu@ about how kde4 goes? what has been updated, what blockers are currently seen, etc?11:37
crimsun(apparently I've traded one unstable connection for another, great. I'll lag momentarily.)11:37
imbrandonok just to be clear , we have a UVFe for KDE4 snapshots / programs ?11:37
dholbachI think that'd be only fair to know what's going on and where we might want to step in if things break to awfully11:37
ajmitchimbrandon: aiui, yes, since we know there's a defined set of programs there you'll be putting in11:37
imbrandondholbach, sure, and i'll be happy to be the "contact" for that if you wish , between the MC and the KDE team11:37
ajmitchthanks11:37
dholbachimbrandon: thanks a lot11:38
dholbachwe'll announce it like that and inform the TB about the decision11:38
sistpotyyay, thanks11:38
dholbachmoving on11:38
dholbachwhat lessons can we learn from this? shall we do a quick brainstorming on that?11:38
=== j_ack [n=rudi@p508D85DE.dip0.t-ipconnect.de] has joined #ubuntu-meeting
dholbachi'd like to hear imbrandon and Riddell on that, because their input is quite valuable as "other teams who deal with the MC"11:39
ajmitchwe need to move faster on making a decision11:39
ajmitchwhile keeping everyone involved11:39
dholbach * need clearer guidelines on what needs a MC decision and what not11:39
sistpotyajmitch++11:40
dholbach * don't start voting too early11:40
sistpoty(sorry for that)11:40
dholbachno problem - I'm very happy we're learning that fast11:40
ajmitchsome MOTUs feel like they're cut out now11:40
imbrandonwell on this feasico i have only 2 things i would have changed, imho , 1) the initial email might not have been in the form of a question but i would have requested that it was, or treated it as such ( e.g. asked for more info to grant/deny the UVFe ) and 2) ....11:40
crimsunI think ultimately we need to be careful to not appear to decide _for_ MOTU as a whole but simply decide who becomes MOTU.11:41
ajmitchcrimsun: right, that's a matter of whether we should be making these decisions or not, no?11:41
crimsunIt can be confusing as quite a few of us (MC) straddle teams.11:42
crimsunajmitch: right11:42
imbrandontream other teams that come into your "domain" as any other person, it shouldent have been any diffrent that KC was asking or joe blow11:42
imbrandonyea11:42
sistpotycrimsun: that will leave the following problems: who could do this decisions then? how could decision be done in a timely matter?11:42
dholbachI agree with crimsun there - the MC was envisioned as somebody being responsible for decisions, not making them as a clique - up until now we didn't do that many decisions and they've always been backed up by lots of MOTUs11:42
dholbachimbrandon: how do you feel were you treated differently than joe blow?11:43
ajmitcheven for the SRU policy vote, which was done in a MOTU meeting, some MOTUs felt like their votes wouldn't count11:43
dholbachwe should point that out in the charter11:43
sistpotydefinitely11:43
imbrandoni dont think it was really, but i was just saying, you were worried weather it was KC saying yes or MC saying yes, it should have been turned arround right away in the MC's head that someone was asking for a UVFe , not someone was demanding one11:44
crimsunIn the future, we should move quickly to delegate to the appropriate team. It's kinda unfortunate at the present overlap, but that will change in the next release. In this instance, IMO MC should have said "oh, this is motu-uvf material, *handoff*".11:44
dholbachimbrandon: I personally don't feel that it was a KC vs MC decision. I feel that the problems at hand were discussed quite rationally11:44
imbrandone.g. if i came to the MC and said "i've decided i am granting a uvfe for apt-mirror because i maintain it" you would naturaly turn and ask "why" and explain the situation, not debate weatyher i had the "powa" todoso11:45
ajmitchimbrandon: I think there was confusion about whether the MC would have authority to say no11:45
imbrandondholbach, i 100% agree11:45
dholbachimbrandon: ok good :)11:45
imbrandonhere they were , i mean leading upto here11:45
imbrandonjust was an observation11:45
imbrandonnot a ohh no, kinda thing11:45
dholbach:)11:45
ajmitch:)11:45
crimsunpersonally there seemed to be a lot of "gut reaction" mixed with rational argument11:46
=== ajmitch is becoming too much like dholbach, scary
dholbachI propose to point out in the Charter that the MC is responsible for decisions and that anybody can track them down for deciding in a certain way, but that they're not making the decision - merely making sure that a decision is reached (if there's a dispute)11:46
ajmitchso we should try & keep as many decisions in the MOTU list & meeting as possible11:47
dholbachthat way people won't feel there's a clique who decides over them and blocks them - does that make sense?11:47
ajmitchat what point would the MC step in & make a decision?11:47
imbrandonright, the MOTU's as a whole11:47
crimsunI concur there (to both Daniel and Andrew)11:47
gpocentekdholbach: it does make sens11:47
ajmitcheg we debated the kde stuff for a week or so11:48
sistpotyhm... I'm not quite sure if it works out... since motu meeting (the only instance we came to decisions before MC) are scheduled only every 3 weeks11:48
imbrandonwe can step those up if needed11:48
crimsunwe should always be able to meet more frequently as necessary and certainly in urgent cases11:49
imbrandonbut i dont see a whole lot of decisions needeing to be made imho11:49
dholbachshould we make it a MOTU meeting every 1,5 weeks and just make sure that there's a MC quorum if things really get out of hand?11:49
ajmitchmaking everything too democratic can slow things down a bit - see how GRs work in debian :)11:49
dholbachand drop MC meetings11:49
dholbachand tag agenda points as (POLICY) or something11:49
sistpotyno... imo we should make more clear when MC will step in/what's the place of mc11:49
=== ajmitch doesn't think that every decision needs to be put before all the MOTUs
dholbachajmitch: what do you mean by that?11:50
ajmitchretaining the ability to make minor decisions quickly is important11:50
imbrandonsistpoty, +1 , i only think the MC should step in where the MOTU's cant decide amongst themselfs , even on policy11:50
dholbachI think it's good to have a MC quorum around, so it has the "sign off" effect and can inform the TB as the MC is supposed to11:51
dholbachI'm not sure we need different meetings for that11:51
ajmitchin debian the DPL can make a number of decisions, delegations etc11:51
dholbachand I think that future agendas will be quite short11:51
ajmitchbut everyone can still vote by way of GRs11:51
imbrandonok let me pint this out, the MOTU made decisions before and when a decision couldent be reached it was taken to the TB , the MC is only taking the TB spot in this senerio , not the whole of the MOTU11:52
dholbachajmitch: what do you propose?11:52
sistpotywell, I see it like that: MC should step in exactly where's need. if s.th. is working out already, it should not interfere. This would then mean that Motu meeting can do decisions on its own11:52
ajmitchsistpoty: agreed11:52
sistpotyif these are dumb... or if a decision needs to be done very quick, MC can jump in11:52
dholbachdo you think we need two "different" meetings?11:52
ajmitchdholbach: I mean things like team delegations can take awhile if it's put to nominations, everyone voting, etc11:52
imbrandondholbach, no imho11:53
crimsunOTOH, we need to be careful to not "cut off" any MOTU, so we're walking a thin line here.11:53
dholbachcrimsun: can you explain?11:54
ajmitchjumping into a decision too quickly, not getting input from others11:54
dholbachright11:54
=== ajmitch would hope that more MOTUs could attend the MC meetings
crimsunas Andrew stated11:54
ajmitchunless we want to scrap them & have more MOTU meetings11:54
imbrandoni think only one meeting is nessesary but  a quorum of MC members is needed at any MOTU meeting incase decision pop up11:55
ajmitchwe do need to talk about some MC-specific things, like how we're going with the new MOTU applications :)11:55
dholbachI propose: having motu meetings every two weeks, everybody can vote (also on mailing lists if that's appropriate) and if there are policy decisions together with a MC quorum we can present it to the TB11:56
=== mc44 [n=mc44@unaffiliated/mc44] has joined #ubuntu-meeting
ajmitchdholbach: sounds good11:56
=== fernando [n=fernando@unaffiliated/musb] has joined #ubuntu-meeting
TheMusoAlthough not MC, I like the sound of that.11:56
gpocentek /me agrees with dholbach11:56
ajmitchwe'll need to rotate the meeting times a bit11:56
ajmitch3 of the MC members are (nominally) in european timezones :)11:57
crimsundholbach: as a way of removing MC meetings altogether?11:57
fernandomoin all11:57
dholbachcrimsun: yes, because my impression is that the topics are roughly the same in those meetings anyway11:57
dholbach"the same"11:57
sistpotywell, I still don't see the need why we would need MC quorum. Imo this sounds to me like taking away decisions from motu.11:58
ajmitchgets more input into MC stuff from the rest of the MOTU crowd11:58
dholbachsistpoty: only in the decisions we present to the TB - like BIG changes11:58
crimsunsistpoty: right, I agree there. In MOTU meetings we are not MC but simply MOTU, IMO.11:58
sistpotycrimsun: exactly11:59
ajmitchso in the case that all of the MC members vote one way, while the rest of the MOTUs vote another way..?11:59
crimsun(not that one can "simply" be MOTU, but ... semantics)11:59
ajmitchmajority rules, right?11:59
dholbachcan we agree that there are certain decisions that need "signing off" or need somebody who's "responsible"?11:59
sistpotyajmitch: yep11:59
crimsunajmitch: right, we should still be accountable to our body, so to speak11:59
ajmitchsistpoty: ok, just wanted to make that clear :)11:59
sistpotydholbach: no12:00
=== jenda [n=jenda@ubuntu/member/jenda] has joined #ubuntu-meeting
dholbachok, maybe I meant being "accountable to our body" :)12:00
sistpotydholbach: I'd formulate it the other way round... if big decisions are really getting to be hosed, MC should *then* intervine, but not generally be needed if things work out12:00
sistpotywas that english?12:01
crimsundholbach: the one that I can think of immediately is deciding who becomes MOTU. Beyond that, I really don't see our entity "intruding."12:01
dholbachwhen do you think there needs to be a MC quorum?12:01
imbrandonsistpoty, +512:01
imbrandoncrimsun, +2512:01
dholbachok, that makes sense and is fine with me12:01
dholbachwe're getting quite good at formulating it the right way :)12:02
sistpotyhehe12:02
ajmitchok, do you think the TB will agree?12:02
ajmitchor is the TB expecting the MC to make decisions?12:02
dholbachcan somebody try to sum up the proposal?12:03
crimsunAFAIK the TB has only delegated to MC the approval of new MOTU12:03
imbrandonfrom what i recall in UDS , the TB is only expecting the laod to be off them generaly, so if we wouldent have taken it to the TB before then the MC shouldent be there12:03
imbrandone.g. only new members12:03
imbrandonor "hard decisions that the motus cant agree on after much much debate"12:04
imbrandonthats it12:04
sistpotydholbach: I can try to do it12:04
dholbachok12:04
imbrandonie kinda what i was getting at a while ago that the KDE4 thing was a motu-uvf decision not a MC one12:05
imbrandonjust as an example12:05
ajmitchproposal: that all MOTUs vote on issues, the MC members having the same status as any other MOTU, with meetings being held every two weeks, replacing the 3 weekly cycle of MOTU/MC meetings12:05
ajmitchand that if decisions are not being reached, then the MC steps in & makes a decision where needed12:05
ajmitchwhat did I miss from that? :)12:05
=== Tonio_ [n=tonio@205.207.103-84.rev.gaoland.net] has joined #ubuntu-meeting
imbrandonajmitch, looks like you have it imho12:06
sistpotyyep12:06
crimsunI would amend the last bit to be "if decisions are not being reached in a timely fashion" where timely fashion is clearly stated12:06
dholbachto me it sounds quite accurate12:06
ajmitchdays? 1 week?12:07
ajmitchor within the context of an irc meeting?12:07
imbrandonor s/timely fassion/MOTU's bring it to the MC/12:07
dholbachthat always depends on all the facts being on the table12:07
imbrandon?12:07
sistpotyimbrandon: sounds sane12:07
crimsunwe probably need to relax it a bit over our own 48 hrs12:08
crimsunand since we don't well know that all facts have been presented...12:08
dholbachyeah12:08
crimsun1 week would seem to drag. Does 3 days (72 hours) sound like a reasonable compromise?12:08
imbrandonthat and some MOTU's arent on for days at a time, even though they may be active12:08
sistpotycrimsun: 3 days is fine with me12:08
gpocentek(sorry guys, I have to leave)12:09
crimsunsee ya gauvain12:09
sistpotycya gpocentek12:09
ajmitchbye gpocentek, thanks for helping out12:09
dholbachbye gpocentek12:09
imbrandonif we can wait 7 days for a package in -proposed , i think we can wait 7 days for MOTU input on a topic ( givein that both are in place for the same reason, to give everyone a chance to givce input )12:09
dholbachok, let's add something like "the MC has been called for a vote and a clear proposal has been made"12:10
sistpotyI thought you mean about MC decisions now?12:10
dholbachthat will make it a lot easier12:10
sistpotydholbach++12:10
imbrandondholbach ++12:10
crimsunyes, the distinction is necessary, and I concur12:11
dholbachok, let's add that to the charter12:11
dholbachI'm quite happy with how quickly we resolved that and that we could all agree on it12:11
imbrandonok guys i know i'm non-MC but i must run ( just FYI ) back in ~45 minutes12:11
dholbachfeel all patted on the back :)12:12
sistpotyhm... I'm not sure if it works out... sorry. let's try to replay the kde4 question how it would have ideally happened with the new charter, shall we?12:12
imbrandonsistpoty, motu-uvf would ahve decided and MC would have never been involved, with this charter12:12
crimsunsistpoty: we probably would have called for a vote right about the 1-wk mark12:12
sistpotycrimsun: so that would have been 2 days ago12:13
dholbachin an ideal world uploads wouldn't just have happened12:13
dholbachbut that we don't have control over12:13
sistpotyhm... actually I'm not quite sure who would have made what decision with the current proposal. is anyone else feeling this way?12:14
sistpotybecause I think we should try to make that clear12:15
crimsunsistpoty: KDE 4 should have been a motu-uvf decision12:15
ajmitchwith the current proposal, it would have been up to motu-uvf - but there's nothing about how long a team like -uvf could take to make a decision12:15
dholbachI think we all became more concious of whose responsibility what is - nobody would expect a certain team to do a decision and maybe things wouldn't be in limbo12:16
sistpotyok... so Riddell would have asked, MC would have stayed quiet and motu-uvf have come up with a decision?12:16
sistpotyand in case there weren't a reaction from motu-uvf, MC would ping them, right?12:16
ajmitchyep12:17
dholbachthat sounds good to me12:17
crimsunyes12:17
ajmitchthat would also cover things like that xgl update12:17
sistpotyand if this still won't lead to a decision in a timely manner, MC steps in and makes one. agreed?12:17
crimsunthat sounds sane12:17
ajmitchgreat12:17
sistpotyok, I guess I understand the notion of it now :)12:18
ajmitchok, for other timely decisions - we have 2 weeks to make decisions on new MOTUs12:18
ajmitchI think Lutin's application is almost 2 weeks old12:18
sistpotygood point12:19
ajmitchis the timely decision thing in the charter for that?12:19
sistpotynot yet I believe...12:19
ajmitchsince we should really call for votes in the last 2 days or so if it stretches out that long12:19
dholbachwhat do you think about not letting such mails unanswered for more 24h? so one of us will either a) ask a question or b) step to do a vote12:20
crimsunI think I'm going in invoke (to myself) the sabdfl's sentiment here regarding MOTU approval (back when TB was still approving MOTU), and that is we should give applicants the benefit of the doubt.12:20
sistpotynot quite sure actually... I didn't make up my mind on one day but also didn't have an idea on the same day what to ask12:21
=== ajmitch usually doesn't have bright ideas of what to ask & reads the conversation
sistpotybut I like ajmitch's proposal12:21
=== Hobbsee [n=Hobbsee@ubuntu/member/hobbsee] has joined #ubuntu-meeting
=== sistpoty often asks around on #ubuntu-motu what other motus think
crimsundholbach: I'm a bit uncomfortable with saying someone _must_ respond to email in 24 hrs12:22
dholbachI was just trying to make some sort of commitment12:22
dholbachI don't think it's the best proposal we can come up with either.12:22
sistpotyhow about calling for votes after 1 week?12:22
crimsun12 days seems reasonable12:23
crimsunit's a bit longer than 1 week and still gives MC 48 hours.12:23
dholbachafter the application came in?12:23
sistpotyyep12:23
crimsunright12:23
ajmitchfor most, I suspect we'd make a decision within 3-4 days12:24
sistpotyof course we can always do shorter, if everybody agrees right on the application ;)12:24
Hobbseeargh, MOTU meeting12:24
TheMusoHobbsee: MC meeting actually.12:25
Hobbseeno, ubuntu dev12:25
sistpotyhi Hobbsee12:25
Hobbseeoh.  oops12:25
=== Hobbsee stays quiet then
Hobbseehey sistpoty12:25
dholbachHobbsee: noooooo, no need to be quiet :)12:25
crimsundoes 12 days seem acceptable?12:25
Hobbseedholbach: but i'm not in MC?12:26
ajmitchcrimsun: yep12:26
sistpoty+112:26
crimsun(I have lecture in 15 minutes, so I need to begin wrapping up here)12:26
dholbachI'm happy with that too12:27
sistpotyok, fine12:27
dholbachHobbsee: that shouldn't stop you :)12:27
dholbachok, we'll add that to the charter too?12:27
sistpotysure12:28
dholbachsuper12:28
dholbachany other business?12:28
ajmitchmeeting times12:28
sistpotyI'd also suggest to have the charter ack'd during the next motu meeting12:28
ajmitchTODO lists12:28
dholbachajmitch: meetings times: go with the next motu meeting12:28
crimsunsistpoty: yes, let's bring that up12:28
ajmitchdholbach: ok, when is that scheduled for?12:29
crimsunthe 27th of this month IIRC12:29
dholbach27th, 9 utc12:29
ajmitchhm12:29
ajmitchTuesday, Mar 23rd, 8:00 UTC12:29
ajmitchthat's what the wiki page says12:29
ajmitchtuesday is the 27th12:29
sistpotyajmitch: no 23rd is wrong. I couldn't count weeks when doing the minutes (and just followed the typo in mm)12:29
dholbachhum... the fridge calendar says something else12:29
ajmitch8 or 9 UTC?12:30
dholbachthat'd be the usual 1,5 weeks12:30
dholbachtodo list: ajmitch: will you file those unmetdeps bugs?12:30
ajmitchyeah, ran into problems with massfile12:30
ajmitchand LP ignoring bugs I filed12:30
=== ajmitch has to chase that up
dholbachajmitch: let's disucss that together outside the meeting12:30
ajmitchok12:30
dholbachi'd also encourage each and everyone of you to tag bugs as 'bitesize' and 'packaging'12:31
dholbachto me it seems like a bunch of them got fixed already12:31
ajmitchyou did a great job tagging all those12:31
dholbachand it's easy enough for us to do12:31
dholbachthanks12:31
sistpotybitesize really rocks!12:31
Hobbseeguess you could tag all the unmet deps bugs as bitesize12:31
dholbachmost of them probably12:31
ajmitchHobbsee: not all of them are12:31
dholbachwe have a unmetdeps tag as well12:31
=== ajmitch doesn't know if he can tag by email yet
dholbachajmitch: heno has something figured out for that - we can include him in the discussion12:32
ajmitchmaybe I should just file bugs by the web UI12:32
ajmitchlike apport does12:32
dholbachuniverse hug day next thursday?12:32
dholbachfriday will be a regular one12:32
crimsunthat sounds good12:33
dholbachperfect - let's adjourn then?12:33
ajmitchsure, how regular shall our hug days & revu days be?12:33
=== ajmitch is happy to adjourn :)
dholbachi made 'universe hug days' a fixed agenda item :)12:33
ajmitchok12:33
dholbachmaybe we can revu days once feisty+1 opens12:33
sistpotysounds sane!12:34
ajmitchwe need all people in motu-uvf helping out12:34
imbrandonfirdays are revu days once feisty opens ;)12:34
ajmitchfor the bugs are starting to pile up12:34
dholbachsuper... adjourned then - thanks everybody12:34
=== dholbach will mail about universe hug day
imbrandonfridays*12:34
ajmitchthanks!12:34
crimsunthanks everyone12:34
sistpotyyay... thanks everyone12:34
=== asac [n=asac@debian/developer/asac] has joined #ubuntu-meeting
=== TheMuso [n=luke@ubuntu/member/themuso] has left #ubuntu-meeting []
=== Czessi [n=Czessi@dslb-088-073-041-056.pools.arcor-ip.net] has joined #ubuntu-meeting
=== daviey [n=dave1111@unaffiliated/daviey] has joined #ubuntu-meeting
=== jenda` [n=jenda@83.217.70.247] has joined #ubuntu-meeting
=== jenda` [n=jenda@83.217.70.247] has joined #ubuntu-meeting
=== Hobbsee_ [n=Hobbsee@ubuntu/member/hobbsee] has joined #ubuntu-meeting
=== jenda` [n=jenda@83.217.70.247] has joined #ubuntu-meeting
=== jenda` [n=jenda@83.217.70.247] has joined #ubuntu-meeting
=== givre [n=Florent@82.98.16.2] has joined #ubuntu-meeting
=== jenda` [n=jenda@195.47.80.185.adsl.nextra.cz] has joined #ubuntu-meeting
=== jenda [n=jenda@ubuntu/member/jenda] has joined #ubuntu-meeting
=== etank [n=etank@74-140-129-0.dhcp.insightbb.com] has joined #ubuntu-meeting
=== etank [n=etank@74-140-129-0.dhcp.insightbb.com] has joined #ubuntu-meeting
=== asac [n=asac@debian/developer/asac] has joined #ubuntu-meeting
=== jenda [n=jenda@ubuntu/member/jenda] has joined #ubuntu-meeting
=== lmanul [n=manu@194.230.53.149] has joined #ubuntu-meeting
=== Lure [n=lure@external-7.hermes.si] has joined #ubuntu-meeting
=== fernando [n=fernando@unaffiliated/musb] has joined #ubuntu-meeting
=== mvo_ [n=egon@p54A66BE8.dip.t-dialin.net] has joined #ubuntu-meeting
=== MaievShadowsong [n=ipv6now@222.90.76.164] has joined #ubuntu-meeting
=== MaievShadowsong [n=ipv6now@222.90.76.164] has left #ubuntu-meeting []
=== licio [n=licio@ubuntu/member/licio] has joined #ubuntu-meeting
=== asac [n=asac@debian/developer/asac] has joined #ubuntu-meeting
=== asac [n=asac@debian/developer/asac] has joined #ubuntu-meeting
=== pochu [n=pochu@ubuntu/member/pochu] has joined #ubuntu-meeting
=== rpereira [n=rpereira@ubuntu/member/rpereira] has joined #ubuntu-meeting
=== asac [n=asac@debian/developer/asac] has joined #ubuntu-meeting
=== BackwardsDown [n=niels@5351BB29.cable.casema.nl] has joined #ubuntu-meeting
=== j_ack [n=rudi@p508D85DE.dip0.t-ipconnect.de] has joined #ubuntu-meeting
=== Tonio_ [n=tonio@205.207.103-84.rev.gaoland.net] has joined #ubuntu-meeting
=== arualavi [n=Iva@67.Red-83-33-5.dynamicIP.rima-tde.net] has joined #ubuntu-meeting
=== mdz [n=mdz@cpe-76-173-8-128.socal.res.rr.com] has joined #ubuntu-meeting
=== Tonio_ [n=tonio@205.207.103-84.rev.gaoland.net] has joined #ubuntu-meeting
=== besonen_mobile_ [n=besonen_@71-220-225-182.eugn.qwest.net] has joined #ubuntu-meeting
=== j_ack_ [n=rudi@p508D8D2D.dip0.t-ipconnect.de] has joined #ubuntu-meeting
=== lfittl [n=lfittl@213.129.230.12] has joined #ubuntu-meeting
=== rolando-ve [n=rolando-@200.8.188.242] has joined #ubuntu-meeting
=== asac [n=asac@debian/developer/asac] has joined #ubuntu-meeting
=== BackwardsDown [n=niels@5351BB29.cable.casema.nl] has joined #ubuntu-meeting
=== BackwardsDown [n=niels@5351BB29.cable.casema.nl] has joined #ubuntu-meeting
=== gnomefre1k [n=gnomefre@c-71-225-172-3.hsd1.pa.comcast.net] has joined #ubuntu-meeting
=== asac [n=asac@debian/developer/asac] has joined #ubuntu-meeting
=== cyphase [n=cyphase@adsl-70-231-135-0.dsl.snfc21.sbcglobal.net] 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 []
=== BackwardsDown [n=niels@5351BB29.cable.casema.nl] has joined #ubuntu-meeting
=== asac_ [n=asac@debian/developer/asac] has joined #ubuntu-meeting
=== Klaidas[anapnea] [i=klaidas@anapnea.net] has joined #ubuntu-meeting
Klaidas[anapnea] @schedule Vilnius05:32
UbugtuSchedule for Europe/Vilnius: 17 Mar 17:00: Xubuntu | 19 Mar 17:00: Kernel Team | 20 Mar 01:00: IRC Operators | 20 Mar 20:00: Community Council | 21 Mar 14:00: Edubuntu | 22 Mar 18:00: Ubuntu Development Team05:32
=== Burgundavia [n=corey@24.68.237.193] has joined #ubuntu-meeting
=== Klaidas[anapnea] [i=klaidas@anapnea.net] has left #ubuntu-meeting []
=== hjmf [n=hjmf@62.Red-83-45-116.dynamicIP.rima-tde.net] has joined #ubuntu-meeting
=== merriam [n=merriam@84-12-173-95.dyn.gotadsl.co.uk] has joined #ubuntu-meeting
=== ogra [n=ogra@ubuntu/member/ogra] has joined #ubuntu-meeting
=== robitaille [n=daniel@ubuntu/member/robitaille] has joined #ubuntu-meeting
=== Burgundavia [n=corey@24.68.237.193] has joined #ubuntu-meeting
=== fernando [n=fernando@unaffiliated/musb] has joined #ubuntu-meeting
=== BackwardsDown [n=niels@5351BB29.cable.casema.nl] has joined #ubuntu-meeting
=== Lure [n=lure@clj46-234.dial-up.arnes.si] has joined #ubuntu-meeting
=== cbx33 [n=pete@ubuntu/member/cbx33] has joined #ubuntu-meeting
=== AlexLatchford [n=alex@82-44-193-109.cable.ubr07.haye.blueyonder.co.uk] has joined #ubuntu-meeting
=== fernando [n=fernando@unaffiliated/musb] has joined #ubuntu-meeting
=== BackwardsDown [n=niels@5351BB29.cable.casema.nl] has joined #ubuntu-meeting
=== BackwardsDown [n=niels@5351BB29.cable.casema.nl] has joined #ubuntu-meeting
=== Tonio_ [n=tonio@205.207.103-84.rev.gaoland.net] has joined #ubuntu-meeting
=== Owdgit [n=ron@88-110-225-176.dynamic.dsl.as9105.com] has joined #ubuntu-meeting
=== phanatic [n=phanatic@ubuntu/member/phanatic] has joined #ubuntu-meeting
=== cyphase [n=cyphase@adsl-70-231-135-0.dsl.snfc21.sbcglobal.net] has joined #ubuntu-meeting
=== poningru [n=poningru@pool-72-64-213-219.tampfl.fios.verizon.net] has joined #ubuntu-meeting
=== j_ack [n=rudi@p508d8d2d.dip0.t-ipconnect.de] has joined #ubuntu-meeting
=== Seveas [n=seveas@ubuntu/member/seveas] has joined #ubuntu-meeting
=== asac [n=asac@debian/developer/asac] has joined #ubuntu-meeting
=== tsmithe` [n=tsmithe@ubuntu/member/tsmithe] has joined #ubuntu-meeting
=== SD-Plissken [n=Snake@unaffiliated/sdplissken/x-000001] has joined #ubuntu-meeting
=== Burgundavia [n=corey@24.68.237.193] has joined #ubuntu-meeting
=== PriceChild [n=pricechi@ubuntu/member/pricechild] has joined #ubuntu-meeting
=== PriceChild [n=pricechi@ubuntu/member/pricechild] has left #ubuntu-meeting []
=== fernando [n=fernando@unaffiliated/musb] has joined #ubuntu-meeting
=== F0O [n=F00BaR@82-42-56-84.cable.ubr06.knor.blueyonder.co.uk] has joined #ubuntu-meeting
=== phanatic [n=phanatic@ubuntu/member/phanatic] has joined #ubuntu-meeting
=== F0O [n=F00BaR@82-42-56-84.cable.ubr06.knor.blueyonder.co.uk] has left #ubuntu-meeting []
=== merriam_ [n=merriam@84-12-81-29.dyn.gotadsl.co.uk] has joined #ubuntu-meeting
=== finalbeta [n=finalbet@d54C689F7.access.telenet.be] has joined #ubuntu-meeting

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