Ubuntu Wiki

   1 Mar 13 12:00:19 <lool>	#startmeeting
   2 Mar 13 12:00:20 <MootBot>	Meeting started at 17:00. The chair is lool.
   3 Mar 13 12:00:20 <MootBot>	Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
   4 Mar 13 12:00:24 *	sodarock_laptop2 is now known as sodarock_aka_hap
   5 Mar 13 12:00:26 <praj-laptop>	sodarock_laptop2: the meeting got pushed to 10. it should start now
   6 Mar 13 12:00:27 <lool>	sodarock_laptop2: There is now :)
   7 Mar 13 12:00:43 *	sodarock_aka_hap is now known as sodarock_happyca
   8 Mar 13 12:00:58 <rustyl_>	morning all
   9 Mar 13 12:00:58 <lool>	Hi everybody, hope everybody is doing fine
  10 Mar 13 12:01:08 <tonyespy>	KenKC: like this
  11 Mar 13 12:01:20 <lool>	NB: amitk will be 5 minutes late
  12 Mar 13 12:01:30 *	mawhalen (n=chatzill@nat/intel/x-d37c35735a30bd53) has joined #ubuntu-mobile
  13 Mar 13 12:01:36 <agoliveira>	Hi all
  14 Mar 13 12:01:40 *	sodarock_happyca is now known as sodarock_laptop2
  15 Mar 13 12:01:46 <lool>	I'll chair the meeting this week as David is in another one
  16 Mar 13 12:01:46 <rustyl_>	what was the URL for the wiki with the agenda?
  17 Mar 13 12:01:50 <tremolux>	'lo
  18 Mar 13 12:01:50 <lool>	https://wiki.ubuntu.com/MobileAndEmbedded/Meeting/20080313
  19 Mar 13 12:02:01 *	agoliveira proposes that every action today should be given to amitk :)
  20 Mar 13 12:02:09 <lool>	We'll start by reviewing last weeks action items
  21 Mar 13 12:02:21 <lool>	[topic] patm to to produce boot charts for squashfs vs ext3 for hardy CB by 13 March. [cted]
  22 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] 
  23 Mar 13 12:02:22 <amitk>	agoliveira: I'm back to thwart your sinister plans
  24 Mar 13 12:02:32 <lool>	I fear patm is going to be in the same call as DannyZ 
  25 Mar 13 12:02:35 <lool>	err davidm
  26 Mar 13 12:02:37 <lool>	sorry DannyZ 
  27 Mar 13 12:02:40 <agoliveira>	Damn... 
  28 Mar 13 12:02:41 <lool>	patm: Are you around?
  29 Mar 13 12:02:46 <patm>	I am 
  30 Mar 13 12:02:49 <lool>	Oh cool
  31 Mar 13 12:02:51 <patm>	but with no boot chart
  32 Mar 13 12:02:55 <lool>	Hmm
  33 Mar 13 12:02:58 *	dop3 has quit (Read error: 104 (Connection reset by peer))
  34 Mar 13 12:03:14 *	KenKC_ (n=KenKC@58.34.234.87) has joined #ubuntu-mobile
  35 Mar 13 12:03:15 *	dop3 (n=dop3@201.37.89.212) has joined #ubuntu-mobile
  36 Mar 13 12:03:17 <patm>	Please carry forward, sorry
  37 Mar 13 12:03:18 <lool>	patm: Should put this on someone else's shoulders?
  38 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
  39 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]
  40 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] 
  41 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]
  42 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] 
  43 Mar 13 12:04:06 *	tonyespy has quit ()
  44 Mar 13 12:04:11 <lool>	davidm didn't manage to work on this last week; he said he would look over the WE
  45 Mar 13 12:04:22 <lool>	agoliveira: I'll let you report directly:
  46 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.
  47 Mar 13 12:05:10 <agoliveira>	So, please, push it forward.
  48 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
  49 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]
  50 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] 
  51 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]
  52 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] 
  53 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
  54 Mar 13 12:06:08 <kyleN>	I have a list of the gettext domains for hildon pkgs
  55 Mar 13 12:06:10 *	mawhalen has quit (Client Quit)
  56 Mar 13 12:06:13 <lool>	Cool; is it published somewhere?  Did you manage to output a mini-map?
  57 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...
  58 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?
  59 Mar 13 12:06:55 <kyleN>	lool, i can email it to you if you are interested
  60 Mar 13 12:07:03 <lool>	kyleN: Doesn't need to be packaged IMO
  61 Mar 13 12:07:17 <lool>	kyleN: I think you should publish it on the wiki as an attachment to langpack research page
  62 Mar 13 12:07:20 <kyleN>	the onees they use
  63 Mar 13 12:07:30 <lool>	Where we identified this as a prereq
  64 Mar 13 12:07:34 <kyleN>	I have not yet done the second half: mapping to upstream
  65 Mar 13 12:07:43 <lool>	Ok; shall I carry on with this part only?
  66 Mar 13 12:07:49 <kyleN>	yes
  67 Mar 13 12:08:10 *	AtomicPunk is now known as ToddBrandtClone
  68 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
  69 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 
  70 Mar 13 12:08:33 <kyleN>	python script plus glade file
  71 Mar 13 12:08:42 <kyleN>	and helper files
  72 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
  73 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 
  74 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
  75 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 
  76 Mar 13 12:09:09 *	bspencer (n=chatzill@nat/intel/x-662268d684ff7442) has joined #ubuntu-mobile
  77 Mar 13 12:09:14 <lool>	kyleN: Tell us all about it!
  78 Mar 13 12:09:21 <kyleN>	sorr - haven't had a chance to hit this one yet...
  79 Mar 13 12:09:29 <kyleN>	please carry over
  80 Mar 13 12:09:32 <lool>	Okay
  81 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]
  82 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] 
  83 Mar 13 12:10:00 <lool>	[topic] lool review progress on Hildon 2.0 updates next week
  84 Mar 13 12:10:02 <MootBot>	New Topic:  lool review progress on Hildon 2.0 updates next week 
  85 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
  86 Mar 13 12:10:34 <lool>	I finished pulling the update this afternoon and will push it after the meeting
  87 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
  88 Mar 13 12:10:58 <lool>	agoliveira missed the action item which was assigned to him when he was away (during last meeting)
  89 Mar 13 12:11:09 <lool>	smagoun: did you manage?
  90 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
  91 Mar 13 12:11:17 <lool>	bspencer: Did Horace manage to do one or two?
  92 Mar 13 12:11:26 <lool>	smagoun: You copy-pasted that!
  93 Mar 13 12:11:30 <lool>	:)
  94 Mar 13 12:11:35 <smagoun>	lool: yes. We have the same boss.
  95 Mar 13 12:11:47 <lool>	mjg59: I think you did at least hildon-theme-layout-4 in bzr
  96 Mar 13 12:12:02 <lool>	Which is the only one you had to do!  100%!
  97 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
  98 Mar 13 12:12:26 <bspencer>	lool: oh, sorry.  I am talking about something else.
  99 Mar 13 12:12:37 <bspencer>	lool:  I don't know of his status for porting Hildon 2.0   I'll check 
 100 Mar 13 12:12:45 <lool>	bspencer: Please check with him
 101 Mar 13 12:12:53 <lool>	It looks like everybody was too busy to do all of it
 102 Mar 13 12:13:10 <lool>	I personally took some notes of the steps I followed and will add them to the wiki page
 103 Mar 13 12:13:13 <lool>	[link] https://wiki.ubuntu.com/MobileAndEmbedded/Hildon2%2e0
 104 Mar 13 12:13:13 <MootBot>	LINK received:  https://wiki.ubuntu.com/MobileAndEmbedded/Hildon2%2e0 
 105 Mar 13 12:13:27 <lool>	I guess we'll have to carry over
 106 Mar 13 12:13:37 <lool>	[action] lool review progress on Hildon 2.0 updates next week [cted]
 107 Mar 13 12:13:37 <MootBot>	ACTION received:  lool review progress on Hildon 2.0 updates next week [cted] 
 108 Mar 13 12:13:46 <lool>	[topic] sabotage to provide drafts of themes tools guide and implementation options as links on the mailing-list
 109 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 
 110 Mar 13 12:14:19 <lool>	Hmm where's sabotage and where's mawhalen?
 111 Mar 13 12:14:33 <lool>	Anyone from Intel can comment on this or grab the relevant people?
 112 Mar 13 12:14:43 <bspencer>	I'll get sabotage... I don't know about mawhalen.  Let's postpone this agenda item for 20mins
 113 Mar 13 12:14:47 <lool>	Yes
 114 Mar 13 12:14:54 <lool>	bspencer: Thanks
 115 Mar 13 12:15:03 <lool>	[topic] ToddBrandt to turn on moblin-settings-daemon's watching of the gtk theme gconf keys
 116 Mar 13 12:15:04 <MootBot>	New Topic:  ToddBrandt to turn on moblin-settings-daemon's watching of the gtk theme gconf keys 
 117 Mar 13 12:15:20 <lool>	ToddBrandt: Did you have a change to work on enabling it?
 118 Mar 13 12:15:27 <lool>	or ToddBrandtClone perhaps?
 119 Mar 13 12:15:47 <ToddBrandtClone>	oh, oy, actually I haven't done that yet
 120 Mar 13 12:15:54 <lool>	Hmm ok
 121 Mar 13 12:15:58 <ToddBrandtClone>	I'll do that today, sorry
 122 Mar 13 12:15:58 <lool>	Bad you
 123 Mar 13 12:16:05 <ToddBrandtClone>	yea, I know, the bugs took priority
 124 Mar 13 12:16:08 <lool>	Carrying to check about it next week
 125 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
 126 Mar 13 12:16:12 <lool>	ToddBrandtClone: ack
 127 Mar 13 12:16:21 <lool>	[action] ToddBrandt to turn on moblin-settings-daemon's watching of the gtk theme gconf keys [cted]
 128 Mar 13 12:16:22 <MootBot>	ACTION received:  ToddBrandt to turn on moblin-settings-daemon's watching of the gtk theme gconf keys [cted] 
 129 Mar 13 12:16:27 <lool>	[topic] rustyl (+ lool if necessary) document release process for Moblin modules
 130 Mar 13 12:16:27 <MootBot>	New Topic:  rustyl (+ lool if necessary) document release process for Moblin modules 
 131 Mar 13 12:16:30 *	ToddBrandtClone hangs head in shame
 132 Mar 13 12:16:34 <lool>	So AFAIK, this happened
 133 Mar 13 12:16:38 <lool>	congrats to rustyl_ 
 134 Mar 13 12:16:51 <lool>	He managed to do tarball releases of almost all moblin projects I think
 135 Mar 13 12:16:56 <lool>	rustyl_: kudos to you!
 136 Mar 13 12:17:05 <rustyl_>	k
 137 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?
 138 Mar 13 12:17:30 *	tonyespy (n=tonyespy@bismuth.canonical.com) has joined #ubuntu-mobile
 139 Mar 13 12:17:51 <rustyl_>	we are working on a presentation
 140 Mar 13 12:17:58 <bfiller>	lool: are there plans to incorporate CDBS into debian/rules so we can make patches?
 141 Mar 13 12:17:59 *	KenKC has quit (Read error: 110 (Connection timed out))
 142 Mar 13 12:18:03 <rustyl_>	it just isn't ready yet
 143 Mar 13 12:18:21 <lool>	bfiller: Yes; I think we'll discuss this in "(lool) Rebasing on the Moblin released tarballs"
 144 Mar 13 12:18:31 <lool>	bfiller: Just after that
 145 Mar 13 12:18:33 <bfiller>	lool: thanks
 146 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
 147 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
 148 Mar 13 12:19:43 <rustyl_>	yea, this needs some discussion
 149 Mar 13 12:19:48 <lool>	Moving on to current items for today's meeting
 150 Mar 13 12:19:58 <lool>	Hmm I'll flip two because one is easier
 151 Mar 13 12:20:05 <lool>	[topic] (lool) Launchpad bugs, ubuntu-mobile subscription, and ume tag
 152 Mar 13 12:20:06 <MootBot>	New Topic:  (lool) Launchpad bugs, ubuntu-mobile subscription, and ume tag 
 153 Mar 13 12:20:07 *	YoungGuo has quit (Read error: 104 (Connection reset by peer))
 154 Mar 13 12:20:25 <lool>	EVERYBODY (that's you) please add the ume tag to LP bugs which concern UME
 155 Mar 13 12:20:31 <lool>	And subscribe the ubuntu-mobile LP team to them
 156 Mar 13 12:20:51 <rustyl_>	lool, is there a way to apply a tag to a collection of bugs?
 157 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
 158 Mar 13 12:21:02 <lool>	rustyl_: Excellent question, I think not
 159 Mar 13 12:21:03 <rustyl_>	or do you have to go through each and every bug
 160 Mar 13 12:21:07 <rustyl_>	darn
 161 Mar 13 12:21:14 <lool>	rustyl_: This would seem to suck
 162 Mar 13 12:21:24 <lool>	rustyl_: You might be able to set it via email though
 163 Mar 13 12:21:57 *	rustyl_ looks to see if his moblin-media bugs are tagged already
 164 Mar 13 12:22:01 *	sabotage (n=sabotage@c-24-22-27-185.hsd1.or.comcast.net) has joined #ubuntu-mobile
 165 Mar 13 12:22:08 <lool>	rustyl_: We have some hacked up python bindings to deal with bug reports though
 166 Mar 13 12:22:20 <lool>	rustyl_: Perhaps you can use these to do as you desire?
 167 Mar 13 12:22:46 <lool>	rustyl_: "python-launchpad-bugs"
 168 Mar 13 12:22:51 *	sabotage hears his name being taken in vain
 169 Mar 13 12:22:55 <rustyl_>	i'll read about it
 170 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
 171 Mar 13 12:23:08 <rustyl_>	ok
 172 Mar 13 12:23:12 <lool>	rustyl_: You'd have to file it against "malone", that's the launchpad bug tracker
 173 Mar 13 12:23:33 <lool>	sabotage: Thanks for coming; I'll reopen your topic now then
 174 Mar 13 12:23:48 <lool>	So please everybody tag and subscribe!
 175 Mar 13 12:23:57 <lool>	And file bugs, don't discuss issues via email or IRC :)
 176 Mar 13 12:24:04 <lool>	[topic] sabotage to provide drafts of themes tools guide and implementation options as links on the mailing-list
 177 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 
 178 Mar 13 12:24:27 <lool>	sabotage: Tears flows on my face: no themes tools guide this week?
 179 Mar 13 12:24:39 <bspencer>	s/don't discuss issues via email or IRC/don't discuss issues JUST via email or IRC
 180 Mar 13 12:24:45 <lool>	bspencer: Right
 181 Mar 13 12:24:52 <lool>	Mention the bug in your email :)
 182 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
 183 Mar 13 12:25:19 <lool>	sabotage: Do you need any help to publish the guide?
 184 Mar 13 12:25:30 <sabotage>	can you make days longer?
 185 Mar 13 12:25:31 <lool>	And your thoughts on implementation options?
 186 Mar 13 12:25:50 <lool>	sabotage: I can keep you up longer before you're allowed to sleep :)
 187 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
 188 Mar 13 12:26:18 *	sabotage was up till 1:30am last night as it is
 189 Mar 13 12:26:22 <lool>	sabotage: Please try to push this out this week -- even a draft
 190 Mar 13 12:26:34 <sabotage>	yep, ball is already rolling
 191 Mar 13 12:26:37 <lool>	Cool
 192 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]
 193 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] 
 194 Mar 13 12:26:59 <sabotage>	is HappyCamp on?
 195 Mar 13 12:27:02 <lool>	Resuming on next item to discuss
 196 Mar 13 12:27:07 *	tonyespy has quit ()
 197 Mar 13 12:27:10 <lool>	[topic] (lool) Rebasing on the Moblin released tarballs
 198 Mar 13 12:27:11 <MootBot>	New Topic:  (lool) Rebasing on the Moblin released tarballs 
 199 Mar 13 12:27:12 <bspencer>	sodarock
 200 Mar 13 12:27:21 <sabotage>	HappyCamp, HappyCamp_ubuntu  need you to read my email and set me up
 201 Mar 13 12:27:23 <lool>	So, we have these cool Moblin tarballs
 202 Mar 13 12:27:29 <sabotage>	this will get the theme guide moving
 203 Mar 13 12:27:45 <lool>	We should move to using them
 204 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
 205 Mar 13 12:28:42 <rustyl_>	lool, i understand
 206 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
 207 Mar 13 12:28:54 <bspencer>	rustyl_: lool:   how does that work again, with ubuntu adding patches on their own?
 208 Mar 13 12:28:54 <lool>	It's similar in spirit to the Hildon 2.0 modules transition
 209 Mar 13 12:28:57 <rustyl_>	and there is confusion on our end
 210 Mar 13 12:29:08 *	bspencer confesses a bit of confusion :)
 211 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
 212 Mar 13 12:29:55 <lool>	rustyl_: Where is the confusion?
 213 Mar 13 12:29:57 <bspencer>	lool:  ok.  I understand.  I missed that patches change
 214 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
 215 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
 216 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
 217 Mar 13 12:31:33 <lool>	rustyl_: Ok, the cool thing is that it's going to be very easy
 218 Mar 13 12:31:39 *	ToddBrandtClone Todd trumps bspencer's confusion
 219 Mar 13 12:31:43 <lool>	Once we get it done *once*
 220 Mar 13 12:31:50 <lool>	Subsequent updates are going to be easy
 221 Mar 13 12:31:55 <GrueMaster>	i fail.
 222 Mar 13 12:32:09 <lool>	ToddBrandtClone: We would like project owners to please continue doing so
 223 Mar 13 12:32:31 <ToddBrandtClone>	lool: ok, our source repo layout has changed so I guess I have some more questions for rusty
 224 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
 225 Mar 13 12:32:58 <rustyl_>	ToddBrandt, the packaging for hardy is not in the source repository
 226 Mar 13 12:32:58 <ToddBrandtClone>	rusty_: do we have a HARDY branch now in addition to GASTON?
 227 Mar 13 12:33:21 <rustyl_>	ToddBrandt, that hardy branch is now defunct 
 228 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
 229 Mar 13 12:33:50 <lool>	ToddBrandtClone: Exactly, that dir you retrieve from the ppa each time you plan an upload
 230 Mar 13 12:33:58 <lool>	ToddBrandtClone: It might have been updated by other folks, for example me
 231 Mar 13 12:33:59 <ToddBrandtClone>	ahhh
 232 Mar 13 12:34:09 <ToddBrandtClone>	the missing piece, I'm learning, gotcha
 233 Mar 13 12:34:12 <rustyl_>	yeap, that's the idea
 234 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
 235 Mar 13 12:34:33 <ToddBrandtClone>	k, thx
 236 Mar 13 12:34:44 <lool>	This is the *target* process
 237 Mar 13 12:34:56 <lool>	Before this, we need to add support for debian/patches/ in each package
 238 Mar 13 12:35:09 <lool>	mjg59 did it in hildon-theme-layout-4
 239 Mar 13 12:35:17 <ToddBrandtClone>	ok, so until then we create the hardy packages like before
 240 Mar 13 12:35:23 <lool>	  * Add simple-patchsys from CDBS
 241 Mar 13 12:35:23 <lool>	  * Build-depend on CDBS
 242 Mar 13 12:35:34 <lool>	That's his changelog entry
 243 Mar 13 12:35:35 <lool>	What we did in debian/rules:
 244 Mar 13 12:35:38 <lool>	- he added:
 245 Mar 13 12:35:38 <lool>	include /usr/share/cdbs/1/rules/simple-patchsys.mk
 246 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
 247 Mar 13 12:35:59 <lool>	- he changed the dependencies of the targets to apply/unapply the patches:
 248 Mar 13 12:36:02 <lool>	build: apply-patches build-stamp
 249 Mar 13 12:36:19 <lool>	This means applying the patches is a prereq for the build
 250 Mar 13 12:36:22 *	tonyespy (n=tonyespy@bismuth.canonical.com) has joined #ubuntu-mobile
 251 Mar 13 12:36:47 <lool>	You might have to rename clean: to clean:: as simple-patchsys.mk defines it as well
 252 Mar 13 12:36:53 <lool>	This is all it takes to add debian/patches support
 253 Mar 13 12:36:55 *	agoliveira is happy that the word "quilt" didn't make into this conversation so far :)
 254 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
 255 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?
 256 Mar 13 12:37:44 <lool>	These changes should be converted to debian/patches/*.patch files
 257 Mar 13 12:38:01 <lool>	bfiller: The person authoring the patch should take care to send it to moblin folks
 258 Mar 13 12:38:16 <rustyl_>	bfiller, i think incorporating existing packages before making a release is a good goal
 259 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
 260 Mar 13 12:38:53 <lool>	Does anybody has any question on how it will work and what remains to be done?
 261 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
 262 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?
 263 Mar 13 12:39:42 <lool>	Perhaps we should file a bug instead of mailing the maintainer?
 264 Mar 13 12:39:56 <lool>	rustyl_: Would that work for you?
 265 Mar 13 12:39:59 <ToddBrandtClone>	I vote for mailing the maintainer, that info would be very useful
 266 Mar 13 12:40:04 <lool>	bfiller: Perhaps opening a bug is more logical than using email
 267 Mar 13 12:40:13 <lool>	ToddBrandtClone: Doesn't the maintainer get an email for new bugs?
 268 Mar 13 12:40:14 <rustyl_>	yes, filling a bug is good
 269 Mar 13 12:40:27 <rustyl_>	the maintainer will get the mail via launchpad
 270 Mar 13 12:40:29 <davidm>	 Can do both but filing a bug is important,  and has been requested by Don Johnson.
 271 Mar 13 12:40:42 <ToddBrandtClone>	ok
 272 Mar 13 12:40:44 <davidm>	Need tracking
 273 Mar 13 12:40:53 <rustyl_>	but we need to cc the devel list for potential discussion on the patch
 274 Mar 13 12:41:22 <lool>	rustyl_: I think that's a logical escalation when a bug fix isn't consensual indeed
 275 Mar 13 12:41:33 <lool>	(or any change, not necessarily a bug fix)
 276 Mar 13 12:42:26 *	andrunko (n=andrunko@200.184.118.132) has joined #ubuntu-mobile
 277 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)?
 278 Mar 13 12:42:46 <davidm>	lool, yes please
 279 Mar 13 12:42:51 <ToddBrandtClone>	yes
 280 Mar 13 12:42:54 <rustyl_>	yes
 281 Mar 13 12:42:57 <cwong1>	+1
 282 Mar 13 12:43:10 <lool>	[action] lool to document tarball release + ppa upload process and patch addition + submission process
 283 Mar 13 12:43:11 <MootBot>	ACTION received:  lool to document tarball release + ppa upload process and patch addition + submission process 
 284 Mar 13 12:43:15 <davidm>	Just out of the other meeting, sorry I'm late.
 285 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
 286 Mar 13 12:43:45 <lool>	This requires adding support for debian/patches and extracting the current ppa-only changes as patch files
 287 Mar 13 12:43:58 <lool>	I propose we split that like the Hildon 2.0 modules
 288 Mar 13 12:44:08 <lool>	Does that work for everybody?
 289 Mar 13 12:44:20 <lool>	rustyl_: Would you be willing to participate?
 290 Mar 13 12:44:37 <lool>	Who from Intel would be willing to take a share?
 291 Mar 13 12:44:54 <lool>	Everybody I guess! :)
 292 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
 293 Mar 13 12:45:16 <bspencer>	mawhalen -- since she's not here.
 294 Mar 13 12:45:27 <rustyl_>	i just need the first package to cookbook from
 295 Mar 13 12:45:27 <lool>	rustyl_: deal
 296 Mar 13 12:45:56 <rustyl_>	and by several, i mean i can find people to do all the rest of the moblin projects
 297 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?
 298 Mar 13 12:46:12 <lool>	rustyl_: Cool
 299 Mar 13 12:46:57 <lool>	[action] lool to send rustyl_ steps to update ppa packages for the new tarball based release process
 300 Mar 13 12:46:58 <MootBot>	ACTION received:  lool to send rustyl_ steps to update ppa packages for the new tarball based release process 
 301 Mar 13 12:47:15 <lool>	[action] rustyl_ to assign ppa packages updates for the new tarball based release process
 302 Mar 13 12:47:16 <MootBot>	ACTION received:  rustyl_ to assign ppa packages updates for the new tarball based release process 
 303 Mar 13 12:47:33 <lool>	Does anybody have any question on this?
 304 Mar 13 12:47:38 <rustyl_>	yea
 305 Mar 13 12:47:50 <rustyl_>	what 'project' to i write launchpad bugs against?
 306 Mar 13 12:47:56 <rustyl_>	'launchpad' doesn't work
 307 Mar 13 12:48:09 <lool>	rustyl_: To report the malone bug?
 308 Mar 13 12:48:39 <rustyl_>	to report the 'i want to assign a tag to a couple hundred bugs at once' feature request
 309 Mar 13 12:48:40 <lool>	rustyl_: https://bugs.launchpad.net/bugs/+filebug select "Project" type "malone" and search
 310 Mar 13 12:48:54 <lool>	s/search/choose
 311 Mar 13 12:49:02 <rustyl_>	what is malone?
 312 Mar 13 12:49:21 <lool>	As I was saying earlier, it's the Launchpad bug tracking subproject
 313 Mar 13 12:49:35 <rustyl_>	got it
 314 Mar 13 12:49:53 <lool>	rustyl_: https://launchpad.net/projects/?text=launchpad 
 315 Mar 13 12:50:01 <lool>	rustyl_: You'll see "Launchpad Bugs"
 316 Mar 13 12:50:06 *	tonyespy has quit ()
 317 Mar 13 12:50:08 <rustyl_>	https://bugs.launchpad.net/malone/+bug/201874
 318 Mar 13 12:50:09 <lool>	It's technical/unix name is "malone"
 319 Mar 13 12:50:09 <ubotu>	Launchpad bug 201874 in malone "Need ability to apply tag to a collection of bugs" [Undecided,New] 
 320 Mar 13 12:50:15 <lool>	rustyl_: Tada
 321 Mar 13 12:50:25 <bfiller>	slightly obscure, I'd say :)
 322 Mar 13 12:50:33 <bfiller>	malone, that is
 323 Mar 13 12:50:43 <rustyl_>	it keeps thing mysterious
 324 Mar 13 12:51:03 <bfiller>	good way to keep people from filing bugs :)
 325 Mar 13 12:51:05 <GrueMaster>	Nah, it's perfectly intuitive.
 326 Mar 13 12:51:14 <lool>	Let's end the meeting in a mysterious way then!
 327 Mar 13 12:51:19 <agoliveira>	rustyl_: Santa Rosa? Diamondville? McAslin?
 328 Mar 13 12:51:21 <agoliveira>	:)
 329 Mar 13 12:51:35 <lool>	[endmeeting] malone! soyuz!
 330 Mar 13 12:51:40 <lool>	#endmeeting