/srv/irclogs.ubuntu.com/2008/09/14/#ubuntu-meeting.txt

=== nxvl_ is now known as nxvl
=== nxvl_ is now known as nxvl
=== ubottu changed the topic of #ubuntu-meeting to: Calendar: http://fridge.ubuntu.com/event | Logs: https://wiki.ubuntu.com/MeetingLogs/ | 14 Sep 18:00: Mozilla Team | 16 Sep 11:00: Community Council | 16 Sep 15:00: Server Team | 17 Sep 17:00: QA Team | 17 Sep 22:00: Platform Team | 18 Sep 00:30: ubuntu-pa LoCo Team
=== elkbuntu is now known as elky
=== Rafik_ is now known as Rafik
=== ompaul_ is now known as ompaul
=== gnomefreak is now known as thunderstruck
=== thunderstruck is now known as gnomefreak
=== Rafik_ is now known as Rafik
=== emonkey-t is now known as emonkey
XioNoXhi!14:50
=== asac_ is now known as asac
=== ubottu changed the topic of #ubuntu-meeting to: Current meeting: Mozilla Team Calendar: http://fridge.ubuntu.com/event | Logs: https://wiki.ubuntu.com/MeetingLogs/ | 16 Sep 11:00: Community Council | 16 Sep 15:00: Server Team | 17 Sep 17:00: QA Team | 17 Sep 22:00: Platform Team | 18 Sep 00:30: ubuntu-pa LoCo Team
XioNoXhi!19:00
Jazzvahey XioNoX19:00
XioNoXjust on time ?19:00
Jazzvayep, still didn't officially start19:00
VolansHi all19:01
asachi!19:01
Jazzvahey, hey19:01
asaci think gnomefreak and fta wont make it.19:01
asacok. agenda is https://wiki.ubuntu.com/MozillaTeam/Meetings19:02
asaci pushed "firefox 2 archive removal" to top ;)19:03
asacbecause mdke is blocked on it19:03
asacmdke wants to cleanup ubuntu-docs and remove all those complicated alternatives19:03
* mdke nods19:04
asacwhich where introduced initially to all localized homepages19:04
asacs/where/were/19:04
mdkeI'm right that firefox doesn't use those alternatives anymore right?19:04
asacmdke: yes. firefox without ubufox has the official mozilla homepage19:04
Volansasac: actually in FF3 how the localized Start Pages are managed?19:04
asacubufox uses his own mechanism to detect the language19:04
mdkeand whether the user is online/offline19:05
asacVolans: ubufox uses the preferred language and finds the right page automatically19:05
asacnote: this is only an issue for the "offline" page. the online page uses the same "preferred language" on the webserver side19:05
Volansyes, I know19:06
Volansso ubufox have the translated page itself or open the one provided by the ubuntu-doc package?19:06
asacVolans: does this clarify a bit how it works?19:06
mdkeVolans: the latter19:07
asacVolans: right. the code is http://bazaar.launchpad.net/~asac/ubufox/main/annotate/110?file_id=startpage.html-20080411000353-l3fxb4oqnnv18uwx-119:07
Volansok, thanks19:07
mdkeok, back to the agenda item - what are the issues over removing firefox-2?19:07
asac7-3619:07
asaci think the only issue i can see would be that some extensions are not available19:07
asacthats true for addons.mozilla.org, but what is more important here is that - afaik - we also have some extension packages19:08
asacwhich then would need to be removed19:08
asacJazzva: do you know how many are left?19:08
JazzvaI think there might be few of them... 2-319:08
Jazzvaasac, I'll check them after the meeting19:09
asachttp://paste.ubuntu.com/46938/19:09
asacthats the list of rdepends19:09
asacok.19:09
asacso would be be ok in case there is really an extension that still doesnt have 3.0 support?19:09
Jazzvahuh?19:10
asaccan we decide whether we will remove firefox-2 without looking at the extension list?19:11
Jazzvathose that don't have ff-3.0 support would be removed. there are only 2 or 3 which don't support ff-3.0, iirc19:11
asacor should we postpone decision based on what extension packages we find are not upgradable19:11
asacJazzva: right. maybe those even have new upstream version19:11
Jazzvayep... I'll go through the list to see...19:11
Volansasac: but removing FF2 means that a user cannot still install it via apt?19:11
asacVolans: yes.19:12
asacVolans: but its outdated and we wont be able to provide security support19:12
Volansof course19:12
asacok. so firefox-2 will most likely be removed?19:13
Volansin this case I think that the extension compatibility checks is not fundamental, is an "obsolete" version of a program19:13
asaccan we say that or does anyone object?19:13
Jazzvafine with me...19:13
fta2i agree (drop ff2)19:13
asacgood.19:13
mdkeyay19:13
asac[ACTION] remove ffox 2 from archive as well as extensions that cannot be upgraded19:13
mdkeperhaps someone could poke me when that is done19:14
mdkeor nudge, whatever is preferred19:14
asacmdke: do you have any deadline?19:14
mdkeasac: nope, although I wouldn't want to do anything too close to release, in case I break a path or something19:14
asacmdke: in worst case i would suggest that you remove the alternatives. if people complain you can point them that mozillateam will remove that package anyway19:15
asacmdke: so imo you can just go ahead. or do you see any problems with that?19:15
mdkeah ok. If there will be no possible further upload of mozilla-firefox-locale-all, then I can remove the alternatives now19:15
asacmdke: have you asked Riddell about konqueror?19:15
asacmdke: right. those will be removed for sure19:15
mdkeasac: I tried konqueror, it does it's own thing. And I posted to -devel, but I might ask him too to be sure19:15
asacmdke: right.19:16
asacok moving on?19:16
asac[TOPIC] abrowser rdepends transition19:16
asacabrowser has its own metapackage which basically means that packages that currently depend on firefox cannot be installed with abrowser19:17
asacso what we need to do is to look at all rdepends of "firefox" package. and add a | abrowser there19:17
asacfirefox-3.0 rdepends should be fine though and dont need any action19:17
asacfta: you think you have time to help here? e.g. uploading a batch of universe packages? should take like 2 minutes for each package - though there is always the risk that an upload might suddenly not build anymore ... but we would like to know about them anyway19:18
ftaagreed19:18
ftaasac, it's simpler than the other project so yes, i should able to help here19:19
fta+be19:19
asacfta: i think we could just go through the list and if we work together it should take 1h or so19:20
Volansasac: I can help with some extensions if you want (like mine and others of needed)19:20
asacfta: so when you think you have 1h time just ping me and we can upload everything19:20
ftaasac, oh, you want to do that manually ?19:20
asacfta: well. i think it just takes 1h or even less19:20
ftaok19:21
asacnot sure if we want to develop something19:21
asacVolans: thats good. extensions need be updated too19:21
asacmost likely we could go through all branches and add firefox everywhere19:21
asacerr abrowser ;)19:22
ftaasac, I'll sure ping you when i have some time19:22
asac[ACTION] asac and fta to add abrowser to all firefox rdepends and upload; everyone to help updating extension branches19:22
asac[TOPIC] Mozilla Freeze Exceptions19:23
asacis there anything we want to get in that needs a freeze exception?19:23
Volansall those rebuilding in order to add abrowser need some exception?19:24
asacVolans: no.19:24
ftawe discussed ff3.1 already, is it still a no-go ?19:24
asacVolans: those are bugs ... not a feature so can be fixed all the time19:24
Volansright19:24
asacfta: not sure. my idea is to say that in case 3.1 beta is released before intrepid we should upload it19:25
ftamozclient: i want to extend it a little bit so we can put project files inside packages instead of m-d19:25
asacbut i am open to other ideas ;)19:25
Jazzvaasac, will we upload extensions that have updates, if the version we currently have only support ff2?19:25
ftait should help downstream19:25
asacJazzva: yes. we can surely provide exceptions for those19:25
asacfta: thats ok. cant that even be sold as a bug?19:26
Jazzvacool :)19:26
ftaasac, if someone files one, sure :)19:26
asacfta: most likely the currently supported packages will still be maintained in moclient?19:26
asacfta: ok. we can get kgoetz to file one i think19:26
asacfta: but in the end i dont really mind if we have a bug or not19:27
Jazzvaasac, fta: I read something about wmmode being fixed in some newer ff release. did we upload that?19:27
asacfta: its just that if we release it as 0.10.1 its a bug fix release ;)19:27
asacJazzva: whatis wmmode?19:27
asactransparent (for plugins)?19:27
ftaasac, possible, i'll find a way to accommodate both (ie, files inside packages preferred over the ones in m-d)19:27
asacfta: right. for me that sounds like a bug and definitly doesnt need an exception ... we should just try to keep the diff minimal - if possible at all19:28
asacbut i think the change shouldnt be intrusive19:28
Jazzvaasac, I think it's a windowless mode for flash (and maybe other plugins). Firefox had a bug with it, which caused a lot of crashing before, but now it should be fixed19:28
ftaJazzva, it's fixed in 3.0.2 iirc19:28
Jazzvaok, just wanted to check if we uploaded that fix...19:29
asacJazzva: are you using mozillateam firefox build?19:29
ftaso it should be in since yesterday19:29
Jazzvaasac, yes19:29
asacthat should be 3.0.219:29
asacfta: huh?19:29
asacfta: did they commit to 3.0.2 ?19:29
XioNoXThe last build in ppa for hardy, don't work well with flash19:29
ftadidn't they ? i didn't check19:29
asaci presumed that they were doing quality assurance ;)19:30
ftaok, so it's still not in (oops)19:30
asacfta: not sure. in case it landed in 3.0.3 we should try to cherry pick it19:30
asacfor sure19:30
Jazzvaasac, fta: http://blogs.adobe.com/penguin.swf/ 3rd blog post, that's where I read about it...19:30
XioNoXnpviewer.bin keep crashing19:30
asacas 3.0.3 might be after intrepid and everyting that can mak eplugin crashes less likely is high-prio for us i think19:30
asacXioNoX: on amd64?19:30
asacXioNoX: that is libflashssupport which is still in ia32-libs ... -> that needs to be removed19:31
Jazzvaasac, fta: Also here... http://blogs.adobe.com/penguin.swf/2008/07/addessing_wmode_crashes.html19:31
asac[ACTION] file a bug about removing libflashssupport from ia32-libs19:31
ftaasac, no, it has been committed upstream before 3.0.2, so 3.0.2 should be fine, in fact, people already reported that the 3.0.2~cvs version in my ppa was ok19:31
asac^^ anyone wnats to do that?19:31
asacfta: ok good.19:31
asacfta: maybe thats why i dont see it here ;)19:31
asacXioNoX: can you try to manually remove libflashsupport.so and see if the crashes become less regularly?19:32
Jazzvaasac, I can file a bug... that shouldn't be too much time-consuming... (exams)19:32
asac;)19:32
asacJazzva: thanks.19:32
Jazzvanp19:32
asacok ... i think we still can grant exceptions on demand.19:33
asacfta: 3.1 in intrepid. you think we could keep it updated for 6 month? (e.g. stable support)19:33
asacmost likely people running that will upgrade to intrepid+1 anyway ... so saying that we provide updates for 6 month should be a good compromise19:33
asacfta: alpha 2 was just released right?19:34
ftathe way i work now is to ppa build everything for intrepid and hardy so if someone agrees to test it, i can continue to build it for intrepid when it is released19:35
asacfta: ok cool. i can also help in time you really dont have time19:35
Volansasac: Alpha 2  19 August | Beta 1  Feature freeze. source: https://wiki.mozilla.org/Firefox3.1/Schedule19:35
asacso with that i would like to see 3.1 in intrepid ;)19:35
asacfta: we should just take care that we get the branding right (e.g. use the branding upstream uses)19:36
asacand dont suggest that its 3.1 final in the menu19:36
Volansdamn... that page was not updated after august 24, sorry19:36
asacVolans: i think alpha2 was released last week or something19:37
asacbut i might be completely worng19:37
Volansin the nightly builds I see 3.1b1pre19:37
ftaI still use "Minefield 3.1 Web browser" for the desktop file, but i wanted to jump to "Firefox 3.1" once b1 is out like we did for 3.019:38
asachmm http://www.mozilla.org/projects/firefox/3.1a2/releasenotes/19:38
asacfta: right. but alpha2 should be Shiretoko 3.1 Web browser i think19:39
ftain fact, i remember upstream did that, ie start calling 3.0 firefox instead of granparadiso starting to b119:39
asacyep.19:39
asaci think we should use whatever they use. and thats shiretoko i guess for alpha219:39
ftasure, fixed releases are call Shiretoko 3.1, hg snapshots are called Minefield19:39
ftacalled19:39
asacah19:39
asacok19:39
asacfta: but snapshots are always called minefields ... arent they?19:40
ftatoday yes, it's just a flag19:40
asacits just that b1 b2 and such are called "firefox" ;)19:40
asacok cool19:40
asacfta: ok. then maybe upload the build that is supposed to go to intrepid and let me test. then we can just upload and hope that archive admin will except that we (the mozillateam) granted an exception for that ;)19:41
asac[ACTION] fta and asac try to get 3.1 alpha2 into the archive19:41
asac[ACTION] team report19:42
asacwe had one for the extension team done by Jazzva :) ... great!19:42
ftaalpha2, ok. should be easy. i guess we want it with abrowser-3.1 right, not as it was a few weeks ago in my branch ?19:43
asaci would really like to write a complete team report. and do that regularly.19:43
Jazzvaasac, I should prepare one for august...19:43
asacusually i face the problem that i dont know what was done19:43
ftawe may have SEAMONKEY_1_1_12_RELEASE late19:44
asacand wonder if we could have a wiki page or even a bot in irc channel where we can add all small actions19:44
asacwe did19:44
asacso we can better do a report at the end of the month19:44
ftamay as i'm not sure it's out yet or still in QA upstream19:44
Jazzvaasac, IRC bot would be cool... it's easier to say "action: something", than editing a wiki page :)19:45
asacfta: true. but it doesnt require an exception because its also a security release19:45
asacJazzva: yeah "done: i did this" ;)19:45
asacanyone knows a good bot?19:45
asacor just an irssi perl script maybe?19:45
ftagrep :)19:46
Seveasa small perlscript hooked to editmoin? :)19:46
Jazzvait would be great if it could be done automatically, but i don't have an idea how to do that (collect all the information, if all the information is available)19:46
asacSeveas: how would that work?19:46
Seveasasac, not knowing irssi very well, I'd guess something like: script parses all lines, if it matches [action] oslt, it would add it to a wikipage via the editmoin tool19:47
asacJazzva: well. i think what a list of a) uploads, b) commits and c) DONE: together should give a good picture for the one drafting the team report19:48
asaci think that it will need some manual editing and polishing anyway. its just that all the data would be in the right place19:48
asacSeveas: ah ok.19:48
asacso can we say that if you have done something (even its just a tiny task) just writing a short [DONE] ... line to the mozillateam channel would be ok?19:49
Seveasasac, a post-commit hook using editmoin, and a simple cronjob using launchpadlib that extracts commits/uploads will complete that report ;)19:49
asacSeveas: post-commit hook. how is that done in bzr?19:49
Jazzvaasac, also not to over-use done tag. we don't want very log month reports, right? :)19:49
asacJazzva: true.19:50
Jazzvas/log/long/19:50
Seveasasac, #bzr knows, I don't :)19:50
asacJazzva: i think DONE for commits and uploads shouldnt be done19:50
asaconly for things that cant be tracked otherwise19:50
asac(e.g. like reworking wiki, etc.)19:50
Jazzvamhm19:50
asaccommits and uploads should be gathered automatically ... so a done wouldnt really be needed19:51
asacok ... ill note19:51
asac[ACTION] asac to write down how to get items into the monthly reports and send that to mailing list/wiki19:53
asaci think i have enough ideas now how to do that ;)19:53
asacif anyone else wants to draft this, feel free to high-jack that item from me ;)19:53
asacok ... i think we should skip the intrepid status for now19:53
asacor is there anything more general about our state for intrepid that hasnt been covered above?19:54
asac[TOPIC] check status of automatic update for extensions19:54
ftai guess there's no need to discuss about chrome, there's nothing usable for us so far19:55
asacJazzva asked what the status auf the auto updates of extension branches is19:55
asacfta: right. i think its not relevant for intrepid19:55
asacfta: we should use PPAs until we get something usable19:55
ftaok19:56
XioNoXback19:56
Jazzvayes... iirc, fta's check-extensions script is pretty much usable, we have written a process how to do that, so now we only need to get it working, right?19:56
asacbut we should bug jcastro about the chromium "master" project19:56
XioNoXconnexion problems :(19:56
asacXioNoX: welcome back ;)19:56
asacXioNoX: topic is [TOPIC] check status of automatic update for extensions19:56
XioNoXok, thx, I'll read the log later19:57
asacJazzva: i think we are pretty much stuck right now19:57
Jazzvaasac, stuck with?19:57
asacJazzva: stuck aka "we only have check-extensions"19:57
asacand we have no plan what steps are next ;)19:58
asacbut i would like to change that19:58
ftamostly my fault. I'm sorry, lack of time :(19:58
Jazzvahmm, I think we have a plan :). download newer extensions, unpack, push to branch, notify maintainer :)19:58
asacfta: thats ok. i think the idea was to write something quite powerful19:58
ftayes19:58
asacmaybe we can find a less work intensive solution19:58
asacwhat would be needed to get something useful?19:58
asacJazzva: right. but there are a few undefined variables in that game19:59
asac1. where do we configure branches that are auto-updated?19:59
Jazzvabranch names and how extension is packaged...19:59
asacactually 1. where and how do we configure branches that are auto-updated?19:59
asac2. what upstreams do we support? xpi-med-(un)pack only?20:00
asac3. how do we notify maintainer about a pending merge (i think that would be the launchpad merge feature, but we need to find out how to do that from a script)20:01
asacok. so we have check-extensions20:02
asacnow we need a download script i gues20:02
asace.g. download xpi for extension A with version B20:02
asacfta: we get the latest available version for extensions through check-extension right?20:03
Jazzvayep... afaics, it should determine if it's packaged from xpi, or branched from cvs20:03
ftaasac, yes, those in amo20:03
asacok ... that means once we have the download script, we just need a high level script that goes through all xpi branches then downloads the latest xpi and uses med-xpi-unpack20:04
asacand then would have a script we could run to auto update?20:04
asacoh ... we also need a script to ask for merge20:04
asacfta: have you looked at launchpad 2.0 rpc api?20:05
* asac wonders if they have a "merge request" operation20:05
ftanot deeply enough yet, i just read blog entries about it.20:05
asacok.20:05
ftaseems a WIP to me20:06
asac[ACTION] write a script "download-xpi-from-amo <extension-name> <version>"20:06
asac[ACTION] write a script "request merge <branch1> <branch2>"20:07
Volanssorry, I have to go now, but I'm interested in the automatic update of extension task, I will read the log and I would like to help doing something20:07
ftathe 2nd a feature already in LP20:07
fta+is20:08
asac[ACTION] write a high level script that assembles check-extension, download-xpi-from-amo and request-merge to automatically update upstream branches for extension branches that use the med-xpi orig structure20:08
Jazzvawe also have https://wiki.ubuntu.com/MozillaTeam/Extensions/LargeScaleMaintenance , we could use those ideas20:08
asacfta: right. but we still need to programmatically trigger that feature i think20:08
Jazzva(branch naming and stuff)20:08
ftaok20:08
ftashould be trivial20:08
asacJazzva: yes. thats the document we should keep in mind when doing this20:09
asacbut imo we should rather try to do something incomplete than do nothing, because its too much work to do at one time20:09
Jazzvai agree20:09
asacanything else on this topic?20:10
Jazzvai think we're done with it20:10
asacgreat.20:10
asac[TOPIC] anything else ;)20:11
asacmaybe one more announce: fta is MOTU now ;)20:11
fta:)20:11
Jazzvayay, fta :D20:11
ftai have yet to upload something ;)20:12
asacfta: yeah ;) ... lets do the abrowser transition ;)20:12
ftasure20:12
asacoh. i have one more thing. i think we should look over all extensions and see if they a) have been updated in this cycle at all or b) if they can be updated.20:13
asacbut i think that check-extension probably isnt enough?20:13
asacfta: does check-extnesions already check against intrepid?20:13
Jazzvaasac, i can help with that too... i'll be totally free from 20-24 september20:14
ftait does your current dist20:14
ftaJazzva, lucky guy ;)20:15
asacJazzva: great. is the list on the wiki page more or less complete?20:15
asacor are there still extensions in the archive that we dont track there?20:15
Jazzvaasac, more or less... I think there might be few more that aren't maintained in bzr, and not tracked on the wiki20:16
asacok20:16
asacdo we explicitly add them to that list (and hence making them MT maintained) or is that ok to leave them in the limbo until we hear from them (e.g. because people point to bugs et al)20:17
ftamost come from debian20:18
asaci think having a complete list would be nice. but its not really high prio from what i can tell. especially because most of those not listed on that page come from debian20:18
Jazzvawell, I think we are still diverged from debian regarding extensions...20:19
JazzvaSo, I think most of them are listed there... we don't get that much extensions...20:19
Jazzvaasac, which reminds me... are we gonna get mozilla-devscripts to debian?20:19
asacgood point. someone should file a RFP ;) ... then we can upload it with that bug number in changelog20:20
Jazzvagreat :)20:20
asac[ACTION] file RFP for mozilla-devscripts and get it into debian archive20:20
ftaremember it's a native package20:20
asacfta: is that a problem?20:21
asacor do you mean that RFP is the wrong wording ;)?20:21
ftaif we need to tweak it for debian, then native is probably not good20:22
asac[ACTION] asac to find out if initial uploads to debian strictly require a wnpp bug20:22
asacfta: hmm. we can have a branch ... which usually should be the same i think20:22
asacfta: we could handle debian as downstream20:22
asace.g. merge down20:22
ftalol20:22
asacfta: ok. could you bake an initial release of latest mozilla-devscripts with a debian1 version?20:23
asace.g. 0.10debian120:23
asachmm20:23
ftawe have to blacklist it20:24
asacfta: actually i think we need to use ubuntu1 ... otherwise it will get auto-synched ;)20:24
asac[ACTION] blacklist mozilla-devscripts for auto-syncher/MoM20:24
fta0.10~debian1 ?20:25
asac[ACTION] create debian branch with initial mozilla-devscript debian1 version20:25
asacfta: i think we should use 0.10debian120:25
ftaso debian is always behind ?20:25
asacit would be similar to what we do with debian packages20:25
asacwhen ubuntu is downstream20:25
fta       apt | 0.7.14ubuntu6 | http://archive.ubuntu.com intrepid/main Sources20:25
asacso imo the same logic should apply if debian is downstream20:25
asacfta: but i dont mind. actually we could also maintain it in debian and synch it from there to ubuntu20:26
asacfta: you can decide what you prefer20:26
ftabut with 0.10debian1, debian will be ahead of us, then the merge/sync bot needs to blacklist it20:26
asacfta: right. thats what i mean. either we should use ubuntu1 i ubuntu or we should blacklist it20:27
asacfta: maybe ~debian1 is also an option to consider20:27
asacbut i think we should either blacklist or maintain in debian20:27
ftai prefer the blacklist option, as i'm only on the debian side ;)20:28
fta-debian+ubuntu20:28
asacok20:28
asacfta: we can add you as maintiner for the package in debian ... so you can directly upload there20:28
asacbut lets start in the way you suggested20:29
asacok, so the two actions above correctly reflect what we just discussed here right?20:29
ftayes20:29
asac21:20 < asac> [ACTION] file RFP for mozilla-devscripts and get it into debian archive20:29
asac< asac> [ACTION] asac to find out if initial uploads to debian strictly require a wnpp bug20:30
asac< asac> [ACTION] blacklist mozilla-devscripts for auto-syncher/MoM20:30
asac < asac> [ACTION] create debian branch with initial mozilla-devscript debian1 version20:30
ftaok20:30
=== ubottu changed the topic of #ubuntu-meeting to: Calendar: http://fridge.ubuntu.com/event | Logs: https://wiki.ubuntu.com/MeetingLogs/ | 16 Sep 11:00: Community Council | 16 Sep 15:00: Server Team | 17 Sep 17:00: QA Team | 17 Sep 22:00: Platform Team | 18 Sep 00:30: ubuntu-pa LoCo Team | 18 Sep 12:00: Ubuntu Mobile Team
asacthose are the four actions related to mozilla-devscripts ;)20:30
asacok ... anything else?20:30
asacotherwise i guess ubottu just told me that the meeting is over ;)20:30
ftafine with me, nothing more to add20:31
asacJazzva: XioNoX: Volans ?20:31
Jazzvasame here...20:31
asacok. thanks! anyone wants to write minutes or is that supposed to be me this time? ;)20:32
JazzvaI can do it tomorrow, I think...20:32
XioNoXasac, nothing to add, exept if you have an idea of what i can do20:33
Jazzvasee you in #ubuntu-mozillateam20:33
asacXioNoX: we have plenty of actions in this meeting20:33
asacwe could look if anything suites you20:33
asacbut lets talk about that in -mozillateam20:33
asacthanks all. nice meeting20:34
XioNoXok good20:34
ftabye20:37
=== Mamarok_ is now known as Mymarok
=== Mymarok is now known as Mamarok
=== Rafik_ is now known as Rafik

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!