Launchpad itself

We should look at what we want to do to improve the 'code' menus in Launchpad

Bug #5578 reported by Björn Tillenius
6
Affects Status Importance Assigned to Milestone
Launchpad itself
Invalid
Medium
Unassigned

Bug Description

The 'code' menus in launchpad need some UI / usability work.

We should look at what we want to do to improve the 'code' menus in Launchpad

There are two code menus in launchpad.

The one on a product has one menu item: add a branch

The one on a person has four items: view various kinds of branches relating
to this person, and add a branch.

On the person overview menu, there is an item "packages", which is arguably
to do with code.

There is also "codes of conduct" which is not to do with code, even though
it contains the word "code".

In the product overview menu, we have "add branch", a duplicate of the item
in the code facet, but with a different name.

There is an implied menu item when you click on the "code" facet link
itself, which gives you the "+branches" page for both a person and a
product.

Options to proceed:

 * We could remove the "code" facet. We would add one menu items to the
   overview menu of product (that is, view branches), and five items to the
   overview menu of person. It may be possible to combine some of the
   five menu items.

 * We make the 'code' facet appear only where it is needed. This could
   cause problems with people not expecting to see a new facet there, and
   so not seeing that these facilities are available. We may want to do
   a similar thing with the 'calendar' facet, for consistency.

 * We keep things as is, but make the text of the menu options consistent.

 * We remove the "add branch" item from the product overview menu.

Which is the correct option? We need to think about what user stories and
workflows we want to support with these menus, and choose whichever one
works best for these.

See original description
Tags: lp-code ui
Revision history for this message
Matthew Paul Thomas (mpt) wrote :

This is because "Code" wasn't supposed to be a facet by itself, because (a) it didn't apply to enough things (only products and people), and (b) there were almost too many facets already.

Revision history for this message
David Allouche (ddaa) wrote : Re: [Bug 5578] Should "Create Branch" be on the overview page of a product?

Do you have something specific in mind to remove the code facet? I do
find it somewhat awkward, but I do not really how else the
branch-related pages (product and person branch listings, branch pages,
and in the future revision pages, pending merges, etc.) should be
categorized.

The "Add Branch" link was first put on the product overview page because
I regard it as similar to the "Add Series". The registry aspect of the
Bazaar seems like it should be generally be part of the Launchpad
Registry.

Revision history for this message
Steve Alexander (stevea) wrote :

Daf and I talked about this, and we changed the description of this bug to be a full discussion of the issue.

What remains is to decide what the important workflows and user expectations are, and choose how to proceed.

description: updated
summary: + The 'code' menus in launchpad need some UI / usability work.
Changed in launchpad:
assignee: nobody → mpt
Revision history for this message
Matthew Paul Thomas (mpt) wrote :

A person's context menu is currently very long. However, many of the items in it could be merged (for example, "Edit Personal Details", "Edit Home Page", "Edit Hackergotchi", and "Change Password" should be on a single page). I think this would make the menu short enough to accommodate the items currently in the Code facet.

Dafydd Harries (daf)
Changed in launchpad:
status: Unconfirmed → Confirmed
Revision history for this message
Matthew Paul Thomas (mpt) wrote :

Right now, products have "Add Branch" in their Overview facet, and a Code facet consisting only of an "Add Bazaar Branch" item pointing to exactly the same place. I've removed this redundant facet. I'll do the same for persons, and that menu should be made shorter by fixing bugs like bug 2421.

Changed in launchpad:
status: Confirmed → In Progress
Matthew Paul Thomas (mpt)
Changed in launchpad:
status: In Progress → Confirmed
Revision history for this message
David Allouche (ddaa) wrote :

In the ExCeL sprint, sabdfl insisted on restoring the facet, renamed to "Branches" (which is a much better name). When Launchpad will be broken into multiple virtual hosts (addressing bug 6607), the "branches" facet pages will be moved to bazaar.launchpad.net and occupy the same URL space as the bzr resources.

Given a URL scheme where persons and teams are identified by a leading tilde, that will allow punning the URL for the branch page to the URL of the bzr resource for that branch: /~owner/product/name, solving bug 39015 and complains that the supermirror URL for a branch is not browsable (bug ???).

Revision history for this message
David Allouche (ddaa) wrote :

mpt, is that bug still current, or is it superseded by the 1.0 UI?

Revision history for this message
Matthew Paul Thomas (mpt) wrote :

At Mark's request, I've renamed "Branches" back to "Code". This is still an issue, because the facet is still disabled much of the time. Things may improve if useful distro/Project branches pages can be implemented.

Revision history for this message
David Allouche (ddaa) wrote :

* distro branches: that one might be tricky. I think what we want to display here would be the HCT branches associated to packages of that distro. Likely, that would be too much data to be useful at once, so we would maybe rather show packages of the distro that have HCT data that differs from the parent distro... I think you get my point, we need a lot of specs and code before getting there.

* project branches: I think it would be fine to display a table similar to /bazaar/+all-branches. Fix to bug 58889, and maybe special display of series branches (related to bug 31308) would probably be necessary to keep such listings useful.

Matthew: I am not too sure what is the current issue now. I would like if you could edit the description of the bug to reflect it.

Revision history for this message
Matthew Paul Thomas (mpt) wrote :

I think this bug report is not useful any more, because it does not describe a particular problem to be fixed.

Changed in launchpad-bazaar:
assignee: mpt → nobody
status: Confirmed → Rejected
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.