[00:56] <GrueMaster> davidm: ping
[00:57] <StevenK> GrueMaster: There's no point pinging him, he disconnected 5 minutes ago
[00:57] <GrueMaster> Yea, I just noticed that.
[00:57] <GrueMaster> davidm :  question re: beta3
[00:57] <davidm> GrueMaster, yes?
[00:58] <bspencer> lool,  when is our meeting supposed to be wrt moblin applets?
[00:58] <GrueMaster> video drivers are at build 0007.  Didn't you guys get newer drivers?
[00:59] <davidm> Not in time for the beta, we locked better then a week ago
[00:59] <GrueMaster> Oh.
[00:59] <GrueMaster> I just got the beta today.
[01:00] <GrueMaster> Didn't know it was a week old.
[01:00] <GrueMaster> ok
[01:08] <davidm> We locked the build for the WiMAX stuff but finally built because WiMAX did not make it.  
[01:09] <davidm> WiMAX was a pain, but they got it finally and now we have to remove it....
[06:31] <dholbach> good morning
[12:27] <lool> Hmm yesterday, the battery applet would segfault for me when I clicked on it, but now it wont at full charge
[12:47] <kennyyu> hi there, i wonder if i can get the firefox source code (for UME) because of my academic research purpose? is it available now?
[12:48] <dns53>  apt-get source packagename?
[12:57] <kennyyu> dns53: thanks... hmm, I just wonder why I cannot download the code from there --> https://blueprints.launchpad.net/ubuntu/+spec/mobile-browser   :-(
[13:04] <dns53> the package is actually midbrowser https://blueprints.launchpad.net/ubuntu/+spec/mobile-browser for the launcpad entry, git seems to be http://www.moblin.org/repos/projects/mobile-browser.git/ 
[13:12] <Roj> hi
[13:12] <dns53> hi
[13:13] <Roj> i have a Asus r2h and want to get involved with the ubuntu mobile testing
[13:13] <Roj> have i found the right community?
[13:14] <dns53> well this channel is quiet, i'm here trying to get it installed on my eeepc
[13:15] <Roj> ah ok, have you tried gOS rocket?
[13:15] <Roj> or Linpus?
[13:15] <dns53> not yet,i have a xubuntu with hardy
[13:16] <Roj> both kind of work but the ubuntu mobile release looks interesting to me
[16:36] <kennyyu> dns53: i see. I'll have a look! :)
[17:04] <lool> meeting is in one hour right?
[17:05] <Don_Johnson> I think David left it on UTS, and did not do any daylight saving time adjustments, so you are probably right
[17:06] <kyleN> lool, that's my guess
[17:06] <lool> Don_Johnson: That's my understanding as well; I added an item to move it one hour earlier to the agenda
[17:07] <Don_Johnson> Good, I have a regulary conflict in 1 hour, so I won't be able to make it at that time.
[17:09] <bspencer> lool, dumb Q.  Our weekly ume meeting is at 10amPDT now -- not 9am right?  :)
[17:09] <bspencer> lool, also, are we meeting tomorrow IRC 9am PDT?
[17:09] <davidm> I've had the meeting pegged to 17:00 UTC and not floating.  We can adjust the meeting to 16:00 UTC in this meeting.
[17:10] <bspencer> lool, or I think I was to get a bridge.
[17:10] <bspencer> davidm, right.  Old habit I was rushing to get here by 9am.
[17:11] <davidm> Well there is a aganda item to move it to now so we can talk about it.  It hits at a bad time for those in Europe now.
[17:12] <davidm> And I love google since it moved the meeting to now for me :-/ but I'm fixing that.
[17:14] <lool> bspencer: You were to get a bridge for friday, right?
[17:57] <davidm> Almost time for the meeting.
[18:01] <mawhalen> Rusty
[18:01] <mawhalen> feeling better?
[18:01] <davidm> We are missing mootbot so I'll just post logs later
[18:01] <davidm> it's off line at the moment.  So lets bring the meeting to order
[18:01] <lool> Pff Mootbot is not very reliable
[18:01] <rustyl_> mawhalen, not really
[18:02] <lool> rustyl_: Ah you were sick as well
[18:02] <mawhalen> FYI - John (happycamp) is out of the office today
[18:02] <rustyl_> lool, yea, this sucks
[18:02] <davidm> First action from 27 March then
[18:02] <davidm> #startmeeting
[18:03] <davidm> #startmeeting
[18:04] <davidm> I think mootbot will join us soon
[18:04] <MootBot> Meeting started at 19:02. The chair is davidm.
[18:04] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[18:04] <MootBot> davidm, There is already a meeting in progress.
[18:04] <davidm> OK mootbot is here so 
[18:04] <davidm> #topic kyleN to look into hildon-help; what's is useful for and whether we should package it for UME
[18:04] <kyleN> I have not investigated hildon-help yet. Yes, it needs to be done, but with current daily priorities it won't be done immediately. Therefore, I'd like to remove it from the carried action items for now.   
[18:04] <lool> davidm: #topic, not /topic :)
[18:05] <davidm> lool, yea I blew it
[18:05] <davidm> kyleN, OK done.
[18:05] <kyleN> thx
[18:05] <mabbas> #topic
[18:05] <davidm> #topic lool review progress on Hildon 2.0 updates next week
[18:06] <lool> So, smagoun is the only one around I fear
[18:06] <smagoun> lool: no progress on this one
[18:06] <lool> agoliveira tried updating sapwood, but he didn't manage to pull history
[18:06] <smagoun> I don't think bfiller has had a chance to get to his part either
[18:07] <lool> I think I'll start picking updates from other people to get stuff in hardy in the coming weeks
[18:07] <lool> I wish people with assigned updates could do one to see how it goes with bzr vcs-import and all
[18:07] <lool> So davidm, please carry on
[18:07] <davidm> [topic] lool review progress on Hildon 2.0 updates next week
[18:07] <MootBot> New Topic:  lool review progress on Hildon 2.0 updates next week 
[18:07] <davidm> lool, will do, 
[18:08] <davidm> I just replayed the topic to get it into mootbot
[18:08] <davidm> [topic] lool to document tips for Hildon 2.0 updates on Hildon 2.0 wiki page
[18:08] <MootBot> New Topic:  lool to document tips for Hildon 2.0 updates on Hildon 2.0 wiki page 
[18:08] <lool> See bottom of https://wiki.ubuntu.com/MobileAndEmbedded/Hildon2.0
[18:08] <lool> It's a bit raw, but it's what I did :)
[18:08] <lool> I'm happy to clarify with anybody who needs help
[18:09] <davidm> [link] https://wiki.ubuntu.com/MobileAndEmbedded/Hildon2.0
[18:09] <MootBot> LINK received:  https://wiki.ubuntu.com/MobileAndEmbedded/Hildon2.0 
[18:09] <davidm> lool, carry on?
[18:09] <lool> No, it's done; you can move on to next topic
[18:09] <davidm> [topic] lool to document tarball release + ppa upload process and patch 
[18:09] <MootBot> New Topic:  lool to document tarball release + ppa upload process and patch  
[18:10] <lool> I've wikified my notes and sent them to rustyl_; as they were longer than I thought, I think it's best to get some feedback from rustyl_ and then moving to the wiki
[18:10] <lool> rustyl_ only got them yesterday though, so I suppose we could make that an action for me for next week
[18:10] <davidm> OK
[18:11] <lool> This is just a one shot procedure, not very interesting to keep on the wiki forever, but we'll remove the page later on
[18:11] <davidm> [action] lool to document tarball release + ppa upload process and patch addition + submission process [cted] [cted scheduled for Friday the 28th][cted]
[18:11] <MootBot> ACTION received:  lool to document tarball release + ppa upload process and patch addition + submission process [cted] [cted scheduled for Friday the 28th][cted] 
[18:11] <lool> [action] (lool) add doc on moving to tarball releases for moblin modules to wiki
[18:11] <lool> Hmm ok
[18:11] <davidm> [action] (lool) add doc on moving to tarball releases for moblin modules to wiki
[18:11] <MootBot> ACTION received:  (lool) add doc on moving to tarball releases for moblin modules to wiki 
[18:12] <lool> Well the doc is ready, but I'll move it to the wiki next week
[18:12] <lool> right
[18:12] <davidm> I'll clean later NP
[18:12] <lool> thanks
[18:12] <lool> You can skip the next topic, it's the same
[18:12] <davidm> agree
[18:12] <davidm> next two actually
[18:13] <davidm> [topic] bspencer to list i18n status for Moblin project 
[18:13] <MootBot> New Topic:  bspencer to list i18n status for Moblin project  
[18:13] <lool> davidm: Well i'd like to keep the action on rustyl_, even if he had no chance to do it this week :)
[18:13] <lool> rustyl_: (if you don't mind)
[18:13] <davidm> I'll make it so
[18:13] <lool> bspencer: 19:13 < davidm> [topic] bspencer to list i18n status for Moblin project 
[18:13] <lool> bspencer: You come just on time :)
[18:14] <davidm> [action] #
[18:14] <davidm> rustyl_ to assign ppa packages updates for the new tarball based release process [cted as blocked by lool last week and the week before that...][cted]
[18:14] <MootBot> ACTION received:  # 
[18:14] <bspencer> lool: oy, not completed
[18:14] <davidm> [action] rustyl_ to assign ppa packages updates for the new tarball based release process [cted as blocked by lool last week and the week before that...][cted]
[18:14] <MootBot> ACTION received:  rustyl_ to assign ppa packages updates for the new tarball based release process [cted as blocked by lool last week and the week before that...][cted] 
[18:14] <bspencer> lool: I can list what I know here, but I think you wanted an email
[18:14] <kyleN> here comes my standard remard: ;) we need all apps i8nized, and soonish
[18:15] <kyleN> remark
[18:15] <mawhalen> bspencer: what is holding it up?
[18:15] <bspencer> ToddBrandt: is moblin-applets i18n?
[18:15] <bspencer> mawhalen: nothing -- I just forgot to send the email
[18:15] <lool> bspencer: I think kyleN asked for it
[18:15] <kyleN> the packages should be set up for intltool so they generated tempaltes
[18:16] <kyleN> and the code should be set up for gettext
[18:16] <kyleN> darn fingers, misbehaving again ;)
[18:16] <bspencer> kyleN: lool   is Hildon already for i18n per these requireemnts?
[18:16] <lool> bspencer: Hmm Hildon is special
[18:16] <bspencer> moblin media is, I know, except for a couple of bugs that may already have been fixed
[18:17] <kyleN> bspencer: hildon is not. it is a more complex challenege. but this problem is known and being solved
[18:17] <bspencer> lool:  is Firefox special too?
[18:17] <lool> bspencer: Yes
[18:17] <bspencer> mid browser is also i18n, per Firefox mechanism.
[18:17] <lool> bspencer: But moblin-applets is a good standard example
[18:17] <bspencer> I don't know about moblin-applets.
[18:17] <lool> I reviewed it, and it seemed structured to do it
[18:17] <lool> Can't tell whether all strings were marked as translatable or not
[18:17] <bspencer> Home screen is the one I'm not sure about
[18:18] <bspencer> The icons and names come from freedesktop.org calls now, but I haven't verified the i18n-ness
[18:18] <kyleN> bspencer: can you please address the problem on both fronts: intltool AND code/gettext
[18:18] <lool> bspencer: But you're not using message ids for strings in any other package than midbrowser at moblin.org, so it would be nice if you could make sure all other moblin.org projects are i18ned
[18:19] <lool> Run them in French
[18:19] <bspencer> lool: yes.  My action item.
[18:19] <lool> kyleN, bspencer, davidm: do let's carry on action
[18:19] <davidm> OK
[18:19] <kyleN> ok
[18:19] <lool> [action] bspencer to report on i18n of moblin.org modules [cted]
[18:19] <davidm> [action] bspencer to report on i18n of moblin.org modules [cted]
[18:19] <MootBot> ACTION received:  bspencer to report on i18n of moblin.org modules [cted] 
[18:20] <davidm> OK that is the end of old business
[18:20] <davidm> Current items
[18:20] <kyleN> although I wish the wording wasn't "report" but was "implement intltool in packages and gettext in code"
[18:21] <bspencer> kyleN: did you document this somewhere?
[18:21] <lool> kyleN: Well I think it's clear that they need to be i18ned, but we wont implement it during the meeting so we can only report on status ;)
[18:21]  * bspencer recalls seeing something
[18:21] <lool> bspencer: Two wiki pages are available on the topic
[18:21] <lool> bspencer: As mentionned in last week's links
[18:21] <bspencer> ok.  you can move on while I look.
[18:21] <lool> http://people.ubuntu.com/~davidm/mootbot/meetings/ubuntu-mobile.20080327_1801.html
[18:21] <MootBot> LINK received:  http://people.ubuntu.com/~davidm/mootbot/meetings/ubuntu-mobile.20080327_1801.html 
[18:21] <bspencer> lool: thx.
[18:21] <lool> See the last two links
[18:22] <davidm> [topic] (lool) propose to move meeting one hour earlier (it's summer \o/) 
[18:22] <MootBot> New Topic:  (lool) propose to move meeting one hour earlier (it's summer \o/)  
[18:22] <lool> So I'd like to move the meeting by one hour
[18:22] <lool> I think this will fit everybody
[18:22] <davidm> This works for me.
[18:22] <bspencer> good for me
[18:22] <lool> In fact most people were expecting the meeting earlier ;)
[18:22] <cgregan> no conflict for me
[18:22] <davidm> I know Don Johnson would like this as he can't attend now.
[18:22] <lool> Let's do it!
[18:22] <davidm> Intel side comments?
[18:22] <mawhalen> I don't believe this is a problem, we used to have it an hour earlier
[18:23] <mawhalen> I'll reschedule it for Intel side
[18:23] <davidm> bspencer, mawhalen , thanks
[18:23] <davidm> [action] davidm to move meeting to 1 hour earler and notify all 
[18:23] <GrueMaster> For the most part, the people at Intel have adjusted to daylight savings time, so this would realign with that schedule.
[18:23] <MootBot> ACTION received:  davidm to move meeting to 1 hour earler and notify all  
[18:24] <davidm> [action] mawhalen to reschedule on Intel side 
[18:24] <MootBot> ACTION received:  mawhalen to reschedule on Intel side  
[18:24] <ToddBrandt> bspencer: sorry for the delay, yes moblin-applets is i18n
[18:24] <davidm> OK I think we are covered on that
[18:24] <davidm> [topic] (tonyespy) ppm: git tree out-of-date + write access; licensing question... 
[18:24] <MootBot> New Topic:  (tonyespy) ppm: git tree out-of-date + write access; licensing question...  
[18:25] <tonyespy> OK
[18:25] <tonyespy> There's been some recent interest in the ppm by our customer
[18:25] <tonyespy> and yet, the public git tree is not up-to-date
[18:25] <tonyespy> also, as there's been a request that canonical do some of the work...
[18:25] <lool> tonyespy: (you used rsync?)
[18:26] <tonyespy> i'd like to ask that we be granted write access to the tree
[18:26] <lool> tonyespy: (some git trees at moblin.org are broken / out of date via http)
[18:26] <tonyespy> lool:  i'll check
[18:26] <mawhalen> mabbas: are you around?
[18:26] <tonyespy> lool: i've been looking at the tree via the git web interface
[18:26] <mawhalen> he was
[18:27] <tonyespy> i've spoken with mabbas about this and he said that he'd update it this week...
[18:27] <lool> I guess the gitweb is always up to date
[18:27] <tonyespy> but i'd like to see this be a regular activity... not a once and a while thing
[18:27] <tonyespy> ...especially if we're going to be contributing to the development
[18:28] <mawhalen> Mohamed had joined last week and at the begin of this meeting - 
[18:28] <mawhalen> tonyespy: hae you sync'd with Mohamed, I know he was going to contact you about a script
[18:28] <mabbas> yes I am here
[18:29] <tonyespy> mawhalen: yes, we've been exchanging emails
[18:29] <tonyespy> mabbas: i brought up the topic that i'd like to see the public git tree for ppm be kept up to date
[18:29] <tonyespy> mabbas: and we would also like write access
[18:29] <mabbas> yes I will update by tomorrow
[18:29] <tonyespy> mabbas: especially if we're going to be contributing work
[18:30] <rustyl_> tonyespy, do you already have an account on moblin?
[18:30] <tonyespy> mabbas: after that, can you make sure it's kept up to date on a regular basis
[18:30] <tonyespy> rustyl_: not sure, but i'll check...
[18:30] <mabbas> yes it usually is
[18:31] <tonyespy> mabbas: the last tag was 0.7, the version in the ppa is 0.9
[18:31] <lool> rustyl_: Don't think so
[18:31] <rustyl_> tonyespy, lool, i don't see any type of *tony* or *eps*
[18:32] <rustyl_> in /home on moblin
[18:32] <tonyespy> rustyl_:  ok, i'll create one this afternoon
[18:32] <rustyl_> mabbas, do have an issue with adding another developer with write access?
[18:32] <mabbas> ok the gap here is small and maily to kick hardy build but I will make sure they are always update
[18:32] <mabbas> not at all
[18:33] <tonyespy> ok, i will create an account and then send details to mabbas
[18:33] <mabbas> as long we discuss thing before commit and this will go both way of cource
[18:33] <rustyl_> mawhalen, is HappyCamp_ubuntu HappyCamp on vacation still?
[18:33] <mawhalen> rustyl_: yes - happycamp is on vacation this week.
[18:33] <davidm> Are there any actions I need to track to next week here?
[18:33] <tonyespy> davidm: no
[18:34] <tonyespy> one more piece to the topic...
[18:34] <davidm> tonyespy, OK good enough
[18:34] <tonyespy> which may apply to more than just ppm
[18:34] <davidm> tonyespy, you have the floor
[18:34] <tonyespy> from my pov, ppm is in a way a replacement for gnome-power-manager ( ie. it does many of the same things )
[18:35] <tonyespy> yet it's licensed under a dual-license ( mit & gpl )
[18:35] <tonyespy> this prevents code from being pulled from pure gpl projects like gnome-power-mgr
[18:35] <tonyespy> was this intentional?
[18:35] <rustyl_> no, not intentional
[18:36] <tonyespy> can it be fixed?
[18:36]  * rustyl_ thinks
[18:36] <lool> Is it important if we lose the MIT part of the license?
[18:37] <tonyespy> there's suspicion (sic) that this might apply to other moblin projects as well...
[18:37] <lool> If you merge GPL code, just update the relevant headers in the source files you copy, debian/copyright, and the result of the combination will be GPL
[18:37] <lool> Just like GPM
[18:38] <tonyespy> lool: but isn't that confusing if the top-level of the project includes the mit license?
[18:38] <bspencer> I believe MIT was added to allow for the potential of someone to create a solution with proprietary bits.  But here it is biting us.
[18:38] <rustyl_> i think tonyespy is correct... you can't add GPL licensed code from some other project into a code base that is dual licensed with MIT
[18:38] <lool> Well in Debian/Ubuntu packages we very often have to deal with this; it's best if the toplevel licensing file is correctly indicating which files are MIT+GPL and which are only GPL
[18:39] <rustyl_> if it's a new file, then yea, that's not a problem
[18:39] <bspencer> lool: can you point us to an example?
[18:39] <lool> rustyl_: It makes the code base a mixture of dual licensed + single licensed code which is effectively gpl
[18:39] <rustyl_> the issue is an existing file
[18:39] <lool> bspencer: Looking for one
[18:39] <bspencer> tonyespy: do you already know that you are wanting to pull in gnome-power-mgr stuff?
[18:39] <bspencer> or just guessing you might want to someday
[18:39] <rustyl_> i.e. the user of PPM would not really have the right to use the specific file as MIT (and throw away the rights enforce from the other codebase)
[18:40] <lool> bspencer: http://packages.debian.org/changelogs/pool/main/v/vlc/current/copyright
[18:40] <tonyespy> bspencer: i'm guessing based on my code review
[18:40] <lool> Example of a very complex copyright file listing in details copyright holders and licenses
[18:41] <tonyespy> lool: the end result is still gpl though right???
[18:41] <lool> If each source file says what it's licensed under (MIT+GPL for historic files and GPL for copied files), and the toplevel file summarizes, that's fine
[18:41] <lool> tonyespy: Yes
[18:41] <rustyl_> tonyespy, lool, we need to loop this back through our process for getting approval for open sourcing the code to see if we can make the code pure GPL
[18:41] <lool> tonyespy: Naturally, if you copy GPL over, you make everything GPL
[18:41] <lool> rustyl_: You don't need to really
[18:41] <tonyespy> lool: so the question is whether or not that's ok w/intel
[18:41] <lool> rustyl_: But the question is whether you're happy with this particular module moving from dual licensing to effectively GPL
[18:42] <tonyespy> lgpl is another way to allow linking of proprietary code...
[18:42] <lool> You can't make GPL code LGPL
[18:42] <tonyespy> lool: right, sorry...
[18:42] <tonyespy> anyways, i wanted to raise the issue...  not decided it here.
[18:42] <rustyl_> tonyespy, let me narrow this down some... do you have a need to pull in GPL code on existing files, or will this always be new modules?
[18:44] <tonyespy> rustyl_: right now i don't have a specific piece of code in mind.  i brought this up after doing a design/code review of ppm
[18:44] <tonyespy> rustyl_: which does *a lot* of what gnome-power-manager already does....
[18:44] <tonyespy> rustyl_: and there are certain improvements that have been suggested...
[18:44] <tonyespy> rustyl_: which already exist elsewhere....
[18:45] <rustyl_> I ask because the current licensing model doesn't really have an issue with new modues.  The issue is if you want to pull in pure GPL into the core infrastructure code
[18:46] <tonyespy> rustyl_: i'm not sure it works that way...
[18:46] <tonyespy> rustyl_: the problem's not with the existing code's license...
[18:46] <tonyespy> rustyl_: it's with the license of the source code
[18:46] <tonyespy> rustyl_: no pun intended
[18:47] <tonyespy> rustyl_: should have read 'source of the code'
[18:47] <robr-desk> tonyespy, can you be specific about what improvements are being requested?
[18:48] <bspencer> tonyespy: maybe you could send some patches and we can make a decision as we see the need
[18:48] <rustyl_> well... in order to get permission to change the license I need a clear, rock solid argument or else our process will rip me to pieces.  We should try to articulate / better under stand this in an off-line email
[18:48] <bspencer> we're open to discuss a hange if it makes sense.
[18:49] <rustyl_> maybe this can be captured in a bug report?
[18:49] <tonyespy> bspencer, rustyl_, robr-desk: i've posted an analysis on the private intel/canonical wiki
[18:49] <bspencer> tonyespy: start with some patches you want, then let's discuss again next week.
[18:49] <rustyl_> and then let the discussion be documented in the bug?
[18:49] <tonyespy> i can send a link to y'all via email if you'd like
[18:50] <davidm> 10 minute warning
[18:50] <rustyl_> ok, wiki will work
[18:50] <tonyespy> sure... i've also added a bunch of bugs...
[18:50] <tonyespy> rustyl_: just search for PPMAnalysis
[18:50] <lool> on intel.wiki.c.c
[18:50] <mabbas> by the way I dont have access to this wiki so I need access to read tony comments
[18:50] <tonyespy> rustyl_: or take a look at the ppm buglist on launchpad
[18:51] <davidm> mabbas, mawhalen can get you access
[18:51] <mabbas> thanks
[18:51] <tonyespy> that's it for me, unless anyone else has comments / questions
[18:51] <rustyl_> tonyespy, BTW, about creating an account... go ahead and send me your username, email, and ssh public key, and I will create the account and give you write access while John is on vacation
[18:51] <tonyespy> rustyl_: ok, thanks
[18:51] <mawhalen> Yes - I can get them access
[18:51] <davidm> OK
[18:52] <davidm> I have no further items on the wiki page.
[18:52] <davidm> any last minute items?
[18:53] <davidm> OK going once................................
[18:54] <davidm> OK going twice...............
[18:55] <davidm> #endmeeting
[18:55] <MootBot> Meeting finished at 19:55.
[18:55] <lool> Thanks
[18:55] <lool> rustyl_: Do you have a public document on moblin.org licensing guidance?
[18:55] <lool> Like "this and that layer of this arch must be this license"
[18:56] <rustyl_> lool, no... each project has it's own license
[18:56] <lool> rustyl_: Ok, and did you particularly care about ppm being 100% MIT+GPL?
[18:56] <rustyl_> lool, i don't know
[18:56] <bspencer> lool: ppm is part of another project:  lesswatts
[18:56] <lool> Ohh right
[18:56] <bspencer> so we share the licensing decision with them.
[18:56] <lool> I understand why we were wondering
[18:57] <lool> Okay, makes sense to me now
[18:57] <rustyl_> lool, to answer that question I would need to revisit the original arguments for what license to use
[18:57] <lool> Ok, understood
[18:58]  * lool moves to confcall &
[19:57] <bspencer> bfiller, davidm   who is your marketing guy?  John...
[19:58] <davidm> Jon is
[19:58] <bspencer> yeah.  last name?
[19:58] <davidm> Jon Melamut
[19:58] <bspencer> thx
[19:58] <davidm> NP
[21:06] <inuka_desk> ping GrueMaster
[21:21] <GrueMaster> INUKA_DESK:PONG
[21:22] <GrueMaster> inuka_desk: Pong
[21:22] <GrueMaster> caps was on
[21:23] <inuka_desk> GrueMaster: ok for a moment there I thought you were screaming :) for the CIP stuff... I have come across an issue 
[21:23] <GrueMaster> Are you referring to the 7am meeting?
[21:24] <inuka_desk> if I play a certain clip twice helix dubs server freezes, plus there are 6 instance of helix ... .yes 
[21:24] <inuka_desk> the behavior is consistent for several driver builds of Beta9 so its definitely nothing to do with the build/image
[21:25] <GrueMaster> Did you see my earlier email?  If you could, try to document what you have and post it to the shared drive.  You should have r/w permissions.
[21:25] <inuka_desk> GrueMaster: is there anything special I should look at or try to copy over?
[21:26] <GrueMaster> I'm currently testing the latest helix and the latest PSB on the latest Ubuntu snapshot (Beta3).  As soon as I get them all loaded, I'll run some tests and see if I see the same thing.
[21:26] <inuka_desk> GrueMaster: ok I will send you  a link to the clip I used.
[21:26] <GrueMaster> If you have a particular media clip that hangs, put it in the media folder.
[21:26] <GrueMaster> That will work too.
[21:27] <GrueMaster> Just use my internal email.  This IM client is on an external network running off my Linux laptop.
[21:28] <inuka_desk> GrueMaster: ok
[21:30] <GrueMaster> got it
[21:35] <crevette> hey
[21:36] <crevette> is there a way to test the mobile ubuntu on a normal x86 machine ?
[21:37] <GrueMaster> There are a couple of ways.  One is to make a live-rw-usb image and boot it, the other is to use a virtual machine, like Virtualbox.
[21:38] <GrueMaster> YOu will need to tweek the /etc/X11/xorg-crownbeach.conf file as it is hardcoded to a specific video chip.
[23:50] <tonyespy> rustyl_: ping
[23:54] <rustyl_> tonyespy, yeap
[23:55] <tonyespy> rustyl_: how do i create an account on moblin?  all i can find is the dev mailing list?
[23:55] <rustyl_> you can't do it via the web site
[23:55] <tonyespy> ahhh...
[23:55] <tonyespy> that explains much
[23:55] <rustyl_> send me the user name you want, your email to associate with and public ssh key
[23:56] <tonyespy> ok, will do.  thanks.