/srv/irclogs.ubuntu.com/2008/10/09/#ubuntu-meeting.txt

=== Rafik_ is now known as Rafik
=== asac_ is now known as asac
davidmOK mobile meeting is about to start13:00
lool#startmeeting13:01
MootBotMeeting started at 07:01. The chair is lool.13:01
MootBotCommands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]13:01
loolRoll call  \o/13:01
davidmthanks lool13:01
StevenKYay!13:01
lool#topic roll call13:01
StevenKMade it, sir!13:01
* cgregan waves13:01
lool[topic] roll call13:01
MootBotNew Topic:  roll call13:01
* davidm thinks he is alive, but is not sure.13:01
loolcgregan, StevenK, persia, amitk, davidm, ogra, lool13:01
* lool waves13:01
* ogra waves13:02
* StevenK waves13:02
* davidm Waves13:02
persia 13:02
loollooking at last week's actions13:02
loolnone?13:03
loolis "#13:03
loolcgregan had an action to compare & contract F-Spot and GThumb (CO) "13:03
loolstill an action?13:03
lool[topic] cgregan had an action to compare & contract F-Spot and GThumb (CO)13:03
MootBotNew Topic:  cgregan had an action to compare & contract F-Spot and GThumb (CO)13:03
loolcgregan: woot13:03
cgreganlool: I have compared13:03
cgreganGthumb is a bit less resource hungry13:03
loolcgregan: Cool, did you write down a summary in a wiki page or email?13:03
loolotherwise, fine to do it here13:04
cgreganlool: That I still need to do13:04
loolcgregan: mpt did a nice empathy/pidgin comparison for the ubuntu desktop's im client13:04
loolon wiki.ubuntu.com13:04
cgreganyes13:04
cgreganI have seen that13:04
persiaI don't think we need that much detail : I just want some sort of photo viewer in the seed.13:04
cgreganit may be a bit intense for my bandwidth right now13:04
loolWould be nice to have some much shorter one here as well13:04
cgreganI will put together an email13:05
loolI just wanted to mention this review because it's very complete, so can be inspirational for yours13:05
loolBut I don't expect the same level of completeness; he spent a long time on it13:05
cgreganYEs13:05
StevenKAnd we already seeded gthumb13:05
cgregan:-)13:05
loolcgregan: So your recommendation is gthumb?13:05
StevenKThank $DEITY we agree!13:05
loolcgregan: Did you try importing photos from a camera or the like?13:06
cgreganWell....glad I liked it better then! :-)13:06
persiacgregan, Well we could have changed it if your findings differed13:06
cgreganlool: I did....but only had one camera13:06
lool[agreed] prefer gthumb over f-spot13:06
MootBotAGREED received:  prefer gthumb over f-spot13:06
loolcgregan: I'd love to have some URL to which I can point people for the choice of photo software, so a wiki page or email to public list is nice; this IRC meeting log could do otherwise13:07
loolAnything else to discuss on this topic?  moving on?13:07
cgreganI can put up a wiki.13:07
loolperfect thanks13:07
lool[topic] StevenK to write spec(s) to have choice of launchers/extend launcher for theme ability13:07
MootBotNew Topic:  StevenK to write spec(s) to have choice of launchers/extend launcher for theme ability13:07
StevenKThey're both done13:08
loolStevenK: (muahah)13:08
StevenKYou even have the links to them13:08
loolI do?13:08
StevenKI thought I mailed them to you13:08
persiaWhich is the correct agenda?  I'm looking at https://wiki.ubuntu.com/MobileTeam/Meeting/2008/20081009 but it doesn't seem to match.13:08
loolyou did!13:08
StevenKHah!13:08
lool[link] https://blueprints.edge.launchpad.net/ubuntu-mobile/+spec/mid-jaunty-boot-menu13:09
MootBotLINK received:  https://blueprints.edge.launchpad.net/ubuntu-mobile/+spec/mid-jaunty-boot-menu13:09
davidmpersia, I just fixed pages13:09
lool[link] https://blueprints.edge.launchpad.net/ubuntu-mobile/+spec/mid-jaunty-launcher13:09
MootBotLINK received:  https://blueprints.edge.launchpad.net/ubuntu-mobile/+spec/mid-jaunty-launcher13:09
davidmwill fix them again post this meeting so they don't go a week out of date my bad13:09
loolMoving to current items for this week13:09
lool[topic] status of intrepid tasks: merge of ppa, installer, images etc. (davidm)13:09
MootBotNew Topic:  status of intrepid tasks: merge of ppa, installer, images etc. (davidm)13:09
StevenKI think the only relevant thing on that list is the installer13:10
StevenKimages are done, but currently broken13:10
loolAFAIK, three major things are installation of MID images and linux-restricted-lpia as well as madwifi/ath5k on Q1U13:10
loolStevenK: You fixed lrm-lpia or are about to complete?13:10
loolStevenK: Or will this complete tomorrow?13:10
persiaWhich works except that lpia thinks it uses i686 CPUs for some reason, which we're working around.13:10
ograthe latter is something amitk works on atm13:10
StevenKNeed confirmation, waiting for Soyuz13:10
loolStevenK: Can we expect them tonight still, or tomorrow?13:11
StevenKlool: "Dealing with" is the current status13:11
loolStevenK: Ok; so lpia-lrm in progress13:11
loolthis should fix the images13:11
StevenKI suspect I'm also fixing the installer, due to fiddling with the seeds13:11
loolthen mid might or might not install, might be using wrong kernel?13:11
loolor no kenrel?13:11
persiaYou're working around the remaining installer bug, which will be fixed properly in ubiquity 1.10.513:11
StevenKThe former13:12
loolso I'm aware of grub missing from the images13:12
loolthen 686 being used instead of lpia for kernel flavor (IIUC)13:12
looland the mid image failing to build due to lpia-lrm not being installable13:12
persialool, No.  lpia uses lpia kernel flavour.  dpkg-architecture thinks it's i68613:12
loolanything else on the lpia/mid images?13:12
loolpersia: Thinks that the CPU is i686?  that's fine13:13
loolDEB_HOST_ARCH_CPU=i686 is correct13:13
persiaIs it?13:13
loolWhat's the problem you're seeing?13:13
persiafailure of DEB_HOST_ARCH_CPU to meaningfully match DEB_HOST_ARCH13:14
persiaSpecifically, for multiple arches to have the same CPU values.13:14
persiaIt broke the mapping, which is why we don't have grub today (which we're working around).  it's not worth fixing, but it's certainly confusing.13:14
loolah actually it might not be13:15
loolIn fact you don't want to use ARCH_CPU13:15
persiaNo?13:15
loolOk, what's using ARCH_CPU?13:15
persiaubiquity uses it to determine which is the correct bootloader13:15
loolFor upstream software, we should check GNU_CPU13:15
persiaNo, this is just debian/rules + debian/control13:16
loolthe difference between _ARCH and _ARCH_CPU is that one has the kernel when it's not linux13:16
loolFor instance on kfreebsd-i386 and -amd64, they differ; otherwise they should be the same13:16
persiaRight, which is required for kfreebsd, etc. in Debian.13:16
loolSo I guess you're correct that i686 is the wrong value13:16
lool(I thought we were discussing the other _CPU which should be i686)13:16
persiaIt's at least a confusing value.  Fixing it would be exceedingly painful.13:16
loolYeah13:17
loolI don't see us changing that at this point13:17
loolSo let's go with an _ARCH check?13:17
persiaThat's the consensus.13:17
persiaubiquity has a workaround committed, and the seeds have a workaround committed waiting for the ubiquity workaround upload.13:17
loolOk; so this ubiquity issue is understood and pending an upload to workaround it13:17
loologra: what's today's status on ath5k/madwifi?13:18
ograamit wanted to start working on it today13:18
ograi didnt hear anything back from rtg beyond that he will pull in a LBM package into intrepid-updates13:18
loolOk, so someone is working on it13:19
ograwhich doesnt help us for release13:19
ograamit offered adding a pci quirk to blacklist the module on Q113:19
StevenKThe seeds are commited.13:19
loologra: sounds good13:19
ograwhich i think is our best option13:19
StevenKI'm not sure if I pushed, and I'm in the middle of ./update13:19
loologra: Let's go with this; can I [action] you to push a fix before next week?13:19
* StevenK stops looking for his seed checkout on cocoplum13:19
loolIf the PCI quirk can't be done, we will resort to some blacklist sadly13:20
ograso waiting for feedback from amit on the quirk a,d then waiting for rtg for the backported 2.6.28 modules13:20
ograsure13:20
ograyeah13:20
lool[action] ogra to make sure a quirk or a blacklist entry is prepared to fix Q1U's wifi13:20
ograblecklist would be the most trivial then13:20
MootBotACTION received:  ogra to make sure a quirk or a blacklist entry is prepared to fix Q1U's wifi13:20
ogra*black13:20
loolpersia: Concerning ubiquity, can I assign you to make sure lpia installs (even from a bzr ubiquity)?13:21
lools#lpia#lpia/mid13:21
persialool, OK.  It installs today, as long as you put grub in filesystem.squashfs before you try.13:21
loologra: Please only consider blacklist as last resort -- as discussed already13:21
ograindeed13:21
loolpersia: I want to make sure we land an installable image asap13:21
StevenKHm. No push, since it's a bound branch, duh.13:21
loolpersia: so with the grub seed fixes and bzr ubiquity it works from top to bottom?13:22
StevenKlool: mobile-meta will be uploaded shortly13:22
ograjust wanted to point out thats a one upload thing13:22
StevenKlool: *or*13:22
persialool, It should.  I'll let you know in ~10 hours.13:22
loologra: Ok, indeed13:22
StevenKWith the grub seed fixes *or* bzr ubiquity it works13:22
loolpersia: Thanks; mind if I action to revisit this next week?13:22
persiaNo.13:22
StevenKAh13:22
StevenKOkay13:22
lool[action] persia to make sure lpia/mid installs with trunk versions of seeds and ubiquty13:23
MootBotACTION received:  persia to make sure lpia/mid installs with trunk versions of seeds and ubiquty13:23
loolStevenK: can I action you for fixing lrm-lpia installability?13:23
persiaWell, I'll actually make sure the dailies install :)13:23
loolOMG it's action day13:23
persiaChasing trunk is *hard*13:23
StevenKlool: You can, but I've likely already done it13:23
lool[action] StevenK to make sure lpia-lrm reaches archive and is installable13:24
MootBotACTION received:  StevenK to make sure lpia-lrm reaches archive and is installable13:24
loolStevenK: Things are too easy for you13:24
StevenKOh, are they?13:24
loolStevenK: i'll need to action you with harder stuff!13:24
ogra120 pushups ?13:24
StevenKI used to be able to do that :-(13:24
persiaIt's a matter of practice13:24
* ogra was never in his life in the three digit area ...13:25
lool[topic] amitk - kernel issues13:25
MootBotNew Topic:  amitk - kernel issues13:25
ograis he here ?13:25
loolwho put that topic?  was it amitk himself?13:25
loolhe isn't around to comment sadly13:25
loolI poked him to join13:25
ograi think that was david13:25
looldavidm: What were your discussion topics?  linux/linux-lpia merging?13:26
lool[action] carry over: amitk - kernel issues (davidm)13:26
MootBotACTION received:  carry over: amitk - kernel issues (davidm)13:26
lool[topic] StevenK's status13:26
MootBotNew Topic:  StevenK's status13:26
loolStevenK: How is it going?13:27
davidmI added amitk kernel issues in case there were any13:27
lool(agenda is a bit werid TBH)13:27
StevenKDealing with Kourou, which is uploaded, LRM, now seeds13:27
davidmbut kernel team is busy this week13:27
looldavidm: We'll revisit at end of meeting if he comes up, otherwise next week13:27
davidmyes13:27
StevenKOh, and Soyuz bugs13:28
loolEh13:28
loolOk; StevenK: any blocker?13:28
StevenKSleep13:28
lool[topic] Installation of language packs and network access at install time (EmmetHikory)13:28
MootBotNew Topic:  Installation of language packs and network access at install time (EmmetHikory)13:28
StevenKBut that is painful to fix13:28
loolpersia: woot13:29
persiaThose were last week.13:29
ograStevenK, thats a post release action :)13:29
StevenKHah13:29
persiaThis week I want to talk about bug #280014.  It's in progress, and ought be sorted tomorrow.13:29
ubottuLaunchpad bug 280014 in ubiquity "Cannot install with a blank password" [Undecided,In progress] https://launchpad.net/bugs/28001413:29
persiaOnce that's done, and in the images, I'll want to push a change to casper to put ubuntu-mid installation into --automatic mode, and it should be clean.13:30
loolpersia: sorry, they are lsited in https://wiki.ubuntu.com/MobileTeam/Meeting/2008/2008100913:30
StevenKpersia: cjwatson disagreed with the change, from what I saw13:30
lool[topic] installation with blank password13:30
MootBotNew Topic:  installation with blank password13:30
persiaStevenK, The disagreement was with the implementation, as the way I did it broke the UI.  I'm working on an alternate implementation that doesn't do that.13:31
loolpersia: so status is that you made the debconf additions to have a flag to allow this and this needs uploads?13:31
persiaEssentially, I first just ignored blank passwords, but the user then presses next and gets an error.13:31
StevenKpersia: Ah, okay13:31
loolok, pending a bug fix13:31
persiaI need to check the preseed values in the ubiquity frontend, and use that to determine whether to allow the user to proceed.13:31
persialool, The debconf changes and d-i stuff is complete.  I'm just working on the ubiquity front-ends.13:32
loolpersia: I guess I can also skip "Switching to ISO9660 images instead of USB images" then?13:32
persiaYeah, last week we determined that we weren't doing that.  I believe I was supposed to start a spec about it, but I didn't start it yet.13:33
davidmIt's gone13:33
loolthanks13:33
loolpersia: any blocker?13:33
loolpersia: anything else you're working on?13:33
persiaNo real blockers.  I'm looking forward to the landing of the install-from-USB fixes underway, but not actively involved.  I've been looking at the lpia desktop alternate CD installer, which still has some issues, but I don't consider that intrepid-critical.13:34
lool[action] persia to write spec on providing iso images or vm support or how to write mobile images for end users13:34
MootBotACTION received:  persia to write spec on providing iso images or vm support or how to write mobile images for end users13:34
lool[topic] lool status13:35
MootBotNew Topic:  lool status13:35
persiaWhat?  I'm not going to do that.13:35
ograwhat ?13:35
loolstatus is currently here, chairing your meeting13:35
ograwhy is that ?13:35
persiaI'll write release notes if the problem can't be fixed.13:35
* ogra thought we were over the iso stuff13:35
* persia too13:36
loolpersia: "I believe I was supposed to write a spec about it", davidm proposed that I action you on it13:36
ograjaunty wont need it because the nstaler will be fixed13:36
loolI thought we were done as well, but perhaps you wanted to spec something for intrepid13:36
loolerr jaunty13:36
persiaOK.  That makes more sense.  Sure, I'll write a spec for Jaunty.13:36
loolOk; so we'll drop the action from wiki or dismiss next week :)13:36
ograand your mini iso will fix it for intrepid13:36
StevenKSeed changes uploaded13:36
loolok13:36
loolback to my status, I've been helping around with misc issues as usual lately; nothing blocking to report13:37
loolI'm playing with jax10 hardware13:37
* ogra wants ... 13:37
lool[topic] ogra's /proc/self/status13:38
MootBotNew Topic:  ogra's /proc/self/status13:38
ograall fine, chasing some general intepid bugs that also affect mobile13:38
loologra: So, how is it going?13:38
loolgood13:38
loologra: blocked on anything?  anything intrepid critical you'd like to mention?13:38
ograi.e. the compiz doesnt allow dpms one13:38
ograonly that i still have a bunch of .fdi file changes to make for touchscreens13:39
ograi found a proper successor for ltsp13:39
looleh13:39
ograstgraber will take that over from em13:39
ogra*me13:39
ograso i can do ltsp upstream but got the packaging off my back13:39
ograi.e. everything that pust duties on me with ltsp is gone13:40
loolGood news13:40
ograyeah13:40
loolOk, moving on13:40
ograwill give me more free time in jaunty13:40
lool[topic] special guest cgregan's status13:40
MootBotNew Topic:  special guest cgregan's status13:40
cgregan:-)13:40
loolcgregan: would you like to mention anything intrepid related or blocking :)13:40
ograoh, and i wrote https://wiki.ubuntu.com/MobileTeam/Mobile/HowTo/ImageWriting13:40
loolor anything relevantr eally13:40
lool[link] https://wiki.ubuntu.com/MobileTeam/Mobile/HowTo/ImageWriting13:40
MootBotLINK received:  https://wiki.ubuntu.com/MobileTeam/Mobile/HowTo/ImageWriting13:40
cgreganWorked on a new landing page for the cases yesterday13:41
cgreganSince we now have mobile and MID versions13:41
cgreganit seemed like a good idea13:41
* ogra needs to go over that one 13:41
ograthe text is a bit confusing ...13:41
cgreganAlso....reviewing some potential testers for this team13:41
cgreganogra: the text on the landing page?13:42
ogra(note mobile is not centric on netbooks, but on UMPCs)13:42
ograi.e. focused on touchscreen use13:42
loolit's also ok with netbooks :)13:42
cgreganMobile or MID?13:42
ograright13:42
ogramobile13:42
cgreganthen MID is?13:42
loolMID is MID and UMPC :)13:42
cgreganhehe13:43
persiaFor MIDs.  Currently only the Aigo or the D4, but could be more.13:43
loolmobile is UMPC and netbooks and MID :)13:43
ograyou can very well use mobile on netbooks but mobile *is* for UMPCs without keyboards13:43
cgreganok....as long as it is not confusing! :-)13:43
looland Ubuntu Desktop is desktops laptops mids umpc netbooks13:43
persiaMobile works *great* with a keyboard.13:43
ograsure13:43
loolServer is servers desktops laptops netbooks umpcs and mids13:43
persiaNo.  -desktop doesn't work very well for MIDs (I've tried).13:43
ograbut the mobile UI was designed with touchscreen in mind13:43
persiaogra, Sure, but it also works the other way.  Be inclusive :)13:44
cgreganOk....so we need to clarify what we are building these for.....and update the wiki13:44
loolpersia: It works better than minimal in my experience13:44
persialool, I guess, but there are better options.13:44
ograpersia, currently the test case says mobile is the version we designed for netbooks13:44
loolcgregan: So in general you're calling for contributions to the QA test cases?13:45
persiaHrm.  That's not very inclusive.13:45
loolI also saw davmor2 work on them13:45
cgreganlool: Yes....and this clarification13:45
cgreganI have been pulling UNR cases over to cover mobile....since the former mobile cases are now MID13:45
loologra: Well it's better suited for netbooks than desktop still :-)  but it shouldn't restrict to netbooks13:45
cgreganBut I have a feeling there are inaccuracies13:45
ograright13:45
loolcgregan: I think we need to clarify this for everybody's sake13:46
cgreganlool: yes13:46
persiacgregan, If you have some time, I'd be happy to discuss in #ubuntu-mobile after the meeting.13:46
ogralool, i had a bunch of complaints from umpcportal users that wanted to see UMPC mentioned ...13:46
loolThe way I see it, everything will work more or less on netbooks, mids, and umpcs, but the experience is really different13:46
ograso i like to advertise mobile as designed for touchscreen driven UMPCs but also usable on netbooks atm13:47
* persia points at the clock, and suggests further discussion after the meeting.13:47
cgreganpersia: More calls after this, but perhaps a little later, or in your morning13:47
persiacgregan, OK.13:47
* lool welcomes persia's pointer to the clock13:47
cgreganThat's it for me13:47
loolThanks Chris13:47
loolIt seems on topic to mention a new position at Canonical *cough*13:47
lool[topic] new QA position at Canonical13:48
MootBotNew Topic:  new QA position at Canonical13:48
davidmWe are looking for someone with a commercial background13:48
cgreganyes...looking over some candidate info today13:48
loolFor people reading this, there's a job opening in the mobile team at Canonical13:48
davidmhttp://webapps.ubuntu.com/employment/canonical_MIDQA/13:48
MootBotLINK received:  http://webapps.ubuntu.com/employment/canonical_MIDQA/13:48
loolOk; that should get the attention of people reading the minutes13:48
loolMoving to davidm's stauts13:48
davidmYep, thanks13:48
lool[topic] davidm's status13:49
MootBotNew Topic:  davidm's status13:49
davidmI've been in meetings and paperwork all week13:49
loolcoffeed or not coffeed is the question13:49
ograheh13:49
davidmthe QA position was one output13:49
StevenKBeing in paperwork sounds uncomfortable13:49
davidmthe other is a bit of a focus change13:49
davidmOnce we clear the intrepid critical bugs we should have a look at the rest of the intrepid bug list13:50
davidm https://edge.launchpad.net/ubuntu/intrepid/+bugs13:50
davidmAnd see where we might be able to help a bit.13:50
davidmSo fix intrepid critical bugs and then help the other teams with their intrepid critical bugs :-)13:51
loolOk; davidm are you blocked on anything where you could be helped by the team?13:51
looland anything else intrepid critical which yuo'd like to mention?13:51
ogradavidm, mobile is affected by most of the desktop things there anyway13:51
davidmNo, I'm not blocked, and I appreciate your suggestion last week of a rotating secretary within the team13:52
davidmthat will help me a great deal13:52
davidmthanks for all of the output last week13:52
loolSo I've picked up October and will call for a November secretary again as we near up13:52
davidmOnce we have images again that install I'm happy to help were ever we can.13:52
loolAny other topic?13:52
davidmnot from me.13:53
loolWe need to fill up the last 8 minutes, I can't let people wander off freely before the end of the hour13:53
pittihi13:53
StevenKYou can't?!13:53
StevenKYou monster!13:53
loolWell you're under my responsability13:53
ograheh13:53
loolWhat if you're hit by a truck?13:53
persiaIs there anyone else who wants to raise anything?13:53
loolOk; thanks everybody for attending13:53
lool#endmeeting13:53
MootBotMeeting finished at 07:53.13:53
cgreganthanks13:54
* lool waves to desktop team13:54
Riddellhi13:56
pittihey everyone14:00
pittidesktop team ready?14:00
pittiseb128, Riddell, kwwii, mvo, Keybuk ?14:00
seb128hey pitti14:01
pitti(well mvo-ish)14:01
kwwiipitti: I am here :-)14:02
Riddellhi pitti14:03
mvohello14:03
mvoI'm still part of the team until the 20th, then I move to foundations :)14:03
pittiok, Keybuk might still be recovering14:03
pittimvo: oh, good to know14:03
pitti#startmeeting14:03
MootBotMeeting started at 08:04. The chair is pitti.14:04
MootBotCommands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]14:04
pitti[LINK] https://wiki.ubuntu.com/DesktopTeam/Meeting/2008-10-0914:04
MootBotLINK received:  https://wiki.ubuntu.com/DesktopTeam/Meeting/2008-10-0914:04
pittitoday's meeting template14:04
pittiI didn't see any explicit agenda items, did I miss any?14:04
pittiI saw the langpack and bluez problems from Riddell, and I plan to go through some RC bugs14:05
pittitedg: here by chance? some questions involve you, too14:05
kwwiipitti: I just want to make sure that the gnome-themes stuff gets done as well as reverting ubuntu-sounds14:05
pittilet's add that to the topic14:06
tedgpitti: Yes, for a little while.  The conference picks up in an hour, and I have to walk over (no IRC there)14:06
pittitedg: great, thanks14:06
pitti[TOPIC] Outstanding actions from last meeting14:06
MootBotNew Topic:  Outstanding actions from last meeting14:06
pittiseb128 to propose three options for bug 27414614:06
ubottuLaunchpad bug 274146 in gnome-session "Has not yet replaced the existing log out applet" [High,New] https://launchpad.net/bugs/27414614:07
pittithat has happened (thanks)14:07
seb128done14:07
pittihowever, we didn't really get closer to a decision14:07
seb128extra suggestions followed and discussion14:07
seb128and the bug stalled since14:07
pittior, rather, we seem to have several different personal preferences, but it's a bit unclear who is to decide14:07
seb128it's rather than we are getting late, some options are not changes you want to land one week before intrepid14:08
pittitedg: I left some questions to your latest reply, wrt. going back to hardy with the updated gconf setup, is that actually possible? or is it an one-way thing?14:08
seb128ie changing user datas would require testing14:08
pittiseb128: what's your preference, BTW?14:08
tedgpitti: It should be okay.  As then the panel will drop the new FUSA applet and pick up the old one.  It won't rewrite it's config, we'd only be appending.14:09
seb128I've to admit I didn't think about the issue for a few days and I've been coming forth and back so not really sure right now14:09
pittitedg: oh, I see; but you'd change the logout applet, too?14:09
seb128I think what mvo suggested (the update-notified hook to update the config)14:09
tedgpitti: Yes, but that would then be the same.  On Intrepid it would pick up the new logout applet if a user put it there, but on Hardy it would do the old one.14:10
pittitedg: hm, that sounds good actually14:10
seb128what option is that one?14:10
pittitedg: on the topic of feasibility, could you actually work on that, so that we can test it soon?14:10
pittitedg: it would be triggered by what, an Xsession.d script?14:11
pittior autostart .desktop or so? or by the panel itself?14:11
tedgseb128: The idea of changing the namespace for both the FUSA applet and the logout button.  And then inserting the new applet name into the panel config.14:11
seb128I don't like the namespace change option14:11
seb128and would that work?14:12
tedgpitti: I can work on it, but I'm not getting much hacking time right now -- probably not until the weekend.14:12
seb128the logout button is a panel object where fusa is an applet14:12
tedgpitti: The GNOME Summit is more of a hackfest, this is more talking and whiteboarding.14:12
tedgseb128: Correct, but they both have names.  One would be a patch to GNOME Panel.14:12
pittimy personal feeling is, if we don't have working code for this by the next meeting, we fall back to the upstream behaviour and document it14:12
seb128patch to keep forever which makes us incompatible with upstream configs?14:12
seb128no thanks14:13
pitti(which is actually my preference)14:13
pittiwe did the decision to have the split dialogs again, so the desktop look&feel changes *anyway*14:13
tedgCan we do a phone call on this?  I feel like IRC/email/launchpad isn't really working towards getting agreement on where to go.14:14
seb128right, the split dialog is not an issue, the issue is the green man button which is pretty much useless after upgrade14:14
pittiseb128: it can log out out...14:14
seb128right, but it changes the sementic over what it was before14:14
mvoif we go with the "document" approach, we could as well use a notifier hook for the documentation14:14
kwwiiyeah, and I have now linked the logout button to the little green man pic, so that will be going away graphicaly14:14
seb128ideally we would have the new fusa or nothing there now14:14
seb128mvo: what was your little python code thing doing?14:15
pittimvo: *nod*, if it explains what to do, good14:15
mvothe notifier hook can have code attached as well, so we could add a small python script that does the required gconf juggling automatically if the user decides on it14:16
seb128mvo: what was your juggling exactly?14:17
mvoseb128: the python code I played with jsut moves the existing fusa applet to the right coerner and removes the logout button from the object list14:17
seb128mvo: deleting and adding or moving things?14:17
pittimvo: could it replace logout with fusa if the user just has logout?14:18
seb128mvo: if you tested it and it works that would be my favorite option14:18
pittimine, too14:18
=== e-jat is now known as norly
seb128ask the question in update-manager after upgrade14:18
=== norly is now known as nOrly
pittiI just don't like fully automatic gconf changing14:18
seb128pitti: I would not care about people who don't have the standard ubuntu layout, they know how to customize their config14:18
pittiseb128: it's asked in the desktop, in update-notifier, I think14:19
mvoit could do a replace too, not sure if that is desirable, my initial "design" was to bail out if anything is unexcpected assuming that the user has customizations14:19
seb128if fuse and session applets are there ask otherwise do nothing14:19
pittiseb128: but we added the logout applet earlier than fusa, so it is a standard setup situation IMHO14:19
seb128+1 from me on mvo's current juggling14:19
pittie. g. if the user installed edgy and upgraded since then, he would have never seen fusa14:19
mvopitti: thats right14:20
pitti+1 from me too, if we can extend it to the "just logout applet" case, and we can get it in by next meeting14:20
seb128pitti: ok, so always delete the session button on upgrade and add fusa in the corner and delete old fusa before doing that if it's used in the config?14:20
mvoI really shouldn't ask for more work, but I think it can done reasonably simple14:20
* seb128 hugs mvo14:21
pittiseb128: sounds right14:21
tedgIt works for me.14:21
seb128ok, agreement, every sign now ;-)14:21
pittiyay, an agreement!14:21
pittiw00t14:21
seb128\o/14:21
* tedg looks for some Boston Tea to send mvo -- apparently they had a tea party here a while back.14:21
pittimvo: I think you are the natural victi^Wassignee now?14:21
seb128everybody hug mvo!14:22
* seb128 hugs mvo14:22
mvotedg: ohhhh, that would make me a happy man, but check the "best-before" date, the party was a while ago IIRC ;)14:22
pitti[ACTION] mvo to upload upgrate notification based panel gconf updating for bug #27414614:22
MootBotACTION received:  mvo to upload upgrate notification based panel gconf updating for bug #27414614:22
ubottuLaunchpad bug 274146 in gnome-session "Has not yet replaced the existing log out applet" [High,New] https://launchpad.net/bugs/27414614:22
* pitti hugs mv"hero"o14:22
pittimvo: oh, and of course we need u-m to support my new "upgrate" mode, too14:22
pitti(merge update and upgrade)14:23
mvohu?14:23
pittiok, I'm glad that we settled this14:23
pitti[TOPIC] kwwii: revert ubuntu-sounds14:23
MootBotNew Topic:  kwwii: revert ubuntu-sounds14:23
pittikwwii: can you please give us a little heads-up?14:24
kwwiiso, I was told to revert the sounds as they are way too close to windows vista sounds (duh! /me does not have windows)14:24
pittiFWIW, I just noticed the new login sound once, about 20 minutes ago14:24
kwwiiI really like the new sounds but this came down from on high, so there is no discussion, just reverting :-)14:24
pittikwwii: ok; can you please prepare a new package and poke me or seb for uploading?14:24
kwwiipitti: well, all we need to do is to revert to the hardy version14:25
seb128just raising the issue but think way decisions are taken at the moment will not work correctly14:25
kwwiiseb128: apparently there are quite a few people who think the sounds are too vista-like14:25
pitti-EPARSE14:25
seb128those gnome-themes, etc decision are taken nowhere visible, not discussed and come as "you need to do those changes" on random team people now14:25
kwwiiseb128: yeah, the gnome-themes stuff is a bit different than we normaly do things, but we have been talking about that for along time14:26
seb128pitti: well, basically kwwii ping random people saying "we need to do those changes"14:26
seb128pitti: changes which are neither discussed before, not documented14:26
kwwiiseb128: the only time I do that is when I have approval or direction from sabdfl14:27
seb128and not coming through a proper procedure14:27
seb128kwwii: I understand that but I don't think it's a good way to do things or will scale14:27
seb128you just ping random people on IRC about changes to do which are not explained, not discussed, etc14:27
kwwiiseb128: I can understand what you are saying, I guess to some extent the artwork has always been a bit chaotic in this regard14:28
pittiArtwork has always had this kind of "Mark's baby" on it, though14:28
seb128pitti: the gnome-themes split is not really artwork14:28
seb128it's delta over debian14:28
kwwiihonestly, the only things I push on people to change are things in which I have an email from Mark telling me to take care of it14:28
seb128upstream themes we don't ship etc14:28
kwwiiand I only do that if I cannot do it myself14:28
pitti(next topic)14:28
seb128pitti: it'll make upstream angry, we will get complain and we have nothing to point about why that has been decided14:29
pittiseb128: that's for gnome-themes already, or for ubuntu-sounds?14:29
seb128pitti: gnome-themes in my case14:29
pittiok, seems the actual u-s topic is done14:29
seb128I don't know about ubuntu-sounds14:29
pitti[TOPIC] Ken: gnome-themes cleanup14:29
MootBotNew Topic:  Ken: gnome-themes cleanup14:29
kwwiiso, this is what seb128 wants to discuss :-)14:29
pittikwwii: the themes you propose to remove, are they from upstream, or did we patch them in?14:30
kwwiipitti: they are from the upstream package14:30
pitti(Crux, Glider, etc)14:30
pittiso why should we remove them then?14:30
kwwiipitti: everything except the high-contrast* themes14:30
pittiQ1) why remove them in the first place? it's GNOME14:30
kwwiibecause they are "ugly" and outdated, basically14:30
seb128pitti: because somebody think they don't look nice and clutter the themes lists14:31
pittiQ2) how can we make sure that we can DTRT on upgrades?14:31
kwwiithe only ones that interest anyone is the accessability stuff14:31
pitti*shrug* de gustibus non disputandum est14:31
seb128pitti: we discussed the upgrade previous week and that's no issue14:31
mvoI think seb128 has a point, upstream releations are very important, if that is a change that upsets them, that is not good14:31
kwwiipitti: the answer to the upgrade issue is to put all the themes we remove into another package and only install that on upgrades14:31
pittiseb128: if the theme files suddenly disappear, it'll fall back to hi-contrast?14:31
seb128we need a gnome-themes dummy package depends on nice looking and not ubuntu shipped packages and install only nice looking14:31
seb128so upgrades still have "not ubuntu shipped"14:32
pittikwwii: that sounds like a lot of effort for no visible effect14:32
seb128and new install have only "nice looking themes"14:32
pittido they take so much space on CDs that we need to worry about them?14:32
seb128no14:32
pittiSize: 27260614:32
kwwiipitti: it cleans out the interface and removes cruft14:32
pitti(hardy)14:32
kwwiithe size issue is not worth talking about :-)14:32
seb128pitti: it just makes the themes lists be also empty14:33
seb128almost14:33
pittikwwii: apparently there were upstream discussions, if they are abandoned, would upstream remove them?14:33
kwwiipitti: afaik upstream will not change this package any time soon14:33
seb128pitti: upstream did some cleaning some cycles ago, crux is used14:33
pittiif upstream says "we'll remove them in 2.26", I'd be okay with doing the change ahead of time, but why bother otherwise?14:33
seb128they probably don't agree on the uglyness there14:34
pittikwwii: is there actually a point for discussing this, or is that another sabdfl-ism?14:34
kwwiipitti: mianly because sabdfl told me to14:34
kwwiipitti: exactly :-)14:34
pittihm, but it's a part of GNOME after all14:35
kwwiisure, and it is not like he won't listen to reason14:35
seb128it's going to create package delta, angry upstream and users for no win14:35
pittiso, for the record, I don't agree to the approach, and I don't see why having some non-default themes available is a bad thing14:35
kwwiibut then someone who knows the reasons should discuss it with him14:35
seb128ok, let's take that out of the meeting14:35
kwwiiok14:35
tedgkwwii: Weren't you getting some push back on including the community themes?14:35
kwwiitedg: we do include the community themes now...not sure what you mean14:36
kwwiiso we do have three new themes14:36
tedgkwwii: Oh, on the CDs?14:36
kwwiiyes14:36
tedgAnd that's generally okay?14:36
pittiok, I propose we continue the discussion on u-desktop@ as replies to Ken's mail14:36
pittiI'll start with it, and CC: Mark14:36
kwwiipitti: cool, thanks :-)14:36
pitti[ACTION] pitti and other desktop members to reply on gnome-themes issue on the ML, CC'ing Mark14:37
MootBotACTION received:  pitti and other desktop members to reply on gnome-themes issue on the ML, CC'ing Mark14:37
pitti[TOPIC] Martin: Discuss desktop related intrepid-targeted bugs14:38
MootBotNew Topic:  Martin: Discuss desktop related intrepid-targeted bugs14:38
pittibug 26108414:38
ubottuLaunchpad bug 261084 in gnome-power-manager "Suspends again right after resume" [High,Confirmed] https://launchpad.net/bugs/26108414:38
pittitedg: your PPA package seems to have improved the matters, but not completely fixed them apparently14:38
pittitedg: do you have an estimate how common the remaining cases are?14:38
pittiand should it still be RC after your PPA fix?}14:39
tedgpitti: No, sorry I hadn't noticed that someone had said that they didn't work.  (I'm behind on mail)14:39
tedgpitti: I'm trying to check to see if the power button fixes break Xubuntu (no new GNOME Session) before uploading them genericly.14:39
pittitedg: ok, thanks; it's the only remaining unclear "Ted"ish bug on my list14:40
pittitedg: thanks for making the meeting (in case you have to leave soon)14:40
pittitedg: so that bug is still on track? or do you need help?14:40
tedgpitti: I think that it's generally on track, but I really think it is another "X changed the way they do keys" bugs, and we're kinda working around it by fixing it in GPM.14:41
tedgpitti: It goes with the X doesn't have a keyboard on boot (drives me crazy) and pommed no longer works.14:41
* tedg is not impressed with the new X14:41
pittiit causes all kinds of trouble, same with non-workign suspend/brighthness keys, etc., yes14:42
pittidoes anyone feel attached to rarian? we have two bugs which look important (bug 256131 and bug 276878), they don't have an assignee14:42
ubottuLaunchpad bug 256131 in docbook-xml "failed to upgrade : "update-xmlcatalog: error: entity already registered"" [Unknown,Confirmed] https://launchpad.net/bugs/25613114:43
ubottuLaunchpad bug 276878 in rarian "better package relations for the upgrade" [Medium,Triaged] https://launchpad.net/bugs/27687814:43
tedgI think that the "no mouse or keyboard" on boot think should probably be elevated to a release blocker though.  I don't think most users want to restart X on the command line before logging in.14:43
pittiok, seems not; I just fixed my remaining intrepid bug, so I'll have a look at these two14:44
seb128pitti: I don't think anybody is really looking at it in debian or ubuntu no14:44
pittiok, next one is bug 21209814:45
ubottuLaunchpad bug 212098 in nautilus-share ""easy" file sharing not notifying about logout/login" [High,Confirmed] https://launchpad.net/bugs/21209814:45
seb128pitti: ah, the second one is basically a "change GNOME depends on scrollkeeper to rarian-compat", I can do that when uploading GNOME 2.24.1 updates14:45
mvomaybe we can get help from someone from the plattform^Wfoundations team for rarian? assuming there is someone with spare cycles ...14:45
pittiseb128: oh, that easy? nice14:45
seb128I've no clue about how the xml catalogs thing work but if somebody does that would be nice14:46
pittiseb128: ok, I assigned the second one to you, and I'll look into the first one14:46
seb128we can ask on #ubuntu-devel14:46
seb128pitti: ok thanks14:46
pittijust making sure that all the RC bugs have an assignee14:46
pittiand a plan14:46
seb128the file sharing thing, I though mvo was looking to it for 8.04.1 but I guess that got an another ETOOMUCHTODO14:46
pittiis that actually still an issue?14:47
seb128that should be easy enough14:47
pittiI guess it isn't for new installs14:47
pittisince we put the user into sambashare by default now14:47
pittibut for upgrades it is, right?14:47
seb128it is14:47
seb128samba is not installed by default14:47
pittiso it's just a matter of a better error message?14:47
pittiseb128: right, but that part is already handled, no? it presents a "install samba now" button14:47
seb128you get samba installed when trying to use the feature for the first time14:48
seb128right14:48
seb128but after the install you need to restart the session14:48
pittiright14:48
seb128because the group membership is not dynamic14:48
pittiso that just needs to be added to the dialog then?14:48
seb128so that's still an issue for new installs14:48
pittiseb128: s/new installs/upgrades/14:48
pittiwell, s/&/existing users/14:48
seb128either to that dialog or display an another dialog after the installation14:48
kwwiimuch like the "restart required" notification14:49
cjwatsonit's a problem for non-first users on new installs too14:49
pitticoudl the main sharing dialog just say so if samba is already installed, but the process doesn't have the group yet?14:49
seb128cjwatson: it's a problem for first user too no?14:49
cjwatsonseb128: not on new installs at the moment; the installer creates the sambashare group and adds the user to it14:49
cjwatsonas a grotty workaround14:49
seb128cjwatson: ah ok, I didn't know about that, I though that was the samba install doing that14:49
cjwatsonI don't like it, I'd rather remove that in favour of something better14:49
cjwatsonsamba install does it too14:50
cjwatsonbut this is to avoid the "gotta restart the session" thing14:50
pittiso if we get the "restart your session" message right, we could even remove that again14:50
seb128right, I though only samba was doing it, I didn't know about the workaround14:50
seb128pitti: right14:50
seb128people tend to not read the dialogs, so I think we should better display an another dialog after install14:50
seb128rather than trying to put too much text in the first one that users will not read14:50
pittiright, agreed, I just looked at it14:51
pittibut if you try to enable the check box again, you could get a msgbox saying "you need to restart" [RESTART] [LATER] instead of the "install samba?" question14:51
seb128that's a corner case but ideally right14:52
seb128having the "you need to restart your session" after the samba install would already be nice14:52
pittiwell, it's exactly what this bug is about, isn't it?14:52
seb128the bug is about notifying the user that the feature will not working until next login14:53
seb128s/not working/not be working14:53
seb128anyway it should be easy enough, you can assign it to me, I'll have a look14:54
pittiseb128: do you know someone from the community who could be intersted in that?14:54
seb128I'll try to see if some of the desktop contributors are wanting to give it a try other I'll look at it myself later14:54
pittiseb128: ok, thanks; please let me know if you don't find one and don't have time for it, then I'll try to look into it (I'd have to drop other stuff, though)14:55
pittiRiddell: I didn't see notable RC bugs for KDE, is it just working, or aren't they milestoned?14:55
seb128pitti: ok14:55
ScottKpitti: I think Bug #279983 should count14:56
ubottuLaunchpad bug 279983 in kdebluetooth "kblueplugd crashed with DBusException in call_blocking()" [High,Confirmed] https://launchpad.net/bugs/27998314:56
pittiScottK: right, that's for Riddell's complaint about bluez 0.4 breaking KDE?14:57
ScottKThat's the one about kdebluetooth not working with the new bluetooth stack.14:57
ScottKYes.14:57
pittihm, too bad that this didn't come up with Mario's test packages14:57
pittimarked for Intrepid now14:58
ScottKI guess leave the autopsy for another discussion.14:58
pittiok14:58
pitti[TOPIC] sponsoring queue14:58
MootBotNew Topic:  sponsoring queue14:58
pittihttp://people.ubuntu.com/~dholbach/sponsoring/14:58
MootBotLINK received:  http://people.ubuntu.com/~dholbach/sponsoring/14:58
pittihas some desktopish stuff14:58
pittiI won't go over it in detail right now, but a reminder:14:58
ScottKpitti: I do think we ought to discuss what to do about the problem though.14:58
Riddellhttps://bugs.launchpad.net/bugs/278634 is the other one, rosetta being frustratingly slow this cycle14:59
ubottuLaunchpad bug 278634 in ubiquity "[Intrepid Beta] KDE does not use the language selected during install" [Critical,Confirmed]14:59
pittiplease remember to note your sponsored uploads in the activity report, I didn't see it from anyone14:59
pittiand have a look at the queue, e. g. there is a gtk patch for an RC bug14:59
seb128ups14:59
pittiRiddell: tell me about it, this drives me mad14:59
seb128pitti: this bug is assigned to ArneGoetje and I've no clue about it15:00
pittiRiddell: but that's definitively something I'm watching and discussing, too15:00
seb128pitti: my call would be to "have upstream to comment on it first" but ArneGoetje might have a clue15:00
pittiseb128: it was just an example, nothing particularly towards you15:00
pittiseb128: yeah, sounds good15:00
pittihe should at least be able to test it15:00
pittiok, those bugs covered the "release status" topic, too15:01
pittiwe're out of time15:01
pittiScottK: does superm1 know about the KDE regression?15:01
ScottKpitti: He does.15:01
pittihe worked a lot with the packages recently15:01
ScottKMy impression was he pretty well shrugged.15:01
pittihmm15:02
seb128I don't think anything went especially wrong there15:02
ScottKThe Kubuntu dev who's mostly looked into bluetooth (Tonio) is mostly MIA at present.15:02
seb128it's just a lack of manpower issue15:02
persiaIt's more about needing upstream to do something.  None of the few people hacking the bluetooth stack now understand kdebluetooth15:02
pittihttp://launchpadlibrarian.net/18310466/Traceback.txt looks like an API change15:02
MootBotLINK received:  http://launchpadlibrarian.net/18310466/Traceback.txt looks like an API change15:02
seb128we can't block ubuntu in a broken state because nobody tests other desktop variants15:02
ScottKseb128: There's nothing especially wrong with breaking Kubuntu just before release?15:02
Riddellpersia: it would be better not to do major foundation changes after beta15:03
seb128nobody broken kubuntu just for the fun of break it15:03
seb128the work was to have a decent stack for ubuntu intrepid15:03
persiaRiddell, Agreed.  In this case the alternative was bluetooth not working for anyone.15:03
ScottKYes, but testing late major upgrades should be comprehensive.15:03
ScottKpersia: It was working for me before and it's not now.15:04
seb128having ubuntu broken just in case a derivative would break is not a solution eithjer15:04
seb128well, they did things correctly, used a ppa, had a bug for testing feedback etc15:04
persiaScottK, Ah.  Nobody said that to any of the bluetooth upgrade discussions I saw.15:04
seb128they didn't land everything to intrepid directly without testing15:04
Riddellclearly they did15:04
seb128Riddell: they did what?15:05
ScottKseb128: Not without testing, but without sufficient testing.15:05
pittihm, I don't even have a org.bluez.Manager on either the system or session bus15:05
seb128ScottK: somebody in the kubuntu community could have tested15:05
ScottKseb128: Yes and it was on my TODO.  No one said that it was about to be uploaded.15:06
pittianyway, little point in debating blame here now (I'm fine with discussing this further in #u-devel, particularly resolutions)15:06
pittiis there anything else anyone has for the meeting?15:06
seb128ScottK: better to upload sooner than later15:06
ScottKseb128: Then just skip all the testing and upload straight to Intrepid.15:06
* persia notices the complete lack of response to the call for testing on kubuntu-devel@lists.ubuntu.com15:07
seb128ScottK: they did test it correctly on ubuntu, I disagree on the lack of testing15:07
* ScottK moves to #ubuntu-devel as pitti asked.15:07
seb128the manpower is limited and it's not always possible to test all the environment you don't use15:07
pittiok, then thanks everyone, let's close the official meeting bit15:08
pitti#endmeeting15:08
MootBotMeeting finished at 09:08.15:08
seb128pitti: thanks15:08
seb128pitti: the bot is on a weird timezone ;-)15:09
persiaOK.  Who's here for the Java meeting?15:10
persiaslytherin, Koon, robilad, doko ?15:10
persiaAnyone else?15:10
Koono/15:10
dokosorry, will be away in 15min15:11
persiadoko, OK.  Anything you want to announce quickly before you go?15:11
dokono15:11
persiaOK.15:12
persiaSo Meeting Agenda is https://wiki.ubuntu.com/JavaTeam/Meeting15:12
slytherinI have a bug for which I need discussion with doko15:12
persiaslytherin, Then go now, and we'll do roadmap later, as there's nothing else on the agenda this week.15:12
dokojust one?15:12
slytherindoko: Specifically one, bug #255149. The fix is small but I wanted to discuss before I submit debdiff.15:13
ubottuLaunchpad bug 255149 in openjdk-6 "javascript script support through rhino should not be on bootclasspath" [High,Confirmed] https://launchpad.net/bugs/25514915:13
dokowell, the openoffice.org build now succeeds. what else will break?15:14
slytherindoko: The problem is that users are not able to use external versions of rhino.15:14
slytherinwhere as it can be used with Sun JDK because the symlink is not present there.15:15
dokoright, do you have a fix, e.g. getting it loaded with a class loader when needed?15:18
slytherinNo. But I will first try what is working for others i.e. removing symlink. And then I will also do some more testing to make sure there are no regressions.15:20
persiaI think I'd prefer to keep the symlink as a workaround until a proper class loader can deal with it, as trying to track down Oo.o build issues is *extremely* time consuming.15:21
slytherinpersia: OOo build issues has been fixed already with a workaround. We now need to fix other problems caused by this bug.15:21
dokoso if anybody wants to work on the class loader issue, please go ahead. this maybe is annoying for a developer, but I don't want to "fix" it by removing the symlink before the release15:22
persiaOh, a different workaround.  I misunderstood then.15:22
dokoslytherin: did you forward the report to icedtea?15:22
slytherindoko: No. The feedback from users was received a just few days ago.15:23
slytherinI will do that today.15:23
persiaAnd we're running against the 15 minute boundary, so on to the RoadMap.15:24
slytherinsure15:24
persiarobilad isn't here today, so slytherin: you're first.  I think we're just wating on ubuntu-archive for the rest of MoveToUniverse for Intrepid, right?15:25
slytherinyes. I tried more than once to get attention on #ubuntu-devel, but that hasn't helped.15:25
persiaAs long as everything is ACK'd, and waiting in queue, we're in about as good shape as we're likely to get.  Don't worry about it too much.15:26
slytherinpersia: I am worrying because libxstream-java is still in multiverse and its reverse-build-depends have entered in universe.15:27
persiaThe relevant bug has that information added as a comment?15:27
slytherinNo.15:28
persiaThat's probably the best thing to do then : it will mail the archive admins about it, and maybe raise the priority.15:28
persiaAnything else of note for MoveToUniverse?15:29
dokook, I'm away15:29
slytherinno15:29
persiaHave a good afternoon doko15:29
persiaOK.  Koon: did you get everything you needed registered for the maven spec?15:29
Koonyes, I think doko accepted to review it, so now it's waiting for review/approval15:30
KoonI also welcome other team member reviews while there is still time15:31
persiaI'm happy with it, to the extent I understand it.  It seems a lot easier than the other models presented.15:31
persiaIt just needs mvn-packaging for some makefile snippets to ease work for the maintainers.15:32
Koonyes, and a good working example :)15:32
persiaNow, for implementation, I think you needed a bunch of extra hands for packaging.  Do you want to schedule a session at OpenWeek to lead people through packaging something with Ant to help get through the first block of packages?15:33
persia(Level 0)15:33
Koonwhen is it ?15:34
persiaIt's usually the first or second week after release, so early November.  I haven't seen an announcement yet.15:34
KoonI've a team sprint around that time. If I can make it, I will.15:35
KoonWill confirm whenever we have the OpenWeel announcement15:35
Koonotherwise I'll do a wikipage explaining how to do it15:35
persiaOK.  If your schedule won't allow it, let's try to get someone else to lead a session, as I think we need three or four packagers to get this in good shape.15:36
Koonpersia: we'll decide what route to take when we have the timing for OpenWeek15:39
persiaKoon, Sounds good.15:39
KoonI'll check if it's as easy as I suspect it is15:40
persiaAnything else for maven?15:40
Koonnope15:40
persiaOK.  Any other topics anyone wants to raise?15:40
slytherinnothing form my side15:40
Koonnothing here15:40
persiaOK.  Have a good week.15:41
Koonthanks persia15:41
slytherinbye.15:43
=== persia_ is now known as persia
=== ubottu changed the topic of #ubuntu-meeting to: Calendar: http://fridge.ubuntu.com/event | Logs: https://wiki.ubuntu.com/MeetingLogs/ | 10 Oct 17:00: Ubuntu Arabic | 14 Oct 15:00: Server Team | 14 Oct 17:00: Kernel Team | 15 Oct 12:30: ubuntu-us-pa LoCo Team | 15 Oct 17:00: QA Team | 15 Oct 22:00: Platform Team
=== beuno is now known as beuno-lunch
=== dholbach_ is now known as dholbach
=== beuno-lunch is now known as beuno
=== nxvl_ is now known as nxvl
jjesse@time sydney21:16
ubottuCurrent time in Australia/Sydney: October 10 2008, 07:16:21 - Next meeting: Ubuntu Arabic in 20 hours 43 minutes21:16
* Eluxzen is away: Away22:04
=== ompaul_ is now known as ompaul

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