[04:06] <bicchi> I would like to know if the webcam works on the Samsung Q1 with Linux?
[04:08] <mjg59> No
[04:08] <bicchi> mjg59: Really I have been trying to configure it for the pass 2 hours.
[09:21] <dholbach> good morning
[12:22] <asac_> Mithrandir: i have a request to update midbrowser .desktop file ... where should fixes go to now? do we have a ppa ... or just hardy?
[12:25] <Mithrandir> asac: we have a ppa, but we don't have lpia buildds yet.  You should be able to upload to the ppa
[12:25] <StevenK> I wonder if that's on the cards.
[12:26] <asac> Mithrandir: ok ... i will try
[12:26] <Mithrandir> StevenK: I have a ticket in for it.
[13:59] <mdz> Mithrandir: I prioritized that ticket, right?
[13:59] <mdz> yep, I did
[13:59] <Mithrandir> mdz: you did, yes.
[14:01] <mdz> status was updated yesterday, due date is next Wednesday
[14:02] <Mithrandir> ok, sounds fine to me.
[14:51] <dantalizing> morning all....
[14:55] <dantalizing> so I'm perusing a linux format or linux pro or some magazine where they make mention of the ubuntu-mobile project, and along with the blurb is a pic of the n800 with an "ubuntu" screen...ie brown bg, top & bottom menu bars.... does UME work on n800s?  I cant find any reference on the wiki other than maemo as a related project.....
[14:58] <mjg59> Not currently, no
[14:58] <mjg59> Ubuntu Mobile doesn't look like that, anyway :)
[14:58] <dantalizing> thats why i was confused
[14:59] <dantalizing> and i just found the faq...sorry..should have rtfm
[16:45] <bspencer> Mithrandir:   I'll be 10mins late to our meeting htis morning.  FYI
[16:59] <davidm> bspencer, Mithrandir will not be attending prior commitments, though he may catch a few minutes I"m not sure.
[17:01] <davidm> OK, we are about to start the Mobile community meeting
[17:01] <davidm> #startmeeting
[17:01] <MootBot> Meeting started at 17:01. The chair is davidm.
[17:01] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[17:01] <davidm> Morning Don ood timing I've started the meeting.
[17:02] <davidm> s/ood/good/
[17:02] <Don_Johnson> Good morning
[17:02] <davidm> bspencer, said he would be about 10 minutes late.
[17:03] <rustyl> morning
[17:03] <davidm> [TOPIC] Action items from last week
[17:03] <MootBot> New Topic:  Action items from last week 
[17:03] <davidm> good morning rustyl 
[17:04] <davidm> Just starting the meeting.
[17:04] <davidm> Don_Johnson, who else are we expecting? Do you know?
[17:05] <Don_Johnson> I don't know who else to expect at this meeting.
[17:05] <davidm> With the day change it could be quite empty I think.
[17:05] <Don_Johnson> I thougth Kyle might want to grill me on USB Client.  But so far he does not appear to be on
[17:05] <davidm> Well I'll lead off then.
[17:06] <smagoun> Don_Johnson: I can grill you in Kyle's place
[17:06] <kyleN> hi
[17:06] <Don_Johnson> I don't know much, but if you explain the problems I'll try to get answers
[17:06] <kyleN> smagoun: please go ahead if you like
[17:06] <davidm> Last week we had an action for Mithrandir which was: tfheen to get download area for proprietary builds set up. (carried forward): In progress: Waiting for IS to set up, got preempted by the 7.10 release.
[17:06]  * HappyCamp_laptop is here, I do the Moblin Image Creator
[17:06] <HappyCamp_laptop> s/the//
[17:07] <davidm> We expect to have the download area in place by next Thursday if not EOD Wednesday.
[17:07] <kyleN> I am asking about the basic use case of plugging the MID into a PC and sharing files to the PC in order to back up the MID data
[17:07] <kyleN> my question is whether the USB client work is expecting to accomplish this
[17:08] <davidm> kyleN, please add your question to the agenda at: https://wiki.ubuntu.com/MobileAndEmbedded/Meeting/20071024
[17:08] <kyleN> one issue may be that incompatibility in file systems: ext3 on MID vs FAT on PC
[17:08] <kyleN> sorry, i though Don asked
[17:08] <Don_Johnson> kyleN, OK, I'll ask the developers
[17:08] <rustyl> Don_Johnson, unless something changed, all your guys were delivering were the gadget drivers
[17:09] <rustyl> which means you would be able to represent a mass storage device
[17:09] <Don_Johnson> The release notes talk about "Utilities" DHCP and Samba.  So it sounds like something changed
[17:10] <Don_Johnson> davidm, Please give me an AR to follow up on USB Client utilities etc.
[17:10] <rustyl> i suspect that is talking about what happens on the host side
[17:11] <kyleN> perhaps the core and mobile teams can say whether they think the use case I describe is critical
[17:11] <davidm> [Action] Don_Johnson to follow up on USB Client utilities etc.
[17:11] <MootBot> ACTION received:  Don_Johnson to follow up on USB Client utilities etc. 
[17:12] <davidm> The next open action is: lool will look at the current issues with hildon-desktop this coming week.
[17:12] <davidm> lool, status?
[17:12] <lool> So I tried looking into the hildon-desktop issue which seems to be some bad interaction of the new hildon-desktop with the old themes/engines/configs we're using; I've updated hildon-theme-layout-4 and hildon-theme-plankton and started looking at all issues I get in .xsession-errors one by one
[17:12] <lool> The broken look of hildon-desktop does change, but it's still completely unusable; I also tried using plankton instead of umebasic (hence the update) to no luck
[17:13] <davidm> lool, what are your next steps?
[17:13] <lool> I'm currently stracing the thing and I'm learning a lot on how hildon-desktop works internally in the process, such as using the cached config in the home of the end-user and using a stamp file to detect its crashes and disable some config
[17:14] <lool> I'm currently trying to solve all warnings I get and the next ones on my list are why the engine can't find its pixmaps and then why there are some negative widget sizes allocations being logged
[17:14] <lool> I expect the images are the biggest problem with the display of hildon-desktop
[17:15] <davidm> OK, sounds like the action is to continue the prior action?
[17:15] <lool> So frankly, I don't feel like I've been making a lot of progress, and don't know how much time I'll need to solve the issues; yes, simply keeping the action as it is seems best
[17:16] <lool> Or rather rename to "Cursed action: ..."
[17:16] <davidm> [action] lool to continue looking at the current issues with hildon-desktop this coming week.
[17:16] <MootBot> ACTION received:  lool to continue looking at the current issues with hildon-desktop this coming week. 
[17:16] <bspencer> lool: I'll try to provide some help
[17:16] <davidm> The next open action was: "Intel should verify the ubuntu branch works and suggest changes."
[17:16] <lool> bspencer: That's nice of you, thanks
[17:16] <bspencer> davidm: still an open action
[17:16] <davidm> OK
[17:17] <bspencer> we haven't done it yet
[17:17] <davidm> [action] Carry forward the action -> Intel should verify the ubuntu branch works and suggest changes.
[17:17] <MootBot> ACTION received:  Carry forward the action -> Intel should verify the ubuntu branch works and suggest changes. 
[17:17] <davidm> The next open action was: "bspencer to resolve issue with hildon-desktop configuration files and separate packages"
[17:18] <bspencer> lucasr suggested a configuration option that allows all plugins to be used
[17:18] <bspencer> and also suggested that for advanced placement we could implement a policy
[17:19] <bspencer> and associate the policy with the marquee
[17:19] <bspencer> he didn't bite at the idea of having a "plugins.d" subdirectory
[17:19] <lool> bspencer: (I think there's a commented out example on how to do this in the upstream default config; not sure whether there's also example code for the policy)
[17:19] <bspencer> so I will follow his advice and use the "accept all plugins" option, and investigate the policy idea further for the future
[17:19] <bspencer> lool: right.  I recall seeing this now that it was mentioned
[17:20] <bspencer> davidm: along with the ubuntu-branch hildon-desktop review, I'll add this change
[17:21] <lool> bspencer: There seem to be some policies in hildon-desktop's policies/
[17:21] <davidm> bspencer, any additional action items I should record?
[17:21] <bspencer> I don't like action items assigned to me...  but I think the "ubuntu-branch" action I already have covers this ok.
[17:22] <bspencer> :)
[17:22] <davidm> OK
[17:22] <bspencer> lool: right.  I've played with those a little (not too successfully)
[17:22] <bspencer> does anyone know if Hildon v2.0 was officially released?
[17:23] <bspencer> they seem to have started tagging, but there is on announcement about their progress.
[17:23] <bspencer> s/on/no
[17:23] <lool> bspencer: I /think/ it's part of OS2008 which should be launched with the N810 in november
[17:23] <bspencer> lool: ok.
[17:24] <davidm> Are we ready for the next open action?
[17:25] <bspencer> davidm: yes from my side.
[17:25] <davidm> The next open action was: "#davidm: Review test place at UDS
[17:25] <davidm> #
[17:25] <davidm> davidm, Review UI issues at UDS
[17:25] <davidm> #
[17:25] <davidm> davidm, further discussion of Application development and upstream at UDS"
[17:25] <davidm> which is really three items but they all relate so.....
[17:26] <davidm> We will have testing and UI issues as topics at UDS.
[17:26] <davidm> as well as conversations on Application development
[17:27] <smagoun> davidm: pat_mcgowan has a list of sessions we want to have
[17:28] <davidm> I've asked him for it but I don't as yet have it.
[17:28] <smagoun> ok, I'll ping him
[17:28] <davidm> can you give him a poke?  Thanks.  I'm going to commit the schedule in a couple of hours.
[17:29] <davidm> We can adjust it but I'd prefer get it as correct as possible the first time.
[17:29] <smagoun> ok. he's down the hall, we'll make sure he gets it to you today
[17:29] <davidm> Right now I have ~20 items to be scheduled
[17:30] <pat_mcgowan> davidm, hi
[17:30] <davidm> I'm hoping some of his are overlaps to mine.
[17:30] <davidm> Hi pat_mcgowan 
[17:30] <davidm> We were just tlking about you  :-)
[17:30] <pat_mcgowan> I have a list, and I am sure there will be much overlap
[17:30] <pat_mcgowan> I was planning to send it after the next meeting
[17:30] <davidm> Can you pop it into email to me? I'm going to commit the schedule today.  Thanks
[17:31] <pat_mcgowan> will do
[17:31] <davidm> Perfect
[17:31] <davidm> [action] pat_mcgowan to send davidm scheduling list.
[17:31] <MootBot> ACTION received:  pat_mcgowan to send davidm scheduling list. 
[17:31] <bspencer> uds schedule is on a wiki ?  or how is it created?
[17:32] <davidm> [action] davidm to commit schedule for UDS by Thursday
[17:32] <MootBot> ACTION received:  davidm to commit schedule for UDS by Thursday 
[17:32] <davidm> OK, is that it for schedule so far?
[17:32] <bspencer> is there already a posted schedule, or is there nothing until this action item is done?
[17:32] <davidm> The next open action was: "davidm, look into what and and how to have status meetings"
[17:33] <pat_mcgowan> bspencer, it is on a wiki, but no mobile items scheduled yet
[17:33] <davidm> bspencer, noting until this is done, but I can send you a copy of the items later today.
[17:33] <davidm> s/noting/nothing/
[17:33] <bspencer> I can wait ... just want to make sure I'm there at the right places/times
[17:34] <davidm> Since I'm new I'm working with someone who knows how to get things posted, and I've been holding off for rustyl's input
[17:35] <bspencer> ok.  I'll ping him about it
[17:35] <davidm> On the next open issue, we will have IRC access at UDS so I will schedule time for this meeting in the agenda
[17:35] <davidm> As to the later phone call, I'm working on that one still
[17:36] <davidm> OK, as to the next open item we got a bit out of sequence earlier :-) but"Don_Johnson to investigate USB client issues."
[17:37] <kyleN> me bad ;)
[17:37] <davidm> [action] davidm to figure out issues around Intel call
[17:37] <MootBot> ACTION received:  davidm to figure out issues around Intel call 
[17:37] <Don_Johnson> I included the USB client release notes in this week's status report.
[17:37] <Don_Johnson> And now Kyle has more questions for me to follow up on.
[17:37] <davidm> kyleN, np, you'll find I'm a bulldog on stuff it will get done :-) I won't forget if it's on my status/wiki page.
[17:38] <davidm> Don_Johnson, any other action item besides the one already committed?
[17:38] <Don_Johnson> So next step is to follow up with USB C developers and get a complete description of what they are delivering.
[17:39] <Don_Johnson> No I don't think there are any additional action items relative to USB C
[17:39] <davidm> Good enough
[17:39] <davidm> kyleN, any thing else relating to this old action item?
[17:40] <kyleN> I'd like the core and mobile teams to chime in at some point re: what functionality they think a MID needs to be succesful
[17:40] <bspencer> kyleN: for USB in particular?
[17:40] <kyleN> s/succesful/successful
[17:41] <kyleN> yes. the basic use case(s)
[17:41] <bspencer> kyleN: thanks for the spelling correction :P
[17:41] <bspencer> kyleN: ok.  I have some basic ones related to media syncing
[17:41] <bspencer> should email to you?
[17:42] <kyleN> bspencer: the list, if you please
[17:42] <bspencer> yep
[17:42] <bspencer> I just meant vs. updating a wiki directly
[17:43] <smagoun> wiki updates are only good if people know that the wiki was updated
[17:43] <davidm> Though it's handy if they subscribe to a page, then they get notices.
[17:43] <davidm> Ok are we ready for the next topic?
[17:43] <kyleN> I am
[17:44] <davidm> [topic] Current Items: Testing + running on an 800x480 screen (smagoun)
[17:44] <MootBot> New Topic:  Current Items: Testing + running on an 800x480 screen (smagoun) 
[17:44] <davidm> smagoun it's open to you..
[17:44] <smagoun> we put a recent build onto a device with an 800x480 screen, and there was a lot of broken stuff
[17:44] <smagoun> Primarily it was things not fitting onscreen
[17:44] <bspencer> smagoun: home screen mainly?
[17:45] <smagoun> (dialogs, games, apps in the home plugin, etc)
[17:45] <Sciri> Mostly apps; dialog boxes taller than the screen.
[17:45] <Sciri> Wi-Fi config, control panels, etc.
[17:45] <bspencer> it has been a few weeks since we've worked at that resolution
[17:45] <smagoun> Since 800x480 is a supported resolution, people need to test their apps at that res
[17:45] <bspencer> I doubt if ToddBrandt (our control panel guy) has ever tried 800x480
[17:45] <bspencer> :-\
[17:45] <smagoun> bspencer: yes, that's the problem :)
[17:45] <bspencer> smagoun: agree
[17:45] <pat_mcgowan> I have seen 5-10 requests for proposals, and all have been at this resolution
[17:45] <bspencer> the devil himself.
[17:46] <bfiller> can we make ume-start-xephyr default to 800x480?
[17:46] <bspencer> ToddBrandt: we were just discussing how many things don't work on 800x480
[17:46] <bspencer> bfiller: really?  ... hm..  How about a cmd-line parameter?
[17:46] <Sciri> Or are there command line switches to launch ume-start-xephyr in different resolutions?
[17:46] <ToddBrandt> bspencer: I sure don't
[17:46] <bfiller> bspencer: cmd line would be good
[17:46] <smagoun> You can edit ume-xephyr-start to do the right thing
[17:47] <Sciri> bfiller/bspencer: Gary and I were just discussion adding command line resolutions to ume-xephyr-start.
[17:47] <smagoun> but a default would be better for us (not so good for people on q1s perhaps?)
[17:47] <bspencer> I'll update to accept a WxH input
[17:47] <bspencer> I can make the default 800x480 to shake people up
[17:48] <bspencer> (like myself)
[17:48] <smagoun> bspencer: thanks, that will be a bit help
[17:48] <kyleN> bspencer: +1
[17:48] <ToddBrandt> bspencer: the screen resolution dialog supports 800x600 and 640x480, both of which aren't widescreen and don't look right on t6he samsung, I'll have to investigate how to add 800x480
[17:48] <bspencer> ToddBrandt: does it have 1024x600 ?
[17:48] <Sciri> bspencer: That'd be outstanding. :) Force people to at least see it in 800x480 once before they start using the WxH parameter to go back to their favorite resolution. ;)
[17:48] <ToddBrandt> bspencer: yes, 1024x600 is the default
[17:48] <smagoun> ToddBrandt: I thought the screen res dialog crashed hildon desktop?
[17:49] <bspencer> smagoun: details  :)
[17:49] <ToddBrandt> smagoun: It does and we removed it for aplpha as there were higher priority bugs, but I can fix that crash this week
[17:50] <smagoun> Do we really need it at all outside of Xephyr? I think it's unlikely MID users will want anything but the device's native resolution
[17:50] <bspencer> smagoun: not sure a single device will support both at this point
[17:51] <bspencer> and changing screen res isn't likely to change the Xephyr resolution
[17:51] <bspencer> (not sure about that...)
[17:51] <smagoun> right, therefore we don't need the applet at all...right?
[17:51] <pat_mcgowan> right
[17:51] <ToddBrandt> smagoun: some of the games might look better in a smaller resolution if they don't support 1024x600
[17:51] <bspencer> I don't know.
[17:51] <ToddBrandt> just a thought
[17:52] <smagoun> ToddBrandt: good thought. The game should do that automatically.
[17:52] <Sciri> Shouldn't the game do that automatically though? Users aren't going to want to know how to switch resolutions.
[17:52] <Sciri> Oh...jynx... :)
[17:53] <bspencer> ok.  we'll chat about it.  Might be useful to find out why it is crashing
[17:53] <lool> (Some video players do this too (I think mplayer did this for a while when going to full screen); not sure it's a win though)
[17:54] <bspencer> if we have a good zooming capability (e.g in the browser or text readers) then it isn't needed I think
[17:54] <bspencer> but on a device like the Sony UX, I use it often when reading 
[17:54] <bspencer> cause I can't see .01px font
[17:55] <davidm> need a better magnifying glass? ;-P
[17:55] <kyleN> again, maybe it's an app level capability
[17:55] <bspencer> it would be nice to have a system-level zoom feature (wish list)
[17:56] <davidm> five minute warning. I have another meeting to run to .....
[17:56] <bspencer> davidm: we're done with this topic  
[17:56] <davidm> K
[17:57] <davidm> In that case I added a quick question if there were any UDS attendance changes to topic additions.
[17:58] <davidm> [topic] UDS  UDS attendance changes or UDS topic additions
[17:58] <MootBot> New Topic:  UDS  UDS attendance changes or UDS topic additions 
[17:58] <davidm> If there are none then I can close the meeting.
[17:58] <HappyCamp_laptop> where is the list of UME topics for UDS?
[17:58] <HappyCamp_laptop> I will be there along with bspencer 
[17:58] <bspencer> davidm: Intel:  Bob is there Mon-Thu.   I don't know if rusty is coming.  JohnV will be there Sun-Thu.
[17:59] <HappyCamp_laptop> I am JohnV
[17:59] <davidm> I can mail a copy of the UDS topics, they will be posted I hope today.
[17:59] <pat_mcgowan> davidm, I sent you my list
[17:59] <davidm> I was holding for input from Rusty
[18:00] <davidm> pat_mcgowan, thanks
[18:00] <davidm> I'll merge the lists and get them moving along into the queue.  And I'll post them to the mailing list.
[18:00] <davidm> Any last items?
[18:00] <rustyl> i'm trying to do the multiple meetings at once thing... as for UDS, i don't have an answer if i will be able to attend yet
[18:01] <davidm> rustyl, OK, I'll rearrange things as needed if possible if you can attend.
[18:01] <davidm> If thats it I'll close the meeting.
[18:01] <davidm> Going once?
[18:02] <davidm> Twice?
[18:02] <lool> Thanks
[18:02] <davidm> Gone
[18:02] <davidm> #endmeeting
[18:02] <MootBot> Meeting finished at 18:02.