[12:18] <dilys> Merge to<EMAIL_ADDRESS>[r=bradb]  bring in kiko's patch to fix a bug with the bugtask assignee widget, review it, make some slight tweaks and add a test (patch-2300<EMAIL_ADDRESS>[12:19] <kiko> don't I rock!
[12:51] <dilys> Merge to<EMAIL_ADDRESS>[r=BjornT]  Remove the svn_oo.EVIL_available_EVIL hack. Move svn_oo test helpers to a separate module and fix PEP8 compliance. (patch-105<EMAIL_ADDRESS>[12:55] <bradb> kiko: Do you mind if I wait until another merge to worry about engineering the change-to-tableview-with-one-line-of-code thing? I don't think it's particularly trivial anymore, given that the APIs are inevitable somewhat different (e.g. one has table headers, one does not, one has a notion of "listing columns", the other does not, etc.) Additionally, I've cut a huge amount of ZPT out of sourcepackage-bugs.pt, which should make twea
[12:55] <bradb> If I can worry about that later, I can get MaloneSearchResults into a review queue tonight.
[12:59] <bradb> I would almost create a separate template for the other kind of view, actually, to avoid hard-to-read ZPT full of conditions, which jumps through hoops to achieve the appropriate layout pattern for a listview vs. a tableview.
[01:02] <kiko> humm humm
[01:02] <kiko> you want to make me unhappy
[01:03] <lifeless> noone *wants* to make you unhappy
[01:03] <lifeless> it just happens
[01:03] <lifeless> ;0
[01:03] <kiko> brad, what if we made listing columns optional?
[01:04] <bradb> kiko: I don't want to make you unhappy. I'm more than happy to engineer it, it just means it doesn't land into a reviewer queue until tomorrow.
[01:04] <bradb> listing columns optional.../me ponders
[01:05] <kiko> well
[01:05] <kiko> what is the API for the listing view?
[01:05] <bradb> listing_columns, task_batch_navigator and mass_edit_allowed, approximately
[01:05] <bradb> oh, the listing view
[01:05] <kiko> right
[01:06] <bradb> while, right now it's only API'd at the row level, not at the whole table level
[01:07] <kiko> oh
[01:07] <bradb> because the sp bug listing formatting is different to what it will look like elsewhere
[01:07] <kiko> and what's the row API?
[01:07] <bradb> task
[01:07] <bradb> as might be expected
[01:07] <kiko> that's compatible :)
[01:10] <bradb> kiko: Like I say, I'm happy to engineer it to be a one line switch to turn a table view into a list and vice versa, but that means it doesn't end up into a reviewer queue until some point tomorrow, my time.
[01:11] <bradb> Alternatively, I can take a quick look through the diff right now and give it to BjornT to review
[01:12] <kiko> I still don't understand
[01:13] <kiko> you say the API is line-specific
[01:13] <kiko> and that API is compatible
[01:13] <kiko> you should be fine
[01:14] <bradb> kiko: What one line do you think you can change to get a table view? You'd have to change more than one line, as best I can tell.
[01:14] <elmo> is there anyway to see the currently excuting command in postgres?
[01:15] <bradb> elmo: psql -d launchpad_dev -c "select * from pg_stat_activity"
[01:15] <elmo> ah, nm, pg_stat_activity
[01:15] <elmo> bradb: thanks ;)
[01:15] <bradb> heh
[01:16] <bradb> ffs, baz has failed a ridiculous number of times today
[01:16] <bradb> even when all i have open is a gnome terminal
[01:16] <ddaa> lifeless: are you cleared to make code reviews?
[01:17] <ddaa> I'm finally untangling my cscvs branch, and I found I forgot to get a cleanup patch through the reviewers
[01:17] <kiko> bradb, you would, but that's okay -- when we /do/ make the listing view API we can accomodate.
[01:18] <bradb> ok, cool, I'll review the diff now then
[01:41] <dilys> Merge to<EMAIL_ADDRESS>[trivial]  sync with ddaa, no source code change (patch-106<EMAIL_ADDRESS>[01:52] <lifeless> ddaa: not on the team at the moment no.
[01:53] <kiko-zzz> I've checked in enough times today, I'm going to bed
[02:51] <Keybuk> lifeless: uh, you took away the "name location" form of baz register-archive ?!
[02:51] <lifeless> nope
[02:51] <lifeless> or rather - damn straight.
[02:52] <lifeless> you can register by location only
[02:52] <lifeless> if you can't connect, we don't believe you about the name, and if you can connect, the name is an error
[02:52] <Keybuk> so how do I register a pull mirror that already existed?!
[02:52] <Keybuk> or, for that matter, a push mirror?
[03:12] <lifeless> Keybuk: baz register-archive URL
[03:13] <Keybuk> how does that know whether it's the source or a new mirror?
[03:16] <lifeless> it probes it
[03:16] <lifeless> here, read up on ArchiveRegistration on the gnuarch.org wiki
[03:16] <lifeless> or look at ~/.arch-params/archives/foo@bar
[03:16] <lifeless> pull and push separation was bogus and removed
[03:17] <lifeless> there are now just copies of the archive, some of which are readonly and some of which are mirrors
[03:19] <Keybuk> URL?
[03:19] <Keybuk> it'd be nice to actually have that documented in the package, ya know
[03:19] <lifeless> yeah, and absolute or relative url. relative urls are file-system local.
[03:19] <Keybuk> no, I mean URL of the "ArchiveRegistration on the gnuarch.org wiki" page
[03:19] <lifeless> its documented 'register-archive location'
[03:19] <lifeless> oh.
[03:20] <lifeless> http://wiki.gnuarch.org/ArchiveRegistration
[03:20] <Keybuk> especially as that's somewhat contrary to the existing tla documentation
[03:20] <Keybuk> including the format of that file
[03:21] <lifeless> baz != tla
[03:21] <lifeless> that file is generally not edited by users, but if it is, it is fully documented on the wiki
[03:21] <Keybuk> right, but then on that basis baz is totally undocumented; and that's not a good thing for a project that's trying to get love
[03:22] <Keybuk> so I create a file like
[03:22] <Keybuk> []
[03:22] <Keybuk> URL=....
[03:22] <Keybuk> keywords=master
[03:22] <Keybuk> []
[03:22] <Keybuk> URL=...
[03:22] <Keybuk> keywords=
[03:22] <Keybuk> that means the second file is a mirror of the first?
[03:22] <Keybuk> second url, I mean
[03:22] <lifeless> uhm
[03:23] <lifeless> heres my rocketfuel archive file:
[03:23] <lifeless><EMAIL_ADDRESS>[03:23] <lifeless><EMAIL_ADDRESS>[03:23] <lifeless><EMAIL_ADDRESS>readonly priority=90
[03:23] <lifeless> when_unsigned=error
[03:23] <lifeless> [03:23] <Keybuk> that doesn't match anything like that wiki page you just gave me
[03:23] <Keybuk> that talks about "URL" and "keywords" keys
[03:23] <lifeless> look at 'sample file contents' on that wiki page
[03:24] <Keybuk> I did
[03:24] <lifeless> it does not say 'keywords keys' anywhere. it talks about keywork _parameters_
[03:24] <Keybuk> that seems to concur me
[03:24] <lifeless> parameter != key in ini files.
[03:24] <Keybuk> keywords is listed as a separate thing under "Valid sections and keys"
[03:24] <Keybuk> so I assumed it was a valid key
[03:24] <lifeless> its a subsection under URL.
[03:25] <lifeless> the style sheet doesn't make that clear, damn.
[03:25] <Keybuk> I'm trying to work out how I could change the gpg key for a given archive
[03:25] <Keybuk> and it's a bit of a mystery
[03:25] <lifeless> what do you mean by change the key - change policy, or resign the contents, or sign with a different key ?
[03:26] <Keybuk> sign with a different key
[03:26] <lifeless> gpg_options=--default-key foo
[03:26] <lifeless> gpg_options
[03:26] <lifeless> Defaults to empty. options to supply to gpg for signing of archive data. I.E. -q or --no-default-keyring --keyring ... gpg_options=[option ...]  Checking of signatures always uses your $GNUPGHOME configuration.
[03:26] <Keybuk> ok
[03:26] <lifeless> (from the wiki page ;0)
[03:26] <Keybuk> so url=.... gpg_options=--default-key foo ?
[03:26] <lifeless> no.
[03:26] <Keybuk> gah, you SUCK at docs, dude :p
[03:26] <lifeless> url=.... \n
[03:27] <lifeless> gpg_options=--default-key foo
[03:27] <lifeless> uhm, given the number of folk I know have read that page and got it right first time, in this case I'm not convinced the error is me ;0
[03:28] <Keybuk> can I get rid of my .arch-params/signing directory now?
[03:29] <Keybuk> it had a =default, =default.check file
[03:29] <Keybuk> and a bunch of -MIRROR rules
[03:29] <lifeless> run baz upgrade --move-old-config
[03:29] <lifeless> it will probe and upgrade all your info, and then yes you can
[03:29] <Keybuk> that didn't do anything
[03:29] <lifeless> then you are done,
[03:30] <Keybuk> baz still doesn't support ~/.arch-params/=ids does it?
[03:30] <lifeless> I thought I merged that to mainline, I may not have.
[03:30] <lifeless> brb
[03:30] <Keybuk> well, there's no -A for baz my-id
[03:30] <Keybuk> so I'd guess you didn't :p
[03:47] <dilys> Merge to<EMAIL_ADDRESS>[trivial]  Improve checkwatches spam (patch-2301<EMAIL_ADDRESS>[04:24] <jblack> lol.
[04:24] <jblack> we have three archives with pkgconfig in the name.
[04:31] <Alinux> hello , how can I add the new tamplates of a program, I mean how can I register a new program to translate?
[04:31] <Alinux> ?
[04:32] <jblack> That would be the rosetta guys...
[04:32] <jblack> daf: ping
[04:33] <jblack> I know one of them is daf, but here's not here right now. I'm not sure who else is on that team.
[04:33] <Alinux> must I send an e-mail?
[04:33] <jblack> Would you, please?
[04:33] <Alinux> jblack, ?
[04:33] <jblack> Yes? :)
[04:34] <Alinux> :) I'm not strong in english :) could you explane me better?
[04:35] <jblack> Do you know what a project in launchpad is?
[04:35] <jblack> .de german
[04:36] <Alinux> and another question, how often they update localization packages in apt repositories?
[04:36] <Alinux> yes I translate from italian and russian :) I use to :)
[04:36] <jblack> You would have to speak with daf, or one of the other rosetta members. I don't track rosetta very closely, I'm sorry to say.
[04:37] <Alinux> jblack, :) don't you worry... :) thank you a lot.
[04:37] <Alinux> ubuntu will the first distribution that speaks Georgian :)
[04:37] <jblack> Very nice!
[04:38] <Alinux> I'm translating right now gnome-panel :)
[04:38] <Alinux> Totem is finished :) gaim too,
[04:38] <jblack> To translate all of ubuntu... that's a big task
[04:38] <Alinux> started gnomemeeting and yelp :)
[04:38] <Alinux> jblack, yes I know...
[04:38] <jblack> Very good for a lot of people. I hope you're proud of your work. =)
[04:39] <Alinux> but translate main things..and global interface... is quite enough for the beggining :)
[04:39] <Alinux> jblack, ofcourse...
[04:40] <Alinux> we've started this projec to contras other big sorrow... http://microsoft.ugt.ge :(
[04:40] <stub> Alinux: At the moment you really need to talk to kiko, jordi or carlos. jordi and carlos are in Spain and kiko is in Brazil.
[04:41] <Alinux> :)
[04:41] <Alinux> no problem, I'll see them tomorrow :)
[04:41] <stub> Alinux: If you can't meet up with the timezones, you might need to use the mailing list - http://lists.ubuntu.com/mailman/listinfo/rosetta-users
[04:42] <Alinux> stub no problem , mainly I work at night :) so normally I meet them :)
[04:42] <jblack> Late Morning/Early afternoon, your time, is good to reach Jordi and Carlos. Late afternoon/early evening, again your time, is a good time to reach kiko.
[07:19] <dilys> Merge to<EMAIL_ADDRESS>[trivial]  More traversal fixes and tests (patch-2302<EMAIL_ADDRESS>[08:54] <SteveA> stub, spiv, BjornT: are we having a launchpad meeting today?
[08:54] <stub> We voted to suspend all future meetings because they are boring
[08:55] <stub> Or maybe my memory is playing tricks on me...
[09:38] <SteveA> morning scott
[09:39] <Keybuk> morning
[09:43] <wdamn> Morning, I'd like to install zope3 for helping with italian translation. I have debian and it tells me that there isn't the libc6 package: what can I do?
[09:46] <SteveA> wdamn: hello
[09:46] <SteveA> for developing launchpad (which uses various parts of zope3), we use ubuntu hoary, and compile zope3 from source
[09:46] <SteveA> so, i'm not sure how you'd get it working on debian
[09:46] <SteveA> try asking on #zope3-dev
[10:04] <carlos> morning
[10:05] <jamesh> hi carlos
[10:05] <carlos> jamesh, did you see my emails about daf's branches?
[10:05] <jamesh> carlos: yes.  You should have replies in your inbox
[10:05] <carlos> oh, ok
[10:05] <carlos> thanks
[10:06] <jamesh> carlos: for the languages admin, I think /rosetta/languages or /rosetta/+languages is probably better than /rosetta/language
[10:06] <jamesh> I mean /rosetta/+language
[10:06] <SteveA> hi carlos
[10:06] <SteveA> hi jamesh
[10:07] <carlos> jamesh, ok
[10:07] <carlos> SteveA, hi, how was your holidays?
[10:07] <SteveA> very good, thanks carlos
[10:08] <carlos> cool
[10:09] <carlos> jamesh, the use of +language was mark's choice
[10:09] <carlos> but I suppose we could name it as rosetta/languages
[10:10] <carlos> and use +language as a traversal URL just like +pots
[10:10] <SteveA> mark wants everything to move to a "singular noun" convention for "containment" or "namespacing"
[10:10] <carlos> or +sources
[10:10] <carlos> oh
[10:10] <SteveA> and to a "plural noun" arrangement for "look at an overview of these things"
[10:10] <SteveA> so, +languages for "let me look through all the languages"
[10:10] <carlos> so rosetta/+language
[10:10] <SteveA> and +language/en
[10:11] <carlos> ok
[10:11] <SteveA> for "the english language"
[10:11] <SteveA> do we have a spec on what launchpad URLs should look like?
[10:11] <carlos> SteveA, as jamesh says, we don't have conflicts at rosetta/ so should it be rosetta/languages or rosetta/+languages ?
[10:11] <jamesh> SteveA: that seems a bit weird if you see the container as the overview
[10:11] <SteveA> i guess it can go in the hackers faq
[10:11] <jamesh> (if you consider URL structure to have meaning)
[10:12] <SteveA> jamesh: i know.  but, mark very much does not consider the container as the overview
[10:12] <SteveA> the container can redirect to the overview
[10:13] <jamesh> carlos: okay then.  I guess /rosetta/language is probably best then (not using '+' because there is nothing to avoid conflicting with)
[10:14] <carlos> jamesh, so, rosetta/languages for the overview and rosetta/language/FOO for every language?
[10:15] <jamesh> carlos: I guess so.
[10:15] <carlos> ok
[10:16] <carlos> jamesh, thanks for all
[10:16] <jamesh> carlos: that'd mean make rosetta/language/+index a redirect to rosetta/languages, and make that page hang off IRosettaApplication
[10:16] <jamesh> you'd probably need to add a view class to get access to the ILanguageSet utility in that case
[10:17] <carlos> jamesh, yeah, that's exactly the behaviour we have with the +pots/ urls
[10:17] <carlos> the users are redirected to +translations
[10:18] <jamesh> I suppose you could avoid the extra view class by making the ILanguageSet utility accessible from IRosettaApplication directly
[10:21] <SteveA> actually...
[10:21] <SteveA> this can be done directly in the traversal function
[10:21] <SteveA> and will be supported when i land that navigation stuff RSN
[10:21] <carlos> jamesh, well, https://chinstrap.ubuntu.com/~dsilvers/paste/filegc1pnD.html is not so complicated....
[10:21] <carlos> That's what we use for +pots
[10:24] <jamesh> carlos: I was talking more about the /rosetta/languages page (which has IRosettaApplication as the context rather than ILanguageSet)
[10:25] <carlos> well, rosetta/languages' context is ILanguageSet so I think it should have a view for that context instead of reuse IRosettaApplication, right?
[10:26] <jamesh> ILanguageSet would be hooked up at "/rosetta/language" though, right?
[10:26] <jamesh> so "/rosetta/languages" would probably be a view on IRosettaApplication (/rosetta)
[10:26] <jamesh> unless I'm mistaken
[10:27] <carlos> hmmm
[10:27] <carlos> right
[10:28] <jblack> Ohhh. If I go to bed now, I could get a solid...
[10:28] <carlos> I got confused because the +pots and +translations pages use POTemplateSet and POTemplateSubset
[10:28] <jblack> how long until the meeting these days?
[10:28] <carlos> and this case is different
[10:28] <carlos> jblack, 3 hours and a half
[10:29] <jblack> that's 8am.
[10:29] <SteveA> stub: yay!  https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1242657&group_id=5470
[10:29] <jblack> Was hoping the old 9am time came back
[10:29] <SteveA> list() no longer swallows most exceptions
[10:29] <carlos> jblack, next month (I think)
[10:35] <jamesh> jblack: you could always try and get your state to switch to daylight savings year round
[10:35] <jblack> Pennsylvania?
[10:36] <jblack> I think the last thing that changed in pennsylvania was accepting daylight savings time!
[10:36] <sivang> lol
[10:36] <jamesh> I know some new zealanders want 1 hour daylight savings in the winter and 2 hours in the summer
[10:58] <WaterSevenUb> join #ubuntu-pt
[11:08] <koke> carlos: we already have the ubuntu-l10n-es mailing list :)
[11:08] <koke> is there any "magic" way to extract all the emails of the spanish translators from rosetta?
[11:09] <carlos> hmmm
[11:09] <carlos> not sure
[11:09] <carlos> salgado is your man there
[11:10] <carlos> koke, now that you talk about that... are you attending the translation team?
[11:10] <carlos> there are many people asking me to accept their request to join the team
[11:10] <carlos> so I did it
[11:10] <carlos> should I leave it to you now?
[11:11] <carlos> also, can I transfer the ownership of the team to you?
[11:11] <koke> hmm, I have it in my todo list
[11:11] <koke> :D
[11:11] <carlos> koke, If you are too busy... could you try to get someone else to help you?
[11:11] <carlos> the team can have more than one admin
[11:12] <koke> it would be a good idea too :)
[11:12] <koke> you asked another Jorge (aloriel ?) from the GTP, IIRC
[11:13] <koke> he was also interested but had not much time
[11:13] <niran> is there any work being done on getting debian package descriptions translated?
[11:13] <koke> but not much *2 maybe = enugh time ;)
[11:13] <koke> niran: talk to mvo, he was working on it
[11:14] <sabdfl> carlos: ^
[11:14] <carlos> niran, https://launchpad.net/products/ddtp-ubuntu/
[11:19] <carlos> koke, I asked, but he was not too sure he had enough time
[11:20] <jamesh> carlos: looks like +translations for the above URL is giving an error
[11:20] <jamesh> "SQLObjectNotFound: The object POSubmission by the ID 3970388 does not exist"
[11:21] <carlos> jamesh, yeah, I saw it already
[11:21] <carlos> that's weird
[11:21] <carlos> how is possible that we have a reference to a POSubmission that does not exists in our database?
[11:22] <jamesh> good question
[11:22] <jamesh> the db constraints should prevent it
[11:22] <carlos> right
[11:22] <carlos> no stub around...
[11:27] <sabdfl> Kinnison: ping
[11:28] <Kinnison> sabdfl: yo
[11:28] <carlos> niran, all descriptions are there, but due a bug seems like it's not available, I will try to fix it as soon as possible
[11:28] <sabdfl> carlos: it appears there is no Foreign Key on that one, which is a big screwup
[11:29] <carlos> really?
[11:29] <carlos> how is that possible?
[11:29] <carlos> :-(
[11:29] <niran> carlos, ok. the only questions i really had about it was whether those translations would make it to breezy, and in what form
[11:29] <carlos> sabdfl, oh!, you are right
[11:29] <carlos> we are missing the foreign key!
[11:30] <carlos> how could that happen?
[11:30] <niran> carlos, i.e. will it be integrated into apt, or will there just be a text file i can get the translations from for each package
[11:30] <carlos> niran, mvo is working on it
[11:30] <carlos> niran, he will handle that
[11:30] <carlos> niran, I think that apt will use them directly
[11:31] <niran> carlos, ok, thanks for the information
[11:31] <carlos> niran, I think it's a big file with all descriptions
[11:31] <carlos> that will be retrieved as Packages.gz is
[11:31] <carlos> with apt-get update
[11:31] <carlos> depending on your selected locale
[11:31] <sabdfl> kiko-zzz: ping when you're up
[11:38] <Keybuk> http://www.dilbert.com/comics/dilbert/archive/images/dilbert2005228920825.gif
[11:39] <carlos> stub, !
[12:01] <sabdfl> carlos: we need to not allocate karma when people are on imported po files
[12:01] <sabdfl> check the karma for Christian Rose
[12:03] <carlos> sabdfl, hmm, I think we do it only when it's not a 'published' import
[12:04] <sabdfl> carlos: ok. so the breezy import, which got that wrong, might be the reason for the huge data on christian rose?
[12:04] <carlos> hmm
[12:05] <carlos> no, that means that I'm wrong and we are giving karma always
[12:05] <carlos> sabdfl, anyway, why shouldn't we give karma? they are contributing too, right?
[12:06] <sabdfl> carlos: in many cases, they are just the last guy before the import, and other people did much of the work
[12:07] <sabdfl> karma should reflect the *use of launchpad*
[12:07] <carlos> ok
[12:08] <carlos> niran, https://launchpad.net/products/ddtp-ubuntu/+series/ubuntu/+translations
[12:08] <carlos> niran, it works now
[12:08] <carlos> stub, thank you for the fix
[12:08] <niran> carlos, thanks
[12:10] <sabdfl> stub: how did you fix the broken values?
[12:10] <stub> UPDATE POFile SET latestsubmission=NULL WHERE latestsubmission IS NOT NULL AND latestsubmission not in (select id from posubmission where id=pofile.latestsubmission);
[12:10] <stub> (which matched 33 rows)
[12:11] <sabdfl> stub: does it get cached when the pofile gets viewed next?
[12:11] <stub> Not my department I'm afraid ;)
[12:11] <sabdfl> carlos?
[12:12] <carlos> sabdfl, it gets cached when a new translation is submitted
[12:12] <carlos> sabdfl, that problem was a side effect of the whitespace fix
[12:12] <carlos> sabdfl, we removed some posubmissions
[12:12] <Keybuk> sabdfl: you really nice to sign the coc on lp.net :p
[12:13] <SteveA> carlos, stub: /msg me agenda items for the meeting
[12:13] <SteveA> Keybuk: will you be coming to the lp meeting?
[12:13] <Keybuk> SteveA: when is it?
[12:13] <SteveA> 12:00 UTC, for 45 mins
[12:13] <Keybuk> sure
[12:13] <Keybuk> that's 1h45 time right?
[12:14] <SteveA> yes
[12:30] <sabdfl> thanks stub
[12:32] <\sh> I'm not sure if this is the correct channel, but how do i register a "source-package-name" in malone?
[12:34] <carlos> \sh, you don't register it, it should be there if it belongs to Ubuntu
[12:35] <\sh> carlos: universe packages?
[12:35] <carlos> \sh, if it's not there, just tell it here or file a bug report against launchpad to add it
[12:35] <carlos> \sh, yes, most of them are there already
[12:35] <\sh> carlos: ok :) thx :)
[12:35] <carlos> \sh, np
[12:39] <WaterSevenUb> carlos: ahoy... What happens to the translations in Rosetta that are not translated up to 100%? Let us say... only 20%? Are they still used ?
[12:39] <carlos> shouldn't we, launchpad admins have rights to do anything on launchpad? I'm not able to close: https://launchpad.net/products/wordpress/+bugs/860
[12:39] <carlos> WaterSevenUb, yes
[12:40] <carlos> WaterSevenUb, but you will get partial translations
[12:40] <WaterSevenUb> carlos: ok:) thx.
[12:49] <dilys> Merge to<EMAIL_ADDRESS>[trivial]  Add missing foreign key constraint on POFile.latestsubmission (patch-2303<EMAIL_ADDRESS>[12:50] <WaterSevenUb> carlos: following BreezyReleaseSchedule... After 6th October only there is the chance of checking the translation of the distribution as a whole.... No language packs will be regenerated until 13th October so the errors found meanwhile will not be corrected? I know that there are frequent updates for the translations, but is much better if the errors are corrected in the clean install with no network. If the errors are not corrected, a dea
[12:50] <WaterSevenUb> dline of 8th October for translation corrections and regeneration of langpacks would be great. Did I make any sense at all? :)
[12:52] <carlos> WaterSevenUb, I don't know that plannification, pitti is your man for that
[12:55] <carlos> WaterSevenUb, he's at #ubuntu or #ubuntu-devel
[12:57] <WaterSevenUb> carlos: ok
[01:47] <Alinux> language-pack-ka is packaged by Martin Pitt, so how often he updates the translations ftom launchpad?
[01:47] <Kinnison> SteveA: meeting in 13m yes?
[01:47] <SteveA> yes
[01:48] <carlos> Alinux, it's supposed to be done once per month
[01:48] <Alinux> ah good
[01:49] <Alinux> and what mean this? "Translation unchanged since last synchronized"
[01:49] <Alinux> green line...
[01:50] <carlos> Alinux, that means that those translations are the same that upstream has
[01:50] <Alinux> mmm upstream?
[01:50] <carlos> so thre was no change at all from Rosetta
[01:50] <Alinux> so they are packeged allredy?
[01:50] <carlos> or the changes done in Rosetta were already sent to maintainers
[01:50] <carlos> yeah
[01:50] <Alinux> and are they in repository?
[01:50] <carlos> Alinux, but it does not means they are in language pack yet
[01:51] <Alinux> ah
[01:51] <carlos> Alinux, it's more related about GNOME or GNU projects directly
[01:51] <carlos> more than Ubuntu itself
[01:52] <Alinux> and how do I know, if package is packeged or not?
[01:53] <carlos> we don't have an easy way to know that, sorry
[01:53] <Alinux> so when I translate for Ubuntu, I translate GNOME packacage generally
[01:53] <jamesh> Alinux: once the Ubuntu package repository is imported, there will be links between source packages and upstream products
[01:53] <Alinux> so I contribute not only for GNOME you mean?
[01:54] <Alinux> jamesh, I need some FAQ about Launchpad :) Some things are not clear to me :)
[01:54] <carlos> Alinux, right, but you should send those changes manually upstream (to GNOME )
[01:54] <carlos> Alinux, https://wiki.ubuntu.com/RosettaFAQ
[01:54] <carlos> Alinux, feel free to send any question you are missing there to<EMAIL_ADDRESS>[01:54] <carlos> Alinux, he will add it with the answer
[01:55] <Alinux> so for example I've translated gdm or Totem package for Ubuntu,
[01:55] <jamesh> Alinux: there are parts of Launchpad that aren't running on the production server right now (the Ubuntu repository watching is one example)
[01:55] <Alinux> and will be present the same translation into gnome for debian (for example)?
[01:56] <carlos> Alinux, only if debian maintainers get the translations from Ubuntu
[01:56] <jblack> meeting coming up in a couple moments, right?
[01:56] <carlos> jblack, 4 minutes
[01:58] <Alinux> boys :) I've translated totem and gnome-panel, but for hoary :) will be imported something in breezy?
[01:59] <Alinux> :) if not ,I would like to transloate only for Breezy is it possible?
[01:59] <kiko-zzz> T1 minute
[01:59] <kiko-zzz> err
[01:59] <kiko-zzz> T-1 minute
[02:00] <kiko-zzz> SteveA!
[02:00] <Alinux> https://launchpad.net/distros/ubuntu/hoary/+lang/ka  here translations for Hoary, I hope that it helps Breezy too :)
[02:00] <jblack> I've come down with alzheimers. What channel?
[02:00] <kiko> jblack, #wakeupjblack
[02:00] <SteveA> MEETING TIME!
[02:00] <SteveA> who's here?
[02:00] <bradb> me
[02:00] <spiv> me
[02:00] <jblack> me
[02:00] <BjornT> me
[02:00] <jamesh> me
[02:00] <salgado> I'm here
[02:00] <stub> yo
[02:00] <morgs> me
[02:00] <lifeless> not me
[02:00] <kiko> as always
[02:01] <SteveA> carlos: ?
[02:01] <carlos> Alinux, you will see it as suggestions, until we implement a new feature to migrate all translations automatically from one release to another. Now is meeting time, we could talk later.
[02:01] <carlos> SteveA, yes
[02:01] <carlos> sorry
[02:01] <SteveA> ddaa: ?
[02:01] <dePOLL> hey guys. not really a launchpad-question but what exactly is an "upstream alioth package" (as seen here: https://launchpad.net/distros/ubuntu/+bugs/331/+index) resp. where do i get it? :)
[02:01] <SteveA> anyone else from brazil?
[02:01] <SteveA> okay, here's today's agenda
[02:01] <kiko> cprov is travelling
[02:01] <Kinnison> celso might be preparing to travel
[02:01] <Kinnison> snappish!
[02:01] <SteveA> == Agenda ==
[02:01] <SteveA>  - roll call
[02:01] <SteveA>  - agenda
[02:01] <SteveA>  - next meeting
[02:01] <SteveA>  - activity reports (SteveA)
[02:01] <SteveA>  - bzr status, london sprint dates and people (lifeless)
[02:02] <SteveA>  - production / staging / dogfood (stub, Kinnison)
[02:02] <SteveA>  - new spec system (SteveA)
[02:02] <SteveA>  - shipit branding (SteveA, mpt)
[02:02] <SteveA>  - test suite (Kinnison)
[02:02] <SteveA>  - packaging database changes (Kinnison)
[02:02] <SteveA>  - menu system (SteveA, kiko, mpt)
[02:02] <SteveA>  - three sentences
[02:02] <SteveA>
[02:02] <SteveA> this is a long agenda, so we need to keep items brief
[02:02] <SteveA> hi cprov
[02:02] <SteveA> next meeting -- same time next week?
[02:02] <kiko> yes
[02:02] <Kinnison> yes
[02:02] <carlos> yes
[02:02] <cprov> yes
[02:02] <spiv> dePOLL: http://alioth.debian.org/ probably.
[02:03] <cprov> SteveA: hi, a bit late, sorry
[02:03] <SteveA> activity reports: who's up to date and who's behind?
[02:03] <spiv> Predictable times are good.
[02:03] <kiko> behind
[02:03] <jamesh> behind
[02:03] <SteveA> kiko: how far?
[02:03] <Kinnison> behind due to crapness
[02:03] <SteveA> jamesh: how far?
[02:03] <lifeless> up to date
[02:03] <spiv> I'm up to date (just did the traditional pre-meeting catch-up... :/ )
[02:03] <SteveA> Kinnison: how far?
[02:03] <stub> uptodate
[02:03] <ddaa> oops
[02:03] <Kinnison> SteveA: about two weeks. I have the notes, but haven't formalised them into reports
[02:04] <dePOLL> spiv: I went there but couldn't find what i was looking for :/
[02:04] <ddaa> updateto
[02:04] <jblack> up to date
[02:04] <Kinnison> SteveA: I can either spam the list, summarise, or restart
[02:04] <Alinux> ok carlos :) thank yuo :)
[02:04] <SteveA> Kinnison: send the notes to the list, and restart
[02:04] <Kinnison> SteveA: okay
[02:04] <dePOLL> but it's not a launchpad issue and i notice, i'm rather a disturbance here :) thx anyway.
[02:04] <jamesh> SteveA: too long.  I'll restart and send a summary.
[02:04] <kiko> SteveA, so long I can't see the horizon
[02:04] <SteveA> dePOLL: hi.  we're having our weekly 45 minute developer meeting.  maybe ask again in 40 mins?
[02:05] <bradb> i'm up to date
[02:05] <SteveA> kiko: start again?
[02:05] <carlos> dePOLL, just come in an hour or so, the meeting will be finished
[02:05] <SteveA> jamesh: okay
[02:05] <kiko> SteveA, it's the only way
[02:05] <dePOLL> Alright, thanks guys.
[02:05] <SteveA> did i miss anyone?
[02:05] <SteveA> okay, lifeless: bzr status and london sprint
[02:06] <lifeless> in reverse order, I'm in london 4th through 17th september
[02:06] <lifeless> the first week with ddaa and sabdfl, the second with keybuk & neimeyer
[02:06] <lifeless> bzr dogfooding for rocketfuel is moving along
[02:06] <kiko> lifeless, have you coordinated with niemeyer since?
[02:06] <lifeless> http://bazaar.canonical.com/CanonicalBzrDogfooding
[02:07] <lifeless> kiko: yes
[02:07] <kiko> lifeless really wants to avoid that pie
[02:07] <jblack> I'm not going?
[02:07] <jblack> 4th sept. guess not.
[02:07] <lifeless> jblack: no, its not a team sprint, its two focused sprints
[02:08] <lifeless> bzr still has some way to go, but I'm confident of avoiding that pie ;0
[02:08] <kiko> carlos, congrats on tracking down the pofile newline issue
[02:08] <lifeless> I've just finished step 1 in my tree ;0
[02:08] <SteveA> cool
[02:09] <ddaa> jblack: I'm not there for the second week, and the first week is mostly sabfl wanting to get me started on my launchpad work
[02:09] <carlos> kiko, I detected a bug that still causes it so it's not fixed :-(
[02:09] <SteveA> i'd like to move along
[02:09] <SteveA> okay lifeless ?
[02:09] <lifeless> done
[02:09] <SteveA>  - production / staging / dogfood (stub, Kinnison)
[02:09] <SteveA> Kinnison: next dogfood update?
[02:09] <Kinnison> dogfood hasn't been updated in a week or so. I've been concentrating on other things (see later in the agenda)
[02:09] <Kinnison> as always, if anyone wants me to update anyway, let me know
[02:09] <SteveA> anyone have a problem with that?
[02:09] <kiko> Kinnison, what of the gina run on production?
[02:10] <Kinnison> kiko: Now that I've finished the db rework, I can go back to the publisher work. gina on production is still held up by the gpg import
[02:10] <SteveA> i thought jamesh was going to be working on the gpg import tool
[02:10] <stub> Dogfood is Kinnison's toy for the time being - I don't see any point bringing it up at meetings unless that status changes.
[02:12] <jamesh> SteveA: I've got code to work out the email address clusters from the signatures on uids of keys.  It still needs a bit more testing, and the code to do the account merging and adding email addresses
[02:12] <kiko> jamesh, I would be really happy if you made that priority minus zero
[02:12] <SteveA> stub: production / staging?
[02:13] <stub> Staging is as usual (daily updates going fine in general).
[02:13] <stub> Production is as usual (I'll tag from rocketfuel as-start-of-meeting unless anyone is landing anything that needs to go out today or tomorrow, and roll out Tuesday)
[02:14] <kiko> stub, carlos will have at least one update
[02:14] <SteveA>  - new spec system (SteveA)
[02:14] <SteveA> mark's been working on a new spec system for integration with launchpad
[02:14] <SteveA>  - spec adding, linked to products or distros
[02:14] <SteveA>  - edit, admin pages
[02:14] <SteveA>  - review workflow, you can request a review from someone and they can clear the review request when they have done it
[02:14] <SteveA>  - specs can be targeted to milestones and show up on the milestone page along with bugs targeted to the milestone
[02:14] <SteveA>  - you can have spec subscriptions
[02:14] <stub> If the GPG tool is going to merge accounts, we don't have to necessarily delay the Gina run for it.
[02:14] <SteveA>    (all that means is you can see the spec on your personal pages)
[02:14] <SteveA>  - linking specs to bugs
[02:14] <SteveA>  - spec dependencies, showing a dependency tree
[02:14] <SteveA>  - calculation of a recommended project plan for the distro / product based on spec priority and dependencies
[02:14] <SteveA>
[02:14] <SteveA> mark says it does all these things.
[02:14] <SteveA> kiko, mark will be pinging you to review it later today.
[02:15] <carlos> SteveA, is that implemented already???
[02:15] <carlos> wow
[02:15] <SteveA> it still needs integrating with karma, and also into branches (when the branch work is landed)
[02:15] <kiko> wow
[02:15] <carlos> sabdfl, you are THE man
[02:16] <SteveA> mark plans to work on the support request tracker next
[02:16] <SteveA>  - shipit branding (SteveA, mpt)
[02:16] <SteveA> mpt has some concerns about how shipit will be branded
[02:17] <kiko> indeed he does
[02:17] <SteveA> i spoke with mark about this earlier today
[02:17] <mpt> That was a combination of several mistakes, mostly mine
[02:17] <SteveA>  - shipit will be branded standalone
[02:17] <kiko> hah
[02:17] <SteveA>  - you'll be able to view your requests from inside launchpad
[02:17] <kiko> SteveA, hosted at shipit.ubuntu.com as well?
[02:18] <SteveA> sure, we can do that
[02:18] <SteveA> we need to work out the details still
[02:18] <SteveA> but these are the high-level goals
[02:18] <stub> Is it a problem if shipit lives under /distros/ubuntu ?
[02:18] <kiko> it will require a skin and running the shipit skin on a vhost
[02:18] <SteveA> stub: it will be a crappy url
[02:18] <mpt> I overguessed the maintainability of the current code, there is no ShipIt spec on the LP wiki, salgado didn't know the rationale, I didn't go ask kiko the rationale before mailing the list first, etc
[02:18] <SteveA> kiko: yep.  we have the tech for it.
[02:19] <jamesh> stub: if "shipit for ubuntu" is under /distros/ubuntu, that doesn't seem a problem
[02:19] <SteveA> we can add a special "facet" for ubuntu, for example
[02:19] <SteveA> or some other application menu
[02:19] <kiko> that we could
[02:19] <SteveA> moving on...
[02:19] <mpt>  /distros/ubuntu/+shipit, /people/mpt/+shipit, /products/firefox/+shipit
[02:20] <SteveA>  - test suite (Kinnison)
[02:20] <Kinnison> Over the past two weeks I've been using the test suite a lot
[02:20] <Kinnison> at various times, I've encountered issues which I'd love to see resolved, but I don't understand how to fix them myself
[02:20] <Kinnison> the two major ones are:
[02:21] <Kinnison> When starting a subprocess (E.g. build slave, librarian etc) if it fails, it's not obvious what the error was
[02:21] <Kinnison> It'd be really nice if we could have the test suite have an option to stop on the first failure
[02:21] <kiko> yeah
[02:22] <Kinnison> My cursory glance through the code couldn't spot how to do those, but someone with more knowledge of the test system should be able to do them
[02:22] <Kinnison> ddaa: a stable ordering is sufficient
[02:22] <SteveA> i think there's an option for it already
[02:22] <lifeless> ddaa: begone that foul meme forsooth
[02:22] <Kinnison> SteveA: noone could tell me it when I asked (several times)
[02:22] <SteveA> but, we may want to switch to marius's testrunner anyway
[02:22] <lifeless> unittest has that built in, just most testrunners don't use it
[02:23] <SteveA> so, i'd like to nominate spiv and stub to look into improving the test running
[02:23] <stub> Kinnison: For your first issue, do you mean 'if the fixture fails it is not obvious' or 'My test runs buildd and it fails, but I don't know why the test is failing' ?
[02:23] <ddaa> Kinnison: maybe you want to look at OrderedTestLoader in pybaz. That tries to use source code ordering. SteveA had a problem with it where inspect were breaking in weird symlink situations. Oh and lifeless thinks that crack, but I'll pay attention when he knows how to layout code :P
[02:23] <SteveA> lifeless: dude, you
[02:23] <SteveA> lifeless: dude, you're busy with bzr and avoiding pie
[02:23] <lifeless> I've just partly redone two other test runners. Might be able to help ;)
[02:23] <spiv> Kinnison: Hmm, the LibrarianTestSetup harness already tries to detect when it doesn't fail, and the code looks sane.
[02:24] <spiv> lifeless would be extremely valuable here.
[02:24] <Kinnison> stub: I mean that you don't get to see why the fixture fails to load
[02:24] <SteveA> lifeless: by all means *consult*, just don't do any work on it ;-)
[02:24] <Kinnison> stub: although this might be a buildd slave only issue, I dunno
[02:24] <spiv> He knows the design of xUnit inside and backwards with his eyes closed while standing on his head.
[02:24] <Kinnison> Anyway, can we discuss this outside of the meeting please?
[02:24] <Kinnison> SteveA asked me to keep it short
[02:24] <Kinnison> ;-)
[02:24] <spiv> I've been trying to absorb bits of this by osmosis recently ;)
[02:25] <lifeless> SteveA: ok ;). once I've avoided pie I'd like to work on it though ;)
[02:25] <SteveA> spiv, stub, lifeless (consulting) -- okay with this?
[02:25] <lifeless> I am happy with that.
[02:25] <spiv> I'm happy to work on this.
[02:25] <SteveA> it means you're in the same TZ too
[02:25] <spiv> A pleasant change :)
[02:25] <SteveA> report back at the next LP meeting
[02:25] <SteveA> stub: ?
[02:26] <SteveA> please also talk to mgedmin.  he has a test runner that he wants to merge into the zope3 one
[02:26] <SteveA>  - packaging database changes (Kinnison)
[02:26] <Kinnison> Okay, again a short one.
[02:26] <stub> I'm not sure there is any sort of magic bullet for improving the fixtures (I'm not familiar with the buildd one).
[02:26] <Kinnison> I've been working on moving a bunch of stuff in the packaging tables around
[02:26] <Kinnison> in particular, BinaryPackage is now called BinaryPackageRelease and the publishing tables for binaries and sources are more consistently named
[02:27] <stub> SteveA: I have been discussing this with Jim on Zope-dev. There is a new test runner almost ready to merge into the Z3 and Z2 trunks.
[02:27] <Kinnison> This is likely to have collateral fallout around the app which the test suite and my own eyeballing hasn't caught yet
[02:27] <Kinnison> I have put my branch up for review, it's in jamesh's queue but if another reviewer wants to take it and do it quickly I won't complain
[02:27] <Kinnison> I will merge it as soon as I can, at that point I'd appreciate it if each of you would check your parts of the app which interact with the packaging stuff to make sure it still works
[02:28] <Kinnison> (add tests to catch a repeat failure :-)
[02:28] <Kinnison> If you want to get a head-start on looking, you can merge<EMAIL_ADDRESS>[02:28] <Kinnison> that is all
[02:29] <SteveA> Kinnison: please put up a wiki page specifically for this, where people can check off the part of the app they've done.
[02:29] <SteveA> i'm concerned that nothing in particular will happen
[02:29] <SteveA> and we need a way to track what's been checked and works, or has been fixed, or whatever
[02:30] <Kinnison> I will do that today, thanks
[02:30] <SteveA>  - menu system (SteveA, kiko, mpt)
[02:30] <SteveA> we need to start https://wiki.launchpad.canonical.com/LaunchpadMenusDelivery
[02:31] <kiko> Kinnison, what points interact with this side of the packaging system?
[02:31] <SteveA> particularly, i have a bunch of menus system bugs to fix / updates to make
[02:31] <Kinnison> kiko: In theory anything which cares about binary packages at all, or anything which might look into the publishing tables
[02:31] <kiko> Kinnison, only soyuz, really.
[02:31] <SteveA> and we need to get the "actions portlet" converted to use menus
[02:31] <kiko> correct
[02:32] <kiko> mpt has produced a layout change mandated by the sab
[02:32] <kiko> that will also need review and merging
[02:32] <kiko> I'm not particularly fond of it because I also think it's a bit short-sighted
[02:32] <Kinnison> kiko: and anything in malone which looks at packages in distros, and anything in rosetta which does the same, etc.etc.
[02:32] <Kinnison> kiko: bits of foaf look at packages in distros
[02:33] <SteveA> mpt: can you and i spend a set time each day working on menus implementation?
[02:33] <kiko> Kinnison, AFAIK all the ties are done using the package names, but okay
[02:33] <mpt> SteveA: sure
[02:33] <SteveA> mpt: what time works for you (utc?)
[02:33] <Kinnison> kiko: better safe than sorry
[02:33] <mpt> SteveA: 1pm?
[02:33] <SteveA> 1pm UTC for 1 hr
[02:33] <kiko> Kinnison, yeah, just wanted to check if you had considered that side of it
[02:34] <mpt> ok
[02:34] <SteveA> mpt: we'll keep it up until the menus system works completely and smoothly
[02:34] <SteveA> any other items before we do the three sentences
[02:34] <bradb> two questions:
[02:35] <bradb> 1. (Same as last week) What are the remaining specs to be delivered for Malone 1.0, and by what date?
[02:35] <bradb> (I did a lot of wiki gardening to make it easy to see the overview of what's all there, and what its status is.)
[02:35] <kiko> great
[02:36] <ddaa> BTW
[02:36] <kiko> bradb, will advise. what's the second question?
[02:36] <ddaa> kiko: I received no response from you about my list of Registry blockers. Was there a problem?
[02:36] <bradb> And 2. I got the impression at the end of .br that we were going to move forward with the google suggest widget, but that seems to remain stalled. Are we working on the google suggest widget right now?
[02:37] <SteveA> the month after brazil was meant to be a bugfixing month
[02:37] <kiko> ddaa, no, it's still waiting to be looked at
[02:37] <kiko> bradb, we're not working on it, no.
[02:37] <SteveA> bradb: so, it isn't surprising that we're not going to be moving forward with it at the moment
[02:37] <SteveA> we're definitely going to be improving the current pop-up thing
[02:38] <kiko> IIRC the suggestion was for jamesh to work on it (but IMBW)
[02:38] <spiv> The google suggest widget is supposed to be in my hands, but yeah, I've been busy with bugs.
[02:38] <kiko> ah, spiv
[02:38] <SteveA> we may be developing a more advanced JS based system, based on paul sladen's prototype, a bit later
[02:38] <spiv> kiko: IIRC it was me, but IMBW too ;)
[02:38] <SteveA> it isn't a priority
[02:39] <jamesh> spiv: I can help look at it after I've cleared some other stuff off my plate
[02:39] <bradb> that's all from me, thanks
[02:39] <SteveA> so, let's look at the clearness of plates next week, and see where we are
[02:39] <SteveA> anything else?
[02:39] <spiv> jamesh: Cool.
[02:39] <SteveA> thanks ddaa.  let the sentences begin!
[02:39] <spiv> ddaa: Enjoy!
[02:40] <mpt> DONE: cleanup of Malone search results, products/projects, ShipIt design
[02:40] <mpt> TODO: Rosetta 1.0 polish, TranslationReview, bug-fixing
[02:40] <mpt> BLOCKED: nothing in particular
[02:40] <bradb> DONE: Lots of wiki gardening to update Malone specs and add missing ones. Landed fmt:approximateduration. Landed BugTaskAssigneeWidget. Landed IBugTask.context* => .target* renaming. Got portlet mania into review queue. Got MaloneSearchResults into review queue. Started work on BugAndTaskPageURLs. Pain.
[02:40] <lifeless> DONE: leave
[02:40] <spiv> DONE: Code reviews as always, bug 1585, bug 1785, Twisted sprint (leave), booked flight to .ca
[02:40] <spiv> TODO: Test suite unsucking, code reviews, TeamLogin, SupermirrorFilesystemHierarchy.
[02:40] <spiv> BLOCKED: No.
[02:40] <ddaa> DONE: lots of cscvs cleanups, cscvs nested log parsing (blocking python import)
[02:40] <ddaa> TODO: get nested log parsing rolled-out and reviewed, flush my various queues of pending patches
[02:40] <ddaa> BLOCKED: NukeChangesetFile, cannot type with right pinky. On leave next week, then sprint.
[02:40] <bradb> TODO: Portlet mania and MaloneSearchResults reviewer nagging/landing. BugAndTaskPageURLs agony. Malone menus. Continuning the fight against feeping creaturism.
[02:40] <BjornT> DONE: implemented MaloneKarma. implemented DistroreleaseCVEReport. almost finished making notifications threadable. reviews.
[02:40] <lifeless> TODO: bzr usefulness
[02:40] <bradb> BLOCKED: (Only on myself; MaloneMenus is blocked by BugAndTaskPageURLs implementation.)
[02:40] <BjornT> TODO: finish threadable notifications. coordinate with brad and kiko about remaining malone 1.0 tasks. reviews. fix bug in email wrapping.
[02:40] <lifeless> BLOCKED: hours in day
[02:40] <cprov> DONE: ABUI spec implementing and buildd fixes, review buildd and soyuzUI
[02:40] <cprov> TODO: buildd sprint in UK
[02:40] <cprov> BLOCKED: none
[02:40] <BjornT> BLOCKED: no
[02:40] <kiko> DONE: Malone bug triage and fixing, Rosetta release management
[02:40] <kiko> TODO: Release Rosetta 1.0, Triage Malone 1.0, Triage Registry 1.0
[02:40] <kiko> BLOCKED: Carlos keeps finding issues in the language pack exports!
[02:40] <salgado> DONE: basic-voting--1, ShipItNG, code review, random fixes
[02:40] <salgado> TODO: ShipItNG, code review, merge person-edit and basic-voting--1
[02:40] <salgado> BLOCKED: Nothing
[02:40] <jblack> done: community, imports
[02:40] <carlos> DONE: Language packs, daf's branches work, user support, debug
[02:40] <jblack> TODO: community, imports, supermirror
[02:40] <jblack> BLOCKED: None
[02:40] <jamesh> DONE: more work on gpg thingee, some lp-int work, respond to review comments, code reviews
[02:40] <jamesh> TODO: finish off gpg thingee, code reviews
[02:40] <jamesh> BLOCKED: no
[02:40] <carlos> TODO: More language packs, bug fixes, improve my performance
[02:40] <Kinnison> DONE: db rework
[02:40] <Kinnison> TODO: back to publisher
[02:40] <Kinnison> BLOCKED: none
[02:40] <stub> DONE: Drive by bug fixing, prodution staging and dba stoof
[02:40] <stub> TODO: test suite work
[02:40] <stub> BLOCKED: Nothing
[02:40] <SteveA> DONE: vacation
[02:40] <SteveA> TODO: management, menus delivery, code review
[02:40] <SteveA> BLOCKED: no
[02:41] <carlos> BLOCKED: no
 BLOCKED: (Only on myself; MaloneMenus is blocked by BugAndTaskPageURLs implementation.)
