14:02 <@jono> jordi, woo!
14:02 < sabdfl> hey jordi!
14:03 < jordi> hmm, seems I can't change the topic
14:03 < jordi> too bad
14:03 < tonyyarusso> jordi: Tell me what you'd like in /msg and it's yours.
14:03 < jordi> The session is Translations with Rosetta :)
14:04 < givre> sabdfl: i think that make an advance option in the installer to disable restricted repo https://lists.ubuntu.com/archives/ubuntu-devel/2006-November/022596.html , just like suggested collin watson should make everybody happy. Just my 2 cents
14:04 < dneary> jordi: I'm here for you :)
14:04 < jordi> Ok, so for those who don't know me, I'm Jordi Mallach, and I've been involved with the Rosetta team trying to be the link between the development team and the Ubuntu translators and rosetta users
14:05 <@tonyyarusso> hmm
14:05 < jordi> tonyyarusso: just "Rosetta" then :)
14:05 < stalefries_away> or perhaps cut down on the info
14:06 < jordi> let's get moving
14:06 < jordi> The Rosetta Translation Portal
14:06 < jordi> Rosetta is one of the components that make up “Launchpad”,
14:06 < jordi> Canonical's service platform.
14:06 < jordi> Launchpad is made up of five major components: a bug tracker, a
14:06 < jordi> request tracker, a specification tracker, a "source code"
14:06 < jordi> supermirror and Rosetta, a web-based translation portal.
14:06 < jordi> Christian Reis will talk tomorrow about Launchpad in general, so
14:06 < jordi> let's focus on Rosetta.
14:06 < jordi> Rosetta's aim is to make translation of Free Software as easy and
14:06 < jordi> non-technical as it can get. The Rosetta team has been working on
14:06 < jordi> creating an interface which hides the specifics of the Gettext PO
14:06 < jordi> file format, which is the standard for translating Free Software,
14:06 < jordi> thus lowering the barrier so anyone with a reasonable knowledge
14:06 < jordi> of English can help out with the translations of their favourite
14:06 < jordi> project into their mother tongue.
14:07 < jordi> (please say if I'm too fast, I'm worried about lack of time)
14:07 < jordi> Rosetta is the main translation system of Ubuntu Linux, and is
14:07 < jordi> the source of all translations which appear in the Ubuntu
14:07 < jordi> releases, and in the frequently updated “langpacks”. Rosetta is
14:07 < jordi> also designed to help program authors getting their applications
14:07 < jordi> translated.
14:07 < jordi> A close look on the Gettext PO file format
14:07 < jordi> ==========================================
14:07 < jordi> Most of the software in your desktops use a standard translation
14:07 < jordi> interface called GNU gettext, which is in charge of showing the
14:07 < jordi> applications in the language the user has chosen. Application
14:07 < jordi> programmers need to take care of marking all the user-visible
14:07 < jordi> messages (or strings, as the initiated tend to call them) with a
14:07 < jordi> special marker which can be extracted to plain text ".po" files.
14:07 < jordi> We translators use these files to translate the applications.
14:08 < jordi> Let's look at how a PO file looks. I've put some examples in
14:08 < jordi> http://pusa.informat.uv.es/~jordi/ubuntu-school/
14:08 < jordi> Have a look at the ubuntu-school.pot file. A POT file is a "PO
14:08 < jordi> Template", that is, an empty PO file ready to be translated.
14:08 < jordi> Looking at the contents of the file, you can see the format is
14:08 < jordi> pretty straight forward: each original string in English (a
14:08 < jordi> msgid) has its corresponding translation (msgstr). While simple,
14:08 < jordi> the po format is quite fragile. One missing quote, and your
14:08 < jordi> entire application build will fail with a syntax error. There are
14:08 < jordi> several very popular PO file editors which help the editing
14:08 < jordi> process: KBabel, PoEdit, GTranslator, Emacs PO-mode...
14:09 < jordi> Rosetta goes one step further in easing the translation of these
14:09 < jordi> PO files, using a clean, web-based interface which hides the
14:09 < jordi> format, presenting only sets of string/translation pairs that you
14:09 < jordi> can fill up. Once the work is done, it's stored in its database
14:09 < jordi> where the information can be exported or shared among other
14:09 < jordi> projects.
14:09 < jordi> Using Rosetta's Web Interface
14:10 < jordi> Rosetta is, as hinted before, divided in two main branches: one
14:10 < jordi> serves to translate the applications of the people who request
14:10 < jordi> it. For example, the Gobby collaborative editor is being
14:10 < jordi> translated by Rosetta contributors, after its authors requested
14:10 < jordi> us to set it up for them in Rosetta. On the other hand, Rosetta
14:10 < jordi> is the platform from where Ubuntu gets all its translations.
14:10 < jordi> We'll focus on Ubuntu a bit more now.
14:10 < jordi> Ubuntu translations revolve around the Ubuntu translation teams,
14:10 < jordi> which coordinate and produce the translations which get shipped
14:10 < jordi> with every new version.
14:10 < jordi>    https://launchpad.net/rosetta/groups/ubuntu-translators
14:11 < jordi> Here you'll see a list of teams which belong to the Ubuntu
14:11 < jordi> translation teams. While Rosetta is open enough to let everyone
14:11 < jordi> with a Launchpad account contribute, there is need for some
14:11 < jordi> access control, to protect quality, avoid vandalism, etc. Being
14:11 < jordi> part of one of the translation teams grants you "write" access to
14:11 < jordi> every translation for that language in Ubuntu. Still, if you're
14:11 < jordi> not a member of your language's team, you can still go ahead and
14:11 < jordi> translate. Your contributions will be also stored in Rosetta's
14:11 < jordi> database as "suggestions", but won't appear in Ubuntu's language
14:11 < jordi> packs until a member of the team reviews and validates them.
14:11 < jordi> Rosetta offers a long list of applications that can be
14:11 < jordi> translated. Taking the French team as an example,
14:11 < jordi>  
14:11 < jordi>    https://launchpad.net/distros/ubuntu/edgy/+lang/fr
14:12 < jordi> we can have a look at how their translation status is for the
14:12 < jordi> Ubuntu Edgy release. I like showing the French team because they
14:12 < jordi> are really an amazing example of completeness.
14:14 < jordi> woops
14:14 < jordi> this had to happen today, I new it
14:14 < jordi> my router just rebooted :O)
14:14 < ivoks> hehe
14:14 <@jono> :P
14:14 < jordi> Rosetta presents us a list of applications which are ready to be
14:14 < jordi> translated to French, and their current translation status. As
14:14 < jordi> you see, the French have done their homework and there's barely
14:14 < jordi> no red bars, meaning "untranslated". See the bottom of the
14:14 < jordi> page for the meaning of the bar colours.
14:15 < jordi> The list is ordered from most important to less important
14:16 < jordi> Let's see how we'd translate an application. Close to the top of
14:16 < jordi> the list is "launchpad-integration". We'll pick this one as it's
14:16 < jordi> easy and short.
14:16 < jordi>    https://translations.launchpad.net/distros/ubuntu/edgy/+source/launchpad-integration/+pots/launchpad-integration/fr/+translate
14:17 < jordi> okay, I just started to look at the questions in the chat channel
14:17 < jordi> I'll try to paste them here now, sorry about that ;)
14:17 < waod> LOL
14:17 < jordi> If instead of French you want to have a look at your own
14:17 < waod> 14:38 < mogaal> Soy bruto
14:17 < jordi> language's translation, simply replace "/fr" in the URL with the
14:17 < jordi> corresponding ISO 639 code. You can find the code for your
14:17 < jordi> language here:
14:17 < jordi> http://www.loc.gov/standards/iso639-2/php/code_list.php
14:17 < waod> 14:38 < mogaal> Comprende :(
14:18 < jordi> In our case, the first string is "The Launchpad helper
14:18 < jordi> application failed", which is already translated to French as
14:18 < jordi> "L'assistant Launchpad a échoué". Below the accepted translation
14:18 < jordi> there is a list of alternative translations suggested by other
14:18 < jordi> people. You can quickly navigate through the translation fields
14:18 < jordi> using the tab key. Once you have completed all the strings in a
14:18 < jordi> page, you want to save your work: hit "Save & Continue" at the
14:18 < jordi> bottom, and if there are more strings to do, Rosetta will then
14:18 < jordi> show them to you.
14:19 < jordi> There are other bits that can help the translators while they
14:19 < jordi> work on a translation: you might want to see what the translators
14:19 < jordi> to a language similar to yours used in a string that is hard to
14:19 < jordi> translate, for inspiration. You can get such information using
14:19 < jordi> the "Make suggestions from" widget at the top of the string list.
14:19 < jordi> Also, you'll be more interested in seeing the strings that need
14:19 < jordi> work instead of those which are translated already. You can
14:19 < jordi> filter the kind of messages you want to see using the "Show"
14:19 < jordi> widget, where you can select from "all", "unstranslated",
14:19 < jordi> "translated" and "needs review".
14:20 < jordi> 20:20 < neophile> QUESTION: Is it possible to search for a string in the translation? That's major drawback when trying to correct translations. Is a search feature planned for rosseta in the near future?
14:20 < jordi> It's currently not possible to search for a string easily
14:20 < jordi> it is one of the most requested (and no doubtely most useful) features, and we do plan to add it
14:21 < jordi> the implementation isn't trivial though, as the database is huge and there are some perdformance issues to solve
14:21 < jordi> But yes, the team will focus on providing it as soon as possible
14:22 < jordi> Using Rosetta's import/export interface
14:22 < jordi> While the web interface has allowed many Ubuntu users help out
14:22 < jordi> with the translations to their language, there's certainly
14:22 < jordi> die-hard, old-time translators who will prefer using their own
14:22 < jordi> tools (obscure emacs modules and weird command line tools!) to
14:22 < jordi> work on their translations. Or there might be people who cannot
14:22 < jordi> afford to be online during the whole translating session.
14:23 < jordi> To help them, Rosetta has an import/export mechanism, which
14:23 < jordi> allows you to easily upload translations you have worked on
14:23 < jordi> offline, using your own ways, but you still want to see
14:23 < jordi> integrated in Rosetta, and download your finalised files so you
14:23 < jordi> can do whatever you want with them: back them up, send them to
14:23 < jordi> your team's mailing list, send them to the upstream author so
14:23 < jordi> they get included in the next release...
14:24 < jordi> Importing and exporting is easy: to download your work, use the "Download" and "Upload file" links in the boxes at the left side
14:24 < jordi> When requesting a download, Launchpad will prepare the file for you and will email you the location of the desired export.
14:25 < jordi> Importing is similar. Just fill in the field with the location path to your file, and rosetta will integrate it in the database
14:26 < jordi> I translated all night long. What now?
14:26 < jordi> ======================================
14:26 < jordi> Okay, so you've worked on the files you were interested in, and
14:26 < jordi> Rosetta now has all the info. What happens now?
14:26 < jordi> Ubuntu will, on a monthly basis, extract all the translations
14:26 < jordi> from the database and put them in the "language packs" for each
14:26 < jordi> supported language in the distro, which will automatically hit
14:26 < jordi> your Ubuntu mirror the 1st Monday of the month. This way, Rosetta
14:26 < jordi> allows people to keep improving the support for their language
14:26 < jordi> even after a Ubuntu release has shipped. For example, more than 6
14:26 < jordi> months after the release of Ubuntu 6.06 LTS, there's a group
14:26 < jordi> working on adding Dzonghka support to Ubuntu, when there was
14:26 < jordi> close to nothing included in dapper initially.
14:27 < jordi> I see there's many interesting questions going on, so I propose we go on with Q+A, trying to focus on the classics: Rosetta and upstream relationship, etc.
14:28 < jordi> 20:24 < bugman> QUESTION: In https://translations.launchpad.net/people/bugman/+translations for example, is possible to implements the view of all string translated for a package and not only the last?
14:28 < jordi> bugman: it's possible, yes. These are wishlist features, though, and will get a lower priority than say "search a string"
14:28 < jordi> but the info is in the database, so it's prefectly possible to show the info
14:29 < jordi> it's important that bugs are filed against rosetta requesting these things
14:29 < bugman> jordi: ok :-)
14:29 < jordi> 20:26 < dneary> QUESTION: What's the recommended workflow for updating .po files outside Launchpad for the moment?
14:29 < jordi> dneary: can you be more specific?
14:30 < jordi> there's several scenarios: gnome-panel or launchpad-integration, for example
14:30 < ivoks> jordi: he asks if he could see all his translations in one package
14:30 < ivoks> just his own
14:30 < ivoks> or someone elses
14:30 < jordi> ivoks: bugman?
14:31 < ivoks> yes
14:31 < jordi> oh, I see.
14:31 < dneary>  jordi: It's related to bug #68014
14:31 < jordi> Well, tha can be done too
14:31 < ivoks> urgh.. sorry lag :)
14:31 < bugman> :)
14:31 < jordi> (please give me full malone urls so I can open fast)
14:31 < dneary> jordi: It seems like uploading .po files doesn't automatically update translations at the moment (if I understand the problem)
14:32 < Gwaihir> jordi: https://launchpad.net/bugs/68014
14:32 < jordi> dneary: right, the import mechanism is restricted right now, while a nasty bug involving reverted translñations is tracked down
14:32 < dneary> Some translations were lost, so on the 1st of November, the upload form was disabled
14:32 < jordi> for the time being, mailing rosetta@launchpad.net with import requests is the recommended way
14:32 < dneary> So - what's the reccommended workflow for people working on .po files outside teh tree while that bug is being fixed?
14:33 < dneary> jordi: OK - thanks :)
14:33 < jordi> although I hope we'll go back to normal operation rsn -- aiui the bug fixing is making progress
14:33 < dneary> I was typing rather than reading
14:33 < dneary> cool
14:33 < jordi> 20:27 < dand> QUESTION: any packages in Rosetta that sync automatically with upstream? if yes, are they marked somehow in Launchpad and how often do they sync?
14:33 < jordi> good one: this doesn't happen right now, but is a desired feature
14:34 < jordi> this would allow minimise the "conflicts" between rosetta and upstream preojects (KDE, GNOME...) translations
14:35 < jordi> so if some translator has rights to translate both on Ubuntu and GNOME CVS, a translation inserted in Rosetta could be exported to GNOME
14:35 < jordi> we want this, but it'll won't be here before some time
14:35 < dand> alright, thanks :)
14:35 < jordi> 20:27 < Gwaihir> QUESTION: is it possible to have a --use-fuzzy implementation for exporting mo files?
14:36 < jordi> Gwaihir: as far as I know, we don't do this now because Rosetta generates fuzzies using its own knowledge. I guess it'd be easy to add an option to generate files with fuzzies, yes. Is there a bug filed?
14:37 < jordi> 20:29 < Gwaihir> QUESTION: is there any difference between "fuzzy string" in po and "Need review" in Rosetta?
14:37 < jordi> I've gone over this as I wanted to keep the text dump simple
14:37 < jordi> but yeah, needs review can map to fuzzy
14:37 < jordi> some teams do use it as in the strict "needs review" sense though
14:38 < jordi> ie, theey translate it, but if they are not sure, they use the mark so others can easily find the unsure strungs
14:38 < jordi> strings even
14:38 < ivoks> right, that's common practice
14:38 < jordi> 20:29 < somerville32> QUESTION: How does a member of a translation team approve suggested translations?
14:39 < jordi> The current implementation is built on very complex copy and paste technology :)
14:39 < ivoks> (could we get a checkbox instead?) :)
14:39 < jordi> we do have plans to have the checkbox :)
14:40 < pepsiman> jordi: there's a greasemonkey script which helps
14:40 < jordi> I'm a bit on time pressure I guess, otherwise I'd dig the relevant spec urls
14:40 < danilos> Gwaihir: another thing to note: currently, both fuzzy and string needing review is implemented using the same mechanism in rosetta; there is, however, a plan to separate these out and put them to their right meanings (i.e. fuzzy == machine-selected "similar" string; needs review == human selected "unsure" string)
14:40 < bugman> ivoks: i written a spec on this but it was rejected
14:40 < jordi> danilos, maybe you can find some of the relevant ones so people can read over them
14:41 < jordi> danilos is one of the main rosetta coders. Woo! :)
14:41 < jordi> 20:31 < somerville32> QUESTION: If I suggest a translation and then join the translation team later, are all my suggested translations automatically approved?
14:41 < jordi> somerville32: no, as far as I know. That could be dangerous on some cases, actually
14:42 < jordi> but it might be a good idea to do it if the string was unstranslated
14:42 < somerville32> So I have to go and redo all my work? haha
14:42 < jordi> I can't stress enough that having bug reports for all the requests is really helpful
14:43 < jordi> 20:32 < dand> QUESTION: any plans so far on opening Rosetta for contributions?
14:43 < jordi> dand: "opening", I assume you mean opening the source code
14:43 < dand> yeah
14:43 < danilos> on dneary's QUESTION: Does Rosetta keep a history of translation updates and who made them?
14:43 < Gwaihir> jordi: for the --use-fuzzy question I've a bug was opened: https://launchpad.net/bugs/70974
14:43 < danilos> dneary: yes, Rosetta keeps a history of all translation contributions
14:44 < jordi> There's sabdfl's statement that Launchpad will be freed when the project is ready to do so. We can't give dates or estimations on when that might happen.
14:44 < jordi> There are people helping out with Launchpad on a NDA basis, though.
14:44 < jordi> Gwaihir: thanks
14:44 < dand> jordi: k, thanks
14:45 < jordi> 20:36 < bugman> QUESTION: It's possibile to hava a Wiki page (or other similar) for see LangPack scheduling?
14:45 < Gwaihir> jordi: you are welcome!
14:45 < jordi> bugman: the general rule is "1st Monday of the month". We chose this because it's easy to remember. I'm sure this is written up somewhere though, can't find a pointer irght now
14:46 < bugman> jordi: ok thanks
14:46 < danilos> dneary: but no, we don't have the level of details you wonder about (when string has moved from suggestion to approved, etc.)
14:46 < jordi> there's a Plan™ to write docs pointing these things clearly
14:46 < jordi> 20:36 < dneary> QUESTION: Does Rosetta keep a history of translation updates and who made them?
14:47 < jordi> a feature showing how a string has changed over time has just been rolled onto production, and Rosetta is now gathering this info
14:47 < jordi> This will be good to help team leaders track bad translators
14:48 < jordi> 20:40 < neophile> QUESTION: Where someone should translate a package, in head brunch or in the edgy brunch?
14:48 < dneary> jordi: danilos already answered that - thanks to you both
14:48 < jordi> neversfelde_: this very much depends on the specific packages
14:49 < jordi> we have a feature on our queue, which will allow someone translating gnome-panel in edgy "push" that same translation to dapper, feisty, or GNOME CVS HEAD if applicable
14:50 < jordi> so you just have to translate once
14:50 < ivoks> that would be awsome
14:50 < jordi> neversfelde_: of course, if you translate the Panel in GNOME CVS, that translation will automagically percolate to the next ubuntu release
14:51 < jordi> this gets us to the "working with upstream" chapter
14:51 < jordi> while rosetta is a great tool to get ubuntu translated verfy easily, it's vital that the translation teams cooperate with their upstream teams
14:52 < jordi> ie, the French Ubuntu team should be in contact with the French GNOME team, so they use the same guidelines, etc
14:52 < jordi> or don't duplicate efforts
14:52 < bugman> yes is the same with itlian team
14:52 < bugman> * italian
14:53 < jordi> we've had problems with some teams redoing all the work in Rosetta, which resulted in a completely different set of translations in Ubuntu and other distros.
14:53 < jordi> The "translation override" feature in rosetta is powerful and useful if used wisely. If it goes out of control, it can cause frictiuons between teams.
14:54 < jordi> We need to work on that, I believe it's a procedural problem which can be mostly solved by educating new translators which join the ubuntu teams
14:55 < jordi> there's been quite some talk on this on the rosetta list, and teams like italian or Brazilian have already implemented some measures to work nicely with their upstreams
14:55 < Amaranth> metacity
14:55 < bugman> i quit, thanks jordi :-)
14:55 < Amaranth> beryl-manager
14:55 < jordi> 20:45 < aleka> QUESTION: If I am eager to help the Ubuntu community, and the only way I can right now if through translation, What Can I do when the admin of a team does not respond to my requests or approve my membership to the team?
14:55 < jordi> good one!
14:56 < jordi> aleka: we're seeing this every now and then
14:56 < jordi> the best and quickest way is to mail us at rosetta@launchpad.net
14:56 < pepsiman> lots of people apply to teams without telling the team leader their email address
14:56 < jordi> and we'll mediaate
14:57 < jordi> ie, we'll try to contact the current leader. If he doesn't respont, we'll transfer leadership to whoever we think deserves it (ie, whoever wants to do the work ;)
14:57 < jordi> pepsiman: good point. That's bad, and I've suffered that myself.
14:58 < jordi> danilos: we should think on some way to circumvent this, when a leader can't contact a member because there's no public email address
14:58 < danilos> <dneary> QUESTION: We have had some issues with translations where people outside the project translated things badly, and we couldn't easily revert to the correct translation - how can I configure our translation to make sure only approved translation team members can do the translation?
14:58 < jordi> danilos: want to answer that one?
14:58 < danilos> dneary: at the moment, members of the translation team should only be those you trust; in other words, anyone who is member of your translation team can approve/modify translations
14:59 < dneary> And only translation team members can do translations?
14:59 < dneary> Thanks
14:59 < jordi> right, we ACK that there's oversized teams right now.
14:59 < jordi> dneary: if the given project is setup up like that, yes
14:59 < danilos> dneary: yes; anyone else can post suggestions -- we'll work on improving team layout (and docs), so this is clear to everybody
15:00 < jordi> 20:51 < tonyyarusso> QUESTION: Does Rosetta have some method for handling dialects?  I'm just getting the ball rolling for a language (oji) that varies widely (esp. for technical terms)
15:00 < jordi> tonyyarusso: not yet, but both danilos and I are involved with teams which would benefit of dialect support
15:01 < jordi> We really want to see this happen, but it's not high priority right now
15:01 < jordi> 20:53 < somerville32> QUESTION: How do you know if a translation is suggested or approved?
15:01 < tonyyarusso> jordi: What is the best way to approach things for the time being then until it is implemented?
15:01 < jordi> a approved translation appears in the translation field
15:01 < jordi> suggestions appear as suggestions beneath it
15:02 < danilos> jordi: as far as unresponsive team leaders, we can establish regular "checks" with team leaders; but that's something I feel ubuntu l10n coordinator should handle, since it's not a direct rosetta issue
15:02 < jordi> danilos: ^ want to answer that one?
15:02 < danilos> jordi: sure
15:02 < jordi> yeah, we haven't mentioned the coordinator at all
15:02 < jordi> 20:53 < dneary> QUESTION: Can I export translations in other formats than .po?
15:03 < jordi> dneary: no, Rosetta currently only groks po files
15:03 < jordi> although it will soon be able to export firefox and openoffice data via langpacks.
15:03 < metatecque> QUESTION - is Brandon here yet - isn't the open kubuntu discussion scheduled to start now?
15:03 < danilos> somerville32: any actual translation is the approved one; suggestions only appear as "suggestions"
15:03 < somerville32> kk
15:03 < jordi> but not via the standard export mechanism as far as I know, danilos can correct me
15:04 < dneary> So I need to do a post-processing move to generate a .ts?
15:04 < imbrandon> moins all ( sorry i'm really lagging here )
15:04 < jordi> 20:57 < dneary> QUESTION: What happens in Rosetta when an overridden string gets changed in a later revision of the upstream translation?
15:04 < danilos> dneary: btw, we're working on adding native support for other formats right now; first to come should be firefox XPIs, OpenOffice GSI's, KDE PO files, but we also have plans for XLIFF and others
15:04 < jordi> Rosetta has a "tracker" which makes it think it should follow what comes from upstram or not.
15:05 < imbrandon> jordi: ping me when you wrap it up i'm going to try to fix my lag issue
15:05 < jordi> In short, if you change a string, forking it to something different, it'll stay forked unless you put the upstram string back again.
15:06 < dneary> jordi: How do you get to decide?
15:06 < jordi> We want to implement a filter so it's easy to find these strings and do a "merge with upstream" for them, etc.
15:06 < dneary> Is there a fuzziness thing that shows you changed over-ridden strings?
15:06 < jordi> imbrandon: okay
15:06 < jordi> just kick us out when you're ready
15:06 < jordi> dneary: no, there's proposals to mark them as such
15:06 < jordi> hasn't happened yet
15:07 < jordi> 21:01 < aleka> QUESTION: where can I get help in aquiring fonts that I need for translating (Amharic - ethiopic fonts) that work in Linux. This question emailed to team leader twice and no response..
15:07 < jordi> aleka: you might want to ask in the ubuntu-devel list
15:07 < jordi> mark shuttleworth has big interest in getting ubuntu working out of the box for special script like yours
15:08 < jordi> if there are free fonts, it should be easy.
15:08 < imbrandon> ok jordi i think i'm fixed up here
15:08 < danilos> aleka: finding that information is sometimes even hard for the team leader, since it might be scattered all over internet
15:08 < jordi> just on time, because we're done with the questions
15:08 < imbrandon> :)
15:08 < jordi> Thanks everyone, and thanks danilo!
15:08 < jordi> next, Kubuntu!
15:08 < ivoks> thank you jordi and danilos
15:09 < kappa> thanks, jordi and danilos!
15:09 < danilos> everyone else, feel free to ping us whenever you've got questions :)
15:09 < ivoks> watch out, ping flood :)