[00:00] <fta> http://weblogs.mozillazine.org/gerv/archives/2008/06/firefox_3_language_coverage.html
[00:38] <rzr> hi, someone can review my branch https://bugs.edge.launchpad.net/ubuntu/+source/flashblock/+bug/239151 ?
[00:51] <Jazzva> rzr, looks good. I suppose the changelog entry will be adjusted at the end :). If there are important changes in the new version, beside the bugfix, maybe it's good to mention them too. And it would be good if you could be sure that it closes the bug.
[00:52] <gnomefreak> anyone know of a phone(hardware) you hook up to PC for VoIP?
[00:52] <rzr> i have a friend that uses a usb on
[00:52] <gnomefreak> rzr: do you know the name?
[00:52] <rzr> i can ask hime the references
[00:52] <rzr> i know my friend name yes :)
[00:53] <Jazzva> Great ... skype site thinks my locale is czech (cs) instead of serbian (sr... or I think rs is the new one)
[00:53] <gnomefreak> not his the name of the hardware and or service
[00:53] <Jazzva> Though, we did use some variants of cs before ... I think
[00:53] <rzr> gnomefreak: i think it was designed to be used w/ skype but he uses wengo w/ it
[07:59] <asac> oh darn, working since 7:30 ... and already fed up :/
[08:03] <rzr> weekend is near
[08:03] <asac> yay
[08:05] <rzr> asac: can you remind me how to assign a branch for review regarding bug https://bugs.edge.launchpad.net/ubuntu/+source/flashblock/+bug/239151
[08:05] <rzr> should I only change bug status ?
[08:05] <rzr> to fix commited ?
[08:06] <rzr> well I'll RTFM this week end :)
[08:10] <asac> rzr: ask for your branch to be merged in the release branch
[08:11] <asac> but bug status is more important I would say
 rzr: ask for your branch to be merged in the release branch