[02:41] <morgs> DONE: small fixes
[02:41] <morgs> TODO: clarify role
[02:41] <morgs> BLOCKED: none
[02:41] <SteveA> bradb: what's up with the URLs implementation?
[02:41] <bradb> SteveA: The "bug page" context is turning into an IBugTask, which breaks everything on that page.
[02:41] <bradb> Hence the word "pain".
[02:42] <SteveA> is it blocked on someone other than you?
[02:42] <bradb> "Only on myself", so no. :)
[02:42] <SteveA> okay.  do you know exactly what you need to do?
[02:42] <bradb> Yes.
[02:43] <SteveA> cool
[02:43] <bradb> (It was mainly a note to others about what order I'm doing thigns in and why.)
[02:43] <SteveA> so, anyone else blocked that i missed?
[02:43] <SteveA> hi jordi
[02:43] <jordi> weird, my irc client didn't join to a bunch of channels
[02:43] <jordi> hi guys
[02:43] <SteveA> okay.  1 minute left... any last points?
[02:43] <jordi> is it magic lines time for me?
[02:43] <SteveA> kiko: next code reviewers meeting?
[02:43] <jordi> SteveA: nice to see you back
[02:43] <SteveA> jordi: go for it
[02:44] <jordi> actually, I guess you're not so glad, but anyway
[02:44] <kiko> SteveA, how about next wednesday?
[02:44] <SteveA> jordi: i'm really happy.  vacation got boring.
[02:44] <SteveA> kiko: ok, what time?
[02:44] <jordi> d'oh
[02:44] <ddaa> "idleness is like rich food, you only value it when you do not have enough of it"
[02:44] <lifeless> I luxuriated ;0
[02:44] <kiko> SteveA, 12UTC?
[02:45] <SteveA> antipodeans -- ?
[02:45] <jamesh> 12UTC is fine for me.
[02:45] <carlos> bradb, me too, if I'm alone :-)
[02:45] <SteveA> BjornT: ?
[02:45] <spiv> 1230 UTC as usual would suit me a little better on Wednesdays.
[02:45] <Kinnison> Are we done?
[02:45] <jamesh> 13UTC too
[02:45] <SteveA> we're done
[02:45] <BjornT> SteveA, kiko: works for me
[02:45] <jordi> DONE: email processing, replying to half of them, importing several requests, wiki page for new import queue method, new rosetta bugs filed. (Been out last week, had to catch up during the last two days)
[02:45] <kiko> 13UTC is fine
[02:46] <SteveA> we can arrange the exact time after the meeting
[02:46] <carlos> SteveA, thanks
[02:46] <SteveA> MEETING ENDS
[02:46] <SteveA> oh, jordi, you can keep going ;-)
[02:46] <siretart> hi
[02:46] <ddaa> spiv: thanks, but that's not vacation for fun. That's vacation for renting a flat and moving furniture :-/
[02:46] <siretart> does a wiki admin happen to be here?
[02:46] <SteveA> kiko, BjornT, spiv, jamesh, salgado: 13 UTC, wed ?
[02:46] <jamesh> SteveA: sure.
[02:46] <BjornT> SteveA: sure
[02:46] <spiv> ddaa: Oh, shame :(
[02:47] <salgado> SteveA, ok
[02:47] <siretart> I mean for wiki.ubuntu.com, who should I contact?
[02:47] <carlos> siretart, which wiki?
[02:47] <spiv> SteveA: Ok, but it'll need to be fairly brief -- that's 11pm my time.
[02:47] <jordi> BLOCKED: Sime System errors (repoprted) prevent me of doing some requests, permission problems (reported) prevent me of doing changes to teams, creating them, etc.
[02:47] <carlos> siretart, I suppose<EMAIL_ADDRESS>[02:47] <kiko> SteveA, yea
[02:47] <jamesh> siretart: what sort of problem is it?
[02:47] <spiv> But they generally aren't marathon meetings, so that should be ok.
[02:48] <SteveA> jordi: have your bugs been accepted?
[02:48] <siretart> jamesh: just a feature request: interwiki's to ubuntu bugzilla, wiki.debian.net and debian bts
[02:48] <jordi> TODO: finish replying to pending -user/privates email, pending requests. Start using the wiki-based importqueue
[02:48] <SteveA> jordi: are they all things that carlos knows about and can fix?
[02:48] <carlos> jordi, just say... blocked by carlos' lack of two extra hands :-P, I will try to mute
[02:48] <kiko> siretart, sounds like webmaster@ stuff
[02:48] <siretart> kiko: ok
[02:48] <carlos> SteveA, I think so, yes
[02:48] <jordi> carlos: sorry :P
[02:48] <SteveA> carlos: make sure these get reviewed by someone as a priority, when you've made the fixes
[02:48] <jordi> I can gety you plastic hands.
[02:48] <carlos> SteveA, sure
[02:48] <jordi> No mobility or anything, but...
[02:49] <jordi> my netwrok provider is being naughty today
[02:49] <jordi> loading webpages takes ages
[02:49] <carlos> jordi, perhaps a brain link with my computer is enough :-)
[02:49] <carlos> ok, see you later
[02:49] <jamesh> siretart: if you're sending in a request, ask for a malone interwiki link too :)
[02:49] <jordi> SteveA: all except 1 is New
[02:49] <siretart> jamesh: ah, sure!
[02:50] <jamesh> siretart: "https://launchpad.net/malone/bugs/" as the prefix
[02:51] <mpt> ... for now :-)
[02:51] <mpt> (well, I guess that will always work, though where it redirects you will change)
[02:52] <jordi> SteveA: https://launchpad.net/people/jordi/+reportedbugs
[03:00] <kiko> lifeless, ping?
[03:02] <lifeless> kiko: pong
[03:02] <kiko> lifeless, would you entertain changing the PQM email to include some information on who requested the merge in the header?
[03:03] <lifeless> kiko: sure, you mailed me and its on my queue somewhere
[03:03] <kiko> ah, okay. maybe I could produce a patch?
[03:03] <lifeless> best bet is to file a bug on pqm in launchpad
[03:03] <lifeless> better yet, file a bug with a patch ;0
[03:03] <lifeless> :)
[03:03] <kiko> sure
[03:03] <mpt> SteveA: menus?
[03:03] <lifeless> but, that part of pqm is still pure-inherited-crack, so bewarned
[03:04] <kiko> mpt, he went for food but would brb
[03:04] <mpt> is brb enough time to look at AutoBuilds, cprov?
[03:04] <kiko> maybe
[03:05] <cprov> mpt: few minutes, probably 10 ...
[03:05] <kiko> do it
[03:05] <mpt> cprov: You're still committing?
[03:06] <mpt> jblack: around?
[03:06] <cprov> mpt: commiting, applying review, setting up buildfarm, etc ;)
[03:06] <kiko> salgado, bradb-bbl, BjornT: how about if we move all the personal bug reports (including malone/+assigned) to be under the person's page?
[03:07] <mpt> kiko: Will you have time to finish that review today?
[03:07] <kiko> yes
[03:07] <mpt> thanks
[03:07] <BjornT> kiko: yeah, i think we should to that.
[03:07] <mpt> kiko: /people/kiko/+bugs
[03:08] <bradb-bbl> kiko: yeah, i'd love to do that. I'd love to see /malone/assigned go away.
[03:08] <salgado> kiko, I think it's okay
[03:08] <mpt> with links to the Assigned Bugs, Reported Bugs, Fixed Bugs, etc
[03:08] <mpt> links to specialized pages, I mean
[03:08] <kiko> mpt, let's do a mockup of that and I'll fix this week
[03:08] <kiko> thanks
[03:08] <mpt> There's a mockup from February-ish somewhere ;-)
[03:09] <mpt> It would need a different layout for the current page structure
[03:09] <kiko> right
[03:10] <kiko> jamesh?
[03:10] <mpt> Fairly simple, a bunch of <h2>s and <ul>s
[03:11] <kiko> bradb-bbl, BjornT: bug 1871: should I just go ahead and remove it?
[03:12] <BjornT> kiko: i have no idea what should be on that page, so i think it's safe to remove it. bradb-bbl?
[03:14] <kiko> great
[03:14] <kiko> I love removing pages
[03:16] <dePOLL> Mh.. How come I can translate stuff in input boxes but not in textareas?
[03:17] <mpt> dePOLL: That's a bug I'm working on right at the moment
[03:17] <kiko> dePOLL, that's a small issue that carlos (and mpt, really?) are working on
[03:18] <dePOLL> Alright. Any estimate on when it's fixed? :)
[03:18] <kiko> by next tuesday if I'm lucky
[03:18] <mpt> kiko: yes, bug 1326
[03:18] <kiko> ah
[03:18] <kiko> mpt, I recommended to carlos an interim fix meanwhile
[03:20] <mpt> Well, the easiest fix is removing two lines from the code
[03:20] <mpt> (the fix that would make the page long)
[03:21] <mpt> Given the number of complaints about it, it might be worth doing that for 1.0
[03:21] <dePOLL> i'll just wait then. thx for the info.
[03:21] <kiko> dePOLL, note that your translation actually /is/ accepted, it just isn't displayed
[03:22] <kiko> mpt, right.
[03:22] <dePOLL> then there maybe are some duplicates now :>
[03:22] <mpt> kiko: Should I do that, then?
[03:23] <kiko> mpt, coordinate with carlos, because it was on his todo list for this morning, ok?
[03:24] <mpt> ok
[03:24] <mpt> I wouldn't be able to do anything until launchpad--devel--0 is unblocked anyway
[03:24] <kiko> (and the plan I outlined with him was a bit different)
[03:27] <dilys> Merge to<EMAIL_ADDRESS>[r=jamesh] Slave Status Handler improvements (patch-2304<EMAIL_ADDRESS>[03:44] <bradb> BjornT, kiko: Right, removing /malone/packages/ seems ok to me too.
[03:44] <BjornT> bradb: do you have any high priority task on your plate that you can push off to me?
[03:45] <bradb> BjornT: Yeah, I was going to ask you...can you talk to mdz and co. and see what kind of reports they need for 1.0? i.e. Ask them what they think about having a bunch of predefined reports, created at their request, and what they think of there not being an advanced search page, etc.
[03:46] <bradb> salgado: BTW, I fixed the conflicts yesterday on the portlet mania branch.
[03:46] <salgado> bradb, I saw. am going through it right now. ;)
[03:46] <bradb> sweet
[03:47] <BjornT> bradb: sure
[03:48] <bradb> BjornT: great, thanks. Maybe it would be useful to write up a simple wiki page that documents what those predefined reports are (it should be quite lightweight on the implementation side of things, because that should already be covered by things like MaloneSearchResults, etc.)
[03:48] <bradb> (And any other observations you've noted from the users related to those predefined reports.)
[03:49] <salgado> bradb, are we already hiding dupes in bug lists?
[03:49] <bradb> salgado: yeah
[03:49] <bradb> by default, in any case
[03:49] <salgado> oh, nice
[03:49] <BjornT> bradb: yeah, i'll do that
[03:49] <kiko> salgado, yes, I did that.
[03:49] <kiko> bradb, is there no way of adding pagetitles to a page that uses the default views
[03:50] <bradb> kiko: Not that I'm aware of.
[03:50] <kiko> doh
[03:50] <bradb> kiko: I found it useful to create custom pages, to customize which portlets will be shown. This makes it easy to add a page title.
[03:50] <bradb> kiko: I've been nagging SteveA about page titles for a couple months now though. ;)
[03:51] <salgado> ddaa, is there something wrong with using 'diff --link' and the library-relink script together?
[03:52] <ddaa> not additional caveat compared to using them individually (except you probably want to avoid running them at the same time, just to be safe)
[03:53] <ddaa> That's what gives the best performance, and what I'm doing.
[03:53] <salgado> yes, not at the same time. I ask because I got "corrupt library" quite a few times
[03:53] <salgado> will try it again now. my rev library seems to be ok now.
[03:53] <ddaa> Of course, that also means that if you write a file in place, that will corrupt all the revlib entry that contain that file...
[03:54] <ddaa> in my experience, the only tree where that's a problem with the makefiles is the zope tree.
[03:54] <ddaa> aside from that, you have to be careful with your text editor and scripts...
[03:54] <sabdfl> bradb: in my current branch i've added page titles for everything that does not have one, and made it mandatory
[03:54] <ddaa> that means, no additional caveat, same caveat as with linked trees
[03:55] <salgado> oh, right. that's must be the problem, then.
[03:55] <bradb> sabdfl: My portlet mania branch adds 1. portlets to all the pages linked to from the actions portlet on the bug pages and 2. page titles to those pages.
[03:55] <bradb> salgado's reviewing it right now
[03:56] <bradb> s/bug pages/bug page/
[03:57] <ddaa> BTW, that's a bug with the zope tree, that it archives a makefile-generated file
[03:57] <sabdfl> if those pages did not have tests then i would not have added page title
[03:57] <bradb> sabdfl: the problem previously was that, if you use one of the default forms, you can't add a custom title to the page. it's still a problem now, but I've added custom pages for all the pages linked from the bug actions portlet, so that they can have portlets that make sense (e.g. CVE-related portlets on the Add CVE page, dup-related portlets on the mark as dup page, etc.)
[03:57] <ddaa> but one needs pqm superpowers to fix that
[03:58] <sabdfl> i've only added titles where tests were failing because the mandatory titles were not present
[03:58] <kiko> sabdfl, did you add templates for the pages which used the default forms, then?
[03:58] <sabdfl> hmmm...
[03:58] <kiko> cverefs/+new for instance
[03:58] <sabdfl> so what happens to the data you put in pagetitles.py for a template used in a generated form?
[03:58] <sabdfl> kiko: yes
[03:59] <sabdfl> where they were being tested
[03:59] <bradb> sabdfl: They all get a title like "Launchpad" :/
[03:59] <kiko> right
[03:59] <sabdfl> so the tests were failing
[03:59] <sabdfl> bradb: not anymore
[03:59] <sabdfl> iirc, i made all of those fail
[03:59] <kiko> ah, I see what you mean
[03:59] <sabdfl> then added titles for them
[03:59] <sabdfl> i've been fixing up a lot of cruft the past week
[03:59] <sabdfl> that included
[04:00] <kiko> sabdfl, if you don't tell us what you're working on we will guerilla conflict you!
[04:01] <sabdfl> kiko: so, please will you review my --specmachine--0 branch, i'll hand it over to you once i've added tests
[04:01] <sabdfl> doc tests are done, just doing page tests now
[04:01] <kiko> sure
[04:02] <kiko> sabdfl, did you by any chance touch the assigned bugs pages?
[04:02] <sabdfl> has morgs been around today?
[04:02] <sabdfl> kiko: no
[04:02] <sabdfl> not iirc
[04:02] <kiko> great thanks
[04:03] <kiko> I'm doing person/+bugs properly
[04:03] <sabdfl> most of my work has been on the spec tracker
[04:03] <kiko> finally
[04:03] <sabdfl> kiko: very cool, that'sbeen crying out for attention for a while
[04:03] <kiko> sabdfl, malone/assigned is going away in favor of stuff in the person/+bugs hierarchy
[04:03] <sabdfl> the spec tracker is about half as complex as malone, and its done in a week
[04:03] <sabdfl> kiko: perfect
[04:04] <sabdfl> the +bugs page should do something sane
[04:04] <kiko> yep
[04:04] <sivang> sabdfl: a spec tracker? ready for UBZ  ? Cool ;-)
[04:04] <sabdfl> then have +assignedbug, +createdbugs, etc
[04:04] <bradb> BjornT: speaking of important tasks, it would be sweet if you could review MaloneSearchResults so I can land it and that we can proceed with creating more reports without worrying about conflicts.
[04:04] <sabdfl> sivang: ready for next week :-)
[04:04] <sivang> sabdfl: wooo
[04:04] <kiko> or +bugs/assigned +bugs/reported
[04:04] <sabdfl> kiko: no thanks
[04:04] <sabdfl> since level view names
[04:04] <sivang> sabdfl: does that suggests specs from current wikis need to be imported there?
[04:04] <kiko> huh?
[04:05] <sabdfl>  +bugs/+xxx got canned a while back
[04:05] <kiko> "since level view names"?
[04:05] <sabdfl> single
[04:05] <sabdfl> sorry
[04:05] <sabdfl>  /path/to/object/+view
[04:05] <sabdfl> that is all
[04:05] <kiko> wonder why
[04:05] <kiko> +bugs/assigned reads a lot more sensibly
[04:05] <sabdfl> kiko: because i never liked it, and after rewriting rosetta and being able to do without it, it became the standard
[04:05] <sabdfl> remember ct?
[04:06] <sabdfl> so, single page view names
[04:06] <kiko> ct?
[04:06] <sabdfl> single level page view names
[04:06] <sabdfl> cape town, we had a long discussion about /+bugs/+foo
[04:07] <kiko> there must be something I'm missing in terms of implementation, so okay
[04:09] <carlos> mpt, so are you fixing the multiline suggestion too?
[04:09] <kiko> no
[04:09] <kiko> not that I'm aware of -- he is helping design the pomsgsetview, right?
[04:09] <mpt> carlos: Not the long-term way, no
[04:09] <bradb> kiko: BTW, when can I expect to hear from you re: exactly which specs need to be implemented for 1.0 and by what date?
[04:09] <carlos> mpt, no, the "fast" fix
[04:10] <sivang> sabdfl: I discussed some points re: LaunchpadIntegrationHelpPage with mpt last night, I thought to use the current wiki page for my ideas, guess I can wait a week and use the spec tracker when its ready
[04:10] <kiko> bradb, is there a preliminary list?
[04:10] <mpt> carlos: Not until kiko reviews my other fixes
[04:10] <kiko> mpt is confusing me
[04:10] <carlos> mpt, ok
[04:11] <SteveA> kiko: so, you asked about why not +bugs/+new and suchlike
[04:11] <kiko> I did
[04:11] <bradb> kiko: I'll update MaloneOneDotZero to add the other 6 or 8 (or whatever it is) that I understand to be part of 1.0.
[04:11] <mpt> carlos: The quick fix is to delete the tag containing condition="not:messageSet/isMultiline", and its matching end tag
[04:11] <kiko> bradb, ah.
[04:11] <carlos> mpt, not really, we should limit it to one entry
[04:11] <carlos> mpt, and add a suggestions count
[04:12] <SteveA> so, such a pattern emphasises the idea that there is such a thing as context/+bugs, a subset of bugs, and that we're performing operations on that subset
[04:12] <kiko> that's the less quick quick fix
[04:12] <carlos> so people can see it change when they add a new suggestion
[04:12] <kiko> SteveA, I don't read that much into URLs
[04:12] <SteveA> that pattern is very good for programmers and people who find it straightforward to think in that way
[04:12] <mpt> SteveA: I'm trying to use the variables described in http://www.zope.org/Control_Panel/Products/PageTemplates/Help/tal-repeat.stx but they return NotFoundError
[04:12] <kiko> emphasizes to whom, the end-user, or the developers?
[04:12] <kiko> I wasn't suggesting that
[04:13] <kiko> I was saying +bugs/assigned
[04:13] <kiko> which is person-specific
[04:13] <mpt>  /person/stevea/+bugs/reported
[04:13] <mpt> for example
[04:13] <kiko> ah, are you saying it would then be inconsistent with +bugs on other contexts?
[04:13] <SteveA> another pattern is to consider that the '+bug' in /+bug/123 is just a namespace thing to differentiate that '123' is a bug and not something else
[04:14] <SteveA> you now have the choice: do you put 'this page shows bugs that are assigned' in that namespace, or in the 'regular' namespace
[04:14] <kiko> what regular namespace?
[04:14] <SteveA> the former is to say .../+bug/assigned
[04:14] <kiko> what are you talking about?
[04:14] <SteveA> the latter is to say .../+assigned
[04:15] <SteveA> the first example i just gave is to put the 'assigned' page name inside the '+bug' namespace
[04:15] <kiko> what is the +bug namespace?
[04:15] <SteveA> the second example i just gave is to put it in the same 'namespace' as other pages
[04:15] <SteveA> i'll take a step back
[04:15] <kiko> please
[04:15] <SteveA> so, you can consider '.../+bug/...' in two different ways
[04:16] <kiko> more than two, arguably, but okay :)
[04:16] <SteveA> you could consider it as a first class object in launchpad, a collection of bugs in a particular context
[04:16] <SteveA> a subset of all bugs
[04:16] <SteveA> you could alternatively consider it as just a way to put something in the url to distinguish what is to come after it.
[04:17] <kiko> right
[04:17] <mpt> ah!!
[04:17] <kiko> I'm talking about the latter
[04:17] <SteveA> okay
[04:17] <SteveA> so, does 'assigned' need to be distinguished?
[04:17] <kiko> well
[04:17] <kiko> assigned, reported and other bug-related pages could come under +bugs
[04:18] <SteveA> yes, they could
[04:18] <jamesh> kiko: pong
[04:18] <kiko> offering some sort of functionally-related grouping
[04:18] <SteveA> right
[04:18] <SteveA> that is one way of thinking about it
[04:18] <kiko> and trimming off the assigned bit leaves the users in a "default page" for +bugs
[04:18] <kiko> which also makes sense
[04:18] <SteveA> or, you could decide that 'flat is better than nested' for these page names
[04:18] <kiko> (for instance, helping out breadcrumbs)
[04:18] <kiko> flat makes breadcrumbs less trivial
[04:19] <kiko> (the facet links sort of work around that, yes)
[04:19] <bradb> kiko: https://wiki.launchpad.canonical.com/MaloneOneDotZero -- I've added the seven specs that I can think of as being added to 1.0. I'm now going to update LaunchpadOneDotZero.
[04:19] <kiko> great.
[04:19] <kiko> SteveA, just to be clear, I'm not suggesting the subset pattern
[04:20] <kiko> I'm just suggesting trivial grouping
[04:20] <SteveA> right
[04:20] <SteveA> we're just discussing urls for functionality
[04:20] <kiko> right
[04:20] <kiko> If I visit +bugs/
[04:21] <SteveA> so, as it stands, the menus system was written with this "grouping" pattern in mind
[04:21] <kiko> it gives me perhaps a summary page
[04:21] <sivang> kiko: why do you have + next to action urls?
[04:21] <SteveA> and i need to change it to allow for the "flat" pattern
[04:21] <carlos> bradb, hi, do you have a moment?
[04:21] <kiko> SteveA, :-(
[04:21] <kiko> SteveA, where is the win?
[04:21] <SteveA> sivang: we use the "+" to distinguish pages from the names of things that are at the same point in the url
[04:21] <kiko> sivang, to disambiguate when there is a collection of data-dependent names in that level
[04:22] <SteveA> sivang: for example, if you have .../people/stevea   and .../people/kiko
[04:22] <SteveA> then i could register a user called 'bugs'
[04:22] <SteveA> or 'assigned'
[04:22] <kiko> right
[04:22] <SteveA> and that would clash with the page that shows what bugs are assigned to a person
[04:22] <SteveA>   .../people/assigned
[04:22] <kiko> more or less
[04:22] <SteveA> so instead, we call it .../people/+assigned
[04:22] <kiko> ;)
[04:22] <sivang> ah cool
[04:22] <SteveA> beacause people's names, and other names, are not allowed to begin with '+'
[04:23] <bradb> BjornT: you put DR CVE reports in the review queue, right?
[04:23] <cprov> mpt: do you have time now ?!
[04:23] <bradb> carlos: I'll have a moment in about 3 moments from now
[04:23] <mpt> cprov: yes
[04:23] <carlos> bradb, :-)
[04:23] <carlos> ok
[04:23] <cprov> mpt: going to you.
 /me feels like if he'd continue asking question, he'll know enough about launchpad to start helping development </humor>
