[07:51] <himcesjf> cjwatson: More than merging account, my concern is to retain the username lost with deleted account!
[07:51] <himcesjf> cjwatson: I'll mail you and yes, you can verify
[10:38] <cjwatson> himcesjf: merging the accounts is a necessary part of this
[10:50] <acheronuk> cjwatson: I assume no-one has had the free time to look at? bug #1655298
[10:51] <acheronuk> I know you will all be busy, so that may get bumped to the back of work queues
[10:51] <cjwatson> I'm afraid not
[10:52] <acheronuk> Ok
[11:03] <himcesjf> cjwatson: While attempting to merge accounts on https://launchpad.net/people/+requestmerge I got "The duplicate is not a valid person or team." error
[11:03] <cjwatson> himcesjf: I can look but only if I know the usernames
[11:04] <himcesjf> Do you mind talking in PM?
[11:04] <cjwatson> That's fine
[11:53] <cjwatson> Should be sorted now
[12:01] <himcesjf> Yep, thanks for your help and time cjwatson
[23:18] <tjaalton> hi, how do I create a git repo for a team that I'm an admin on?
[23:18] <tjaalton> of
[23:19] <tjaalton> lp:~USER/PROJECT just says project does not exist
[23:19] <tjaalton> err, lp:~team/project
[23:19] <tjaalton> when trying to git push
[23:24] <wgrant> tjaalton: Does the project exist?
[23:24] <tjaalton> well, no
[23:25] <tjaalton> that's what I'm trying to create
[23:25] <wgrant> The project needs to exist before you can give it a git repository.
[23:25] <wgrant> https://launchpad.net/projects/+new
[23:25] <tjaalton> it needs to be an "upstream" project before it can be cloned under a team?
[23:26] <wgrant> Can you explain your use case?
[23:26] <wgrant> It's not an upstream project, it's just a project.
[23:26] <tjaalton> I want to get a git repo that a team owns
[23:26] <wgrant> It might be upstream from Ubuntu, but that's Ubuntu's perspective.
[23:26] <wgrant> That's a means to an end, not a use case.
[23:26] <wgrant> Is this a new piece of software?
[23:26] <tjaalton> kinda
[23:27] <tjaalton> bunch of scripts for hwe stack handling
[23:27] <wgrant> Sounds like a project to me.
[23:27] <wgrant> You could use lp:~team/+git/some-junk-repo-name, which is the git equivalent of a bzr +junk branch, but that's usually a mistake.
[23:27] <wgrant> If more than one person is working on something it almost always makes sense to have a project.
[23:27] <tjaalton> so a team can't share something like lp:~team/project?
[23:28] <wgrant> Having a git repository in a project requires the project to first exist.
[23:28] <wgrant> If the project exists then what you suggest is totally possible.
[23:28] <tjaalton> or should I put '~team/project' in the project creator url?
[23:29] <wgrant> Recall that LP projects are a global namespace. They're not scoped by team.
[23:29] <tjaalton> okay
[23:29] <wgrant> A team may own a repository inside a project.
[23:29] <wgrant> but the top level object is still https://launchpad.net/PROJECt.
[23:29] <tjaalton> ah
[23:29] <tjaalton> got it
[23:30] <wgrant> There are two key distinctions from the GitHub model:
[23:30] <tjaalton> I'm more used to git.debian.org model :)
[23:30] <wgrant>  - Since LP isn't just about code, the code repository is not the top level object -- the project is at the top, and it may contain multiple code repositories, one of which may be referred to as lp:PROJECT.
[23:31] <wgrant>  - LP projects are globally namespaced and multiple users/teams may participate, unlike GitHub where there's no central location and everything is namespaced under a person or team.
[23:31] <wgrant> s/person or team/user or org/