launchpad-dev team mailing list archive

[Tim Penhey <tim.penhey@xxxxxxxxxxxxx>]

On Fri, 07 May 2010 09:09:19 Curtis Hovey wrote:
> On Thu, 2010-05-06 at 14:23 -0600, Paul Hummer wrote:
> > Thoughts?  Suggestions?  Whinging?
> 
> I like Source, because some of the items you list are not code either
> (and we can set the tooltip to "use the source Luke.").

I like Source in some situations.  I like Code more for the tab.

https://bugs.launchpad.net/bugs/573834 talks about the branches tab name, and 
there are other bugs filed about one or two a month about finding it hard to 
navigate to the source code for the project.

One issue that Launchpad has (and it has many) is that it tries to be 
everything for everyone.  Which never works.


On 05/06/2010 06:24 PM, Curtis Hovey wrote:
> All we need to do is add a link to related content, eg, +downloads.

If there are downloads for the project, we already show the download link on 
the branch index page for the project.  Perhaps it isn't obvious enough.  I 
have a whole pile of other issues around downloads (or more precisely 
uploading files for a project, but that is for another conversation).


On Thu, 2010-05-06 at 18:19 -0300, Martin Albisetti wrote:
> So, the reasoning behind this, IIRC, was:
> 
> - A lot of people where asking "where do I find the branch?"
> - "Code" implies you can download tarballs as well
> - And yes, because it's not always code

Most people aren't asking "where do I find the branch".  What they are asking 
is "Where do I find the main source code for this project?"

To be honest, I don't really thing that we should take the "it isn't always 
code" as a good reason to make things harder to find.


Here are my concrete suggestions:

 1) Add a section on the main project page above the downloads that says 
something like:
   Source
     (i) Browse the source code for <project name>
     bzr branch lp:<project name>
 - perhaps hyperlinking the lp:<project name> to go to the trunk branch

 - Don't show this if the project hasn't set a development focus branch
 - UNLESS the user has the ability to set it
 - remove the links from the project information section

 2) Rename "Branches" to "Code"
  - If you look at the subdomains, code is the only one that isn't the same as 
the tab.
  - Code also contains code reviews, revision feeds, recipes, and code import 
machinery views
  - Using the name Branches doesn't help the new user who doesn't understand 
DVCS.  Users who do understand DVCS have no problems knowing that branches are 
code.

Tim