[00:05] <wgrant> vila: There should be a delete button to the right of the title if you have permission, but only on edge at the moment.
[00:05] <Andre_Gondim> I have a question, this strings in rosetta is correct? https://translations.edge.launchpad.net/ubuntu/jaunty/+source/installation-guide/+pots/partitioning/pt_BR/111/+translate maybe is ubuntu instead debian, no?
[00:06] <wgrant> You might need privileges over the project, not just the series.
[00:12] <vila> wgrant: https://bugs.edge.launchpad.net/launchpad-registry/+bug/174489 should be fixed RSN :)
[00:12] <vila> wgrant: thanks
[00:29] <tacone> how to mark a bug as duplicate ?
[02:35] <MTecknology> I'm trying to remember - how do I mark that a bug it being tracked externally and add the link?
[02:35] <MTecknology> nevermind
[02:36] <MTecknology> I can't track using http://drupal.org/node/203467 ...
[04:21] <Ursinha> MTecknology: so you're there :)
[04:21] <Ursinha> having a hard time with the bot :/
[04:22] <MTecknology> idk if I have time to really help
[04:22] <MTecknology> I've been fighting hard with developing creap for drupal
[04:23] <Ursinha> I know how that feels
[04:23] <Ursinha> but the help won't be nothing more complicated than telling me how to change a factoid :)
[04:24] <MTecknology> !no foo is <reply>bar
[04:25] <MTecknology> oops - ubottu is in here
[04:25] <Ursinha> hahahahahahahaha
[04:25] <Ursinha> :)
[04:25] <MTecknology> !MTeck is sorry, just showing an example
[04:25] <Ursinha> this seems easy
[04:26] <Ursinha> MTecknology: I didn't know that trick
[04:26] <Ursinha> thanks for that :)
[04:27] <MTecknology> np
[05:07] <poolie> i seem to be having trouble filing a new bug...
[05:07] <poolie> it just stalls
[05:16] <spm> poolie: edge? looks like edge1 got stuckered in the auto-update. So you may have been hitting that.
[05:18] <poolie> or just telstra suck
[05:18] <poolie> it worked now anyhow
[05:18] <poolie> https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bug/342118
[05:19] <spm> yeah - I manually killed edge1, and was trying to verify if the update has completed or fail
[05:20] <thumper> poolie: heh, is this when skype died?
[05:20] <poolie> no, that was different
[05:20] <thumper> it is way past EOD here
[05:20] <thumper> poolie: how about we catch up Monday?
[05:20] <poolie> thumper: anyhow: for brisbane-core stuff see http://bazaar-vcs.org/Roadmap
[05:20] <poolie> oh right it's +3 hours from here
[05:20] <thumper> poolie: ta
[05:20] <poolie> i'd forgotten
[05:21] <poolie> have a good weekend
[05:21] <poolie> but just quickly-
[05:21] <poolie> you're not sprinting around allhands?
[05:27] <thumper> not personally
[05:27] <thumper> I expect there will be several people at the UDS
[05:27] <thumper> to do LP/code type talks
[05:27] <thumper> mingling
[05:28] <thumper> and all the rest
[05:30] <poolie> cool thanks
[05:54] <mwhudson> oh yes UDS
[05:54] <mwhudson> thumper: we should chat about that i guess
[07:38] <Coke> I have a few questions about launchpad BZR, why is my branch named barcodesforpython/beta when I actually named it "devel"? I have a series named beta, but I clearly remember naming the branch devel. ??
[07:48] <wgrant> Coke: If you associate a branch with a series, it gets an alias.
[07:49] <wgrant> It still has the lp:~user/project/branch name, but it also gets lp:project or lp:project/series
[07:53] <spiv> Coke: if you look at https://code.edge.launchpad.net/barcodesforpython, the link to lp:barcodesforpython/beta takes you to https://code.edge.launchpad.net/~peter-stockholm/barcodesforpython/devel
[07:54] <spiv> Coke: i.e. see what wgrant said :)
[08:17] <soren> Any idea why the createBug API call gives me a HTTP 503 on staging?
[08:18] <soren> Mind you, I'm trying this for the first time. It's possible I'm doing something wrong.
[08:18] <wgrant> soren: I've been getting 503s from staging frequently today.
[08:18] <wgrant> Trying again generally helps.
[08:18] <wgrant> Or is yours reproducible?
[08:18] <soren> wgrant: Ok, good, so my code might be correct, I suppose.
[08:18] <soren> I'll try a few times..
[08:19] <wgrant> It could be your fault, but if it is then the 503 is a bug.
[08:19] <soren> True :)
[08:21] <soren> launchpad.bugs.createBug(description='long description', title='the title', target=pkg) where pkg is a a DistributionSourcePackage object I've created earlier.
[08:25] <wgrant> soren: Ah, it's a timeout.
[08:26] <wgrant> OOPS-1168S1099\
[08:26] <wgrant> And staging just got a new DB server...
[08:49] <Coke> spiv & wgrant indeed, thanks.
[09:00] <soren> wgrant: Ah, ok. Thanks.
[14:12] <flo_> Hi, does the ssh keys have a delay before they can be used ?
[14:55] <flo_> ok, i solved this alone .. have a good day everyone !
[16:31] <Pegasus_RPG> I need some help committing code to a launchpad project: I originally did bzr checkout using the public http address and now want to commit using the sftp address but I can't figure out how to tell bzr to stop using the http address
[16:33] <rockstar> Pegasus_RPG, hi
[16:33] <batoms> i need to reupload a package but in the rejection letter that I got from launchpad it doesn't have the link to the original tarball
[16:33] <rockstar> Pegasus_RPG, have you been using a checkout or a branch?
[16:33] <batoms> where are these original tarballs kept?
[16:33] <Pegasus_RPG> rockstar: uh, both?
[16:33] <Pegasus_RPG> rockstar: a checkout of a branch
[16:33] <batoms> crap, just found a link to it on my ppa page
[16:33] <batoms> that always happens
[16:33] <rockstar> Pegasus_RPG, so you have a local mirror of the branch then?
[16:34] <Pegasus_RPG> rockstar: Yes. I just used bzr checkout (via Olive)
[16:34] <Pegasus_RPG> but Olive is too slow to work with, so now I'm trying to commit via the command line
[16:34] <rockstar> Pegasus_RPG, what I need to know is whether you used did bzr checkout http://... or whether you did a bzr branch http://... and then a bzr checkout of that branch.
[16:35] <Pegasus_RPG> I just did bzr checkout http://
[16:35] <rockstar> Pegasus_RPG, Okay, so you can't commit right now then?
[16:35] <Pegasus_RPG> correct, as it says  http does not support mkdir()
[16:36] <Pegasus_RPG> (or it did, until I *cough* edited .bzr/branch/location
[16:36] <rockstar> Pegasus_RPG, what happens if type bzr info on your branch?
[16:36] <rockstar> Pegasus_RPG, It's a good idea to stay out of .bzr/branch/location
[16:36] <Pegasus_RPG> dunno, since I edited that file then changed it back, it tells me bzr: ERROR: Transport error: Server refuses to fullfil the request
[16:37] <Pegasus_RPG> no matter what I do
[16:37] <Pegasus_RPG> I can do bzr info on the sftp address and it looks sensible
[16:37] <Pegasus_RPG> Do I need to start over with a fresh checkout from the sftp address?
[16:39] <rockstar> Pegasus_RPG, I think you need to consider this checkout a loss.
[16:39] <Pegasus_RPG> rockstar: That's fine. Noone's done anything to the files I changed yet so I can just copy them somewhere safe
[16:40] <rockstar> Pegasus_RPG, I would suggest branching instead of checking out.
[16:40] <rockstar> Pegasus_RPG, checking out basically means "I don't want the D in DVCS"
[16:40] <Pegasus_RPG> The head devs of the project are just getting their feet wet with bzr as well
[16:40] <Pegasus_RPG> so I think they were trying to make it easy for us coming from SVN
[16:41] <Pegasus_RPG> At the moment, I don't think I want the 'D' since I need to share my changes with the other devs so we can collaborate on problems
[16:41] <Pegasus_RPG> So if I can still do that with a branch, what command should I issue to do the correct branch/checkout?
[16:42] <Pegasus_RPG> that will let me commit later?
[16:42] <rockstar> Pegasus_RPG, if you branch, you can version your patch, and then it can be merged into the trunk.
[16:42] <rockstar> Pegasus_RPG, what's the project?
[16:42] <Pegasus_RPG> Mixxx
[16:43] <Pegasus_RPG> Our trunk is still in SVN but we're trying bzr on Launchpad for the 1.6.2 release
[16:43] <rockstar> Pegasus_RPG, so what you want to do is bzr branch lp:mixxx
[16:43] <Pegasus_RPG> well, http://bazaar.launchpad.net/%7Emixxxdevelopers/mixxx/release-1.6.2/ in this case
[16:43] <rockstar> This will give you a branch that you can then push to your own code area and then propose to merge.
[16:45] <rockstar> Pegasus_RPG, this is usually how I work:  (1) create a branch from the most recent trunk, (2) Hack on it, making commits where it makes sense, (3) push the branch, (4) propose for merging...
[16:45] <rockstar> Pegasus_RPG, In the proposal stage, the code can be reviewed by my peers before it lands.
[16:45] <Pegasus_RPG> That's where we want to get to I think, but for now everyone's just trying to get used to bazaar
[16:45] <rockstar> Then people can vote on the proposal, and the you can merge your branch into trunk.
[16:46] <rockstar> Pegasus_RPG, but you don't want to get used to bzr as if it was svn.
[16:46] <Pegasus_RPG> oh
[16:47] <Pegasus_RPG> allright, so the devs have already made a branch for the feature-frozen v1.6.2 release. You're saying I need to branch that?
[16:47] <rockstar> Pegasus_RPG, yes, branch that.
[16:47] <rockstar> Pegasus_RPG, bytheway, what's your lp username?
[16:47] <Pegasus_RPG> pegasus-renegadetech
[16:48] <rockstar> Pegasus_RPG, so you'll want to do something like bzr push lp:~pegasus-renegadetech/mixxx/<name-of-your-branch>
[16:49] <Pegasus_RPG> I see, so I'll have a personal branch of the corporate release branch
[16:49] <Pegasus_RPG> (which is itself a branch of trunk)
[16:49] <rockstar> Pegasus_RPG, yes.  This means that anyone can hack on mixxx without having to have "commit privileges"
[16:49] <Pegasus_RPG> But I do have commit privs. :)
[16:50] <rockstar> Pegasus_RPG, So if I wanted to do something on Mixxx, I don't have to have those commit privileges.  I can just hack and then propose for merging.
[16:50] <Pegasus_RPG> anyway, ok. THanks for your time
[16:50] <Pegasus_RPG> ...as opposed to mailing patches. NIce
[16:50] <rockstar> Pegasus_RPG, since you have privileges on the branch, you can merge your branch yourself.
[16:50] <rockstar> Pegasus_RPG, yeah, it makes it really easy to collaborate.
[16:51] <Pegasus_RPG> ok, so the command sequence again will be bzr branch sftp://
[16:51] <Pegasus_RPG> <make changes>
[16:51] <Pegasus_RPG> bzr commit
[16:51] <Pegasus_RPG> <like changes>
[16:51] <rockstar> Pegasus_RPG, no, not sftp:// but bzr+ssh://
[16:51] <Pegasus_RPG> aroo?
[16:52] <rockstar> Pegasus_RPG, also, when you're committing, you're only committing locally to your filesystem.  If you want others to see these changes, you'll have to push them to Launchpad.
[16:53] <Pegasus_RPG> ok so after I like my changes, I bzr push?
[16:54] <rockstar> Pegasus_RPG, or, if you're making a lot of commits, you push every few commits, so everyone can see your progress, even if it's not ready.
[16:55] <Pegasus_RPG> and that goes into my personal branch, when I push, right?
[16:55] <rockstar> Pegasus_RPG, when it IS ready, you can propose it for merging into 1.6.2 and/or trunk
[16:55] <rockstar> Pegasus_RPG, it goes into A personal branch.  You can have as many personal branches of a project as you want.
[16:55] <Pegasus_RPG> oh jeez
[16:55] <rockstar> Pegasus_RPG, ?
[16:56] <Pegasus_RPG> starting to hurt my brain. :)
[16:56] <Pegasus_RPG> anyway, I think I get it
[16:56] <rockstar> Pegasus_RPG, so, let's say that I'm hacking on a feature, and I get blocked on another developer's work.  I can branch again and work an another feature, coming back to that one.
[16:56] <rockstar> Er, coming back to the original one when I'm not blocked anymore.
[16:57] <Pegasus_RPG> Sounds handy, but all the merges that have to happen after that make me shudder
[16:57] <rockstar> Pegasus_RPG, it's really not that hard.
[16:57] <rockstar> Merges in bzr are not like merges in svn.  They are MUCH easier, and have less issue.
[16:57] <Pegasus_RPG> well that's good
[16:58] <Pegasus_RPG> Much of the work we're currently doing is cleanup, and due to Mixxx poor internal design, everything touches everything else, so chances for conflicts are high
[16:58] <rockstar> Pegasus_RPG, also, I have a project that merges approved branches automatically.  http://edge.launchpad.net/tarmac
[16:59] <rockstar> Pegasus_RPG, I know that dance.  Another project I work on is doing something similar.  As long as you communicate, it's relatively trivial to fix the conflicts.
[17:00] <Pegasus_RPG> ok, so is there a quick reference sheet on the appropriate times to use the different bazaar commands?
[17:00] <Pegasus_RPG> I'm not going to remember all this
[17:01] <rockstar> Pegasus_RPG, https://edge.launchpad.net/+tour/index
[17:01] <rockstar> Pegasus_RPG, https://help.launchpad.net/
[17:01] <rockstar> Pegasus_RPG, http://theironlion.net/blog/2009/01/13/using-bazaar-launchpad-making-pushing-easy/
[17:02] <rockstar> Pegasus_RPG, and I'm usually always around, so you can just bug me.
[17:02] <Pegasus_RPG> heh thanks
[17:25] <thekorn_> leonardr, hi, are you working on bug 340935? if not I can give it a try, from your last comment it looks like it should be easy to fix
[17:26] <leonardr> thekorn_: go ahead
[17:27] <thekorn_> okidoki
[17:41] <_Groo_> hi/2 all
[17:41] <_Groo_> any kubuntu devs alive?
[17:46] <Pegasus_RPG> hey rockstar, When doing bzr branch lp:~mixxxdevelopers/mixxx/release-1.6.2  I first get a warning that the server doesn't support streaming, then it gets stuck at the same point every time while downloading
[17:46] <Pegasus_RPG> any idea what's wrong?
[17:48] <rockstar> Pegasus_RPG, that was a bug with 1.6 I believe.
[17:48] <rockstar> Pegasus_RPG, how does it get "stuck"
[17:48] <Pegasus_RPG> \ [[17:48] <Pegasus_RPG> ] Transferring 0/4^
[17:49]  * Pegasus_RPG has bzr 1.5 in Debian
[17:49] <kiko> Pegasus_RPG, you really want to be on 1.12 or more recent
[17:49] <Pegasus_RPG> peachy
[17:52] <rockstar> Pegasus_RPG, it's probably still working, but older bzr's had a hard time telling you it was doing anything.
[17:52] <Pegasus_RPG> oh so just be patient? ;)
[17:53] <rockstar> Pegasus_RPG, possibly.
[17:54] <thekorn> leonardr, pushed a fix to lp:~thekorn/launchpadlib/fix-340935-bug_target, I'm not totally sure if this is the same idea as in your last comment, but at least it seems to work
[17:55] <leonardr> thekorn, cool
[17:56] <Pegasus_RPG> ah yes, my modem is showing activity and df shows more space taken each time :
[17:57] <Pegasus_RPG> :)
[17:59] <kiko> thekorn, hey, nice work
[18:00] <thekorn> hi kiko, thanks
[18:05] <leonardr> thekorn: can you propose that for merging into the trunk?
[18:05] <leonardr> https://code.edge.launchpad.net/~thekorn/launchpadlib/fix-340935-bug_target/+register-merge
[18:06] <leonardr> write up a summary of your changes and we'll get it reviewed
[18:06] <thekorn> leonardr, https://code.edge.launchpad.net/~thekorn/launchpadlib/fix-340935-bug_target/+merge/4452
[18:11] <leonardr> thekorn: your code needs to work for any incoming document that has a resource_type, not just #bug_target
[18:12] <leonardr> the code to do this might have to go into bind()
[18:19] <thekorn> leonardr, hmm, so this bug has to be fixed in wadllib and not launchpadlib ;) will try to understand how this bind() method works tomorrow
[18:20] <leonardr> thekorn: ok, great. thanks again for taking this on
[18:23] <Pegasus_RPG> rockstar: ok, ready to push...what ssh:// address do I need?
[18:24] <rockstar> Pegasus_RPG, well, need to push to your area of the mixxx project, so you construct the url like this:
[18:25] <rockstar> Pegasus_RPG, bzr push lp:~<your-lp-name>/mixxx/<your-branch-name>
[18:36] <Pegasus_RPG> rockstar: the head devs are playing around now. How do they actually merge an approved proposal?
[18:37] <rockstar> Pegasus_RPG, there are a few ways, but the easiest is to go to the branch index page of the branch and then click "Propose for merging into another branch"
[18:37] <Pegasus_RPG> No, I mean another user already did that, and the hed dev approved it
[18:37] <Pegasus_RPG> how does he merge it now?
[18:42] <Pegasus_RPG> when I do "bzr commit" locally, must I specify the files I want to commit?
[18:44] <rockstar> Pegasus_RPG, no.
[18:44] <rockstar> Pegasus_RPG, you CAN, but you don't have to.
[18:44] <Pegasus_RPG> if I don't does it push the ENTIRE repository? because it's been saying Copying signature texts 3/5 for the last 10 minutes
[18:44] <rockstar> Pegasus_RPG, when you need to merge, go to your branch that you want to merge into, and do bzr merge lp:<path-to-the-other-branch> and then commit and push.
[18:45] <rockstar> Pegasus_RPG, push and commit and two different things.
[18:45] <Pegasus_RPG> rockstar: I know. I'm jumping around concepts, sorry. ;)
[18:45] <Pegasus_RPG> I committed before to my local store
[18:45] <Pegasus_RPG> now I'm pushing and it's taking a loooong time
[18:45] <Pegasus_RPG> which makes me wonder if I committed incorrectly
[18:46] <rockstar> Pegasus_RPG, you REALLY need to upgrade to at least bzr 1.6, as bzr will then stack the branch on the trunk branch, so you don't push the whole repo.
[18:46] <Pegasus_RPG> ah, so I AM pushing the whole damn thing
[18:47] <seb128> hi
[18:48] <seb128> is there any way to tell launchpad to spam you about a project you don't care about but for which one you registered the upstream product or component?
[18:49] <seb128> I got a GNOME upstream who registered seahorse to be able to add a bug watch and he complains about getting spammed now
[19:03] <Pegasus_RPG> now how do I keep my personal branch in sync with the corporate one?
[20:06] <savvas> Pegasus_RPG: something like this? bzr pull
[21:54] <ronny> gmb: ping? sup on the pida lp sync issue?
[21:56] <gmb> ronny: I've made no headway on this as yet. I'm just dealing with another issue at the moment. Bear with me and I should be able to check out a couple of theories that I have within the next hour or so.
[21:58] <ronny> gmb: i dont personally manage the trac tho, so it might also be a small issue on out side
[22:00] <gmb> ronny: Okay. I'm investigating. I think the issue is in the plugin rather than in what launchpad is passing to it (otherwise it would fail for everyone, and it doesn't) but I want to be sure exactly what the problem is and if necessary issue a patch for it.
[22:01] <MTecknology> kiko: Hey.... you available?
[22:01] <ronny> hmm, let me get some logins
[22:07] <MTecknology> Why can't kiko be around... I started talking to him once and he ran away... :P
[22:07] <MTecknology> I don't think I smell that bad
[22:08] <ronny> MTecknology: kiko is a very busy man - you have to be very assertive
[22:09] <MTecknology> ronny: hrm... I know he's busy - that's why I tried to be polite
[22:09] <MTecknology> kiko: HERE, NOW!
[22:09] <ronny> hmm, you might need a whip
[22:09] <MTecknology> no - that just feels wrong :P
[22:12] <ronny> gmb: we noticed that the permissions in our egg cache where fscked, that caused sporadic random server errors
[22:12] <ronny> i think its fixed now
[22:18] <kiko> MTecknology, heh, ok. how are you doing?
[22:18] <kiko> hey ronny
[22:20] <MTecknology> kiko: doing great, I devoted my entire spring break to getting that theme done... it's 100% perfect in IE7 and Firefox
[22:21] <MTecknology> kiko: Is there any chance I could steal some of your day away from you? :)
[22:21] <kiko> heh
[22:21] <MTecknology> oh - theme almost 100% if IE6
[22:21] <kiko> MTecknology, yes, you have me for 2 minutes
[22:22] <MTecknology> kiko: https://answers.edge.launchpad.net/launchpad/+question/62325
[22:23] <kiko> MTecknology, I am physically opposed to a project which is named anything-releases
[22:23] <kiko> it just screams bad modeling
[22:23] <MTecknology> kiko: That's just where I package the compilation of everything
[22:24] <kiko> mmm
[22:24] <MTecknology> kiko: That was only if you approve the ubuntu-drupal super project, then that thing has a place to move too
[22:24] <MTecknology> kiko: I can pick any name you think appropriate for that :P
[22:25] <kiko> I'm thinking, but I think you're right
[22:25] <rockstar> statik, yo.
[22:26] <kiko> MTecknology, what does ubuntu-drupal-openid, etc have that is special that drupal-openid wouldn't have?
[22:26] <kiko> i.e. why isn't this drupal-openid?
[22:27] <MTecknology> ubuntu-drupal-openid is where the active development takes place, Canonical QA merges those changes to drupal-openid after they check everything
[22:27] <MTecknology> same with those other 2 devs
[22:28] <kiko> what's the reason for that to be a separate project?
[22:28] <kiko> I'm a bit baffled as why those aren't just devel branches of drupal-openid
[22:29] <kiko> it suggests abuse of project
[22:29] <MTecknology> Stuart Metcalfe seemed to really like the idea
[22:29] <kiko> this is why I really don't like that request -- when I start looking into it it just looks totally wrong
[22:29] <kiko> yeah, and I think he's crazy
[22:29] <MTecknology> lol
[22:29] <kiko> we put in 2 man-years of work to get codehosting to do exactly what you are doing
[22:29] <kiko> and then you create separate projects and defeat us in one button click :)
[22:30] <MTecknology> you could name them drupal-openid-dev if you wanted...
[22:30] <kiko> no
[22:30] <kiko> they shouldn't exist
[22:31] <kiko> they should just be branches of the existing drupal-openid branch
[22:31] <kiko> all under the drupal-openid project
[22:31] <kiko> using a separate project makes no sense!
[22:31] <MTecknology> The reason we made another branch for it was for all of us to work on w/o worrying about who has access
[22:31] <MTecknology> another project*
[22:32] <MTecknology> Stu was making sure that nobody except those select few has access to the trunk
[22:32] <kiko> MTecknology, you can have separate branches under the same project. I repeat, there's no reason to have separate projects.
[22:32] <kiko> separate branches, owned by different people and teams, I underline
[22:32] <kiko> do you see what I mean?
[22:32] <MTecknology> could you assign a team to have control over just that branch?
[22:33] <kiko> YES
[22:33] <kiko> YES
[22:33] <kiko> YES
[22:33] <kiko> heh
[22:33] <kiko> I guess this must be really confusing
[22:33] <MTecknology> sorry
[22:33] <kiko> I have the curse of knowledge!! argh
[22:33] <kiko> so
[22:33] <kiko> in summary
[22:34] <kiko> just move the branches over to the drupal-openid project
[22:34] <MTecknology> k
[22:34] <kiko> the owner of the branch will remain unchanged
[22:34] <kiko> i.e.
[22:34] <MTecknology> that much makes sense now
[22:35] <kiko> if it is currently https://code.edge.launchpad.net/~ubuntu-drupal-modules/ubuntu-drupal-openid/6.x
[22:35] <kiko> all that will change
[22:35] <kiko> is that it will be
[22:35] <kiko> if it is currently https://code.edge.launchpad.net/~ubuntu-drupal-modules/drupal-openid/6.x-ubuntu or whatever
[22:35] <kiko> sorry, strike that last sentence and replace with:
[22:35] <kiko> https://code.edge.launchpad.net/~ubuntu-drupal-modules/drupal-openid/6.x-ubuntu or whatever
[22:35] <kiko> IOW
[22:35] <kiko> the ~ bit stays the same
[22:35] <MTecknology> iow?
[22:35] <kiko> and the project changes
[22:35] <kiko> so for that branch, only members of ubuntu-drupal-modules can commit to it
[22:36] <kiko> even though it is part of another project
[22:36] <MTecknology> ok
[22:36] <MTecknology> then I just destroy the projects...
[22:36] <kiko> yeah, I can do that as soon as you've finished
[22:37] <MTecknology> ok - after I do that, would you be opposed to making a super project with those different projects?
[22:37] <MTecknology> the ones I move the branches to
[22:37] <kiko> do you think it makes sense to make drupal-openid a member of a project group called ubuntu-drupal?
[22:37] <kiko> I think that will turn off pure drupal users..
[22:38] <MTecknology> It'd still be the Ubuntu Drupal project doing the developement on it
[22:38] <kiko> no..
[22:38] <kiko> well, the ubuntu teams
[22:38] <kiko> not opposed, but I think it does turn off people that have nothing to do with ubuntu
[22:38] <kiko> do you see my point?
[22:38] <MTecknology> ya
[22:39] <kiko> drupal-openid is an independent entity in a way -- any fedora user that uses drupal can use it and benefit
[22:39] <kiko> as soon as you place it under ubuntu, that value decreases
[22:39] <MTecknology> except that they only work w/ Launchpad
[22:39] <MTecknology> I saw it as Ubuntu and Launchpad being related
[22:40] <MTecknology> common link: canonical
[22:40] <MTecknology> so when we do that - no point in the super project
[22:41] <kiko> well..
[22:41] <kiko> do they only work with launchpad, or is it with any openid provider, launchpad being the default?
[22:41] <MTecknology> only launchpad
[22:41] <kiko> why?
[22:41] <kiko> the openid stuff should be totally generic
[22:42] <kiko> is it because of the teams stuff?
[22:42] <kiko> or something else?
[22:42] <MTecknology> drupal-openid has modified code so it'll work with the drupal-launchpad and and drupal-teams modules
[22:42] <kiko> interesting
[22:43] <MTecknology> I think drupal-openid by itself still works fine w/ any provider
[22:43] <MTecknology> but the other two modules won't work w/o the modified code
[22:43] <kiko> gotcha
[22:43] <kiko> so
[22:43] <kiko> here's my suggestion
[22:43] <kiko> move the branches across
[22:43] <kiko> there's only reason to keep the branches separate if they are really meant to be long-lived forks
[22:43] <kiko> if they are just devel branches, then they live under the main projects
[22:44] <MTecknology> k
[22:44] <kiko> I think we should create a project group
[22:44] <kiko> to group ubuntu-drupal-theme and ubuntu-drupal if you mean the last one to be a long-lived branch
[22:44] <MTecknology> I'll do that - It might take me a little bit since I'll need to run it by stu and everyone else
[22:44] <kiko> I'm unsure about drupal-planet
[22:44] <kiko> is it like drupal-openid in the sense that it's ubuntu-unspecific?
[22:45] <kiko> or is it more like ubuntu-drupal-planet?
[22:45] <MTecknology> We were trying to mimic planet.ubuntu.com
[22:45] <kiko> or is it just a branch of ubuntu-drupal?
[22:45] <kiko> err
[22:45] <kiko> a branch of drupal sorry
[22:45] <MTecknology> not a branch of drupal
[22:45] <MTecknology> module for it
[22:45] <kiko> gotcha
[22:45] <kiko> so...
[22:45] <kiko> guideline for you in the future
[22:46] <kiko> if the thing is going to have releases (i.e. tarballs) it is a project
[22:46] <kiko> if it is just a bunch of branches of some existing project, put the branches in that project -- the branches will still be owned by whatever team you specify!
[22:47] <kiko> I think drupal-openid is likely to be standalone, or maybe part of the drupal project group
[22:47] <kiko> as I suspect drupal-openid should be
[22:47] <kiko> MTecknology, want me to write this up in the answer?
[22:47] <MTecknology> sure
[22:47] <MTecknology> That way I always have a reference rather than in logs
[22:47] <kiko> MTecknology, I really don't want to be difficult -- I just want to make sure you get the most out of launchpad by using the features :)
[22:48] <MTecknology> yup :)
[22:48] <MTecknology> kiko: would you consider drupal-{launchpad,teams} part of the project group since those interect directly with launchapd and only launchpad?
[22:49] <MTecknology> the teams module was considered for being opened to other openid providers, but we pretty quickly dismissed it because their would be too much each provider would have to exactly match for it to work
[22:49] <kiko> MTecknology, no
[22:49] <MTecknology> ok
[22:49] <kiko> MTecknology, because it's not ubuntu-specific
[22:50] <MTecknology> alrighyty
[22:50] <kiko> if you want to call the project group something like "Drupal Futurism" or whatever
[22:50] <MTecknology> hey...
[22:50] <kiko> then I think it might be more appropriate
[22:50] <kiko> is there a drupal project group already?
[22:50] <MTecknology> I like that
[22:50] <kiko> heh
[22:51] <MTecknology> ya, there is
[22:51] <kiko> my point is to keep the stuff ubuntu-neutral to the extent it is possible and useful
[22:51] <kiko> if there is stuff that is more closely related to drupal, put it in the drupal project group!
[22:51] <kiko> that way it's advertised more widely
[22:51] <MTecknology> you wanna give me a few seconds here
[22:52] <MTecknology> eh... nvm
[22:52] <MTecknology> sounds good :)
[22:52] <MTecknology> kiko: what did you conclude about ubuntu-drupal-release?
[22:53] <kiko> MTecknology, I'm not sure -- asked in the question just now
[22:53] <kiko>   - The only remaining thing I'm curious about is ubuntu-drupal and ubuntu-drupal-theme. Does it make sense to actually have a project group for them? Will they release separate tarballs? Is ubuntu-drupal a fork of drupal, or a config, or a module?
[22:54] <MTecknology> there will be separate release tarballs
[22:55] <MTecknology> I just haven't made any yet for the theme
[22:56] <MTecknology> kiko: sometime in the near future, I will package released for ubuntu-drupal-theme
[22:57] <MTecknology> I'm just finishing up with some IE6 bullshit and I'll bre ready
[22:57] <kiko>  Is ubuntu-drupal a fork of drupal, or a config, or a module?
[22:57] <MTecknology> the tarball is a group of modules and themes
[22:57] <MTecknology> one theme
[22:57] <MTecknology> I devoted of 80hr this week to that theme.....
[22:58] <MTecknology> hurray spring break
[22:58] <kiko> my mom is very funny
[22:58] <kiko> she just called me
[22:58] <kiko> I am on the second story
[22:58] <kiko> and she's on the first
[22:58] <kiko> she wants me to come to dinner!!
[22:58] <MTecknology> lol
[22:58] <kiko> she says the stairs are too hard
[22:58] <MTecknology> :P
[22:58] <kiko> MTecknology, hmmmmmmmm
[22:59] <kiko> MTecknology, it's an interesting problem!!
[22:59] <MTecknology> what is?
[22:59] <kiko> the -releases thing
[22:59] <kiko> it's like an all-in-one
[22:59] <MTecknology> kiko: actually - and some point ubuntu-drupal will have branches
[22:59] <MTecknology> I'm waiting on a bazaar feature though
[22:59] <MTecknology> to do exactly that
[22:59] <MTecknology> ubuntu-drupal-package
[22:59] <MTecknology> ?
[23:00] <kiko> hmmm
[23:00] <kiko> I think -releases is okay
[23:00] <kiko> I'll do that now
[23:00] <gmb> ronny: Okay, thanks for letting us know. I don't *think* that's the problem (the error message suggests that LP isn't passing an integer where it should be), but I'll bear it in mind.
[23:00] <MTecknology> rename it if we ever come up with anything better?
[23:00] <kiko> exactly
[23:02] <kiko> https://edge.launchpad.net/ubuntu-drupal
[23:02] <kiko> yours!
[23:02] <MTecknology> kiko: oh - drupal isn't a project group
[23:02] <MTecknology> lol - so pretty :P
[23:03] <MTecknology> thanks :)
[23:03] <kiko> maybe we need a drupal project group instead
[23:03] <kiko> well, think about it
[23:03] <kiko> I'm gonna have dinner! yay
[23:03] <MTecknology> kiko: thanks
[23:04] <MTecknology> kiko: I guess I need to ask the staff to add my projects?
[23:08] <wgrant> MTecknology: No, you just set the field on your project's +edit.
[23:08] <wgrant> (which is very strange)
[23:08] <MTecknology> wgrant: oh - thanks :)
[23:09]  * wgrant makes his projects part of ~launchpad-project
[23:09] <wgrant> s/~//
[23:12] <gmb> :744
[23:12] <gmb> Err.
[23:12] <gmb> Whoops. This isn't vim, is it?
[23:12] <wgrant> gmb: Unfortunately.
[23:12] <wgrant> We have vimperator for web browsers, but nothing for IRC AFAIK :(
[23:13] <gmb> wgrant: If I had any kind of notion to hack using Perl I would write an irssi plugin to accept basic vim commands for no other reason than the desire to do so. However, I have no desire to write Perl.
[23:13] <gmb> Ever.
[23:14] <wgrant> gmb: Good policy.
[23:21] <rockstar> gmb, I can't count how many times I've typed :!bzr commit in the terminal.
[23:36] <MTecknology> kiko: when you get back - what is your opinion about making a project group for drupal and giving a team we make access to it?