[12:15] <ddaa> Is there some documentation explaining what are the benefits or being the owner of a launchpad product?
[12:15] <ddaa> jblack: that would be something useful when talking to community folks about taking ownership of products in launchpad.
[12:37] <jblack> Not that I'm aware of, no
[12:38] <jblack> Presumably the two benefits would be karma, control or both. 
[12:38] <jblack> I don't think karma is in yet. Control is a more interesting question, but it might not hurt until there's a little more implemented. That doesn't mean we can't make a nice document and have it ready 
[12:44] <ddaa> I do not feel that karma bling is really a good selling point for pragmatic maintainers, for I would not care the least. It's more the specifics of the "control" that I'm asking about. I posted to the mailing list.
[01:00] <jblack> Certainly, there's going to be a point when there's enough value in launchpad that a creator of a product will want to be the launchpad owner as well.
[01:00] <jblack> They'll want to take personal responsibility for that content. 
[01:01] <jblack> daf and rosetta as well.
[01:02] <jblack> I have no doubt that if not today, then soon the product owner gets to decide who has awesome powers when it comes to bugs for a product.
[01:03] <jblack> rosetta probably has a copule weak relationships. 
[01:03] <jblack> The product series management will be very, very important too, once there's enough percieved value there.
[01:04] <ddaa> but it's not clear how useful such "awesome powers" are for a product that already has its own bug tracker.
[01:04] <jblack> It will be once malone is so good, that anybody that uses anything else will be a dope. =D
[01:04] <ddaa> I'm not being negative, just trying to keep focus on "now and here".
[01:05] <ddaa> Since I'm sure there's more to Launchpad that I'm aware of.
[01:05] <jblack> "What do I miss if you delay taking ownership until next week, if I'm not using malone anyways?" 
[01:06] <jblack> "What do I miss if I delay taking ownership of a product until next week, if I'm not using malone anyways?" 
[01:06] <jblack> Is that the question? 
[01:48] <ddaa> The question from the scribus guy was more like "why should I care about launchpad"
[01:48] <ddaa> which was a genuine question
[01:49] <ddaa> not "why should I care this week and not next week", but "why should I care today".
[01:50] <ddaa> but maybe that's just my own perspective
[01:50] <ddaa> like some guy pointed out, I believe in working code, not in shiny ideas.
[02:27] <jblack> What I'm trying to get out of this is whether he's asking why he should care today, or why he should care at all
[02:31] <ddaa> does that make any practical difference?
[02:37] <jblack> I think so.
[02:39] <jblack> If he doesn't care today, then he has a understanding of the possible value, but doesn't recognize current value. 
[02:39] <jblack> If he doesn't care at all, then he doesn't recognize possible value as well. 
[02:39] <ddaa> Well, they were quite friendly, I guess he was asking about today. "You can assign it to me once my account registration goes through, that's fine. What can we do with it is the question?"
[02:39] <ddaa> I just understand that as a "that's cool, but what is it useful for?"
[02:40] <jblack> Heh. I wonder what my life would be like if I had registered certain domain names back in the mid 90's.
[02:41] <ddaa> That's a different thing. We'll arbitrate disputes sensibly, and anyway the owner is a core developper.
[02:41] <ddaa> Clearly, if it were not possible to speculate on domain names, websquatting would be pointless.
[02:42] <jblack> I'm not suggesting that he squat. :) 
[02:42] <ddaa> That was a "okay, the product is in good hand, and you can assign it to me if you want, but then what?"
[02:42] <jblack> I'm suggesting that he can avoid the inconvience of contacting a human if somebody else squats on his property.
[02:43] <jblack> but then what? Then we'll get ahold of him when we've got somethign ready that we think he needs. 
[02:44] <jblack> Today, we've got the resources to hunt down owners for many of the owners of ~1k products. We likely won't have those resources when we've got 50 times that. 
[02:44] <ddaa> Ha, that's a interesting answer "we're working hard to make launchpad something you will want to use, the product owner is the person we will spam when we think it's ready"
[02:44] <jblack> Nah. Thats not spam. 
[02:45] <jblack> spam is centered around money. This isn't. 
[02:46] <ddaa> Maybe "launchpad is something you will want to use as a packager when it's ready. It's not ready just yet, but if you are the project owner we will contact you with interesting news and events"
[02:46] <ddaa> duh...
[02:47] <jblack> You've got a point (a good one too, a lot of people could think that way). 
[02:47] <jblack> So we do a standard do-not-contact checkbox.
[02:47] <ddaa> then, back to the original question
[02:48] <ddaa> why, as a project maintainer or core developer, should someone care today about it?
[02:48] <jblack> David, if he's not interested right now, then that's ok. He'll come along on his own some day. 
[02:48] <ddaa> (except for the import, since it that case it was already done)
[02:49] <ddaa> jblack: you're missing my point, the guy was not "not interested". Actually, you could read it as he was asking us what interesting stuff we had for him.
[02:49] <jblack> Did you consider the "we did this import info in the hope it would be useful to you. Now that the work has been done, would you mind registering as the proper owner of the product, so that the product is owned by the right person rather than a canonical developer?"
[02:50] <ddaa> Let's play a game. I'll play the maintainer.
[02:50] <ddaa> To what you just said, I reply:
[02:51] <ddaa> "You can assign it to me once my account registration goes through, that's fine. What can we do with it is the question?"
[02:52] <jblack> One of the things that you can do right now is that you can assign extra product series to your import. That way a program named dyson can be used by the distributors to track patches for your software. That way, end users can compare whats been fixed where. 
[02:52] <ddaa> IOW, "no problem, I'm creating my account so you can assign the product to me. Thanks for the import, that's going to be useful. Now that the import is running automatically, what else can I do with that product?"
[02:52] <jblack> Are we role playing, or debugging? :) 
[02:52] <ddaa> "How do I use Dyson"?
[02:53] <ddaa> Roleplaying to debug the argumentation :)
[02:53] <jblack> Dyson isn't the thing that's actually used. The actual interface is going to be through the bug tracker, malone. Don't worry, you don't have to use malone if you don't want (in fact, if you're using bugzilla, malone tracks things for you) 
[02:54] <jblack> The important part is that the people that are packing your software for you and giving it to the community for you are going to be able to track patches for your software much more efficiently. 
[02:54] <jblack> There's other things as well, if you're interested. ;) 
[02:55] <jblack> We have plans in the near future of implementing something at the supermirror called "starring".
[02:56] <ddaa> "Actually, I'm the packager. The baz import will allow me to package using tla-buildpackage. But the import is already running."
[02:56] <jblack> As the maintainer of a product, you can note for end users which third party branches for your product are important. Its a way for you to help developers of your software to know which branches you're interested in.
[02:56] <jblack> Oh, which distro do you package for? 
[02:56] <ddaa> "I'm packaging for ubuntu"
[02:57] <jblack> Oh. In that case, you're gonna do it because if you don't, Mark will shove his size-X boot up your ass. ;) 
[02:57] <ddaa> (taking user hat off) the thing you say about third party branches is not true, yet
[02:57] <jblack> I didn't say its true now. I said it's going to be true. :) 
[02:57] <jblack> btw, I wouldn't make the boot comment, at least not in those terms. 
[02:58] <jblack> Id actually say something more along the lines of "If you're already in ubuntu, then you probably have a good idea of where we're going, and why we're trying to get the dataset as accurate as possible" 
[02:58] <ddaa> The guy appeared to be quite reasonable, not hostile, but not a fanboy either.
[02:58] <jblack> He's a ubuntu developer? 
[02:59] <ddaa> nope, it's just the upstream
[02:59] <jblack> Ok. So he's not the packager, correct? 
[03:00] <ddaa> the -ubuntu packages versions are done by doko, jriddell and so on. He is signing the changelog entries for version that are not specific to ubuntu. He is the upstream packager.
[03:00] <jblack> Ok. sync.
[03:00] <ddaa> http://packages.ubuntu.com/changelogs/pool/main/s/scribus/scribus_1.2.2.1-1ubuntu1/changelog
[03:00] <jblack> In that case, I'd mention the plans for malone doing multi-distro tracking and ubuntu-upstream tracking.
[03:01] <jblack> We also are in strong need for projects that are willing to be test subjects for us. 
[03:02] <ddaa> mh... I sort of see the point, but that starts to be a bit complicated for me...
[03:02] <jblack> If he helps us by letting us use him as a test case, then the process is going to be salted with his input, and give him tools that are closer to his needs.
[03:02] <ddaa> I guess that the guy might be receptive to that.
[03:02] <jblack> Most developers are. :)
[03:03] <jblack> Another approach I'd consider (I'd have to know him reasonably well first) is the old changing-the-world argument.
[03:04] <ddaa> But I do not really feel up to the task of convincing him. "We are going to track your bugtracker in malone, and other distro bucktrackers as well. Okay, it's not really working yet and it sucks as a bug tracker, but if you would beta-test the stuff for us we would do our best to make Malone something you'd use every day"
[03:04] <jblack> (Nobody likes to think that they're getting in the way of an einstein)
[03:04] <jblack> ddaa: That's ok. Its my job to do that. :) 
[03:05] <jblack> The very, Very useful thing you could do to help getting this done is to give him a favorable introduction of me. 
[03:05] <jblack> That should be easy. I'm a nice, patient guy and I rarely bite. 
[03:06] <ddaa> well, I'm certainly ending up doing a fair bit of it myself, as I'm going to interact with community guys as part as the import sheperding etc.
[03:06] <jblack> Hur? I thought I was sheparding imports? 
[03:06] <ddaa> ha?
[03:06] <ddaa> Well, that's fine.
[03:07] <ddaa> All this stuff just came from a reply I made for a bug.
[03:07] <jblack> I could be desynced here (that happens to me) 
[03:07] <ddaa> "cannot create project scribus"
[03:07] <jblack> But my impression from the self appointed one was that I'd be the human interface to imports and keeping an eye on it. 
[03:07] <ddaa> that naturally led me to assign the guy as the owner of the product (i.e. not the packager), and going to #scribus to make publicity and ask if the guy was known and trustworthy.
[03:07] <jblack> Presumably, if there was a problem with the back-end, I'd dump it into some queue somewhere for attention by the guys that have worked ont he code for a yaer. 
[03:08] <ddaa> Yeah, it completely makes sense. But then there's not point in setting to strong a separation.
[03:08] <jblack> Yeah. I wasn't planning on that. 
[03:09] <jblack> Basically, continuing the old process. Keeping a list of various failures. As time permits, you or lifeless hit the failures.
[03:10] <ddaa> As we get better at diagnosing common failures it would make sense for you to work on the diagnosing as well, as that would enable you to do on-the-spot support.
[03:10] <jblack> If something particularly juicy comes up, I might ping you for a canfix/cantfix 
[03:10] <ddaa> Whatever, no point is arguing semantics.
[03:10] <ddaa> Let's just get the work done :)
[03:11] <jblack> And yes, I'm open to that. 
[03:11] <jblack> ("Let's get..." and "make sense for you..." 
[03:12] <jblack> I'd probably avoid the complicated ones though, as I have the impression from mark that I should be more concerned about hitting the pavement, so to speak.
[03:12] <ddaa> That's my understanding, though second hand, too.
[03:13] <ddaa> That malex guy seems to be away ATM. I'll ping you to to arrange a fortuitous encounter when he seems back :)
[03:13] <jblack> Ok.
[03:13] <ddaa> do you think I should do that in private or public?
[03:14] <jblack> Is he an independant sort, or a community sort? 
[03:14] <jblack> If we're dealing with a Lord, then private. If we're dealing with a Raadt, then community. 
[03:15] <jblack> Private is generally slightly better, because its better to already ahve a convert amongst the group, so that he does most of the selling.
[03:15] <ddaa> Dunno Raadt, but he seems rather oriented towards his own community.
[03:15] <ddaa> Okay.
[08:22] <dilys> Merge to thelove@canonical.com/dists--bazaar--1.5: new build (patch-58)
[08:25] <dilys> Merge to thelove@canonical.com/bazaar--devo--1.5: Added a -m, --modified option to baz commands displaying revision lists (patch-44: Matthieu.Moy@imag.fr)
[10:08] <sivang> ddaa, jblack : can anyone at that stage contribute patches to bazaar ? 
[10:11] <nakeee> all the translation I upload rosetta get to the original projects?
[10:19] <sivang> nakeee: there's a mechanism to push them back to the upstream project, IIRC so yes
[10:21] <nakeee> sivang: hwo many translators are using it in hebrew?
[10:23] <sivang> nakeee: you can check through rosetta, let me see
[10:26] <sivang> nakeee: we don't have a registered translators group, guess we'll have to make one
[10:26] <sivang> nakeee: done with tests? :)
[10:29] <nakeee> sivang: hopefully I have a bit free time now:) can I have the permission to add translators?
[10:30] <sivang> nakeee: let's see
[10:30] <sivang> Anyone here can help us set up a hebrew translation group?
[10:30] <sivang> jordi: ping , howya doing? 
[10:31] <jordi> hi!
[10:31] <jordi> right now I'm berserking
[10:31] <sivang> jordi: you're waht?
[10:31] <sivang> :)
[10:32] <jordi> raging
[10:32] <jordi> I'm veeery annoyed today.
[10:32] <sivang> jordi: oh, I'm sorry to hear that.
[10:35] <sivang> jordi: do you know who approves new language translation groups?
[10:35] <jordi> hmm, probably carlos right now.
[10:35] <jordi> aha!
[10:36] <carlos_> hi
[10:37] <sivang> carlos: hey carlos
[10:37] <sivang> carlos: What do I need to do to start a hebrew translation team in rosetta ?
[10:38] <carlos> sivang, send an email to rosetta@ubuntu.com asking for it
[10:38] <sivang> jordi: btw, may I as why are you annoyed?
[10:38] <sivang> carlos: ok, what happens when you open it ? I become moderator / whatever and can approve new translators? can I then delegate it to another person?
[10:38] <nakeee> sivang: who is going throught the translation people submit for hebrew?you?
[10:39] <jordi> sivang: I learned just now that I'm forced to give a talk in "Campus Party" about LliureX
[10:39] <sivang> jordi: hmm, is this some kind of an academic project?
[10:39] <nakeee> hmm that's not good
[10:40] <nakeee> so all the translations ppl did so far didn't get in?
[10:40] <carlos> sivang, as we know you, we can add you as the admin for that team and you can add other admins 
[10:40] <carlos> jordi, ;-)
[10:40] <sivang> nakeee: what carlos said :)
[10:40] <sivang> carlos: what happened to all translations of poeple so far?
[10:40] <carlos> sivang, is there a problem with their translations?
[10:42] <jordi> sivang: no, one of these meetings of people with pcs where they spend a week copying porn, warez and movies and sleep very little
[10:47] <sivang> carlos: thinking of the moderation now, something must have been done with the translations - either they are held back until review, or already in
[10:47] <sivang> carlos: which is the right case?
[10:47] <carlos> sivang, you will see them as suggestions
[11:14] <nakeee> carlos: I see there are suggestion from other places and found somewhere else comments
[11:14] <nakeee> is it something rosetta adds?
[11:15] <carlos> nakeee, those are translations related to the one you are doing from other versions of that resource or from other projects
[11:16] <nakeee> what other projects?
[11:17] <carlos> nakeee, anyone imported into Rosetta
[11:17] <nakeee> oh it looks for similar strings?
[11:17] <carlos> we will add a link to the origin of that suggestion
[11:17] <carlos> yeah
[11:18] <nakeee> carlos: a use suggestion button might be nice so one wont need to copy paste it
[11:18] <carlos> nakeee, planned too
[11:22] <nakeee> is there a way to add a dictionary project?like something that the string would be the words that appear in all other projects 
[11:22] <nakeee> and then it can be used as reference while translating
[11:22] <nakeee> to make sure wording is the same
[11:23] <carlos> nakeee, well, it would be a bit difficult
[11:23] <nakeee> how so?
[11:23] <carlos> as we work with the whole string
[11:23] <carlos> so you need to add lots of terms there
[11:23] <sivang> carlos: I'll email rosetta@ubuntu.com, for the translation group , k? :)
[11:24] <carlos> but there is also a glossary like feature that will handle that by words
[11:24] <carlos> sivang, sure
[11:24] <nakeee> well, it  can use a word list but I thought like that it would be more effective
[11:24] <nakeee> carlos: it just a script that need to run once and in the future just adding few words is no big deal
[11:25] <sivang> carlos: done
[11:26] <carlos> nakeee, if you want to translate 'File' the same across all Ubuntu, you need it done with a glossary like feature
[11:26] <carlos> it's really difficult to store all kind of strings that contains that word
[11:27] <carlos> so you translate it always the same
[11:27] <nakeee> that not what I mean
[11:27] <nakeee> I mean it more as a hint to the translator
[11:27] <nakeee> he can click on the word file and see how it appears in the dictionary
[11:27] <nakeee> so he won't need to go around looking how it was in other projects
[11:29] <carlos> nakeee, so you are talking about a html file with a list of words
[11:41] <nakeee> carlos: yes only 1) I can translate those words using rosetta interface 2)I can quickly ask from inside rosetta what is certain's word translation
[11:55] <carlos> nakeee, that's not so trivial as you think...
[11:56] <nakeee> in what sense?
[11:58] <carlos> that we cannot do it in an afternoon 
[11:59] <nakeee> maybe, but I think it would be worse it
[11:59] <nakeee> it would make the translation level of people a lot higher
[12:06] <carlos> I know, and as I said, it's a planned feature
[12:23] <nakeee> ok cool
[12:59] <jblack> when is the meeting? Now or now +1 ?
[12:59] <daf> now+1
[01:00] <jblack> be back
[01:12] <jordi> daf, carlos: where are we regarding importing/exporting?
[01:12] <jordi> is it fixed in production now?
[01:12] <jordi> I can't start mailing people if it's not working right now
[01:12] <jordi> would scare people away.
[01:13] <daf> we were just discussing it
[01:13] <carlos> jordi, we can add new potemplates now
[01:13] <daf> seems like breezy imports are being really slow
[01:13] <carlos> jordi, but the import is being a bit slow
[01:13] <jordi> nod
[01:13] <daf> and slowing the other imports down
[01:13] <carlos> and that slows too other imports
[01:13] <carlos> X-)
[01:13] <daf> :)
[01:13] <carlos> daf, get out of my mind!
[01:13] <jordi> stop the echo effect
[01:15] <daf> carlos: I suggest you mail launchpad about the problem
[01:15] <daf> carlos: perhaps Steve or somebody will have an idea about debugging it
[01:17] <carlos> daf, well, I suspect where the problem would be
[01:17] <carlos> daf, but hadn't time to test my theory
[01:17] <daf> what's your hypothesis?
[01:19] <carlos> daf, that the imports are failing because the poimports from breezy are attached by Rosetta admins and they are not editors
[01:21] <daf> why would that make it so slow?
[01:23] <carlos> because it takes time to do an import that it's rejected
[01:23] <daf> hmm
[01:23] <daf> and the rejected ones stay in the queue?
[01:26] <carlos> yeah
[01:26] <carlos> so a restart makes it slower
[01:26] <daf> ouch
[01:26] <daf> wait a minute
[01:27] <daf> I thought they were marked as Failed
[01:27] <daf> and not tried again
[01:28] <carlos> daf, it depends on the kind of error
[01:30] <daf> isn't that a bug?
[01:31] <daf> what if we change the permissions somehow?
[01:37] <carlos> permissions?
[01:37] <carlos> so it doesn't fall?
[01:38] <carlos> fall/fail/
[01:38] <carlos> that's the plan, yes
[01:42] <daf> what's blocking it?
[01:44] <carlos> daf, I was working on the language packs, remember?
[01:44] <carlos> :-)
[01:53] <daf> carlos: how are the language packs going? :)
[01:53] <carlos> daf, added to the review queue
[01:53] <carlos> and being executed on mawson
[01:54] <jdahlin> elmo?
[02:02] <jblack> time for the weekly meeting? 
[02:03] <daf> yes
[02:03] <daf> but no SteveA
[02:03] <jdahlin> there's no internet connection in the office here in brazil, where the meeting is held
[02:04] <daf> ahh
[02:04] <daf> that explains it :)
[02:07] <jblack> Is somebody keeping a log, and we can just meet and send stevea the log? 
[02:07] <daf> I expect we'll have the meeting when they get their internet connection back
[02:07] <daf> there's no point having a meeting with 4 people :)
[02:07] <carlos> daf, :-)
[02:08] <bob2> hah
[02:22] <morgs> 3
[02:22] <morgs> 2
[02:22] <morgs> 1
[02:22] <morgs> MEETING E...
[02:22] <morgs> oh] 
[02:23] <morgs> hiya
[02:23] <SteveA> hi
[02:23] <SteveA> no meeting today
[02:23] <SteveA> the internet went down
[02:23] <jblack> !!
[02:26] <SteveA> daf, carlos, jblack, ddaa, morgs: the launchpad wiki will be read only for a few days
[02:26] <ddaa> blah
[02:26] <SteveA> so that we can work from it directly here in brazil, in case our network goes down again
[02:26] <carlos> SteveA, ok
[02:26] <morgs> You took the wiki with you?
[02:27] <ddaa> I was just running upstairs with my breakfast...
[02:27] <carlos> SteveA, how will we handle the review queue?
[02:27] <SteveA> carlos: good question
[02:28] <SteveA> carlos: first of all, we won't have any reviewers available until later next week anyway
[02:28] <carlos> SteveA, I'm asking because I just added an entry there
[02:28] <carlos> ok
[02:28] <SteveA> carlos: that's okay. 
[02:28] <daf> yeah, I added a page just now
[02:28] <SteveA> carlos: secondly, if we have urgent reviews then you need to mail them
[02:28] <daf> apparently, I am now DafyddHarries4
[02:28] <SteveA> if you have urgent updates to pages, you need to mail them to here and tell people
[02:28] <SteveA> daf: you need to talk with stu about that
[02:29] <daf> ok
[02:29] <carlos> ok
[02:29] <carlos> daf, I think you can change it from launchpad
[02:30] <SteveA> it is possible that you can't
[02:30] <SteveA> if you can't, tell stu
[02:32] <carlos> stub, I will need to cherrypick a patchset today, would it be possible?
[02:32] <carlos> daf, my theory was correct, I have a test and the fix ready
[02:32] <stub> Email me and lifeless as per usual
[02:33] <daf> carlos: fix?
[02:33] <daf> carlos: make it fail when the permissions are wrong?
[02:33] <daf> carlos: or rather, makrk the import as failed
[02:34] <carlos> hmmm
[02:34] <carlos> daf, that other fix should be done too. Thank's for remind me it
[02:34] <daf> heh
[02:34] <daf> what was your fix?
[02:34] <daf> even better, check the permissions *before* doing the import
[02:34] <daf> to avoid doing unneccessary work
[02:35] <carlos> daf, canEditTranslations returns True always if it's a rosetta expert
[02:36] <daf> ah
[02:36] <daf> rosetta admin, you mean?
[02:36] <daf> does that use a celebrity?
[02:37] <daf> if it doesn't, it should
[02:37] <carlos> it does
[02:37] <carlos> that's why I said Rosetta expert ;-)
[02:37] <daf> hmm
[02:37] <daf> ok
[02:41] <carlos> hmmm
[02:41] <carlos> daf, the error is: raise AssertionError, 'published translations are ALWAYS is_editor'
[02:41] <carlos> daf, that was a programming error that the test will detect in the future
[02:42] <carlos> I don't think we should try to catch that exception
[02:42] <daf> can we change that message to something clearer?
[02:42] <daf> and it's better to use AssertionError("...")
[02:42] <daf> not AssersionError, "..."
[03:12] <salgado> lifeless, can you check what happened with a merge request I sent 30mins ago? I didn't get any mail from pqm and it's already processed
[03:12] <morgs> cprov: some friends of mine use jira, very shiny but in java...
[03:15] <cprov> morgs:yeah, I've seen it in a comparision with Trac (http://trac.edgewall.com) which smells much better because is python
[03:18] <lifeless> looks like it failed
[03:18] <lifeless> I'm betting your mail is borked after the outage and the result will come later
[03:41] <jblack> lifeless: I had a couple problems to tell you about this morning, but they're worked out. 
[03:41] <lifeless> col
[03:41] <lifeless> cool I mean
[03:42] <jblack> btw, good morning. Hope you're well. =) 
[03:43] <dilys> Merge to rocketfuel@canonical.com/launchpad--devel--0: [trivial]  Bug 1279: Move bazaar branches from portal to main part of product page (patch-2183: morgan.collett@canonical.com)
[04:03] <mpt> cprov: WordPress uses Rosetta for translations, and Trac for issue/changeset tracking
[04:04] <dilys> New Malone bug 1602 filed on Bazaar by Matthieu Moy: baz inventory panic()s on unreadable directories
[04:04] <dilys> https://launchpad.ubuntu.com/malone/bugs/1602
[04:05] <ddaa> sivang: anybody can contribute to bazaar (that is baz or bzr), they are just plain vanilla free software projects.
[04:07] <sivang> ddaa: ah nice, I deduced that from the rocketfuel dillys spit outs, I saw "patch from jone doe, ....." :)
[04:08] <sivang> ddaa: but I reckon the canonical versions and the upstream vanilla are different no?
[04:09] <morgs> sivang: the canonical one *is* the upstream one...
[04:09] <jamesh> sivang: we use the same baz as everyone else
[04:10] <sivang> jamesh, morgs : ah oops, thanks fellas for the enlightment :)
[04:10] <morgs> :)
[04:15] <cprov> mpt: Trac rocks a lot, I use it for private/public issue tracking and our clients like a lot the wiki/tickets/SVNview/Roadmap integration 
[04:32] <daf> morgs: seems to me that owners of teams always get notifications about membership requests
[04:32] <daf> morgs: so I get these notifications about teams I've created but which I'm not a memeber of
[04:32] <daf> morgs: these teams do have admins who take care of the membership applications
[04:33] <salgado> daf, I fixed this in one of the branches I'm working on. that was a bug.
[04:33] <daf> cool
[04:33] <salgado> from the days before TeamEmail
[04:34] <daf> why did I think that morgs was the teams person?
[04:34] <salgado> daf, I asked that question to myself too. maybe you're the right person to answer? :P
[04:35] <daf> heh
[04:35] <daf> well, I don't know
[04:57] <dilys> Merge to rocketfuel@canonical.com/launchpad--devel--0: [trivial]  BuildFarm works again, bits repaired and ready for deep redesign. (patch-2184: celso.providelo@canonical.com)
[05:24] <dilys> Merge to rocketfuel@canonical.com/launchpad--devel--0: [trivial]  PackageVersionVerification and tweaks (patch-2185: stuart.bishop@canonical.com)
[05:45] <dilys> New Malone bug 1603 filed on Registry by Morgan Collett: RDF fails when team has an email
[05:45] <dilys> https://launchpad.ubuntu.com/malone/bugs/1603
[05:50] <dilys> Merge to rocketfuel@canonical.com/launchpad--devel--0: [trivial]  Bug 1279: Move bazaar branches from portal to main part of product page, add URL (patch-2186: morgan.collett@canonical.com)
[06:29] <kiko> carlos?
[06:29] <Keybuk> daf: see you soon
[06:30] <Keybuk> be sure to pack any diseases you might want to bring with you
[06:30] <Keybuk> everyone else has
[06:35] <dilys> Merge to rocketfuel@canonical.com/launchpad--devel--0: [r=SteveA]  add facet menus to people and projects.  add calendar link to facets (patch-2187: james.henstridge@canonical.com)
[06:39] <carlos> kiko, ?
[07:10] <dilys> Merge to rocketfuel@canonical.com/launchpad--devel--0: [trivial]  Added Rosetta experts as editors for every .po file (patch-2188: carlos.perello@canonical.com)
[08:33] <dilys> Merge to rocketfuel@canonical.com/launchpad--devel--0: Some fixes as per Steve review. Do not use Subsets to traverse; instead do the traversal by consuming items from the traversal stack. r=SteveA (patch-2189: guilherme.salgado@canonical.com)
[09:03] <SteveA> salgado: jim fulton says +1 to modifying zope/security/checker.py to have declarations for set and frozenset, using a try:except NameError to make it still work with python 2.3.
[09:03] <SteveA> salgado: you can tell stub, or whatever
[09:06] <salgado> SteveA, great. I'll talk to stub
[09:13] <SteveA> thanks
[09:20] <salgado> stub, <SteveA> salgado: jim fulton says +1 to modifying zope/security/checker.py to have declarations for set and frozenset, using a try:except NameError to make it still work with python 2.3.
[09:20] <salgado> would you fix that for me?
[09:21] <stub> shh.... I'm sleeping
[09:21] <Kinnison> lies
[09:23] <stub> ok
[11:05] <dilys> Merge to thelove@canonical.com/dists--bazaar--1.5: new build (patch-59)
[11:06] <dilys> Merge to thelove@canonical.com/bazaar--devo--1.5: Added ARCH_LOG to commit, import and tag hooks (patch-45: Matthieu.Moy@imag.fr)
[11:21] <dilys> Merge to thelove@canonical.com/dists--bazaar--1.5: new build (patch-60)
[11:22] <dilys> Merge to thelove@canonical.com/bazaar--devo--1.5: rbrowse shows revisions one-by-one (not version per-version) (patch-46: Matthieu.Moy@imag.fr)