[01:02] <mpt> Gooooooooooooooood afternoon Launchpadders!
[01:17] <prvul> danilos, 
[01:55] <Ubugtu> New bug: #64079 in launchpad "SourcePackage should be DistroReleaseSourcePackage" [Undecided,Unconfirmed]  http://launchpad.net/bugs/64079
[01:57] <mpt> spiv, ping
[02:18] <mpt> jamesh, ping
[02:26] <Ubugtu> New bug: #64080 in launchpad "Highlighting of active application in facets menu has broken" [Undecided,Unconfirmed]  http://launchpad.net/bugs/64080
[02:56] <jamesh> mpt: pong
[02:58] <mpt> jamesh, SteveA told me that you are a Grep Jedi Master
[02:59] <mpt> In particular, I'd like to change all the <h4>s to <h2>s in any template that has "portlet" in its name
[02:59] <mpt> So, please teach me to fish, figuratively speaking
[03:05] <jonh_wendell> Hi! I've created a bug report both in malone and sourceforge. When i click "affect upstream" in malone, sourceforge doesn't appear in the list of remote bug tracker
[03:05] <jonh_wendell> how can i associate malone bug with sourceforge one?
[03:05] <mpt> jamesh, brb
[03:10] <Ubugtu> New bug: #64084 in launchpad "In Distro Product Search: Cannot match multiple strings" [Undecided,Unconfirmed]  http://launchpad.net/bugs/64084
[03:10] <jonh_wendell> anyone?
[03:11] <crimsun> jonh_wendell: (just wait a tick, please)
[03:24] <jamesh> jonh_wendell: we've got a fix for that but it hasn't been rolled out yet
[03:25] <jamesh> stub: would the sourceforge bug tracker collapsing patch be a candidate for cherry picking?  (it needs a db change, but doesn't alter the schema)
[03:26] <jonh_wendell> jamesh: when will it ready? tomorrow?
[03:26] <stub> jamesh: es
[03:26] <jamesh> jonh_wendell: I'm just asking stub if it'd be possible to put the fix into production before the next rollout
[03:26] <stub> jamesh: Yes
[03:26] <jamesh> stub: okay.  I'll add the request.
[03:27] <stub> ta. Should be today or tomorrow.
[03:27] <jonh_wendell> great
[03:30] <jonh_wendell> thanks, guys
[03:32] <mpt> jamesh, back
[03:34] <jamesh> mpt: okay.  This is one of those situations where Perl is probably the best option
[03:36] <jamesh> mpt: try running this: perl -pi~ -e 's/h4>/h2>/g' *-portlet-*.pt
[03:37] <jamesh> in the templates directory
[03:37] <jamesh> that'll edit each of the portlet files in place
[03:38] <jamesh> the "h4>" expression should match the start and end tags too
[03:38] <jamesh> stylistically, it seems weird to use any level of heading for portlet titles though ...
[03:39] <mpt> Semantically, <h2> is the best fit
[03:40] <mpt> and this way we can move them from the portlet column to the main content area, or vice versa, without altering the markup
[03:41] <mpt> jamesh, I thought "h4>" would work, but it doesn't catch numerous cases of <h4 tal:content="..."
[03:41] <mpt> but I think I can work it out from there, thank you
[03:42] <jamesh> mpt: okay.  Doing a followup replace on "<h4" should do the trick then
[03:43] <mpt> whee
[03:45] <jamesh> don't forget to check that the "bzr diff" output is sane after a search/replace operation like this
[03:48] <mpt> yes, that's what I'm doing now :-)
[03:48] <mpt> jamesh, are you willing to give an rs= on that?
[03:49] <mpt> I'm (1) changing the <h4>s to <h2>s, (2) removing the colons from the portlet headings, and (3) changing two lines in launchpad.css so everything looks as it did before (sans the colons)
[03:49] <jamesh> mpt: you'll need to change a few lines in lib/canonical/launchpad/ftests/test_pages.py (in find_portlet())
[03:50] <jamesh> and may need to update a few tests
[03:50] <mpt> test_pages.py fixed
[03:51] <jamesh> but yea, rs=jamesh is fine.
[03:51] <mpt> thanks muchly
[03:52] <mpt> ugh, one of the portlets had <h4 title="Bug watches keep track of this bug in other bug trackers.">Remote bug watches:</h4>
[03:53] <mpt> Nobody expects the secret tooltip!
[03:53] <mpt> ^W^WSpanish Inquisition
[03:56] <poolie> hi
[03:56] <poolie> is it really right that https://launchpad.net/distros/ubuntu/edgy/+bugs shows no bugs in edgy?
[03:56] <mpt> hi poolie, you've probably been asked this severl times, but why the new nick?
[03:56] <poolie> if only that were true
[03:56] <poolie> mpt, because someone else owns mbp, and i dislike mpool
[03:57] <mpt> fair enough
[03:57] <poolie> and i got used to the idea that irc nicks are informal
[03:57] <jamesh> poolie: because no bugs are filed against ubuntu edgy (as opposed to ubuntu)
[03:57] <mpt> As to your question, I'd point you to https://staging.launchpad.net/distros/ubuntu/edgy/+bugs except that it's down right now
[03:57] <poolie> mpt, i liked your mail about lp-bzr stuff 
[03:57] <jamesh> poolie: bradb has been working on a new release targetting API, but it isn't in production
[03:57] <mpt> bradb implemented release management, wherein people can nominate bugs to be fixed in a particular release
[03:58] <poolie> mpt: have you met or heard of _thumper_, Tim Penhey?
[03:58] <mpt> but it's not rolled out yet
[03:58] <poolie> he'll be working on lp-bzr things; he should hear your thoughts on this stuff
[03:58] <poolie> and he'll be working from Dunedin from December on
[03:58] <poolie> jamesh: ah i see
[03:58] <poolie> jamesh: but it is rather confusing, don't you think?
[03:58] <mpt> poolie, no I hadn't, and argh, Dunedin? I just *left* Dunedin a month ago :-)
[03:58] <poolie> mpt: where to?
[03:58] <mpt> Nelson
[03:58] <mpt> which, in theory, is warmer
[03:58] <mpt> except in the past week
[03:59] <poolie> that's near the top of the south island?
[03:59] <mpt> Top of the South!
[03:59] <jamesh> everywhere in New Zealand is within walking distance though
[03:59] <poolie> oh well
[03:59] <poolie> for large values of "walking" :)
[03:59] <mpt> Still, I could go see him in December when my sisters graduate
[03:59] <poolie> at least it's the same timezone, and moderately close
[03:59] <poolie> cool
[04:00] <mpt> but then, I'll see him at the allhands anyway, I expect
[04:00] <poolie> i should send mail...
[04:00] <poolie> no, unfortunately he won't be there because he'll be in the middle of moving from London to Dunedin
[04:00] <poolie> ("when a man is tired of London...")
[04:01] <poolie> anyhow, although I can understand why it's saying "there are no bugs targetted at edgy"
[04:01] <poolie> or something like that
[04:01] <poolie> don't you think it'll be rather confusing to a new user?
[04:01] <mpt> of course
[04:02] <mpt> it's Launchpad
[04:02] <mpt> I reported a bug on it, though
[04:02] <poolie> actually presumably it doesn't mean "none targetted at edgy", but something else?
[04:02] <poolie> ok
[04:02] <poolie> well, i thought you probably already knew

