[00:27] <mspencer> Hi, I've created a new project in launchpad which will be based on a specification on wiki.ubuntu.com. Should I set myself as the bug supervisor? I'm new to launchpad.
[00:27] <ebergen> who else would be the bug supervisor?
[00:29] <mspencer> ebergen: In the configure bugtracker page, the bug supervisor is listed as optional.
[00:29] <ebergen> ok
[00:29] <ebergen> then maybe don't worry about it
[00:29] <mspencer> ebergen: What are the benefits of doing so?
[00:30] <ebergen> probably if someone else other than the project owner will manager bugs
[00:30] <mspencer> ebergen: According to https://help.launchpad.net/Bugs/YourProject, "You may want to give some people extra bug editing privileges: The bug supervisor's role is to manage the planning of bug work and the triage of newly reported bugs. "
[00:31] <ebergen> makes sense
[00:31] <mspencer> ebergen: I plan to work on as many bugs as I can handle, so should I set this to myself or leave it blank?
[00:31] <ebergen> if you are the project owner just leave it blank
[00:32] <mspencer> ebergen: Okay, thanks.
[00:35] <mspencer> Can I directly upload code to a launchpad project? I'm using quickly but it won't let me use the share command telling me something about configuring a PPA.
[00:46] <ebergen> did you configure a PPA?
[00:47] <ebergen> I don't know what quickly is
[00:47] <ebergen> I just bazaar
[01:00] <mspencer> ebergen: No, I have not.
[01:00] <mspencer> ebergen: I've tried asking in the quickly channel but haven't gotten an answer, so I thought trying here might work. I'll ask again there later.
[01:02] <mspencer> ebergen: So is it possible to upload code directly to a launchpad project versus to a PPA first and then linking it to the project?
[01:03] <mspencer> ebergen: https://launchpad.net/contributor-console/trunk/+setbranch says "You can push the branch directly to Launchpad with the command: bzr push lp:~mdspencer/contributor-console/trunk"
[01:04] <mspencer> ebergen: Does this mean that I'm just doing something wrong with the program I use to upload my project?
[01:13] <mspencer> ebergen: 'the program' meaning quickly.
[01:15] <ebergen> I have no idea what quickly is or how to use it
[01:16] <ebergen> I use bazaar which provides the command bzr to push directly to launchpad
[01:16] <wgrant> mspencer: Branches store source code, PPAs store installable Ubuntu packages
[01:17] <wgrant> Branches are associated with a project, but PPAs aren't directly.
[01:18] <mspencer> My question doesn't matter on what quickly is, I'm just wondering if I can directly load code to the project. I'm new to launchpad and not very familiar with how it works.
[01:19] <wgrant> Well, it depends what quickly means
[01:19] <wgrant> PPAs and branches are for separate things, and it sounds like quickly might conceal the real terms
[01:20] <mspencer> wgrant: quickly is a tool for creating programs and allows changes to be saved to bazaar and launchpad.
[01:20] <wgrant> I suspect that "quickly share" wants to upload to a PPA, which means you'll need to create a PPA (probably at https://launchpad.net/~/+activate-ppa, if it's just you working on the project for now)
[01:20] <wgrant> I know
[01:20] <wgrant> I know what it is, but I've never used it so I don't know its terminology well
[01:20] <mspencer> wgrant: Yes, that is the command I'm trying to use  and that is what it wants to do.
[01:21] <wgrant> Right
[01:21] <wgrant> Personal Package Archives are, as the name suggests, personal -- they're not directly affiliated with a project.
[01:21] <wgrant> You'll need to create one, or have it do it for you
[01:21] <wgrant> Projects don't come with one
[01:23] <mspencer> wgrant: I'm not very familiar with projects, so I don't need to use a PPA except when using quickly? I can just use 'bzr push' to upload directly to my project?
[01:24] <wgrant> mspencer: "bzr push" is used to upload your code to a branch on Launchpad. "quickly share" builds your code into an Ubuntu package and uploads it to a PPA, where users can easily install it.
[01:24] <wgrant> PPAs are most frequently used without quickly
[01:24] <wgrant> quickly just provides a sometimes convenient shortcut to build and upload packages to them
[01:25] <mspencer> wgrant: I meant for me, I only need to use a PPA when I use quickly? Otherwise I can just use 'bzr push' to upload directly to my project?
[01:25] <mspencer> wgrant: I understand that a PPA can be used without using quickly.
[01:25] <wgrant> You only want to use a PPA when you want to make your project apt-get'able.
[01:25] <wgrant> You can use quickly without using 'quickly share'
[01:25] <wgrant> The point of 'quickly share' is to upload it to a PPA so users can easily install it
[01:26] <wgrant> You don't need to use a PPA with quickly unless you actually want to use a PPA
[01:26] <wgrant> Normally when you're developing you'd just bzr push
[01:26] <mspencer> wgrant: Okay, that helps me understand PPAs better, thanks!
[01:26] <wgrant> I'm not sure if quickly has a shortcut for that
[01:26] <wgrant> But yeah, PPAs are generally for distribution to end-users.
[01:27] <mspencer> And that answers my main question of how to upload code, thank you guys so much for all your help!
[01:31] <mspencer> One more question, how often should I load code to my project? Is it okay to upload code that is in progress or should I wait until everything works?
[01:35] <wgrant> Different projects have different branch policies. Many decide that the trunk branch on Launchpad should always contain finished, stable, releasable code; in that case developers usually develop features or fixes on a separate branch, then merge them into trunk when they're done. Others, particularly small, immature projects, don't care too much about trunk stability, and develop incomplete features straight on trunk.
[01:35] <wgrant> The latter tends to be common on young projects, as there's no real need to keep trunk stable
[01:35] <wgrant> And not much point if it's all under heavy development anyway
[01:35] <wgrant> But in the end it doesn't really matter; you can do whatever works for your project's development strategy.
[01:36] <mspencer> wgrant: Mine is new, so should I upload right away and then upload in-progress work for a while until it's ready for general use then only complete code?
[01:37] <mspencer> wgrant: I realize than there is no definite rule, I'm just looking for good advise.
[01:37] <wgrant> mspencer: Sounds reasonable. When you're working on the early stages of a project you usually end up touching code all over the place, and there might not be a logical way to break it up into separate, stable iterations.
[01:37] <mspencer> wgrant: Thanks!
[01:38] <wgrant> But for a large project like Launchpad, we only ever land finished work to trunk. We ensure that trunk always passes tests, and unless something goes wrong we can deploy any revision of trunk to production at any time without a problem.
[01:39] <wgrant> So all developers work in branches dedicate to a particular feature or bugfix, push them up to Launchpad, and propose them for merging into trunk. One of the other developers reviews the changes, and if they approve then the change can land to trunk in one piece.
[01:40] <wgrant> But that's because Launchpad has a lot of developers, is a very large codebase, and we deploy once or twice a day so it must *always* be stable
[01:40] <wgrant> You probably have none of those constraints, so a different process will suit you better :)
[01:42] <mspencer> wgrant: Considering this is a small project with only me so far, I don't think I have any of those constraints :)
[01:47] <mspencer> I've ran the command suggested on my project's page when no code was found in it: " You can push the branch directly to Launchpad with the command: bzr push lp:~mdspencer/contributor-console/trunk" but it isn't showing up in my project. Do I still need to link it to the project?
[01:50] <wgrant> mspencer: You'll see it if you click the "Code" tab, where you'll also see a suggestion that you might want to set it as your project's trunk branch
[01:52] <mspencer> wgrant: I checked the code tab, do you mean "A development focus branch hasn't been specified, set it now."?
[01:52] <wgrant> Yeah
[01:54] <mspencer> wgrant: Do I need to do this every time I upload code?
[01:54] <mspencer> wgrant: Do I type it with or without the 'lp:' part?
[01:55] <wgrant> mspencer: Just the first time you set up a new project
[01:55] <wgrant> I think both should work, but without the lp: will certainly work
[01:56] <mspencer> wgrant: Okay. So I can continue pushing to my branch because it's linked, not copied?
[01:58] <wgrant> mspencer: Right. All branches have a "lp:~user/project/branch" name, but as the project owner you can define a branch as having the alias "lp:project" -- the main trunk branch for the project. It still exists under the old name, and there's still only one branch, but it has that shortcut as an additional alias.
[01:58] <wgrant> You'll see that the branch is now shown on the web as "lp:contributor-console"
[01:59] <mspencer> wgrant: That makes sense because when I mouse over the links it still shows up as my branch.
[01:59] <wgrant> And I can just say "bzr branch lp:contributor-console" without having to worry about the branch's full name
[01:59] <wgrant> Yep
[01:59] <mspencer> wgrant: Yes, I notice that that shows up.
[01:59] <mspencer> wgrant: Thanks for you help!
[02:00] <wgrant> np
[02:10] <mspencer> Should I set myself as the project's driver and/or bug supervisor? I asked before about bug supervisor and was told that there was no need, but it doesn't seem right seeing 'None set'.
[02:20] <mspencer> Also, I'm writing my program based off of a specification. Should I create a blueprint based on that spec?
[14:00] <thopiekar> hi, is there a way only to import tagged git commits?
[15:13] <thopiekar> I also found out that tags are not correctly imported.. see https://github.com/kivy/kivy/tags and http://bazaar.launchpad.net/~kivy-team/kivy/master/files the last 2 tags (1.4.0 and 1.4.1) have not been imported according to the web UI..
[16:22] <mspencer> I've created a new project in launchpad that will be based off an specification at wiki.ubuntu.com. Should I set myself as the project's driver and/or bug supervisor? I asked before about bug supervisor and was told that there was no need, but it doesn't seem right seeing 'None set'.
[17:11] <mspencer> I've created a new project in launchpad that will be based off an specification at wiki.ubuntu.com. Should I set myself as the project's driver and/or bug supervisor? I asked before about bug supervisor and was told that there was no need, but it doesn't seem right seeing 'None set'.
[17:11] <ebergen> you must be joking
[17:12] <mspencer> ebergen: I'm also asking about project driver.
[17:14] <ebergen> I know
[17:14] <ebergen> because it's the same question from yesterday
[17:14] <ebergen> why don't you try using the project for while then make adjustments as needed
[17:14] <mspencer> I just don't understand why there is any reason to leave either blank. I'm new to this and don't understand launchpad very well.
[17:15] <ebergen> fine then
[17:15] <ebergen> don't leave it blank
[17:15] <ebergen> put your name there
[17:16] <mspencer> But why is there a reason to leave it blank?
[17:17] <ebergen> because you already own the project
[17:17] <ebergen> you already have all the privileges
[17:18] <mspencer> ebergen: That makes sense, then why doesn't it say that it is defaulting to the project owner?
[17:18] <ebergen> I don't know
[17:19] <mspencer> ebergen: Thanks for your help, I'll leave it blank
[17:19] <mspencer> Sorry for asking again, I just didn't understand why it would be left blank.
[17:23] <mspencer> How do I get other people to help on the project? I'd like someone else to create the icons since I'm not good at it.
[17:26] <ebergen> what project is this?
[17:27] <mspencer> ebergen: https://launchpad.net/contributor-console, based off of https://wiki.ubuntu.com/ContributorConsole
[17:28] <mspencer> ebergen: Also, I will probably want someone else to code a part of it that I'm not familiar with.
[17:29] <ebergen> it either has to be an interesting project or you have to pay
[17:32] <mspencer> ebergen: when I asked the author of the spec if this was something a beginner could handle, he say I could work on as much as I could do and others could help on the rest. Should I try asking on one of the ubuntu development channels for advice on how to get help?