[09:19] <maxb> Ah, that's better, SSHServerLayer tests are happier now I've uninstalled bzr-svn
[09:39]  * maxb is starting to wonder if xx-resetpassword-of-sso-account.txt requires you to have canonical-identity-provider to pass :-/
[09:41] <wgrant> maxb: Where does that live? I can't see it anywhere.
[09:45] <maxb> ./lib/lp/registry/stories/foaf/xx-resetpassword-of-sso-account.txt
[09:47] <wgrant> Oh.
[09:47] <wgrant> Doesn't exist in db-devel.
[09:47] <wgrant> WTF.
[09:47] <wgrant> That seems like a somewhat concerning bug.
[09:48] <wgrant> Oh, it's just brand new.
[09:48] <wgrant> Nevermind.
[09:48] <wgrant> But yes, that should live in c-i-p
[09:53] <maxb> well, goody, that means ztk-2.5 is still alive and unbitrotten
[09:54] <wgrant> Excellent.
=== Ursinha is now known as Ursinha-afk
[18:20] <rockstar> sinzui, do you happen to be reviewing projects right now?
[18:48] <sinzui> rockstar: I did a few hours ago
[18:48] <rockstar> sinzui, ah, okay.  I just noticed the project count was dropping.
[18:49] <rockstar> sinzui, I've been doing them in 20 project increments because it's so fucking tedious.
[18:49] <sinzui> rockstar: okay. reviewed some commercial projects, those that has test in their descriptions,
[18:51] <rockstar> sinzui, cool.  I'm trying to get that backlog out so that gmb doesn't have that much to do.
[18:53] <sinzui> I was thinking of writing a script to send a license info email all "don't know" projects and mark them as reviewed
[18:54] <sinzui> I see 1/3 of projects need a license and all that we can do is ask for one an mark it reviewed
[18:55] <rockstar> sinzui, yeah, I was wondering if project review stuff was available through the API.  I'd be happy to script it out if it was.
[18:55] <rockstar> Basically, does it have branding? Approve. Does it have a designated team as driver? Approve.  Does it have branches or bugs or translations? Approve.
[18:56] <rockstar> That's what I've been doing.
[18:56] <sinzui> I approved all those this morning
[18:56] <sinzui> well all the obvious ones
[18:57] <sinzui> After I disabled or approved all 'test' projects, I approved all projects that had code, or bugs, or was creates by someone with a lot of karma, or was created by a canonical employee
[18:57] <sinzui> I cannot identify projects with branding or announcements :(
[19:36] <mwhudson> why do i have 300 emails to look through :(
[19:45] <sinzui> rockstar: I just tried a script that sent a variation of the license-info email to most the unreviewed undecided projects. 6 were skipped. I need to look at them to learn why
[19:46] <sinzui> oh, I see. It was right to script them. They were dual/multi-license.
[20:18] <thumper> mwhudson: when did you want to chat?
[20:18] <thumper> mwhudson: I'm down to 80 odd emails from 300
[20:19] <mwhudson> thumper: now ish is good i guess
[20:19] <mwhudson> thumper: gimme a minute to refill my cup :-)
[20:20] <thumper> mwhudson: ok
[20:21] <thumper> mwhudson: I installed the gnome-desktop to try to debug some karmic issues
[20:21] <thumper> mwhudson: and it installed pulse audio
[20:21] <thumper> mwhudson: I need to work out how to kill it for kde
[20:22] <mwhudson> thumper: aaron posted advice to warthogs on that i think
[20:22]  * mwhudson wonders why all the staging cronscripts are barfing
[20:40] <matgeek> Hi!
[20:43] <matgeek> Just new to launchpad development. I am interested in working on modular backend plugins.  Git is really interesting to me, now that GNOME, the Linux kernel, and KDE are using it within their projects.  It is the DCVS that has buy-in with all the development communities.  Seamless integration is te name of the game.  It would be good to be able to work on a project with the VCS that the project uses, with out having to know about 
[21:10] <lifeless> matgeek: your paragraph was too long and IRC cut it off at 'to know about'
[21:10] <lifeless> matgeek: but have you seen bzr-git? it gives seamless git integration..
[21:16] <matgeek> lifeless:  So I don't have to know any bzr commands to work with the launchpad web interface?  I can continue to use git as my development VCS without having to use bzr?
[21:17] <lifeless> matgeek: other way around, you can use bzr without having to know any git commands :)
[21:17] <thumper> matgeek: kinda, but Launchpad only supports bzr as a branch repository storage, and can mirror git repositories
[21:19] <matgeek> lifeless:  That will not lead to buy-in from the development projects.  I use git myself on top of svn, and I don't want to have to know about bzr.  Is the launchpad - bzr backend based on a modular API?
[21:19] <matgeek> lifeless: that is if I was from GNOME, project or working on kernel.
[21:21] <matgeek> lifeless: hypothetical situation I know, but wanting to see if there is a case for making git another first class launchpad backend.
[21:21] <lifeless> if you want to use git and push to launchpad, there is a git-bzr too, I believe
[21:22] <matgeek> Mmmmm, I will have to explore further with my own Debian package, netscript-2.4
[21:22] <lifeless> matgeek: the lp backend uses bzrlib, but bzrlib can talk to git, so in terms of /code/ it could be done. However we don't want the overhead of supporting many different VCS backends throughout the system
[21:22] <lifeless> how to scale storage, ensure consistent backups, etc all are very simple at the moment
[21:24] <matgeek> lifeless:  From my POV, it doesn't matter what backend launchpad uses, as long as it is seamless with the VCS a project is using.
[21:26] <lifeless> I may not quite understand your criteria / rationale then
[21:28] <matgeek> lifeless: OK, I am coming from the hypothetical POV of being a project developer interacting with launchpad.  It struck me that we want to get it to the point where everybody just wants to use it because it is so good.
[21:29] <matgeek> lifeless:  Not knowing about bzr gets a big VCS elephant out of the room if you want a major project to actually start using launchpad itself.
[21:30] <lifeless> matgeek: so, you don't need to use the VCS services of launchpad to use launchpad
[21:31] <matgeek> lifeless: Yess, you just use the web frontend to point it at your project VCS of choice, the Web application uses bzr to get source trees etc, but the developers don't even have to type a bzr command, it is all transparent and just works!
[21:32] <lifeless> matgeek: we have that today
[21:32] <lifeless> https://help.launchpad.net/Code/Imports
[21:33] <matgeek> lifeless: Ta! I will have a play around with my Debian package.  I am trying to come up with something useful for the launchpad project.  Where can I help?
[21:33] <lifeless> thumper: ^
[21:34] <lifeless> I'm not sure where the hotspots needing help are right now. thumper may.
[21:34] <thumper> lifeless: on a call right now, so I can't focus here right now
[21:37] <matgeek> thumper:  I will hang around till you have finished your call, if you want to chat with me.
[21:42]  * thumper is off the call and reading scroll-back
[21:44] <thumper> matgeek: what sort of help were you thinking about?
[21:44] <thumper> matgeek: developing features? fixing bugs?
[21:44] <thumper> matgeek: QA?
[21:45] <matgeek> thumper: fixing a few bugs at first to get familiar with the code base, and then looking at some minor features before getting into the major stuff.
[21:45]  * thumper nods
[21:45] <thumper> ok
[21:45] <thumper> matgeek: firstly get on the beta tester team if you aren't already
[21:46] <thumper> matgeek: then get the code building locally
[21:46] <thumper> matgeek: then look at bugs.edge.launchpad.net/launchpad-project
[21:46] <thumper> matgeek: there should be some easy ones tagged trival or easy
[21:47] <thumper> matgeek: the way we tend to work is:
[21:47] <thumper> 1) identify what to fix
[21:47] <thumper> 2) talk through the proposed fix with someone
[21:47] <thumper> 3) fix it
[21:47] <thumper> 4) submit the fix for merging, and go through the code review process
[21:49] <matgeek> thumper:  Cool, I will need a day or two to get to the bug list, as I have to get some things done today.  Are people on this channel in the evening NZ time?
[21:49] <thumper> matgeek: yes, where are you based?
[21:49] <matgeek> Dunedin.
[21:49] <thumper> matgeek: we should meet
[21:49] <thumper> matgeek: I'm in dunners too
[21:50] <thumper> matgeek: are you going to kiwipycon?
[21:50] <matgeek> That would be good.  I am going to Earthlight this afternoon where I work on a Radius accounting project, using python.
[21:51] <matgeek> When and where is kiwipycon? Could we meet today or tomorrow, or later this week?
[21:51] <thumper> matgeek: you sent me an email the other week :)
[21:52] <thumper> matgeek: if you hadn't heard, it is a little late as kiwipycon is this weekend in Christchurch, and sold out
[21:52] <matgeek> Yes, I did email you.  I have applied for a couple of Ubuntu positions already.
[21:53] <matgeek> thumper: About kiwipycon, a pity, but I can easily get accommodation up there with family.  It is only a bus ride or drive.  Are they full-house at the moment.
[21:53] <thumper> I believe so.
[21:54] <thumper> matgeek: you should also hang out in #nzpug
[22:00] <thumper> matgeek: also get on the launchpad-dev and launchpad-users mailing lists
[22:00] <matgeek> thumper: Will do.  Will subscribe tonight.
[22:00] <thumper> ok
[22:00] <thumper> I'm not usually on at NZ evening
[22:01] <thumper> but the europeans are just starting
[22:01] <thumper> and there are quite a few of them :)
[22:01] <thumper> however,
[22:01] <thumper> I do respond to email :) (eventually)
[22:26] <jml> hello antipodes
[22:34] <MTecknology> jml: hi
[22:34] <MTecknology> if that includes me - long word
[22:34] <jml> MTecknology, only if you are in Australia or New Zealand, normally
[22:35] <MTecknology> jml: :(
[22:35] <MTecknology> well... then I take back my hi
[22:38] <mwhudson> jml: hello
[22:39] <mwhudson> jml: a very euro-centric definition of antipodes!!
[22:39] <jml> mwhudson, it's rather me-centric, actually
[22:41] <RAOF> jml: Hello antipodes!
[22:42]  * wgrant whinges a bit about the lack of APAC RMs and Soyuz people.
[22:50] <thumper> wgrant: RM as in release manager?
[22:50] <thumper> wgrant: you wanting a release-critical stamp?
[22:50] <thumper> jml: hi
[22:50] <jml> thumper, RAOF: hello
[22:50] <thumper> I've finally booked my accomodation for kiwipycon
[22:53] <wgrant> thumper: RM as in release manager, yes. It's not quite that simple -- I have ~1200 lines of branches that we need in the next couple of weeks for Debian compatibility. It would only need to be CPed onto a couple of the Soyuz machines, but there are safe enum and other DB changes that the appservers need as well.
[22:54] <wgrant> The urgency of this only came to light two days ago, unfortunately.
[22:58] <mwhudson> wgrant: well at least the RM is noodles so he should understand the issues more easily than some
[23:35] <MTecknology> When is stu online? I want to ask him some questions.......
[23:36] <thumper> MTecknology: it depends
[23:37] <thumper> MTecknology: sometimes he is on in 3 to 4 hours, other times later
[23:38] <MTecknology> thumper: ok - I was trying to figure out how he's managing the branches - but now that I'm looking at last revision times; it seems like there's little point in worrying about it
[23:39] <wgrant> I think we are talking about different Stus here.
[23:39] <MTecknology> thumper: heck - if they need the branches - then they can do bzr push and it'll all be happy
[23:39] <MTecknology> stuart metcalfe
[23:39] <wgrant> You mean Stuart Metcalfe.
[23:39] <wgrant> thumper means stub.
[23:39] <MTecknology> oh
[23:39] <thumper> ah
[23:39] <thumper> sorry
[23:39] <thumper> misread stu as stub
[23:43] <MTecknology> So when is this version of stu normally around?
[23:43] <wgrant> His timezone suggests in about 9 hours.
[23:44] <wgrant> But he's not around here.
[23:44] <MTecknology> Where is he normally at?
[23:44] <wgrant> I've never seen him on freenode, I don't think.
[23:44] <wgrant> He lurks in the realms of ISD, I would imagine.
[23:45] <MTecknology> oh - so I guess it's only when I ask him that he comes around