"branches" is not a good name for tab

[Zooko Wilcox-O'Hearn]

Every now and then I want to look at the source code of a project on launchpad, and it always takes me a bit of exploring the user interface and getting frustrated before I rediscover that the source code is under a label "Branches". I'm almost never looking for branches -- I'm almost always looking for the main version of the source code!

I wouldn't be surprised if other people similar have trouble finding it.

[Tim Penhey (thumper)]

We are in discussion with the UI devs over what to call it. It may go back to "Code".

[Jonathan Lange (jml)]

Really, I thought the UI devs said that we should call it "Branches"?

[Zooko Wilcox-O'Hearn (zooko)]

I just did a quick spin around all the code-hosting sites that I know of. I figured if there is a consensus among them about what to call this element then launchpad going along with the consensus would make it easier for users to recognize and navigate.

github: "Source"
http://github.com/thraxil/canopy

bitbucket: "Source"
http://bitbucket.org/nejucomo/hglafs/overview

code.google.com: "Source"
http://code.google.com/p/hadoop-lafs/wiki/HadoopTahoeSecureConfig

savannah.nongnu.org: "Source Code"
http://savannah.gnu.org/projects/gnu-crypto

trac: "Browse Source"
http://tahoe-lafs.org/trac/tahoe-lafs

patch-tag: "Browse"
https://patch-tag.com/r/zooko/Tahoe-LAFS/snapshots/all/history

darcsden: it puts the source on the front page for the project :-)
http://darcsden.com/alex/darcs

[Paul Hummer (rockstar)]

Curtis and I talked about this on Monday. I took the result of that discussion to the code team. The result of the Code team discussion was posted to the launchpad-dev mailing list. Basically, here's what we determined: "branches" will be renamed "code." We initially used "branches" to not exclude people that didn't just store code in their branches. We've decided to be opinionated and just call it code. It also makes more sense now that we have source package recipes as well, and not just branches.

[Zooko Wilcox-O'Hearn (zooko)]

"Source" is less exclusionary toward other things such as text, diagrams, etc. than "Code" is. You can think of your files as being the "source" of your document, image, etc.. It is also more alike the other major code-hosting sites per my previous comment.

However, "Code" is definitely an improvement in my book over "Branches" so I won't complain again if you don't see the wisdom of "Source" after reading this comment. :-)

[Tim Penhey (thumper)]

On Fri, 07 May 2010 08:28:39 you wrote:
> Curtis and I talked about this on Monday. I took the result of that
> discussion to the code team. The result of the Code team discussion was
> posted to the launchpad-dev mailing list. Basically, here's what we
> determined: "branches" will be renamed "code." We initially used
> "branches" to not exclude people that didn't just store code in their
> branches. We've decided to be opinionated and just call it code. It
> also makes more sense now that we have source package recipes as well,
> and not just branches.

Perhaps this could all be mitigated by having a "portlet" on the project
overview page with the title "Source" that gives a link to the source code
browser for the trunk branch.

[Matthew Paul Thomas (mpt)]

"Code" was renamed to "Branches" in bug 373341.

[Paul Hummer (rockstar)]

Playing in ec2 now.

[Paul Hummer (rockstar)]

"Branches" has been changed to "Code" in devel 10890

[Ursula Junque (ursinha)]

Fixed in stable r10890 <http://bazaar.launchpad.net/~launchpad-pqm/launchpad/stable/revision/10890>