=== Nafallo [~nafallo@nafallo.user] has left #launchpad ["Read] === spiv [~andrew@dsl-116.12.240.220.rns02-kent-syd.dsl.comindico.com.au] has joined #launchpad === mpt [~mpt@203-167-186-66.dsl.clear.net.nz] has joined #launchpad === Burgundavia [~corey@S0106000000cc07fc.gv.shawcable.net] has joined #launchpad === lifeless [~robertc@dsl-116.12.240.220.rns02-kent-syd.dsl.comindico.com.au] has joined #launchpad === Burgundavia [~corey@S0106000000cc07fc.gv.shawcable.net] has joined #launchpad === jamesh [~james@203-59-196-1.dyn.iinet.net.au] has joined #launchpad === carlos [~carlos@69.Red-80-33-181.pooles.rima-tde.net] has joined #launchpad === Luciph3r [~Luciph3r@217.221.83.130] has joined #launchpad [10:53] reboot === Luciph3r [~Luciph3r@217.221.83.130] has left #launchpad ["Mi] === Luciph3r [~Luciph3r@217.221.83.130] has joined #launchpad === SteveA_ [~steve@213.226.190.253] has joined #launchpad === morgs [~morgan@wblv-146-238-216.telkomadsl.co.za] has joined #launchpad === spiv [~andrew@CPE-141-168-51-86.nsw.bigpond.net.au] has joined #launchpad === salgado [~salgado@200-171-140-32.dsl.telesp.net.br] has joined #launchpad === bradb [~bradb@MTL-ppp-147026.qc.sympatico.ca] has joined #launchpad === SteveA_ [~steve@adsl-213-190-44-43.takas.lt] has joined #launchpad [04:28] Time passes... [04:29] It is dark === lamont__ [~lamont@15.238.5.202] has joined #launchpad [04:32] carlos, ping [04:32] mdke, pong [04:32] carlos, one of the portugese guys has just asked me a question about translation [04:32] which one? [04:32] carlos, he says the translations of the gnome menus are inaccurate, would you know where he can correct these? [04:33] joao === lamont__ is now known as lamont_r === jalrnc [~joao@ip68-0-220-224.ri.ri.cox.net] has joined #launchpad [04:34] carlos, meet joao [04:35] carlos: hi [04:35] jalrnc, hi [04:35] we are translating the quickguide as you know, and it makes references to application names that show up in the gnome menus [04:35] those application names in gnome already exist when we install portuguese support with ubuntu [04:35] 1. some of those names are not properly translated 2. we would like to have them corrected and so be consistent with quickguide [04:35] usually, the translation is stored inside the application [04:36] so for instance, if the Evolution translation is broken [04:36] you should fix it at:... === carlos looks for the URL === koke [~koke@adsl229-164.unizar.es] has joined #launchpad [04:36] koke, ! [04:36] hi! [04:37] carlos, he was wondering whether it is best to translate in rosetta and then push upstream, or coordinate directly with upstream (gnome?) [04:37] carlos: so we should fix those names at each individual application, ok [04:37] I'm planning to work on the FindingPackages goal, and I'll need some help from launchpad team [04:37] carlos: right [04:38] can someone tell me what is this about https://wiki.launchpad.canonical.com/DoapSchemaNG ? [04:38] I can't see it :) [04:38] hmmm, evolution is really slow in Rosetta.... we should improve its performance... [04:39] mdke, jalrnc: Well, you can use Rosetta and then send the updates to upstream [04:39] mdke, jalrnc usually is a good thing to coordinate with upstream that way the fix is shared [04:39] koke, morgs is your man [04:39] carlos: what's the best way to coordinate with upstream? [04:40] koke: I'm responsible for DoapSchemaNG... it's about extending the Launchpad product registry to allow multiple wikis, mailinglists, screenshot URLs, download URLs etc per product / productrelease etc. [04:40] carlos: lets say we fix it first in rosetta, what should we do next? or should we coordinate with upstream before start changing in rosetta? [04:41] koke: Not really major rocket science, just extending the launchpad database schema a bit. [04:41] morgs: great, that's what I needed [04:41] jalrnc, the best solution is talk first with upstream [04:41] I was wondering if you were working on it [04:41] koke: yes [04:41] jalrnc, and you can use Rosetta so Ubuntu gets the fix and then send the fixed .po file to upstream [04:42] http://koke.amedias.org/img/g-a-i-mockup-2.png <-- I need to extract that metadata from somewhere [04:42] carlos: and by upstream you mean each application individually or gnome upstream? [04:42] jalrnc, if you want the fix in Ubuntu, you need to use Rosetta, but you don't need to use Rosetta to coordinate with upstream if you don't want to [04:42] carlos: ok [04:42] jalrnc, in GNOME case, the GNOME Portuguese team [04:43] morgs: but some I'll need also information about available versions in diferent releases of ubuntu. Is this possible from DOAP-ng ? [04:43] evolution was not a good choice as example... [04:44] carlos: ok, should those menu names be fixed in each indivual application individually or in gnome? [04:44] jalrnc, those menu names come from the application [04:44] carlos: ok [04:44] so you need to fix them individually [04:44] koke: Hmm. All the data is in the database, but it is "part" of different systems - so the versions in Ubuntu are part of the "soyuz" part of launchpad. [04:45] got it [04:45] I'm not convinced you want to know the different versions available [04:45] unless they're in your apt sources [04:45] in which case the info is available by interrogating apt [04:45] morgs: I know. What I need is a rdf file for all that data, it will be processed at the client [04:45] I'll discuss with my team weather we want to fix it in rosetta, but I think we do, and we'll definitely coordinate with upstream [04:46] koke: Another project w.r.t. DOAP is to publish project/product/productseries/productrelease information in RDF/XML format - like the real DOAP upstream project. [04:46] carlos, mdke: thanks! [04:46] koke: the RDF publishing is targeted at being implemented by July 6. [04:46] "Launchpad 1.0" [04:46] cheers carlos [04:46] morgs: I can manage the files in another place for development and integrate with launchpad then [04:47] It will include the basic Freshmeat-type details in RDF - basically representing the "upstream" versions of the products, not the ubuntu versions. [04:47] jalrnc, no, thank you! === jalrnc [~joao@ip68-0-220-224.ri.ri.cox.net] has left #launchpad [] [04:47] mdke, cheers [04:47] morgs: maybe the final solution will imply to have those files in another place but taking the data from launchpad === jalrnc [~joao@ip68-0-220-224.ri.ri.cox.net] has joined #launchpad === jalrnc [~joao@ip68-0-220-224.ri.ri.cox.net] has left #launchpad [] [04:49] koke: I'm not sure what you mean by "in another place", but the basic idea is that a product in launchpad is at https://launchpad.ubuntu.com/products/foo, and you will find the RDF at https://launchpad.ubuntu.com/products/foo/+rdf [04:49] It will have a list of product releases (I'm oversimplifying but basically...) and each release will have the URL where you can download the RDF for that release. [04:50] morgs: I have to spec what I need in that file and I'll tell you to see if it fits on launchpad plans [04:50] like https://launchpad.ubuntu.com/products/foo/+series/stable/1.0.1/+rdf [04:51] koke: I can mail you a preliminary example of the RDF files - still subject to change at this stage but will give you an idea... [04:51] and any way to match which version is on a specific ubuntu release? [04:51] morgs: great :) [04:52] koke: Soyuz RDF hasn't even been specced at all yet [04:52] koke: Hmm. It just gives "upstream" releases. [04:52] Kinnison: that would be done by soyuz rdf?? [04:52] koke: Well, if you care about what is in a distro yes [04:52] soyuz is all the distro-related stuff [04:52] ok [04:53] that's what I meant with "in another place" [04:53] So you'd be looking for something like: /distros/ubuntu/hoary/foosourcepackage/+rdf [04:53] but that's way off [04:53] back in a bit... [04:54] Kinnison: maybe, just some way to be able to discover from a doap rdf which version of that product is availble in each ubuntu release [04:55] it'd be not-right to look via doap for that I don't think [04:55] but we've not got completely tight distro<->upstream linkage in the db yet === koke [~koke@adsl229-164.unizar.es] has joined #launchpad [06:15] bradb: is there any way to list all the bugs for a package? [06:15] or is planned to be? [06:16] koke: there have been a few requests for it (i've wanted to use it too :). how about if we made "All Bugs" one of the search "quick links"? [06:17] if you had a different expectation of how it would be done, please feel free to tell me about it [06:18] bradb: just like https://launchpad.ubuntu.com/malone/distros/ubuntu, but https://launchpad.ubuntu.com/malone/products/foo [06:18] an url for a "show bugs of package foo" [06:18] /malone/products/foo already works [06:19] do you mean /distros/ubuntu/+packages/somepackage and /distros/ubuntu/hoary/+packages/somepackage or something like that? === JanC [~janc@dD5764BD1.access.telenet.be] has joined #launchpad [06:23] bradb: yep, something like that [06:24] koke: i feel it would be useful too. you can likely expect that kind of thing to land a little bit after 1.0. [06:25] ok [06:26] bradb, isn't it what /distros/ubuntu/+packages/somepackage/+bugs is for? [06:26] I suppose it's not implemented yet :-) [06:27] correct ;) [06:27] but I think we talked about it at UDU [06:27] bradb, isn't it a 1.0 goal? [06:27] we talked about it as early as cape town, just didn't prioritize it for 1.0. [06:27] bradb, it's part of launchpadmenus, isn't it? [06:27] carlos: no. [06:27] not that i'm aware of. [06:27] oh, ok [06:28] which isn't saying that it for sure isn't, but just that if it /is/, i didn't know that was a required part of making LP menus work === mdke [~mdke@81-178-74-18.dsl.pipex.com] has joined #launchpad === bradb [~bradb@modemcable082.64-130-66.mc.videotron.ca] has joined #launchpad === koke [~koke@219.Red-81-35-151.pooles.rima-tde.net] has joined #launchpad === Luciph3r [~Luciph3r@217.221.82.66] has joined #launchpad === Burgundavia [~corey@S0106000000cc07fc.gv.shawcable.net] has joined #launchpad