launchpad-dev team mailing list archive

[Jelmer Vernooij <jelmer@xxxxxxxxxxxxx>]

Hi Jon,

On Mon, 2010-08-30 at 15:46 -0400, Jon Sackett wrote:
> In updating the codebase to use the usage enums proposed a month ago, the following scenario (which I think Martin Pool alluded to) comes up:
> 
> 1) A product uses a branch on launchpad as its development focus.
> 
> 2) The branch is itself a mirror of an externally hosted branch.
> 
> Previously, the code saw the presence of a development focus and determined that the product did in fact use Launchpad for codehosting. But our criteria for the codehosting_usage enum requires that the branch's type be HOSTED, and in this instance the branch is actually MIRRORED. 
> 
> It would seem that in this scenario the product shouldn't be said to use Launchpad for codehosting, but as there was some discussion on this before I thought I might get other  opinions.
I think those two scenarios make sense; there are two more that might be
nice to include as well: 

What about projects that don't use any VCS at all or use an upstream VCS
that is not supported by Launchpad? 

Some people still just use a directory with sources that they tar up and
put up on the web now and then (can't think of one right now but I've
come across them when linking upstream projects in the past) or don't
have source code at all (e.g. launchpad-code, soyuz). 

Some projects also use Monotone, Fossil, Microsoft Team Foundation
Server (though there is some work happening on a bzr-tfs plugin...),
perforce, etc. 

Cheers,

Jelmer

Attachment: signature.asc
Description: This is a digitally signed message part