[08:11] <rzr> isnt it already set ?
[08:12] <asac> havent looked ;)
[08:12]  * asac looks at bug
[08:13] <asac> rzr: did you "propose for merging" on this page: https://code.edge.launchpad.net/~rzr/firefox-extensions/flashblock.ubuntu ?
[08:13] <rzr> no I just linked to bug and set fix available
[08:14] <asac> rzr: ok i asked for merging now
[08:14] <rzr> i was about to
[08:14] <asac> (its not really important after all, but a nice feature of launchpad imo)
[08:15] <asac> rzr: FIX: sync upstream via LP : http://bazaar.launchpad.net/~rzr/firefox-extensions/flashblock.upstream/revision/4
[08:15] <asac> why do you call this a "FIX" ?
[08:15] <rzr> it'll fix a bug
[08:16] <asac> rzr: ah. ok. consider to use the form we use in changelog
[08:16] <asac> e.g.
[08:16] <rzr> thx, well i'll be back this evening ... I have some rude work to be done until next week
[08:16] <asac> Fix LP: #XXXXX - flashblock crashes all the time; we fix this by updating to latest
[08:16] <rzr> ok will do now
[08:16] <asac> or something more verbose :)
[08:16] <asac> thanks
[08:17] <asac> its just a hint. not important as long as the bug is documented in debian/changelog
[08:17] <asac> cu around
[11:21] <Bombela> Hello all
[11:21] <Bombela> I have just an question for the mozilla license
[11:21] <Bombela> i want use the MPL for my code, but i want sure to understand one point
[11:22] <Bombela> (sorry for my bad english)
[11:22] <Bombela> i want my code always free : when people modifie it,my code must be redistribued with modification
[11:24] <Bombela> and if an entreprise want use my code in proprietary program, it's must be possible, bu my modified code must be always redistributed
[11:24] <Bombela> Mozilla license make this ?
[11:27] <asac> Bombela: I'd suggest to use LGPL if you have those requirements
[11:27] <asac> that allows proprietary software to link against it without requiring the proprietary code to be GPL
[11:27] <asac> but still changes to the LGPL part needs to be redistributed
[11:34] <Bombela> but my code can be embeded in the application
[11:35] <Bombela> not only linked
[11:35] <Bombela> it's linked staticly
[11:35] <Bombela> and the LGPL it's only allowed to link dynamicly no ?
[11:36] <Bombela> (i will be back later)
[11:43] <asac> Bombela: hard to say. i think its a matter of how decoupled the code is
[11:43] <asac> if you only use public exported API there shouldnt be much a difference
[11:44] <asac> if LGPL doesnt suite you then there is not license that fits your needs i guess
[11:44] <asac> Bombela: but you can always grant more rights.
[11:45] <asac> you could add a clause that explicitly allows you to link statically under conditions: a) only use public API b) modifications to your part are still to be redistributed
[11:48] <Bombela> mmm cool
[11:50] <Bombela> by what the différence between MPL and LGPL then ?
[11:50] <Bombela> i will read more documentation, and thank you for your help.
[12:01] <asac> mozilla bug 438688
[12:01] <asac> Bombela: MPL is considered not really free by some
[12:02] <asac> its more like GPL from what i understand
[12:02] <asac> but i might be just misinformed about MPL
[12:02] <asac> i dont care that much about
[12:59] <Bombela> ok thank
[14:22] <fta> debian bug 474353
[14:25] <asac> XCB?
[14:25] <fta> nm
[14:25] <asac> what is that?
[14:26] <asac> ah "X protocol C-language Binding (XCB)"
[14:27] <fta> http://xcb.freedesktop.org/
[14:29] <fta> asac, I wanted to make flock use the gre plugins/addons so i reused bzXXX_gre_extension_plugin_support.patch from our xul, it doesn't work. do i need something else ?
[14:30] <asac> hmm
[14:30] <asac> bzXXX_autoconfig_in_gre.patch
[14:30] <asac> bzXXX_gre_autoreg.patch
[14:31] <asac> bzXXX_gre_extension_plugin_support.patch
[14:31] <asac> try to take all and see if things improve
[14:31] <asac> fta: maybe the addons are not used because they dont have the flock em:id as a targetApplication?
[14:32] <fta> i'm looking for plugins 1st.. flash is important for flock
[14:33] <fta> but strace doesn't show anything in /usr/lib/xulrunner-addons
[14:33] <asac> fta: well
[14:33] <asac> fta: what you really need is a link
[14:34] <asac> from GRE_DIR/plugins => /usr/lib/xulrunner-addons/
[14:34] <asac> since you dont use system xul you cannot really do taht
[14:34] <asac> you can only decide to either use a flock specific dir _or_ the GRE dir; but not both
[14:35] <asac> makes sense?
[14:36] <fta> i can drop that patch then, it's useless
[14:39] <asac> yes
[15:47] <jetsaredim> anyone know of a way to get kde file dialogs to work with ff3?
[17:31] <rzr> back
[17:31] <rzr> let's resume my 2d job :)
[17:53] <rzr> for french speakers : http://blog.racoon97.net/ubuntu-hardy-804-pulseaudio-et-youtube/
[18:17] <fta> bof, j'ai PA dans intrepid et ca marche bien maintenant
[18:26] <valent> hi
[18:27] <valent> ﻿asac: I still haven't seen your reply to fedora mailing list so as per your request I'm reminding you
[18:54] <rzr> fta: j ai pas trop de crash non plus
[19:12] <Volans> Hi all :)
[19:12] <Volans> asac: are you there?
[23:02] <fta> jcastro, asac: flock 2.0 b1 is out, or will be soon (the upstream branch is already tagged). Did you contact the Flock guys already?
[23:13] <jcastro> fta: yeap, I made initial contact
[23:13] <jcastro> fta: do you have a list of concerns or a bug # or something?
[23:14] <jcastro> fta: songbird .6 is now out, so hopefully now they have time to fix our issues. :D
[23:16] <fta> let's hope so :)
[23:17] <fta> jcastro, i've listed my concerns in https://wiki.ubuntu.com/MozillaTeam/Ideas/Intrepid (there's a section for flock).
[23:17] <jcastro> ah rock, I must have missed it when it went  up
[23:17] <jcastro> I'll send it along
[23:19] <fta> maybe we need to rephrase a bit, it's just a raw list of points
[23:19] <jcastro> k, I'm stepping out for a bit, I'll just send it along on monday or something. Or let me know when. :D
[23:19] <Volans> fta: I can ask you how if FF3.1 will be included in hardy or not?
[23:20] <jcastro> fta: while I have you here though
[23:20] <Volans> s/how//
[23:20] <jcastro> fta: do you guys used the "triaged" bug status at all?
[23:21] <fta> Volans, it will not. ff 3.0 final will be in hardy for sure, and subsequent security fixes (such as 3.0.x), but not 3.1.x or higher
[23:21] <Volans> ok, good, then for my extension a 3.0.* compatibility is enough
[23:22] <fta> jcastro, yes, some bugs of our bugs are tagged as triaged.
[23:22] <jcastro> fta: are you guys going to move away from like confirmed and stuff to triaged?
[23:23] <fta> Volans, once we have the bot to update the extension packages, i'm thinking about a dedicated ppa with extensions bumped to 3.1
[23:25] <Volans> good idea! :)
[23:25] <Volans> but for update an extension the "standard" procedure is to create a backport?
[23:25] <fta> jcastro, you may have to ask asac for this bug topic, i'm not good at it. asac worked with bdmurray recently to update/improve our bug workflow
[23:26] <jcastro> ah ok, cool
[23:26] <jcastro> thanks
[23:28] <fta> Volans, i mean, update with a bot in ubuntu+1, so intrepid for now. for hardy, as it needs SRU, maybe it's safer to stay in manual mode
[23:29] <Volans> I mean for hardy, you want to made an SRU for every extension update?
[23:31] <fta> we're not supposed to update hardy, just fix critical/security bugs. upstream versions are supposed to remain fixed. backport is different though. we need to think about this.
[23:34] <Volans> I don't know if the SRU guys will accept an SRU for a simple FF extension update, I think backport is probably the right solution until an automated system will be created
[23:35] <Volans> for example I have updated my estension today and uploaded the new version on mozilla addons site and I would know what I have to do for the deb package now in hardy
[23:38] <fta> you may bring the topic to the next meeting
[23:39] <Volans> ok thanks
[23:39] <Volans> now I have to ho to bed... sorry
[23:39] <Volans> bye bye