[04:24] <carlos> sivang, ;-)
[04:24] <carlos> sivang, wiki.launchpad.canonical.com would help you ;-)
[04:24] <BjornT> bradb: yeah
[04:24] <sivang> carlos: I know , I'm gonna set a weekend to have it read throughly
[04:25] <carlos> sivang, wow, that would be a really intense weekend :-)
[04:25] <mpt> SteveA: I've figured out the joy of repeat/foo variables, but now I have an evil TAL question
[04:25] <mpt> if you have time
[04:25] <SteveA> mpt: sure
[04:25] <bradb> BjornT: thanks (just updating LaunchpadOneDotZero, that's why I ask)
[04:27] <mpt> SteveA: Currently the Rosetta translation form looks rather messy because each item has its own little table, so the cells take up different widths
[04:27] <mpt> SteveA: To fix this, I we need to stop using nested tables
[04:27] <mpt> and start using rowspans
[04:27] <mpt> brb
[04:31] <sivang> carlos: well, weekends and late night is mostly what I have currently :)
[04:32] <carlos> sivang, at least you have those... :-)
[04:35] <salgado> elmo, pqm is stuck again. can you kill it for us?
[04:36] <dePOLL> .. it's me again. is there any way to a) delete an account and b) change the name (not the displayed name, but the one taken from the first part of your initial email address)?
[04:37] <mpt> SteveA: Sorry, had to talk to cprov before he left the country
[04:37] <salgado> dePOLL, no, there's no way to delete an account, but you can merge another account into yours. in case you ask this because you found a duplicated account
[04:37] <SteveA> mpt: i totally forgot you were in brazil
[04:38] <salgado> dePOLL, about change the name, it'll be possible after the next production rollout (next tuesday)
[04:38] <salgado> s/change/changing/
[04:38] <bradb> kiko: https://wiki.launchpad.canonical.com/LaunchpadOneDotZero updated
[04:39] <dePOLL> salgado: ok. will the option to merge accounts be added next tuesday too or do i have to send a mail to some admin?
[04:39] <mpt> SteveA: So I have a <th> whose rowspan is dependent on a whole lot of things that are tal:repeated further inside the code, and I'd just like to know the python syntax for that
[04:40] <bradb> BjornT: Can you ensure that you add the pre-defined reports spec to those two pages too?
[04:40] <bradb> (pretty please)
[04:40] <mpt> SteveA: current pseudocode is tal:attributes="rowspan python: number of English forms + 1 for the source + number of forms if translated, or 1 if untranslated + number of suggestions shown * number of plural forms + number of plural forms, for a new translation/suggestion + 1 if there's a developer note"
[04:40] <salgado> dePOLL, you can do that by yourself. just go to https://launchpad.net/people and you'll see a link there
[04:41] <dePOLL> Thanks, salgado. I love you guys and your software :)
[04:41] <salgado> dePOLL, also, if you try to register an email address that's registered on that account you'll get a link to do the merge easily
[04:41] <BjornT> bradb: sure, i'll do it soon
[04:41] <kiko> we try harder
[04:42] <bradb> BjornT: thanks
[04:44] <SteveA> mpt: you want to know how to do this stuff in python?
[04:45] <bradb> carlos: btw, did you need me for something?
[04:45] <mpt> SteveA: Actually I could probably muddle through it myself given enough time
[04:45] <SteveA> do you want to do it in the page template, or in the view class?
[04:45] <carlos> bradb, just want to know how is that launchpad admins are not able to edit/close any bug report
[04:45] <mpt> SteveA: I don't know :-)
[04:46] <mpt> It's just a rowspan value
[04:46] <SteveA> it looks rather complex to me
[04:46] <bradb> carlos: which bug report?
[04:46] <SteveA> so, i'd say, do it in python code
[04:46] <bradb> carlos: you said "any", but let's start with a specific example, to make sure we're on the same page.
[04:47] <carlos> bradb, wordpress
[04:47] <carlos> has a bug report
[04:47] <carlos> that I want to close
[04:47] <SteveA> mpt: as a start, can you formulate it as:  tal:attributes="rowspan python: view.calculateRowspan(some args)"
[04:47] <carlos> but I'm not able to do that because I'm not the owner or the reporter
[04:47] <bradb> carlos: URL?
[04:47] <carlos> https://launchpad.net/products/wordpress/+bugs/860/+index
[04:49] <bradb> carlos: Right, the rules for upstreams are more restrictive than the "wiki mode" of distributions. It doesn't necessarily have to be this way though, but until it's changed, you have to be either the maintainer or assignee to edit an upstream task.
[04:49] <mpt> SteveA: view.calculateRowspan(messageSet), perhaps
[04:49] <mpt> SteveA: Then that function can look in the messageSet itself
[04:49] <SteveA> okay.  so, that's a good first step
[04:49] <SteveA> then, you can write tests for that function
[04:50] <SteveA> which is worthwhile, as it is doing some significant computation
[04:50] <carlos> bradb, but it makes no sense, if I'm a Launchpad admin, I should be able to "admin" the whole site, right?
[04:50] <salgado> lifeless, still here? can you kill pqm? it's stuck, again
[04:51] <kiko> friggin pqm
[04:52] <mpt> SteveA: and the code would go in browser/pofile.py
[04:52] <bradb> carlos: perhaps, yes
[04:52] <SteveA> mpt: is there no view class for this page already?
[04:53] <mpt> oh, pmsgset.py
[04:53] <mpt> pomsgset.py, rather
[04:54] <bradb> carlos: I'll file a bug on it.
[04:54] <carlos> bradb, thanks
[04:54] <SteveA> bradb: nice work organising the malone 1.0 stuff.  i appreciate it, and i know kiko does too.
[04:55] <bradb> thanks ;)
[04:55] <siretart> can anyone explain me how to assign packages to groups in malone?
[04:55] <siretart> or to people?
[04:56] <kiko> siretart, you can't. the maintainer is set based on what the package says it contains
[04:56] <carlos> salgado, around?
[04:56] <kiko> s/contains/is maintained by"
[04:56] <kiko> my god I'm confused today
[04:56] <siretart> kiko: well, then I dont understand, why I have no packages? I'm in the maintainer field of 2 packages: londonlaw and pong2
[04:57] <salgado> carlos, yep
[04:57] <kiko> siretart, we haven't imported the package data into launchpad yet, jus tthat.
[04:57] <kiko> siretart, are there pong2 or londonlaw packages in launchpad?
[04:57] <carlos> salgado, yesterday I changed the owners of all translation teams
[04:57] <siretart> kiko: aaah. that explains
[04:57] <siretart> kiko: how can I check that?
[04:58] <siretart> https://launchpad.net/products/londonlaw
[04:58] <carlos> salgado, to the real owners bu that added daf and I as members of the teams, is there anyway to:
[04:58] <carlos> a) remove us completely not just deactivate us
[04:58] <siretart> but no pong2
[04:58] <kiko> siretart, that's a product, not a package :)
[04:58] <carlos> b) create the team setting another owner different from the one that creates it?
[04:58] <kiko> siretart, welcome to launchpad :)
[04:59] <siretart> ok
[04:59] <carlos> salgado, https://launchpad.net/people/carlos <- This page looks a bit "ugly" with current behaviour
[05:00] <salgado> carlos, b) No, when you create a team you're the owner. maybe it's a good ide to let admins create teams owned by someone else? not sure, you could file a bug and then we'll discuss it with everyone else
[05:00] <kiko> carlos, salgado, mpt: if somebody cooks up a good idea of what should be on that page I can update it. I think it should contain a summary of the person's involvemnet in lp.
[05:01] <jordi> carlos: can we have a look at team creating/editing by me?
[05:01] <carlos> salgado, yeah, that sounds like a good thing
[05:01] <jordi> carlos: for starters, am I able to do this?
[05:01] <kiko> you should be, jordi
[05:01] <carlos> jordi, please, talk with kiko about that, he will be helping you a bit while I work on language packs
[05:02] <salgado> carlos, a) Right now there's no way to completely remove someone from the team. Maybe this is just a matter of hiding inactive memberships, so they won't show on your page neither on the team's +members page
[05:02] <kiko> tell me all you want to know jordi and I will answer
[05:02] <carlos> kiko, seems like launchpad is preventing that Rosetta Experts handle teams
[05:03] <kiko> salgado, I can fix that for you if you like
[05:03] <jordi> kiko: let's create a Greek team that was requested.
[05:03] <salgado> carlos, all members of rosetta experts should be able to handle team owned by the Rosetta Experts and teams in which the Rosetta Experts team is an administrator
[05:03] <salgado> kiko, that'd be great, I think
[05:04] <jordi> now I should /+appoint, right?
[05:04] <carlos> salgado, the problem is that Rosetta Experts will never own a team as a team never creates another team
[05:04] <jordi> https://launchpad.net/rosetta/groups/ubuntu-translators/+appoint == No perms, no chocolate error.
[05:04] <salgado> carlos, you can reassign all translation teams to the Rosetta Experts team
[05:04] <carlos> salgado, anyway, the problem is not related with launchpad teams, sorry, is more related with the Rosetta specific bits
[05:05] <salgado> oh, ok
[05:05] <kiko> carlos, really? how so?
[05:05] <carlos> kiko, launchpad.net/rosetta/groups
[05:05] <carlos> that part of the application
[05:06] <carlos> should be updated to allow Rosetta experts to add/remove teams there
[05:06] <kiko> who can currently add/remove teams there? ah, nobody -- people register teams themselves
[05:06] <SteveA> mpt: do you need someone to help you write a test for that method?
[05:07] <carlos> kiko, only launchpad admins have rights there
[05:07] <kiko> carlos, okay, good point
[05:08] <kiko> salgado, how can we reassign groups?
[05:08] <mpt> SteveA: I don't think so
[05:09] <mpt> I should be able to figure it out
[05:09] <SteveA> the thing is, we haven't been testing view classes much so far.  but we should test them more
[05:09] <mpt> carlos: lib/canonical/launchpad/doc/pomsgset.txt ends with "Let's make a submission, when we are not an editor. It should not
[05:09] <mpt> become the active submission, and it" ... and nothing else
[05:09] <SteveA> i think brad added one the other day
[05:09] <SteveA> to somecontentobject-view.txt
[05:10] <mpt> SteveA: So I should make a pomsgset-view.txt, then
[05:10] <SteveA> yep
[05:10] <carlos> mpt, :-?
[05:10] <SteveA> or maybe it was ....-page.txt
[05:10] <carlos> mpt, is it truncated?
[05:10] <SteveA> i don't remember
[05:10] <kiko> jordi, is there a bug filed on this? could you file it?
[05:10] <mpt> carlos: Looks like it.
[05:10] <SteveA> you should be able to see it in /doc/
[05:11] <mpt> bug-release-targeting-pages.txt, SteveA
[05:11] <carlos> oh :-(
[05:11] <SteveA> sounds right
[05:11] <carlos> mpt, please file a bug abou that
[05:11] <jordi> kiko: not the exact bug. Possibly related, #1776
[05:11] <jordi> I'll file another for this exact situation
[05:13] <kiko> thanks
[05:13] <mpt> carlos: https://launchpad.net/malone/bugs/1881
[05:13] <carlos> mpt, thank you
[05:14] <jordi> kiko: #1882
[05:15] <jordi> kiko: this is blocking a few week-old requests. Should we go over them now?
[05:15] <jordi> only if you have the time
[05:18] <jordi> Georgian, Greek, Slovak team requests; Juanjo Marin asks what to do to join Ubuntu Spanish Translators (possibly the leader is MIA). That's all the team/group pending issues I see.
[05:18] <kiko> jordi, I'm not a launchpad admin -- SteveA who is? could I be, in order to help jordi out?
[05:19] <BjornT> bradb: PreDefinedBugReports added
[05:19] <jordi> actually, tHe Spanish issue is now gone.
[05:20] <bradb> BjornT: great, thanks
[05:20] <bradb> BjornT: Any chance of doing the MSR review today, btw?
[05:21] <BjornT> bradb: no, not today, it's too late already.
[05:21] <bradb> ok
[05:21] <carlos> jordi, koke is the admin of that team and I accepted him already yesterday
[05:22] <SteveA> kiko: according to https://launchpad.net/people/admins, stu, rob and mark are admins of the admins team
[05:23] <kiko> darn
[05:23] <kiko> sabdfl, can I be a launchpad admin?
[05:25] <sabdfl> kiko: done
[05:26] <sabdfl> hey Mez
[05:26] <carlos> superkiko with new super powers!
[05:26] <carlos> :-D
[05:27] <kiko> thanks sabdfl
[05:28] <kiko> jordi, go ahead, I can help you now
[05:28] <jordi> kiko: great.
[05:28] <jordi> hi sabdfl
[05:28] <sabdfl> hey jordi, get a good break?
[05:28] <jordi> good, just two requests/replies to go on the mailing list
[05:29] <jordi> sabdfl: excellent, it was fantastic.
[05:29] <kiko> jordi, privmsg perhaps?
[05:29] <jordi> I really needed to get awayfrom computers. The weather could have been a lot better... it was Februarish!
[05:29] <Mez> evening sabdfl
[05:29] <jordi> but having snow in August is unique :)
[05:29] <christian> i have a problem with my launchpad account. can someone help me?
[05:29] <jordi> kiko: let's go
[05:29] <kiko> christian, sure. what's up?
[05:30] <sabdfl> jordi: where were you?
[05:30] <christian> well, actually everything is fine on launchpad.net
[05:30] <jordi> Peter Chabada<EMAIL_ADDRESS>[05:30] <christian> but when i want to login on ww.ubuntu.com/wiki
[05:30] <christian> it always says: wrong password
[05:30] <jordi> Asks for a Slovak team. As he's the only one for now, he should be appointed as the Slovak member in Ubuntu translators, instead of creating a team (for now)
[05:30] <kiko> christian, are you using the same email address in both cases?
[05:31] <kiko> (to log in)
[05:31] <jordi> sabdfl: Pyrenees, Benasque/Posets valley.
[05:31] <christian> yes. i am logged in into launchpad right now.
[05:31] <jordi> sabdfl: kms and kms of walking during 6 days
[05:32] <kiko> christian, that's most odd. what's your account name?
[05:32] <jordi> sabdfl: soonish I'll post a blog entry with the best pics. I'll give oyu a link.  As you prefer?
[05:34] <kiko> jordi, yeah, this channel is a disaster :)
[05:35] <sabdfl> carlos: we have another problem in production
[05:35] <sabdfl> something is creating pofiles with owner=None
[05:35] <kiko> sabdfl, could you report a bug?
[05:35] <sabdfl> kiko: i'm afraid to drive up my karma
[05:35] <kiko> that way carlos can stay concentrated on fixing the language packs.
[05:36] <kiko> you can put it as max priority
[05:36] <kiko> I'll keep it in my inbox, too :)
[05:36] <kiko> sabdfl, you deserve it
[05:36] <kiko> christian, I don't see a reason why you shouldn't be able to log into the wiki
[05:36] <kiko> christian, you're logging into the wiki using your email address?
[05:36] <carlos> sabdfl, yes, please, file a bug
[05:36] <jordi> sabdfl: heh, you're sooo lacking karma, man
[05:37] <jordi> (wtf I got them from, dunno)
[05:37] <christian> sorry, kiko, wait a sec...
[05:37] <sabdfl> jordi: you rock, but that loophole will get closed by Carlos in due course ;-)
[05:37] <carlos> jordi, breezy imports
[05:38] <bradb> 57K karma points? Sounds like we need to work on karma weighting a bit. :)
[05:39] <jordi> carlos: lol
[05:39] <jordi> sabdfl: see, I get points for getting an obscene amount of Rosetta SWAT email :)
[05:39] <sabdfl> jordi: that's fair enough :-)
[05:40] <carlos> jordi, https://launchpad.net/people/menthos <- He's THE man 314819 points!
[05:41] <bradb> heh, that's hilarious
[05:41] <jordi> woa
[05:41] <jordi> carlos: so all strings imported to rosetta with Last-Translator: Jordi got me points?
[05:41] <jordi> *FUN*
[05:42] <jordi> carlos: we've got a problem with Georgian.
[05:42] <carlos> jordi, yeah
[05:42] <jordi> can you clue us a bit?
[05:42] <carlos> ask and I will try
[05:42] <jordi> carlos: remember Aiet asking to be Georgian admin?
[05:42] <jordi> that got done; thanks.
[05:42] <jordi> but he also says:
[05:42] <jordi> Also, please kindly set my owner permissions to Georgian GNOME, XMSS,
[05:42] <jordi> POEDIT and vte, so I have the right to review the Georgian
[05:42] <jordi> translations.
[05:42] <jordi> what would that mean?
[05:42] <jordi> Should he be added to GNOME translators for GNOME and vte?
[05:43] <jordi> what about poedit and xmms? If they are owned by ubuntu translators, he should be ok, right?
[05:43] <carlos> jordi, poedit and xmms are in open mode
[05:43] <carlos> jordi, and you should create the GNOME Georgian team with he as the admin *only* if he's the official coordinator in GNOME
[05:45] <jordi> he is
[05:46] <jordi> Of course, "You should create the GNOME Georgian team" brings me back to my "I can't do much as a Rosetta Expert" bug ;)
[05:46] <jordi> kiko: you'll have to help me here.
[05:46] <jordi> https://launchpad.net/rosetta/groups/gnome-translation-project/+appoint
[05:46] <kiko> sure
[05:46] <jordi> What you'll see there is unknown to me
[05:46] <kiko> I need to create the team first, I think
[05:46] <kiko> carlos, why is only the maori team currently appointed to gnome?
[05:47] <carlos> kiko, because I hadn't time to create the others
[05:48] <kiko> carlos, that's fine -- I was just curious
[05:48] <jordi> what other?
[05:48] <jordi> do we need to create all GTP groups in therE?
[05:48] <carlos> jordi, yes
[05:48] <carlos> jordi, that's the plan
[05:49] <kiko> somebody remind me of who else apart from elmo has access to the moin datafiles?
[05:49] <jordi> ok, so create the team and then add Aiet?
[05:49] <kiko> right
[05:49] <kiko> jordi, you can probably create that team yourself
[05:50] <kiko> I'll do the rest
[05:50] <kiko> or actually
[05:50] <carlos> jordi, yeah, you should be able to create the team
[05:50] <kiko> you can create the teams and add the people
[05:50] <carlos> then change the ownership to Aiet
[05:50] <kiko> I can do the reassigning later if you like
[05:51] <jordi> I should be able to create the team? How? I see no links
[05:51] <mdz> bradb: fine with hardcoded reports for 1.0, so long as it isn't a problem for you to create new ones on request
[05:51] <carlos> jordi, it's a normal launchpad team
[05:51] <kiko> jordi, https://launchpad.net/people doesn't contain that link for you?
[05:51] <carlos> jordi, launchpad.net/people
[05:52] <bradb> mdz: We're preparing for that to be the case, so it shouldn't be too difficult.
[05:52] <kiko> bradb, the table listing rocks, and I now have a default set of columns, hoo hoo
[05:52] <jordi> kiko: right. Sorry, I still don't know where to fidn all the pointers. /rosetta/groups/foo could have a link in the right blocks if permissions are sufficient, maybe.
[05:53] <kiko> jordi, hmmm, but that's a bit odd, in a way, because you'd be creating a group in the context of another group?
[05:53] <bradb> kiko: default set of columns where?
[05:53] <jordi> wow I can do this
[05:53] <jordi> kiko: hmm.
[05:53] <kiko> bradb, for the table macros :)
[05:53] <Mez> hmm, in launchpad, how can you change which product a bug is assigned to
[05:53] <Mez> we have a big assigned to backports, but it should be in beagle...
[05:53] <bradb> Ah...there was always a default set before, but there were in browser view code, rather than in ZPT.
[05:53] <kiko> Mez, you currently can't, but mpt is going to file a bug to cover that -- we have it speced.
[05:54] <Mez> kiko, that's a shame
[05:54] <kiko> bradb, well, that's a pretty liberal interpretation of "default set" :)
[05:54] <kiko> Mez, you can add another task to the correct one
[05:54] <kiko> and close the original one as invalid
[05:54] <bradb> i.e. "the set you get if you don't override them" :)
[05:55] <Mez> kiko: i only have option "in upstream" or "in distribution"
[05:55] <kiko> Mez, well, is it a package or a product bug?
[05:56] <jordi> carlos: contact address should be aiet or a mailing list if I find it?
[05:56] <Mez> erm, could be either ... most likely product
[05:56] <carlos> jordi, leave it empty
[05:57] <jordi> k
[05:57] <bradb> I think one of the first things I'm going to do after the initial implementation of MSR lands is add an option to that screen to toggle between table/list. No sense waiting for the inevitable user screaming.
[05:58] <kiko> bradb, was there a way of overriding before?
[05:58] <jordi> carlos, kiko: https://launchpad.net/people/gnome-l10n-ka
[05:59] <bradb> kiko: yeah, before there was a macro for those fragments, you just had to define your own little view class with a "task_columns" method. I did it for each of the three types of listings (D, DR and P).
[05:59] <bradb> otherwise it used the base class's default definition of task_columns.
[06:01] <kiko> ah I see
[06:01] <kiko> jordi, add the members you want in it
[06:01] <bradb> In any case, it's nice that that idea has been macrofied
[06:01] <kiko> and reassign ownership
[06:02] <jordi> kiko: oh, so I can because I 0wn the group.
[06:02] <jordi> good.
[06:02] <bradb> lifeless: pqm appears to be wedged.
[06:02] <kiko> PQM WAKE UP
[06:03] <jordi> He should be a team admin so he can approve the rest, right?
[06:03] <kiko> jordi, yes. you can actually make him owner
[06:03] <bradb> i imagine lifeless isn't around
[06:04] <bradb> elmo: can you do the daily pqm bounce please?
[06:04] <kiko> we should have a pqm bounce cronjob
[06:04] <jordi> https://launchpad.net/people/gnome-l10n-ka/+edit <-- can anyone confirm the right block there is a bit fucked up? Small font and stuff like that?
[06:04] <kiko> totally fucked up
[06:05] <kiko> jordi, file a bug
[06:05] <kiko> I can fix it later
[06:05] <jordi> great
[06:05] <jordi> kiko: I don't see how to change the owner
[06:05] <kiko> I can do it
[06:06] <kiko> salgado-lunch, is changing the owner only allowed for admins?
[06:06] <kiko> what's the guy's username, jordi?
[06:07] <jordi> doh, wait a minute. There are two Aiets.
[06:07] <jordi> he hasn't merged
[06:08] <kiko> can you email him and tell him to merge?
[06:08] <jordi> yes
[06:08] <jordi> now he's a member with both accounts.
[06:08] <jordi> I sthat going to be ap roblem?
[06:09] <kiko> shouldn't be, and is a good test of the merge code.
[06:09] <jordi> aietkolkhi is his main user
[06:09] <kiko> great.
[06:11] <sabdfl> jordi: i will fix that bug now in my branch
[06:11] <kiko-fud> thanks sabdfl
[06:12] <jordi> sabdfl: the layout? Thanks!
[06:12] <sabdfl> jordi: np
[06:14] <kiko-fud> sabdfl: https://launchpad.net/malone/bugs/1884
[06:14] <kiko-fud> jordi, added team to translation group.
[06:14] <kiko-fud> what next?
[06:15] <sabdfl> kiko-fud: karma, dude, karma!
[06:15] <kiko-fud> sabdfl, it's your chance to reach the stars<tm>
[06:15] <jordi> thanks; this clears Georgian AFAICT
[06:15] <kiko-fud> can I have lunch and continue later, jordi?
[06:16] <jordi> kiko-fud: I'll have to leave in like 45. I suspect this one will be fast. 5m?
[06:16] <kiko-fud> sure
[06:16] <kiko-fud> what's up?
[06:17] <jordi> Logiotatidis Giorgos asks for a Greek team.
[06:17] <kiko-fud> create the team
[06:17] <kiko-fud> add him as a member
[06:17] <kiko-fud> I'll do the rest
[06:17] <jordi> k
[06:17] <jordi> same for Slovak
[06:18] <jordi> I'll do what I can and drop you a note.
[06:18] <kiko-fud> jordi, email me with the people and teams, ok? will do as soon as I'm back.
[06:18] <jordi> bon apetite :)
[06:18] <kiko-fud> thanks
[06:19] <jordi> Now I wonder if it's  Giorgios Logiotatidis or Logiotatidis Giorgios.
[06:19] <jordi> His mail says the latter, LP the former.
[06:28] <jordi> hrm.
[06:28] <jordi> So for what I'm doing for Greek (just one translator), I just created a team and it will have Giorgos as only translator.
[06:28] <carlos> jordi, no, I told you to add that person directly
[06:28] <jordi> I recall Carlos told me to just add Giorgos to the Ubuntu translators group.
[06:29] <carlos> jordi, teams are only created when we have more than one member
[06:29] <carlos> jordi, right
[06:29] <jordi> yeah. Should we revert this team creation for now?
[06:29] <jordi> I still can do Slovak the Right Way.
[06:30] <carlos> jordi, if the team is already created... do it that way
[06:30] <carlos> but don't create a Slovak team ;-)
[06:31] <jordi> yeah :)
[06:48] <jordi> carlos: so, to get this straight, Peter Chabada, the slovak guy, should be added directly to the ubuntu group
[06:52] <carlos> jordi, right
[07:07] <elmo> does pqm still need bounced?
[07:07] <elmo> (sorry, been working in the DC, hadn't checked IRC)
[07:17] <cprov> bjorn: ping
[07:24] <carlos> jordi, please, add instructions about how to create a new mailing list for translation teams
[07:24] <jordi> yeah
[07:24] <carlos> jordi, it's just a matter of sending an email to<EMAIL_ADDRESS>[07:24] <carlos> asking for it
[07:25] <carlos> but people will not have a clue if we don't say that
[07:25] <carlos> perhaps it's a good entry for our FAQ :-)
[07:26] <jordi> carlos: where did you want me to add it if it's not the FAQ?
[07:27] <carlos> jordi, to any email you send related to new team creation
[07:28] <carlos> last email you sent has this: "You may want to setup a mailing list for this too!"
[07:29] <carlos> jordi, but you don't say how to create it
[07:29] <carlos> jordi, I did the same in previous emails but I think new ones should be more explicits
[07:29] <jordi> carlos: right, oops.
[07:30] <kiko-fud> good ole carlos
[07:30] <kiko> I'm back, I can help jordi
[07:31] <carlos> cool
[07:31] <jordi> kiko: great
[07:31] <jordi> I sent  you mail.
[07:32] <Kinnison> ciao dudes
[07:32] <kiko> Kinnison, treat cprov well!
[07:32] <jordi> kiko: I'm about to leave, I have a dinner.
[07:32] <Kinnison> kiko: I will
[07:32] <Kinnison> kiko: We have plenty of meat
[07:32] <Kinnison> kiko: and a 10kg bag of rice
[07:32] <Kinnison> :-)
[07:33] <kiko> heh
[07:43] <dilys> Merge to<EMAIL_ADDRESS>[trivial]  Add the task status to the latest bugs portlet, and fix expanded/collapsed arrow alignment (patch-2305<EMAIL_ADDRESS>[07:47] <kiko> rock!
[07:49] <jordi> gotta go guys
[07:49] <jordi> laters
[07:49] <jordi> carlos, have a look at the FAQ changes of today and tell me if you think it's missing anything.
[07:49] <jordi> Gotta run
[07:49] <carlos> ok
[07:49] <carlos> jordi, will do later. See you!
[08:09] <bradb> with a new helmet!
[08:14] <bradb> hm, it appears as through cprov has two merge requests in pqm's queue without a reviewer tag. "failure"!
[08:20] <kiko> hoo hoo
[08:28] <dilys> Merge to<EMAIL_ADDRESS>[r=spiv]  cleanups and debug logging (patch-107<EMAIL_ADDRESS>[08:29] <kiko> bradb, an e2? :)
[08:30] <kiko> bradb, does this mean you're going to have to find me a bike for the montreal sessions?
[08:34] <bradb> it's a louis garneau
[08:35] <bradb> if the weather's okayish, i'd imagine it'd be easy to hook up with a bike somewhere
[08:35] <bradb> my neibourhood is a biking mecca
[08:36] <bradb> next investment will probably be some pedals and shoes
[08:37] <sabdfl> kiko: i'm just starting to add tests. would you like to review the code so long?
[08:42] <kiko> sabdfl, I can wait, I have three reviews in the queue
[08:42] <sabdfl> kiko: it's almost [trivial]
[08:42] <sabdfl> ;-)
[08:42] <kiko> that is indeed Very Funny
[08:42] <kiko> now stop interrupting me ;)
[08:44] <sabdfl> jamesh: around?
[08:45] <kiko> hopefully not, it's like 4am in perth :)
[09:06] <sabdfl> kiko: i'm putting the spec in your review queue, but don't start the review till i ping you, 'k?
[09:07] <kiko> sabdfl, that's great, that way I get diffs
[09:07] <sabdfl> ed zachary
[09:07] <kiko> (earlier rather than later)
[09:10] <carlos> see you!
[09:11] <kiko> carlos!
[09:11] <kiko> wait up
[09:11] <carlos> kiko, tell me
[09:11] <kiko> no, you tell me :)
[09:11] <carlos> kiko, test added
[09:11] <carlos> kiko, code ready
[09:11] <kiko> how big is the patch?
[09:11] <carlos> kiko, just need to glue it but I need to leave now
[09:11] <kiko> ah
[09:12] <kiko> so hmmm
[09:12] <carlos> kiko, not too big
[09:12] <kiko> if you like I can help you with it
[09:12] <kiko> anyway
[09:12] <carlos> the test is the biggest part
[09:12] <kiko> I was going to say
[09:12] <kiko> the workflow will need to be: land patch and test in production
[09:12] <kiko> then run the cleanup
[09:12] <carlos> kiko, it's a matter of 30 minutes or so to finish it
[09:12] <carlos> so don't worry
[09:12] <kiko> scrip
[09:12] <kiko> t
[09:12] <carlos> right
[09:12] <kiko> then generate the pack
[09:13] <kiko> can you email stub to make sure this is cherry picked and then the script run tonight?
[09:13] <kiko> it can be later, just as a reminder
[09:13] <kiko> anyway
[09:13] <carlos> kiko, we can do that on staging
[09:13] <kiko> see you a bit later?
[09:13] <kiko> staging?
[09:13] <carlos> kiko, no need to cherry pick it yet
[09:14] <kiko> ah, you mean generate the language pack?
[09:14] <carlos> kiko, yeah, just to be sure it's the right fix
[09:14] <kiko> agreed
[09:14] <carlos> kiko, all, fix the db, generate the language packs and test the new code
[09:14] <kiko> better idea (though more delays :-)
[09:14] <carlos> kiko, I know, but I think is better :-)
[09:14] <kiko> okay, fair enough.
[09:15] <kiko> let's write to the gettext maintainers tomorrow, btw
[09:15] <carlos> will finish the patch before leaving tonight
[09:15] <kiko> great
[09:15] <carlos> but I need to leave now...
[09:15] <kiko> see you later then
[09:15] <carlos> sure
[09:15] <carlos> kiko, see you
[09:15] <kiko> ping me when you're around
[09:15] <kiko> later!
[09:15] <carlos> sure
[09:19] <bradb> Hm, would it be crazy to register a portlet called "+foo-portlet-bar" for "*", where the portlet has simple API that just expects a "foo" to be defined?
[09:19] <kiko> bradb, give me more concrete details :
[09:19] <kiko> )
[09:19] <bradb> e.g. moving all the bug portlets to be now on the bug task (due to the URL change), there's immediately a naming conflict: +portlet-actions
[09:20] <bradb> I can't simply re-register that to be on IBugTask, because then I'll be trying to register two different portlets on IBugTask called +portlet-actions
[09:20] <kiko> bugtask-portlet-actions
[09:20] <kiko> and bugtask-status-portlet-actions
[09:21] <bradb> right, that could work. /me ponders.
[09:22] <bradb> the other problem though was that the naming seems to be slightly confusing on all the pages linked to from what is the current actions portlet for a bug.
[09:22] <bradb> e.g. "+bugtask-portlet-actions" would be used in the Add CVE ref form as well (that merge is already in pqm's queue, in fact. :)
[09:23] <bradb> (the name isn't yet bugtask*, because that would come with the current URL changes, but the actions portlet will be on all those pages now.
[09:24] <kiko> another alternative is saving the rename for later
[09:24] <kiko> and just renaming what is clashing now
[09:26] <bradb> kiko: right, I'll try that and see what happens.
[09:26] <dilys> Merge to<EMAIL_ADDRESS>[r=salgado]  add context-relevant portlets to all the pages linked to from the actions portlet on the bug page (patch-2306<EMAIL_ADDRESS>[09:26] <bradb> s/portlets/portlets and titles (!)/
[09:27] <bradb> round II will hit up all the edit screens
[09:28] <kiko> creeeiiizy
[09:28] <bradb> are we scrapping lp:url, btw? I hope so.
[09:28] <bradb> if so, I'm going to start sniping
[09:30] <SteveA> i think we can get rid of lp:url, now that we have canonical_url, and doc/canonical-url-examples.txt
[09:30] <SteveA> but, please mail the list, proposing it
[09:31] <bradb> ok
[09:31] <SteveA> i'd like to get some input from some others first, to make sure we're not removing something with legitimate uses
[09:35] <bradb> SteveA: Was the original intent of lp:url to help give URL-based code coverage statistics for our page tests?
[09:35] <SteveA> no
[09:35] <bradb> What was the original intent of lp:url?
[09:36] <SteveA> it was originally to provide structured documentation in the zcml file, so people could readily understand what pages go where
[09:36] <SteveA> now that we have a better structured URL space in general, we don't need it so much
[09:37] <bradb> according to sabdfl it was "to help us produce a listing of all the pages and views we had defined"
[09:37] <bradb> which i guess is related
[09:38] <SteveA> yes
[09:39] <kiko> is there a way of concatenating strings in tal?
[09:39] <SteveA> it had that effect too
[09:39] <kiko> i.e. tal:define="foo bar+baz"?
[09:39] <kiko> ah, string:
[09:39] <SteveA> although, now that they are all in one place, this gets easier
[09:39] <SteveA> i mean in templates/
[09:44] <kiko> SteveA, is there a special name (like nothing for None) for the empty string?
[09:44] <SteveA> "string:"
[09:44] <SteveA> "python:''"
[09:45] <kiko> right
[09:45] <kiko> thanks
[10:08] <bradb> kiko: I guess all the portlets like bug-portlet-cve.pt have to be renamed to bugtask-portlet-cve.pt? That feels so wrong, but at the same time, it's consistent with the context-portlet-foo.pt naming convention.
[10:08] <kiko> I wouldn't do it, to be honest
[10:09] <bradb> ok, I'll leave it as is for now then
[10:11] <kiko> pagetests ffs
[10:11] <bradb> Trust me, it's little comfort to *know* that dozens of them will fail :)
[10:13] <kiko> I was referring to my failures :-(
[10:13] <bradb> oh, heh. (i noticed how your merge request disappeared from the pqm queue without dilys saying anything...we all know what a joy that is)
[10:14] <bradb> because you just *know* wait's waiting for your in your inbox
[10:14] <bradb> "Subject: failure"
[10:15] <kiko> exactly
[10:15] <kiko> I just resent
[10:15] <kiko> minor friggin failures
[10:16] <kiko> why doesn't pqm fix the tests for me automatically, I don't know
[10:31] <kiko> ugly issue.
[10:36] <bradb> It might be reasonable to raise an error, because it doesn't seem at this moment that there's a sane use case for wanting the URL of a "bug". Personally, I like the idea of heavily pushing context (both to LP developers and, well, to users, I don't think it needs "pushing"; I think it'll just work the way they expect.)
[10:51] <dilys> Merge to<EMAIL_ADDRESS>[trivial]  Cosmetic fixes to translation group pages: add sortable tables, minor tweaks (patch-2307<EMAIL_ADDRESS>[11:05] <dangerous_piper> #asturlinux
[11:10] <salgado> kiko, can you use your super powers and access https://launchpad.net/people/jalrnc/+edit, so I can see the traceback for the problem reported on #1886?
[11:14] <sabdfl> salgado: it didn't traceback
[11:15] <salgado> sabdfl, oh, I saw it in the error logs. looks like you forgot to remove the comma at the end of +edit. ;)
[11:16] <sabdfl> salgado: no
[11:16] <kiko> me?
[11:16] <sabdfl> i just tried that with the comma
[11:16] <sabdfl> and it failed
[11:16] <sabdfl> tried it without
[11:16] <sabdfl> and it worked
[11:16] <sabdfl> no traceback
[11:16] <salgado> ah, ok
[11:17] <kiko> salgado, did you get the traceback?
[11:17] <salgado> kiko, aparently there's no traceback when accessed by an admin
[11:18] <kiko> I see
[11:18] <kiko> salgado, you can probably ask stub to grep the error logs
[11:18] <salgado> I wonder if it's possible that not accessing it as admin would cause any problem
[11:18] <kiko> wouldn't it be useful to have the raw logs available?
[11:18] <salgado> yes, it would
[11:19] <kiko> salgado, can you email stub CC: launchpad on that topic please?
[11:26] <bradb> https://chinstrap.ubuntu.com/~dsilvers/paste/filexOuCpA.html -- The Joy of Programming
[11:26] <jblack> mpt: Sorry. worked all night and crashed.
[11:26] <salgado> kiko, done
[11:27] <bradb> oops, gotta change the docstring
[11:27] <mpt> jblack: It's ok, I mailed you
[11:28] <jblack> mpt: yeah. He told me that. :)
[11:31] <mpt> any progress?
[11:31] <jblack> I'm going to tray and track that down tonight if he's on.
[11:31] <mpt> cool
[11:32] <lamont> lifeless: btw, congrats on d-d status
[11:37] <bradb> later all
[11:45] <dilys> Merge to<EMAIL_ADDRESS>[trivial]  Fix for bug 1871: /malone/packages is broken. Removes the traversal link. (patch-2308<EMAIL_ADDRESS>[11:50] <carlos> kiko, hi, I'm back
[11:51] <carlos> kiko, and I did the glue code to use the fix. The test are passing now
[11:51] <carlos> now I need to do the whole test run