← Back to team overview

launchpad-dev team mailing list archive

Re: Code -> Branches, and a new meaning for Code

 

2009/8/18 Barry Warsaw <barry@xxxxxxxxxxxxx>:
> On Aug 18, 2009, at 1:24 AM, Tim Penhey wrote:
>
>> This has been floated before, but perhaps we could add this in for 3.0.
>>
>> <thumper> sinzui: rename code -> branches for the "tab", and add a "code"
>> tab
>> for projects that goes to loggerhead
>> <sinzui> +1
>> <thumper> I'll copy that into an email for beuno

I agree with most of jml's points, including that there is already a
bug about this.

I think the Launchpad-metadata view of branches needs to be closely
linked to the loggerhead view of the branch contents.  Perhaps in the
branch listing page there should be a link on each row that will take
you into the branch.

>> Questions:
>> 1) What about projects that don't have "code" like documentation projects

That seems to mean that you can't use the word 'code' to mean Loggerhead.

>> 2) What about packages?  Enable if a linked branch?
>
> My concern with "branches" is that the term assumes a more than passing
> understanding of how a VCS works.  I think a better term that should be
> instantly recognizable and applicable across types of projects would be
> "Files".
>
> It's not a precise term, since of course we also track directories, and
> Files might imply also downloads (and PPAs?) but I actually think that's
> fine.  I would expect to go to Files and find all the artifacts of the
> project, in whatever downloadable form is most natural.  E.g. instructions
> for branching, links to download, help in hooking up to Ubuntu, web browser
> of source code.  Make it a one-stop-shop for everything I can grab for the
> project and I think Files makes sense as a tab name.

If you think about this from the point of view of a software project
designing their own home page:

Most software project homepages have a tab or similar for 'downloads'
or 'releases'.   I think those are somewhat better names than 'files'.
 People seem to think Launchpad should have one too.

I really feel 'files' should not take you into a branch contents
browser, but rather into the specifically identified download files.
Developers would not thank us for encouraging users to get a snapshot
of trunk when they want a release tarball.

I like them both but I don't actually want a one-stop
motorcycles-and-marmalade shop. :-)

-- 
Martin <http://launchpad.net/~mbp/>



Follow ups

References