[00:00] <Frozenball> Finally, https://launchpad.net/ideazilla/+download
[00:00] <Frozenball> I don't like being so organized :(
[00:01] <beuno> Frozenball, hahah, neither do I. That's how I learned how to create downloads  :p
[05:52] <techII> i just added a release to a project thinking i can reference the releases that where made on sourceforge on launchpad
[05:53] <techII> can anyone undo this? (https://launchpad.net/crossfire-maps/1.x/1.11.0)
[08:43] <poolie> thumper, jml, ping?
[08:43] <poolie> https://code.edge.launchpad.net/~mbp/bzr/bzr.1.6
[08:44] <poolie> ^^ it looks like i can no longer edit or delete that
[08:44] <poolie> oh i see
[11:06] <MvG> Who can tell me about default contacts for newly registered projects? Do I have to subscribe to bug mail and become answer contact, or will I receive mails for those automatically as I registered the project?
[11:07] <MvG> And how about questions asked in languages I don't speak? Can I learn about them anyway?
[11:10] <LarstiQ> MvG: afaik the registrant will be the default target. So unless you specifcally set contacts, that will be it.
[11:10] <MvG> LarstiQ: Thanks.
[11:10] <MvG> I had hoped as much.
[11:14] <MvG> There are errors for a SVN import on https://code.launchpad.net/~vcs-imports/vpnc/trunk which I don't understand. Can anyone make sense of them? Is there anything I can do to get the branch operational again?
[11:55] <thumper> MvG the best way to get traction on this is to either file a bug or ask a question (see /topic)
[11:55] <MvG> thumper: thx, will do so later on.
[14:32] <epsy> hi, i have a problem, i linked a branch to a blueprint, but on the branch summary page it links to a blueprint from another project
[14:32] <epsy> what can i do?
[14:33] <epsy> in the dropdown list it shows with the title of the "events" blueprint from out project, but on the summary page it shows up with the title of the "events" blueprint from a totally different project
[14:33] <epsy> https://code.launchpad.net/~armagetronad-dev/armagetronad/trunk-armagetronad-eevent
[14:35] <lamalex> Is there a tutorial or a manual on using LPs new code review features?
[15:25] <mpt> lamalex, I don't think there is yet
[15:25] <mpt> lamalex, mrevell would be the best person to answer that question, next time he's here
[15:25] <lamalex> does LP actually do the merging? or is that still done by hand
[15:30] <beuno> lamalex, if you're talking about bzr merge requests, you have to do them by hand
[15:31]  * beuno waves at mpt
[15:31] <lamalex> beuno: thanks
[15:31] <lamalex> that was I was wondering, it wasn't exactly clear
[15:32] <beuno> lamalex, I don't think you'll ever have auto-merge, because conflicts can arrive which can't really be solved automatically
[15:32] <mpt> lamalex, if there's anything that's unclear, please report it as a bug
[15:33] <lamalex> beuno: yeah, I wasn't sure if it was going to do some kind of web-based meld, or something crazy
[15:33] <lamalex> mpt: I will
[15:34] <mpt> thanks
[15:40] <jcastro> barry: around?
[15:41] <barry> jcastro: yep, but in a meeting.  give me 5 minutes?
[15:41] <jcastro> sure!
[15:44] <barry> jcastro: hi!  what's up?
[15:46] <jcastro> barry: there are a few mailing lists requests that I rejected on LP a while back, and now with the clarification from the CC they should be on launchpad.
[15:46] <jcastro> but when the guy reapplies he gets and error
[15:46] <jcastro> "The application for this team's mailing list has been declined. Please contact a  Launchpad administrator for further assistance."
[15:47] <barry> jcastro: known issue. there's even a bug open on the general problem
[15:47] <jcastro> ah.
[15:47] <barry> jcastro: for each such team, if they submit a question for launchpad though, i can get the losas to tweak the database and then they can reapply
[15:47] <jcastro> barry: ok
[15:47] <jcastro> a question under launchpad itself?
[15:48] <barry> jcastro: yep.  assign them to me
[15:48] <jcastro> ok
[15:49] <barry> thanks!
[15:55] <jcastro> barry: he couldn't find a way to subscribe you to it, so the answer is here: https://answers.edge.launchpad.net/launchpad/+question/41393
[15:56] <barry> jcastro: got it, thanks
[16:14] <ffm|sh> is it possible to sign ppa packages?
[16:14] <ffm|sh> how about when a team has a ppa?
[16:15] <lamalex> ffm|sh: no
[16:15] <ffm|sh> lamalex: :(
[16:16] <beuno> ffm|sh, there's a bug for it though, so you may be able to at some point
[16:19] <lamalex> ok, I have another question about LP branch management. I just merged a branch, but my page says 0 branchs approved for merging
[16:20] <beuno> lamalex, did anyone approve your branch merge?
[16:20] <lamalex> yeah, but it was me.. does that affect it?
[16:20] <lamalex> I'm playing with the system trying to determine if we want to use it for our project
[16:20] <beuno> you requested the merge and approved it?
[16:20] <lamalex> yes
[16:21] <beuno> lamalex, hm, link?
[16:21] <lamalex> from a personal branch to a branch of a team that I am a member of
[16:21] <lamalex> beuno: link to?
[16:21] <beuno> lamalex, the branch you're playing with
[16:22] <philn> hi
[16:22] <philn> can a team have a PPA?
[16:22] <beuno> philn, sure, you just have to activate it once
[16:23] <philn> interesting
[16:24] <lamalex> beuno: https://code.launchpad.net/~alexlauni/do-plugins/del.icio.us-indexing
[16:24] <lamalex> and https://code.launchpad.net/~do-plugins/do-plugins/trunk
[16:24] <AndyP> what should i do if i come across comment spam on launchpad? is there an official way to report it?
[16:27]  * Peng_ points at the topic. You should use answers.
[16:29] <AndyP> ah sorry, the topic scrolls off my screen here ;)
[16:29] <Peng_> Mine too. I just see "answers.launch".
[16:29] <lamalex> /topic
[16:32] <beuno> lamalex, you already merged the branch, so it's not pending anymore
[16:32] <beuno> the link you see is for branches that are pending
[16:32] <lamalex> beuno: I know, but should it say N approved branches here -> https://code.launchpad.net/~alexlauni
[16:32] <lamalex> er, approved merges
[16:34] <beuno> lamalex, it should. Sounds like a good bug to file  :)
[16:35] <lamalex> I thought I was just using it wrong :P
[16:35] <AndyP> oh good, ScottK already reported the spam i was talking about, that saves me the trouble
[16:41] <lamalex> ok beuno bug filed, enjoy
[16:41] <ffm|sh> Hey, there's a typo on the front of edge.lp.net
[16:41] <ffm|sh> "Launchpad is hosting service for open source projects that's big on collaboration."
[16:42] <philn> looks like only the team owner can open the team's PPA?
[16:43] <beuno> philn, that sounds correct
[16:43] <beuno> lamalex, thanks
[16:52] <volver> hi to all
[16:52] <epsy> hi to nobody!
[16:52] <volver> i would like to add a project to an existing group
[16:53] <volver> how can i do that
[16:53] <volver> thx
[16:53] <volver> epsy: ;)
[16:53] <epsy> you mean changing a projet's owner or..?
[16:53] <epsy> or creating a new project?
[16:54] <volver> epsy: the project already exists and the group (team) to
[16:54] <volver> too*
[16:55] <volver> i m the team owner but the project is created by another tem member
[16:55] <epsy> ok, go to your project's overview page
[16:55] <epsy> click on that link in the top-right corner "change details"
[16:55] <epsy> click the subtab "People", then you're at it
[16:57] <epsy> got it?
[16:57] <volver> epsy: i must be the project owner ?
[16:57] <epsy> or part of the owner team indeed
[17:00] <volver> epsy : actually the project is owned by another team member :) and i ask it to add his project as a team project
[17:00] <epsy> ask him to do the steps i enumerated
[17:01] <volver> i will do epsy :)
[17:02] <volver> if the project is added to the team, all members can administrate it ? or we can specify privileges ?
[17:03] <beuno> mrevell, you've got mail!
[17:05] <epsy> volver, all members will be able to admin it
[17:06] <epsy> that mainly just means, that they will be able to change frontpage details
[17:06] <epsy> (i am right?)
[17:07] <volver> okay i see. thx epsy
[17:11] <mrevell> cheers beuno!
[17:14] <persia> bigjools: Just a follow-up on 125987: would it make your life easier if you didn't need to show the overview, or is that trivial due to the existing page?
[17:15] <bigjools> persia: trivial, I can simply re-use it
[17:15] <bigjools> persia: I was actually considering not having a separate "related projects" tab but again it could need batching
[17:15] <persia> OK.  Sounds good then.  I'll post to the bug.  I'd be curious to see a mock-up if you end up with one, but otherwise will look at staging.
[17:16] <bigjools> persia: I can do a mock up on dogfood in the next couple of days
[17:17] <persia> bigjools: If it's not much extra work to do that, I'd like to take a look and make sure it matches my imagination.
[17:17] <bigjools> the plan with leaving the overview there is that we can easily do incremental tweaks to include your other suggestions
[17:17] <bigjools> persia: great - I don't want to do anything that's no use
[17:17] <bigjools> and no extra work really6
[17:18] <persia> Also, I think batching related projects is probably wise.  https://launchpad.net/~brian-murray/+related-software is an example of how it can be now, but I can imagine more as LP starts to track more projects.
[17:18] <persia> (in that the example page ignores 884 related projects)
[17:18] <bigjools> 959!
[17:18] <bigjools> jeebus
[17:19] <persia> Well, one gets related when one files a bug upstream, and some people tend to do that a lot.
[17:19] <bigjools> yeah the related projects page was merged into related-software recently, for some bizarre reason
[17:19] <bigjools> well, if there's a real reason I am not aware of it anyway
[17:20] <persia> Seems separate to me, but then aside from the "Most Active" projects, I don't think it typically matters much.
[17:20]  * persia isn't part of the target audience for "Related Projects"
[17:20] <mpt> bigjools, it was to avoid having multiple navigation menus, and to reduce the number of clicks to see the list of maintained packages.
[17:20] <persia> mpt: That was why "Related Projects" was added to /+related-software ?
[17:21] <mpt> That's why the two pages were merged.
[17:21] <bigjools> mpt: hmmm I am proposing a sub navigation menu to fix bug 125987
[17:21] <bigjools> mpt: as it stands, that page is largely useless
[17:21] <mpt> Why is it useless?
[17:21] <persia> There's no clear association between maintained packages and related projects (plus, there's about 35 individually maintained packages in Ubuntu that aren't sync'd from Debian)
[17:22] <bigjools> because it has to reduce what it shows on the page so that the page doesn't time out
[17:22] <persia> mpt: I could go at length, but bug #125987 sums up some of my thoughts.
[17:22] <bigjools> some people have thousands of packages
[17:23] <mpt> bigjools, that bug was reported nearly a year before the pages were combined, so splitting them up again wouldn't fix the bug.
[17:23] <persia> mpt: No.  The fact that the pages were merged and the fact that the current page is useless are completely unrelated.
[17:24] <mpt> ok
[17:24] <bigjools> discarding information with no other means of seeing it is not helpful - which is why I need to put batching in - which is why they need to be separated again :/
[17:24] <persia> We were just confused why "Related Projects" was merged with "Related Packages", given that the two sets are typically highly disjointed.
[17:24] <mpt> bigjools, I don't understand that logic. Why does introducing batching require separating the pages?
[17:25] <bigjools> mpt: they are different queries for each section, how can I batch them all at once?
[17:25] <mpt> bigjools, why would you batch them all at once?
[17:26] <bigjools> so I can have multiple batcheson the same page?
[17:26] <mpt> Why would you have multiple batches on the same page?
[17:26] <ffm|sh> Any idea why my packages have yet to build on thje amd64 platform, but have on all the others? : https://edge.launchpad.net/~sugarteam/+archive
[17:27] <bigjools> mpt: because there are four separate queries/sections on that page that need to be individually batched
[17:27] <mpt> bigjools, sorry, I still don't understand
[17:28] <bigjools> ffm|sh: one of the builders is down and there's a queue of 15 jobs waiting on the other - be patient and it will get there :)
[17:28] <mpt> bigjools, for example, go to <http://news.google.com/>. Notice how you can click on the section headings ("World", "Business", "Sports") to see lists of stories in individual sections.
[17:28] <ffm|sh> bigjools: thx
[17:28] <ffm|sh> In other news, how do I set a team to be the maintainer/owner of a ubuntu pacakge?
[17:29] <mpt> bigjools, so showing subsequent batches for one section does not require showing the other sections.
[17:29] <bigjools> mpt: if I am not much mistaken, that is separate pages for each category
[17:30] <mpt> bigjools, right, and they don't prevent the front page from existing.
[17:30] <persia> ffm|sh: You can set the maintainer in the Maintainer field of the source package: it's generally best to coordinate with the existing maintainer (or team responsible for the component in the absence of an Ubuntu maintainer).
[17:30] <persia> mpt: So you'd advocate that each section has a link to the batch?
[17:31] <persia> (rather than top navigation)
[17:31] <mpt> persia, yes.
[17:31] <ffm|sh> persia: Well, ~jani is the currernt maintainer of all sugar-* packages, we are planning on changing that to the ~sugarteam group.
[17:31] <mpt> persia, would that work for your purposes?
[17:31] <persia> mpt: See, the only issue I have is that I can't think of any use case that would actually make any use of the information on that page.
[17:31] <persia> ffm|sh: You'd want to talk to jani
[17:31] <bigjools> which is why I didn't do it that way ...
[17:32] <ffm|sh> persia: how hard would such a change be?
[17:32] <ffm|sh> assuming I discussed it with her.
[17:32] <persia> ffm|sh: Trivial, but requires an upload of each package.  Best discussed in #ubuntu-motu
[17:33] <philn> does the uploader need to upload a gpg key on the team's homepage to be able to upload to the team's PPA?
[17:33] <mpt> persia, if all someone does is maintain packages in Ubuntu, the current page shows that without any extra clicks required (though of course it should be batched). And if all someone does is maintain one project, the current page shows that without any extra clicks required (though it too should be batched if necessary).
[17:33] <persia> mpt: So, not only do batching, but replace the current content on the page with useful content?
[17:34] <persia> Also, I don't understand what you mean by "maintain one project"
[17:34] <mpt> persia, what information do you have in mind, specifically?
[17:34] <persia> philn: The uploader only needs  GPG key on their own page, and to be a member of the team.
[17:35] <philn> persia: ok, thanks
[17:36] <persia> Well, I've a somewhat narrow set of use cases, so I can't say what is useful for viewing PPAs or Related Projects.
[17:36] <persia> I don't think "Maintained Packages" is meaningful in any way, as the information is typically incorrect in the context of Ubuntu.
[17:37] <persia> For "Uploaded Packages", I want to see every revision of every package uploaded by that person.
[17:37] <mpt> persia, e.g. <https://launchpad.net/~cmsj/+related-software> -- Chris maintains the Terminator project, but no other projects that I know of
[17:38] <persia> mpt: Except he doesn't maintain the Terminator project: he's the upstream project lead.
[17:38] <bigjools> mpt: check this one out: https://launchpad.net/~brian-murray/+related-software
[17:38] <persia> nxvl tends to maintain the actual package.
[17:38] <mpt> persia, eh?
[17:38] <persia> mpt: A project is not a package.
[17:38] <mpt> persia, a project isn't a package. The upstream *is* the project.
[17:39] <ffm|sh> persia: merci
[17:39] <persia> Right.  Chris is upstream for Terminator.  He did one upload through REVU, which got more interest in his project, and now he doesn't tend to do the maintenance.
[17:39] <persia> Anyway, it's not under "Maintained Packages": it may just be that the terminology is confusing me.
[17:41] <persia> I tend to think of "Maintenance" as operational adjustments, bugfixing, etc.  I tend to think of "Development" as feature creation, etc.
[17:41] <mpt> persia, can you give an example of a page that mentions "Maintained Packages"? I don't see it anywhere
[17:41] <persia> Mine does.
[17:42] <mpt> ah
[17:42] <mpt> And is that information correct?
[17:42] <persia> Well, it happens to be, but that's a coincidence.  I'll find one that's not correct.
[17:42] <mpt> ok, so if the information in sections of the page is incorrect, that should be fixed
[17:43] <mpt> I'm missing how that relates to the overall page structure, though
[17:43] <persia> While I'm not certain, I suspect it's fairly unlikely that https://launchpad.net/~joeyh/+related-software is correct.
[17:45] <persia> mpt: https://bugs.launchpad.net/soyuz/+bug/125987/comments/12 sums up my thoughts on the use cases for the parts of the page.
[17:45] <persia> I just don't understand to whom the page is targeted, nor for what purpose all that information is interesting at once.
[17:45] <bigjools> persia: he is listed as the Maintainer in the .dsc
[17:45] <persia> bigjools: Yes, because we sync'd from Debian.
[17:46] <persia> That said, that specific person doesn't tend to like getting Ubuntu issues unless they are also Debian issues.
[17:46] <mpt> and that person doesn't even use Launchpad
[17:46] <bigjools> so in this case, who is the maintainer as far as we are concerned?
[17:46] <persia> And has stated that he doesn't intend to do so.
[17:46] <persia> Depends on the package, either MOTU or core-dev, depending on the component.
[17:47] <persia> The pkgbinarymangler package changes this in the binary package during the Soyuz build.
[17:47] <bigjools> right
[17:49] <persia> Actually, it depends on the component of the *source* package: some packages are inaccurately listed as being maintained by MOTU because the binary package is in universe (which is a minor bug in pkgbinarymangler)
[17:49] <mpt> So those packages will have joeyh as X-Original-Maintainer, but not as Maintainer?
[17:51] <persia> mpt: The binary packages do.  The source packages are left unchanged.
[17:51] <bigjools> mpt: I confess I am a bit confused by your google news example because it seems to do exactly what I suggested
[17:52] <mpt> bigjools, sorry, I misread your comment. I thought you were proposing *replacing* the overview with the specialized pages.
[17:52] <mpt> I agree with having the specialized pages *in addition* to the overview.
[17:52] <bigjools> mpt: check out my comment: https://bugs.edge.launchpad.net/soyuz/+bug/125987/comments/13
[17:52] <mpt> bigjools, yes, that's the comment I'm referring to.
[17:52] <persia> mpt: The proposal is to have them in addition.  I think I'm the only one questioning the entire point of the overview.
[17:53] <mpt> soren, there are two use cases for the overview
[17:53] <mpt> arg
[17:53] <mpt> (sorry, soren)
[17:53] <mpt> soren, there are two use cases for the overview
[17:53] <bigjools> because nobody's really sure what we need here, I am going for an incremental approach so we can tweak it along the way
[17:53]  * persia is impressed at the proximity of 'p' and 's' on mpt's keyboard
[17:53] <mpt> that must be an X-Chat bug, surely
[17:53] <mpt> persia, foo
[17:54] <mpt> huh
[17:54] <bigjools> :)
[17:54] <persia> quux!
[17:54] <mpt> so THAT's what that "Automatic nick completion (without TAB key)" checkbox does
[17:54] <mpt> evil evil evil
[17:55] <bigjools> mine just repeats the last completion
[17:55] <mpt> pe, test
[17:55] <mpt> hooray!
[17:55] <mpt> ok
[17:55] <persia> bigjools: That makes sense to me, but I'm still curious which problem the overview is solving.  For me, it's one more click than I used to have to do (back when I still found the page useful)
[17:55] <mpt> SO, there are two use cases for the overview
[17:56] <mpt> (1) If you're wanting to see what a person does in general, not wanting to look at their bugs etc in detail
[17:56] <mpt> (assuming their profile page doesn't tell you)
[17:58] <mpt> (2) If someone *just* maintains projects, or *just* uploads packages, the Overview can (in theory) show you what the relevant specialized page would, without you having to navigate again to the specialized page.
[17:58] <persia> See, I haven't yet found an example where (1) actually does that.
[17:58] <mpt> Ok, so if there are bugs that prevent #1 from working, they should be fixed
[17:58] <persia> For (2) I still don't understand what you mean by "maintains projects", but I'd be happy if it solved the case of needing to chase to discover uploads.
[17:59] <persia> I don't know of any bugs, I just don't know of any cases where the data used to generate that page provides a good viewpoint for what someone does.
[18:00] <persia> If Chris had been able to interest anyone who knew more about packaging in Terminator before it go into Ubuntu, it would only be a minor mention in the list of Related Packages.
[18:00] <mpt> I mean "maintains projects" in the sense that Martin Pool maintains the Bazaar project, Neil Patel maintains the AWN project (afaik), Chris Jones maintains Terminator
[18:00] <persia> s/go/got/
[18:00] <persia> So the project leads?  I can't see that from that page.
[18:01] <persia> Unless someone happens to have not been involved in another project.
[18:01] <bigjools> guys, sorry I have to dash now, but I'll read scrollback later, thanks for your input in fixing this problem
[18:01] <persia> Mind you, if the Related Projects section displayed something like the "Most Active Projects" section on the main page, I might be able to tell that.
[18:01] <mpt> yes, it should
[18:01] <persia> But it probably also needs to show per-project karma
[18:02] <mpt> In <https://edge.launchpad.net/~mbp/+related-software> Bazaar itself is 9th on the list, which is bong
[18:02] <mpt> 9th on the "Related projects" list, I mean
[18:02] <persia> "bong" is wrong?
[18:02] <persia> or right?
[18:02] <mpt> wrong
[18:03] <persia> That's been my consistent experience with Related Projects.
[18:03] <persia> Unfortunately, I don't know enough about how they work to even begin to file any bugs about it.
[18:04] <persia> Also, even if there was some association based on karma, and enough activity in launchpad that karma balanced cleanly (more a matter of time than design), I'd expect active Ubuntu BugSquad members to show lots of spurious involvement from upstream bug coordination (when they may have little to no interest in the upstream project as such)
[18:09] <persia> Anyway, you've given me the impression that (2) is soluable, although I'd still think that "Related Projects" ought be most of it, and that "Maintained Packages", "Uploaded Packages", and "PPA Packages" don't help with that.
[18:10] <persia> Err.  (1) is soluable.
[18:11] <persia> (2) is only ever the case if someone doesn't upload packages, since any upload is going to close a bug or complete a spec or something (or where it doesn't, that's a different bug), and have an impact on "Related Projects".
[18:12] <persia> Given that (1), once fixed to work, would be very useful, I'm either going to have to scroll down a lot to look at packages, or everyone else is going to have to scroll down for (1).
[18:12] <persia> Personally, I'd rather either click something or type the right URL than scroll a lot.
[18:16] <persia> (and think that (1) is more generally useful than my somewhat specialised use case: there's really only 8 people who regularly review things that way)
[18:18] <mpt> ok, I commented on 125987
[18:18] <mpt> Now for the specific problems with the overview page
[18:18] <mpt> persia, am I correct in assuming that Launchpad shouldn't claim that joeyh maintains any packages Launchpad knows about?
[18:19] <persia> mpt: I can't 100% speak for joeyh, but he's not actively involved in Ubuntu, and recently changed his maintenance habits to restrict himself to native packages for Debian.
[18:20] <persia> Rather, I can't speak for him at all :)
[18:20] <persia> But the above has been publically stated at various times.
[18:21] <persia> Personally, I feel that it's not entirely accurate to indicate him as the maintainer for random people looking for information about Ubuntu packages.
[18:22] <persia> (Despite the fact that our only change is to recompile)
[18:22] <mpt> yeah
[18:22] <mpt> I see the package release page does that too
 says "Maintainer: Joey Hess"
[18:26] <persia> And this is perhaps an exceptional case in a number of complicated ways, but the same is generally true for any Debian Maintainer whose packages we don't modify.  I'm all for giving them full credit for the work, but I think Ubuntu ought get the blame for any issues.
[18:27] <mpt> right
[18:27] <mpt> reported bug 255417
[18:28] <persia> (and it gets more complicated if one considered groups like the Zope maintainers, the Games team and the Python Applications Packaging Team, which are groups of combined Debian and Ubuntu maintainers working on sets of packages).
[18:30] <persia> Reading bug 255417, I think that makes a good general statement of the issue: for the complicated groups, if they wanted to fix it, that would be a bug in plgbinarymangler, and then presumably a sufficiently accurate solution of 255417 would take advantage of the update.
[18:31] <persia> ubottu: Don't you have a timeout to not repeat the same bug frequently?
[18:32] <mpt> I think the timeout is 2 minutes or something like that
[18:32] <persia> And I'm a slow typist :)
[18:33] <persia> So, back to the original thought: given the use cases you've described, what do you think about having a "Related Software" page default to showing the Related Projects (with some improved useful view) and links to PPA packages and Uploaded packages?
[18:37] <mpt> persia, but then ScottK would complain, like he did before the pages were combined, that he was having to click too many times to get to the list of uploaded packages
[18:37] <persia> Except ScottK isn't one of the 8 people who does this regularly :)
[18:37] <mpt> 8 people?
[18:37] <persia> MC and TB
[18:37] <mpt> TB = ... Tech Board?
[18:37] <mpt> What's MC?
[18:37] <persia> Yes, and MOTU Council.
[18:38] <persia> Not having that information complete on the uploads page means we have to scrape through the -updates email lists to find sets of packages to review, which is exceedingly painful, and makes us not want to review new develoeprs.
[18:39] <persia> More developers is a good thing, but I think people other than the 8 of us mostly aren't concerned about reviewing the sets of uploads except in a very general sense of whether there are lots or not.
[18:39] <mpt> so batching the list is a separate issue
[18:39] <persia> Entirely.  I just conflated the two because bigjools would listen to me.
[18:39] <mpt> there could be a "More uploads" or an "All uploads" link after the list of however many most recent uploads
[18:39] <persia> Isn't that batching?
[18:39] <mpt> exactly
[18:41] <persia> Right.  The idea of dropping the big summary page is somewhat separate.
[18:41] <persia> And certainly separable.
[18:41] <mpt> I got the impression that ScottK used the list of uploads fairly frequently
[18:42] <persia> That would be a use case I didn't expect.  I can summon him if you like.
[18:43] <persia> My guess would be that he's reviewing as shadow MC, but I could be completely mistaken.
[18:50] <kiko> ahoy there
[18:50] <persia> Hey kiko
[18:52] <kiko> how's it going persia
[18:52] <kiko> \sh, yo!
[18:52] <lamalex> Hi, I pushed a rev a couple of hours ago, but the launchpad web still doesnt show it
[18:53] <kiko> siretart, you gone yet?
[18:53] <kiko> lamalex, gar
[18:57] <beuno> lamalex, you can cheat and make sure the revision is there by click "All revisions" on the bottom:  http://bazaar.launchpad.net/~alexlauni/do-plugins/del.icio.us-indexing/changes
[18:58] <beuno> still means the code scanner is stuck again though
[18:59] <kiko> beuno, I pinged herb and spm about it, so let's see what they say
[18:59]  * beuno cheers kiko 
[19:02] <lamalex> beuno: different branch
[19:03] <beuno> lamalex, same trick
[19:03] <beuno> (that one is missing a revision too, btw)
[19:03] <lamalex> hmm yeah they seem to be in that changes page
[19:05] <beuno> lamalex, that's just a workaround, not a solution. It *should* appear on the Launchpad page.
[19:07] <lamalex> indded
[19:07] <lamalex> and its keeping me from merging
[19:09] <kiko> lamalex, do you have bzr+ssh access to that branch?
[19:09] <lamalex> yes
[19:09] <asabil> hi all
[19:10] <asabil> is there a way to turn a mirrored branch into a hosted branch in LP ?
[19:10] <kiko> lamalex, then you should be able to bzr launchpad-login and use bzr+ssh when merging
[19:10] <lamalex> kiko: we're trying to learn the launchpad merge management stuff
[19:10] <kiko> lamalex, ah, merge requests?
[19:11] <lamalex> I know I can merge it in without the merge queue and such, but we're seeing if that's a good fit for our project
[19:11] <kiko> sure thing
[19:16] <thumper> asabil: no
[19:16] <asabil> ok thanks
[22:38] <kiko> \sh, hey there (*2)
[23:10] <mattl> mrevell/sabdfl: http://www.fsf.org/blogs/community/savannah/
[23:19] <beuno> that's pretty close to spam
[23:21] <kiko> that's fun spam though
[23:21] <beuno> heh, sure, that's one way to look at it
[23:22] <thumper> man, turn up, dump a link and leave
[23:22] <thumper> not even hanging around to get feedback
[23:22] <thumper> that is a bit sucky
[23:29] <kiko> thumper, well, I think it's more that matt l. had already spoken to them before
[23:30] <kiko> and the article is a good one too!
[23:30] <thumper> kiko: except it didn't mention bzr as a supported RCS
[23:30] <kiko> thumper, is it supported?
[23:30] <thumper> kiko: I believe so, at least in some form