[04:02] <mpt> bug 32795
[04:02] <Ubugtu> Malone bug 32795 in malone "Distribution release Bugs pages and portlet list hardly any bugs" [Medium,Confirmed]  http://launchpad.net/bugs/32795
[04:02] <mpt> bug 36645
[04:02] <Ubugtu> Malone bug 36645 in malone "Link prominently from distro release bugs pages to distribution bugs pages" [Medium,Confirmed]  http://launchpad.net/bugs/36645
[04:03] <mpt> bug 47833
[04:03] <Ubugtu> Malone bug 47833 in malone "Distribution release package Bugs page usually doesn't list any bugs" [Medium,Confirmed]  http://launchpad.net/bugs/47833
[04:03] <mpt> I spy a duplicate!
[04:03] <jamesh> hmm.  someone stole some snakes at gun point
[04:03] <mpt> oh, wait, the latter includes the word "package"
[04:04] <mpt> jamesh, and next they're going to hijack a plane
[04:04] <jamesh> mpt: it is obviously someone planning a copycat crime, yes.
[04:05] <mpt> We prevent that kind of silliness in New Zealand by not having any snakes
[04:05] <jamesh> we've got whole islands full of snakes over here
[04:05] <jamesh> like Carnac Island
[04:06] <jamesh> lots of tiger snakes there
[04:06] <mpt> bbl
[04:06] <poolie> yeah, those are the bugs i was talking about
[04:07] <poolie> ok, now for my actual bug...
[08:38] <SteveA> stub: hi
[08:38] <SteveA> stub: there's a bug about menus (actions / facets) that has appeared.  Apparently it's not broken on production, but it is broken in RF.
[08:38] <SteveA> bug 64080
[08:38] <Ubugtu> Malone bug 64080 in launchpad "Highlighting of active application in facets menu has broken" [Undecided,Unconfirmed]  http://launchpad.net/bugs/64080
[08:39] <SteveA> I'm not going to get a chance to look at this until next week, I expect
[08:39] <SteveA> so, please bear that in mind for roll-out planning
[09:06] <carlos> morning
[09:22] <stub> SteveA: ok
[09:48] <_thumper_> morning
[09:51] <jamesh> SteveA: for what it is worth, bug 64080 looks like a CSS issue rather than a code issue
[09:51] <Ubugtu> Malone bug 64080 in launchpad "Highlighting of active application in facets menu has broken" [Undecided,Unconfirmed]  http://launchpad.net/bugs/64080
[10:13] <SteveA> thanks for looking into it jamesh 
[10:36] <doko_> ugly, the malone bug watch update doesn't make a difference between rejected and duplicate reports :-(
[10:39] <_Shade_> hi there
[10:39] <_Shade_> how can i confirm my public key at launchpad?
[10:40] <poolie> _Shade_: hi, i thought there was some kind of email confirmation
[10:42] <_Shade_> poolie: yes you're right but they ask me to decrypt the message they've sent, and i have no idea how can i do it
[10:42] <poolie> well do you have a gpg key?
[10:42] <_Shade_> yes i do
[10:43] <poolie> ok, and does the message say something about gpg encryption?
[10:43] <poolie> i think what you should do is
[10:43] <poolie> well, actually it depends on what mail software you're using
[10:43] <poolie> what is it?
[10:44] <_Shade_> well actually it's a... web browser :)
[10:44] <poolie> on gmail or something?
[10:44] <poolie> ok
[10:44] <poolie> open your favourite text editor
[10:44] <_Shade_> yes, gmail
[10:44] <poolie> copy & paste he body of the mail into it
[10:44] <poolie> save that
[10:45] <poolie> then run gpg on the file
[10:46] <_Shade_> ok can you give me the exact syntax please?
[10:46] <jamesh> _Shade_: gpg --decrypt filename
[10:49] <_Shade_> ok it works.... thanks and sorry for bothering you
[10:49] <SteveA> poolie: we have a call with Mark in 10 mins?
[10:50] <poolie> jamesh: actully i think just 'gpg file' will do maybe?
[10:50] <poolie> SteveA: yep, tahnsk
[10:50] <poolie> SteveA: did you send me a mail with comments on 32/Bazaar?
[10:51] <SteveA> not recently
[10:51] <SteveA> at some point in the past, yes
[10:52] <jamesh> poolie: probably.
[10:57] <SteveA> poolie: you're not on the canonical irc channel
[10:57] <SteveA> so clan didn't know you're around for the call
[12:25] <sabdfl> ddaa: that's very good news (svn imports that work^Wrock)
[12:25] <sabdfl> poolie: still around?
[12:26] <ddaa> not yet done, but seeing good progress on the new code
[12:34] <carlos> SteveA: do you have time for an admin task in launchpad? it should be quite fast
[12:35] <carlos> stub, lifeless: ^^^
[12:39] <_thumper_> ddaa: morning
[12:39] <ddaa> hello
[12:39] <_thumper_> docs are explaining much
[12:39] <_thumper_> I'm pleased that they exist
[12:39] <_thumper_> even if slightly out of date
[12:40] <ddaa> I'm glad to appreciate the work I put in that
[12:41] <Ubugtu> New bug: #64154 in rosetta "package page should have a link to current translation" [Undecided,Unconfirmed]  http://launchpad.net/bugs/64154
[01:04] <carlos> danilos: ping
[01:04] <jgi> Hi everyone
[01:04] <danilos> carlos: pong
[01:11] <jgi> how long (in average, or approximatively) does a new template get to be imported?
[01:12] <danilos> jgi: it depends on how busy is the queue; eg. when openoffice import is in progress, it might take a day, but sometimes it's done in a few minutes (but we'll fix this so human uploaded templates get in first)
[01:13] <jgi> ok
[01:20] <doko_> jordi, carlos, danilos: what's the best list to ask for translations beeing made (needing openoffice.org/ooo-build translations for the next upload)?
[01:20] <jordi> doko_: ubuntu-translators@
[01:21] <doko_> ok
[01:21] <carlos> danilos: well, in fact oo.org takes two days to be imported....
[01:21] <doko_> jordi: how can I approve myself translations for https://launchpad.net/distros/ubuntu/edgy/+source/openoffice.org/+pots/ooo-build/de/+translate ?
[01:22] <danilos> carlos: I was just averaging (one might hit the two day delay, but you might also hit a minimal delay if the ooo import was just ending :P)
[01:22] <carlos> yeah :-D
[01:24] <doko_> carlos: ^^^
[01:26] <carlos> doko_: you need to join ubuntu-l10n-de team
[01:26] <danilos> doko_: you need appropriate privileges (be member of ubuntu-l10n-de team, or rosettaadmin
[01:26] <carlos> as you are German, I think you should ask to join ubuntu-l10n-de more than being a rosettaadmin ;-)
[01:27] <doko_> carlos, danilos: that's not the same as a "Rosetta translation group"
[01:27] <doko_> ?
[01:28] <danilos> doko_: that's "Ubuntu German translation group", if that's what you mean ;)
[01:28] <doko_> well, I'm trying to find things ...
[01:28] <doko_> https://launchpad.net/rosetta -> https://launchpad.net/rosetta/groups -> dead end
[01:28] <poolie> sabdfl: hi, still here (briefly)
[01:29] <poolie> _thumper_: hello
[01:29] <stub> carlos: ?
[01:30] <poolie> ok, really away now
[01:31] <carlos> doko_: from there, choose the Ubuntu translation group
[01:31] <carlos> and once there, choose German
[01:32] <doko_> could be better documented ...
[01:32] <stub> Meeting in 28 minutes
[01:37] <carlos> stub: hi, could you do an admin task for me in launchpad.net?
[01:37] <danilos> doko_: you could have simply clicked on "Ubuntu German Translators" on the left side of pahttps://launchpad.net/distros/ubuntu/edgy/+source/openoffice.org/+pots/ooo-build/de/+translatege 
[01:38] <danilos> (some nasty copy pasting inside word "pa<>ge" ;)
[01:40] <stub> carlos: you will need to be more specific
[01:40] <carlos> stub: please, go to https://launchpad.net/people/ubuntu-l10n-hi/+members and approve 'Aniruddha Shankar' request to be a member
[01:41] <carlos> don't give him admin rights, just a plain member
[01:42] <stub> carlos: done
[01:43] <carlos> stub: thanks!
[01:49] <_thumper_> poolie: still there?
[01:50] <poolie> _thumper_: yeah, hi
[01:50] <poolie> how's it going?
[01:50] <_thumper_> good
[01:50] <_thumper_> big picture is coming into focus
[01:52] <jamesh> _thumper_: there is a lot to take in ...
[01:52] <_thumper_> there sure is
[01:52] <Spads> Hey folks, just letting you know, I plan to move asuka from one rack to another.  
[01:53] <Spads> So I'll be taking asuka down for a while
[01:57] <jamesh> http://www.google.com/codesearch <- interesting
[01:58] <stub> Meeting 2 mins
[01:59] <spiv> jamesh: yeah, it is.
[02:00] <spiv> jamesh: you can have fun searching for obscenities and "WTF" and "XXX" and the like :)
[02:00] <jamesh> or the ever popular "how many times does the word fuck appear in the Linux source code?"
[02:00] <stub> == Agenda ==   * Roll call  * Agenda  * Next meeting  * Activity reports  * Actions from last meeting  * Oops report (Matsubara)  * Bug report report (mpt)  * Production and staging (Stuart)  * Launchpad 1.0 status reports  * Sysadmin requests ----  * 1.0 UI help text (mpt)  * 1.0 UI portlet divs (mpt)   * (other items) ----  * Keep, Bag, Change  * Three sentences
[02:00] <stub> Meeting! Who is here
[02:00] <SteveA> me
[02:00] <matsubara> me
[02:00] <carlos> me
[02:00] <BjornT> me
[02:00] <flacoste> me
[02:00] <SteveA> mpt sends apologies
[02:00] <jamesh> me
[02:00] <_thumper_> me
[02:00] <kiko> me
[02:00] <danilos> me
[02:00] <malcc> me
[02:00] <ddaa>  me
 me
