[02:50]  * lfaraone waves.
[03:23] <gonzalo> Hi, I have a problem in sugar-jhbuild on ubuntu lucid
[03:37] <lfaraone> gonzalo: ask in #sugar, prolly.
[03:38] <gonzalo> thanks
[03:50] <lfaraone> dfarning: btw, Ubuntu Feature Freeze is sometime todayish
[04:47] <dipankar> lfaraone: aroud?
[04:47] <lfaraone> dipankar: for a little while.
[04:48] <dipankar> lfaraone: just wondering, if I make any changes to my git.debian repo, will they be automatically synced to debian repository?
[04:48] <lfaraone> dipankar: No.
[04:48] <dipankar> * after they are being sponsored
[04:49] <dipankar> ohk
[04:49] <dipankar> lfaraone: then what is the way proper way to work that out?
[04:49] <lfaraone> dipankar: changes to git.d.o are only that. They have to be uploaded by someone with permissions, ie me.
[04:50] <dipankar> lfaraone: ohk
[04:50] <dipankar> lfaraone: so, any packaging work left?
[04:51] <lfaraone> dipankar: probably.
[04:52] <lfaraone> dipankar: from my quick look, sliderpuzzle. paint, flipsticks (frozen). and I need to review speak in full, I think.
[04:52] <dipankar> lfaraone: just curious, any update on 'polyol'? (Flipsticks activity depends on it and till last time the packaging of polyol was not done)
[04:53] <lfaraone> dipankar: I have no idea what polyol is.
[04:56] <dipankar> lfaraone: man, you are getting forgetful :P. Filpsticks currently is on 'toolkit' which has gone obsolete. 'polyol' is the replacement of toolkit. remember alsroot saying this.
[04:57] <lfaraone> dipankar: it's been at least a week and a half :)
[04:58] <dipankar> lfaraone: hehe
[04:58] <lfaraone> alsroot: is polyol in a place where it can be packaged?
[05:03] <dipankar> lfaraone: I guess alsroot is not online
[05:03] <dipankar> * s/online/here
[05:04] <lfaraone> dipankar: I'm sure he'll be around at some point.
[05:04] <lfaraone> As for me, I'm off to bed. Ttyl.
[05:05] <dipankar> lfaraone: sure. Good night :)
[05:28] <dipankar> alsroot: around?
[14:14]  * lfaraone waves morning.
[14:46] <dipankar> dfarning, hello
[15:06] <dipankar> manusheel, hello sir
[15:06] <manusheel> dipankar: Hi Dipankar.
[15:07] <manusheel> dipankar: Let me send you the Tam Tam mini issue number.
[15:07] <manusheel> dipankar: https://bugs.edge.launchpad.net/ubuntu/+source/sugar-0.88/
[15:07] <dipankar> manusheel, ok sir
[15:07] <satellit___> manusheel: is there a download site for USR  .iso's (I know it was being moved yesterday)
[15:11] <manusheel> dipankar:satellit_, I'll need to ask David on it.
[15:11] <satellit___> thanks
[15:11] <manusheel> satellit_: Will ask him the URL today.
[15:11] <manusheel> kandarpk: Hi Kandarp.
[15:12] <dipankar> * yeah I was looking for the same
[15:12] <kandarpk> manusheel sir: Hello sir.
[15:12] <dipankar> dfarning, around?
[15:13] <manusheel> kandarpk: Did we get an understanding on animator.py?
[15:13] <manusheel> kandarpk: Will we be able to send the first set of patch with the docstrings today?
[15:13] <kandarpk> manusheel sir: I'll try, not very sure.
[15:14] <kandarpk> manusheel sir: packaged exe yesterday and pushed to it to the repo., so will spend time studying the code today.
[15:15] <dipankar> manusheel, Sir, I think the Sugar people are out with a fix for the bug Tam Tam not starting
[15:16] <manusheel> kandarpk: Sure. Make a google spreadsheet today, and have 3 sheets - (functions, classes, variables) in it. List down the functions, classes and variables used in animator.py. Then, start with writing the description, whatever we are able to understand. Let us complete this spreadsheet for animator.py today.
[15:16] <manusheel> dipankar: Ok.
[15:16] <kandarpk> manusheel sir: Ok.
[15:17] <manusheel> dipankar: Can you tell me who started working on this issue?
[15:18] <dipankar> manusheel, Sir, I think alsroot worked on it
[15:18] <dipankar> * as David has thanked alsroot for the patch on 64 bit system
[15:20] <manusheel> dipankar: Ok.
[15:21] <alsroot> TamTam uses custom .so, it could be build while packaging to suppress any further prolems
[15:21] <manusheel> alsroot: Thanks for the pointer. Appreciate it.
[15:22] <dipankar> manusheel, now I remember David told me that Luke has worked on .so
[15:23] <dipankar> lfaraone, around?
[15:23] <lfaraone> dipankar: yes.
[15:24] <manusheel> dipankar: Ok.
[15:24] <dipankar> lfaraone, dfarning told me that you have worked on .so files in packaging (I don't know what he exactly meant)
[15:25] <lfaraone> dipankar: I'm not sure what he meant either.
[15:25] <dipankar> lfaraone, here is the actual issue
[15:27] <dipankar> lfaraone, https://bugs.edge.launchpad.net/ubuntu/+source/sugar-0.88/+bug/502991
[15:27] <dipankar> lfaraone, this bug requires handling .so files in packaging
[15:28] <dipankar> as told to me by David
[15:29] <dipankar> alsroot, sorry for my ignorance could you explain a bit on this: "TamTam uses custom .so, it could be build while packaging to suppress any further problems"
[15:29] <lfaraone> dipankar: that's intereting. I still have no idea what he wants you to do.
[15:30] <lfaraone> it is most def not a bug in sugar-0.88,
[15:30] <lfaraone> *.
[15:31] <alsroot> dipankar: .xo w/ TamTam contains bunch of blobs (per arch/csound-version), but sources of course doesn't, so spec file should build them from these sources http://git.sugarlabs.org/projects/tamtam-branch/repos/mainline/trees/master/common/Util/Clooper
[15:34] <dipankar> alsroot, thanks
[15:35] <dipankar>  :? tam tam files are in C/C++ !!
[15:37] <manusheel> ankur: Hi Ankur. Around?
[15:39] <manusheel> kandarpk: Have we completed the spreadsheet?
[15:40] <manusheel> on animator.py?
[15:40] <kandarpk> manusheel sir: I am browsing through the code trying to understand it.
[15:42] <manusheel> kandarpk: ok.
[15:49] <ankur> manusheel,  sir yes :)
[15:49] <manusheel> ankur: Send you the e-mail.
[15:49] <manusheel> usr..@dev..
[15:50] <manusheel> ankur: with login details.
[15:50] <manusheel> ankur: you can send across the e-mail today.
[15:50] <manusheel> ankur: How is 6th bug coming along?
[15:50] <manusheel> Have we completed it?
[15:50] <ankur> manusheel,  was just reading that , does everybody have different account ? i mean do we need to change the password?
[15:50] <ankur> manusheel,  will send the mail today
[15:51] <ankur> manusheel sir , was just creating the patch , identified the changes to be made
[15:57] <ankur> dipankar,  is this the right page to download dsc file ? http://packages.ubuntu.com/en/lucid/i386/python-sugar-toolkit-0.88
[15:57] <manusheel> ankur: no need to change the password.
[15:57] <manusheel> ankur: wrote it by mistake.
[15:57] <manusheel> ankur: Everyone has the same account.
[15:57] <ankur> manusheel sir okay :)
[15:57] <dipankar> ankur, yup, its for ubuntu
[15:58] <ankur> so the link given in side is for dsc file , is that right?
[15:59] <manusheel> ankur: why are we using the lucid link?
[15:59] <manusheel> dipankar: ^^
[16:00] <dipankar> manusheel, I have just setup maverick and am facing trouble with adding ppa in that
[16:00] <dipankar> so I reverted back to lucid
[16:00] <dipankar> * switched
[16:01] <manusheel> dipankar: ok. ppa is no longer supported in maverick.
[16:02] <manusheel> dipankar: do we have maverick?
[16:02] <dipankar> manusheel, Ok sir
[16:02] <manusheel> dipankar: Once you are at maverick, do sudo apt-get install sugar-emulator-0.88
[16:03] <manusheel> ankur: ^^
[16:03] <dipankar> manusheel, Ok sir. i thought we have to use the ppa
[16:03] <dipankar> to download USR
[16:03] <manusheel> dipankar: Then install activities via synaptic manager.
[16:03] <dipankar> and tet
[16:03] <ankur> i was not able to find the link  for maverick packages , and i dont know i uploaded the packages for maverick on ppa and they were not there after some time. might be some reasone that they were deleted
[16:03] <ankur> manusheel,  sir i need to get packages source , any hints here , i am creating patch for ftime
[16:03] <ankur> i was in lucid now
[16:03] <kandarpk> alsaroot: can you recall what _timeout_sid is used for in animation ? http://paste.ubuntu.com/476977/
[16:04] <lfaraone> alsroot: in sugar-speak-activity, do we know where chat.py, chatbox.py, messenger.py, espeak.py, espeak_cmd.py, espeak_eye.py came from?
[16:04] <manusheel> ankur: switch to maverick first.
[16:04] <ankur> neeraj said it was okay that if i create patch from lucid or maverick.......
[16:04] <manusheel> ankur: Better use maverick.
[16:04] <dipankar> ankur, debcheckout
[16:04] <dipankar> ankur, or try : apt-get source <package-name>
[16:05] <manusheel> dipankar: right. Ankur, use debcheckout. or ^^
[16:05] <alsroot> lfaraone: but these files are in activity root directory
[16:05] <dipankar> ankur, you will get the upstream original
[16:05] <ankur> dipankar,  i know that but still , does it make difference if i i download it from debcheckout or using dsc file as neeraj expalined.
[16:05] <ankur> dipankar,  okay
[16:05] <lfaraone> alsroot: right, but they're unattributed.
[16:05]  * alsroot got what lfaraone meant y "came from"
[16:06] <lfaraone> alsroot: chatbox.py indicates that it might have come from Chat.activity
[16:06] <lfaraone> alsroot: and therefore was authored by... :)
[16:06] <lfaraone> alsroot: copyrights are fun :)
[16:06] <alsroot> lfaraone: ok, I'll parse git log and tweak these files and will release v17 tarball
[16:07] <lfaraone> alsroot: cool, thanks.
[16:07] <dipankar> ankur, sometimes its better to use debcheckout or apt-get source, than locating a wrong .dsc file :)
[16:07] <ankur> dipankar,  thanks
[16:08] <dipankar> mention not :)
[16:08] <ankur> manusheel,  sir i need to get to maverick and update it....... will take time, will get back to you. I ahvent used it for some time.
[16:11] <manusheel> ankur: Ok.
[16:11] <manusheel> Please use Maverick only.
[16:11] <ankur> manusheel,  sir can i use lucid to patch it for now and then use maverick.
[16:11] <manusheel> ankur: Don't back port to Lucid if you have any issues.
[16:11] <ankur> will take some time to set up maverick
[16:12] <ankur> may be today will go into that only
[16:12] <manusheel> ankur: I would say first shift to Maverick, and then create a patch.
[16:12] <ankur> manusheel sir , okay
[16:12] <manusheel> ankur: We had lot of confusions on that part yesterday.
[16:12] <ankur> will create patch afterwards then.
[16:13] <manusheel> ankur: Yes, once you have Maverick with you.
[16:13] <dfarning> dipankar, there is no need to use a ppa in maverick. all of our packages are in universe.... that is something neeraj is doing.
[16:13] <ankur> shiftinf to maverick from now. Need to set it up , register keys and update software as well.
[16:13] <dipankar> dfarning, ohk.
[16:13] <manusheel> ankur: sure.
[16:14]  * ankur going as of now , will be back when shift to maverick , wil take time.
[16:14] <dfarning> dipankar, the ppa (in lucid ) was just a sandbox for learning to package.
[16:15] <dfarning> dipankar, did you still have questions about TamTam?
[16:16] <dipankar> dfarning, yeah. about Tam tam. hwo do I start?
[16:17] <dfarning> dipankar, let me download it and look. did alsroot explain what I meant by blobs?
[16:17] <kandarpk> manusheel sir: around ?
[16:18] <dipankar> dfarning, I actually couldn't get back to alsroot regarding this
[16:18] <dipankar> dfarning, I was trying to install sugar
[16:19] <alsroot> lfaraone: there are also bunch of files in bundled PyAIML that are also w/o copyright notes, is it ok?
[16:20] <manusheel> kandarpk: yes.
[16:20] <manusheel> kandarpk: How are things progressing?
[16:20] <kandarpk> manusheel sir: need help
[16:20] <dipankar> dfarning, oh here it is : <alsroot> dipankar: .xo w/ TamTam contains bunch of blobs (per arch/csound-version), but sources of course doesn't, so spec file should build them from these sources http://git.sugarlabs.org/projects/tamtam-branch/repos/mainline/trees/master/common/Util/Clooper
[16:20] <kandarpk> the code is at http://paste.ubuntu.com/476977/
[16:20] <manusheel> kandarpk: ok, tell me.
[16:20] <kandarpk> manusheel sir ^^
[16:21] <manusheel> kandarpk: ok.
[16:22] <lfaraone> alsroot: uh? not really.
[16:22] <alsroot> lfaraone: but it external project, not Speak
[16:22] <lfaraone> alsroot: hmmm
[16:24] <lfaraone> alsroot: we probably should strip that out from the tarball, it should be pulled out as a separate package.
[16:25] <alsroot> lfaraone: I'm afraid, Speak sources should be patched in that case, does debian/ubuntu have pyaiml package?
[16:26] <lfaraone> alsroot: no, but we should.
[16:26] <lfaraone> alsroot: right now I'm looking at the license for pyaiml, it is rather... colorful: "I hate legalese. This software is free to use and distribute however you'd like. I'm not aware of any catastrophic bugs, but please don't come crying to me if this software fries your board. Void where prohibited. No purchase necessary. You must be 18 or older to make this call. For indoor or outdoor use ONLY. We live for the One, we die for the One."
[16:26] <dfarning> lfaraone,  that ^^ was what I was talking about:(  sorryy for being unclear.... several XO files in aslo have binary blobs for cross arch compatibility.
[16:26] <dipankar> dfarning, 2 minutes and I have sugar on maverick
[16:27] <alsroot> lfaraone: I guess it could be considered as Public Domain :)
[16:28] <dipankar> dfarning, what is the new download link for USR? it is moved I guess
[16:29] <lfaraone> dfarning: feature freeze is in effectl.
[16:29] <lfaraone> alsroot: http://sprunge.us/OdUG <_<;
[16:30] <dfarning> dipankar, I have not gotten a iso to rebuild since I moved it.  do you have a iso from last week around?  or I can rebuild on on the old site?
[16:30] <lfaraone> alsroot: as of current, although it appears to be tounge-in-cheek, it's ambiguous.
[16:30] <dfarning> lfaraone, what does that mean for us beside need exceptions?
[16:31] <dipankar> dfarning, I have the older one which worked perfectly. I don't have the last week's
[16:31] <lfaraone> alsroot: from a legal perspective, it is contradictory and probably as a whole invalid.
[16:31] <lfaraone> dfarning: we need an exception.
[16:31] <dipankar> dfarning, I think neeraj will be having it
[16:31] <dfarning> dipankar, ok please you neeraj's copy.
[16:32] <dipankar> dfarning, actually satellit__ was asking for it
[16:32] <dipankar> dfarning, <satellit___> manusheel: is there a download site for USR  .iso's (I know it was being moved yesterday)
[16:32] <dfarning> lfaraone, is it clear what what need to be done for TamTam mini?
[16:33] <alsroot> lfaraone: anyway, from my pov, only one thing is important - name of pythom modules directory which will contain pyaiml on installed system, I guess it will aiml (subdirectory from pyaiml tarball). I will patch Speak sources to not fail if pyaiml is installed from native packages will strip pyaiml from sources and will release v17 tarball
[16:33] <lfaraone> alsroot: I'm talking with the folks on #debian-devel as to what we can do.
[16:33] <lfaraone> alsroot: okay, cool. I'll wrangle with the pyamil licnsing.
[16:33] <dfarning> dipankar, I'll work on the new build machine today.
[16:33] <dipankar> dfarning, ohk sure
[16:33] <lfaraone> dfarning: I have no idea. I wasn't aware we were shipping TamTam mini.
[16:36]  * dipankar is off to dinner
[16:36]  * dipankar is away: Be Right Back
[16:36] <dfarning> lfaraone,  SoaS does not ship it.  If it looks too hard we can drop it for this release and add it next release.  I wanted dipankar to dig into to problem.
[16:37] <dipankar> lfaraone, dfarning, I will be right back after dinner
[16:37] <dfarning> dipankar, see you.
[16:39] <dfarning> ishan, what are you working on this evening?
[16:39] <ishan> dfarning, hi
[16:39] <dfarning> ishan, hello
[16:40] <ishan> i am presently working on error bugging part
[16:40] <dfarning> ishan, what part of it are you working?
[16:42] <ishan> dfarning, presently i just started working on it and I am trying to reproduce the listed errors
[16:43] <dfarning> ishan, Ahh one of the cases where the log reports an error instead of a warning?
[16:50] <lfaraone> dfarning: so as is, speak is halted because the PyAIML code A) needs to be separately packaged, and B) cannot be distributed in Debian because it probably fails the DFSG. Mail arriving in your inbox to the author CCing you momentarily.
[16:52] <dfarning> lfaraone, sounds good.  now we just wait for a response from the author about the liscense?
[16:52] <lfaraone> dfarning: yes.
[16:52] <lfaraone> dfarning: the "license" is comical.
[16:54] <dfarning> ishan, what error are you looking for? the best tool is grep to search through the source for the error.
[16:55] <ishan> dfarning, i am presently trying to reproduce the errors on my system
[16:56] <dfarning> lfaraone, I can see why debain would have some concern about the liscensing:)
[16:56] <dfarning> ishan, what is the error?
[16:56] <manusheel> dfarning: Ishan is working on the bugs that we have assigned the team.
[16:58] <manusheel> dfarning: bugs #7, 9, 10 ana 11 were not reproducible on maverick emulator.
[16:59] <manusheel> dfarning: maverick sugar emulator*
[16:59] <dfarning> manusheel, which bug list are you looking at?
[16:59] <alsroot> lfaraone: btw you regenerate locale/ by calling `./setup.py build` while creating binaries?
[16:59] <lfaraone> alsroot: we might.
[17:00] <lfaraone> alsroot: we *do* call setup.py build, that is.
[17:00] <alsroot> lfaraone: I'm just using 0sugar to create tarball, ok, fine then
[17:00] <manusheel> dfarning: 11 bugs that we started with in sugar emulator on maverick. Let me send you the bug names.
[17:01] <dfarning> manusheel, thanks.
[17:03] <manusheel> dfarning: send.
[17:05] <alsroot> lfaraone: also another thing, just let you know, in 0sugar, I follow regular way for tarring sources, e.g., tarred root directory will be speak-17/ not Speak.activity
[17:05] <lfaraone> alsroot: that's fine, dpkg doesn't care :)
[17:06] <dfarning> manusheel, for 10 try starting sugar in emulator, switching to a different window, and then switching back to the sugar window, then using the function keys to switch views.
[17:07] <dfarning> manusheel, hmmm I can't reporduce it today either.....
[17:07] <manusheel> dfarning: ok. Thanks for the pointer. I had ask the team to define QA scenarios if the bug was not reproducible.
[17:07]  * lfaraone is now investigating turtleart's copyright.
[17:08] <manusheel> dfarning: Ok, I'll update the sheet on bugs, once the investigation has been done.
[17:08] <manusheel> lfaraone: Thanks,
[17:11] <manusheel> let me know if Mukul has done it correctly.
[17:11] <dfarning> manusheel, the problem with #7 is probobly rather complicated.
[17:11] <manusheel> lfaraone: Will ask him to make changes.
[17:11] <manusheel> if required.
[17:11] <manusheel> dfarning: Ok.
[17:12] <lfaraone> manusheel: sorry, I'm not sure we're talking about the same thing.
[17:12] <dfarning> manusheel, for example when changing the time in the time zone in the control panel you must restart the computer for it to take effect.
[17:12] <lfaraone> manusheel: I'm talking about the "turtleart" package, which provides turtleart for GNOME / window-manager / non-sugar enviorns.
[17:13] <manusheel> lfaraone: Ok. Thanks for the clarification. Appreciate it.
[17:13] <lfaraone> manusheel: I'm not sure what you mean, that is.
[17:13] <dfarning> manusheel, this is probobly a fundemental problem with sugar design.  for example when changing the time zone in gnome you don't need to restart the computer.
[17:14] <manusheel> dfarning: ok. That means we should arrive at the list of scenarios, and do the feature request.
[17:14] <manusheel> lfaraone: I was referring to packaging of turtle art activity.
[17:14] <lfaraone> dfarning: "fundamental", perhaps not, it could require some small changes in the code to make better use of changes in gconf
[17:16] <dfarning> manusheel, hmm 9 works for me today:)  did not work yesterday:(
[17:16] <lfaraone> manusheel: okay. it's not on Sugar/Tasks as far as I can tell, so I have no basis for knowing about it or having it in the review queue. I suspect that the work will be partially duplicated, because once TA is packaged wrapping it for Sugar is straightforward.
[17:16]  * dipankar is back (gone 00:40:15)
[17:17] <lfaraone> manusheel: was Mukul packaging turtleart or turtleblocks?
[17:18] <dipankar> lfaraone, mukul was packaging turtleart
[17:18] <manusheel> dfarning: Ok :-)
[17:18] <dfarning> lfaraone, WRT to the start full screen issues.  do you know if it is possible to add a "full screen" window decorator to a xypher window?  That would solve the problem.
[17:19] <lfaraone> dfarning: I do not know.
[17:19] <dipankar> dfarning, +1 with your idea
[17:19] <dfarning> manusheel, can you assign some one to see about the possibility of ^^?
[17:20] <manusheel> lfaraone: Mukul is packaging TA. Will be getting it added at the Sugar/Tasks page.
[17:20] <manusheel> dfarning: Sure.
[17:20] <dfarning> manusheel, thanks
[17:21] <dipankar> dfarning, any pointers on the tam tam problem?
[17:21] <dipankar> * after what alsroot mentioned
[17:23] <dfarning> dipankar, lfaraone and alsroot were discussing it.  the hinging point is package pyAIML as a seperate package,  luke sent the author a note about a issues with the liscense.
[17:24] <lfaraone> dfarning: oh? does TamTam use pyAIML? I was talking about Speak.
[17:24] <dfarning> lfaraone,  opps I though you were talking about TamTam
[17:24] <dipankar> dfarning, It seems that whatever package I work on (Flipsticks or Tam Tam), they have complex dependency problems
[17:25] <dfarning> dipankar, just bad luck:(
[17:25] <dipankar> dfarning, btw what are blobs?
[17:25] <lfaraone> dipankar: http://en.wikipedia.org/wiki/Binary_blob
[17:25] <alsroot> lfaraone: done, http://download.sugarlabs.org/sources/honey/Speak/speak-17.tar.gz
[17:26] <lfaraone> alsroot: cool, thanks.
[17:32] <dfarning> dipankar, in the case of some XOs bundles they sometimes have dependencies recompiled into them for cross arch compatibility.  as packagers these are 'binary blobs.'
[17:36] <manusheel> dfarning: Dipankar got disconnected due to some internet issues. Will be back.
[17:36] <manusheel> dfarning: I'll send him your message.
[17:36] <dfarning> manusheel, thank
[17:36] <manusheel> dipankar: David wrote - dfarning> dipankar, in the case of some XOs bundles they sometimes have dependencies recompiled into them for cross arch compatibility.  as packagers these are 'binary blobs.'
[17:36] <dipankar> * just some internet jerk
[17:38] <dipankar> dfarning, manusheel : 'recompiled into them' : meaning : they are already kind of patched?
[17:38] <dipankar> instead of making them as separate package?
[17:42] <dfarning> dipankar, yes, they have a binary patch that must be built correctly from source.
[17:42] <manusheel> kandarpk: Hi Kandarp.
[17:43] <kandarpk> manusheel sir: yes sir.
[17:43] <manusheel> kandarpk: Kindly send the e-mail for review to me.
[17:46] <lfaraone> manusheel: turtleart is a bit special, since the same codebase functions as both an application and an activity. packaging it will be non-typical.
[17:46] <manusheel> lfaraone: Ok. Thanks for the pointer.
[18:36] <dfarning> lfaraone, what do you recommend for a method of submitting fixes to ubuntu.  It looks to me like we should 1) Make patches and apply them using quilt 2) Attach a debdiff to a bug in LP and 3) request that you sponsor uploading the debdiff.
[18:37] <lfaraone> dfarning: That's the most popular way.
[18:39] <lfaraone> dfarning: There are particular elements inside Ubuntu that are trying to move to bzr branches rather than debdiffs and source packages, but although I've found them easy to produce (if you know bzr) they are less popular with the rest of the community, put more work on reviewers, and aren't really mature enough for prime-time.
[18:41] <dfarning> lfaraone, ok let's go go with quilt patches for now we can switch later if necessary.
[18:41] <lfaraone> dfarning: yeah, with bzr branches you'd still need quilt patches, you'd just be pushing up a branch rather than generating and attaching a debdiff.
[18:42]  * lfaraone will be back, foodseek.
[18:42] <dfarning> lfaraone, ok thanks.  I'll write up a step by step guild for how to do this with sugar packages tonight.
[18:46] <manusheel> lfaraone, dfarning: Very neat.
[18:46] <manusheel> I'll have a look at .bzr packaging too.