[00:30] ScottL: I'll take a quick look: I suspect we can get audacity, fontforge, gtick, and qsynth updated if there's anything useful. rakarrack would need testing and strong rationale. [00:31] The same logic would apply to outdatedandlocalinB [01:43] I'd be happy to make whatever necessary bugs are required [01:44] since we have trouble getting any testing done, then I'll make a reminder to reevaluate rakarrack after lucid is released [01:44] oh, and persia, if you don't have time to look at audacity, etc I'll be happy to do that as well to see what's improved [01:46] as for a 'outdated and local changes', the majority didn't seem to be huge changes (at least judging from version numbers) and I thought since they would require changes they would be more difficult to get FF exception approval [01:47] It's the case where there's a change to the debian revision, but not the upstream version that tends to interest me most. [01:48] The upload happened for a reason, and it usually closes a bug. [01:48] (or several bugs) [01:48] So it's a matter of checking if the bugs that got closed are interesting [01:50] For example, if I look at audacious-plugins [01:50] The Debian changes are listed at http://changelog.debian.net/audacious-plugins [01:51] This looks fairly serious, but audacious-plugins doesn't appear at http://qa.ubuntuwire.com/ftbfs/ (launchpad records) or http://udd.debian.org/cgi-bin/ubuntu_ftbfs.cgi (rebuild test), so it's actually not important. [01:52] cdrdao appears to be an ubuntu -> debian merge, so no worries. [01:53] Conversely, audacity fixes a track export bug. [02:00] hmmm, didn't think of that (closing bugs) that makes a whole lot of sense and is extremely useful [02:01] Yeah. The development viewpoint tends to be very different than the marketing viewpoint. If something small changes in something that doesn't usually get updated, it's often critical. [02:02] If something big changes in something that gets updated regularly, it's often uninteresting because there's an even chance it introduces as many issues as it resolves. [02:03] But when promoting stuff, the small rare changes are uninteresting, and the big flashy features are exciting and can garner several paragraphs. [02:05] persia, do you ever sleep? most time I see you active online [02:07] I sleep. I'm just not diurnal, and I travel not infrequently, so it may create the wrong impression based on various assumptions. [02:07] Note that it look me > 7 hours to get back to you earlier, which is the sort of thing that may be an indicator of when I'm away. [02:08] s/look/took/ [02:09] (being away isn't always sleep, but sleep is always being away) [09:49] * abogani waves [11:05] hi abogani, i got delayed a bit in testing kernels this weekend but I will try to start tonight [11:06] my wife got sick this weekend, luckily I haven't so far and I'm really hoping I don't ;) [11:07] * ScottL is going to work will log on again when I get there [12:07] ScottL: Don't worry about kernels! Take care of your wife instead! :-) [12:28] abogani: she puked all day saturday, slept most of Sunday and is right as rain yesterday...I just hope I dont' get it ;) [12:29] * abogani don't know what means "right as rain"... [12:31] ScottL: ^ [12:32] abogani: "In good health" [12:32] persia: Ah Thanks! [12:32] ScottL: So I'm happy for your wife! :-) [12:48] * abogani wondering if there are news about Studio lead (tech and in general).. [13:40] I have some thoughts about team positions along with community involvement but I'd like to develop them a little more before presenting them [13:40] perhaps by the end of this weekend I'll something a little more cohesive and tangible [13:41] I'm extremely opinionated about that sort of thing. I'd love to critique something once you have it ready. [14:30] Capital! Feedback, especially critical feedback, would be most appreciated. [14:32] I can certainly provide that :)