[02:00] <cprov> me
[02:01] <jordi> me!
[02:01] <bradb> me
[02:01] <salgado> me
[02:01] <spiv> me
[02:01] <danilos> (salgado twice ;)
[02:02] <stub> That appears to be everyone on channel - we missing anyone
[02:02] <kiko> that's because salgado has friends in high places
[02:02] <stub> ?
[02:02] <stub> == Agenda ==   * Roll call  * Agenda  * Next meeting  * Activity reports  * Actions from last meeting  * Oops report (Matsubara)  * Bug report report (mpt)  * Production and staging (Stuart)  * Launchpad 1.0 status reports  * Sysadmin requests ----  * 1.0 UI help text (mpt)  * 1.0 UI portlet divs (mpt)   * (other items) ----  * Keep, Bag, Change  * Three sentences
[02:02] <stub> Next meeting - same time, same channel next week?
[02:02] <stub> 5
[02:02] <stub> 4
[02:02] <stub> 3
[02:02] <SteveA> yes.  ddaa, _thumper_ and I will be sprinting in london
[02:02] <SteveA> but it's okay
[02:02] <stub> 2
[02:02] <stub> 1
[02:03] <carlos> I will be on vacations
[02:03] <carlos> but will try to attend it
[02:03] <Spads> Sorry to butt in, but staging is now going down for 30 minutes for hardware maintenance.
[02:03] <kiko> I will be on vac
[02:03] <SteveA> thanks Spads 
[02:03] <stub> Two down - not too bad.
[02:03] <jordi> I'll be away next week
[02:04] <stub> Three. ok.
[02:04] <stub> Activity reports. Who is up to date? Who isn't?
[02:04] <bradb> up to date
[02:04] <stub> I'm up to date
[02:04] <carlos> kiko: isn't it a holiday for all Brazilian people too? 
[02:04] <BjornT> up to date
[02:04] <spiv> up to date
[02:04] <salgado> that's true
[02:04] <matsubara> up to date
[02:04] <kiko> carlos, it is.
[02:04] <_thumper_> up to date (except monday)
[02:04] <malcc> not up to date
[02:04] <salgado> I won't be here next friday either
[02:04] <flacoste> up to date
[02:04] <danilos> behind (still--need buttkicking)
[02:04] <salgado> up to date
[02:04] <jamesh> not up to date
[02:04] <carlos> I'm up to date because I started again this Monday
[02:04] <ddaa> up to date
[02:04] <cprov> not up-to-date
[02:04] <jordi> not up to date: missing two reports
[02:05] <matsubara> I'll be here. I swapped thursday with monday
[02:05] <carlos> stub: then, I guess all Brazilian and Spanish people would be on vacations next Thursday
[02:05] <SteveA> out of date
[02:05] <cprov> cprov: I'll be here next thursday.
[02:06] <matsubara> mpt is up to date btw
[02:06] <stub> I suspect we have enough attendees, even if we need to defer some items a week.
[02:06] <stub> Serial offenders - you know who you are.
[02:06] <stub>  * Actions from last meeting
[02:07] <stub>  * SteveA to put up a wiki page for the launchpad project to note disaster scenarios on, and mail the list about it
[02:07] <stub> Steve?
[02:07] <kiko> ha ha ha
[02:07] <ddaa> I think he just went into a tunnel and lost signal
[02:07] <SteveA> hi
[02:07] <SteveA> no
[02:07] <SteveA> whatever
[02:07] <stub>  * SteveA to write up what needs doing to implement `__eq__`, `__ne__`, and `__hash__` for database objects
[02:08] <SteveA> still sitting in a stick note on my desktop
[02:08] <stub> SteveA the Action Man
[02:08] <SteveA> mandatory comic reference: http://www.fatalexception.org/action_item.html
[02:08] <stub> ACTION: SteveA to do his action items or delegate them
[02:08] <stub>  * Oops report (Matsubara)
[02:09] <matsubara> Today's oops report is about bugs 63579, 2369, OOPS-276A553. OOPS are boring lately, which is good. Mostly known bugs with people assigned to handle them.
[02:09] <Ubugtu> Malone bug 63579 in shipit "Request CDs form needs better validation for Phone field." [High,Confirmed]  http://launchpad.net/bugs/63579
[02:09] <Ubugtu> Malone bug 2369 in launchpad "Some people don't have a Ubuntu WikiName" [Medium,Confirmed]  http://launchpad.net/bugs/2369
[02:09] <Ubugtu> https://devpad.canonical.com/~jamesh/oops.cgi/276A553
[02:09] <matsubara> bug 63579 is assigned to salgado. Can you handle that this week?
[02:09] <matsubara> Bug 2369 happens when a someone tries to change the WikiName of a team. I'll take this one, unless someone wants it. :)
[02:09] <matsubara> Carlos or danilos can one of you take OOPS-276A553? I have a quick hack that fixes it but missing tests (https://sodium.ubuntu.com/~andrew/paste/fileuYyk6P.html). Don't know if that's the correct way to fix though
[02:09] <Ubugtu> https://devpad.canonical.com/~jamesh/oops.cgi/276A553
[02:09] <salgado> matsubara, I'll do 63579 this week
[02:09] <matsubara> thanks salgado 
[02:10] <matsubara> This is not related to an OOPS but it would be nice to solve bug 63000 in a way to address bug 62717.
[02:10] <Ubugtu> Malone bug 63000 in malone "Need a way to protect milestone and importance differently from the rest of IBugTask" [Undecided,Confirmed]  http://launchpad.net/bugs/63000
[02:10] <Ubugtu> Malone bug 62717 in blueprint "Anybody can target specs at milestones" [Undecided,Confirmed]  http://launchpad.net/bugs/62717
[02:11] <kiko> matsubara, I think that spec milestone perms.. are unrelated to bug milestone perms.
[02:11] <carlos> matsubara: that's not the right fix
[02:11] <kiko> unfortunately
[02:11] <carlos> matsubara: the problem is that we got: 'start=970&alt=ru?batch=50'
[02:11] <carlos> matsubara: they put there a '?' instead of a '&'
[02:11] <kiko> carlos, matsubara: doesn't my branch fix that?
[02:11] <spiv> kiko: it sounds like there's a common infrastructure feature required to fix them properly, though?
[02:11] <carlos> I think we already talked about this...
[02:11] <matsubara> kiko: nope.
[02:11] <carlos> kiko: I don't know
[02:11] <kiko> spiv, mark suggested adding a launchpad.XXX permission
[02:12] <kiko> matsubara, I think it does.
[02:12] <kiko> spiv, so in a way the infrastructure is already there
[02:12] <SteveA> spiv: I want to have a talk with the infrastructure / review team about permissions
[02:12] <carlos> kiko: your branch changes a lot that code
[02:12] <carlos> so could be that it fixes that issue
[02:12] <SteveA> we should add permissions for these sorts of things right now, but not literally launchpad.XXX
[02:12] <matsubara> kiko: have it landed?
[02:12] <kiko> yes, not literally
[02:12] <kiko> matsubara, no. jamesh doesn't want to review it. ;)
[02:13] <SteveA> we'll fix this up properly after launchpad 1.0 with some more granular security
[02:13] <SteveA> that actually takes interfaces and attributes into account
[02:13] <jamesh> kiko: sorry.  I am working on it :(
[02:13] <SteveA> when choosing what security code to run
[02:13] <carlos> matsubara, kiko: I think that we should raise UFD exception, they gave us a broken query string
[02:13] <spiv> SteveA: That would be good.  Did you see the review thread where I discussed the IBugTask issue with bradb?
[02:13] <matsubara> oh, it's the rosetta refactoring on pending review.
[02:13] <kiko> jamesh, it's okay, I was just teasing. but I am going on vacation tomorrow.. so it will miss next week's rollout
[02:13] <carlos> matsubara: yeah
[02:13] <SteveA> spiv: yes.  I don't really have time to answer in full.
[02:13] <kiko> carlos, maybe..
[02:13] <kiko> I think I added an XXX for that.
[02:13] <SteveA> spiv: but, the answer for now is use more permissions for particular purposes
[02:13] <danilos> well, we actually need that to land before next weeks rollout
[02:13] <matsubara> kiko: I thought you're mentioning another branch
[02:14] <spiv> SteveA: That's fine.  Just so long as you're aware of it.
[02:14] <kiko> matsubara, I don't have any landed branches this rollout, snif
[02:14] <stub> We can discuss rollout later
[02:14] <matsubara> anyway. I'm done here. thanks stub. thanks everyone.
[02:14] <stub>  * Bug report report (mpt)
[02:14] <danilos> ok
[02:15] <jamesh> do we have someone else to handle this one?
[02:15] <kiko> oh mmmm
[02:15] <SteveA> no bug report this week, I think
[02:15] <kiko> I can prepare a report in a few minutes
[02:15] <kiko> if stub reorders things
[02:15] <stub> If we have time :)
[02:15] <stub>  * Production and staging (Stuart)
[02:15] <stub> Staging is back running HEAD (with Carlos' and James' data migration scripts run today too). Enjoy it while you can, as I'll put brads branch back on when he asks for it.
[02:15] <stub> We don't want to do a full production rollout next week due to Bug 64080, but I'm happy to continue with cherry picks.
[02:15] <stub> Nothing else thrilling happening.
[02:15] <Ubugtu> Malone bug 64080 in launchpad "Highlighting of active application in facets menu has broken" [Undecided,Unconfirmed]  http://launchpad.net/bugs/64080
[02:16] <SteveA> bug 64080 is just a CSS omission
[02:16] <SteveA> according to jamesh 
[02:16] <kiko> stub, ah, wonderfull
[02:16] <SteveA> so should be a trivial fix tomorrow from mpt
[02:16] <danilos> stub: how about 1.0 testing?
[02:16] <stub> 1.0 testing?
[02:16] <carlos> stub: which data migration script I asked to run?
[02:17] <danilos> i.e. what's the final date to land something in RF to be able to test it on production as well?
[02:17] <stub> carlos: sorry, I meant salgado (person creation stuff)
[02:18] <salgado> stub, can you paste the script's output somewhere?
[02:18] <carlos> ok ;-)
[02:18] <stub> danilos: I don't know any dates.
[02:18] <salgado> stub, btw, carlos is not a brazilian. ;)
[02:18] <danilos> ddaa: they are, I am going to be seriously bored once it's out ;)
[02:18] <stub> salgado: If I have the output
[02:18] <danilos> stub: ok
[02:18] <ddaa> danilos: you wish you will :)
[02:20] <stub> So stick your cherry pick requests on LaunchpadProductionStatus. I'll make a call next week if we should do a full rollout or not.
[02:20] <stub> Next item?
[02:20] <stub> 5
[02:20] <stub> 4
[02:20] <stub> 3
[02:20] <stub> 2
[02:20] <stub> 1
[02:20] <kiko> I can do the report if you like
[02:20] <stub>  * Launchpad 1.0 status reports
[02:20] <salgado> Question Tracker 1.0
[02:20] <salgado> ---------------------------------
[02:20] <salgado> - SupportTrackerWorklow: in review
[02:20] <salgado> - SupportTrackerViews: started, exception requested to kiko.
[02:20] <salgado> - SupportTrackerHelp: not started.
[02:20] <salgado> - LocalizedSupportRequests: started; reasonable progress.
[02:20] <salgado> Random Things 1.0
[02:20] <salgado> -------------------------------
[02:20] <salgado> - DirectPersonRegistration has a tricky issue blocking its implementation; I'll check today if it needs an exception or if it's going to be dropped.
[02:20] <bradb> Malone 1.0
[02:20] <bradb> [02:20] <bradb> upstream-forwarding-workflow: Added to 1.0. Good progress. BjornT waiting on kiko to confirm scope.
[02:20] <bradb> series-and-distrorelease-mgmt: No news. Still blocked on ConjoinedBugTasks.
[02:20] <bradb> removing-duplicate-comments: Was keeping-bugs-concise. Practically implemented.
[02:20] <bradb> guided-filebug-form: Got all the workflows working, and the +package top-level filebug page refactored to use the same forms and views as the other filebug workflows. Need to update tests and polish.
[02:20] <bradb> malone-essential-docs: No news.
[02:20] <danilos> Rosetta 1.0 weekly report:
[02:20] <danilos> - opening edgy for translation: DONE
[02:20] <danilos> - firefox import/export: good progress, TranslationImport done, cleaning tests
[02:20] <danilos> - oo import/export: blocked on ff support
[02:20] <danilos> - translation review: main functionality implemented (without javascript), fixing tests
[02:20] <danilos> - essential docs: no progress this week
[02:20] <bradb> simple-bug-keywords: Slightly re-defined. Implemented.
[02:20] <cprov> = Soyuz-1.0 Report =
[02:20] <cprov>  * PPA: blocked on ArchiveRework (still).
[02:20] <cprov>  * Archive Rework: progress, still designing a reliable tests, malcc
[02:20] <cprov>  * Code quality: nothing new.
[02:20] <cprov>  * Production upgrade to dapper and started tests with new a-f in mawson
[02:20] <cprov>  * NoMoreAptFtpArchive: Approved, r=kiko, renaming bits, finishing
[02:20] <danilos> - search: not started, pre-draft stage
[02:20] <cprov>    and testing populate-sources.py as part of the main implementation.
[02:21] <danilos> - checks not to upload wrong language PO file using "too many changes" check: not started
[02:21] <cprov>  * General Fixing: nothing new.
[02:21] <danilos> - ui fixes: mpt on those
[02:21] <danilos> - outstanding issues: none
[02:21] <ddaa> importd-bzr-native: database cleanups landed, pybaz removal blocked on extracting used utilities from hct
[02:22] <ddaa> supermirror-smart-server: spiv said he would be late and would get in touch with kiko about additional delay
[02:22] <ddaa> on the implementation front, recent activity was focusing on http transport for smart server protocol
[02:22] <ddaa> wsgi support for launchpad integration was next on the list
[02:23] <stub> That everyone?
[02:23] <stub>  * Sysadmin requests
[02:24] <stub> 6
[02:24] <stub> 7
[02:24] <stub> 5
[02:24] <stub> 4
[02:24] <stub> 3
[02:24] <kiko> I asked for something non-urgent
[02:24] <stub> 1
[02:24] <kiko> so it's ok
[02:24] <SteveA> me too
[02:24] <stub> ok
[02:24] <SteveA> I asked for a symlink of /home/warthogs/archives/ to /code/
[02:24] <SteveA> on devpad
[02:24] <stub> Yay!
[02:24] <kiko> less typin!
[02:24] <SteveA> so we can start using shorter URLs in bzr
[02:24] <SteveA> but it's still pending doing
[02:25] <stub> Two items from mpt on the agenda....
[02:25] <SteveA> I'll handle those
[02:25] <stub>  * 1.0 UI help text (mpt)
[02:25] <SteveA> ok
[02:25] <SteveA> so, one of the 1.0 UI goals is for every page to have some help text
[02:25] <SteveA> often this will just be the text in the "what's all this then?" portlet
[02:25] <SteveA> moved into the helptext area
[02:25] <jamesh> when the symlink gets made, don't update all the URLs on the PendingReviews page -- it will screw up some of the stats the summary page script keeps
[02:25] <SteveA> there's a specific pop-out part of the 1.0 UI page for help text
[02:26] <danilos> (connection died, back now)
[02:26] <SteveA> mpt will be adding a particular <div> on some pages, and some CSS to keep this hidden in mainline
[02:26] <SteveA> but so that it becomes helptext on the 1.0 UI branch
[02:26] <danilos> (can someone paste me privately the part after ddaa's weekly report if anything important happened?)
[02:26] <SteveA> and he'll be asking particular launchpad teams of developers to add helptext for specific pages
[02:26] <SteveA> danilos: there are logs.  see channel title.
[02:27] <danilos> SteveA: are they live? (I am actually checking them right now)
[02:27] <SteveA> this allows us to keep a small deviation between mainline and the ui branch
[02:27] <stub> danilos: yes - live
[02:27] <SteveA> and also allows the work of writing helptext to be spread around
[02:27] <danilos> ok, great, thanks
[02:27] <stub> danilos: (or close...)
[02:27] <SteveA> so, please watch out for this in the coming days, and do the work swiftly.  it isn't a lot of work each.
[02:27] <SteveA> that's all.  thanks.
[02:27] <stub>  * 1.0 UI portlet divs (mpt) 
[02:28] <SteveA> so, as another forwards-compatibility thing, mpt is updating all our portlets to have a particular structure of nested divs
[02:28] <ddaa> sorry, stupid gaim not throttling big pastes properly
[02:28] <SteveA> mpt will be doing this, but please be aware of the need to keep portlets like this, even if it has no particular effect in the standard current ui
[02:29] <SteveA> and if you write new portlets, again, be aware of the correct use of markup for them.
[02:29] <SteveA> mpt will mail about this over the coming days.
[02:29] <SteveA> that's all. thanks.
[02:29] <stub>  * Dropping Malone, Rosetta, Soyuz etc. products -- StuartBishop
[02:29] <stub> Now that we have bug keywords implemented, I would like to collapse all the various Launchpad pseudo-products (rosetta, soyuz, calendar, malone etc.) into the main Launchpad product.
[02:29] <stub> The way we have things setup at the moment breaks our model, particularly relating to branches. For example, if I have a branch registered as a Launchpad branch, I cannot link that to a bug on Rosetta at the moment.
[02:29] <stub> I feel this situation also hinders us dogfooding Launchpad properly at the moment, as we are using it in a different fashion than we expect our users to use it.
[02:29] <stub> Can anyone think of any advantages to keeping things the way they are?
[02:29] <stub> If not, I will collapse all the products into one, assigning keywords to the various bugs so we don't lose that information.
[02:29] <SteveA> eh
[02:29] <SteveA> what about specs?
[02:30] <SteveA> this needs a mail to the list, cc mark
[02:30] <stub> Ok. So we can't look at this until we have a way of categorizing specs better?
[02:30] <malcc> I thought you meant something quite different when you suggested dropping all those products ;)
[02:30] <SteveA> pink slips all round!
[02:30] <kiko> stub, right now launchpad is too big to not be categorized, I think
[02:31] <kiko> so we'd need some sort of sub-product organization if we are to drop the products
[02:31] <SteveA> I think it's a valid point that we're using projects/products differently than we expect others to
[02:31] <kiko> which sounds like surgery
[02:31] <stub> kiko: If that is the case, we need to rethink a lot of our model
[02:31] <kiko> SteveA, I'm not sure. why do you say that?
[02:31] <danilos> I also believe people are really used to filing bugs against rosetta, not launchpad
[02:31] <jamesh> if we did this, we'd want some way to let users categorise the bug on the +filebug page
[02:31] <SteveA> kiko: because I think it's a valid point. :-p
[02:31] <jamesh> which might involve offering a few predetermined bug keywords
[02:31] <SteveA> but really, this is a mailing list discussion
[02:31] <kiko> SteveA, why do you say that rosetta and malone are not separate products, is my question?
[02:32] <SteveA> not a co-ordination meeting discusiion
[02:32] <stub> jamesh: A question I often see go past on this channel is 'which product should I file a bug against?'
[02:32] <kiko> just because they share a code repo?
[02:32] <danilos> and since we're discussing rebranding as well, a keyword "rosetta" wouldn't make much sense ("translation service"? I dunno)
[02:32] <SteveA> although it is okay to point out the mailing list thread (or forthcoming one) and ask for participation
[02:32] <kiko> stub, that should be reduced once we have bugs.launchpad.net, etc.
[02:32] <ddaa> -> mailing list everybody
[02:32] <ddaa> let's move on
[02:32] <kiko> yeah yeah.
[02:32] <stub>  * Keep, Bag, Change
[02:32] <danilos> ok
[02:32] <ddaa> KEEP: bradb!
[02:32] <ddaa> BAG: turnover
[02:33] <stub> yay
[02:33] <SteveA> ddaa: turnover implies hiring people too.  welcome _thumper_!
[02:33] <ddaa> in french we call that "mettre les pieds dans le plat"
[02:33] <bradb> heh
[02:33] <malcc> Are we headhunting from Watership Down now? :)
[02:33] <_thumper_> hi all
[02:34] <kiko> hey _thumper_
[02:34] <ddaa> everybody welcome _thumper_ the new launchpad-bazaar guy
[02:34] <kiko> what's with the underscores? :)
[02:34] <matsubara> hey _thumper_, welcome!
[02:34] <SteveA> kiko: they represent the tub
[02:34] <_thumper_> freenode didn't like it without
[02:34] <ddaa> now that we have danilos and _thumper_, bets are on about who of carlos or me will resign next
[02:34] <carlos> _thumper_: welcome!
[02:34] <carlos> ddaa: good bye dude.... where are you moving
[02:34] <carlos> ?
[02:34] <carlos> :-P
[02:34] <kiko> _thumper_, that's surprising. is thumper already nickserved?
[02:35] <_thumper_> kiko: not sure, just wouldn't allow the name, didn't say owned
[02:35] <stub> And before anyone else resigns.... 
[02:35] <stub>  * Three sentences
[02:35] <danilos> ddaa, carlos: heh ;) _thumper_, wilkommen ;)
[02:35] <malcc> -NickServ- The nickname [thumper]  is not registered
[02:35] <stub> DONE: Name Blacklist
[02:35] <stub> TODO: Pillar Name traversal
[02:35] <stub> BLOCKED: No
[02:35] <malcc> DONE: More ArchiveRework.
[02:35] <malcc> TODO: More ArchiveRework, test new a-f on mawson
[02:35] <malcc> BLOCKED: No
[02:35] <bradb> DONE: Landed fixes for heartfelt issues with dupe bug subscriptions. Resurrected search filter UI patch. Wrote BugVerificationWorkflow after talking to Simon. Finished most of guided +filebug, less updating tests.
[02:35] <bradb> TODO: Put guided filebug up for review. Release management tweaks.
[02:35] <bradb> BLOCKED: kiko/mark on ConjoinedBugTasks decision.
[02:35] <cprov> DONE: NoMoreAptFtpArchive, SoyuzRebuildHandling, bug triage, test new a-f
[02:35] <flacoste> DONE: updated email interface for new support-tracker-workflow, add support requests expiration script, put support-tracker-workflow in review
[02:35] <flacoste> TODO: implement support-tracker-views, land support-tracker-workflow
[02:35] <flacoste> BLOCKED: no
[02:35] <cprov> TODO: new a-f in production, open edgy+1 in mawson, bug fixing for edgy+1
[02:35] <cprov> BLOCKED: no
[02:35] <BjornT> DONE: code reviews. clarified 1.0 goals, good progress on upstream forwarding workflow work spec.
[02:35] <BjornT> TODO: code reviews. last bits of upstream forwarding workflow spec.
[02:35] <matsubara> DONE: oops report analysis, triage and some trivialities fixes
[02:35] <matsubara> TODO: answer kiko's review, fix team wiki bug, more triage and oops report analysis.
[02:35] <matsubara> BLOCKED: no
[02:35] <BjornT> BLOCKED: no
[02:35] <jamesh> DONE: bzr 0.11 in LP, bug export, single SourceForge bugtracker entry, .bzr branch references for products, series and branch pages
[02:35] <jamesh> TODO: code reviews, URL handling branch, other launchpad-bazaar stuff
[02:35] <jamesh> BLOCKED: no
[02:35] <carlos> DONE: oo.org lang packs export, TranslationReview, fixed some missing translations in Rosetta, ticket #1930, 
[02:35] <carlos> TODO: finish TranslationReview and vacations
[02:35] <carlos> BLOCKED: no
[02:35] <salgado> DONE: Removed person creation API from the authserver, discussed and implemented some bits of LocalizedSupportRequests, landed person-creation-rationale, fixed a couple of bugs on the mirror prober and reviewed some code.
[02:35] <matsubara> mpt: DONE: structural object headings, page redesigns, portlet markup
[02:35] <salgado> TODO: Finish LocalizedSupportRequests, add the rss feed of release mirrors to be used in ubuntu.com, code review and random fixes.
[02:35] <salgado> BLOCKED: No
[02:35] <matsubara> mpt: TODO: page redesigns, implement already-designed pages
[02:35] <matsubara> mpt: BLOCKED: no
[02:36] <spiv> DONE: Reviews.  bzr HTTP smart server, including WSGI backend and docs on how to run it with Apache+mod_fastcgi.
[02:36] <_thumper_> [Nick]  Erroneous Nickname
[02:36] <spiv> TODO: bzr smart server/launchpad supermirror integration.
[02:36] <spiv> BLOCKED: no
[02:36] <danilos> DONE: TranslationImport, Firefox support, tests, respond to bug 2181 review
[02:36] <danilos> TODO: FF tests fixing, OOo support, rosetta search, new contract, visa, plane tickets
[02:36] <danilos> BLOCKED: no
[02:36] <Ubugtu> Malone bug 2181 in rosetta "Rosetta automated e-mail should come from @launchpad.net" [Medium,In progress]  http://launchpad.net/bugs/2181
[02:36] <spiv> _thumper_: mysterious!
[02:36] <kiko> DONE: Launchpad report, some hacking, some management, serious email catchup.
[02:36] <kiko> TODO: More email catchup and hacking, solve blockage
[02:36] <kiko> BLOCKED: No
[02:36] <_thumper_> DONE: reading
[02:36] <_thumper_> TODO: more reading
[02:36] <_thumper_> BLOCKED: no
[02:37] <ddaa> DONE: remove-gnuarch, new svn changeset logic
[02:37] <ddaa> TODO: new svn changeset logic, _thumper_ sprint
[02:37] <ddaa> BLOCKED: no
[02:37] <bradb> reading++
[02:37] <_thumper_> stub: just not the smae
[02:37] <_thumper_> s/smae/same/
[02:37] <stub> One blocker from BradB that I see.... kiko - is that under control?
[02:37] <SteveA> DONE: management, UI stuff
[02:37] <SteveA> TODO: relocate, bzr sprint, interviews
[02:37] <SteveA> BLOCKED: no
[02:38] <kiko> stub, well, yes.
[02:38] <bradb> !
[02:38] <stub> kiko: Did you want to do the bug report? we have some time
[02:38] <kiko> stub, yes.
[02:39] <carlos> kiko: btw, if you are on vacations next week and your restructuring branch is not merged before you leave... you are blocking TranslationReview from being reviewed/merged
[02:39] <kiko> Bug report report
[02:39] <kiko> [02:39] <kiko> I picked only the top 5 criticals since we have a lot of 1.0 to do
[02:39] <kiko> https://launchpad.net/products/launchpad/+bug/929
[02:39] <Ubugtu> Malone bug 929 in launchpad "Long words (such as URLs) overflow columns" [Critical,Confirmed]  
[02:39] <kiko> Could James pick up bug 929, so we can finally close this 3-digit one?
[02:39] <kiko> https://launchpad.net/products/rosetta/+bug/2497
[02:39] <Ubugtu> Malone bug 2497 in rosetta "/people/*/+translations times out for prolific translators" [Critical,In progress]  
[02:39] <kiko> I've got to reply to review on the branch for bug 2497; unfortunately
[02:39] <kiko> I've been too busy.
[02:39] <kiko> https://launchpad.net/products/malone/+bug/4594
[02:39] <jamesh> kiko: okay.
[02:39] <Ubugtu> Malone bug 4594 in malone "Shouldn't be able to add duplicate bug watches" [Critical,Confirmed]  
[02:39] <SteveA> _thumper_: I'll explain next week
[02:40] <kiko> Bjorn, will you have time to do 4594?
[02:40] <SteveA> _thumper_: in london
[02:40] <kiko> https://launchpad.net/products/rosetta/+bug/30602
[02:40] <Ubugtu> Malone bug 30602 in rosetta "Timeout errors in +translate" [Critical,Confirmed]  
[02:40] <_thumper_> SteveA: ok
[02:40] <kiko> I need James' review of my branch first before I can fix 30602. My 
[02:40] <kiko> branch puts all the code that needs optimizing in a single place, so it
[02:40] <kiko> should not be too hard unless the problem is intractable.
[02:40] <kiko> https://launchpad.net/products/rosetta/+bug/44214
[02:40] <Ubugtu> Malone bug 44214 in rosetta "We need to add code to prevent POFiles being in the same path" [Critical,In progress]  
[02:40] <kiko> Carlos, how's bug 44214 looking?
[02:41] <carlos> I got some test errors and switched tasks... I should resume it, will try to finish it before leaving tomorrow. Otherwise, it should wait until I'm back on 16th
[02:41] <BjornT> kiko: yeah, i think that one should be doable. it's related to what i'm working on now, so it shouldn't take too long.
[02:41] <kiko> carlos, you've got a one-week vacation?
[02:41] <danilos> carlos: I did take a short look at it, but didn't see anything obvious; I might take another look next week
[02:42] <kiko> BjornT, thanks. if you need help, let me know?
[02:42] <carlos> kiko: yes, you approved it...
[02:42] <kiko> carlos, hmmm, timing..
[02:44] <malcc> Is this thing still on|
[02:44] <malcc> s/|/?/
[02:44] <stub> ok. Meeting over. 1 minute early!
[02:45] <ddaa> thanks stup
[02:45] <ddaa> stub
[02:45] <malcc> Thanks
[02:45] <danilos> thanks stub
[02:45] <SteveA> thanks for a smooth meeting stub
[02:45] <SteveA> BjornT: lunch?
[02:45] <BjornT> SteveA: yeah, i'm hungry. where?
[02:46] <SteveA> I was going to invite M along, as he's in Vilnius.  I'll just call him...
[02:47] <SteveA> BjornT: s. valentinos?  I'll leave my place in 15 mins
[02:48] <BjornT> SteveA: ok
[02:49] <SteveA> ok, see you there
[02:53] <jordi> gah, stub; I had to walk away from the keyboard here at office
[02:54] <jordi> stub: want my 3 lines by msg?
[02:54] <stub> jordi: Sure
[02:55] <salgado> stub, so, you don't have the output of the guess-rationale script, nor the time it took to run?
[02:56] <stub> salgado: I think it took about three hours
[02:56] <stub> salgado: I've lost the output - it was in my screen session, but the server has since been rebooted
[02:56] <stub> (I have the tail end if that helps)
[02:57] <stub> 10:36:36 INFO    Profile with id 670220 and name 'eof' has references from both SourcePackageRelease and POSubmission tables.
[02:57] <stub> 10:40:18 INFO    Updated 2469 profiles with the BUGIMPORT rationale
[02:57] <stub> 10:40:18 INFO    Updated 1749 profiles with the SOURCEPACKAGEIMPORT rationale
[02:57] <stub> 10:40:18 INFO    Updated 4096 profiles with the POFILEIMPORT rationale
[02:57] <stub> 10:40:18 INFO    6806 profiles were not updated
[02:57] <salgado> stub, yeah, that's better than nothing
[02:58] <stub> salgado: https://devpad.canonical.com/~andrew/paste/fileb611VK.html is all I have
[02:58] <salgado> stub, so, assuming this script will run only once in production and that it doesn't use a single transaction, would it be okay to run it as is in production or does it need to be optimized?
[02:58] <stub> salgado: I'll run it again tomorrow anyway
[02:58] <stub> salgado: Yes - that is fine to run against production.
[02:59] <salgado> cool
[03:13] <Spads> Just another notice: PQM is now going down for 30 minutes for hardware maintenance.
[03:13] <kiko> carlos, what's the policy for creating new translation groups?
[03:17] <salgado> Spads, already gone, I guess?
[03:20] <Spads> salgado: yes
[03:22] <salgado> Spads, does the branch that it was processing has been lost and needs to be submitted again?
[03:22] <Spads> salgado: no pqm was running, and we shut down cron before halting
[03:22] <kiko> carlos?
[03:41] <kiko> SteveA, ping
[03:42] <_thumper_> kiko: I think SteveA is out to lunch
[03:42] <kiko> bummer man
[03:42] <kiko> how  bizarre
[03:43] <_thumper_> truely
[03:43] <JPohlmann> Hi all. I need help from one of the Launchpad admins - anyone here?
[03:45] <kiko> yes, JPohlmann 
[03:45] <JPohlmann> I am an Xfce developer and it looks like my name got automatically registered at least two times.
[03:46] <JPohlmann> Once as jannis-pohlmann and once as jannis-xfce.
[03:46] <kiko> JPohlmann, do you have access to both email addresses?
[03:46] <JPohlmann> Yes, of course.
[03:46] <kiko> JPohlmann, just perform a merge, then
[03:46] <kiko> launchpad.net/people
[03:46] <sivang> hiho
[03:46] <kiko> there's a link to request merge
[03:47] <sivang> I have a rosetta quesiton from one of my translation team members
[03:47] <JPohlmann> kiko: Ah, thanks very much.
[03:47] <sivang> yaniv: please go ahead
[03:47] <kiko> JPohlmann, sure thing
[03:47] <JPohlmann> Now, How can I get assigned to the software packages I've written and for which I'd like to observer bug reports?
[03:50] <kiko> JPohlmann, what packages are they? I can fix them for you.
[03:51] <JPohlmann> thunar-media-tags-plugin and xfce4-verve-plugin
[03:51] <JPohlmann> I've registered to all bugmail for those packages now.
[03:51] <JPohlmann> Is this all?
[03:51] <kiko> JPohlmann, one second. are you upstream or packager for those packages?
[03:51] <jgi> hi everyone
[03:52] <JPohlmann> kiko: Upstream. I'm the developer of these two plugins.
[03:52] <yaniv> Well, don't jump at me, but I read the answer to the KDE team's reservations about Rosetta, where it said that the translation teams are encouraged to cooperate with the corresponding GNOME team. I wondered if there was any regular sending of strings to the IL GNOME translation team, as I try to send my translations to their coordinator, but it's quite a long procedure
[03:52] <jgi> a new template is in the queue for the "WengoPhone" product since this morning. Could someone please check if there's anything wrong with it? It's right here: http://librarian.launchpad.net/4678912/qtwengophone.pot
[03:52] <kiko> yaniv, there is no infrastructure in Rosetta to do this now, though it is a planned feature. it still needs to be done manually.
[03:53] <kiko> JPohlmann, okay. what bug tracker do you use for them at the moment?
[03:53] <yaniv> kiko: right. Is there any preferred/effective way to do so?
[03:53] <carlos> kiko: well, if any upstream project request a translation group and ubuntu one doesn't fit their needs, we create one
[03:54] <sivang> kiko: is there an ETA? I get this question loads of times :)
[03:54] <kiko> yaniv, you'd need to contact jordi or carlos for more information
[03:54] <JPohlmann> kiko: We're using our own bugzilla for all Xfce projects. But Jani Monoses, who seems to be responsible for parts of Xubuntu, invited us (Xfce developers) to register to launchpad in order to get notified of bugs in our software.
[03:54] <kiko> carlos, okay.
[03:54] <carlos> jgi: oo.org is being imported right now and that delays a bit the entries in the queue
[03:54] <jgi> carlos, ok, thank you very much
[03:55] <kiko> JPohlmann, that's great. there are some additional things you can do:
[03:55] <kiko> - register the upstream product information
[03:55] <yaniv> kiko: thanks
[03:55] <kiko> - register an upstream bugtracker (though I believe that XFCE is already registered)
[03:55] <kiko> - indicate that those upstreams are packages in ubuntu as those source package names.
[03:56] <carlos> yaniv: well, the only procedure I know about is to contact the team directly and offer your .po file from Ubuntu. If there is someone already working on such pofile in GNOME/KDE, then you will need to coordinate to reuse as much as possible from your translations
[03:56] <carlos> yaniv: if you contact they before starting in Rosetta that would be even better
[03:56] <JPohlmann> kiko: Yep, Xfce is already registered, I think. What do you mean by "indicate that those ..."? And how can I register the upstream product information?
[03:57] <kiko> JPohlmann, launchpad.net/products/+new
[03:57] <sivang> yaniv: we can try recontacting upstream folks, I contacted them in the past and there was not much response. we might be able to try interest them more in translating through rosetta now.
[03:57] <kiko> JPohlmann, create a product for each of your plugins
[03:57] <kiko> JPohlmann, and I'll help you set up the bugtracker information and packaging links.
[03:58] <JPohlmann> kiko: is there a difference between packages and products?
[03:58] <yaniv> sivang: I am in contact with Yair Hershkovitz, head of GNOME translation team. I sen himemy .po's.
[03:58] <kiko> JPohlmann, a product is an upstream that launchpad knows about. products are packaged into ubuntu packages. :)
[03:58] <sivang> yaniv: do you know if he's interested in working thought rosetta maybe? I used to be in contact with Gil Osher (Dolphin) but he was not enthusiastic
[03:59] <JPohlmann> Hmm. There already are (X)ubuntu packages for the plugins, I think.
[03:59] <yaniv> sivang: he's not enthusiastic either, to say the least. I don't see that happening.
[03:59] <kiko> JPohlmann, there are packages, right, but the upstream information is not registered in launchpad.
[03:59] <kiko> JPohlmann, product registration is a bit like freshmeat registration
[04:00] <JPohlmann> Ok.
[04:00] <yaniv> sivang: but maybe we should merge with his repository once in a while (once in a release?)
[04:00] <yaniv> sivang: i.e. send him translations
[04:00] <Keybuk> jamesh: don't suppose there's a "latest 5 revisions" portlet anywhere?
[04:01] <yaniv> sivang: and another question is what is the easiest way (technically) to merge Rosetta ans upstream .po's
[04:02] <sivang> kiko: is there a tool in existance for something like that? ^^
[04:02] <kiko> sivang, you mean msgmerge?
[04:02] <kiko> it's a standard l10n tool
[04:02] <sivang> right
[04:02] <yaniv> the way I do it  now is with poEdit
[04:03] <kiko> msgmerge merges two pofiles
[04:03] <jamesh> Keybuk: nah.  We generally put information like that in the main content where people will see it :)
[04:03] <kiko> trivially
[04:03] <yaniv> kiko: thanks
[04:03] <kiko> jamesh, one disadvantage of that, ironically, is that it's harder to reuse that content in other pages
[04:03] <Keybuk> jamesh: shame, it'd be a nice gadget for that site
[04:03] <sivang> kiko: gazil thanks :)
[04:03] <kiko> Keybuk, could make one if you requested it
[04:04] <kiko> Keybuk, would you iframe it?
[04:04] <kiko> hmm, how would you
[04:04] <Keybuk> SSI include it, was my plan
[04:05] <JPohlmann> kiko: https://launchpad.net/products/xfce4-verve-plugin
[04:05] <sivang> right, it's even comes with gettext. doh
[04:05] <kiko> Keybuk, so file the bug, assign it to me 
[04:06] <kiko> JPohlmann, https://launchpad.net/products/xfce4-verve-plugin/+launchpad
[04:06] <Keybuk> kiko: #64182, thanks
[04:06] <kiko> JPohlmann, in that page you can indicate what bug tracker you use
[04:06] <kiko> (that's the Define Launchpad Usage page)
[04:07] <kiko> JPohlmann, https://launchpad.net/products/xfce4-verve-plugin/+bugcontact and https://launchpad.net/products/xfce4-verve-plugin/+securitycontact let you set up bug contacts who will be notified if upstream issues are reported and need to be forwarded to your bugzilla instance
[04:09] <kiko> matsubara, hmm remind me where we can set up packaging information?
[04:10] <JPohlmann> kiko: Ok, did this for both plugins.
[04:11] <kiko> JPohlmann, cool. I'll add the packaging information for you as soon as I remember where it's done
[04:11] <JPohlmann> kiko: Hehe.
[04:11] <JPohlmann> kiko: The other plugin is https://launchpad.net/products/thunar-media-tags-plugin
[04:11] <kiko> thanks JPohlmann, much appreciated.
[04:12] <kiko> JPohlmann, are there translations for those plugins?
[04:13] <JPohlmann> Sure, but they are managed internally (using an Xfce mailinglist).
[04:13] <kiko> JPohlmann, you may want to look at using Rosetta to get external translations for free, if you like.
[04:13] <JPohlmann> kiko: Thanks for the hint, I'll look into it later.
[04:13] <kiko> okay, cool. 
[04:14] <JPohlmann> Could you notify me when the two packages are linked to both products?
[04:14] <kiko> JPohlmann, I'm about to add them. tell me, is the latest release series of verve 0.2.0?
[04:15] <matsubara> kiko: launchpad.net/products/$product/$series/+addpackage ?
[04:15] <kiko> matsubara, yeah, I just forgot about the series thing
[04:15] <JPohlmann> kiko: No, it's 0.3.4.
[04:15] <matsubara> kiko: or launchpad.net/products/$product/$series/+ubuntupkg
[04:15] <kiko> JPohlmann, and there's a 0.3 series right now?
[04:15] <kiko> of which .4 was the 4th release?
[04:15] <JPohlmann> Yeah. 0.3.2, 0.3.3 and 0.3.4.
[04:15] <JPohlmann> Yep.
[04:15] <_thumper_> kiko: can I get you to change someones name on lp?
[04:15] <Ubugtu> New bug: #64182 in launchpad "Latest 5 Revisions Portlet" [Undecided,Unconfirmed]  http://launchpad.net/bugs/64182
[04:15] <kiko> _thumper_, yeah, in a bit
[04:15] <kiko> thanks Keybuk 
[04:17] <kiko> JPohlmann, and for media tags?
[04:19] <kiko> JPohlmann, 0.1?
[04:19] <JPohlmann> kiko: 0.1 (latest release is 0.1.1). 
[04:20] <kiko> JPohlmann, cool. both products now have packaging links.
[04:20] <kiko> JPohlmann, this means that bugs that are actually upstream issues will now have the product information prefilled, and you will get notified of the need to file them upstream.
[04:20] <kiko> (in the xfce bugzilla)
[04:21] <JPohlmann> Ok, thanks.
[04:21] <kiko> most welcome -- thanks to you for helping out!
[04:22] <JPohlmann> kiko: I noticed there was a bug report for xfce4-verve-plugin. But it's not listed in the project bugs. Is this correct?
[04:23] <kiko> JPohlmann, it needs to be marked as an upstream issue. that bug was reported in the package, but we don't automatically mark it upstream.
[04:23] <JPohlmann> Ah.
[04:23] <kiko> JPohlmann, the reason we don't do that is that the bug may actually be in the packaging
[04:23] <kiko> to mark it as upstream, just follow the +upstream link
[04:23] <JPohlmann> Ok, so I'll only be notified of those who were marked as upstream?
[04:24] <kiko> well
[04:24] <kiko> because you subscribed to the source package
[04:24] <kiko> you'll also be notified of bugs there
[04:24] <salgado> Spads, I just got an email from pqm, which makes me thing the box is back, but the web interface doesn't seem to be back yet
[04:24] <JPohlmann> Hehe, right.
[04:25] <kiko> JPohlmann, https://launchpad.net/distros/ubuntu/+source/xfce4-verve-plugin/+bug/58551/+upstreamtask
[04:25] <Ubugtu> Malone bug 58551 in xfce4-verve-plugin "[edgy]  verve panel plugin does not scale " [Undecided,Unconfirmed]  
[04:25] <kiko> JPohlmann, as you can see, the upstream product name is now prefilled (thanks to the packaging link)
[04:25] <kiko> JPohlmann, and you have the option of linking that task to a bug in your bugzilla
[04:25] <elmo> salgado: the web interface isn't started automatically yet
[04:26] <JPohlmann> kiko: Ah, nice.
[04:26] <kiko> JPohlmann, of course, the bug needs to be filed upstream first!
[04:27] <JPohlmann> kiko: What if I want to say "no, this ain't a bug". Am I able to change the status of any bug report for my products/source packages?
[04:27] <JPohlmann> Or is that up to the packagers?
[04:27] <kiko> JPohlmann, you can change the status -- just click on the package name in the affects table
[04:28] <JPohlmann> kiko: the affects table? What's that?
[04:29] <kiko> JPohlmann, that table in the middle of the bug page
[04:29] <kiko> I would call it the tasks table but brad doesn't let me
[04:29] <JPohlmann> Ah.
[04:38] <salgado> flacoste, have a second?
[04:39] <flacoste> salgado: yep
[04:39] <salgado> flacoste, I'm writing the language vocabulary to use when making new support requests or change existing ones, and this is what I came up with: https://devpad.canonical.com/~andrew/paste/file2hSPsF.html
[04:40] <salgado> I'm wondering if the fact that I cache the vocab elements as an instance variable may be a problem
[04:41] <bradb> BjornT: do you have time to review a small fix for bug 64017?
[04:41] <Ubugtu> Malone bug 64017 in launchpad "Setting a bug confidential after its creation creates a ghost bug" [Critical,In progress]  http://launchpad.net/bugs/64017
[04:41] <salgado> flacoste, there's a bug in it, that will cause English to be shown twice in some cases, but that's another issue. :)
[04:42] <flacoste> salgado: i don't think it is a problem because vocabularies will be instantiated in each request
[04:42] <flacoste> salgado: what is registered is a factory, not an instance
[04:42] <flacoste> salgado: but this is neither implementing IVocabulary nor IVocabularyTokenized
[04:42] <salgado> flacoste, yeah, that is what I thought
[04:43] <salgado> flacoste, I just pasted the __init__() method
[04:43] <salgado> but I have the other ones, necessary to implement these interfaces
[04:43] <flacoste> salgado: I suggest you use an IContextSourceBinder that creates a SimpleVocabulary instanced filled with the needed values
[04:43] <flacoste> salgado: by using IContextSourceBinder, your __init__ method is all you need
[04:44] <bradb> kiko: do you have time to review that fix for bug 64017?
[04:44] <Ubugtu> Malone bug 64017 in launchpad "Setting a bug confidential after its creation creates a ghost bug" [Critical,In progress]  http://launchpad.net/bugs/64017
[04:44] <flacoste> salgado: plus you don't even have to think about the instance attribute issue :-)
[04:44] <kiko> bradb, no
[04:44] <salgado> hmmm. that means less code... I'm all for it. :-)
[04:44] <bradb> ok
[04:44] <salgado> flacoste, thanks dude!
[04:45] <bradb> jamesh: do you have time for a quick review?
[04:45] <flacoste> salgado: my pleasure!
[04:50] <salgado> bradb, that branch seems to have been assigned to me
[04:51] <bradb> salgado: oh, cool. do you have time to review it today? it's pretty important.
[04:52] <ddaa> _thumper_: what are you up to at the moment?
[04:52] <salgado> bradb, sure; I'm reviewing it now
[04:52] <_thumper_> ddaa: yep
[04:52] <_thumper_> not hard since only 15:52
[04:52] <_thumper_> not in NZ yet
[04:52] <bradb> salgado: awesome, thanks
[04:52] <elmo> salgado: the web interface has no init script, so it's not auto-restarted
[04:52] <_thumper_> ddaa: sorry misread
[04:52] <ddaa> _thumper_: I said "what are you up to", not "are you up yet" :)
[04:52] <_thumper_> ddaa: though you asked am I up
[04:52] <elmo> I think last time I bothered lifeless about this he through me some handwavy instructions
[04:53] <salgado> elmo, I see. I guess I need to pester lifeless to get it done?
[04:53] <_thumper_> ddaa: still going through Launchpad's Bazaar
[04:53] <_thumper_> jotting questions
[04:53] <ddaa> reading the documentation?
[04:53] <_thumper_> yeah
[04:53] <_thumper_> and been going through existing bugs and features for launchpad-bazaar
[04:54] <elmo> salgado: try now
[04:54] <ddaa> I suggest you fire some questions now, otherwise I'll dive into cscvs hacking.
[04:54] <_thumper_> cscvs sounds scarey
[04:54] <_thumper_> at least from what I read
[04:54] <salgado> elmo, works now. thanks!
[04:54] <ddaa> _thumper_: it's scary
[04:56] <elmo> anyone mind if we take staging down again for 15 minutes?  If it helps, this will give it some of it's RAM back
[04:57] <salgado> bradb, everything looks good, but one thing you could do (not required) is to comment the "notify(SQLObjectToBeModifiedEvent(context, args))" line on mail/commands.py and see if any tests break. if you get no failures it'd be good to add another one, similar to the one you added, but for the email interface
[04:58] <JPohlmann> kiko: I'm still confused by one thing: How can I see the products I'm maintaining? Are they listed anywhere in my profile (/people/jannis-xfce)?
[04:58] <salgado> bradb, since this is quite critical, I think we should try very hard to avoid regressions
[05:00] <elmo> ok, taking staging down now then
[05:01] <kiko> JPohlmann, heh, no, but that's a bug.
[05:01] <bradb> salgado: right, since you said not required, I'll land what I have (because we know it fixes a critical problem), and then double check the email UI, which should be orthogonal to this bug.
[05:03] <JPohlmann> kiko: Hehe, ok.
[05:06] <salgado> bradb, that's fine
[05:07] <bradb> salgado: great, thanks for the review
[05:07] <salgado> flacoste, on IUnlinkBugsForm, you define bugs as a Set() field and pass in a "value_type=Choice(source=BugLinksVocabularyFactory())". why do you do that instead of using a Choice() field?
[05:08] <flacoste> salgado, because you can select multiple bugs
[05:08] <flacoste> salgado: multiple bugs in the vocabulary created by BugLinksVocabularyFactory
[05:09] <salgado> ahh, I see
[05:09] <flacoste> salgado: in you case, a simple Choice will be enough
[05:09] <salgado> in my case, can I do Choice(vocabulary=MyVocabFactory())?
[05:09] <flacoste> salgado: yes
[05:09] <salgado> cool
[05:10] <flacoste> salgado: well, do provide a title and maybe a description ;-)
[05:10] <salgado> yeah, sure
[05:10] <salgado> I just wasn't sure if I could pass the vocabulary object or if it would accept only a name
[05:11] <flacoste> salgado: to be precise, you are passing a factory object (IContextSourceBinder)
[05:11] <flacoste> salgado: i don't think we can register these by name yet
[05:12] <salgado> well, I'm actually passing a SimpleVocabulary if I do like I said, no?
[05:12] <flacoste> salgado: probably in Zope 3.3 where vocabulary becomes simple adapters
[05:12] <salgado> ah, no
[05:12] <salgado> indeed, it wouldn't make sense to not do that
[05:15] <SteveA> kiko: pong
[05:16] <salgado> flacoste, actually, zope seems to accept only a basestring as the value for the vocabulary argument of a Choice field
[05:17] <flacoste> salgado: that's right, use source=
[05:20] <Ubugtu> New bug: #64191 in launchpad "Should not accept team membership expiry dates beyond 2049" [Undecided,Unconfirmed]  http://launchpad.net/bugs/64191
[05:22] <flacoste> salgado: who reads launchpad-error-reports?
[05:41] <salgado> flacoste, AFAIK, only kiko reads all topics. but there may be more people subscribed to just a few topics
[05:41] <salgado> I think I'm subscribed to one or two of them
[05:46] <salgado> flacoste, I wanted to add a link to the +editlanguages page alongside the dropdown where people can choose the language of a ticket, is there an easier way than subclassing DropdownWidget and overwriting renderValue()?
[05:52] <jordi> jgi: hey
[05:53] <flacoste> salgado: Bjorn suggested justing putting the link in the label
[05:53] <jordi> jgi: by the way, is there any reson to include a "en.po" for wengophone?
[05:53] <flacoste> salgado: oops, sorry
[05:53] <flacoste> salgado: your talking about the ticket language selection UI
[05:53] <jgi> jordi, hello
[05:54] <jgi> jordi, you mean, an english translation?
[05:54] <jordi> yes
[05:54] <jordi> does it contain the same stuff as the original strings?
[05:54] <salgado> flacoste, yep. async.com.br/~salgado/addticket.jpg
[05:54] <jordi> jgi: if so, you should consider removing the file
[05:55] <jordi> jgi: or I can tell rosetta to "ignore it"
[05:55] <kiko> salgado, doesn't that widget sort of clash with the text above it?
[05:55] <jgi> jordi, I think an english translation is interesting because sometimes we use string identifiers that need to be translated in english instead of correct english strings
[05:56] <salgado> flacoste, if I add it to the label, the link wouldn't be on the right side of the dropdown
[05:56] <salgado> kiko-fud, yes, it does. this is just a prototype
[05:56] <flacoste> salgado: yeah, i got that
[05:56] <flacoste> salgado: you could do it in the template by controlling the rendering of the widget
[05:57] <salgado> I think appending something to the return value of DropdownWidget.renderValue() is pretty trivial already... 
[05:57] <jordi> jgi: ok, I can approve it
[05:57] <jgi> jordi, sorry
[05:57] <salgado> flacoste, what do you think would be better?
[05:57] <flacoste> salgado: overriding DropdownWidget is probably less lines
[05:57] <jgi> jordi, I think I misunderstood your question. I didn't realize that there was an english translation waiting in the queue
[05:57] <flacoste> salgado: and has more forward compatibility
[05:58] <jgi> jordi, you can ignore it if you want
[05:58] <salgado> flacoste, yeah, I prefer that too
[05:58] <jgi> jordi, the important thing is importing the templat
[05:58] <jgi> template sorry
[05:58] <jordi> jgi: oh, so I shouldn't approve it?
[05:58] <jordi> if the original strings are != what's in the english file, I guess it should go in.
[05:58] <flacoste> salgado: regarding lp-error-reports, I sent an email to the janitor@support.launchpad.net and it should end up on that list, I was looking for a confirmation of that
[05:59] <jordi> but you tell me, I'm on time to revert the import still
[05:59] <flacoste> salgado: you could put the link in the description?
[05:59] <jgi> jordi, if we're talking about the translation (that is .po file and not .pot file) you can revert the import
[05:59] <salgado> yeah, maybe the description will do. I'll try that
[05:59] <jordi> ok, I told rosetta to ignore these.
[05:59] <jgi> thanks a lot
[05:59] <jordi> jgi: yeah, en.po, not .pot
[06:00] <jgi> ok
[06:01] <salgado> flacoste, hmmm, I'm not sure under which topic that message would end up. I did a quick search on the ML archives but didn't find anything.  when did you send the email?
[06:02] <flacoste> about 20 minutes ago
[06:02] <flacoste> salgado: it should be processed by the SupportTrackerHandler that should decline to process it and thus ends up on that list
[06:03] <salgado> flacoste, it should be under the "Unhandled email" topic then. I'm subscribing to it now
[06:06] <BjornT> flacoste: try sending an email to a ticket that doesn't exist. that way you can see if there's an address filter in place, or if something else is wrong.
[06:08] <flacoste> BjornT: done
[06:16] <salgado> flacoste, X-Original-To: ticket100000@support.launchpad.net is the one you sent?
[06:16] <flacoste> salgado: yes
[06:16] <salgado> flacoste, okay, the one to janitor is there too
[06:16] <flacoste> salgado: great, thanks!
[06:16] <salgado> just got a notification about it
[06:23] <salgado> flacoste, do you think it's a good idea to have the language selection widget on the page where you enter the summary of the ticket to search for similar ones (before actually filing a new one)?
[06:25] <salgado> I think it's confusing not too, but searching for tickets only on non-english language is very likely to not find anything
[06:25] <flacoste> salgado: no I think it is a good idea to enter that information at that point
[06:26] <flacoste> salgado: altough we probably want to search across all languages for similar ones
[06:26] <flacoste> salgado: we can change that later once we settle on a multi-languages indexing strategy
[06:29] <salgado> flacoste, yeah, that sounds good to me
[06:31] <carlos> see you!
[07:25] <Ubugtu> New bug: #64214 in rosetta "untranslated strings included in POs" [Undecided,Unconfirmed]  http://launchpad.net/bugs/64214
[08:17] <kristog> hello :) 
[08:20] <kristog> 2 days ago i was accepted as ubuntu member, but atm my ubuntu.com mail-alias doesn't work
[08:20] <kristog> any hint for this?
[08:23] <matsubara> kristog: it must be manually approved by one of the admins
[08:23] <kristog> uhm, so i have to wait :) ok! thank you.
[08:23] <kristog> matsubara: approved == joined the ubuntumembers group?
[08:24] <matsubara> kristog: also note that your alias can't be any blacklisted name (like 'root') and your preferred email in LP can't create a mail loop (like setting your preferred email to your @ubuntu.com address)
[08:25] <kristog> afaik the name is the same as the one on LP
[08:25] <kristog> (in my case giskard)
[08:25] <matsubara> kristog: that should be ok then.
[08:26] <kristog> matsubara: uhm how i can know what is my prefererred email?
[08:27] <matsubara> kristog: https://launchpad.net/people/giskard/+editemails
[08:27] <kristog> ok the one of autistici.org :)
[08:27] <matsubara> kristog: but the portlet at https://launchpad.net/people/giskard shows it too
[08:28] <kristog> what? the ubuntumembers logo?
[08:28] <matsubara> kristog: shows your preferred address
[08:28] <kristog> ahhh, right sorry, didn't see it :(
[08:29] <kristog> so, i have to wait :) ok.
[08:29] <kristog> thank you
[08:29] <matsubara> kristog: you're welcome.
[08:29] <kristog> :)
[08:31] <Ubugtu> New bug: #64223 in blueprint "Changed status to 'Deferred', message says 'Not Started'" [Undecided,Unconfirmed]  http://launchpad.net/bugs/64223
[08:49] <kiko> salgado, okay, cool, just checking
[09:05] <yleeyas> I have a quick question about un-subscribing from a bug, and discontinuing notifications about that bug
[09:10] <bradb> yleeyas: What's your question?
[09:11] <yleeyas> Ok, I un-subscribed from afew bugs I was following, and my name got shifted to the 'Also notified' list. Now how do I get off that list?
[09:12] <bradb> yleeyas: There are three people that end up in also notified:
[09:12] <bradb> 1. assignees
[09:12] <bradb> 2. bug contacts
[09:12] <bradb> 3. subscribers from dupes
[09:13] <yleeyas> I'm guessing I'm a #3
[09:13] <bradb> ok, good. i have a fix on the way to production, hopefully in the next rollout.
[09:13] <bradb> bug 48860
[09:13] <Ubugtu> Malone bug 48860 in malone ""Also notified" makes difficult to unsubscribe" [Critical,Fix committed]  http://launchpad.net/bugs/48860
[09:13] <yleeyas> Excellent. Thanx for the info.
[09:14] <bradb> no prob
[09:30] <kiko> hey BjornT?
[09:35] <BjornT> hi kiko 
[09:36] <kiko> BjornT, I was going to look for an updated patch of yours to review, but I just found it.
[09:36] <kiko> so you'll have mail soon
[09:39] <BjornT> kiko: cool. i have some questions for you, though, regarding upstream-forwarding-workflow. do you have time to discuss that one now?
[09:39] <kiko> BjornT, sure thing fire away 
[09:44] <kiko> BjornT? :)
[09:46] <BjornT> kiko: sorry, got distracted :)
[09:46] <flacoste> kiko: ping
[09:47] <kiko> ai ai
[09:47] <flacoste> kiko: where should I put the links to the ticket reports?
[09:47] <kiko> flacoste, in the actions menu? I'm chickening out on that question :)
[09:47] <flacoste> kiko: in the action box (like in many place) or in a separate porlets (like on bugs)
[09:47] <flacoste> kiko: so, you give me carte blanche, nice :-)
[09:48] <BjornT> kiko: so, i've tried to incorporate as much from the mockups as possible in the current ui, but there are a few things i didn't do, and i want to know if that's ok or not.
[09:48] <kiko> flacoste, in fact I'm interested in knowing if you have an opinion :)
[09:48] <kiko> BjornT, are you massaging me for bad news? tell me!
[09:48] <flacoste> kiko: i would have put them in the actions menu, but bradb made me wonder
[09:49] <BjornT> kiko: it's not that bad :) the first is about the external bug tracker. i include only a link to the base url, not for filing and searching bugs, since we don't have that information.
[09:49] <flacoste> kiko: i think putting them in the actions box takes less space, which is a plus
[09:49] <kiko> flacoste, there's evidence that people don't look at /any/ boxes around the page, so I'm not sure if either if the options is actually worse. :)
[09:49] <flacoste> lol
[09:50] <BjornT> kiko: i also didn't include a lot of "Change this" links, since only a few people will have access to change the product bug tracker and such.
[09:50] <kiko> bradb, as impartial as the judges at salem
[09:50] <kiko> BjornT, ah, but the change this links were so cute!
[09:51] <kiko> BjornT, so constructing those links for certain bug trackers is very easy and would help our end-users, but you can do that as an additional step (doesn't require undoing anything you've done) if you file a bug when the time comes.
[09:52] <BjornT> kiko: another thing i want to ask you about is what to do with +distrotask? we won't have any upstream links there, so it will always be a two step process (where +upstream should be one-step most of the times). is it ok to keep the current +distrotask as it is, and deal with it later?
[09:52] <kiko> BjornT, what about links to debian?
[09:52] <BjornT> kiko: sometimes we can't construct such links, though, for example SourceForge.
[09:52] <kiko> BjornT, I knew you were going to say that; I agree.
[09:53] <kiko> "it's easy for certain bug trackers" <- insurance :)
[09:53] <BjornT> kiko: do we have any packaging links to debian? the biggest problem with +distrotask is that it can be used for three different things; add a downstream disto, add a upstream distro, or add a source package.
[09:54] <kiko> BjornT, indeed we do not, but we may in the future. let's leave +distrotask for now (but I am curious as to how you will set this up in specs -- perhaps u-f-w-part-2? :-)
[09:55] <kiko> well, we won't have packaging links in the future, but there is such a thing as native-syncs if you ask cprov
[09:56] <BjornT> kiko: distribution-bug-forwarding? :) it should probably be a spec that deals with only +distrotask at least.
[09:57] <kiko> BjornT, accepted.
[09:58] <BjornT> kiko: cool, thanks. did you say you will leave for vacation tomorrow?
[09:58] <kiko> only for 2 days
[09:58] <kiko> I'm back tuesday
[10:01] <BjornT> kiko: ok. then there will still be time next week to show you the ui before the branch is landed.
[10:01] <kiko> BjornT, ping me first thing tuesday because I am curious
[10:01] <kiko> bradb, about CJBT
[10:02] <kiko> bradb, you have a reply pending to me, right?
[10:03] <bradb> kiko: i was going to add anything to that, but...
[10:03] <kiko> ...
[10:07] <bradb> kiko: well, i pointed out that at least 24 files (which means more than 24 files) would need to be changed
[10:07] <kiko> bradb, I don't care about tests. what about the code itself?
[10:07] <bradb> but then you started saying something about "/in code/", which confuses me, because tests are as much "code" as implementation. on even keel, and all that.
[10:08] <kiko> bradb, code as in "not tests". don't be difficult
[10:08] <bradb> kiko: Why do you make that distinction?
[10:09] <kiko> bradb, why don't you answer my question first? :)
[10:09] <bradb> i don't understand how a line of test code is not morally equivalent to a line of implementation.
[10:09] <bradb> kiko: ok. i don't understand what you're aiming for, that's all.
[10:10] <kiko> I appreciate your care for tests, but I'd like to know how much of our implementation currently depends on directly settng attributes.
[10:10] <kiko> now, pretty please with sugar on top, answer my question :)
[10:11] <bradb> kiko: i count 7 non-test files that reference transitionToAssignee
[10:11] <kiko> bradb, could we have other places that set attributes but don't call transitionTo?
[10:18] <bradb> kiko: it's possible that there could be a few more files doing that somehow, though not many, at most.
[10:18] <kiko> there's a call to transitionToStatus in browser/bug.py
[10:18] <bradb> i see about 10 imp files in total doing transitionTo*
[10:18] <kiko> yeah
[10:18] <kiko> one other thing I like about having an API to update everything is that we can put the event triggering into it
[10:18] <bradb> about 44 files overall
[10:18] <kiko> avoiding inconsistency there.
[10:18] <bradb> (er 35, i mean...anyway)
[10:18] <kiko> because you've already done the excellent transitionTo* APIs it seems like the changes are also pretty self-contained requiring little code reorganization
[10:18] <bradb> right
[10:18] <kiko> the fact that there are no ftests underlines that
[10:18] <kiko> oh there is one actually
[10:19] <kiko> test_bugtask.py
[10:20] <bradb> yeah. my main concern is how much work is involved in making this change.
[10:21] <bradb> folding the event handling into this method, while having some benefit, also adds the extra work of making sure events aren't getting fired twice in view code.
[10:22] <kiko> bradb, I know what you mean. OTOH the cleaning up would be very nice and avoid bugs like the one you just fixed today, wouldn't it?
[10:22] <bradb> i'm not necessarily saying these are bad ideas in the big picture. just worried about the workload.
[10:23] <bradb> kiko: yes, it would avoid some bugs. if we really believe that that's how events should be done though, then it seems to me every object should be updated in this way though.
[10:23] <bradb> er, actually, it wouldn't have avoided that other bug
[10:23] <bradb> that was on a bug attribute
[10:23] <kiko> bradb, you wouldn't have to do the event moving in the same work
[10:23] <kiko> but it would allow us to do that as follow-on work
[10:23] <kiko> a further cleanup
[10:24] <kiko> made possible by the amazing API refactoring
[10:24] <kiko> that led to CJBT being trivial
[10:24] <kiko> and that led to DRBT being implemented
[10:24] <kiko> this is warm fuzzies all over!
[10:24] <bradb> DRBT? :)
[10:24] <kiko> distribution release bug targeting!
[10:24] <bradb> heh
[10:25] <kiko> well I should have said deployed
[10:25] <bradb> it's one way to solve that problem, yeah. there are other ways though too, which seem much quicker, if my understanding of sqlobject is correct
[10:25] <bradb> and i mean /much/ /quicker/
[10:26] <kiko> I know, but they do not give the warm fuzzies to me, instead they give me nightmares
[10:27] <bradb> kiko: so, are you really planning on migration /all/ our db objects to such an update() method?
[10:27] <bradb> (speaking of a lot of work!)
[10:27] <kiko> bradb, well, it's been discussed before, and it has actually been done for a few of them.
[10:27] <kiko> I don't think it's practical to do it consistently for evey object at once
[10:27] <bradb> me neither
[10:28] <kiko> but mark and I agree that the side-effects like event triggering etc. can only be done competently if we do factor things like that.
[10:28] <kiko> bradb, my suggestion is have a pre-imp call with jamesh to see what he thinks of the updateAPI proposal.
[10:28] <kiko> and if he thinks it's sane, move ahead with it
[10:28] <kiko> that way you are unblocked
[10:29] <bradb> right. and like i say, i'm not suggesting it's a bad idea, though i will continue to fear how much work may be involved.
[10:30] <kiko> bradb, the work cleaning up the implementation seems easy from my inspection; the work updating tests may not be, but we may have some redundant tests 
[10:30] <bradb> it's a brain transplant, basically
[10:30] <kiko> no
[10:30] <kiko> not nearly that
[10:30] <bradb> we have to rewrite all the edit views too, etc.
[10:30] <kiko> bradb, "rewrite"?
[10:31] <bradb> and create, in some cases, yeah.
[10:31] <bradb> obviously only the parts that actually edit a bugtask are affected
[10:32] <kiko> isn't it a matter of not using applyWidgetsChanges?
[10:32] <bradb> yeah
[10:32] <kiko> I'm confused by your statements about rewrite
[10:32] <bradb> and note that *neither* of the recent event-related bugs would have been prevented by this change :)
[10:32] <bradb> because one was on a create event, and the other was on bug, not bugtask
[10:33] <kiko> the create events should be folded into API as well
[10:33] <kiko> AFAICS
[10:33] <bradb> yeah, it's doable, but would just take a bit longer
[10:33] <kiko> well don't do event folding now
[10:33] <kiko> just the setting-of-attributes folding
[10:34] <bradb> right
[10:35] <bradb> so, i'll talk to jamesh more about it tomorrow then, ok?
[10:43] <kiko> that sounds excellent
[10:43] <kiko> thanks!
[10:51] <bradb> cool, thanks