/srv/irclogs.ubuntu.com/2015/04/30/#launchpad-dev.txt

cjwatsonwgrant: I'm looking into the reported (non-timeout) bug unsubscribe oops.09:48
cjwatsonUnless you are already.09:48
wgrantcjwatson: Fixed on DF already.09:50
wgrantJust writing tests for the untested cod09:50
wgrante09:50
cjwatsonHeh, OK.09:50
cjwatsonwgrant: Did you have any thoughts on http://irclogs.ubuntu.com/2015/04/29/%23launchpad-dev.html#t16:48 ?09:59
wgrant "Default" is ew, the rest makes some sense.10:01
cjwatsonMm, maybe I can just drop that and the singular is enough.10:02
wgrantIn an ideal world that would be where the repository selector was, I think.10:03
wgrantBut "default" should definitely not be the first word on the page!10:03
cjwatsonrepository selector> how do you mean?10:03
wgrantWell, we need some way to see the other repositories, probably near the top of the page.10:04
cjwatsonRight.10:04
wgrantMaybe even above the "You can browse the source code"10:04
cjwatsonMaybe just "Git branches".  It's "branches associated with the default Git repository", but "Git repository branches" just sounds like we're confused.10:04
wgrantThat would make it clear which repo is selected.10:04
wgrantYeah, "Git branches" makes sense-ish.10:04
cjwatsonThe page is annoyingly spread out over product-branches.pt and product-branch-summary.pt right now, which makes it awkward.10:06
wgrantdammit nvidia10:26
wgrantnumber_of_duplicates10:27
wgrant    115610:27
wgrantother_users_affected_count_with_dupes10:27
wgrant    286510:27
wgrantcjwatson: https://code.launchpad.net/~wgrant/launchpad/git-fixes/+merge/25797722:14
cjwatsonwgrant: r=me22:18
wgrantcjwatson: Thanks.22:18
cjwatsonI think we can NDT without that, though - I was going to sort that out after this call22:18
cjwatsonif that's OK22:18
cjwatsonsince at least ASCII-only MPs work22:19
wgrantyep22:20
wgrantsounds good to me22:20
cjwatsonwgrant: LPSed/RTed; feel free to amend both if your rev is ready before webops take that22:43
cjwatsonhttps://code.qastaging.launchpad.net/~cjwatson/grub/+git/qas/+ref/fstest-test/+merge/254312 was the ASCII-only case I mentioned, BTW22:45
wgrantYep, saw it in the OOPS.22:46
wgrantI poked around locally and found all the obvious crashers and fixed them.22:46
cjwatsonYep.  Thanks for that.22:46
cjwatsonI think anything further from our side is gravy at this point.22:47
cjwatsonIs there anybody at the sprint who might be able to help chase down the nova scheduling thing tomorrow?22:48
wgrantIf it's not solved overnight, I will harrass someone.22:49
wgrantI'm talking to designy people tomorrow morning, will try to get something useful out of them. But I think we just need something like your screenshot, target/owner repo listings...22:50
wgrantAnd GitRef:+activereviews would be nice and might be easy.22:50
wgrantAll of which are quick to do something roughly as dirty as the bzr equivalent.22:50
cjwatsonYeah, there's a huge pile of misc views to clean up.22:51
cjwatsonLayouts of the worst cases of combining git and bzr listings that also show a useful set of information about git branches would be good.22:51
cjwatsonIn some ways I'd like to ram them all into a single table.22:52
cjwatsonPartly because multiple similar-content tables on a single page look bad because their column widths don't match.22:53
cjwatsonI haven't touched the package views yet.22:53
wgrantThe only place we really need to show both simultaneously is on Person:+branches22:53
wgrantSince a target (or an owner-target) has a primary VCS defined.22:54
cjwatsonThe project and package views could get away with having a mode switch, indeed.22:54
cjwatsonOnce we model such a thing.22:54
wgrantPerson:+branches already has a relationship filter.22:55
wgrant(it was several separate pages a few months ago, but it's all one now)22:55
cjwatsonI'd been focusing on the target partly because I'd like to have a rule that the target page for a target with a default repository always shows at least something about the default repository, so that we can switch the canonical URL over to shortened_path rather than unique_name22:57
cjwatsonsince I really don't like the canonical URL for default project repositories being /~owner/project/+git/project22:57
wgrantYeah, definitely. And that's the only bit that really requires thought.22:57
wgrantThe others are, well, tables.22:58
cjwatsonso I think that even if we have a mode switch we always need to show *something* about the non-default mode22:58
cjwatson(if there's any content for it)22:58
wgrantyep22:58
cjwatsonwe could certainly have a radically different summary, though22:58
cjwatsonvery hard to get the summary right without a mode switch - I tried, it's a mess as you saw22:59
cjwatson"you can clone a git repository!  oh and by the way you can push a bzr branch!"22:59
wgrantMhm.22:59
cjwatsonbut perhaps I could go and try Person:+branches for a while, because that involves a lot of the same kind of infrastructure but has a fairly minimal summary23:01
cjwatsonand, I think, should probably just show repositories rather than refs23:01
cjwatsonmaybe?23:01
cjwatsonalthough "last commit" is meaningless for repositories, so perhaps that's wrong23:02
cjwatsonperhaps repositories should have an expander for branches23:03
cjwatsonworth asking design if they have any thoughts there23:03
wgrantI don't really know. I like seeing all the recent work, but it might get drowned out by eg. a push --mirror23:04
cjwatsonYeah.  And status is meaningless for repositories *and* refs, too.23:04
cjwatson(To the extent that it's meaningful for branches ...)23:05
wgrantI would not complain if the status column accidentally went missing tomorrow.23:05
wgrantmm23:05
wgrantI guess Merged is useful23:05
wgrantBut meh23:05
cjwatsonIn the default view, which excludes it :-)23:06
wgrantyep23:06
cjwatsonIf we're using committer_date (which we do right now in ref listings), then push --mirror is less of a problem23:07
cjwatsonOne of my branches in progress fixes ref listings to sort by descending committer_date23:07
cjwatsonWhich makes them a lot more sensible23:07
wgrantblr: Do you want to experiment with these couple of views and see if you can get something vaguely sensible?23:07
cjwatsonhttp://paste.ubuntu.com/10956927/ is what I have today, if you want to crib anything from that23:08
blrwgrant: sure - thanks cjwatson23:08
cjwatson(also I have http://paste.ubuntu.com/10956930/ lying around from an older branch that tried to do more with targets, but I suspect more of that branch is crap)23:09
wgrantI'll work with designy people tomorrow, but it'll be a while before we have anything useful, and we just need something vaguely adequate for tomorrow.23:09
blrcjwatson: will move push-instructions to a partial, it is used in two places23:09
blrand add the git specific copy we discussed last night23:10
cjwatsonThe fixed sorting is the top bit of the patch to lib/lp/code/browser/gitrepository.py, and we likely want that regardless23:10
cjwatson(from the first paste)23:10
cjwatsonI'm inclined to say that we may want to drift away from trying to have a single view for Person again23:11
wgrantYeah23:12
cjwatsonPerson:+branches is recent work, but there could also be a view that lists all your repositories23:12
cjwatsonThen Person:+branches can just mix in refs with the committer date as "last modified"23:12
wgrantA push --mirror with a billion branches seems not hugely likely.23:12
wgrantCan always be adjusted if it doesn't work out.23:12
cjwatsonright, but even if somebody does that, a lot of those branches are going to be old23:12
wgrantYep23:12
cjwatsonin terms of committer date23:13
wgrantSo Person:+branches intersperses branches and refs.23:13
cjwatsonwe miiiight have a perf problem, but I don't think it's a fundamental UI problem if you end up with a bazillion branches off in batch 8723:13
wgrantProduct:+branches shows one or the other, and additionally the default git repo if git is selected, plus a VCS switcher.23:13
wgrantI don't see a perf problem here, though it will be awkward to implement.23:14
cjwatsonGitCollection lalala23:14
wgrantIt may be better to have a VCS switcher for Person:+branches in the first iteration.23:14
wgrantNo fundamental perf problem, then :)23:14
cjwatsonlike another dropdown?23:14
wgrantIt's a simple matter of code.23:14
wgrantCould be, yeah.23:14
cjwatsonOr just Person:+repositories, if it's going to have totally different semantics anyway23:15
wgrantWe can't currently dynamically change the default view for a particular object.23:15
wgrantOnly an interface.23:15
wgrantBut I guess having it as a secondary page for the first iteration is OK.23:16
cjwatsonright, but we could have another slot in PersonBranchesMenu23:16
cjwatsonwhich already has "Branches", "Active reviews", "Source package recipes"23:16
cjwatsonthe only concern would be whether we're painting ourselves into a corner, but redirects are a thing ...23:16
wgrantRight, it works short term.23:17
wgrantAnyway, I need to sleep.23:18
cjwatsonI'm not convinced we can fix the canonical URL of target default repos by tomorrow, but even making it possible to find them via a Person view would be a small step up23:18
cjwatsonyeah, me too23:18
wgrantblr: Experiment with what you can today, and Colin and I can hopefully bikeshed over whatever you have into something releasable in our morning.23:19
cjwatson(conceivably, Person:+repositories could list all the projects you've worked on in code terms, whether that be bzr or git - take advantage of the bzr repository metaphor even if it isn't precisely identical23:19
cjwatson)23:19
wgrantTrue23:19
cjwatsonthat sort of thing might help address people's issues with code23:20
cjwatsonand after all e.g. https://code.launchpad.net/~cjwatson/launchpad is a thing, so we *sort of* have that notion already23:22

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!