Mar 13 12:00:19 <lool> #startmeeting Mar 13 12:00:20 <MootBot> Meeting started at 17:00. The chair is lool. Mar 13 12:00:20 <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE] Mar 13 12:00:24 * sodarock_laptop2 is now known as sodarock_aka_hap Mar 13 12:00:26 <praj-laptop> sodarock_laptop2: the meeting got pushed to 10. it should start now Mar 13 12:00:27 <lool> sodarock_laptop2: There is now :) Mar 13 12:00:43 * sodarock_aka_hap is now known as sodarock_happyca Mar 13 12:00:58 <rustyl_> morning all Mar 13 12:00:58 <lool> Hi everybody, hope everybody is doing fine Mar 13 12:01:08 <tonyespy> KenKC: like this Mar 13 12:01:20 <lool> NB: amitk will be 5 minutes late Mar 13 12:01:30 * mawhalen (n=chatzill@nat/intel/x-d37c35735a30bd53) has joined #ubuntu-mobile Mar 13 12:01:36 <agoliveira> Hi all Mar 13 12:01:40 * sodarock_happyca is now known as sodarock_laptop2 Mar 13 12:01:46 <lool> I'll chair the meeting this week as David is in another one Mar 13 12:01:46 <rustyl_> what was the URL for the wiki with the agenda? Mar 13 12:01:50 <tremolux> 'lo Mar 13 12:01:50 <lool> https://wiki.ubuntu.com/MobileAndEmbedded/Meeting/20080313 Mar 13 12:02:01 * agoliveira proposes that every action today should be given to amitk :) Mar 13 12:02:09 <lool> We'll start by reviewing last weeks action items Mar 13 12:02:21 <lool> [topic] patm to to produce boot charts for squashfs vs ext3 for hardy CB by 13 March. [cted] Mar 13 12:02:22 <MootBot> New Topic: patm to to produce boot charts for squashfs vs ext3 for hardy CB by 13 March. [cted] Mar 13 12:02:22 <amitk> agoliveira: I'm back to thwart your sinister plans Mar 13 12:02:32 <lool> I fear patm is going to be in the same call as DannyZ Mar 13 12:02:35 <lool> err davidm Mar 13 12:02:37 <lool> sorry DannyZ Mar 13 12:02:40 <agoliveira> Damn... Mar 13 12:02:41 <lool> patm: Are you around? Mar 13 12:02:46 <patm> I am Mar 13 12:02:49 <lool> Oh cool Mar 13 12:02:51 <patm> but with no boot chart Mar 13 12:02:55 <lool> Hmm Mar 13 12:02:58 * dop3 has quit (Read error: 104 (Connection reset by peer)) Mar 13 12:03:14 * KenKC_ (n=KenKC@58.34.234.87) has joined #ubuntu-mobile Mar 13 12:03:15 * dop3 (n=dop3@201.37.89.212) has joined #ubuntu-mobile Mar 13 12:03:17 <patm> Please carry forward, sorry Mar 13 12:03:18 <lool> patm: Should put this on someone else's shoulders? Mar 13 12:03:41 <patm> lool, no I will keep it, but we moved a deliverable to this week, so needs to be later Mar 13 12:03:50 <lool> [action] patm to to produce boot charts for squashfs vs ext3 for hardy CB by 13 March. [cted] [cted] Mar 13 12:03:50 <MootBot> ACTION received: patm to to produce boot charts for squashfs vs ext3 for hardy CB by 13 March. [cted] [cted] Mar 13 12:03:56 <lool> [topic] davidm & agoliveira to look at what asac provides and get script written by 13 March that does conversion of .po files to xpi structures. [cted] Mar 13 12:03:57 <MootBot> New Topic: davidm & agoliveira to look at what asac provides and get script written by 13 March that does conversion of .po files to xpi structures. [cted] Mar 13 12:04:06 * tonyespy has quit () Mar 13 12:04:11 <lool> davidm didn't manage to work on this last week; he said he would look over the WE Mar 13 12:04:22 <lool> agoliveira: I'll let you report directly: Mar 13 12:04:51 <agoliveira> Same here. Took more time than expected for Asac provide us with the examples we required and I had a very short week last week. Mar 13 12:05:10 <agoliveira> So, please, push it forward. Mar 13 12:05:20 <lool> I'm carrying on the action; it should be escalated if no progress is made next week as we're nearing the release of hardy and asac needs these Mar 13 12:05:29 <lool> [action] davidm & agoliveira to look at what asac provides and get script written by 13 March that does conversion of .po files to xpi structures. [cted] [cted] Mar 13 12:05:30 <MootBot> ACTION received: davidm & agoliveira to look at what asac provides and get script written by 13 March that does conversion of .po files to xpi structures. [cted] [cted] Mar 13 12:05:34 <lool> [topic] kyleN to prepare a mapping of hildon source packages to gettext domains, and list where the gettext domains are in maemo. [cted] Mar 13 12:05:35 <MootBot> New Topic: kyleN to prepare a mapping of hildon source packages to gettext domains, and list where the gettext domains are in maemo. [cted] Mar 13 12:05:44 <kyleN> since gettext domains can be set programmatically, there's no absolute way to derive all for a package programmatically. However, I wrote a python tool that gets 90% of the way for an arbitrary/editable set of packages Mar 13 12:06:08 <kyleN> I have a list of the gettext domains for hildon pkgs Mar 13 12:06:10 * mawhalen has quit (Client Quit) Mar 13 12:06:13 <lool> Cool; is it published somewhere? Did you manage to output a mini-map? Mar 13 12:06:40 <kyleN> I have not had a chance to create a deb for it. this is a very busy week for us here... Mar 13 12:06:55 <lool> kyleN: "I have a list of the gettext domains for hildon pkgs" => which one? the one telling which gettext domains they use or the one they provide? Mar 13 12:06:55 <kyleN> lool, i can email it to you if you are interested Mar 13 12:07:03 <lool> kyleN: Doesn't need to be packaged IMO Mar 13 12:07:17 <lool> kyleN: I think you should publish it on the wiki as an attachment to langpack research page Mar 13 12:07:20 <kyleN> the onees they use Mar 13 12:07:30 <lool> Where we identified this as a prereq Mar 13 12:07:34 <kyleN> I have not yet done the second half: mapping to upstream Mar 13 12:07:43 <lool> Ok; shall I carry on with this part only? Mar 13 12:07:49 <kyleN> yes Mar 13 12:08:10 * AtomicPunk is now known as ToddBrandtClone Mar 13 12:08:17 <lool> [action] kyleN to attach his python script to list gettext domains in use in hildon modules on the langpack research page Mar 13 12:08:17 <MootBot> ACTION received: kyleN to attach his python script to list gettext domains in use in hildon modules on the langpack research page Mar 13 12:08:33 <kyleN> python script plus glade file Mar 13 12:08:42 <kyleN> and helper files Mar 13 12:08:54 <lool> [action] kyleN to enhance his python script looking into hildon modules to build a map of where the gettext templates are stored Mar 13 12:08:54 <MootBot> ACTION received: kyleN to enhance his python script looking into hildon modules to build a map of where the gettext templates are stored Mar 13 12:09:06 <lool> [topic] kyleN to look into hildon-help; what's is useful for and whether we should package it for UME Mar 13 12:09:07 <MootBot> New Topic: kyleN to look into hildon-help; what's is useful for and whether we should package it for UME Mar 13 12:09:09 * bspencer (n=chatzill@nat/intel/x-662268d684ff7442) has joined #ubuntu-mobile Mar 13 12:09:14 <lool> kyleN: Tell us all about it! Mar 13 12:09:21 <kyleN> sorr - haven't had a chance to hit this one yet... Mar 13 12:09:29 <kyleN> please carry over Mar 13 12:09:32 <lool> Okay Mar 13 12:09:53 <lool> [action] kyleN to look into hildon-help; what's is useful for and whether we should package it for UME [cted] Mar 13 12:09:53 <MootBot> ACTION received: kyleN to look into hildon-help; what's is useful for and whether we should package it for UME [cted] Mar 13 12:10:00 <lool> [topic] lool review progress on Hildon 2.0 updates next week Mar 13 12:10:02 <MootBot> New Topic: lool review progress on Hildon 2.0 updates next week Mar 13 12:10:19 <lool> So, I'm supposed to be an example here, and *cough*, I only have hildon-control-panel ready but not even pushed to our bzr repo Mar 13 12:10:34 <lool> I finished pulling the update this afternoon and will push it after the meeting Mar 13 12:10:37 <bfiller> lool: no progress on my end, too busy with customer release, hopefully I'll have some time next week Mar 13 12:10:58 <lool> agoliveira missed the action item which was assigned to him when he was away (during last meeting) Mar 13 12:11:09 <lool> smagoun: did you manage? Mar 13 12:11:09 <smagoun> lool: no progress on my end, too busy with customer release, hopefully I'll have some time next week Mar 13 12:11:17 <lool> bspencer: Did Horace manage to do one or two? Mar 13 12:11:26 <lool> smagoun: You copy-pasted that! Mar 13 12:11:30 <lool> :) Mar 13 12:11:35 <smagoun> lool: yes. We have the same boss. Mar 13 12:11:47 <lool> mjg59: I think you did at least hildon-theme-layout-4 in bzr Mar 13 12:12:02 <lool> Which is the only one you had to do! 100%! Mar 13 12:12:05 <bspencer> lool: I just got in and saw his email. I haven't tried it out yet. But he said he had done something Mar 13 12:12:26 <bspencer> lool: oh, sorry. I am talking about something else. Mar 13 12:12:37 <bspencer> lool: I don't know of his status for porting Hildon 2.0 I'll check Mar 13 12:12:45 <lool> bspencer: Please check with him Mar 13 12:12:53 <lool> It looks like everybody was too busy to do all of it Mar 13 12:13:10 <lool> I personally took some notes of the steps I followed and will add them to the wiki page Mar 13 12:13:13 <lool> [link] https://wiki.ubuntu.com/MobileAndEmbedded/Hildon2%2e0 Mar 13 12:13:13 <MootBot> LINK received: https://wiki.ubuntu.com/MobileAndEmbedded/Hildon2%2e0 Mar 13 12:13:27 <lool> I guess we'll have to carry over Mar 13 12:13:37 <lool> [action] lool review progress on Hildon 2.0 updates next week [cted] Mar 13 12:13:37 <MootBot> ACTION received: lool review progress on Hildon 2.0 updates next week [cted] Mar 13 12:13:46 <lool> [topic] sabotage to provide drafts of themes tools guide and implementation options as links on the mailing-list Mar 13 12:13:47 <MootBot> New Topic: sabotage to provide drafts of themes tools guide and implementation options as links on the mailing-list Mar 13 12:14:19 <lool> Hmm where's sabotage and where's mawhalen? Mar 13 12:14:33 <lool> Anyone from Intel can comment on this or grab the relevant people? Mar 13 12:14:43 <bspencer> I'll get sabotage... I don't know about mawhalen. Let's postpone this agenda item for 20mins Mar 13 12:14:47 <lool> Yes Mar 13 12:14:54 <lool> bspencer: Thanks Mar 13 12:15:03 <lool> [topic] ToddBrandt to turn on moblin-settings-daemon's watching of the gtk theme gconf keys Mar 13 12:15:04 <MootBot> New Topic: ToddBrandt to turn on moblin-settings-daemon's watching of the gtk theme gconf keys Mar 13 12:15:20 <lool> ToddBrandt: Did you have a change to work on enabling it? Mar 13 12:15:27 <lool> or ToddBrandtClone perhaps? Mar 13 12:15:47 <ToddBrandtClone> oh, oy, actually I haven't done that yet Mar 13 12:15:54 <lool> Hmm ok Mar 13 12:15:58 <ToddBrandtClone> I'll do that today, sorry Mar 13 12:15:58 <lool> Bad you Mar 13 12:16:05 <ToddBrandtClone> yea, I know, the bugs took priority Mar 13 12:16:08 <lool> Carrying to check about it next week Mar 13 12:16:08 <kyleN> please note that we are very intested in this as it appears necessary to get gtk theme switching working Mar 13 12:16:12 <lool> ToddBrandtClone: ack Mar 13 12:16:21 <lool> [action] ToddBrandt to turn on moblin-settings-daemon's watching of the gtk theme gconf keys [cted] Mar 13 12:16:22 <MootBot> ACTION received: ToddBrandt to turn on moblin-settings-daemon's watching of the gtk theme gconf keys [cted] Mar 13 12:16:27 <lool> [topic] rustyl (+ lool if necessary) document release process for Moblin modules Mar 13 12:16:27 <MootBot> New Topic: rustyl (+ lool if necessary) document release process for Moblin modules Mar 13 12:16:30 * ToddBrandtClone hangs head in shame Mar 13 12:16:34 <lool> So AFAIK, this happened Mar 13 12:16:38 <lool> congrats to rustyl_ Mar 13 12:16:51 <lool> He managed to do tarball releases of almost all moblin projects I think Mar 13 12:16:56 <lool> rustyl_: kudos to you! Mar 13 12:17:05 <rustyl_> k Mar 13 12:17:29 <lool> rustyl_: I personally had in mind that there would be some kind of process document on moblin.org for module maintainers, but perhaps you have an internal one, to release subsequent tarballs? Mar 13 12:17:30 * tonyespy (n=tonyespy@bismuth.canonical.com) has joined #ubuntu-mobile Mar 13 12:17:51 <rustyl_> we are working on a presentation Mar 13 12:17:58 <bfiller> lool: are there plans to incorporate CDBS into debian/rules so we can make patches? Mar 13 12:17:59 * KenKC has quit (Read error: 110 (Connection timed out)) Mar 13 12:18:03 <rustyl_> it just isn't ready yet Mar 13 12:18:21 <lool> bfiller: Yes; I think we'll discuss this in "(lool) Rebasing on the Moblin released tarballs" Mar 13 12:18:31 <lool> bfiller: Just after that Mar 13 12:18:33 <bfiller> lool: thanks Mar 13 12:19:05 <lool> rustyl_: Ok; well thanks for the efforts; I'm around to help you succeed in defining/documenting the process Mar 13 12:19:22 <lool> rustyl_: I'd also like to talk to moving to these new tarballs now, but I made this a separate topic Mar 13 12:19:43 <rustyl_> yea, this needs some discussion Mar 13 12:19:48 <lool> Moving on to current items for today's meeting Mar 13 12:19:58 <lool> Hmm I'll flip two because one is easier Mar 13 12:20:05 <lool> [topic] (lool) Launchpad bugs, ubuntu-mobile subscription, and ume tag Mar 13 12:20:06 <MootBot> New Topic: (lool) Launchpad bugs, ubuntu-mobile subscription, and ume tag Mar 13 12:20:07 * YoungGuo has quit (Read error: 104 (Connection reset by peer)) Mar 13 12:20:25 <lool> EVERYBODY (that's you) please add the ume tag to LP bugs which concern UME Mar 13 12:20:31 <lool> And subscribe the ubuntu-mobile LP team to them Mar 13 12:20:51 <rustyl_> lool, is there a way to apply a tag to a collection of bugs? Mar 13 12:20:54 <lool> This is to help everybody keep track of important bugs we have to follow for UME and derived projects Mar 13 12:21:02 <lool> rustyl_: Excellent question, I think not Mar 13 12:21:03 <rustyl_> or do you have to go through each and every bug Mar 13 12:21:07 <rustyl_> darn Mar 13 12:21:14 <lool> rustyl_: This would seem to suck Mar 13 12:21:24 <lool> rustyl_: You might be able to set it via email though Mar 13 12:21:57 * rustyl_ looks to see if his moblin-media bugs are tagged already Mar 13 12:22:01 * sabotage (n=sabotage@c-24-22-27-185.hsd1.or.comcast.net) has joined #ubuntu-mobile Mar 13 12:22:08 <lool> rustyl_: We have some hacked up python bindings to deal with bug reports though Mar 13 12:22:20 <lool> rustyl_: Perhaps you can use these to do as you desire? Mar 13 12:22:46 <lool> rustyl_: "python-launchpad-bugs" Mar 13 12:22:51 * sabotage hears his name being taken in vain Mar 13 12:22:55 <rustyl_> i'll read about it Mar 13 12:22:59 <lool> rustyl_: But please file a feature request if you can't find the tagging feature you're looking for Mar 13 12:23:08 <rustyl_> ok Mar 13 12:23:12 <lool> rustyl_: You'd have to file it against "malone", that's the launchpad bug tracker Mar 13 12:23:33 <lool> sabotage: Thanks for coming; I'll reopen your topic now then Mar 13 12:23:48 <lool> So please everybody tag and subscribe! Mar 13 12:23:57 <lool> And file bugs, don't discuss issues via email or IRC :) Mar 13 12:24:04 <lool> [topic] sabotage to provide drafts of themes tools guide and implementation options as links on the mailing-list Mar 13 12:24:04 <MootBot> New Topic: sabotage to provide drafts of themes tools guide and implementation options as links on the mailing-list Mar 13 12:24:27 <lool> sabotage: Tears flows on my face: no themes tools guide this week? Mar 13 12:24:39 <bspencer> s/don't discuss issues via email or IRC/don't discuss issues JUST via email or IRC Mar 13 12:24:45 <lool> bspencer: Right Mar 13 12:24:52 <lool> Mention the bug in your email :) Mar 13 12:24:55 <sabotage> ok, so I dropped the ball this week, but I've identified the wiki that I will be publishing it in Mar 13 12:25:19 <lool> sabotage: Do you need any help to publish the guide? Mar 13 12:25:30 <sabotage> can you make days longer? Mar 13 12:25:31 <lool> And your thoughts on implementation options? Mar 13 12:25:50 <lool> sabotage: I can keep you up longer before you're allowed to sleep :) Mar 13 12:26:01 <sabotage> honestly, I've been completely swamped with another project, so I just need to kick it out for visibility Mar 13 12:26:18 * sabotage was up till 1:30am last night as it is Mar 13 12:26:22 <lool> sabotage: Please try to push this out this week -- even a draft Mar 13 12:26:34 <sabotage> yep, ball is already rolling Mar 13 12:26:37 <lool> Cool Mar 13 12:26:45 <lool> [action] sabotage to provide drafts of themes tools guide and implementation options as links on the mailing-list [cted] Mar 13 12:26:46 <MootBot> ACTION received: sabotage to provide drafts of themes tools guide and implementation options as links on the mailing-list [cted] Mar 13 12:26:59 <sabotage> is HappyCamp on? Mar 13 12:27:02 <lool> Resuming on next item to discuss Mar 13 12:27:07 * tonyespy has quit () Mar 13 12:27:10 <lool> [topic] (lool) Rebasing on the Moblin released tarballs Mar 13 12:27:11 <MootBot> New Topic: (lool) Rebasing on the Moblin released tarballs Mar 13 12:27:12 <bspencer> sodarock Mar 13 12:27:21 <sabotage> HappyCamp, HappyCamp_ubuntu need you to read my email and set me up Mar 13 12:27:23 <lool> So, we have these cool Moblin tarballs Mar 13 12:27:29 <sabotage> this will get the theme guide moving Mar 13 12:27:45 <lool> We should move to using them Mar 13 12:28:19 <lool> rustyl_: I'm not sure I made this clear enough, but one thing which we want to keep is Intel publishing its releases all the way down to the ppa Mar 13 12:28:42 <rustyl_> lool, i understand Mar 13 12:28:42 <lool> But the transition frmo the current mode to the mode where we use tarballs needs a little extra efforts Mar 13 12:28:54 <bspencer> rustyl_: lool: how does that work again, with ubuntu adding patches on their own? Mar 13 12:28:54 <lool> It's similar in spirit to the Hildon 2.0 modules transition Mar 13 12:28:57 <rustyl_> and there is confusion on our end Mar 13 12:29:08 * bspencer confesses a bit of confusion :) Mar 13 12:29:35 <lool> bspencer: The idea is that we put patches in debian/patches; when a new upstream release comes out and you push it to the ppa, you drop the debian/patches which have been merged upstream and port the other ones Mar 13 12:29:55 <lool> rustyl_: Where is the confusion? Mar 13 12:29:57 <bspencer> lool: ok. I understand. I missed that patches change Mar 13 12:30:45 <lool> This will make the Ubuntu/ppa specific changes into separate patches, and easy to rebase on the next release Mar 13 12:31:13 <rustyl_> lool, If you gave everyone a written test that made them explain exactly what commands/steps you need to do go from "i have a new tarball release" to "i am now calling dput to push to the ppa", i'm afraid most intel people would fail the test Mar 13 12:31:23 <ToddBrandtClone> Do each of the project owners need to upload their source to the hardy ppa for each release still or has this been streamlined Mar 13 12:31:33 <lool> rustyl_: Ok, the cool thing is that it's going to be very easy Mar 13 12:31:39 * ToddBrandtClone Todd trumps bspencer's confusion Mar 13 12:31:43 <lool> Once we get it done *once* Mar 13 12:31:50 <lool> Subsequent updates are going to be easy Mar 13 12:31:55 <GrueMaster> i fail. Mar 13 12:32:09 <lool> ToddBrandtClone: We would like project owners to please continue doing so Mar 13 12:32:31 <ToddBrandtClone> lool: ok, our source repo layout has changed so I guess I have some more questions for rusty Mar 13 12:32:58 <lool> It's so damn easy that it's basically: dget -x the current ppa source, uupdate with the new tarball, update the packaging and patches, upload Mar 13 12:32:58 <rustyl_> ToddBrandt, the packaging for hardy is not in the source repository Mar 13 12:32:58 <ToddBrandtClone> rusty_: do we have a HARDY branch now in addition to GASTON? Mar 13 12:33:21 <rustyl_> ToddBrandt, that hardy branch is now defunct Mar 13 12:33:32 <ToddBrandtClone> rustyl_: yea but we still haev to use the debian tools to create the source package, which require the debian dir, which is no longer in master Mar 13 12:33:50 <lool> ToddBrandtClone: Exactly, that dir you retrieve from the ppa each time you plan an upload Mar 13 12:33:58 <lool> ToddBrandtClone: It might have been updated by other folks, for example me Mar 13 12:33:59 <ToddBrandtClone> ahhh Mar 13 12:34:09 <ToddBrandtClone> the missing piece, I'm learning, gotcha Mar 13 12:34:12 <rustyl_> yeap, that's the idea Mar 13 12:34:25 <lool> If you prefer, instead of "uupdate" you simply "copy over the debian/"; it should end up being the same Mar 13 12:34:33 <ToddBrandtClone> k, thx Mar 13 12:34:44 <lool> This is the *target* process Mar 13 12:34:56 <lool> Before this, we need to add support for debian/patches/ in each package Mar 13 12:35:09 <lool> mjg59 did it in hildon-theme-layout-4 Mar 13 12:35:17 <ToddBrandtClone> ok, so until then we create the hardy packages like before Mar 13 12:35:23 <lool> * Add simple-patchsys from CDBS Mar 13 12:35:23 <lool> * Build-depend on CDBS Mar 13 12:35:34 <lool> That's his changelog entry Mar 13 12:35:35 <lool> What we did in debian/rules: Mar 13 12:35:38 <lool> - he added: Mar 13 12:35:38 <lool> include /usr/share/cdbs/1/rules/simple-patchsys.mk Mar 13 12:35:39 <rustyl_> we several things on moblin that need to do a new release, so we have some projects to try to run through the new process Mar 13 12:35:59 <lool> - he changed the dependencies of the targets to apply/unapply the patches: Mar 13 12:36:02 <lool> build: apply-patches build-stamp Mar 13 12:36:19 <lool> This means applying the patches is a prereq for the build Mar 13 12:36:22 * tonyespy (n=tonyespy@bismuth.canonical.com) has joined #ubuntu-mobile Mar 13 12:36:47 <lool> You might have to rename clean: to clean:: as simple-patchsys.mk defines it as well Mar 13 12:36:53 <lool> This is all it takes to add debian/patches support Mar 13 12:36:55 * agoliveira is happy that the word "quilt" didn't make into this conversation so far :) Mar 13 12:37:34 <lool> The other thing to do is to compare the Ubuntu ppa tree to the moblin release it claims to base on to see which changes were done since this moblin release Mar 13 12:37:41 <bfiller> lool: do moblin folks take the patches in debian/patches and incorporate them into the source and remove the patches? Mar 13 12:37:44 <lool> These changes should be converted to debian/patches/*.patch files Mar 13 12:38:01 <lool> bfiller: The person authoring the patch should take care to send it to moblin folks Mar 13 12:38:16 <rustyl_> bfiller, i think incorporating existing packages before making a release is a good goal Mar 13 12:38:23 <lool> Moblin folks are naturally welcome to look from time to time if there would be interesting patches which failed the upstreaming process Mar 13 12:38:53 <lool> Does anybody has any question on how it will work and what remains to be done? Mar 13 12:39:17 <rustyl_> it makes a nice way to send a patch.... send an email to the maintainer with moblin devel list cc'ed, and at the same time upload the patch to the ppa Mar 13 12:39:38 <bfiller> lool: so if I had a patch, I would put the patch in debian/patches, upload to the ppa and also send the patch to moblin? Mar 13 12:39:42 <lool> Perhaps we should file a bug instead of mailing the maintainer? Mar 13 12:39:56 <lool> rustyl_: Would that work for you? Mar 13 12:39:59 <ToddBrandtClone> I vote for mailing the maintainer, that info would be very useful Mar 13 12:40:04 <lool> bfiller: Perhaps opening a bug is more logical than using email Mar 13 12:40:13 <lool> ToddBrandtClone: Doesn't the maintainer get an email for new bugs? Mar 13 12:40:14 <rustyl_> yes, filling a bug is good Mar 13 12:40:27 <rustyl_> the maintainer will get the mail via launchpad Mar 13 12:40:29 <davidm> Can do both but filing a bug is important, and has been requested by Don Johnson. Mar 13 12:40:42 <ToddBrandtClone> ok Mar 13 12:40:44 <davidm> Need tracking Mar 13 12:40:53 <rustyl_> but we need to cc the devel list for potential discussion on the patch Mar 13 12:41:22 <lool> rustyl_: I think that's a logical escalation when a bug fix isn't consensual indeed Mar 13 12:41:33 <lool> (or any change, not necessarily a bug fix) Mar 13 12:42:26 * andrunko (n=andrunko@200.184.118.132) has joined #ubuntu-mobile Mar 13 12:42:31 <lool> Should I document what we just discussed on a wiki page? (how tarball releases work down to the ppa and how patches are added+sent back)? Mar 13 12:42:46 <davidm> lool, yes please Mar 13 12:42:51 <ToddBrandtClone> yes Mar 13 12:42:54 <rustyl_> yes Mar 13 12:42:57 <cwong1> +1 Mar 13 12:43:10 <lool> [action] lool to document tarball release + ppa upload process and patch addition + submission process Mar 13 12:43:11 <MootBot> ACTION received: lool to document tarball release + ppa upload process and patch addition + submission process Mar 13 12:43:15 <davidm> Just out of the other meeting, sorry I'm late. Mar 13 12:43:29 <lool> Ok; last thing to discuss on the topic is who is going to do the work to conver the ppa packages to the layout Mar 13 12:43:45 <lool> This requires adding support for debian/patches and extracting the current ppa-only changes as patch files Mar 13 12:43:58 <lool> I propose we split that like the Hildon 2.0 modules Mar 13 12:44:08 <lool> Does that work for everybody? Mar 13 12:44:20 <lool> rustyl_: Would you be willing to participate? Mar 13 12:44:37 <lool> Who from Intel would be willing to take a share? Mar 13 12:44:54 <lool> Everybody I guess! :) Mar 13 12:45:15 <rustyl_> lool, if somebody does the first package, then I would be happy to do (or delegate) several of the other packages Mar 13 12:45:16 <bspencer> mawhalen -- since she's not here. Mar 13 12:45:27 <rustyl_> i just need the first package to cookbook from Mar 13 12:45:27 <lool> rustyl_: deal Mar 13 12:45:56 <rustyl_> and by several, i mean i can find people to do all the rest of the moblin projects Mar 13 12:46:04 <lool> rustyl_: I'll mail you with the steps I follow for a sample package, you will split the work amongst Intel people for some modules you'll list me and the others we shall do? Mar 13 12:46:12 <lool> rustyl_: Cool Mar 13 12:46:57 <lool> [action] lool to send rustyl_ steps to update ppa packages for the new tarball based release process Mar 13 12:46:58 <MootBot> ACTION received: lool to send rustyl_ steps to update ppa packages for the new tarball based release process Mar 13 12:47:15 <lool> [action] rustyl_ to assign ppa packages updates for the new tarball based release process Mar 13 12:47:16 <MootBot> ACTION received: rustyl_ to assign ppa packages updates for the new tarball based release process Mar 13 12:47:33 <lool> Does anybody have any question on this? Mar 13 12:47:38 <rustyl_> yea Mar 13 12:47:50 <rustyl_> what 'project' to i write launchpad bugs against? Mar 13 12:47:56 <rustyl_> 'launchpad' doesn't work Mar 13 12:48:09 <lool> rustyl_: To report the malone bug? Mar 13 12:48:39 <rustyl_> to report the 'i want to assign a tag to a couple hundred bugs at once' feature request Mar 13 12:48:40 <lool> rustyl_: https://bugs.launchpad.net/bugs/+filebug select "Project" type "malone" and search Mar 13 12:48:54 <lool> s/search/choose Mar 13 12:49:02 <rustyl_> what is malone? Mar 13 12:49:21 <lool> As I was saying earlier, it's the Launchpad bug tracking subproject Mar 13 12:49:35 <rustyl_> got it Mar 13 12:49:53 <lool> rustyl_: https://launchpad.net/projects/?text=launchpad Mar 13 12:50:01 <lool> rustyl_: You'll see "Launchpad Bugs" Mar 13 12:50:06 * tonyespy has quit () Mar 13 12:50:08 <rustyl_> https://bugs.launchpad.net/malone/+bug/201874 Mar 13 12:50:09 <lool> It's technical/unix name is "malone" Mar 13 12:50:09 <ubotu> Launchpad bug 201874 in malone "Need ability to apply tag to a collection of bugs" [Undecided,New] Mar 13 12:50:15 <lool> rustyl_: Tada Mar 13 12:50:25 <bfiller> slightly obscure, I'd say :) Mar 13 12:50:33 <bfiller> malone, that is Mar 13 12:50:43 <rustyl_> it keeps thing mysterious Mar 13 12:51:03 <bfiller> good way to keep people from filing bugs :) Mar 13 12:51:05 <GrueMaster> Nah, it's perfectly intuitive. Mar 13 12:51:14 <lool> Let's end the meeting in a mysterious way then! Mar 13 12:51:19 <agoliveira> rustyl_: Santa Rosa? Diamondville? McAslin? Mar 13 12:51:21 <agoliveira> :) Mar 13 12:51:35 <lool> [endmeeting] malone! soyuz! Mar 13 12:51:40 <lool> #endmeeting