[00:04] <mwhudson> lifeless: different problem now
[00:05] <lifeless> mwhudson: tell me if you want to talk about it
[00:05] <mwhudson> lifeless: keep an eye on https://code.staging.launchpad.net/~vcs-imports/linux/trunk if you're curious how it goes
[00:05] <lifeless> mondayish
[00:05] <mwhudson> lifeless: sure
[00:05] <mwhudson> right
[00:05] <mwhudson> certainly not now :-)
[00:05] <lifeless> its mah birthday :P
[00:05] <mwhudson> oh, happy bday!
[00:05] <lifeless> ciao
[00:17]  * wgrant is slightly scared by Launchpad classes that inherit private Twisted classes.
[02:12] <wgrant> sinzui: Hmm. The default advanced bug search page has both "Show only bugs with linked branches" and "Show only bugs without linked branches", yet it still returns all of the bugs.
[02:12] <sinzui> Yep
[02:12] <wgrant> Has both of those selected, that is.
[02:12] <sinzui> It is insane
[02:12] <wgrant> Less insane than before, though.
[02:12] <sinzui> abel and I wanted radio buttons to who mutually exclusive states
[02:12] <wgrant> Ah.
[02:13] <sinzui> I had to do a search to prove I would get results
[02:13] <sinzui> I intend to report a bug about it
[16:26] <Pilky> sinzui: you around?
[16:26] <sinzui> I am
[16:27] <Pilky> just going to do some mockups for the team page
[16:27] <Pilky> based on the current design
[16:27] <Pilky> got two questions before I start though
[16:28] <Pilky> 1. you said on the list that the emphasis on certain information is wrong, what bits would you consider the most important to emphasise?
[16:29] <Pilky> 2. Does the list of pending members need to be shown to people who can't accept a new member?
[16:31] <sinzui> 1. The projects and packages that a team owns or creates.
[16:31] <sinzui>    What are the latest bugs, blueprints, questions, and branches that the team is assigned...We should find a away to indicate if a team is involved in translations.
[16:33] <sinzui> 2. All team members should be able to see who is pending, or if the user is himself in the pending list. As for everyone else, we show it to make the possible change visible, but I do not think it is necessary to be visible on the index page
[16:34] <Pilky> ok
[16:35] <Pilky> well, I'll have a go at mocking something up and then post it to the list. I'll try a few variations.
[16:35] <sinzui> Pilky: I really do not like the approach we have taken to show the latest <bug|blueprint|...> on pages. Some items might be months old. I have suggested a changelog or facebook wall approach to show recent activity. This may work for projet, but not necessarilly teams
[16:36] <Pilky> yeah it does cause quite a bit of clutter, I'll try looking at ways to simplify it
[16:36] <sinzui> What many users want to know (about themselves or others) is what has happened recently, what do I need to do next.
[16:37] <Pilky> the wall approach is slightly iffy legally now, seeing as facebook just got a patent on combined news feeds for activity on a site :/
[16:37] <sinzui> changelog is an metaphor that cannot be challenged.
[16:37] <Pilky> yeah
[16:38] <Pilky> well I'm pretty sure there's some prior art as with half of software patents, but I'll have a look at some sort of change log for the team
[16:39] <Pilky> well I'll hopefully have a few mockups in a few hours
[16:39] <sinzui> The design has been limited by implementation details, such each box has only one type of object. I want the code to 1. allow me to have a mixed list of objects to show. 2. allow me to set filters on the page so that I see only the kinds of objects|events that interest me
[16:40] <sinzui> My hope is that if we can have mixed objects and filters, we can solve a lot of wasted space on the page--either empty spaces, or boxes of information that the user does not care about.
[16:41] <Pilky> yeah
[16:42] <Pilky> well I'll try some ideas, if we can get the team page cleaned up a bit then hopefully a lot of that can be transferred to other pages.
[19:50] <Pilky> sinzui: you around? I've got some mockups
[20:13] <lifeless> moin
[21:08] <jelmer> mwhudson, hi
[21:43] <mwhudson> jelmer: hello
[21:45] <jelmer> mwhudson, I've tried to reproduce the bug you were seeing with gedit
[21:45] <jelmer> but I can't reproduce it by pulling 1k revisions at a time from a local git repo into a local bzr repo
[21:45] <mwhudson> jelmer: and it just worked?
[21:45] <mwhudson> jelmer: hmm
[21:45] <mwhudson> jelmer: linux failed on staging in the same way as locally: https://code.staging.launchpad.net/~vcs-imports/linux/trunk
[21:45] <jelmer> mwhudson, yes
[21:46] <jelmer> mwhudson, this was from not inside of launchpad though but from the commandline
[21:46] <mwhudson> well
[21:46] <mwhudson> that shouldn't make a difference
[22:02] <jelmer> mwhudson, So you could reproduce the issue with both gedit and linux?
[22:56] <mwhudson> jelmer: i didn't try gedit on staging actually
[23:01] <jelmer> mwhudson: ah, ok
[23:02] <jelmer> mwhudson: staging is running a recent bzr-git, isn't it?
[23:02] <jelmer> so maybe that happened to have the bug that gedit is breaking on fixed
[23:02] <jelmer> mwhudson: I'm running bzr pull --limit=1000 for the kernel now
[23:02] <jelmer> do you know after how many revisions it broke?
[23:09] <wgrant> IIRC it was on the third run.
[23:12] <jelmer> wgrant, thanks