Launchpad product names aren't consistent

Hello Matthew,

why did you change this bug to launchpad-development-infrastructure project? It seems to me this is a launchpad bug rather than a bug on the tools we develop to support launchpad.

Sorry, my mistake.

Can you offer suggestions for these?

e.g. today https://bugs.launchpad.net/malone/+bug/91013 tomorrow https://bugs.launchpad.net/LaunchpadBugTracker/+bug/91013 ?

You can't use capital letter in launchpad names.
Maybe:
    launchpad-bugs
    launchpad-translations

Ok, so we'd be looking at something like this:

launchpad
launchpad-bugs
launchpad-translations
launchpad-blueprint
launchpad-packaging (soyuz)
launchpad-answers (already this way)
laucnhpad-cscvs (already this way)
launchpad-documentation (already this way)

Questions:

1) Is the launchpad product itself worthwhile or should it be renamed to something like launchpad-general?

2) Soyuz is the Launchpad Package Manager but launchpad-package-manager kinds sounds funny.

I would prefer:
launchpad
launchpad with tag "bugs"
launchpad with tag "translations"
launchpad with tag "blueprint"
launchpad with tag "soyuz"
launchpad with tag "answers"
launchpad-cscvs (because it's a separate codebase)
launchpad with tag "help".

This would require beefier tagging support -- tagging while reporting (bug 54359), tagging while updating (bug 127138), mass tagging (bug 76083), easy tag searching (bug 66839), searching for the absence of tags (bug 81575), blueprint tags (bug 137397), and eventually auto-completion of common tags -- but IMO these things are sorely missing anyway. And in the meantime, I'd rather not more than double the length of names that I type dozens of times each day ("launchpad.net/some-short-name/+bugs").

On Wed, Sep 05, 2007 at 06:29:56AM -0000, Matthew Paul Thomas wrote:
> I would prefer:
> launchpad
> launchpad with tag "bugs"
> launchpad with tag "translations"
> launchpad with tag "blueprint"
> launchpad with tag "soyuz"
> launchpad with tag "answers"
> launchpad-cscvs (because it's a separate codebase)
> launchpad with tag "help".

+1

>
> This would require beefier tagging support -- tagging while reporting
> (bug 54359), tagging while updating (bug 127138), mass tagging (bug
> 76083), easy tag searching (bug 66839), searching for the absence of
> tags (bug 81575), blueprint tags (bug 137397), and eventually auto-
> completion of common tags -- but IMO these things are sorely missing
> anyway. And in the meantime, I'd rather not more than double the length
> of names that I type dozens of times each day ("launchpad.net/some-
> short-name/+bugs").
>
> --
> Launchpad product names aren't consistent
> https://bugs.launchpad.net/bugs/91013
> You received this bug notification because you are a direct subscriber
> of the bug.

--
Diogo M. Matsubara

It might also be a good time to rename launchpad-bazaar to something better. It seems that the emerging name at the moment would be "launchpad-code" or "launchpad-codehosting".

Last time we discussed this it was agreed that there should be a single Launchpad product, not several. The only reason for having several was limitations in blueprint (which have hopefully been fixed by now), as it did not have tags like Malone. And this is the only reason they haven't already been merged into a single one.

Having multiple products for the single code base causes lots of other problems, as we are using Launchpad in a way it was not intended. In particular, branches - if a branch is registered against the 'Launchpad' product, it is problematic linking it to soyuz bugs or rosetta specs. I'm aware of at least one feature currently being worked on by Tim that we want for Launchpad, but will be unable to use until the lp products are collapsed into a single one.

If we can't use Launchpad the way it was intended, we need to redesign it rather than trying to work around these issues, and work around the new issues the work arounds create, ad infinitum.

As a follow-on, I've been attempting to reduce the overall number of launchpad-x products to get us to the future Stu depicts in the above comment. We have a plan for the doc project but it is dependent upon bug 137397 being implemented.

bug #134545 applies here as does https://launchpad.canonical.com/SupportTrackerRename

Assigning to Kiko per his request.

Doing this renaming would break all links on the Launchpad wiki from specifications to their corresponding blueprints, and break many (though not all) bug links within those specifications.

Why would bug links be broken?

Updated proposed:

launchpad (the project)
launchpad-core (existing launchpad)
launchpad-bugs
launchpad-translations
launchpad-blueprints
launchpad-packaging (soyuz)

Disputed:

launchpad-codehosting (I think launchpad-bazaar is clear enough)

Already existing:

launchpad-answers
laucnhpad-cscvs
launchpad-documentation
launchpad-publisher
launchpad-cal (which should go away)
launchpad-buildd

Why would bug links be broken? Well, if we adopted Joey's proposal and renamed launchpad to launchpad-core, and launchpad-project to launchpad, every extant link of the form <https://launchpad.net/launchpad/+bug/nnn> would return a 404, for the same reason as <https://launchpad.net/launchpad-project/+bug/91013> returns a 404 today.

Other than banishing the "Malone" and "Rosetta" brand names, is there any actual problem that would be solved by renaming the projects? I know there are many problems with the current project structure (extra duplicate bug reports from people looking in the wrong project, difficult to set up and use milestones, impossible to link blueprints in different projects, problems with linking branches, etc), but I don't think any of them would be fixed or even improved by renaming.

On Tue, Mar 25, 2008 at 04:52:12AM -0000, Matthew Thomas wrote:
> would return a 404, for the same reason as <https://launchpad.net
> /launchpad-project/+bug/91013> returns a 404 today.

I'm kind of inclined to say that's actually a bug.
--
Christian Robottom Reis | http://async.com.br/~kiko/ | [+55 16] 3376 0125

Perhaps, but the only people who would ever be affected by it is us, if we did that renaming. And in the time we took to fix it, we could instead implement one of the missing features that are preventing us from using tags instead, and that would benefit many more people. :-)

On Tue, Mar 25, 2008 at 09:32:39PM -0000, Matthew Thomas wrote:
> we did that renaming. And in the time we took to fix it, we could
> instead implement one of the missing features that are preventing us

Please. It's not the same amount of time by any reasonable stretch of
the imagination.
-
Christian Robottom Reis | http://async.com.br/~kiko/ | [+55 16] 3376 0125

We've:
 - consolidated all the bug trackers that talked about the LP code base in to the /launchpad tracker.
 - other projects we are managing are in /launchpad-project and do not need to be branded launchpad-XYZ - see our current CreatingNewProject guidelines on the wiki (specifically things we do for infrastructure, e.g. lazr- components, are better -not- branded Launchpad so we don't sow confusion about what is domain specific and what is good tools other folk should use).