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

=== j_ack [n=rudi@p508DC0A7.dip0.t-ipconnect.de] has joined #ubuntu-meeting
=== Burgwork [n=corey@ubuntu/member/burgundavia] has joined #ubuntu-meeting
=== tonyyarusso [n=anthony@ubuntu/member/tonyyarusso] has joined #ubuntu-meeting
=== bordy [n=bordy@153-161.127-70.tampabay.res.rr.com] has joined #ubuntu-meeting
=== zul_ [n=chuck@CPE0006258ec6c1-CM000a73655d0e.cpe.net.cable.rogers.com] has joined #ubuntu-meeting
=== rpereira [n=rpereira@ubuntu/member/rpereira] has joined #ubuntu-meeting
=== doko [n=doko@dslb-088-073-065-209.pools.arcor-ip.net] has joined #ubuntu-meeting
=== Hobbsee [n=Hobbsee@ubuntu/member/hobbsee] has joined #ubuntu-meeting
=== ogra [n=ogra@ubuntu/member/ogra] has joined #ubuntu-meeting
=== ash211_ [n=andrew@user-1121s8r.dsl.mindspring.com] has joined #ubuntu-meeting
=== Burgwork [n=corey@ubuntu/member/burgundavia] has joined #ubuntu-meeting
=== Burgwork [n=corey@ubuntu/member/burgundavia] has joined #ubuntu-meeting
=== fasdfas__ [n=asdfasdf@24.98.177.125] has joined #ubuntu-meeting
=== freeflying [i=root@ubuntu/member/freeflying] has joined #ubuntu-meeting
=== cyphase [n=cyphase@c-71-202-49-23.hsd1.ca.comcast.net] has joined #ubuntu-meeting
=== bordy [n=bordy@153-161.127-70.tampabay.res.rr.com] has joined #ubuntu-meeting
=== licio [n=licio@ubuntu/member/licio] has joined #ubuntu-meeting
=== zul [n=chuck@ubuntu/member/zul] has joined #ubuntu-meeting
=== tonyy [n=anthony@ubuntu/member/tonyyarusso] has joined #ubuntu-meeting
=== nixternal [n=nixterna@c-71-194-189-213.hsd1.il.comcast.net] has joined #ubuntu-meeting
=== nixternal [n=nixterna@ubuntu/member/nixternal] has joined #ubuntu-meeting
=== tonyyarusso [n=anthony@ubuntu/member/tonyyarusso] has joined #ubuntu-meeting
=== slomo_ [n=slomo@ubuntu/member/slomo] has joined #ubuntu-meeting
=== fernando [n=fernando@unaffiliated/musb] has joined #ubuntu-meeting
=== bordy [n=bordy@153-161.127-70.tampabay.res.rr.com] has joined #ubuntu-meeting
=== Neronious [n=michael@user-0c8hlrm.cable.mindspring.com] has joined #ubuntu-meeting
=== Neronious [n=michael@user-0c8hlrm.cable.mindspring.com] has left #ubuntu-meeting []
=== doko [n=doko@dslb-088-073-065-209.pools.arcor-ip.net] has joined #ubuntu-meeting
=== asac_ [n=asac@debian/developer/asac] has joined #ubuntu-meeting
=== ash211 [n=andrew@user-1121s8r.dsl.mindspring.com] has joined #ubuntu-meeting
=== Brady_M [n=o0splitp@cpe-24-166-229-191.columbus.res.rr.com] has joined #ubuntu-meeting
=== bordy [n=bordy@153-161.127-70.tampabay.res.rr.com] has joined #ubuntu-meeting
=== Brady_M [n=o0splitp@cpe-24-166-229-191.columbus.res.rr.com] has left #ubuntu-meeting []
=== fernando__ [n=fernando@189.0.131.95] has joined #ubuntu-meeting
=== bordy240 [n=bordy@153-161.127-70.tampabay.res.rr.com] has joined #ubuntu-meeting
=== bordy240 [n=bordy@153-161.127-70.tampabay.res.rr.com] has joined #ubuntu-meeting
=== bordy240 is now known as bordy_away
=== bordy_away is now known as bordy240
=== bordy240 is now known as bordy
=== freeflying [i=root@gobstopper.dreamhost.com] has joined #ubuntu-meeting
=== Pien [n=novUgrh5@h-68-164-91-167.snvacaid.dynamic.covad.net] has joined #ubuntu-meeting
=== Pien is now known as PienLoKe
=== PienLoKe [n=novUgrh5@h-68-164-91-167.snvacaid.dynamic.covad.net] has left #ubuntu-meeting ["#ubuntu]
=== robitaille [n=daniel@ubuntu/member/robitaille] has joined #ubuntu-meeting
=== fabbione [i=fabbione@gordian.fabbione.net] has joined #ubuntu-meeting
=== ZhongHan [n=chatzill@bb121-6-206-96.singnet.com.sg] has joined #ubuntu-meeting
=== Hobbsee [n=Hobbsee@ubuntu/member/hobbsee] has joined #ubuntu-meeting
=== Lure [n=lure@external-7.hermes.si] has joined #ubuntu-meeting
freeflying@schedule Shanghai08:01
UbugtuSchedule for Asia/Shanghai: 07 Mar 02:00: Mozilla Team | 07 Mar 04:00: MOTU meeting | 07 Mar 20:00: Edubuntu | 09 Mar 00:00: Ubuntu Development Team | 11 Mar 18:00: LoCo Team | 13 Mar 02:00: Derivative Team08:01
sid@schedule New_York08:01
UbugtuSchedule for America/New_York: 06 Mar 13:00: Mozilla Team | 06 Mar 15:00: MOTU meeting | 07 Mar 07:00: Edubuntu | 08 Mar 11:00: Ubuntu Development Team | 11 Mar 06:00: LoCo Team | 12 Mar 14:00: Derivative Team08:01
=== MootBot [n=MootBot@li15-14.members.linode.com] has left #ubuntu-meeting []
=== Seveas [n=seveas@ubuntu/member/seveas] has joined #ubuntu-meeting
=== MootBot [n=MootBot@lister.incognitus.net] has joined #ubuntu-meeting
=== beuno [n=martin@200-127-6-133.cab.prima.net.ar] has joined #ubuntu-meeting
=== dholbach [n=daniel@i59F752EF.versanet.de] has joined #ubuntu-meeting
=== fabbione [i=fabbione@gordian.fabbione.net] has joined #ubuntu-meeting
=== mruiz [n=mruiz@ubuntu/member/mruiz] has joined #ubuntu-meeting
=== mvo [n=egon@p54A65CC8.dip.t-dialin.net] has joined #ubuntu-meeting
=== raphink [n=raphink@ubuntu/member/raphink] has joined #ubuntu-meeting
=== pochu [n=pochu@ubuntu/member/pochu] 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!"]
=== pipedrea1 [n=pipedrea@musselcracker.aims.ac.za] has joined #ubuntu-meeting
=== finalbeta [n=finalbet@d54C68D0D.access.telenet.be] has joined #ubuntu-meeting
=== pipedream [n=pipedrea@musselcracker.aims.ac.za] has joined #ubuntu-meeting
=== mc44 [n=mc44@unaffiliated/mc44] has joined #ubuntu-meeting
=== yharrow [n=sysadmin@h-68-164-34-22.nycmny83.dynamic.covad.net] has joined #ubuntu-meeting
=== freeflying [i=root@gobstopper.dreamhost.com] has joined #ubuntu-meeting
=== afflux [i=discoflu@gateway/gpg-tor/key-0x6E18D3C4] has joined #ubuntu-meeting
=== cyphase [n=cyphase@c-71-202-49-23.hsd1.ca.comcast.net] has joined #ubuntu-meeting
=== lmanul [n=manu@dan75-4-82-239-58-38.fbx.proxad.net] has joined #ubuntu-meeting
=== lionel [n=lionel@ip-61.net-82-216-103.rev.numericable.fr] has joined #ubuntu-meeting
=== Hobbsee [n=Hobbsee@ubuntu/member/hobbsee] has joined #ubuntu-meeting
Hobbsee@schedule sydney12:00
UbugtuSchedule for Australia/Sydney: 07 Mar 05:00: Mozilla Team | 07 Mar 07:00: MOTU meeting | 07 Mar 23:00: Edubuntu | 09 Mar 03:00: Ubuntu Development Team | 11 Mar 21:00: LoCo Team | 13 Mar 05:00: Derivative Team12:00
emonkey@schedule zurich12:08
UbugtuSchedule for Europe/Zurich: 06 Mar 19:00: Mozilla Team | 06 Mar 21:00: MOTU meeting | 07 Mar 13:00: Edubuntu | 08 Mar 17:00: Ubuntu Development Team | 11 Mar 11:00: LoCo Team | 12 Mar 19:00: Derivative Team12:08
=== Hobbsee wont make that MOTU meeting. oh well.
=== fernando [n=fernando@unaffiliated/musb] has joined #ubuntu-meeting
=== daviey [n=dave1111@unaffiliated/daviey] has joined #ubuntu-meeting
daviey@schedule london12:33
UbugtuSchedule for Europe/London: 06 Mar 18:00: Mozilla Team | 06 Mar 20:00: MOTU meeting | 07 Mar 12:00: Edubuntu | 08 Mar 16:00: Ubuntu Development Team | 11 Mar 10:00: LoCo Team | 12 Mar 18:00: Derivative Team12:33
=== jsgotangco [n=jsg123@ubuntu/member/jsgotangco] has joined #ubuntu-meeting
=== jeang [n=jeang@196.209.157.27] has joined #ubuntu-meeting
=== jeang [n=jeang@196.209.157.27] has left #ubuntu-meeting []
=== lengau [n=lengau@c-68-53-53-39.hsd1.tn.comcast.net] has joined #ubuntu-meeting
=== beuno [n=martin@68-155-114-200.fibertel.com.ar] has joined #ubuntu-meeting
=== licio [n=licio@ubuntu/member/licio] has joined #ubuntu-meeting
=== fernando [n=fernando@unaffiliated/musb] has joined #ubuntu-meeting
=== dholbach_ [n=daniel@i59F70192.versanet.de] has joined #ubuntu-meeting
=== freeflying [i=root@gobstopper.dreamhost.com] has joined #ubuntu-meeting
=== peppe84 [n=peppe84@host5-47-dynamic.6-87-r.retail.telecomitalia.it] has joined #ubuntu-meeting
=== peppe84 [n=peppe84@host5-47-dynamic.6-87-r.retail.telecomitalia.it] has left #ubuntu-meeting ["Baciamo]
=== 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
=== peppe84 [n=peppe84@host5-47-dynamic.6-87-r.retail.telecomitalia.it] has joined #ubuntu-meeting
=== peppe84 [n=peppe84@host5-47-dynamic.6-87-r.retail.telecomitalia.it] has left #ubuntu-meeting ["Baciamo]
=== jsgotangco [n=jsg@ubuntu/member/jsgotangco] has joined #ubuntu-meeting
=== mc44 [n=mc44@unaffiliated/mc44] has joined #ubuntu-meeting
=== afflux [i=k@gateway/gpg-tor/key-0x6E18D3C4] has joined #ubuntu-meeting
=== peppe84 [n=peppe84@host5-47-dynamic.6-87-r.retail.telecomitalia.it] has joined #ubuntu-meeting
=== ogra [n=ogra@ubuntu/member/ogra] has joined #ubuntu-meeting
=== peppe84 [n=peppe84@host5-47-dynamic.6-87-r.retail.telecomitalia.it] has left #ubuntu-meeting ["Baciamo]
=== mvo [n=egon@p54A65CC8.dip.t-dialin.net] has joined #ubuntu-meeting
=== sky_walkie [i=czzhrd02@xdsl-563.lodz.dialog.net.pl] has joined #ubuntu-meeting
=== j_ack [n=rudi@p508DC141.dip0.t-ipconnect.de] has joined #ubuntu-meeting
=== finalbeta [n=finalbet@d54C68D0D.access.telenet.be] has joined #ubuntu-meeting
=== meltdown [n=meltdown@cpe-24-198-175-219.maine.res.rr.com] has joined #ubuntu-meeting
=== Rinchen [n=Rinchen@ubuntu/member/rinchen] has joined #ubuntu-meeting
=== Rinchen [n=Rinchen@ubuntu/member/rinchen] has left #ubuntu-meeting ["is]
=== peppe84 [n=peppe84@host5-47-dynamic.6-87-r.retail.telecomitalia.it] has joined #ubuntu-meeting
=== peppe84 [n=peppe84@host5-47-dynamic.6-87-r.retail.telecomitalia.it] has left #ubuntu-meeting ["Baciamo]
=== jsgotangco [n=jsg123@ubuntu/member/jsgotangco] has joined #ubuntu-meeting
=== Lure [n=lure@clj46-234.dial-up.arnes.si] has joined #ubuntu-meeting
=== geser [n=mb@ubuntu/member/geser] has joined #ubuntu-meeting
=== Mez [n=Mez@ubuntu/member/mez] has joined #ubuntu-meeting
=== mooey [n=chris@217.151.110.115] has joined #ubuntu-meeting
=== cbx33 [n=pete@ubuntu/member/cbx33] has joined #ubuntu-meeting
=== hjmf [n=hjmf@140.Red-217-125-227.dynamicIP.rima-tde.net] has joined #ubuntu-meeting
=== Admiral_Chicago [n=Admiral_@ubuntu/member/admiral-chicago] has joined #ubuntu-meeting
=== jenda [n=jenda@ubuntu/member/jenda] has joined #ubuntu-meeting
=== ScottK [n=ScottK@static-72-81-252-22.bltmmd.fios.verizon.net] has joined #ubuntu-meeting
=== robitaille [n=daniel@ubuntu/member/robitaille] has joined #ubuntu-meeting
=== tonyyarusso [n=anthony@ubuntu/member/tonyyarusso] has joined #ubuntu-meeting
=== mc44 [n=mc44@unaffiliated/mc44] has joined #ubuntu-meeting
=== licio [n=licio@ubuntu/member/licio] has joined #ubuntu-meeting
=== phanatic [n=phanatic@ubuntu/member/phanatic] has joined #ubuntu-meeting
=== lariamat [n=qnull@p54BC9C2F.dip0.t-ipconnect.de] has joined #ubuntu-meeting
=== PriceChild [n=pricechi@ubuntu/member/pricechild] has joined #ubuntu-meeting
=== bipolar [n=bflong@146.145.26.91] has joined #ubuntu-meeting
=== ..[topic/#ubuntu-meeting:Ubugtu] : Current meeting: Mozilla Team | Calendar: http://fridge.ubuntu.com/event | Logs: https://wiki.ubuntu.com/MeetingLogs/ | 06 Mar 20:00 UTC: MOTU meeting | 07 Mar 12:00 UTC: Edubuntu | 08 Mar 16:00 UTC: Ubuntu Development Team | 11 Mar 10:00 UTC: LoCo Team | 12 Mar 18:00 UTC: Derivative Team
=== dfarning [n=dfarning@72-160-220-159.dyn.centurytel.net] has joined #ubuntu-meeting
gnomefreakare we ready? and who is chairing?06:58
dfarningim ready06:59
dfarningfor once06:59
dfarningI thought alex was06:59
Admiral_Chicagohe won't be back until 18.3007:00
gnomefreakme too07:00
asacready07:00
tonyyarussoHave an agenda link handy?07:00
gnomefreakAdmiral_Chicago: what to chair?07:00
gnomefreaktonyyarusso: https://wiki.ubuntu.com/MozillaTeam/Meetings07:00
Admiral_Chicagognomefreak: no thank you, i have to be in and out due to school reponsibilities07:01
dfarninggnomefreak, you are the one with experience;)07:02
AlexLatchfordmeh?07:02
gnomefreakthanks but im in middle of something atm if someone wants to start07:02
gnomefreakdfarning: your up first anyway iirc07:02
AlexLatchfordOkay ill chair07:02
gnomefreakty AlexLatchford07:02
dfarningty07:02
AlexLatchforddfarning: Approve MozillaTeam/Governance07:03
dfarninghttps://wiki.ubuntu.com/MozillaTeam/Governance07:03
gnomefreakbtw we dont have council page so i changed it07:03
dfarningWanted to formally approve this07:03
gnomefreakbut i see you found out :)07:03
dfarningty07:03
AlexLatchfordPersonally I have no problems with the Council at the moment07:04
AlexLatchfordthe document as it stands is great07:04
gnomefreak+107:04
AlexLatchfordMaybe the whole 2 weeks meeting should be changed to monthly07:04
gnomefreakoh crap07:04
asacmonthly is better i guess07:04
dfarningok things were busy busy last month;)07:05
dfarning1 per month07:05
Admiral_Chicago+107:05
AlexLatchfordwell we can call one if we need one in between07:05
gnomefreak+1 unless needed otherwise07:05
AlexLatchford+107:05
AlexLatchfordwho is on the Council so we know?07:05
dfarningnominate asac, john, alex, and freddy07:05
AlexLatchfordI nominate dfarning07:05
AlexLatchforddo we need CC approval?07:06
Admiral_Chicagoi would nominate hilario07:06
asacdon't know07:06
dfarningtalk to johno we are ok07:06
Admiral_Chicagoerr i nominate hilario as well07:06
gnomefreakno we wouldnt really07:06
dfarningtalked07:06
dfarningvery clear we are under cc07:06
gnomefreakcorrect07:06
AlexLatchfordhmm okay07:06
gnomefreakwe need to decide on couuncil since 07:07
dfarning??07:07
gnomefreakwow wtf was that07:07
Admiral_ChicagoSo to be clear, the council would take effect immedietly?07:07
Admiral_Chicagoand last until feisty+1 came out?07:08
dfarningyes until feisty comes out in a couple of wee07:08
gnomefreakAdmiral_Chicago: not as of now with new nominations07:08
AlexLatchforderm, well we have nominations for dfarning, AlexLatchford, gnomefreak, Admiral_Chicago, asac and hjmf07:08
dfarningI fine with that07:08
AlexLatchfordcool, anyone know if hjmf has a problem with this?07:09
Admiral_Chicagoditto07:09
gnomefreakthats fine. has anyone checked with hjmf?07:09
AlexLatchfordas I dont believe he is here07:09
gnomefreakhe left a little while ago07:09
dfarninghe is pretty busy with school07:09
Admiral_Chicagohes afk.07:09
Admiral_Chicagofrom what i recalll07:09
AlexLatchfordaha okay, ewll we can include him and if his status changes we can rethink07:09
AlexLatchford+1 on all candidates07:09
dfarning+107:09
gnomefreaki say we finish that up on ML07:10
asac+1 (though a pretty large group imo) :)07:10
Admiral_Chicago+107:10
dfarningok finish on ML07:10
AlexLatchfordokay, dfarning can you make a new LP.net team and add the various members?07:10
dfarningyes07:11
gnomefreakif i remember i will send out a post to list07:11
AlexLatchfordokay, thanks john07:11
gnomefreakyw07:11
AlexLatchfordNext: Approve MozillaTeam/Membership07:11
dfarninghttps://wiki.ubuntu.com/MozillaTeam/Membership07:11
AlexLatchfordhttps://wiki.ubuntu.com/MozillaTeam/Membership07:11
dfarningI would like to postpone until i talk more with jono07:12
dfarningnew person friendly vs QA is hard;(07:12
AlexLatchfordyeah you have a point there07:12
gnomefreakagreed dfarning you gonna handle talking to jono?07:13
dfarningI will do so07:13
gnomefreaki may have something else for you to run by him if i cant find elkbuntu07:13
dfarningok07:13
AlexLatchfordokay07:13
dfarningnext?07:13
AlexLatchford-1 on Membership Wiki, postpone to next meeting07:14
AlexLatchfordyou again david07:14
AlexLatchfordApprove MozillaTeam/Upstream07:14
Admiral_Chicago-107:14
Admiral_Chicagoerr membership07:14
dfarninghttps://wiki.ubuntu.com/MozillaTeam/Upstream07:14
AlexLatchfordlol Freddy07:14
asacpostpone07:15
asacups07:15
asaclate :)07:15
gnomefreakwhy -1?07:15
asacabout membership ;)07:15
dfarningasac, what are your thoughts?07:15
=== popey [n=alan@ubuntu/member/popey] has joined #ubuntu-meeting
gnomefreakim happy with postponing it until david speaks with jono07:16
asacthe document is good, but i don't know if we need a official policy for that07:16
dfarningI would like to set a standard of behavior07:17
dfarningthat other can depend on07:17
dfarningothers07:17
dfarningso they know we will not send crap/spam07:17
asacah ok07:17
=== gnomefreak wants to stop what has happned the past week with triaging
dfarningexactly;(07:18
asacpatches should only be pushed upstream as well as bugs07:18
asacafter being reviewed by someone experienced imo07:18
asacif that is in that document then its fine07:18
asacits important not to stress upstream relationship ... as you said with "crap/spam"07:18
AlexLatchfordPersonally I feel the document needs a little more work before it should be approved07:19
dfarningi'll add that07:19
dfarningAlexLatchford, what other work?07:19
gnomefreaklets get up with jono see what he says than add it to agenda after wiki is fixed in jonos idea of it07:19
AlexLatchfordSaying who to contact to confirm patches, I am on the team but do not know much about Patches07:19
AlexLatchfordfor instance..07:20
Admiral_Chicagoi think we need to be more visible so people don't do work outside of our policies07:20
gnomefreakasac: would be the contact maybe david also?07:20
AlexLatchfordAdmiral_Chicago: True07:20
=== gnomefreak not good with patches but i can apply them for testing
Admiral_Chicagofor example, having to go and undo peoples tagging after we set a tag library07:21
dfarningI have been trying to be an admin contact letting you guys do all the tech stuff07:21
gnomefreakdfarning: tagging closing remarking ect...07:21
asacgnomefreak: contact for upstream bug review?07:21
dfarningok with this in mind i'll rewrite and ask for more feed back on ML07:22
AlexLatchford+1 on dfarning's suggestion07:22
gnomefreakremarking example = after full crash report is attached people are "please install -dbg and run backtrace" or " not enough info closing..."07:22
asacok .... action: improve upstream directions07:22
Admiral_Chicago+1 to a rewrite as well07:23
AlexLatchfordYes, it still needs a bit more discussion in my eyes07:23
AlexLatchfordon the mailing list07:23
dfarningnext?07:23
asacAdmiral_Chicago: about the visibility07:23
asacthere is a general debuggingprocedures page07:23
asacwhich links to our policy07:23
AlexLatchfordNext: Extension / Theme policy - Admiral_Chicago07:23
Admiral_Chicagodoesn't mean people read it07:24
asacbug triagers should read that page from time to time ... though they probably don't do07:24
Admiral_Chicagoi mean in the community07:24
asacyes07:24
AlexLatchfordmaybe we can link it in from the Bugsquad page..07:24
gnomefreakthey dont they are using -bugs responces07:24
asaci am working on convincing lp folks for adding special hints for packages07:24
Admiral_Chicagowell i put this agenda item to be clear about which themes / extensions we can support07:24
asaclike: bugs for this package are processed following procedures on http://xxx07:25
gnomefreakso far only what we have afaik07:25
Admiral_Chicagoas I know of, we have a handful of themes and extensions in the repositories07:25
dfarningI did have enough tech knowledge to determine why we were packaging certain extensions07:26
dfarningdid not07:26
gnomefreakasac: should we get a list and go one by one down list to see what ones would be worth adding for feisty+1 (somehow i doubt they will end up in feisty)07:26
asacplease lets not add more to feisty07:26
asacothers that crash07:26
Admiral_Chicagoso i suggest we build a library of supported packages07:26
asacfeisty is pretty late07:26
gnomefreakasac: thats why i said feisty+1 :)07:26
asacsorry :)07:26
asacsure07:26
asacanyway, i guess there are only a few extensions are valid candidates07:27
AlexLatchfordWell, which extensions are we going to include, how do we decide?07:27
Admiral_Chicagoonce we get a valid bug report, those would have to be pushed upstream07:27
gnomefreakAdmiral_Chicago: get a list of what you are thinking we support and add it to agenda for future meeting (IMHO) i have one nad asac had one we were looking into07:27
dfarningI am thinking remove unless there is a good reason to keep07:27
asacyes ... good reason: extension is really popular; ubuntu specific; or uses native component07:28
dfarningasac,  +107:28
AlexLatchford+1 for me07:28
gnomefreakdfarning: i would rather in respect to community add some extensions/themes but only ones that can erally provide help and are throughly checked out07:28
asacnative components are really rare ... so there should be only a handful in the end07:28
dfarningnot becaue a MOTU thinks it would be a good place to start packaging07:28
dfarning;(07:28
asacdfarning: imo we cannot do much, but deny that we will take care for them07:29
gnomefreakcolorzilla == popular but imho crap since it is cause of alot of crashes07:29
AlexLatchfordso what action are we taking?07:29
asacif they add such packages, packagers have to take care on bug triage alone07:29
Admiral_Chicagocould we assign them back to the packager?07:29
asaccolorzilla qualifies by "native component" which is why it crashes :)07:29
gnomefreakah07:29
asachowever colorzilla has not been released under free license07:29
asacso not yet a valid candidate07:30
AlexLatchfordso what action are we taking?07:30
dfarningI'll post something to MOTU ML for consideration07:30
asacAdmiral_Chicago: yes you can assign back to packager07:30
AlexLatchfordare we going to make a list of extensions that are working, etc..07:30
Admiral_Chicagono i mean, let them deal with the bug reports07:30
asacdon't know ... document which extensions qualify for mozilla team support07:30
gnomefreakmine has but i dont know where to even think about beginning on that one since i couldnt find the files we were looking for and i think i have since made it go away07:30
asace.g. by guidelines i posted above07:30
Admiral_ChicagoAlexLatchford: i was hoping we could get a list of extensions we support.07:30
dfarningwould can do the list07:31
gnomefreakAdmiral_Chicago: i would say start there07:31
AlexLatchfordAdmiral_Chicago: could you flesh out a wiki page and then post it to the ML for discussion?07:31
Admiral_ChicagoAlexLatchford: can do chief07:31
asacAdmiral_Chicago: i think we should decide if request pops up ... we can of course screen what is currently in archive and say "yes or no"07:31
AlexLatchfordta07:31
gnomefreakmaybe on your rounds in irc look for what people like and use but try not to ask in support channels07:31
Admiral_Chicagoyes07:32
AlexLatchfordwell look for bug reports, only package extensions that do not work without it07:32
gnomefreakim guessing we have a bit of time on that but would be good to have around feisty's release07:32
Admiral_Chicagoi'll get a wiki going, send it to the ML, maybe post on the planet about it07:32
gnomefreakk07:32
AlexLatchfordgood idea07:32
asack07:32
dfarningAdmiral_Chicago, +107:32
AlexLatchfordNext: Greasemonkey script maintainer wanted - asac07:33
gnomefreaklol07:33
asacits just a request07:33
asacif someone knows .js07:33
asacand wants to improve life for us all :)07:33
AlexLatchfordmeh fair enough07:33
gnomefreak+1 for asac as maintainer ;) j/k07:33
AlexLatchfordthought I would link it07:33
asacotherwise, i will try to do at some point07:33
AlexLatchfordlol07:33
Admiral_Chicagoi know a little java but not too much07:33
gnomefreaki havent looked at it yet07:33
gnomefreakAdmiral_Chicago: its JS not so much java07:33
asacits just javascript07:33
asaclike you do in html pages07:33
gnomefreakJS is easier07:33
Admiral_Chicagoeh.07:34
asacmaybe lets open a task page :) ... to add such jobs that still have no owner :)07:34
gnomefreaki remember bits and peices from classes i took in java. we had to work with some JS07:34
AlexLatchfordasac: +107:34
gnomefreakasac: +107:34
dfarninggot one on /Roadmap07:34
AlexLatchfordhttps://wiki.ubuntu.com/MozillaTeam/Roadmap07:34
AlexLatchfordadd it to the Roadmap Tasks07:35
gnomefreakbtw everyone stay i have something to ask at end of meeting :)07:35
Admiral_Chicagowill do gnomefreak07:35
AlexLatchfordokay, next?07:35
dfarningnext?07:35
asacok maybe make another table for tasks that need a maintainer?07:35
Admiral_Chicagowait, we skipped AlexLatchford 's big07:35
asaci think we are through07:35
Admiral_Chicagobug*07:35
asacoh07:35
AlexLatchfordNext: Dapper / Fx 2.0 policy [WWW]  Bug 89704 - Admiral_Chicago07:35
UbugtuMalone bug 89704 in firefox "No backport of Firefox 2.o to Dapper" [Undecided,Needs info]  https://launchpad.net/bugs/8970407:35
AlexLatchfordAdmiral_Chicago: yeah we are not going in order, my points are not High on the list07:36
gnomefreakthats stated in bug07:36
Admiral_Chicagoasac: maybe you can say something about out 1.5 policy07:36
gnomefreakthere isnt much we can do with it07:36
Admiral_Chicagoour*07:36
dfarningAsac can you write a faq on why we can build 2.0 on dapper07:36
AlexLatchfordYes I read the response from cjwatson07:36
asacah07:36
dfarningcann't07:36
asaclook at the bug07:36
gnomefreakdfarning: the upgrade page shouyld be fine for htat07:36
asacits already done07:36
gnomefreakthat07:36
asacwe posted official wiki page07:36
asacthat states how we approach dapper long term security07:37
dfarningwhere, I missed that;(07:37
asacsee comment from colin07:37
Admiral_Chicagolooking now07:37
gnomefreakhttp://wiki.ubuntu.com/DapperFirefoxSupport07:37
Admiral_Chicagothe Beta LP page is slower than molasses07:37
asacyes thats the content07:37
gnomefreakAdmiral_Chicago: yes i know but i think because everyone went looking at it07:38
dfarningreading07:38
AlexLatchfordhttps://wiki.ubuntu.com/MozillaTeam/FAQ07:38
AlexLatchfordhave added this for now07:38
asacgood07:38
AlexLatchfordSo this issue is sorted...07:39
Admiral_Chicagoalright07:39
dfarningsound good07:39
asacshould be ... official statement exists07:39
AlexLatchfordNext: Accessibility testing and issues, where we can help...07:39
asace.g. canonical statement07:39
Admiral_Chicagognomefreak: no, i think in general07:39
AlexLatchfordThis is more of a 'Be Aware' than a discussion point07:39
Admiral_Chicagothe beta page is just slow...07:40
gnomefreakAdmiral_Chicago: its not slow for me anymore07:40
Admiral_Chicagomaybe its my network, i'll test at home07:40
=== asac agrees that beta is slow
gnomefreakagreed in most cases is07:40
gnomefreakmoving on?07:40
AlexLatchfordNext: Accessibility testing and issues, where we can help...07:40
AlexLatchfordThis is more of a 'Be Aware' than a discussion point07:40
asaci have no idea about accessibility07:40
dfarningme neither;(07:41
asaci don't like this07:41
AlexLatchfordBasically the Accessibility Team has been working hard on Orca in Firefox to make sure it actually works07:41
gnomefreakme neither to both comments07:41
asacbut someone who knows should setup some introduction on something07:41
dfarningI'll look into in07:41
asace.g. what tools are used for what07:41
asacetc.07:41
AlexLatchfordwell Orca is the main program07:41
AlexLatchfordcurrently they are implementing colour filters for the colour blind I believe07:41
gnomefreakAlexLatchford: is it orcas issues or ff?07:41
dfarningI'll ask the ocra guy for a introduction to the issues07:41
Admiral_Chicagoafaik, orca has a lot of problems building07:41
AlexLatchfordWell it is Orca issues that will probably be reported to Firefox07:41
asacif its a firefox specific issue, someone who knows should probably come up with some details07:42
gnomefreakIMHO orca should be filed against orca07:42
AlexLatchfordWell, this is what we are trying to discover, we need to work closely with them as sometimes it is their bug and sometimes it is ours07:42
dfarningI'll start the discussion07:43
asacsure ... they should just join us :) ... at least from time to time07:43
AlexLatchfordbut if you see a bug that you believe is Accessibility related, say if it only occuring with Orca enabled07:43
AlexLatchfordyeah, i will invite Henrik to the next meeting07:43
Admiral_Chicagohe was at our last one iirc.07:43
AlexLatchford..then tag it 'Accessibility' and also subscribe the Accessibility Team to the bug07:43
asachaven't seen any ... maybe orca people can do us a favor and search our bts for orca issues?07:43
AlexLatchfordAdmiral_Chicago: yes he was07:43
gnomefreakmy point being we have more than enough bugs to spread out to 35 teams and still not be fixed by end of year why add more if its not related to fx or tb07:44
AlexLatchfordgnomefreak: this is what I am saying, we need to reassign it when it is an issue..07:44
asacyes ... if its not related, its not our problem07:44
asacreassign07:44
AlexLatchfordas we cannot fix it07:44
AlexLatchfordit is more of a be aware of this problem07:45
AlexLatchfordthan what we need to do07:45
asacok :)07:45
gnomefreakAlexLatchford: you have the link to them as tagged still on the tags wiki right?07:45
AlexLatchfordBelieve so07:45
AlexLatchfordhttps://wiki.ubuntu.com/MozillaTeam/Bugs/Tags07:45
gnomefreakdfarning: who are you planning on talking to?07:45
gnomefreakbtw ther eis only 107:46
AlexLatchfordWell I have emailed the Accessibility list07:46
dfarningwho ever know anything about accessability:)07:46
AlexLatchfordand they are kind of aware of the problem, the response I got back was a little quiet07:46
gnomefreaklol dfarning07:46
gnomefreakok who has free time this week07:46
AlexLatchfordill investigate this more07:46
gnomefreaklets kill all birds ;) with this07:46
AlexLatchfordas I started it07:46
dfarningubutnu accessability, firefox accessibilty, ...07:47
AlexLatchfordOkay.. moving on?07:47
gnomefreakasac: any patches/testing need to be done this week?07:47
gnomefreakAlexLatchford: one sec please07:47
AlexLatchfordokay07:47
=== gnomefreak thinking outloud
dfarningdid the apport patch make it?07:48
asacgnomefreak: not yet :)07:48
asac^^ about patches/testing that needs to be done07:48
gnomefreakasac: ok i need someone else with me on bug triaging this week. start at one end and work your way through tagging them and assigning them07:48
AlexLatchfordI have added the testing repository to my sources.list07:49
gnomefreaks/asac/everyone07:49
=== dfarning can do 2 hour per day
asacit might be a bit tricky to install testing repository versions for the first time07:49
gnomefreakit seems like we got caught up with other things nad forgot about it07:49
asacafter that they should automatically upgrade07:49
=== dfarning wil have a lot of questions
gnomefreakdfarning: thats fine.07:49
gnomefreakdfarning: ill be here most of day during week07:49
asacokay ... are we through07:50
asac??07:50
dfarningsounds good07:50
gnomefreakdfarning: just remember crash report/edgy/coredump please assign to me07:50
dfarningok07:50
AlexLatchfordNext: GUI Consistency. [WWW]  Bug 4226307:50
UbugtuMalone bug 42263 in firefox "Toolbar display should be "Icons and text" for consistency" [Wishlist,Confirmed]  https://launchpad.net/bugs/4226307:50
gnomefreakick still on that one07:50
AlexLatchfordmeh?07:50
=== gnomefreak likes the icons without text.
AlexLatchfordwell there is an option to turn it off07:51
gnomefreakhover mouse over it and text is there07:51
AlexLatchfordagreed, but it is more for consistency07:51
dfarningwe may want to postpone this one07:51
dfarningtalk of mozilla starting a linux gui group07:51
AlexLatchfordReally?07:51
gnomefreakyou can add text fairly easy07:52
Admiral_Chicagoyes postpone it.07:52
dfarningso all distros can work together to improve interface on gtk kde07:52
AlexLatchfordgnomefreak: I know, but it is more of a consistency across the desktop07:52
AlexLatchfordTB, Nautilus, gEdit all use Text too07:52
Admiral_ChicagoKonqueror doesn't07:53
AlexLatchford*rolls eyes*07:53
gnomefreakasac: ?07:53
RiddellAdmiral_Chicago: doesn't what?07:54
AlexLatchfordPersonally it wouldn't bother me too much if the change was made07:54
gnomefreakRiddell: have text and icons07:54
Riddellgnomefreak: it does in KDE 407:54
AlexLatchfordas default?07:54
Riddellyes07:54
gnomefreakyes07:54
AlexLatchfordwell if we are after consistency I really think the change needs to be made, but whether or not we wait until Feisty+1 for it if we need more debate time..07:55
gnomefreakwe should beablet o change it with very little feedback from mozilla but im opposed to the change personally. it just adds one more thing to slow fx down07:55
asacsorry ... have no time ... tel conference07:55
gnomefreakasac: k07:56
Admiral_Chicagoi meant in 3.5.6.07:56
gnomefreakok lets posepone this than wait for asac feedback on it07:56
dfarningok07:56
AlexLatchfordgnomefreak: agreed07:56
gnomefreakAdmiral_Chicago: text is off there07:56
Admiral_Chicagoi know that is one thing that has been worked on07:56
gnomefreakit should be as simple as a option in rules during ./configure07:56
gnomefreakbut im not positive on that07:57
AlexLatchfordjust fired up OOo and it doesn't use text07:57
Admiral_Chicagoto be fair, we have to realize we are packaging from MF, it is really up to them07:57
AlexLatchfordmaybe this is a decision the TechBoard should take07:57
Admiral_Chicagothe best we can do is file upstream07:57
gnomefreakMF? and please dont say what i think you mean07:57
Admiral_ChicagoMozilla Foundation...07:57
gnomefreakoh ok good :)07:58
Admiral_Chicagohaha.07:58
dfarningthis it for meeting?07:58
gnomefreakbut again ITS A UBUNTU CHANGE afaik07:58
gnomefreaknot mozillas07:58
AlexLatchfordwell that change will never be included in Firefox default, but we can change it in Ubuntu Firefox07:58
Admiral_Chicagoreally? hmm, we may need to look at that07:59
gnomefreakwe had one more i think07:59
dfarningall ubuntu changes need mozilla approval07:59
dfarningto keep trademark07:59
AlexLatchfordgnomefreak: we have done everything on the list07:59
gnomefreakdfarning: its provided as a ./configure option i think07:59
gnomefreakAlexLatchford: ah ok goodie07:59
AlexLatchfordlol what do you have to say..07:59
dfarningok07:59
gnomefreakok anyone going through bugs please assign edgy retraces to me07:59
dfarningok08:00
AlexLatchfordokay08:00
gnomefreaki want to get them out asap08:00
AlexLatchfordWe have any news of Thunderbird-dbg08:00
gnomefreakand since i cant always be here that doesnt mean im not infront of pc08:00
gnomefreakdfarning: thats your department08:00
gnomefreakwhat email was i going to write? :(08:00
gnomefreakcouncil?08:00
dfarningAre we still missing the latest build -dbgsym08:01
Admiral_Chicagognomefreak: will do if i see any08:01
dfarningfor tb08:01
gnomefreakdfarning: we have no tb-dbg or dbgsym for edgy at all there is a dbg-sym for feisty i think08:01
AlexLatchforddfarning: I am running Feisty and there is no Thunderbird-dbg package08:01
dfarningill follow up with martin08:01
=== dfarning wonders what is going wrong
AlexLatchfordmaybe I am looking in the wrong place..08:02
gnomefreakmozilla-thunderbird-dbgsym in feisty08:02
gnomefreakAlexLatchford: add universe and multiverse restricted to pittis repo :)08:02
gnomefreakits in main08:03
=== coumbes [n=coumbes@pool-71-124-32-100.chi01.dsl-w.verizon.net] has joined #ubuntu-meeting
AlexLatchfordI need pitti's own repository?08:03
tonyyarussoWhat is dbgsym?08:03
gnomefreakfor the dbgsym you do08:03
AlexLatchfordgnomefreak: aha okay, this is probably why it is not showing08:03
gnomefreakthey are debugging symbols for packages08:03
tonyyarussoah08:03
gnomefreakAlexLatchford: its not dbg so you cant get backtrace with it08:03
dfarningthey are the debug symbols striped out of the executables08:04
AlexLatchfordhmm okay08:04
gnomefreakok are we done i need a smoke08:05
AlexLatchfordMeeting Closed I guess08:05
AlexLatchfordthanks guys08:05
gnomefreak:)08:05
gnomefreakty08:05
dfarningadjourn08:05
=== Admiral_Chicago [n=Admiral_@ubuntu/member/admiral-chicago] has left #ubuntu-meeting []
=== coumbes [n=coumbes@pool-71-124-32-100.chi01.dsl-w.verizon.net] has joined #ubuntu-meeting
=== sistpoty [n=sistpoty@ubuntu/member/sistpoty] has joined #ubuntu-meeting
=== btse [n=BTSE@c83-253-242-152.bredband.comhem.se] has joined #ubuntu-meeting
=== lfittl [n=lfittl@213.129.230.12] has joined #ubuntu-meeting
=== emonkey [n=emonkey@static-pro-212-101-27-121.adsl.solnet.ch] has joined #ubuntu-meeting
=== hoora_ [i=ariel@gateway/tor/x-8c30572e75c99b25] has joined #ubuntu-meeting
=== morty [n=morty@88-105-102-205.dynamic.dsl.as9105.com] has joined #ubuntu-meeting
=== rmjb [n=rmjb@cuscon17258.tstt.net.tt] has joined #ubuntu-meeting
=== dholbach [n=daniel@i59F70192.versanet.de] has joined #ubuntu-meeting
=== TheMuso [n=luke@ubuntu/member/themuso] has joined #ubuntu-meeting
=== peppe84 [n=peppe84@host5-47-dynamic.6-87-r.retail.telecomitalia.it] has joined #ubuntu-meeting
=== peppe84 [n=peppe84@host5-47-dynamic.6-87-r.retail.telecomitalia.it] has left #ubuntu-meeting ["Baciamo]
=== rmjb_ [n=rmjb@190.58.8.96] has joined #ubuntu-meeting
\shmoins08:59
ajmitchhi09:00
geserhi09:00
dholbachheya09:00
TheMusoHey all.09:00
siretarthey folks!09:00
lfittlhello everybody09:00
=== ..[topic/#ubuntu-meeting:Ubugtu] : Current meeting: MOTU meeting | Calendar: http://fridge.ubuntu.com/event | Logs: https://wiki.ubuntu.com/MeetingLogs/ | 07 Mar 12:00 UTC: Edubuntu | 08 Mar 16:00 UTC: Ubuntu Development Team | 11 Mar 10:00 UTC: LoCo Team | 12 Mar 18:00 UTC: Derivative Team
shawarmaHi!09:00
Lurehi09:01
Toadstoolheya!09:01
mortyHello09:01
dholbachOk, let's start off with the meeting09:01
dholbachFirst point on the agenda: "SRU Policy evaluation. How can we make it more efficient an worthwhile?"09:01
ajmitchMithrandir had some suggestions about that09:01
=== Mithrandir waves.
sistpotyhi09:02
dholbachsistpoty added some suggestions for that at https://wiki.ubuntu.com/MOTU/Meetings09:02
ajmitchwe have a lot of packages stuck in testing09:02
ajmitchhi Mithrandir :)09:02
sistpotyerm... I didn't add the suggestions :P09:02
sistpotyhowever I agree that we have many pacakges stuck in testing... I actually wanted to do some figure for the next sru-report, but the trend seems obvious already09:03
ajmitch"lots"09:03
dholbachhow many are those?09:03
sistpotydholbach: I don't have the figures yet...09:03
ajmitchsistpoty: since your last report, do you know of any being let into -updates?09:04
Mithrandirdholbach: enough that people try to sneak in bugfixes as backports instead of going through the SRU dance.09:04
sistpotyajmitch: at most one, but I don't remember exactly09:04
Mithrandirwhen people are trying to do that, it means doing the right thing (SRU) is harder than doing the wrong thing (backport)09:04
crimsunone thing that has bugged me about universe SRU is that ours is apparently more stringent than main's. Requiring 5 ACKs seems a bit far-flung.09:04
sistpotyyep09:05
sistpotydo I read the first proposal right, to skip -proposed entirely?09:05
Mithrandircrimsun: agreed, that seems a bit over the top.  Especially given that you won't ever see core packages such as X or the kernel in a universe update.09:05
crimsunI would not feel comfortable skipping release-proposed09:06
sistpoty(also there some really easy ones with trivial changes/or mere rebuilds)09:06
MithrandirI think the ideas added there was from some suggestions I threw out without really thinking them through last night, so they might be crackful.09:06
crimsunhowever, we should consider dropping the 5-ACK requirement09:06
dholbachOk, we have the following suggestions:     * Just have motu-sru ack then upload to -updates09:06
dholbach    * Go back to old policy where SRU didn't need approvals, just MOTU uploads. Perhaps still using -proposed for higher risk or high profile updates.09:06
dholbach    * Form testing team to get testing done faster. The current bottleneck seems to be mostly in getting testing.09:06
dholbach    * (ADDED) Reduce the number of ACKs.09:06
siretartcrimsun: like in requiring 2 or 3 ACKs or dropping it entirely?09:06
sistpotyhm... ideally I'd like to see every motu being able to upload directly to -proposed, and have the checking done only prior to -updates09:07
sistpotyhowever that comes with another problem:09:07
dholbachApart from reducing the number of ACKs, I think the testing team is a very good idea.09:07
Mithrandirthe idea of the first one was to have the current process, but upload to -updates and not -proposed and thereby have -updates be the testing and the safe area.  It means we can get fixes in quite a bit quicker, but also that enabling universe -updates might open you to lightly/not tested fixes.09:07
ajmitchsistpoty: I thought that's how it was meant to be now09:07
=== rmjb [n=rmjb@190.58.8.96] has joined #ubuntu-meeting
sistpotyajmitch: no, it's still going through -proposed first09:07
crimsundholbach: / siretart: dropping a 5-ACK requirement seems like a good idea if we get an SRU verification team (similar to main's) in place09:07
=== _MMA_ [n=mma@cpe-071-070-203-016.nc.res.rr.com] has joined #ubuntu-meeting
sistpotywell the other problem we have is that most of the updates are not done by motu's but rather by motu-hopefuls09:08
crimsunin essence, replacing the 5 ACKs with 109:08
Mithrandirremember that creating another team does not magically increase the amount of manpower available.09:08
ajmitchsistpoty: they have to be checked by 1 MOTU anyway then09:08
ajmitchespecially when you get the same people in 5 teams09:08
sistpotyajmitch: yep... currently that's motu-sru doing the checks09:09
sistpotyajmitch: however I'd also like to have *one* person responsible for an update, so that would probably suggest to transfer the responsibility to the motu sponsoring09:09
sistpoty(which could then as well be bad)09:09
ajmitchthat's what a sponsor should do anyway :)09:09
\shsistpoty: how many StableReleaseUpdates do we have daily/weekly/monthly?09:10
siretart\sh: enough. really..09:10
ajmitch\sh: and how many don't get done because of the long slow process?09:10
crimsunright. I propose we drop the 5-ACK requirement and just have the sponsoring MOTU check it.09:10
sistpoty\sh: currently I'd say ~2 per week, with 26 currently ongoing09:10
crimsun(we should be making this more lightweight instead of adding another team)09:10
ajmitchcrimsun: agreed09:10
=== siretart feels some general concent to crimsun's propsal
sistpoty\sh: however when we first introduced the policy, the numbers where far higher09:11
siretartconsent, even.09:11
ajmitchcrimsun: so make -proposed open for all uploads, and have 1 signoff before it gets pushed to -updates?09:11
Mithrandirgiven that universe is so lightly covered before release, I think we will always have a fairly high amount of SRUs done to fix critical bugs there, so we should just plan for that.09:11
dholbachwas the -proposed stage the bottleneck?09:12
Toadstoolajmitch: how do you determine whether it can be signed off or not? wait for someone to confirm there's no regression?09:12
crimsunajmitch: a step forward, yes. We should keep the minimum aging period, though.09:12
Mithrandirdholbach: many updates seem to get into -proposed, but never get uploaded to -proposed.09:12
sistpotydholbach: currently it is (or rather the testing phase there)09:12
ajmitchdholbach: it seems to be09:12
Mithrandiruh, never get uploaded to -updates09:12
crimsunToadstool: the minimum aging period combined with testing should alleviate that09:13
dholbachok, so making -proposed open for all uploads does not really help the problem, right?09:13
ajmitchToadstool: having at least 1 person testing is helpful09:13
ajmitchdholbach: depends if you still want motu-sru approving anything for -proposed09:13
sistpotyat which point would motu-sru then review the diffs? or not at all?09:13
\shsistpoty: thinking about manpower and time: how many packages are tested and checked from the sru team during one week? (also thinking, that this work is lost from the normal motu work)09:14
dholbachI think that having an initial check is a good thing09:14
sistpoty\sh: sru-team currently doesn't test updates, but only reviews the debdiffs09:14
sistpoty\sh: and this happens (apart from a few exceptions) very timely09:14
siretartsince we have enough members now, it seems.09:15
crimsunmotu-sru shouldn't block release-proposed IMO. Making fixes widely available via release-proposed ASAP seems like a good idea.09:15
=== AstralJava [n=jaska@cm-087-94-053-172.lohjanpuhelin.fi] has joined #ubuntu-meeting
sistpotyMithrandir: is it possible from a lp side to have uploads to -proposed pass through as is?09:15
sistpotycrimsun: I agree09:16
Mithrandirsistpoty: it'd require manual action from an archive team member, but doing that either when prodded or on archive days would be fine.09:16
\shsiretart: well, but checking the debdiffs, doesn't mean that the package is alright. And if there are no users who are actively testing, it won't get uploaded to -updates, right? so the workload of checking debdiffs is useless somehow, until there is at least one user who tells us: "Package works for me" , or did I misunderstood something? :)09:17
sistpotyok09:17
ajmitchafaik there are 3 archive days a week no, so that's no blocker09:17
sistpoty\sh: right. because of that we have the stage in -proposed09:17
sistpoty\sh: however checking the debdiffs is not useless actually ;)09:18
dholbachrequiring the sponsor to test and having a team of testers test it would help with that step, wouldn't it?09:18
sistpotysure, it would, but also lowering the number of acks needed would as well09:19
dholbachthat's what I meant: one sponsor ACK, one testing team ACK09:19
dholbachthat's just a proposal - you guys who work on the motu-sru team know better than I do, if it makes sense.09:20
sistpotyhow about the following: any motu can upload to -proposed. one member of sru needs to give green lights for -updates + 5 works for me within 5 days, 3 within 10 days and > 10 days needs another ack from motu-sru (to sort out simple stuff like rebuilds from tougher updates)?09:20
Toadstooldholbach: so motu-sru approval is not required anymore in your proposal?09:20
\shsistpoty: you know what I mean, checking the debdiff, but no one to test, the package will not leave -proposed, so the work is "vertane zeit" ( I don't know the english translation)09:20
crimsunOk, so how does this proposal sound?  1) Remove the pre-upload-to-proposed ACK requirement (make -proposed open to ubuntu-dev without motu-sru approval).  2) The sponsoring ubuntu-dev member is responsible for gathering testing with 2 ACKs, which must be documented on the LP bug and in the final -updates changelog.  3) The minimum aging period of 7 days in -proposed remains.  4) motu-sru goes away.09:21
sistpoty\sh: hehe, you mean because no update actually makes it, right? *g*09:21
\shsistpoty: yepp09:21
sistpoty\sh: sure09:21
dholbachToadstool: that's a different question :)09:21
Mithrandircrimsun: sounds fine with me.09:22
ajmitchcrimsun: I like it09:23
crimsunFrom my perspective in motu-sru, we've really only encountered a few true discussion-worthy ones. The remainders are trivial "oh, looks good, +1".09:23
siretartcrimsun: how many testers do have to confirm the fix with your proposal?09:23
Toadstoolcrimsun: looks good.09:23
dholbachcrimsun: I like it too.09:23
crimsunsiretart: two (including the ubuntu-dev sponsor and one tester)09:23
Mithrandirof course, people are allowed to ask for second opinions if they feel an update needs more review.09:23
crimsunMithrandir: precisely09:24
rmjbcan ubuntu-qa assist with testing?09:24
sistpotycrimsun: I generally like to see normal motu's more involved in sru's and take more responsibility there. sounds great for me09:24
dholbachrmjb: we could ask ubuntu-bugsquad@ for help with that09:24
crimsunanyone else have thoughts on the proposal given above, and/or can we "vote"?09:25
sistpotylet's vote09:25
ajmitch+1 for crimsun's proposal09:25
sistpoty+109:25
\shcrimsun +1 :)09:25
dholbach+1 too09:25
TheMuso+109:26
crimsun+109:26
Toadstool+109:26
ajmitchsounds like it's approved, what's next on the list? :)09:26
sistpotyhow do we do the transition for this policy?09:26
siretart+1 and +1 :)09:27
sistpotyunsubscribe motu-sru from all bugs and subscribing universe-sponsors for the ones which don't have a motu as assignee?09:27
ajmitchsistpoty: find everything with 2 ACKs & get it pushed to -updates09:27
dholbachWe need to document it and announce it to the public, especially to the TB.09:27
crimsunsistpoty: sounds good for starters09:27
Mithrandirajmitch: somebody needs to actually do the uploads, though.09:28
siretartcan we just remove the group 'motu-sru'?09:28
ajmitchexcellent one *less* team :)09:28
ajmitchMithrandir: ah true, they don't get manually shoved across, do they?09:28
crimsunsiretart: that sounds good09:28
sistpotywell, I'd like to see all SRU's from non-motus which have been sponsored by motu-sru being taken care for... then we can remove motu-sru ;)09:28
sistpotybut I guess I'll do some uploads to -updates after the meeting ;)09:29
Mithrandirajmitch: they need to be uploaded.09:29
dholbachNice. I'll update the Freeze Exception page and write an announcement.09:29
sistpotygreat dholbach09:29
sistpotyok, next item?09:29
dholbachjono asks: "From asking around, it seems the project needs help with (a) outreach and getting new people involved (b) getting people excited about MOTU and (c) defining some direction for the project. Is this a fair assessment?"09:30
=== ..[topic/#ubuntu-meeting:Ubugtu] : Current meeting: MOTU meeting | Calendar: http://fridge.ubuntu.com/event | Logs: https://wiki.ubuntu.com/MeetingLogs/ | 07 Mar 12:00 UTC: Edubuntu | 08 Mar 16:00 UTC: Ubuntu Development Team | 11 Mar 10:00 UTC: LoCo Team | 12 Mar 18:00 UTC: Derivative Team | 13 Mar 16:00 UTC: Forum Council
dholbachI'm not sure it's a good idea to discuss it in a meeting, since we could spend quite some time in here talking about the topic.09:30
=== welshbyte [n=welshbyt@ubuntu/member/welshbyte] has joined #ubuntu-meeting
dholbachWhat do you think about having some minutes of brainstorming as 'data collection' for another meeting or discussion on the mailing list?09:31
TheMusodholbach: I would have to agree.09:31
\shdholbach: I think a better question is: how are the other community driven projects solving this problems? mostly a hen and egg problem ;)09:31
=== comm[A|n] der [n=robert@drsd-4db35dc1.pool.einsundeins.de] has joined #ubuntu-meeting
crimsunI propose we migrate that discussion ubuntu-motu@ .09:31
dholbach\sh: It's definitely another question. :)09:31
sistpotyI guess it might make sense to have jono here to actually discuss it, but brainstorming sounds good09:31
crimsun+to09:31
siretartjust one small point here:09:31
siretartthis weekend, at chemnitzer linux tage, I had a talk about developer communities in ubuntu09:32
dholbachsiretart: nice - you have some slides up somewhere? :)09:32
siretartthe ppl were quite impressed about that we have so few developers for so many packages09:32
siretartand that ubuntu is such a young distro09:32
=== ajmitch still feels we're constantly stretched
dholbachI hope you all feel patted on the back.09:33
siretartdholbach: sure, get them at http://wiki.tauware.de/blog:clt2007 - directly: http://wiki.tauware.de/_media/blog:ubuntu_communities.odp?id=blog%3Aclt2007&cache=cache09:33
\shsiretart: regarding MOTU or complete ubuntu-dev?09:33
siretartgerman, though09:33
siretart\sh: both09:33
ajmitchdholbach: most of the thanks should probably go to debian, though09:33
=== rmjb would like to help... but is overwhelmed with all that is needed to be known
siretartkeep in mind it was a 30min talk, I couldn't go into details09:33
ajmitchrmjb: that's part of what we need to discuss - how to get people involved that can't spend several hours a day on it :)09:34
sistpotyrmjb: #ubuntu-motu is a good starting place ;)09:34
crimsunajmitch: (right, given the ratio of merge to syncs)09:34
siretarthowever, I really think we have way too few developers, espc. in universe land. I  don't have concrete ideas however how to fix this09:34
\shthe difference is: doing OSS work for a living, and get money for it, or just do it as a hobby...09:34
dholbachajmitch: MOTU is doing a very good job, but we're standing on the shoulders of giants. :-)09:34
siretartpersonal package archives could improve things. is there any news on this topic?09:35
ajmitchsiretart: we have quite a few developers, but most are inactive09:35
=== xerosis [n=kieran@87-194-21-125.bethere.co.uk] has joined #ubuntu-meeting
ajmitchwe talked recently about sending out a nice email to inactive motus inviting them to get involved again09:35
crimsuntesting for SRU in -proposed is a good way to get involved, too09:35
siretartajmitch: right. I'm talking about 'active' developers. but it's quite hard to define 'active' contributors.09:35
sistpotyyep... and we need to make more things clear on the mailing lists imho... so that casual hopefuls know what's going on even if they're not on irc09:35
=== ajmitch isn't particularly active
dholbachajmitch: gpocentek and I are working on that09:36
TheMusoOne thing I've noticed is that if one is out of the loop too long, it can take a while to catch up to the latest goings on.09:36
dholbachok let's start to mention problems and possible solutions as bullet points for 3-4 minutes - try not to get too deep into discussions09:36
TheMusoBecause things change so fast.09:36
Toadstooltrue09:36
sistpotyTheMuso: right09:36
ajmitchdholbach: great09:36
crimsunAs for one route to bring in hopefuls:  it would be nice to have instructions for setting up various release chroots to help with testing. I can work on that.09:36
sistpoty* motu-school sessions09:36
dholbach* activity on the mailing list09:37
ajmitch* finding a place to start working09:37
dholbach* more patting on the back09:37
=== bddebian [n=bdefrees@63.81.56.182] has joined #ubuntu-meeting
Toadstool(more hugs? :)09:37
dholbach* (a) outreach and getting new people involved09:37
dholbach*  (b) getting people excited about MOTU09:37
TheMusosistpoty: Thats the impression I've got a couple of times when I have been gone for a while in the past, and have come back to help out again, and found myself having to find out the latest happenings.09:37
dholbach;-)09:37
rmjbthere seem to be diff types of MOTU, mergers, bug fixsers, packagers, maybe different pages for these different types of tasks?09:37
\sh* spreading curiosity to the people / * why should I work on Ubuntu, and what are the benefits for me and my daily life09:38
rmjbat least to help hopefuls ease into tasks09:38
dholbach* better structured documentation09:38
\shI mean it serious...those questions I get here in my office..."why are you working on ubuntu, if you don't earn money with it"09:38
TheMusoCould the packaging guide possibly be improved?09:38
ajmitchTheMuso: if there's someone willing to improve it, sure09:39
dholbachmore (team work - not administrative) teams09:39
TheMusoI have never really looked at it myself, but people may be daunted by it.09:39
crimsunTheMuso: yes, and there's work on that09:39
=== comm[A|n] der [n=robert@drsd-4db35dc1.pool.einsundeins.de] has left #ubuntu-meeting []
rmjbthe packaging guide is good... the end could have some tips and tricks though09:39
sistpoty* monthly summary of all policy changes + todo list on the mailing list?09:39
=== PriceChild [n=pricechi@ubuntu/member/pricechild] has joined #ubuntu-meeting
Toadstoolsistpoty: that'd be great09:40
dholbach* more scheduled QA sessions09:40
crimsun(random thought: why don't we turn the packaging guide into a cookbook, ala the O'Reilly series?)09:40
xerosis* mentors to ease new people in09:40
bddebianWe have mentors09:40
sistpotyxerosis: we have mentors already... maybe that's in a too less prominent place on the wiki`09:41
sistpoty? even09:41
dholbachok, maybe let's close the list here - this should be a good start for more discussions among our team and with jono - let's move on.09:41
xerosisapologies09:41
siretartdholbach++09:41
TheMusoI think some MOTUs that don't currently mentor should consider doing it at some point.09:41
sistpotydholbach: +109:41
dholbachLet's have a look at our TODO lists.09:41
sistpoty(and I should stop mentoring, as I'm a particular bad mentor :P)09:41
dholbachsistpoty mentions "what's missing (php4-transition? what else)"09:41
dholbachxerosis: https://wiki.ubuntu.com/MOTU/Mentors09:42
sistpotydholbach: well, php4 is about to be removed... let me look at the mail back again09:42
dholbachhttps://wiki.ubuntu.com/MOTU/TODO09:42
dholbachdidn't we have a unmetdeps list somewhere?09:42
dholbachor somebody who agreed to file a bunch of bugs on it?09:42
\shphp4-transition to 20050606+lfs?09:42
dholbachIs somebody here who'd like to do that?09:43
\shI already uploaded many php4 packages to rebuild on latest php4 api change09:43
dholbach\sh: we're talking about removal09:43
\shdholbach: ah09:43
sistpotyhttps://lists.ubuntu.com/archives/ubuntu-motu/2007-February/001288.html09:43
tonyyarussocrimsun: (would it be able to cover everything that way?  Seems pretty good as is)09:43
crimsuntonyyarusso: offband to -motu, please09:43
dholbachWhat's missing on  https://wiki.ubuntu.com/MOTU/TODO ?09:44
dholbachIs somebody here who'd like to file a bunch of unmetdeps bugs?09:45
ajmitchresults of an archive rebuild (yet to come)09:45
=== ajmitch was going to, but hasn't yet
dholbachajmitch: do you know what's the status there?09:45
dholbachajmitch: (archive rebuild)09:45
ajmitchno idea about archive rebuild09:45
sistpotythere was some smaller thing as well iirc, but I cannot remember exactly what it was09:45
=== ajmitch could still do unmet deps bugs if you really wish
dholbachthat'd be nice09:46
sistpotyajmitch: that'd be great09:46
dholbachhttp://daniel.holba.ch/bzr/massfile/09:46
ajmitchyeah I have that checked out somewhere09:46
dholbach:)09:46
dholbachanything else we're missing on that list?09:46
dholbachdid anybody spend some time to tag bugs as 'bitesize' or 'packaging'?09:47
dholbachshould we call out a Universe HUG DAY or something?09:47
bddebianProbably a good idea09:47
sistpotydholbach: sure... was just about to mention that ;)09:47
dholbachrock09:47
dholbachwho does it? :)09:47
crimsundholbach: that would be a good idea, and it's an easy way to get people involved this week09:47
TheMusosorry guys, gotta run.09:47
ajmitchdholbach can distribute hugs09:47
=== TheMuso [n=luke@ubuntu/member/themuso] has left #ubuntu-meeting []
dholbachhehe :)09:48
sistpotyhehe09:48
dholbachok, ajmitch will file unmetdeps bugs, I'll try to find out what's up with the rebuilds09:48
dholbachwho'd join Universe HUG DAY to work through universe bugs?09:49
dholbachwho'd announce it?09:49
bddebianI would try to join (work has been brutal lately)09:49
crimsunI'm up for working on tagging universe bugs as bitesize/etc.09:49
sistpotyI'll try my best, but currently I need to cancel many tasks due to my thesis :(09:49
dholbachok, I'd join in as well09:50
dholbachfriday?09:50
crimsunFriday sounds good09:50
dholbachI can write the announce09:50
dholbachanything else for the TODO list?09:50
Toadstoolhmm, i'll try to join too09:50
sistpotyI guess everone should just add s.th. if he finds another thing, ok?09:50
dholbachok09:50
Toadstool(quite busy at work though)09:51
dholbachsiretart asks "What to do with broken packages we know about?"09:51
ajmitchdholbach: blog it on planet :)09:51
bddebiandholbach / siretart: Like?09:52
siretartwe had another example today: xserver-xgl:09:52
dholbach"there are packages, which we know that we won't be able to fix them before release. This includes e.g. unmet dependencies. Can we do better than leaving them in the release?"09:52
bddebianAhh09:52
Toadstooldholbach: remove'em from the archive? :)09:52
=== Toadstool hides
crimsunconcerning xserver-xgl: I'll look at it tonight, since I have access to hardware that would be affected09:53
siretartbddebian: xserver-xgl got broken by the xorg 7.2 upload to main, and the diff to current git head is way too big to review09:53
dholbachI don't think we should try to find a too easy solution to the problem in five minutes of a meeting.09:53
MithrandirToadstool: that is painful when we next time sync from Debian.09:53
siretartbddebian: other packages include packages with unmet deps09:53
ToadstoolMithrandir: yeah I know, just kidding09:53
Mithrandirwe've so far fixed unmetdeps in SRUs, which I think is sane enough.09:53
ajmitchcrimsun: thanks09:54
sistpotyyep... and sometimes contributors contribute fixes for sru's :)09:54
siretartI don't have any concrete proposal, I just find it sad that we release with so many broken package, and for many, we know that they are broken09:54
dholbachI'm not sure there's a general answer to the question.09:54
crimsunwe should really push to get those RC fixes from Debian in before feisty release09:54
siretartI compare with debian, where broken packages get removed before release. but that's not really applicable to ubuntu, I know09:55
Toadstoolif the amount of really broken packages stays reasonably low, we can take care of them with SRUs, right?09:55
sistpotyI guess we should try to remove packages that are broken which have been removed from debian some time ago09:55
crimsununmet deps can be resolved via SRU, so I'm not really worried. Perhaps we should start with known _regressions_ from edgy first.09:55
ajmitchsiretart: that's because they're removed from testing, but can be left in unstable09:55
Mithrandirsiretart: we don't have testing (as in the distribution)09:55
siretartajmitch: right09:55
Mithrandirwe could maybe remove the binaries..09:56
dholbachsistpoty: i think that happens regularly (debian-removed -> ubuntu-removed)09:56
siretartMithrandir: we don't have some other solution either09:56
siretartMithrandir: removing binaries sounds like a good idea to me!09:56
sistpotydholbach: iirc there are some left... maybe if they have ubuntu changes?09:56
dholbachsistpoty: dunno09:56
Mithrandirsiretart: it'll require binary NEW then, which is significantly less work than source NEW.09:56
Mithrandirsiretart: I'd need to discuss it with the archive team.09:56
ajmitchsiretart: btw about xserver-xgl - the majority of the debdiff is the nasty bundled mesa copy09:56
sistpotysiretart: removing the binary sounds like a good idea09:57
dholbachajmitch: that's info we need in the bug report :)09:57
ajmitchdholbach: it's already in the diffstat :)09:57
siretartMithrandir: I'd expect binary removals to happen really short before release. binary new shouldn't be too much of a problem at the beginning of the release cycle09:57
Mithrandirsiretart: uh, have you looked at NEW when we start syncing from Debian?09:58
siretartMithrandir: it's long, I assume :)09:58
siretartMithrandir: but do you really do an extensive NEW review for every NEW package from debian?09:58
dholbachso there's only the possibility to remove binary packages as a reasonable measure it seems.09:59
Mithrandirsiretart: I've done so so far at least, yes.  But as I said, binary NEW is a lot less work than source NEW.09:59
siretartI imagine09:59
Mithrandir(since it doesn't require checking all licences, just making sure the packages are somewhat sane)09:59
=== gbutler [n=gbutler@69-168-169-204.clvdoh.adelphia.net] has joined #ubuntu-meeting
sistpotyok, I guess we'll just wait for a resolution from ubuntu-archive on this one, right?10:00
dholbachright10:00
ajmitchok, so next meeting time?10:00
dholbachany other business?10:00
ajmitch:)10:00
sistpotyMithrandir: can you inform us of the result please?10:00
bddebianyeah, I need a raise ;-P10:00
Mithrandirsistpoty: yes.  Can you mail me reminding me to do so?10:00
sistpotyMithrandir: sure, or I'll just ping you :P10:01
dholbachok, no other business - how about in three weeks?10:01
ajmitchok, what time of day?10:01
dholbachso we keep on rolling with the MC meeting10:01
sistpotyerm... wasn't there some overlapping with TB meeting (or was that MC meeting)?10:01
crimsunafter 20:00 if in 3 weeks10:01
ajmitchsistpoty: with TB10:02
Mithrandirsistpoty: sure, that's fine.  It's just that it's 22:00 here now and I was planning on heading to bed soonish, not work. :-)10:02
crimsunbecause TB is at 20:00 in 3 weeks10:02
ajmitchMithrandir: I'll poke you about f-spot uvf tomorrow then :)10:02
Mithrandirajmitch: sure10:02
dholbachlet's do it before TB then10:02
dholbach:)10:02
crimsun18:00?10:02
ajmitchdholbach: or +- 12 hours10:02
dholbachsounds good to me10:02
ajmitchto allow people in australia to make it to the meeting10:03
sistpotyajmitch: yep, rotating seems like a fair thing to do10:03
sistpoty8.00 UTC?10:03
dholbachfine with me too10:03
ajmitchsounds fair10:04
sistpoty+1 here as well10:04
sistpoty<-- needs to get up really early then :P10:04
Toadstoollate meeting but fair :) +110:04
ajmitchsistpoty: you'll live :)10:04
sistpotyhrhr10:04
bddebianheh10:04
dholbachWFM10:04
dholbachwho writes the announce?10:05
sistpotyhm... WFM always reminds me of WTF *g*10:05
sistpotyI can do it10:05
dholbachok, excellent10:05
sistpotybtw.: is anyone doing the minutes?10:05
dholbachthanks everbody for showing up to the meeting :)10:05
ajmitchthanks10:06
bddebianThanks.  Sorry I'm not as "involved" lately :'-(10:06
crimsunsistpoty: I started but got volunteered for another meeting here. Can you do them?10:07
=== LaserJock [n=mantha@ubuntu/member/laserjock] has joined #ubuntu-meeting
sistpotycrimsun: ok, will do10:07
crimsunthank10:07
crimsun+s10:07
LaserJocksorry guys, really late10:07
dholbachyou ROCK10:07
sistpotybddebian? you *not* involved? then I'm completely away from the project :P10:07
bddebianpfft :-)10:08
bddebianLaserJock: Just in time ;-P10:08
LaserJockall over?10:09
Toadstoolyep10:09
ajmitchLaserJock: yep, just finished10:09
=== dfarning [n=dfarning@69-179-3-108.dyn.centurytel.net] has joined #ubuntu-meeting
ajmitchsistpoty: don't worry, I'm not even remotely in touch with the project :)10:09
sistpotyhaha10:10
LaserJock:(10:10
=== bddebian pokes ajmitch
LaserJockI didn't get volunteered for anything did I?10:10
ajmitchbddebian: yes?10:10
ajmitchLaserJock: only a little bit10:10
sistpotywohoo I don't need to do motu-sru reports any longer :)10:11
Toadstoolheh10:11
bddebianajmitch: Just for fun, sorry :-)10:11
LaserJocksistpoty: what's the new policy?10:11
ajmitch09:21 < crimsun> Ok, so how does this proposal sound?  1) Remove the pre-upload-to-proposed ACK requirement (make -proposed open to ubuntu-dev without10:12
ajmitch                 motu-sru approval).  2) The sponsoring ubuntu-dev member is responsible for gathering testing with 2 ACKs, which must be documented on the10:12
ajmitch                 LP bug and in the final -updates changelog.  3) The minimum aging period of 7 days in -proposed remains.  4) motu-sru goes away.10:12
ajmitchbah, that pasted *really* badly10:12
=== ajmitch blames putty
sistpotypoor ajmitch10:13
sistpoty;)10:13
ajmitchstuck in windows at work10:13
crimsunsistpoty: yes, that was the nefarious plan =)10:13
bddebianPuTTY r0x j0010:13
Toadstooluh10:13
=== phanatic [n=phanatic@ubuntu/member/phanatic] has joined #ubuntu-meeting
=== Hobbsee [n=Hobbsee@ubuntu/member/hobbsee] has joined #ubuntu-meeting
=== _MMA_ [n=mma@cpe-071-070-203-016.nc.res.rr.com] has left #ubuntu-meeting []
=== cbx33 [n=pete@ubuntu/member/cbx33] has joined #ubuntu-meeting
=== xerosis [n=kieran@87-194-21-125.bethere.co.uk] has left #ubuntu-meeting ["Konversation]
=== Burgwork [n=corey@ubuntu/member/burgundavia] has joined #ubuntu-meeting
=== hjmf [n=hjmf@140.Red-217-125-227.dynamicIP.rima-tde.net] has joined #ubuntu-meeting
=== nounours [n=cesare@host149-214-dynamic.2-79-r.retail.telecomitalia.it] has joined #ubuntu-meeting
=== welshbyte [n=welshbyt@ubuntu/member/welshbyte] has left #ubuntu-meeting []
=== nounours [n=cesare@host149-214-dynamic.2-79-r.retail.telecomitalia.it] has left #ubuntu-meeting ["Ex-Chat"]
=== LaserJock [n=mantha@ubuntu/member/laserjock] has left #ubuntu-meeting []
=== j_ack [n=rudi@p508DC141.dip0.t-ipconnect.de] has joined #ubuntu-meeting
=== Whatsisname [n=whatsisn@c-75-72-177-215.hsd1.mn.comcast.net] has joined #ubuntu-meeting
=== bddebian [n=bdefrees@63.81.56.182] has left #ubuntu-meeting ["Leaving"]
=== SportChick [n=essy@about/essy/stouterik/pdpc.base.essy] has joined #ubuntu-meeting
=== popey [n=alan@ubuntu/member/popey] has left #ubuntu-meeting []
=== Lure_ [n=lure@clj46-234.dial-up.arnes.si] has joined #ubuntu-meeting
=== Lure [n=lure@clj46-234.dial-up.arnes.si] has joined #ubuntu-meeting
=== ..[topic/#ubuntu-meeting:Ubugtu] : Calendar: http://fridge.ubuntu.com/event | Logs: https://wiki.ubuntu.com/MeetingLogs/ | 07 Mar 12:00 UTC: Edubuntu | 08 Mar 16:00 UTC: Ubuntu Development Team | 11 Mar 10:00 UTC: LoCo Team | 12 Mar 18:00 UTC: Derivative Team | 13 Mar 16:00 UTC: Forum Council | 13 Mar 20:00 UTC: Technical Board
=== sistpoty [n=sistpoty@ubuntu/member/sistpoty] has left #ubuntu-meeting []
=== bordy [n=bordy@153-161.127-70.tampabay.res.rr.com] has joined #ubuntu-meeting
=== lengau [n=lengau@c-68-53-53-39.hsd1.tn.comcast.net] has joined #ubuntu-meeting
=== Jozo-_ [i=jozo@viola.uninea.fi] has joined #ubuntu-meeting
=== bordy is now known as bordy_away
=== peppe84 [n=peppe84@host5-47-dynamic.6-87-r.retail.telecomitalia.it] has joined #ubuntu-meeting
=== daviey [n=dave1111@unaffiliated/daviey] has joined #ubuntu-meeting
daviey@schedule london'11:53
daviey@schedule london11:53
UbugtuSchedule for Europe/London: 07 Mar 12:00: Edubuntu | 08 Mar 16:00: Ubuntu Development Team | 11 Mar 10:00: LoCo Team | 12 Mar 18:00: Derivative Team | 13 Mar 16:00: Forum Council | 13 Mar 20:00: Technical Board11:53
=== imbrandon [n=brandon@ubuntu/member/pdpc.active.imbrandon] has joined #ubuntu-meeting
=== ScottK [n=ScottK@static-72-81-252-22.bltmmd.fios.verizon.net] has left #ubuntu-meeting ["Konversation]
=== peppe84 [n=peppe84@host5-47-dynamic.6-87-r.retail.telecomitalia.it] has joined #ubuntu-meeting
=== peppe84 [n=peppe84@host5-47-dynamic.6-87-r.retail.telecomitalia.it] has left #ubuntu-meeting ["Baciamo]
=== phanatic [n=phanatic@ubuntu/member/phanatic] has joined #ubuntu-meeting
=== lbm [n=lbm@0x555373ab.adsl.cybercity.dk] has joined #ubuntu-meeting

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