[12:07] <vdepizzol> there are a rosetta channel?
[12:08] <kiko> vdepizzol, you are there!
[12:09] <kermitX_> i have had some problems with a page at launchpad.net. may i ask for help here (may get a little technical)?
[12:10] <vdepizzol> heehe... :P... rosetta would be a search form to see items already translated
[12:12] <kiko> vdepizzol, that's a known bug and highly requested; it's likely that carlos will work on that as soon as his current feature is landed
[12:12] <vdepizzol> ok :P
[12:13] <vdepizzol> it will be easier to standard a lot of words in translations...
[12:25] <kiko> matsubara, review sent.
[12:26] <matsubara> kiko: thanks
[12:52] <bradb> kiko: how much longer will you be around? i hope to land the perms patch tonight.
[01:02] <kiko> bradb, I'm around, send me diffs!
[01:02] <bradb> refactoring this thing is harder than it looks
[01:03] <kiko> as long as you make it simpler
[01:08] <salgado> hey kiko, let's exchange reviews this time? I'm sending you soon. what about mine?
[01:09] <salgado> s/you/yours/
[01:09] <kiko> salgado, yours will ruin my swimming, so I'll need to send it in tomorrow monring. acceptable?
[01:10] <salgado> well, then it's very unlikely that stub will be able to cherry pick it before monday. which means a few thousand extra requests for Marilize to approve
[01:10] <kiko> HEY 
[01:11] <kiko> don't give me this guilt trip crap
[01:11] <salgado> I think she'll understand that it won't get in because you had to go swimming. ;)
[01:12] <kiko> @!#@!#!$
[01:13] <bradb> kiko: pleaseibegyouletmelandthis!
[01:14] <kiko> dude I need to go in like 5 minutes
[01:14] <kiko> you can call me later if you like though
[01:14] <kiko> SMS the patch
[01:14] <kiko> etc
[01:14] <bradb> heh!
[01:15] <bradb> kiko: can i just land it without further refactoring for now?
[01:15] <kiko> why didn't you do the simple suggestion I gave, grumble
[01:15] <bradb> it's not simple!
[01:16] <kiko> well fix it and I'll stamp tomorrow morning first thing
[01:16] <kiko> how about that?
[01:16] <bradb> ok
[01:22] <kiko-zzz> salgado, GO HOME
[01:22] <salgado> not before you send my review!
[01:24] <kiko-zzz> You can increase sperm you produce five times
[02:31] <spiv> siretart: the url for pushing to bazaar.launchpad.net is sftp://bazaar.launchpad.net/~USER/PRODUCT/BRANCH, where USER is your launchpad nick, PRODUCT is the name of a product registered in launchpad (or +junk for no product), BRANCH is the name for this branch.
[07:46] <SteveA> morning
[07:48] <spiv> Afternoon :)
[07:59] <SteveA> spiv. jamesh, stub: meeting time 
[07:59] <spiv> I'm already on skype.
[07:59] <SteveA> so i see
[08:00] <stub> public holiday here, so better be quick
[08:00] <stub> :)
[08:20] <jamesh> SteveA: sorry.  Was out getting lunch
[08:40] <lifeless> morning
[08:52] <sivang> morning
[09:16] <siretart> spiv: I was rather talking about auto-imported branches like this one: https://launchpad.net/products/xine-lib/head
[09:17] <siretart> spiv: is there a list which branches are auto-imported? How to request a product to be auto-imported so that I can branch from them?
[09:34] <spiv> siretart: https://launchpad.net/people/vcs-imports/+branches
[09:34] <spiv> siretart: although for some reason the xine-lib branch doesn't seem to be listed, maybe it isn't syncing correctly :(
[09:34] <spiv> siretart: ddaa will know more
[09:35] <siretart> spiv: cool. can anyone register branches there so they get autoimported?
[09:35] <sabdfl> siretart: yes
[09:35] <siretart> hi mark! 
[09:35] <siretart> cool! :)
[09:39] <spiv> siretart: talk to ddaa, but it ought to just be a matter of filling out the source details.
[09:39] <siretart> spiv: ok. I'll wait for him here. I'm not how to fill in the details, because it's a svn
[09:41] <spiv> siretart: well, https://launchpad.net/products/mplayer/trunk apparently already has some SVN details.
[09:41] <spiv> The import for that is only "testing" rather than "syncing", though.
[09:42] <siretart> spiv: for xine-lib, it is already 'syncing' but it doesn't show up at vcs-imports as well
[09:42] <spiv> But yeah, at this point all I can do is wave my arms about vaguely and point at ddaa ;)
[09:43] <siretart> :)
[10:26] <SteveA> jordi: ping
[10:34] <jordi> SteveA: here
[01:26] <jordi> mdke: pingping!
[02:08] <carlos> later
[02:16] <mdke> jordi: hi
[02:43] <sabdfl> SteveA, kiko-zzz: all set to speak in 15
[02:44] <SteveA> sabdfl: ack
[02:44] <SteveA> cprov: is kiko around?
[02:44] <cprov> SteveA: I'm not at office, want me to call him ?
[02:45] <SteveA> please, he has a conf call in 15 mins
[02:48] <cprov> SteveA: he is not reachable
[02:49] <SteveA> salgado: are you in the async offices?
[02:49] <salgado> SteveA, yes
[02:49] <SteveA> is kiko there?
[02:49] <salgado> SteveA, not yet
[03:01] <SteveA> sabdfl: dialing in...
[03:04] <kiko-zzz> sabdfl, SteveA: all I hear is new age!
[03:10] <sabdfl> SteveA, kiko-zzz: i'm in
[03:21] <Kagou> hi
[03:22] <Kagou> Is it planed to add a release selection form in reporting bugs  https://launchpad.net/distros/ubuntu/+filebug ?
[03:36] <ddaa> good morning
[03:38] <bradb> Kagou: not yet. bug 424.
[03:38] <Ubugtu> Malone bug 424 in malone "No distribution or version field" [Medium,Confirmed]  http://launchpad.net/bugs/424
[03:38] <Kagou> wow pas tout jeune celui-ci ... merci pour l'info
[03:38] <bradb> de rien
[03:47] <Kagou> cya
[04:05] <carlos> BjornT: hi, around?
[04:06] <BjornT> hi carlos 
[04:06] <carlos> BjornT: about your pomsgsetpage review:
[04:06] <carlos> This should mean that choosing the alternative language is currently
[04:06] <carlos> broken in your patch. Please add a simple page test for it.
[04:06] <carlos> does it mean that it's broken as it's atm?
[04:06] <carlos> or that it would be broken if I revert my change?
[04:09] <BjornT> carlos: add a test and find out ;) i meant it looked like it's currently broken in your patch. reverting your changes should unbreak it. either way a simple pagetest would be sure to ensure that it's not broken.
[04:09] <carlos> BjornT: I have a test already
[04:09] <carlos> and it works
[04:09] <carlos> https://chinstrap.ubuntu.com/~dsilvers/paste/fileLhp2zl.html
[04:09] <carlos> that's testing exactly that
[04:10] <carlos> oh, is your point that the selection using a web browser would not work?
[04:11] <BjornT> carlos: yeah
[04:11] <carlos> hmm, let me check, I think I have also that kind of test...
[04:12] <carlos> BjornT: confirmed, I don't have such test
[04:13] <carlos> thanks for the warning
[04:24] <kiko-zzz> bradb, can you show me just the changed and added methods there?
[04:24] <bradb> kiko-zzz: sure, one sec
[04:26] <salgado> stub, are you going to stay around for a while?
[04:27] <salgado> (in case you are around now)
[04:32] <bradb> kiko-zzz: (Sorry, I had to boot up my youbuntwo laptop...was still reading morning mail on another machine): https://chinstrap.warthogs.hbd.com/~dsilvers/paste/filegTxWYt.html
[04:33] <kiko-zzz> bradb, what happened to the widgets that were setup!
[04:33] <bradb> kiko-zzz: don't ask. it's just magic.
[04:33] <kiko-zzz> that used to be setup
[04:33] <kiko-zzz> tell me
[04:33] <kiko-zzz> please
[04:33] <kiko-zzz> I must know!
[04:33] <bradb> they get setup in the setUpWidgets and setUpDisplayWidgets calls
[04:34] <bradb> they were, AFAICS, needlessly manually instantiated
[04:34] <bradb> AFAICS, i.e., the tests passed
[04:34] <kiko-zzz> can you confirm that with BjornT?
[04:34] <kiko-zzz> did you visually inspect?
[04:34] <bradb> i visually inspected, yeah
[04:35] <bradb> i didn't really test the bug watch stuff though
[04:35] <bradb> but i ran its tests
[04:39] <stub> salgado: There is a beer with my name on it. Whats up?
[04:39] <BjornT> bradb: please inspect th bug watch stuff visually. in general we don't test that information is visible on the page that well.
[04:40] <bradb> BjornT: maybe you can have a look since you know more quickly where and what to inspect?
[04:40] <bradb> BjornT: my server is running, same url as yesterday
[04:41] <salgado> stub, there's some shipit changes that need to be cherry picked. but kiko-zzz doesn't want to review them, so I think it's going to take some time until it lands. :-(
[04:41] <BjornT> bradb: actually, did xx-bugtask-bugwatch-linkage.txt still pass after your change?
[04:42] <bradb> i'll try
[04:42] <stub> salgado: Email me the details when it is done - I can look at it tomorrow.
[04:42] <salgado> stub, cool. thanks!
[04:44] <stub> salgado: Might want to remove the LOCK on shippingrequest too while you are at it - I don't think it is serving any useful purpose and just causing timeouts.
[04:44] <salgado> stub, yeah, I've done that already. :)
[04:44] <bradb> BjornT: urgh
[04:46] <bradb> BjornT: that one fails. all the bugtask-management ones and bugwatch.txt passed. do you see any obvious problems in the logic at the URL i gave kiko?
[04:49] <BjornT> bradb: well, one error is that you removed all the CustomWidgetFactory calls, causing the wrong widgets being used. i'll check if i can see a logic error causing the assignee to be editable.
[04:53] <bradb> BjornT: I assumed those widgets would be properly setup, based on whether they were in the setUpWidgets or setUpDisplayWidgets calls.
[04:54] <BjornT> bradb: no, setUpWidgets and setUpDisplayWidgets use the default widgets. CustomWidgetFactory is used to specify non-default widgets.
[05:01] <BjornT> bradb: i think the assignee is editable since a custom widget is specified in zcml, so you need to explicitly specify a display widget using CustomWidgetFactory.
[05:01] <bradb> I so wish kiko didn't make me refactor this code more than I already had. :) Darn "simple" changes.
[05:03] <kiko-zzz> I liked the change
[05:03] <kiko-zzz> and it should be easy to fix that
[05:03] <kiko-zzz> it's not really that complicated AFAICT
[05:03] <kiko-zzz> just add an if clause in _setupWidgets.
[05:04] <kiko-zzz> (and I must say that was what I suggested last evening, which would have taken 10 minutes!)
[05:06] <matthewrevell> Hello - has anyone noticed delays in receiving email from Launchpad.net?
[05:06] <kiko-zzz> matthewrevell, some people whitelist or block email from us. could that be the cause?
[05:07] <matthewrevell> kiko-zzz: I got the mail after a half-hour delay, or so. It happened with a few password reminders and such. Trying to work out if the delay is at my end, with Gmail or at Launchpad.
[05:08] <matthewrevell> kiko-zzz: As I got it eventually, I'm pretty certain it isn't blacklisted.
[05:08] <kiko-zzz> could be whitelisted
[05:09] <matthewrevell> kiko-zzz: Wouldn't a whitelist just mean it bypasses the spam filter? Or am I thinking of something else?
[05:13] <carlos> BjornT: do you know that the DistributionUsingMaloneVocabulary vocabulary has getTermByToken defined twice ?
[05:15] <BjornT> carlos: that's a bug. please remove the first definition.
[05:15] <carlos> ok
[05:16] <carlos> I think I fixed something like that some time ago in another vocabulary
[05:16] <carlos> I guess it's a product of copy&paste
[05:17] <BjornT> yeah, i seem to recall that i fixed something like that a while ago as well
[05:28] <SteveA> kiko-zzz: i thin you meant "greylisted" rather than "whitelisted"
[05:28] <kiko-zzz> yeah I did
[05:28] <kiko-zzz> I was on a transcontinental phone call dammit!
[05:29] <SteveA> inter continental bastard meeting
[05:31] <ddaa> SteveA: I dunno if I came around telling you
[05:31] <SteveA> hello ddaa 
[05:31] <ddaa> SteveA: but before leaving london, I managed to run cscvs to make a bzr-native import
[05:31] <SteveA> holy crap, that's great
[05:32] <ddaa> still a lot of work to do there, so the test suite uses bzr across the board
[05:35] <SteveA> this is good news indeed
[05:35] <SteveA> thanks for telling me
[05:37] <lifeless> SteveA: what are your thoughts on using pyrex in bzr ?
[05:37] <SteveA> i haven't looked at pyrex in a while.
[05:37] <phanatic> evening everyone
[05:38] <SteveA> in its favour, it should be possible to keep a python implementation in sync with a pyrex implementation
[05:38] <SteveA> and rig things up to test both
[05:38] <phanatic> i'd like to ask if it's possible to remove one of my branches from the supermirror?
[05:41] <lifeless> SteveA: yes, thats something I'm looking at.
[05:41] <lifeless> I've just 'whipped up' (2 hours end to end) a listdir that takes 1/3 the time of os.listdir and also provides the file type.
[05:42] <lifeless> this is a core operation for us.
[05:42] <phanatic> actually i'd like to move it from my home directory to a project's directory (i think the easiest way to do this is delete + push again) - or is there no way to do this right now?
[05:43] <lifeless> just change the owner, I think that that is supported
[05:43] <phanatic> lifeless: how can i do that?
[05:45] <phanatic> i've registered the product, but it's now driven by a team. so it would be better to have that branch under the team's space, so other members could work on them. tell me if i said something wrong :)
[05:45] <SteveA> lifeless: what does os.listdir() take so long in comparison?
[05:46] <lifeless> do you mean why ?
[05:46] <SteveA> any w* word will do
[05:46] <SteveA> so long as it is polite
[05:46] <lifeless> wt :)
[05:47] <lifeless> listdir stats the files it looks at twice.  this does not stat at all for many systems
[05:47] <SteveA> interesting
[05:47] <lifeless> also listdir does not access the path elements in an order that is near-optimal for the disk layout 
[05:47] <SteveA> i wonder if there's a patch you could get upstream
[05:48] <SteveA> if it were in C, it could get into python 2.5
[05:48] <SteveA> there's a performance hike going on right now
[05:48] <lifeless> yes, which is good for future :)
[05:50] <lifeless> so there are several things here
[05:51] <claude> hi i have a problem with my pgp key on launchpad
[05:51] <lifeless> the first thing is that we wrote a replacement for listdir in python, it takes 157 ms to yield all the entries of a tree with 10K file in pre-order (return all the entries of dir A before the contents of directories under A, but finish all the children of A before doing siblings of A)
[05:52] <lifeless> os.walk on that tree taks 220ms
[05:52] <SteveA> claude: hello.  what is the problem?
[05:52] <lifeless> the differences between that routine which we call walkdirs and os.walk is that it stats once and only once, grouping files of a dir with the dir, and is stack based not recursive.
[05:52] <claude> SteveA: hi, the initial expiration date is over 
[05:53] <claude> it's not the case anymore
[05:53] <claude> but Laucnhpad doesn't take into account the new expiration date
[05:53] <lifeless> SteveA: taking walkdirs and replacing its use of listdirs with my read_dir wrapper drops the time from 157 to 77ms. os.walk would probably also get a win from readdir.
[05:54] <claude> https://launchpad.net/people/paroz/+editpgpkeys
[05:55] <SteveA> claude: would you file a support request on this please?  https://launchpad.net/products/launchpad/+addticket
[05:55] <SteveA> claude: then people who can look into this for you will be able to do so.
[05:55] <claude> SteveA: ok
[05:56] <SteveA> claude: include all the details you can think of that are relevant
[05:56] <SteveA> lifeless: would the distributed bzr binary package have a pyrex dependency?  or would it all be compiled into C by then?
[05:56] <lifeless> the binary paackage would have no new deps.
[05:57] <lifeless> the source package will have a .py file that gives the 157ms performance
[05:57] <SteveA> .py ?
[05:57] <SteveA> not .pyrex?
[05:57] <lifeless> .py
[05:58] <lifeless> we would ship the following files:
[05:58] <SteveA> i see
[05:58] <SteveA> you have a .py with single-stating
[05:58] <lifeless> .h - a header for the C version.
[05:58] <lifeless> .py - a wrapper if the C extension is not appropriate on a platform/not built
[05:58] <lifeless> .pyx - the pyrex source.
[05:59] <lifeless> .c - the output of pyrex, which allows building by users/developers who dont have pyrex.
[05:59] <lifeless> that is all
[06:02] <matsubara> :w
[06:03] <SteveA> matsubara: hi.  claude is adding a support request about a problem with gpg key expiration in launchpad.
[06:04] <matsubara> SteveA: ok, I'll take a look.
[06:04] <SteveA> lifeless: that all sounds fine to me.  the problem i've seen in the past with parallel python and C or C-ish implementations is when the tests are not run twice with each implementation.  
[06:04] <SteveA> then the C version gets developed and the python one rots away
[06:05] <claude> matsubara; just done, ticket 1020
[06:05] <lifeless> SteveA: indeed. Doingn interface testing on them is already implemented the 'cheap way' - make check on pqm will run on python only then build the extension, then run again.
[06:05] <SteveA> nice
[06:12] <licio> in my launchpad home, show the Ubuntero is Not yet, but I signed the code of conduct
[06:12] <matsubara> licio: bug 48995
[06:12] <Ubugtu> Malone bug 48995 in launchpad "People who have signed the Code of Conduct are now listed as not being Ubunteros." [Medium,Confirmed]  http://launchpad.net/bugs/48995
[06:12] <licio> matsubara, thanx
[06:14] <kiko> matsubara, is this a regression from your changes to CoC 1.0.1?
[06:15] <matsubara> kiko: I think it's related
[06:16] <salgado> it definitely is!
[06:17] <kiko> #@!$!!! FRIGGIN COWBOYS
[06:17] <kiko> is this damned thing not tested ffs?
[06:18] <matsubara> kiko: apparently the ubuntero flasg isn't tested.
[06:19] <kiko> how surprising
[06:27] <lifeless> dinnerish time... kiko do you need anything from me ?
[06:27] <lifeless> if not I might wander off to eat and ponder and stuff
[06:27] <kiko> lifeless, mmmm not that I can recall right now
[06:27] <lifeless> btw, what do you think of bzr using pyrex?
[06:28] <lifeless> (for single functions, carefully selected)
[06:31] <kiko> lifeless, what's wrong with wrapping manually?
[06:31] <lifeless> potentially nothing. pyrex seems very nice though, easier to do the wrapping.
[06:32] <kiko> what sort of things are you seeing to move to C?
[06:32] <kiko> I mean, is it an algorithm which is slow in python? or data structure access? or..
[06:33] <lifeless> in this case its access to an os feature not exposed by python.
[06:36] <bradb> kiko: this seems to work: https://chinstrap.ubuntu.com/~dsilvers/paste/filepajAoc.html
[06:36] <bradb> the bugwatch stuff looks right to me, BjornT's test passes, and my tests pass.
[06:36] <carlos> BjornT: so, can I send a merge request after adding that extra test ?
[06:36] <bradb> less magical than i wanted to believe, but oh well
[06:37] <BjornT> carlos: yeah
[06:38] <carlos> ok, thanks
[06:39] <sladen> can somebody please re-send the signup request to 'vmware-builds@vmware.com' for the person 'vmware-build-team'.  They now have the email alias set up
[06:40] <sladen> ^^probably needs an admin to do it
[06:40] <salgado> sladen, If I got it right, they tried to register a new account but the email address they used wasn't reachable?
[06:42] <salgado> sladen, btw, shouldn't this be Launchpad team, created using https://launchpad.net/people/+newteam?
[06:43] <sladen> salgado: it should really be a 'role'
[06:44] <sladen> salgado: yes.  The account was registered manually the night before dapper release and the email address was not setup ten
[06:44] <sladen> then
[06:44] <sladen> so never got the confirmation request.  As such the account is 'in limbo'
[06:45] <sladen> salgado: I've just had a message from the person at vmware that the alias now actually goes to an internal mailing list for thenm
[06:46] <salgado> well, the account doesn't exist, in fact. that's why somebody has to go to launchpad.net/+login, type this email address there and submit. I can do that, but a person whose name is vmware-builds-team doesn't sound quite right to me
[06:47] <salgado> anyway, they can easily change this later, if they want. (both the email and the name)
[06:51] <salgado> sladen, maybe you could ask the vmware person sign up (https://launchpad.net/+login) again? (It's one page load and one email address to type, so it shouldn't be a problem, I think)
[06:53] <sladen> salgado: that account already has package uploads assocaited with it
[06:54] <sladen> I've tried sticking it into the +forgottenpassword page and that says it's sent a request
[06:55] <salgado> ah, I see
[06:55] <salgado> so, that account was automatically created
[06:55] <salgado> sladen, yes, the +forgottenpassword page should do it, in this case
[06:57] <powerr> s.a trke bilen varm 
[07:00] <powerr> you have free linux cd
[07:05] <bradb> kiko-fud: can i merge my Importance patch?
[07:14] <carlos> see you later
[07:27] <sfllaw> Hey!
[07:27] <sfllaw> Launchpad is sending messages that have lines that start with "From:"
[07:27] <Kinnison> So?
[07:27] <Kinnison> It's only "From " which causes issues
[07:28] <sfllaw> Oy.  You're right.
[07:28] <sfllaw> My bad.
[07:29] <matsubara> hey mpt
[07:47] <kiko-fud> I just called
[07:47] <kiko-fud> to say
[07:47] <kiko-fud> I LOVE YOU
[07:48] <kiko> man do I love having lunch
[07:56] <ddaa> bradb: the coloured bug icons for importance are pretty
[07:56] <ddaa> I like them
[08:07] <ddaa> Wow daily language packs!
[08:07] <ddaa> That's serious love!
[08:07] <ddaa> carlos: congrats!
[08:12] <LarstiQ> ooh
[08:18] <bradb> kiko: Can I merge my patch?
[08:18] <kiko> bradb, one sec
[08:42] <kiko> bradb, does self.fieldNames need to be set before doing the widget setup in _setUpWidgets? if not, I'd move it to after that if clause to make the code clearer.
[08:43] <kiko> bradb, you can also remove the comment:
[08:43] <kiko>            # Don't edit self.fieldNames directly, because it's shared by all
[08:43] <kiko>             # BugTaskEditView instances.
[08:43] <kiko> you can say "# Start out with default fieldNames" if you like though
[08:44] <kiko>                     read_only_field_names.append("importance")
[08:44] <kiko> bradb, that line has excessive indentation
[08:44] <kiko>                     editable_field_names.remove("importance")
[08:44] <kiko> as well
[08:44] <kiko> r=kiko with that
[08:44] <kiko> there is a better way of refactoring that
[08:44] <kiko> maybe
[08:45] <kiko> but not right now
[08:45] <kiko> nice work
[08:46] <bradb> kiko: thanks. /me makes some tweaks
[09:05] <bradb> Is the bzr optimization work -updates worthy?
[09:07] <LarstiQ> there is more optimization work in the pipeline
[09:08] <LarstiQ> so I'd wait with that unless there is something that really hurts you?
[09:10] <bradb> nothing that really hurts, I was just curious if dapper users would get a chance to see it go even faster
[09:10] <lifeless> we'll put 1.0 into dapper
[09:10] <lifeless> we may put 0.9 and other inbetween versions into dapper
[09:10] <bradb> nice
[09:16] <jordi> mdke: so you saw pitti's announcement.
[09:16] <jordi> mdke: I wanted to discuss with you how to document this official policy
[09:17] <jordi> ie, that from now on langpacks fro hoary, breezy, dapper will be available on the 1st monday of each month
[09:27] <sivang> re
[09:27] <sivang> am I never allowed to edit a spec someone else registered?
[09:27] <sivang> https://launchpad.net/distros/ubuntu/+spec/laptop-video-output-control/
[09:27] <sivang> I want to suggest myself as the drafter if it will be discussed
[09:28] <sivang> but seems I cannot do that.
[09:30] <jordi> not sure sivan
[09:30] <mpt> Goooooooooooooooooooood afternoon Launchpadders!
[09:30] <mpt> It's a lovely afternoon here in the Garden State
[09:32] <sivang> yo mpt 
[09:32] <sivang> mpt: where is that ? :)
[09:33] <matsubara> sivang: you could use the Request feedback feature to ask the guy who registerd to add you as the drafter.
[09:34] <sivang> matsubara: so I can only make changes or add myself as a drafter for specs I registered?
[09:36] <matsubara> sivang: not really.
[09:36] <matsubara> sivang: once you're assigned as a drafter you would be able to edit that spec
[09:48] <sivang> matsubara: so what's the default is now? who else is allowed to edit a spec after the registrant has registered it?
[09:49] <matsubara> sivang: everyone who is somewhat related to the spec.
[09:49] <sivang> matsubara: ah, cool, thanks.
[10:02] <mdke> jordi: right. what thoughts do you have?
[10:35] <neutrinomass> I just tried searching with "oldest" and I get newest bugs first. The opposite with "newest". Should I file a bug ?
[10:36] <matsubara> neutrinomass: known bug
[10:36] <tortho> it's been like that for some days, and ill think they know
[10:36] <neutrinomass> matsubara: Ok, thanks.
[10:36] <matsubara> bug 48784
[10:36] <Ubugtu> Malone bug 48784 in malone "newest and oldest searches are reversed" [Medium,Confirmed]  http://launchpad.net/bugs/48784
[10:57] <sivang> have a nice weekend all, laters.
[11:04] <ajmitch> mpt: off visiting foreign lands again
[11:04] <ajmitch> ?
[11:40] <mpt> ajmitch, yep
[11:40] <mpt> sivang, New Jersey
[11:40] <mpt> sivang, are you still planning to implement the Backup tool for Edgy?
[11:51] <sivang> mpt: this time with a gang behind me hopefully :)
[11:52] <sivang> mpt: there's mostly infrastructure work - dar pyndingd, creating dispather for desktop notificiations etc.
[11:53] <sivang> mpt: anywya, I'm singing off for the weekend , can we continue this next week? :)
[11:54] <sivang> mpt: (oh also incorporating the new proposed GUI by glatztor)
[11:54] <sivang> mpt: which I would be keen on seeing feedback from you on it </hint>
[11:54] <sivang> ;-)
[11:55] <sivang> mpt: anyway, catch you later.
[12:05] <mpt> sivang, ok, I'll finish writing a design spec so you can tell me whether it's useful and whether the gang could finish it before September :-)