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

=== Moot2 is now known as MootBot
=== asac_ is now known as asac
=== RoAk is now known as RoAkSoAx
HobbseeSeveas: <#04:38
HobbseeSeveas: <304:38
Hobbsee(@ kmos)04:38
=== aRyn_ is now known as aRyn
=== Mamarok_ is now known as Mamarok
=== hassanibraheem_ is now known as hassanibraheem
=== mdz_ is now known as mdz
=== ogra_ is now known as ogra
=== ember_ is now known as ember
=== persia_ is now known as persia
Syntux@schedule Amman18:33
ubottuSyntux: Schedule for Asia/Amman: Current meeting: Bugs for Hugs Day | 04 Jun 00:00: Community Council | 04 Jun 09:00: Platform Team | 04 Jun 19:00: LoCo Council | 05 Jun 00:00:  Server Team | 05 Jun 01:00: Kubuntu Team18:33
lukehasnoname@schedule cdt19:13
ubottulukehasnoname: Error: Unknown timezone: cdt - Full list: http://jussi01.com/web/timezones.html19:13
lukehasnoname@schedule cst19:13
ubottulukehasnoname: Error: Unknown timezone: cst - Full list: http://jussi01.com/web/timezones.html19:13
lukehasnoname@schedule Houston19:13
ubottulukehasnoname: Error: Unknown timezone: Houston - Full list: http://jussi01.com/web/timezones.html19:13
lukehasnoname@schedule CST19:13
ubottulukehasnoname: Error: Unknown timezone: CST - Full list: http://jussi01.com/web/timezones.html19:14
slangasek@schedule Chicago19:14
ubottuslangasek: Schedule for America/Chicago: Current meeting: Bugs for Hugs Day | 03 Jun 16:00: Community Council | 04 Jun 01:00: Platform Team | 04 Jun 11:00: LoCo Council | 04 Jun 16:00:  Server Team | 04 Jun 17:00: Kubuntu Team19:14
slangasekthere ;)19:14
lukehasnoname;_;19:14
lukehasnonamethat was my next try19:15
slangaseknow, where are the GNOME people when I need to told-you-so them about Americans not commonly referring to their timezones by city name...19:15
lukehasnoname@schedule GMT-619:19
ubottulukehasnoname: Error: Unknown timezone: GMT-6 - Full list: http://jussi01.com/web/timezones.html19:19
lukehasnonamehahaha19:19
Syntux@schedule Mars19:20
ubottuSyntux: Error: Unknown timezone: Mars - Full list: http://jussi01.com/web/timezones.html19:21
lukehasnonameHow are things in Jordan19:26
Syntuxlukehasnoname, dandy19:30
Syntuxlukehasnoname, ever been there?19:31
lukehasnonamenot at all19:31
lukehasnonameI've never been more than 1200 miles from home19:32
lukehasnonamewhich means I've never been out of Texas :)19:32
Syntuxheh19:32
lukehasnonamehaha, no I've been to tennessee and Colorado and everywhere between and south, if you know the U.S.19:32
Syntuxlukehasnoname, yeah, aware of states names, my brother been there for long time.19:33
lukehasnonamesyntux: Is Jordan peaceful compared to the rest of the region?19:34
Syntuxlukehasnoname, depends how you look at the region, anyway I guess we should take this into PM or #Ubuntu-offtopic19:35
Seeker`@schedule19:47
ubottuSeeker`: Schedule for Etc/UTC: Current meeting: Bugs for Hugs Day | 03 Jun 21:00: Community Council | 04 Jun 06:00: Platform Team | 04 Jun 16:00: LoCo Council | 04 Jun 21:00:  Server Team | 04 Jun 22:00: Kubuntu Team19:47
=== gnomefre1k is now known as gnomefreak
mdzgood evening20:00
tkamppeterhi20:00
Keybukevening20:00
mdz#startmeeting20:01
mdzMootBot: poke20:01
jdstrandhi20:01
Keybukmdz: wasn't MootBot one of Dennis's?20:01
pittihi20:01
mdzKeybuk: I haven't tried to use it in a while, but was sure it was rescued20:01
pittihi20:01
mdzit doesn't seem to be responding. oh, well.20:02
zulhello20:02
mdz[TOPIC] core developer application from Till Kamppeter20:02
mdz[LINK] https://lists.ubuntu.com/archives/motu-council/2008-May/001100.html20:03
KeybukI really only have one question for tkamppeter20:04
mdzthere looks to have been some controversy in the thread leading up to this application being submitted20:04
Keybukand it's entirely unrelated to his core-dev application20:04
mdzI hope it isn't "why doesn't my printer work?"20:05
\shevening20:06
Keybukmdz: yes, it pretty much is ;)20:06
tkamppeterKeybuk, are we still waiting for someone?20:06
\shKeybuk, don't buy dell..buy real hardware ,-)20:06
pittiTill is the prime example for a "specialist" developer; I hardly look at the debdiffs of system-config-printer or foomatic etc. any more, but I would carefully check a gnome-panel or udev upload from him20:06
Keybukmore "hawlp! my printer doesn't work! what can I do to help you fix it?" :)20:06
mdztkamppeter: can you tell us about the concerns which were raised on the list with regard to the Brother driver packages?20:06
mdztkamppeter: no, not waiting, we're just a bit slow tonight20:07
mdzKeybuk and I represent a quorum20:07
tkamppeterIt was that I have uploaded the packages with some quirks in them, like a world-writable directory. I have hurried somewhat to get them in before FF and assuming that there are still 6 weeks in which the very motivated contributors could polish them.20:08
pitti(please note that this was merely uploaded to NEW, and rejected there; they never actually landed in the archive)20:09
mdzpitti: tkamppeter mentioned that you had reviewed these packages as well, and approved of their upload. any comment?20:09
Keybuktkamppeter: had you taken any steps to motivate the contributors?20:09
Keybukor at least alert them to the problems?20:09
pittiit was partly my fault20:09
pittiin an effort to process the 23948239432 NEW packages before FF more efficiently, I asked people to just upload, and I'd review them directly in NEW20:09
tkamppeterKeybuk, I have forwarded everything which pitti told me about which was wrong to them and I got improved packages a day later or so.20:10
pittiinstead of getting them reviewed somewhere else by MOTU first20:10
pittimdz: i. e. I said "please upload to NEW, I'll review them", instead of "I review them from <someurl>, then we fix it, then upload" (the standard procedure)20:10
mdztkamppeter: were you aware of any of those problems before pitti reviewed the package?20:10
mdzsome of them seemed like basic packaging errors20:11
tkamppeterThe upstream quality of these packages was very bad. They had to do a lot of hacking to get them into a distro-installable form. I have checked the structure and whether they install smoothly on my box and whether they build under pbuilder, but I have really overlooked that there was a world-writable dir in them.20:12
mdztkamppeter: doesn't lintian check that?20:12
mdznon-standard-dir-perm I think20:13
tkamppeterProbably I have not tried it to drive to complete lintian-cleaniness but looked only on whether it installs and runs.20:14
mdztkamppeter: did you run lintian on the package?20:14
tkamppeterI really must look into the thread again about what exactly I have done and what I have asked the contributor to fix in which stage.20:15
Seeker`sorry bout the lack of mootbot20:17
Seeker`there have been big hosting porblems, and it doesn't seem to be working properly on its current host20:17
mdzSeeker`: sorry to hear it; please email me if there is something I can do to help20:18
Keybuktkamppeter: I have a scenario for you.20:18
KeybukIt's after Intrepid Beta release, and you're getting a lot of bug reports about printers not working.  One of the bug reports has a patch to HAL that people are enthusiastically reporting fixes it for them, and this is getting wide publicity on forums and blogs.20:18
KeybukWhat's your next step?20:18
\shtkamppeter, any reasoning to not follow the motu rules for contributed packages from non-motus? I'm curious why you didn't send them to revu/motu with their packages, despite the fact, that motus could upload NEW packages without being reviewed when they were build from themselves20:18
Seeker`mdz: sadly, most people wont touch eggdrop. I'll try and get it fixed this evening20:19
pittithat has been discussed on the ML already: FF churn20:19
mdzpitti: the feedback of yours linked from the council's recommendation seems to pertain specifically to the comments on the brother package.  do you have more general comments as a sponsor other than what you already said about specialization?20:19
tkamppeter\sh, pitti has told me to directly upload into NEW, due to the FF. If no one has invited me to do so I had taken the standard procedure-20:19
pittimdz: My feeling is that tkamppeter understands the freeze rules now, and I trust him enough to upload the printer specific packages (like system-config-printer, cups, foomatic, etc.); he's still not a 100% proficient packager, but a great printing package maintainer and upstream developer20:21
pittiof course I understand that right now we still don't have this DM-like concept in Ubuntu20:21
tkamppeterKeybuk, I would try out the package by myself and run it to see whether it improves the situation and does not break anything (as longs as feasable on my box). I would also check through the changes to see whether there is something broken, or whether an extra library (= new dependency) is needed ...20:22
pittitkamppeter: what's your answer to Keybuk's scenario?20:22
Keybuktkamppeter: ok, so your testing does indeed show that printing works again with the patch, and doesn't introduce any new dependencies20:23
Keybukwhat's next?20:23
tkamppeterI would also try a build with pbuilder if the patch is non-trivial, to catch an FTBFS due to a new dep.20:23
pittitkamppeter: just assume that the package builds, and works now20:23
tkamppeterIf the patch is not very small I would try a lintian to see whether nothing in the package structure broke (or thingslike world-writale dir)20:24
Keybuktkamppeter: builds fine, lintian shows no new problems20:24
tkamppeterIf there is enough time and if other users are participating in the bug discussion I would upload the files onto my server (or PPA) and invite the others to test.20:25
Keybuktkamppeter: you get a number of thanks from the reporters, and they say it fixes it20:25
tkamppeter(All assumiung that I do not have the printer in question) Then I would have enough confidence to upload it: Package actually improves situation for owners of the hardware in question, package is lintian-OK, package does not FTBFS, then I would sign and upload it.20:27
tkamppeterSmaller issued are then hopefully found by the wide Intrepid testing community.20:28
pittitkamppeter: how much do you actually know about the guts of hal?20:28
tkamppeterOnly more basic stuff, I have done some simple changes in hal-cups-utils, including making it actually working on Ubuntu. I have read through HAL docs for that.20:29
Keybukthere are many patches in Launchpad which appear to fix the problem20:31
Keybukbut are in fact, somewhat wrong20:31
Keybukthey may break something else you weren't testing20:31
pittiand create a huge security  hole, or are fundamentally wrong20:31
Keybukor they may be deliberate decisions by upstream or by the person in Ubuntu who cares a lot about that20:31
Keybukespecially if you don't know much about the package in question, it's often an idea to talk to other people first20:32
Keybukbefore applying a patch to HAL, even I generally check with pitti20:32
Keybukif he's not around, others like cjwatson, slangasek or myself may be able to spot the problem you're about to introduce20:32
pittiand patches should generally be sent to upstream; after FF they should even be discussed with upstream *before* applying them (unless it's really obvious, like fixing a NULL deref, or so)20:33
tkamppeterI am also generally trying to get patches upstream, I akso dislike that the distros deviate too much from upstream as this creates a maintenance nightmare and also a lot of mail about non-upstream problems in upstream forums.20:34
mdztkamppeter: if a mechanism were available for you to gain upload privileges for specific packages, rather than all of main (as ubuntu-core-dev currently implies), would you have opted for that rather than ubuntu-core-dev?20:34
mdztkamppeter: or are you interested in participating more generally in development?20:35
tkamppeterFor the Common Printing Dialog for example I have informed the relevant upstreams and let my GSoC student make work together with them-20:35
Seeker`#startmeeting20:35
MootBotMeeting started at 14:37. The chair is Seeker`.20:35
MootBotCommands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]20:35
Seeker`#endmeeting20:35
MootBotMeeting finished at 14:37.20:35
mdzSeeker`: thanks20:36
Seeker`the logs wont be available immediately, but hopefully in the next 24 hours or so20:36
tkamppetermdz, this mechanism would be enough for me. My plans are simply to continue in the printing area. And on non-printing packages like HAL or so, I would only upload small trivial patches, never a big thing, and I usually ask here on IRC if I am in doubt with a method or idea to get something solved.20:37
mdzI am told that Launchpad will provide such a mechanism in the foreseeable future20:38
mdzand so I would like to propose the option of applying for core-dev with a commitment to limit uploads to a named set of packages20:39
mdzto be transitioned to that new access control mechanism when it becomes available20:39
sirderigohola20:39
mdzKeybuk: would you be willing to consider that?20:39
mdziirc we did something similar for rtg20:39
tkamppetermdz, so I agree with that. Can we simply say that the TB agrees on that with me and activate this state as soon as the Launchpad is ready?20:40
Keybukmdz: as in, grant core-dev privileges until such time as we can make better lists?20:41
mdzKeybuk: privileges with a social limitation20:41
Keybukthat was my feeling of the right course20:41
mdzuntil that social limitation can become a technical one20:41
Keybuktkamppeter: would you be happy limiting yourself to printing packages, and where there are patches to things like HAL, still working with others like pitti to have them upload them?20:42
tkamppetermdz, I will upload only printing stuff directly, for other things I will ask others whether it is OK before uploading.20:42
mdztkamppeter: we will need a list of packages20:43
mdztkamppeter: could you prepare such a list and email it to technical-board? then we can process your application by email20:43
pittithe hardy ones on https://edge.launchpad.net/~till-kamppeter/+packages seem like a good start20:44
mdztkamppeter: you don't need to do it right now; we can take this offline20:45
mdztkamppeter: are you there?20:46
tkamppeterYes, I am here, mail sent.20:47
mdztkamppeter: OK, we will move on with the meeting and then review the package list20:47
tkamppeterOK.20:48
mdztkamppeter: thanks for talking with us20:48
mdzjdstrand: still here?20:48
jdstrandmdz: yep20:48
mdz[TOPIC] Ubuntu core developer application from Jamie Strandboge20:48
mdz[LINK] https://lists.ubuntu.com/archives/motu-council/2008-May/001101.html20:48
mdzkees: are you here?  you've presumably sponsored more of Jamie's packages than anyone20:49
keeshi!20:50
keesI'm a huge super-supporter of jamie's work20:50
Seeker`mdz: You need to do #startmeeting20:50
mdzsoren,zul: are you here?20:51
sorenI am indeed.20:51
keeshe's been doing extensive uploads to -security for a while now, and I have no reservations at all about his abilities.  any time an update is assigned to him, I know it's getting done very well.20:51
mdzSeeker`: I figured an incomplete log would be confusing, and that I should just publish my own copy20:51
Seeker`fair enough :)20:51
sorenI can vouch 100% for Jamie. I have no reservations at all granting him core-dev privileges.20:52
zulmdz: I am I have uploaded a couple of Jamie's packages and I have quite happy about his work. I support him 100%20:52
mdzsoren: what sort of work of his have you reviewed (presumably non-security-related)?20:52
sorenHe's careful and has a keen sense of detail, and most certainly has the techincal skill required.20:52
mdzjdstrand: I'm pretty familiar with your extensive work on security updates, but am curious about what you've done with more general packaging, since there's a different set of issues there20:53
sorenmdz: Hm... All sorts of things really. I can't remember sponsoring a whole lot of uploads for him, but we routinely discuss packaging issues and other techincal stuff.20:53
keesI've sponsored uploads of ufw.  while it's not really part of larger existing subsystems yet, it's packaging, I think, is quite good.20:54
Keybuk"quite good" ? :-)20:54
jdstrandmdz: wrt Ubuntu, I work on ufw, auth-client-config and migrating apparmor profiles to packages. Some of the issues involved with apparmor can be seen in the wiki docoument: https://wiki.ubuntu.com/ApparmorProfileMigration20:54
Keybukas mdz so wryly observed in Prague, that's British for "OMFG! STAY AWAY!" :p20:55
keesKeybuk: ah, oops.  I'm en_US20:55
keesI mean it at face value.  :)20:55
keesit's good, but not complex, packaging, is perhaps what I mean.20:56
jdstrandmdz: I am a big believer in Debian Policy, and while I don't have it memorized, I consult it frequently when packaging20:56
mdzjdstrand: you created that document, right?  very nice20:56
sorenFor one thing, he has demonstrated knowledge of many of the not-quite-obvious details of Debian packaging, but more importantly he's never been afraid to ask, and seems to never have to ask the same question twice.20:56
jdstrandand if I have a question or idea, I am not hesitant to ask20:56
jdstrandmdz: I did-- thank you :)20:56
pittiI reviewed auth-client-config back then for MIR, and didn't find packaging issues20:56
mdzsoren: do you have any examples of not-quite-obvious details in mind?20:56
mathiazI'd like to add that I've worked with jdstrand on Apparmor profile upgrades for hardy - that involved some in-depth discussion about postinst upgrades. This works highlitghts the strength of jdstrand general packaging skill IMO.20:57
mdzpitti: thanks for your feedback.  what sort of package features were used in it?20:57
pittimdz: nothing really exciting; standard debhelper and control; pretty much the package you apt-get source, look at, and understand instantly :)20:58
sorenmdz: I remember discussing maintainer scripts with Jamie on a few occasions, and have been positively surprised at his understanding of them. That seems to be a common stumbling point for lots of people.20:58
pitti(which is, well, good?)20:58
mdzit's basically debconfiscations + supporting bits, right?20:58
pittiauth-client-config uses nothing like that (maintscripts, debconf, etc.)20:58
pittigreat ++ for running tests during build, and having tests at all20:59
mdzpitti: odd, it depends on debconf20:59
zulI think it also worth mentioning that jdstrand does alot of work on ubuntu-qa regression testing20:59
pittiah, heh21:00
mdzKeybuk: any questions for jdstrand?21:00
Keybukmdz: none, everything's covered21:01
mdzok, that's plenty of feedback for me.  calling for votes then21:01
Keybuk+121:01
mdz+1, loads of positive sponsor feedback and a strong track record of good quality work21:01
mdzjdstrand: congratulations and welcome21:02
jdstrand\o/21:02
soren\o/21:02
kees\o/ congratz jdstrand !21:02
mdzone less thing for kees to do, I hope ;-)21:02
jdstrandmdz, Keybuk: thank you :)21:02
zulyay!21:02
mdzany other business for the meeting?  we haven't had one in a while, and I'm a bit behind on email21:02
jdstrandkees, soren, mathiaz, zul: thanks for your support and great feedback all along :)21:02
mdzso if there are any pressing issues which I've overlooked, please raise them now21:03
jdstrandpitti: oh and that goes for you too! :)21:03
mathiazjdstrand: congratzzzz ! you deserve it :)21:03
Keybukmdz: meeting time!21:03
sorenjdstrand: You're welcome. Just keep doing what you're doing :)21:03
pittijdstrand: thanks to your good work! welcome to core-dev21:03
mdzKeybuk: indeed21:03
mdzKeybuk: do you have a proposal in mind?21:03
Keybukmdz: I propose 1400 UTC21:04
Keybukon tuesday21:04
mdzdifficult for the UTC-7 crowd21:05
Keybuktruer21:05
mdzbut I'm a fan of handling more things by email anyway21:05
mdze.g. pitti's micro version request recently21:05
Keybukbut both of our calendars have the "Californian Morning" pretty solid :p21:05
Keybukand I don't think it would be bad to actually make the meeting time more flexible21:06
Keybuke.g. one week we could opt to hold it later, or earlier21:06
mdzkees: you're representing the west side...do you think it would be seen as unfortunate if the meeting moved earlier?21:06
keesthis meeting?21:06
mdzkees: yes, the bi-weekly TB meeting21:06
mathiazmdz: FYI, the ubuntu server team considers moving its meeting to tuesday 15:00 UTC21:06
mdznot something which anyone from your time zone is required to attend, but something we want to keep open to participation21:07
keesthat'd be 7am21:07
keesI don't think that's unreasonable.21:07
slangaseks/Californian/Oregon/, yo ;P21:07
keesprops++21:07
mdzand as Keybuk says, if someone wants to ensure that they can be here to discuss something with us, we can always adjust the time for a particular meeting21:07
keesyeah, it's not like it's 3am or anything.  7am is reasonable if some needs to discuss something live21:08
mdzif there are no objections, I'm fine with changing it, and if anyone shouts, we can discuss it further by email21:08
mdzforgiveness vs. permission and all that21:08
mdzok, 1400 UTC it is21:08
mdzI'll notify ubuntu-devel-announce, ubuntu-news-team, etc.21:08
mdzok, thanks everyone for participating21:09
mdzadjourned21:09
lukehasnonameCanonical should have an America regional office in Houston21:10
Keybuklukehasnoname: it's in Lexington21:11
lukehasnonameKENTUCKY?21:11
nixternalMassachusetts21:11
lukehasnonamethe state has a total population of 'hick'21:11
lukehasnonameoh21:11
lukehasnonamehaha21:11
lukehasnonamecouldn't stray too far from the pond, I guess21:11
lukehasnoname:)21:11
=== ubuntu-l1ptop is now known as ubuntu-laptop
=== gnomefre1k is now known as gnomefreak
=== ubottu changed the topic of #ubuntu-meeting to: Current meeting: Community Council | Calendar: http://fridge.ubuntu.com/event | Logs: https://wiki.ubuntu.com/MeetingLogs/ | 04 Jun 06:00 UTC: Platform Team | 04 Jun 16:00 UTC: LoCo Council | 04 Jun 21:00 UTC: Server Team | 04 Jun 22:00 UTC: Kubuntu Team
=== ubuntu-laptop is now known as gnomefreak
JanC@schedule Brussels22:03
ubottuJanC: Schedule for Europe/Brussels: Current meeting: Community Council | 04 Jun 08:00: Platform Team | 04 Jun 18:00: LoCo Council | 04 Jun 23:00:  Server Team | 05 Jun 00:00: Kubuntu Team22:03
=== emma is now known as emma_
lukehasnonamehm22:11
ompaulSeveas, who should be running this one?22:14
Seveasompaul, hm?22:14
Seveas(just arrived home)22:15
ompaulahh cc meeting should be in progress afik but ain't22:15
JanCaccording to the Fridge calendar & ubottu there is a meeting going on for 15 minutes now  ツ22:15
Burgundaviayes, it is just about to start22:16
mdkeevening, sorry I'm late22:16
BurgundaviaMikeB said his meeting is running later than he expected22:16
Burgundaviaso we need elmo, sabdfl and dholbach22:16
=== emma_ is now known as emma
mdkeBurgundavia: difficult for us to have a meeting with just us two. How late is MikeB?22:22
Burgundaviahe pinged me on gmail chat about 20 minutes and said it would be later than even his email said22:23
Burgundaviayou were almost alone. The weather prevented me from flying today22:23
mdkei had a pretty late one at work, just arrived22:23
mdkedo you know if the local team item was discussed at the last meeting? I believe it has been on the agenda at least since then22:24
ompaulmdke, they are up and running and handling memberships22:25
mdkeompaul: that's not the item I mean... i mean the agenda item22:26
mdke"LoCo teams as legal entities?"22:26
=== emma is now known as emmy
=== emmy is now known as emma_
sbcmdke: That was discussed last time.22:29
=== emma_ is now known as emmy
mdkesbc: thanks, I'll have to check the logs then22:30
Seveasme too22:30
sbcmdke: We (the danish team) hope to show up at a comming meeting with a proposal for the CC, but we are not ready yet.22:31
=== emmy is now known as emma_
mdkesbc: ok22:33
sbchopefully for next meeting.22:33
mdkesbc: I'll take the agenda item off for now then22:33
sbcmdke: Feel free to do so. For the record, who is supposed to clear the agenda after a meeting?22:37
=== emma_ is now known as emma
mdkesbc: we don't have a fixed rule22:38
mdkeBurgundavia: I suggest we postpone the meeting. I don't have much time left now22:38
sbcok - so I shouldn't feel bad? There is no tradition that it is the person who puts a item up there who is supposed to remove it again?22:38
mdkesbc: no, no problem22:39
sbcok :)22:39
Burgundaviayep22:40
mdkeok. MEETING POSTPONED. Sorry to anyone who turned up hoping for a discussion :(22:40
mdkewe'll rearrange the meeting as soon as possible22:40

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