[00:54] Mithrandir: lool : StevenK Question about the PPA. I was understanding the PPA to be used with Gutsy. Is that right? [01:17] bspencer: Right. [02:27] Mithrandir: lool ping [02:27] bspencer: Mithrandir is on holidays, and it has to be something like 2am for lool. What's up? [02:27] Howdy StevenK [02:27] * StevenK waves [02:27] I was trying to understand the PPAs [02:28] gutsy PPA and hardy PPA [02:28] actually my goal is to know what the hildon-desktop story is [02:28] we are trying to find the ubuntu-mobile hildon-desktop [02:28] hildon-desktop was uploaded to Hardy, and also to the Gutsy ubuntu-mobile PPA. [02:29] so they are the same now and forever? [02:29] They are not. [02:29] there is a Hardy PPA curiously enough, which has hildon-desktop [02:29] Which means a Hardy version was also uploaded to the PPA for some reason - I suspect so it actually existed. [02:30] PPAs are very easy to change, and while Hardy is in development, it is also fairly easy to change [02:31] OK. So if we are going to create a Moblin-OSV compliance spec, we will be looking at the Gutsy-PPA hildon-desktop since that is the only thing that works in an image today. [02:31] if/when we move to Hardy based images we can use that. [02:33] Right. Which makes it simple since they are both the same version. They can be updated in lockstep if you so wish it. [02:34] got it [02:34] thanks for the input [02:34] No problem. [02:34] * StevenK runs off to lunch, but with no idea of what to eat. [07:12] good morning [08:43] StevenK: Around? [08:44] StevenK: I just wanted to tell you that I'm switching from "let's kick modest and its deps until we have a build path and it runs" mode to "quiet" mode, where I'll basically work on other stuff. I think the tinymail/modest blockers are solved, but please ping me if you meet any new one [08:45] I'll pursue and bridge the upstream discussions I started when needs be [08:46] Hurray [08:46] I find that modest hangs and mis-behaves on my Q1 [08:47] StevenK: With gtkhtml? [08:47] StevenK: You absolutely need to use tinymail SVN though [08:47] The version you were basing of had bugs here [08:48] s/basing of/basing on === dholbach_ is now known as dholbach [12:25] lool: is there a package or bzr branch somewhere? [12:25] (or a backtrace of the crashes you got with mozembed :)) [12:36] asac: I didn't investigate them further; upstream says it's experimental code in modest [12:37] asac: I wasn't under the impression that they would be passionate about getting mdoest to work nicely with mozembed [12:37] asac: And there are like millions of warnings and errors on startup, so it would make sense to fix these instead IMO [12:37] asac: But if you like to build it, it's not too hard [12:38] asac: You'll need to build tinymail out of SVN with the single line change to configure.ac to add the unstable CFLAGS, and modest is about the same amount of changes [12:38] currently tinymail bails out here in camel [12:38] ../libtinymail-camel/bs/libbodystruct.a: could not read symbols: Bad value [12:38] SVN tinymail? [12:38] have you seen? [12:38] No [12:38] i use --with-platform=mozembed [12:38] aeh [12:38] maemo [12:38] :) [12:38] Big update it seems [12:38] I just svn uped [12:39] ok --enable-imap-part-fetch [12:39] i need i guess (reading the svn log) [12:40] lool: did modest upstream say that mozembed is experimental or gtkhtml? [12:40] mozembed backend is experimental in modest [12:41] And they recommend gtkhtml and it's what they use for maemo [12:41] asac: I get the same error you do [12:41] /usr/bin/ld: ../libtinymail-camel/bs/libbodystruct.a(bodystruct.o): relocation R_X86_64_32 against `a local symbol' can not be used when making a shared object; recompile with -fPIC [12:41] That's the actual error [12:42] Building with -fPIC now [12:43] let me know [12:43] ../../libtinymail-camel/.libs/libtinymail-camel-1.0.so: undefined reference to `camel_folder_get_cache_filename' [12:43] But at least it doesn't bail out in the same ugly way [12:44] i don't understand why to add -fPIC explicitly [12:44] I think it's needed on amd64 [12:44] ok i will get r3066 [12:47] wow ... the modest svn log looks like they don't care [12:47] * fixes, speedups [12:47] * fixes [12:47] * fixes all around [12:47] lol [12:47] :) [12:47] Yeah :-( [12:47] The debian/changelog is the same [12:47] asac: Fortunately, there's the debian/changelog [12:47] you really want to use that in mobile? [12:48] ok tinymail r3066 builds \o/ [12:49] oh modest already integrated the gtkmozembed_glue.cpp stuff [12:49] nice [12:50] asac: Yeah, almost everything merged [12:50] They didn't drop the .c file though [12:50] But modest is using some old ABI we don't have and I think it needs big work to be fully working [12:51] ABI or API ? [12:53] configure: error: you need to have either wpeditor or libwpeditor-plus installed [12:53] ?? [12:54] asac: ABI [12:54] asac: Like the deprecated Gtk+ signals [12:54] It's not visible in the API (and you can't easily check in configure, especially when cross compiling) and checking at runtime would be impracticatl [12:54] ah [12:55] asac: You need wpeditor-dev [12:55] where is that? [12:55] not in hardy for me [12:55] asac: And you should remove libwpeditor-plus* if you have them [12:55] i have nothing :) [12:55] asac: http://people.ubuntu.com/~lool/packages/wpeditor/2.12-0ubuntu1/hardy/ [12:55] thanks [12:56] asac: If you're not running latest p.u.c crack, you're not "in" [12:56] asac: Hi. Do you know any "Openoffice hacking for dummies"? I'm looking at the code and don't even know where to start. This thing uuencoded (God know why) is freaking me out. [12:57] installed ... no going ahead [12:57] agoliveira: i am not openoffice :) ... mozilla is my domain [12:57] asac: Ooops, indeed, sorry :) [12:57] np [12:58] lool: hildon-help or osso-help ? [12:58] where to get that? [12:58] agoliveira: calc is the guy is you want [12:58] StevenK: Ah, thanks. [12:58] asac: I don't think you need anything [12:58] lool: nm ... i found libhildonhelp-dev [12:58] well modest with platform=maemo ... needs it [12:59] Yeah, no -help, but libhd-help-dev indeed [12:59] (I dpkg -led \*help) [13:01] ... + mime + fm :) ... now its building [13:07] lool: http://paste.ubuntu.com/2506/ [13:07] otherwise it fails because of fatal warnings [13:11] wow ... modest starts [13:12] modest works :-D [13:15] now lets see with mozembed [13:21] asac: Of course it works! You didn't see my screenshot? :) [13:22] asac: I've sent a patch for the has_error thing already; I thought it was merged, grmblb [13:22] asac: But Dirk is aware of it, so hopefully should be fixed soon [13:35] k [14:12] asac: I've sent the fpic issue and the subsequent undefined symbol error to tinymail-devel@; I couldn't solve them rapidly enough, and I don't want to dig further since both are the result of recent changes [14:13] sure === cprov is now known as cprov-lunch === cprov-lunch is now known as cprov [16:55] lool: who is the modest maintainer? [16:55] (who did you send the patch to?) [16:56] asac: I am a modest mainteiner! [16:56] asac: Oh, you mean *the* modest mainteiner :) [16:57] the upstream maintainer i mean :) [16:57] ;) [16:57] asac: To Dirk, as found in Debian changelog [16:57] asac: Dirk-Jan Binnema@nokia [16:57] asac: I'm sending stuff to modest-devel@ now though [16:58] asac: I couldn't let the joke oprtunity pass ;) [16:58] agoliveira: :) [16:58] agoliveira: yeah :) [16:58] Almost time to start our weekly meeting... [16:59] lool: Is there a working archive for modest-devel? [17:00] i thought modest used tiny? if so the maintainer is p van hoof i think http://pvanhoof.be/blog/ [17:00] smagoun: I don't think so, I wondered the same :-( [17:00] Are we ready to start? [17:00] #startmeeting [17:00] Meeting started at 17:00. The chair is davidm. [17:00] Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE] [17:01] Action items from last week, stating from the top [17:01] [topic] lool to take a look at bug # 172426 and see if he can reproduce it. [17:01] New Topic: lool to take a look at bug # 172426 and see if he can reproduce it. [17:01] lool, any luck? [17:03] davidm: No, I didn't look at it [17:03] lool, carry it over until next week? [17:03] davidm: horace from Intel took and look and could only reproduce part of it [17:03] I expect to have little time to look at it next week, but will resume work on it the following week [17:04] davidm: Yes [17:04] lool, can you exchange email with horace to see what he knows? [17:04] lool: horace checked in a fix into moblin hildon-desktop. Isn't he supposed to commit changes to launchpad? [17:04] asac: [ Removing make installed files fixed the second tinymail build failure for me (see tinymail-devel) ] [17:05] bfiller: Bah [17:05] [action] carry over lool to take a look at bug # 172426 and see if he can reproduce it. until Dec 20th. [17:05] ACTION received: carry over lool to take a look at bug # 172426 and see if he can reproduce it. until Dec 20th. [17:05] davidm: We discussed this shortly with bfiller, and it seems Horace addressed another bug, but not the bug Bill is seeing and Horace and I don't [17:05] OK [17:05] Thanks [17:05] bfiller: They should IMO [17:05] new topic then [17:05] bfiller: Why they don't escapes me [17:06] Where's Bob? [17:06] [topic] bfiller to for looking into a better solution for a banner to be [17:06] New Topic: bfiller to for looking into a better solution for a banner to be [17:06] Where's Horace? [17:06] lool: Horace is in China I think [17:06] Bob Spencer? [17:06] He is in China working right now - [17:06] It's the middle of the night [17:06] Rusty is there too [17:06] There is some meeting today that is keep Don Johnson from attending today. [17:06] Is Moblin having weekly meetings where we should discuss using bzr? [17:06] davidm: I have temp solution for problem, waiting for hildon-desktop problems to be resolved [17:07] mawhalen: Thanks for the info [17:07] bfiller, Do I need to carry over again or are you good? [17:07] davidm: I will follow up directly with bspencer, so I you don't need to carry over [17:07] OK, thanks [17:07] mawhalen: Tell them to try the marinated snake! :) [17:08] and scorpions [17:08] [topic] Don_Johnson to get this written up (USB info) with some use cases and put it on the mail list. [17:08] New Topic: Don_Johnson to get this written up (USB info) with some use cases and put it on the mail list. [17:08] I'll take this, Don sent out the USB info and I am having it tested. We have the client side files now and will see how it goes. [17:08] lool: ok i added the (new/current) modest and tinymail patches to: https://code.edge.launchpad.net/~mozillateam/xulrunner/xulrunner-porting ... as you said modest was completely broken :) [17:09] So I'm going to drop this action as complete. [17:09] asac: Meeting now. [17:09] I'm going to skip "bspencer & Don_Johnson to clarify the process and deliverables" since neither of them are here [17:10] asac: Well upstream said that [17:10] [topic] bspencer & horaceli to verify the ubuntu branch works [17:10] New Topic: bspencer & horaceli to verify the ubuntu branch works [17:10] sorry for the interruption [17:10] asac, NP [17:10] asac: Modest needs a lot of non-mozembed fixing and upstream says the mozembed part is experimental, so it seems we should focus on gtkhtml as a starter (given current constraint of the mobile team) [17:11] whoops both are not here either. Next topic then [17:11] Carry on? [17:11] [action] carry over to next week: bspencer & Don_Johnson to clarify the process and deliverables [17:11] ACTION received: carry over to next week: bspencer & Don_Johnson to clarify the process and deliverables [17:11] * agoliveira thinks that's going to be a quick meeting :) [17:11] [action] continue to hold open: bspencer & horaceli to verify the ubuntu branch works [17:11] ACTION received: continue to hold open: bspencer & horaceli to verify the ubuntu branch works [17:11] * lool goes filing surprize agenda items [17:11] [topic] smagoun Since my group needs it, I'll take an action item to test overriding exa for a gutsy psb backport [17:11] New Topic: smagoun Since my group needs it, I'll take an action item to test overriding exa for a gutsy psb backport [17:11] Working on it today. Nothing to report, other than my current build crashes [17:11] * agoliveira looks very hard towards Paris... [17:12] carry the action forward? [17:12] haven't had a chance to root-cause yet [17:12] davidm: sure [17:12] [action] carry over smagoun Since my group needs it, I'll take an action item to test overriding exa for a gutsy psb backport. In progress. [17:12] ACTION received: carry over smagoun Since my group needs it, I'll take an action item to test overriding exa for a gutsy psb backport. In progress. [17:12] next action then? [17:13] [topic] kyleN to test h-i-m and get back to StevenK on status Mobile Application spec: (issue documentation is light) [17:13] New Topic: kyleN to test h-i-m and get back to StevenK on status Mobile Application spec: (issue documentation is light) [17:13] I haven't had a chance to try this out yet. Our project is currently expecting to use SCIM though. [17:13] OK, carry over then, or drop? [17:13] it's onmy list to check, so I'd say drop it from the carry over [17:14] OK, will do. [17:14] The next topic is for Amit and he is on holiday so it's a skip [17:14] [topic] amitk to update hardy ppa with drivers [17:14] New Topic: amitk to update hardy ppa with drivers [17:15] I don't know if this got done or not. [17:15] [action] carry over amitk to update hardy ppa with drivers [17:15] ACTION received: carry over amitk to update hardy ppa with drivers [17:15] That concludes prior actions. [17:15] New topics next [17:15] [topic] smagoun - Better tracking of LPIA build failures (correct versions of evince, freetype1, tasks, probably others didn't get into gutsy/lpia because of various build failures: [WWW] https://edge.launchpad.net/ubuntu/gutsy/lpia/+builds) [17:15] New Topic: smagoun - Better tracking of LPIA build failures (correct versions of evince, freetype1, tasks, probably others didn't get into gutsy/lpia because of various build failures: [WWW] https://edge.launchpad.net/ubuntu/gutsy/lpia/+builds) [17:15] We've discovered - the hard way - that a number of LPIA builds failed, so correct versions of certain packages didn't make it into gutsy. For example, the gutsy/lpia versions of freetype1, evince, + tasks are out-of-date. [17:16] We'd like to make sure this doesn't happen in the future. What's the best way to monitor LPIA builds to make sure they're sync'ed with i386? [17:17] agoliveira, lool any thoughts? [17:17] davidm: Sorry, no. I don't know how this works. SOmeone from the build team is needed I guess. [17:18] I remember that Tollef was looking into this. [17:18] He's on holiday this week, right? [17:18] Yes and I don't know where it's at, Tollef is on holiday, so I'll look into it and query the build team [17:18] smagoun, yes he is. [17:19] [action] davidm to query build team on best way to monitor the i386 builds and the LPIA builds to stay in sync. [17:19] ACTION received: davidm to query build team on best way to monitor the i386 builds and the LPIA builds to stay in sync. [17:19] I'll also query tollef but he is on a real vacation and pretty much out of contact. [17:19] next topic [17:19] (I'm personally of the opinion that this is regular QA) [17:19] (On our archive) [17:20] I sent him an email days ago: no response. [17:20] It should be covered by some existing process or docs (I would be surprized if it isn't), but I'm not too familiar to tell which [17:20] I figured it might be a special case since LPIA is in ports.ubuntu.com [17:20] lool thanks, I'll check [17:21] [topic] ChickenCutlass - Discuss reasons behind the decision to use acpid, custom moblin battery applet instead of using gnome-power-manager and its status bar applet. [17:21] New Topic: ChickenCutlass - Discuss reasons behind the decision to use acpid, custom moblin battery applet instead of using gnome-power-manager and its status bar applet. [17:21] I just wanted to get some info from Intel about how the decision was made to use a custom battery applet as well as acpid and not use the existing gnome-power-manager [17:21] I think this might be a question for ToddBrandt [17:22] There seems to be a bunch of duplicate code [17:22] more to maintain [17:22] ToddBrandt, comments? [17:22] I see he's in the room but I'm not sure if he is watching. [17:23] can anyone from Intel ping him? [17:23] >14 hours 20 minutes [17:23] I will [17:23] don't think he's here... [17:24] ChickenCutlass, can you send him an email with your question? [17:24] davidm, ok -- I will post to the list [17:24] Basically Intel is forking a lot of stuff and distros don't like forks [17:24] lool, exactly [17:24] Good point. [17:25] We're going to have a very hard time trying to integrate it back. [17:25] *if* [17:25] [action] Michael Frey to post " Discuss reasons behind the decision to use acpid, custom moblin battery applet instead of using gnome-power-manager and its status bar applet" question to the list. [17:25] ACTION received: Michael Frey to post " Discuss reasons behind the decision to use acpid, custom moblin battery applet instead of using gnome-power-manager and its status bar applet" question to the list. [17:26] [topic] smagoun - startp performance update from agoliveira [17:26] New Topic: smagoun - startp performance update from agoliveira [17:26] I'd heard that agoliveira was measuring bootup time, any progress on that? [17:26] (measuring + finding improvements) [17:26] smagoun: Sorry, didn't have the chance to go into this yet. I made a few tests but nothing conclusive yet. [17:27] I expect to be able to do it early next week. [17:27] agoliveira: Did you manage to get bootchart working? [17:27] lool: It worked for us - apt-get install bootchart was all we needed [17:28] lool: On the Q1? yes. [17:28] But as I said, I didn't look into it very hard. [17:28] smagoun, agoliveira has been stuck on claws fixes and some other work, it's top on his list now. [17:28] thanks [17:28] NP [17:28] smagoun: Yeah, for me too, which is why I wonder [17:29] [action] agoliveira to report next week any findings on boot speed. [17:29] ACTION received: agoliveira to report next week any findings on boot speed. [17:29] Deal. [17:29] OK, I have no further new items, the floor is open as we have some time left... [17:30] [topic] open floor [17:30] New Topic: open floor [17:30] Anything from anyone? [17:30] Going once.......................................... [17:30] the usb client use cases provided a lot of info [17:31] that Don J sent to list: just mentioning that [17:31] It does, and with ARMS access we now have the client side code too. [17:32] Going twice..... [17:32] It's a bit confusing but we are delving into it to see what it does. [17:32] right [17:32] Indeed [17:32] I'm worried that it ends in MIC [17:32] lool: MIC? [17:32] anyone else think that a squashfs partition + ext3 partition + big vfat parition is going to be a bit limiting? [17:32] MIC simply doesn't sound like a very maintainable place to live [17:32] upgrades will be painful... [17:32] agoliveira: moblin-image-creator [17:32] smagoun: I think that will be a mess... [17:32] That could be an issue. [17:32] lool: Oops :) [17:33] smagoun: I don't understand why they picked a real partition for vfat instead of a loopback mounted one [17:33] lool: I don't understand *any* of the decisions they made :) [17:33] smagoun: squashfs should go away [17:33] smagoun, I hope it's not a "big" vfat partition, that could really eat space. [17:33] smagoun: It's supposed to be possible to have only a real ext3 [17:33] Dunno how far this support is at the moment though [17:34] davidm: My understanding from the thing Don posted was that data was expected to be on the vfat partition? Or did I read it too quickly? [17:34] we really need to have Rusty in this discussion for USBC and VFAT [17:34] robr: +1 [17:34] robr, that is true, otherwise we are spinning wheels [17:34] yes, the data to share must be on vfat, which eems non great for usability [17:34] seems [17:34] It sounds like userspace is not architectured for maintenance or upgrades, just one shot "we can do it" :-/ [17:35] Shall we take this to the list and bring it back here if necessary? [17:35] The vfat was only put in a few days ago, by alek. I'm sure it will be easy to make it a file on the system. [17:35] Also I thought squashfs was optional. [17:36] we seem to keep putting this discussion off from week to week, why don't we schedule a meeting when Rusty is back just for the USBC discussion so we can hammer it out once and for all [17:36] HappyCamp_laptop: Did you have a change to discuss doing this in a separate codebase? [17:36] lool: nope [17:36] from a user's point of view, I'd want the photos/videos/music folders to be automatically sharable, but they are not in vfat [17:37] HappyCamp_laptop: I think you should consider what happens if we need to fix a device; say, how do we provide an upgrade to the USB Client files which are in the vfat [17:37] HappyCamp_laptop: I'm sure that if you discuss with Alek, you will want to split it out [17:37] robr: +1 [17:37] I'm confused, wouldn't you just copy the new files there? [17:37] robr, that makes sense to me. Can you take the lead on pulling the meeting together? [17:37] HappyCamp_laptop: Who would? [17:38] if you don't put them on a VFAT partition your other choice is to share them over RNDIS/Samba which a whole bunch of other issues [17:38] Whatever update program we come up with. [17:38] davidm: i can do that [17:38] HappyCamp_laptop: We already have apt and dpkg; why would we want another program? [17:38] robr: right, so the usablity is questionable? [17:38] [action] robr to arrange a meeting around USB and VFAT issues. [17:38] ACTION received: robr to arrange a meeting around USB and VFAT issues. [17:38] Still confused, why wouldn't the usb client files be part of a package? [17:39] I had this crazy idea about creating a client application a la Apple :) [17:39] HappyCamp_laptop: So you need some infrastructure to update the contents of the vfat [17:39] HappyCamp_laptop: Which makes me wonder why we should do it in MIC in the first place [17:40] (Since obviously MIC wont be installed on the final devices) [17:40] lool: why? vfat is mounted, and then you have package which installs content into wherever we decide to have vfat mounted. [17:40] That would be how I would think it should be done. [17:40] HappyCamp_laptop: Hmm I wouldn't want a .deb installing data directly in a mounted vfat [17:40] why not? [17:40] Is that a problem? [17:41] I am not sure dpkg is ready to cope with installing packages over vfat [17:41] Because if not, things will be more difficult :( [17:41] vfat makes things more difficult :( [17:41] I think before we go to far with this conversation we need to have the right people in the meeting. [17:41] okay [17:41] davidm: good point [17:42] OK so it's tabled until robr gets the right people together then. [17:42] HappyCamp_laptop: So I would personally thing it would be simpler to have a package take a directory and generate a vfat out of it; this generation could happen each time we drop something in that dir [17:42] HappyCamp_laptop: I didn't see any drawback to this, and it keeps the problem simple [17:42] HappyCamp_laptop: I'm happy to setup a meeting with you and Alek to discuss this [17:42] lool: okay, I don't understand but I'm sure you can explain it :) [17:43] OK, anything else new? I don't see anything new on the meeting wiki [17:43] lool: you will need to meet with us individually, and probably alek first. alek_desktop is in PRC and I am in Oregon. Will be tough for you to meet with us at the same time. [17:43] HappyCamp_laptop: Ok; will meet with him then; is he aware of the public meeting? [17:43] HappyCamp_laptop: Maybe bring him there for the sprint? [17:44] actually i think lool needs to meet with alek rusty happycamp and me [17:44] robr please make sure I'm on that list too. Thanks [17:44] robr, lool is in Europe and sound asleep when we normally meet with PRC. [17:45] agoliveira: that's a good suggestion [17:45] HappyCamp_laptop: I probably am, it feels like you wake up when I go to bed and vice-versa; it's very bad for day to day questions / work [17:45] HappyCamp_laptop: understood, but if we're going to solve this someone is going to lose some sleep [17:45] (Nobody to blame here, it's just a fact) [17:45] lool: When in need, blame the new guy... [17:45] Hmm... that means you :) [17:46] robr: If it's one shot, I guess I can be the one; but I'll need to plan with a lot of advance time then [17:46] lool: sorry about that. I usually start work late so that it is easier to work with PRC, since I have to work late. [17:46] or you just blame HappyCamp [17:46] * agoliveira can't say that. He's the boss :) [17:46] As my computer is basically in the room where my wife sleeps (and me too naturally) [17:47] i might be able to convince Alek to stay up a little late, 9am PST is only 12 midnight in PRC [17:48] OK, so we have a short range plan, robr is going to find a suitable time for everyone to meet, recognizing that someone is going to be a bit inconvenienced. [17:48] "only" ;) [17:48] correction, that's 1am [17:48] robr: I'm in UTC + 1 ATM, can you send some meeting proposals via email to all of us? [17:49] lool: sure [17:49] Thanks [17:49] Ok we already have an action item for that so we are good. [17:49] We need to exchange more with Intel; I feel we go through huge pains because we don't exchange enough in advance :) [17:50] OK, there is no new additions to the wiki page for the meeting. Are we done then? [17:51] Just a quick note: is Intel aware about our company-wide hollidays? If not, maybe they should. [17:53] Good point, we are off from Dec 24th - Jan 1 back on Jan 2 [17:53] I'll make sure Don Johnson has this info, I think he does already. [17:54] #endmeeting [17:54] Meeting finished at 17:54. [17:54] I'm starting a week earlier so my last week working this year is the next. [17:57] lool: if you haven't already done so you might want to contact pvanhoof 'at' gnome.org directly rather than the nokia maintainer of modest [17:58] ian_brasil: The Nokia maintainer seemed to be doing all the commits [17:58] Another Nokia guy who's hard to reach is the wpeditor maintainer [17:58] Didn't respond to me yet [17:59] Anyone around? [18:00] HappyCamp: So, do you want me to clarify the idea for vfat maintenance? [18:00] InSearchOf: Lot's of people around :) Say hi to Sasha :) [18:01] lool: sure [18:01] lool: ok, most of the underlying modest stuff is tiny so i think he is upstream of upstream [18:01] ian_brasil: Okay; thanks for the tip [18:02] lool, can you write it up as an email? Alek is the one doing the implementation. [18:02] sodarock_home: sodarock_home HappyCamp HappyCamp_ubuntu HappyCamp_laptop how many do you get here? :) [18:02]