=== mholthaus [n=mholthau@johnny33.dersbach.ch] has left #launchpad ["Konversation] === stub [n=stub@ppp-58.8.4.50.revip2.asianet.co.th] has joined #launchpad === BenC [n=bcollins@debian/developer/bcollins] has joined #launchpad [02:04] is lp choking or is it me? [02:05] its choking === BenC performs the heimlich [02:05] i have reason to believe its a hot dog stuck in the throat [02:15] looks like whatever it was got dislodged [02:15] maybe feed it smaller bites, or pre-chew it's food in the future :) [02:17] no, it still seems to be rather slow here, taking a couple of minutes at least to load a page :) === bluefoxicy [n=bluefox@c-68-33-112-13.hsd1.md.comcast.net] has joined #launchpad [02:27] is there anything I should particularly know about creating something so it can easily be shifted into a launchpad module? === bluefoxicy wants to write something independent as a proof of concept; but some of it may be useful later [02:32] bluefoxicy, what do you mean by "a Launchpad module"? [02:36] mpt: I don't know, I don't seem to have the source for launchpad so I'm guessing ;) [02:36] mpt: I am considering, possibly, doing a quick sketch of how something like https://wiki.ubuntu.com/AutomatedProblemReportsTagging would work [02:43] eh I have a paper to finish, I'll worry about this later. === bluefoxicy [n=bluefox@c-68-33-112-13.hsd1.md.comcast.net] has left #launchpad ["google] === BenC [n=bcollins@debian/developer/bcollins] has left #launchpad ["Ex-Chat"] === mpt_ [n=mpt@121-72-132-184.dsl.telstraclear.net] has joined #launchpad === mpt [n=mpt@121-72-132-184.dsl.telstraclear.net] has joined #launchpad === somerville32 [i=somervil@fctnnbsc15w-156034084072.nb.aliant.net] has joined #launchpad [06:21] BjornT: thanks for retrieving that bug description. [06:24] jamesh: no problem. +edit still worked, so it wasn't hard. [06:25] New bug: #73419 in launchpad "Allow locking of bug descriptions" [Undecided,Unconfirmed] http://launchpad.net/bugs/73419 [06:26] BjornT: I guessed you'd done something like that. Good thinking :) [06:26] New bug: #73420 in launchpad "We attempt to render ridiculously large chunks of user input" [Undecided,Unconfirmed] http://launchpad.net/bugs/73420 [06:29] maybe we could refuse bug comments containing the text "ProblemType: Crash" :) [06:29] jamesh, why would I get "ImportError: cannot import name testutil" (from importd.tests)? [06:29] mpt: update the sourcecode/ subtrees? [06:29] Is there a quick way of updating all of them? :-) [06:30] New bug: #73421 in launchpad "Feature: Revert to old state" [Undecided,Unconfirmed] http://launchpad.net/bugs/73421 [06:30] depends on how you created them [06:30] I use lightweight checkouts for them against the rocketfuel-built tree, which means a simple "bzr update" is all that's needed [06:31] In this case, as a lightweight checkout [06:31] bzr update from sourcecode/? === mpt tries that [06:31] from each sourcecode/foo directory [06:31] darn [06:33] how do you normally update the subtrees? [06:34] When someone mails launchpad@ and says "You need to update your X subtree", I go into that directory and use bzr pull [06:34] I haven't used bzr update before [06:36] Ok, "bzr update" for every subtree says it's up to date, but I still get the error [06:37] mpt: if you aren't using checkouts for the subtrees, then "bzr update" won't do anything (the trees will be up to date with themselves) [06:37] mpt: so use "bzr pull" then [06:37] This whole working directory is a lightweight checkout [06:37] So why wouldn't the sourcecode/ subdirectory consist of checkouts? [06:38] er, this whole branch, I mean [06:39] mpt: your launchpad tree may be a lightweight checkout -- whether the trees under sourcecode/ are lightweight checkouts would depend on how you created them [06:39] if you copied them from rocketfuel-built, then they'd be standalone trees [06:41] ahhh [06:46] Who has DB access other than stub? [06:52] jamesh, do you? [06:52] don't seem to [06:52] (I did back when I was doing the bug imports, but not any more) [06:53] So what's the procedure for spammers when stub is asleep? :-/ [06:53] email [06:53] is it urgent? [06:54] Yes, bug 1 is being vandalized [06:54] Malone bug 1 in Ubuntu "Microsoft has a majority market share" [Critical,In progress] http://launchpad.net/bugs/1 [06:54] lifeless might be able to help [06:55] mpt: I get a static page for that bug ;) [06:57] mpt: the admins probably have access, but might not know what to do [06:57] crappity [07:09] but, yay for it being stopped for now [07:11] whats up [07:12] mpt: stub, all the admins, and I [07:12] lifeless, I was just belatedly concerned about the spamming of bug 1, but bug 1 is now static and the offender seems to have been deleted [07:12] Malone bug 1 in Ubuntu "Microsoft has a majority market share" [Critical,In progress] http://launchpad.net/bugs/1 [07:12] so, never mind [07:12] Alas, I predicted this a few days ago, but that was too late :-P [07:13] heh [07:14] bug 73122 [07:14] Malone bug 73122 in malone "Need strategy for stopping pandemonium in individual bug reports" [Undecided,Unconfirmed] http://launchpad.net/bugs/73122 [07:15] Ugh, why do I get a conflict when merging sourcecode/bzr/? [07:15] Text conflict in bzrlib/tests/test_hashcache.py [07:17] why are you merging? [07:17] do a pull --overwrite mpt [07:17] "bzr: ERROR: These branches have diverged" [07:17] oh [07:17] darn [07:17] I already merged and committed zope/, I hope that doesn't matter [07:17] Oh, I suppose I could just pull --overwrite that one too [07:18] mpt: yes, you should [07:18] mpt: in general, you shouldn't have to commit in the subtrees unless you're making changes to them [07:18] mpt: unless you are developing on one of these branches [07:20] Now I have 3 "can't delete bzrlib/ because it is not empty" conflicts [07:20] (After reverting and --overwriting) [07:20] mpt: delete them by hand, [07:20] mpt: 'bzr st' should show nothing when you are done [07:20] oh, it's just .pyc [07:21] spiv: how goes it ? === raphink [n=raphink@ubuntu/member/raphink] has joined #launchpad [07:23] Yay, now I have a different error [07:23] "No module named urlutils" [07:24] mpt: have you updated your bzr? [07:24] yes [07:24] bzrlib.urlutils is in the newer bzr [07:24] The saved location is on chinstrap, though [07:25] Is it more up to date on devpad? [07:25] of course. [07:25] ok === Fujitsu [n=william@ubuntu/member/fujitsu] has joined #launchpad === stgraber [i=stgraber@server.lan.stgraber.org] has joined #launchpad === Keybuk [n=scott@quest.netsplit.com] has joined #launchpad === Seveas [n=seveas@ubuntu/member/seveas] has joined #launchpad === Fujitsu [n=william@ubuntu/member/fujitsu] has joined #launchpad === raphink [n=raphink@ubuntu/member/raphink] has joined #launchpad === malcc [n=malcolm@host86-135-237-55.range86-135.btcentralplus.com] has joined #launchpad [09:34] stub: ping === seb128 [n=seb128@ubuntu/member/seb128] has joined #launchpad === ddaa [n=ddaa@nor75-18-82-241-238-155.fbx.proxad.net] has joined #launchpad [10:02] Hello there [10:03] SteveA: jamesh: spiv: lifeless: ping [10:04] gnip [10:04] Meeting? [10:05] indeed === carlos [n=carlos@75.Red-88-12-132.dynamicIP.rima-tde.net] has joined #launchpad [10:06] mornin [10:06] morning [10:08] hi ddaa === mholthaus_ [n=mholthau@146.112.3.213.cust.bluewin.ch] has joined #launchpad === stu1 [n=stub@ppp-58.8.13.237.revip2.asianet.co.th] has joined #launchpad === quail [n=quail@unaffiliated/quaillinux/x-000001] has joined #launchpad === somerville32 [n=somervil@fctnnbsc15w-156034079057.nb.aliant.net] has joined #launchpad === jinty [n=jinty@177.Red-83-54-74.dynamicIP.rima-tde.net] has joined #launchpad [10:49] review meeting in 12 minutes [11:05] review meeting time [11:05] me [11:05] sorry I'm a litle slow, massive headache [11:06] hi [11:06] I thought "so" came after "me"? ;) [11:06] hi [11:06] spiv: yes, "fa" first [11:07] == Agenda == [11:07] * Roll call [11:07] * Queue status. [11:07] * Whitespace cleanup [11:07] * reviewers to discuss ideas and principles for keeping branch review quick (was on LP meeting agenda) === spiv wonders where "hi" lands in the octave [11:07] at the top [11:07] the very top [11:08] the queue is very big right now [11:09] how are you guys going with the backlog ? [11:10] SteveA suggests that you all look at https://devpad.canonical.com/~jamesh/pending-reviews/ [presumably in case you have forgotten where it is :)] [11:10] I was actually thinking of the wiki page [11:10] but still, I think it's useful to have a call to focus in a meeting [11:11] I think we should consider a new meeting time, so francis and salgado can be here [11:11] we can consider that [11:11] I'll send mail tomorrow [11:11] thanks [11:12] for now though.. [11:12] spiv: you have 3 > 20 days in the queue. when are they going to be reviewed ? [11:12] jamesh: you also have 3 > 20 days.. [11:13] SteveA: your pyrex branches will be reallocated as soon as either spiv or jamesh indicate a preference to do it. [11:13] Immediately, basically. I have half of a (follow-up) review for ddaa's import-svn-safety written. [11:13] I [11:14] 'm working through my oldest two. Will send out soon. Will work on more tomorrow [11:14] And the other two look short, I expect to have them done tomorrow morning at the latest. [11:14] cool. [11:15] I'd like to knock some of my other reviews off before accepting the pyrex branch. [11:15] I realise its a heavy load right after all hands... effect and cause. [11:15] spiv: how do you feel about pyrex ? [11:15] I'm happy to take it. [11:15] ok [11:15] * whitespace cleanup [11:15] this is an item from some time back, jamesh was going to raise at the regular lp meeting. [11:16] jamesh: ? [11:16] spiv: If you haven't gotten to it by the time I've cleared out my queue, I can look at the pyrex branch. [11:16] lifeless: I think this is old. This was brought up a few weeks back (before allhands), and everyone agreed to the change. [11:17] jamesh: thanks, I'll punt it to you if it starts going stale. [11:17] jamesh: ok. [11:17] * reviewers to discuss ideas and principles for keeping branch review quick (was on LP meeting agenda) [11:17] jamesh: you added this. over to you [11:17] SteveA asked me to add it [11:18] SteveA: ? [11:18] I think this was basically what we were discussing earlier [11:19] yeah. [11:19] we want people to make smaller branches to review [11:19] divide their work into smaller chunks to land on mainline [11:19] so a reviewer can see the correspondence between tests and interfaces and gui and code [11:20] people will need help with this, so encourage calls to discuss how they'll break up the work [11:20] encourage agreeing a written plan on this, if it will help [11:20] I'm sure you'll have other ideas too [11:23] done [11:24] I agree with the goals [11:24] not thinking well right now - headache as I mentioned. [11:24] I suggest we all mull on this and discuss next week [11:25] any other business - unless folk have comments on this now ? [11:25] 5 [11:26] 4 [11:26] spiv: can you please assign the pyrex branches to yourself [11:26] ok [11:27] 3 [11:27] thanks [11:27] 2 [11:29] The suspense is killing me. [11:29] 0 [11:30] meeting over, thanks for coming === cprov [n=cprov@monga.dorianet.com.br] has joined #launchpad === danilos [n=danilo@adsl-221-97.eunet.yu] has joined #launchpad === niemeyer [n=niemeyer@200.138.43.78] has joined #launchpad === matsubara [n=matsubar@200-171-140-32.dsl.telesp.net.br] has joined #launchpad === salgado [n=salgado@200-171-140-32.dsl.telesp.net.br] has joined #launchpad === BjornT [n=bjorn@clt-84-32-240-183.dtiltas.lt] has joined #launchpad === Hobbsee [n=Hobbsee@ubuntu/member/hobbsee] has joined #launchpad === jsgotangco [n=jsg123@ubuntu/member/jsgotangco] has joined #launchpad === Starting logfile irclogs/launchpad.log === ubuntulog [i=ubuntulo@ubuntu/bot/ubuntulog] has joined #launchpad === Topic for #launchpad: Developer meeting: Thu 30 Nov, 1200UTC (wiki:MeetingAgenda) | launchpad-users@lists.canonical.com (wiki:MailingLists) | Channel logs: http://tinyurl.com/72w39 === Topic (#launchpad): set by LarstiQ at Sun Nov 26 19:00:09 2006 === Spads [n=spacehob@82.211.81.249] has joined #launchpad === carlos -> lunch === sabdfl [n=sabdfl@ubuntu/member/pdpc.silver.sabdfl] has joined #launchpad === Gwaihir [n=Gwaihir@mail.foredil.it] has joined #launchpad === niemeyer_ [n=niemeyer@201.15.220.164] has joined #launchpad [02:38] matsubara: hi. are you expecting kiko to be in soon? [02:39] Hi SteveA, let me ask Taciana. I arrived yesterday and haven't seen him yet. === frafu [n=frafu@85.93.207.78] has joined #launchpad === niemeyer [n=niemeyer@200.138.132.233] has joined #launchpad === static [n=emurphy@194.18.118.70.cfl.res.rr.com] has joined #launchpad === carlos [n=carlos@75.Red-88-12-132.dynamicIP.rima-tde.net] has joined #launchpad === flacoste [n=francis@modemcable207.210-200-24.mc.videotron.ca] has joined #launchpad === static [n=emurphy@194.18.118.70.cfl.res.rr.com] has left #launchpad ["Ex-Chat"] === static [n=emurphy@194.18.118.70.cfl.res.rr.com] has joined #launchpad === frafu [n=frafu@85.93.207.78] has joined #launchpad === belito [n=user@201.230.49.33] has joined #launchpad === Brushy [n=chatzill@dsl-aur-fefadf00-144.dhcp.inet.fi] has left #launchpad [] === xerxas [n=R67894@AGrenoble-257-1-100-136.w90-9.abo.wanadoo.fr] has joined #launchpad === BugMaN [n=BugMaN@nat.cabi.uniroma1.it] has joined #launchpad [04:34] Hi all [04:35] I would lke to request an "ambassador role" for packages [04:35] following discussions on #ubuntu-classroom [04:38] xerxas: I think you should ask at #ubuntu-devel or #ubuntu [04:38] carlos: he just got sent here from #ubuntu-classroom with the open day [04:39] hmmm === BjornT [n=bjorn@clt-84-32-240-183.dtiltas.lt] has joined #launchpad [04:39] to launchpad? [04:39] yes [04:39] ok, then I'm not the right person to answer.... [04:39] Hobbsee, thanks :) [04:39] cprov: ? [04:40] carlos: hey === jeroentietema [n=jeroen@108pc209.sshunet.nl] has joined #launchpad === jeroentietema [n=jeroen@108pc209.sshunet.nl] has left #launchpad ["Ex-Chat"] === WebMaven [n=webmaven@ip72-193-220-34.lv.lv.cox.net] has joined #launchpad === doko [n=doko@dslb-088-073-092-133.pools.arcor-ip.net] has joined #launchpad === BjornT_ [n=bjorn@clt-84-32-240-183.dtiltas.lt] has joined #launchpad === kiko [n=kiko@200-171-140-32.dsl.telesp.net.br] has joined #launchpad === BugMaN [n=BugMaN@nat.cabi.uniroma1.it] has left #launchpad [] === somerville32 [i=somervil@fctnnbsc15w-156034090229.nb.aliant.net] has joined #launchpad === BjornT [n=bjorn@clt-84-32-240-183.dtiltas.lt] has joined #launchpad [05:07] hello warriors of bug #1 [05:07] Malone bug 1 in Ubuntu "Microsoft has a majority market share" [Critical,In progress] http://launchpad.net/bugs/1 [05:08] heh [05:08] Wrong channel :) [05:08] is there a launchpad developper ? [05:09] there are many === somerville32 points at kiko. [05:09] it's not like highlander [05:09] I would lke to request an "ambassador role" for packages [05:09] following discussions on #ubuntu-classroom [05:09] sabdfl and seb128 agrees with that [05:09] tell me all about it [05:10] what should I do so that request is not lost ? [05:10] kiko, an ambassador role is like a mainteners except the ambassador reports bugs upstream [05:10] and develop good contacts with the upstream team [05:10] kiko, is there anything more you want ? [05:11] xerxas!!! [05:11] (this role is within malone only, If I understand correclty ) [05:11] kiko, !!!! [05:11] :) [05:11] xerxas, so, that's a fabulous idea, and one that mdz and I have discussed many times [05:11] and so ? [05:11] so [05:12] is it going to happen ? or what should I do so that it's being done soon or late ? [05:12] here's a question for you: what does this differ from becoming a package bug contact? [05:12] this is a questions for sabdfl and seb128 probably :) [05:12] maybe the bug contact could filter questions from ubunteros to the ambassador [05:13] the ambassador have more an upstream role, the bug contact probably a downstream role [05:13] but that's only my point of view [05:14] xerxas, shouldn't the "ambassador" get notifications of upstream bugs? [05:14] maybe [05:14] xerxas, because if so, we could just have the ambassador be the bug contact for the upstream product [05:14] probably [05:14] that that's all! === mdz [n=mdz@studiocity-motorola-bsr1-70-36-194-85.vnnyca.adelphia.net] has joined #launchpad [05:14] then the only thing necessary is to add a packaging link [05:15] and everything works as expected [05:15] hello mdz [05:15] speak of the devil [05:16] sabdfl, are you here ? [05:17] can you see a difference between the "package bug contact" and "package ambassador role" ? [05:17] aside the name :) [05:17] xerxas, I think the ambassador role can use the launchpad bug contact functionality to function [05:18] the other part I think is important is to make clear what the ambassador should do [05:18] kiko, I'm not a launchpad master [05:18] i.e. to have a documented process [05:18] kiko: morning [05:18] xerxas, that's fine -- we're here to help! [05:18] kiko, I were attending the ubuntu-classroom , seb128 where talking about an ambassador for package [05:18] I suggested this appears in launchpad, and that's all [05:19] I see now [05:19] I think that's a great idea. [05:19] kiko: the idea is to have a "point of contact" for a package [05:19] somebody upstream could mail when he wants to speak about its software and how it's packaged [05:20] seb128, would he also do bug forwarding, or is that separate? [05:21] xerxas: i would see the ambassador as a more general point of contact between ubuntu and the upstream [05:22] seb128, thanks for clarifyng [05:22] kiko: no, not bug forwarding [05:22] ah, okay. [05:22] for example, its often useful for us to know *which* version of a package is the best to aim for in a particular ubuntu release [05:22] that's indeed different. [05:22] rather pointing the person in contact with upstream [05:22] sabdfl, that's pretty much my point of view, ambassador is upstream, bug contact is downstream (ubunteros) [05:25] I see. [05:27] kiko, is that ok ? [05:28] did you got It ? [05:28] am I suppose to make a feature request anywhere ? [05:28] xerxas, I still need to think a bit more about what launchpad could do to help you [05:28] ok [05:28] is it just having an "Upstream ambassador" slot? [05:28] yes, think so [05:28] what would this slot do? [05:29] kiko: yes, together with the means to work with that group as a community (i.e. mail them) [05:29] this is the "adopt and upstream" thing, i think [05:29] sabdfl, all the ambassadors of all packages, and the individual ambassador by package name? [05:30] yes, i imagine that would do it :-) [05:31] sabdfl, the adopt an upstream thing I specifically envisioned assisting bug reporters moving bugs upstream [05:31] so this is different [05:31] I think it's a good idea [05:32] but wonder if we couldn't conflate the two and get two hits for the price of one [05:32] have to go guys [05:32] bye ! === gnomefreak [n=gnomefre@ubuntu/member/gnomefreak] has joined #launchpad [05:37] i just started a spec for LP on package ambassadors here: https://blueprints.launchpad.net/products/launchpad/+spec/package-ambassador the wiki isnt done yet but i will continue on it sometime today. [05:37] i think we already have upstream bug contacts [05:37] hey gnomefreak [05:37] hi kiko [05:37] so the adopt-an-upstream idea was to be a general ambassador [05:38] we do have upstream bug contacts but it's not clear that they are the people to be notified when we want to forward bug reports to an upstream bugtracker [05:38] they dont ever seem real active with bugs that i have seen [05:39] mainly with bugs the qa team does most of it but we rarely ever contact upstream we just send bugs upstream [06:00] would it make sense to write a job description (but call it something more acceptable) for the sake of clarity for that role, ambassador? [06:02] My $DEITY, there's a HOWTO on encouraging women? [06:04] yeah, the spec should definitely have a job description. [06:04] Could probably draft something [06:05] Anyone else doing work which would overlap that? [06:05] https://blueprints.launchpad.net/products/launchpad/+spec/package-ambassador === danilos [n=danilo@cable-89-216-150-96.dynamic.sbb.co.yu] has joined #launchpad [06:10] matsubara: oh my... was this interesting! https://launchpad.net/products/launchpad/+ticket/600 [06:11] there is no bound to what people with too much free time can achive === jkakar [n=jkakar@d66-183-122-248.bchsia.telus.net] has joined #launchpad === Administrator__ [i=somervil@fctnnbsc15w-156034090229.nb.aliant.net] has joined #launchpad [06:18] kiko: yes, I saw that. Bit thin on detail though (which, admittedly, could be a desirable state) [06:18] YoussefAssad, luckily it's a wikipage! :) [06:18] free time? What is free time? [06:19] kiko: I can take a hint! :) Okay, let me see what I can whip up in a day or two [06:19] ddaa: I'd suggest that drawing attention to worthless abuse on a public channel plays to the intention of the abuser. [06:20] ddaa: that looks like macedonian ;) [06:20] so there'd essentially be an ambassador per package? Where one person could map to multiple ambassadorial posts, of course [06:20] SteveA: I just find this one so extreme it's funny. [06:20] I did too [06:20] I wonder what he meant though [06:20] which site? === somerville32 [n=somervil@fctnnbsc15w-156034080045.nb.aliant.net] has joined #launchpad [06:28] I'm looking at this page: https://wiki.ubuntu.com/launchpadambassadors and wondering if there's a spec spec, or if I can just run in there and append sections pertinent to an eventual SoW/JD for the ambassadorial role === AlinuxOS [n=AlinuxOS@d83-190-149-0.cust.tele2.it] has joined #launchpad [06:33] danilos: hey [06:34] jordi: heey pretty boy, how's it going? [06:34] danilos: if you're going to be around for some more time, there's the Rosetta session in 1.5 hours. [06:34] there'll be a Q+A session after I dump my text; if you can be around for extra support, that'd be good :) [06:35] jordi: sure, though I am not sure I understand what you mean by "Rosetta session" [06:35] :) [06:35] Ubuntu Open Week [06:35] dude [06:35] https://wiki.ubuntu.com/UbuntuOpenWeek [06:35] danilos, wake up [06:35] jordi: ah, right === jordi winks danilos [06:35] kiko: kiss me to wake me up :) === kiko blows a rabid kiss to danilos [06:36] ah, yuck, now I am woken up :) [06:36] heh [06:37] it sucks that just 2 hours before your talk your wireless thingy blows up and you have to doo all the session in a not so comfy table [06:37] Listen, question people if you don't mind. Is there a format for specs on the wiki which is preferred^H^H^H^H^H^H^H^H^H insisted upon? [06:38] there's a specification template [06:38] jordi: tell me about it: I had my phone line supposedly changed to ISDN today, but it turned out completely broken, and my ADSL is not working, so I am now connected via my old ISP, and if I don't want to re-set-up everything, this means cable as well [06:39] heh [06:39] yes, I see it nicely laid out here: https://wiki.ubuntu.com/launchpadambassadors . I'm just wondering if I should append a morevdetailed role description there, or if structure nazis would persecute me [06:39] you're back to isdn? [06:39] wtf? [06:39] jordi: no, wifi internet [06:40] jordi: the speed is fine, but this ISP breaks a lot, and my ap is not set-up to share that connection, so I have to plug cable in [06:40] is it normal for Canonical to keep people waiting three days for information about commercial support, incidentally? [06:40] there's a chap on #ubuntu-marketing sitting on a 50 node ubuntu HA cluster who apparently wants to buy support === AlinuxOS [n=AlinuxOS@d83-190-149-0.cust.tele2.it] has joined #launchpad [06:41] ubuntu-marketing is not the best way to get in contact with commercial support [06:41] I know, he was in there to see if the marketing people would be interested in documenting his cluster === AlinuxOS [n=AlinuxOS@d83-190-149-0.cust.tele2.it] has joined #launchpad [06:42] He apparently sent an inquiry using an online form. Anyhow, what do I care, I'm with Grameen, not Canonical! [06:42] dinnertime [06:42] YoussefAssad: he wanted to buy support, or get documentation? [06:42] I'm confused [06:42] hello all, is there new version of rosetta in some time ? [06:42] SteveA, documenting his cluster as a case study. [06:43] SteveA: jerom1 is the nick if you're curious [06:43] SteveA: Being in #ubuntu-marketing was for a different thing entirely, asking if his cluster was worth using for marketing purposes. Two distinct issues [06:43] Dinner, really. === Gwaihir [n=Gwaihir@ppp-177-105.25-151.libero.it] has joined #launchpad === AlinuxOS [n=AlinuxOS@d83-190-149-0.cust.tele2.it] has joined #launchpad === AlinuxOS [n=AlinuxOS@d83-190-149-0.cust.tele2.it] has joined #launchpad === raphink [n=raphink@ubuntu/member/raphink] has joined #launchpad === jinty [n=jinty@177.Red-83-54-74.dynamicIP.rima-tde.net] has left #launchpad ["Leaving"] === BjornT_ [n=bjorn@clt-84-32-240-183.dtiltas.lt] has joined #launchpad [07:19] hey SteveA === daq4th [n=darkness@netstation-005.cafe.zSeries.org] has joined #launchpad === daq4th [n=darkness@netstation-005.cafe.zSeries.org] has joined #launchpad [07:29] ddaa, ping? [07:36] kiko: ping [07:36] carlos, yes? [07:37] kiko: do you have some time for an UI problem I got while fixing translation reverting? [07:37] sure. what's up? [07:38] kiko: so, I'm adding too the 'locking' feature we talked for po imports to the translation form [07:38] and I'm not completely sure what's the best option to show a message to the user when someone else changed a string while they were translating [07:39] with our current UI [07:39] carlos, so the workflow is: user loads page, other user uploads, user posts page, boom, right? [07:39] with TranslationReview UI it's quite easy, because I have a place for current translation, and another for the submitted value [07:39] kiko: user uploads or other user submits [07:39] ah, ok [07:39] kiko: but yeah, that's the idea [07:39] right. [07:40] and you want to display these conflicting changes specially, right? [07:40] the problem is how to represent current translation + submitted value [07:40] yeah [07:40] erm, the package ambassadors; wouldn't their role overlap with ubuntu packge maintainers to an extent? [07:40] the current value would appear as Currently used without changes [07:40] but there is no way to detect which one is selected in this context [07:41] from the UI perspective [07:41] how about: /!\ Another user submitted a modification to this string while you were editing it. Please review the change below and modify as necessary. [07:41] so we lose what they submitted [07:41] do we lose it? [07:41] hmm [07:42] 'review change below' [07:42] right [07:42] I thought you mean to revert the textarea content to the active translation [07:42] well.. you could do that too. I'm not sure what the option is; just suggesting warning the user is a good idea [07:44] well, I already know that is a good idea to show a warning ;-) [07:45] another option would be [07:45] to leave it as I have it right now [07:45] which sucks a bit [07:45] and wait for TranslationReview to get a less sucky UI [07:46] so I don't expend time in a UI that will be die with TranslationReview (but that will be good for the users) [07:46] so I could say: 'Please, review the suggestions and submit the form again if you prefer to use your changes' [07:47] kiko: what do you think? [07:48] hold on [07:48] ok === elmo [n=james@83-216-156-21.jamest747.adsl.metronet.co.uk] has joined #launchpad [08:07] kiko: ? [08:07] I need to leave [08:10] kiko: please, ping me if you have more input on the issue. === carlos -> out === stub [n=stub@ppp-58.8.13.237.revip2.asianet.co.th] has joined #launchpad === jkakar [n=jkakar@204.174.36.228] has joined #launchpad [08:15] New bug: #73509 in rosetta ".po file export doesn't update cached files" [Critical,Confirmed] http://launchpad.net/bugs/73509 === fdoving [n=frode@ubuntu/member/frode] has left #launchpad [] === Gwaihir [n=Gwaihir@ppp-75-94.25-151.libero.it] has joined #launchpad [08:29] carlos, my feeling is that TranslationReview is going to land tomorrow, and therefore, there's no need to do work before that. If it's not landing tomorrow, well, we have a lot of chatting to do. === YoussefAssad [i=jassad@server1.freeshells.ch] has left #launchpad [] === dand [n=dand@dyn-85.186.137.18.tm.upcnet.ro] has joined #launchpad [08:55] New bug: #73519 in rosetta "Change translations to approved post membership acceptance to translation team" [Undecided,Unconfirmed] http://launchpad.net/bugs/73519 === lifeless [n=robertc@ppp245-86.static.internode.on.net] has joined #launchpad === aleka [i=aleka@24-75-199-158-st.chvlva.adelphia.net] has joined #launchpad === tonyyarusso [n=anthony@d235-240-148.home1.cgocable.net] has joined #launchpad [09:18] jordi: here [09:18] ok [09:18] so, tonyyarusso wants to learn more about our plans to support dialects [09:18] Indeed I do :) [09:18] tonyyarusso: just to have some background, I'm one of the main Catalan translators, [09:19] but, oh no! am Valencian [09:19] Otherwise I think the Elders will be at my throat... [09:19] so being able to produce ca@valencia translations easily from the existing ca translations would be rad [09:19] what's your usecase? === Spads [n=spacehob@host-87-74-89-151.bulldogdsl.com] has joined #launchpad [09:21] I'm not actually a speaker (yet), but am trying to get a translation effort started for Anishinaabe (Known in English as Ojibwe (various spellings). Also related to Odawa, Mississauga, and Cree, and less closely, Algonquin. [09:22] so you want to translate to Ojibwe, Odawa, etc. reusing as much as possible? [09:22] This is an indigenous language in Canada and the United States, I believe the 4th most spoken or so. [09:22] Actually, it's worse than that. [09:23] By some arguments Odawa is a dialect of Ojibwe, others say it's a separate language. Regardless, there are many dialects _within_ Ojibwe, on top of it's relations to other languages. [09:23] The amount of difference between things varies. [09:23] okay, complicated scenario it is :) [09:24] so what would you expect from rosetta? [09:24] The separate language/dialect line is fuzzy, but no matter how you slice it there is a huge number of subdivisions to be considered. [09:24] I'm trying to limit my scope: I won't worry about Cree or Algonquin, but probably include Odawa. [09:25] Given that, I need probably 5 or so dialects - lemme check my book here [09:25] https://blueprints.launchpad.net/products/rosetta/+spec/similar-languages [09:25] https://launchpad.net/products/rosetta/+bug/57925 [09:25]