=== doko_ is now known as doko === xfaf is now known as zul [12:05] persia: dmb meeting? [12:12] is it now or in 50 minutes? my calendar is confusing [12:12] cjwatson: I'd say now [12:12] cjohnston: it should be now [12:13] cjohnston: or to be more precise: 13 minutes ago [12:13] any chance the fridge could just get DST right [12:15] I somehow suspect the fridge isn't the problem. [12:15] * cjwatson is cjwatson not cjohnston [12:15] soren: it bit the LC already this month [12:16] czajkowski: LC? [12:17] sorry cjwatson - i should type more characters before using tab-completion [12:17] bdurng: Or not use tab-completion at all. It works great! [12:17] Oh, wait. [12:18] soren: no, it doesn't :P [12:18] soren: Loco council [12:18] hi all [12:19] hi [12:19] Hi Kmos [12:20] good to see you in a DMB meeting, I guess the first time since you sent your mail to devel-permissions? [12:20] bilalakhtar: correct. I sent an e-mail explaning why I failed the meetings [12:21] I need to run in 45 minutes, just waiting for DMB to start [12:21] hi [12:21] so we have bdrung soren cjwatson. stgraber sent apologies. any other DMB members present? [12:22] cody-somerville is probably asleep [12:22] * bilalakhtar forgot bdrung is a DMB member :D [12:24] then the question is: where is persia? [12:24] or geser for that matter [12:25] oh, yes. i can't count ;) [12:26] I wonder if we should auto-schedule a topic for these meetings a couple of weeks before DST changes in any of the countries in which we have members. Scheduling meetings for people in such a diverse set of timezones will almost always mean it's going to be a stretch for someone. [12:27] ...and when DST kicks in, that might be the... what's the expression? something that tips the scale. [12:27] soren: do all dmb members live in a country with DST? [12:27] bdrung: no. [12:28] bdrung: persia doesn't. [12:28] And the US and EU switch at different times. [12:28] oh [12:29] So we have ~4 TZ combinations that we need to deal with. [12:29] and some of us use google calendar which is known to suck at timezones. [12:29] cjwatson: I hear that a lot. I'm not sure I agree. [12:29] IME [12:30] Most stories have a (perfectly reasonable) explanation, so it's more of a question of wrong expectations. [12:30] cjohnston, really it is so (although I love all google stuff) [12:30] wop [12:30] cjwatson, above :) [12:31] soren: the fact that it hopelessly confuses people on a frequent basis is suckage, even if there's a reasonable explanation for each individual piece [12:31] how can we improve the situation? [12:32] If I schedule a recurring meeting for 8 PM, I've never seen that fail. However, if people in e.g. the US look at the same meeting, it'll move whenever the TZ delta between myself and them changes. [12:32] ...which is surprising, but correct. [12:32] can the chair man ping all members an hour before the dmb meeting start and tell them: dmb meeting in one hour? [12:33] The best solution I've seen is to switch to Icelandic time when you schedule meetings. That way, it should stay constant w.r.t. UTC. [12:33] yes, it would help not to be starting the process of rounding people up at start-of-meeting [12:33] although in this case stgraber already sent an e-mail reminder [12:33] quadrispro: Nothing is perfect. If something's wrong with the calendar, it should be accepted as a mistake and should be fixed or we, as users should work around it [12:34] which is what the DMB is doing [12:34] yep, I see :) [12:35] Sorry: time calculation failure. [12:36] *chuckle* [12:37] why are so many people bad at time calculation? i remember debian-multimedia meeting where too many calculated the wrong time. [12:38] we should start since we now have 4 [12:38] wiki says persia is chairing [12:38] #startmeeting [12:38] Meeting started at 06:38. The chair is persia. [12:38] Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE] [12:38] [TOPIC] Action Item review [12:38] New Topic: Action Item review [12:39] * persia failed to contact the CC [12:39] cjwatson to add haildb to mtaylor's PPU list [12:40] added (about five seconds ago in a panic) [12:40] [TOPIC] Review Marco Rodrigues participation in Ubuntu Development [12:40] New Topic: Review Marco Rodrigues participation in Ubuntu Development [12:40] Kmos, This was stalled, looking for CC input. Since you're here today, did you have anything you wanted to add, specifically? [12:41] persia: I don't think so, just I to appologize for no been around latest DMB meetings. [12:41] No worries. We've been indecisive. [12:42] ok [12:42] Kmos: may i ask how old are you? [12:42] bdrung: 26 years old [12:42] [TOPIC] Martin Pool's Developer Application [12:42] New Topic: Martin Pool's Developer Application [12:42] [LINK] https://wiki.ubuntu.com/MartinPool/DeveloperApplication [12:42] LINK received: https://wiki.ubuntu.com/MartinPool/DeveloperApplication [12:43] is mbp here? [12:44] Hrm, seems poolie is not on freenode :( [12:44] 08:15 < poolie> night all [12:44] From #bzr. [12:44] That's 4½ hours ago. [12:44] BlackZ, Are you here yet? You said you might be late. [12:44] persia: I'm here [12:45] [TOPIC] Lorenzo De Liso's application for core-dev [12:45] New Topic: Lorenzo De Liso's application for core-dev [12:45] [LINK] https://wiki.ubuntu.com/LorenzoDeLiso/CoreDeveloperApplication [12:45] LINK received: https://wiki.ubuntu.com/LorenzoDeLiso/CoreDeveloperApplication [12:45] poolie isn't around on internal IRC either [12:46] he's in .au and it's possible neither of our usual times is terribly congenial [12:46] Do we need him here? [12:46] I think it's something like 2am for poolie: he'll probably be happier with the other meeting time,. [12:46] I, for one, don't feel I need to ask him anything. [12:47] I'd be happy to handle poolie's app in absentia personally [12:48] I think everyone should be asked questions. [12:48] you're the chair :) [12:49] i want to ask him questions [12:49] BlackZ, Beyond helping others become developers, what work do you expect to do in the core packageset? [12:50] mixed feedback from BlackZ's comments [12:50] (on the wiki) [12:50] persia: well, I don't have a specific package set where I want to work on, as I said on my application, I work on some Ubuntu server related packages [12:50] cjwatson: please let me comment Artur Rona's comment :) [12:50] BlackZ: of course everyone makes mistakes and I don't think it's necessary for people to be grilled about every single one - but how do you feel you might have avoided the rsyslog breakage from end of last week? [12:51] BlackZ: I was more looking at the several ones from core-devs who said "hm, not bad, would like a bit more experience though" [12:51] BlackZ, Well, you're applying for upload permission to the "core" package set (and coincidentally, all the others). I'd hope you had specific work you had been doing or planned to do there for which you would need such permission. If you're mostly interested in server stuff, there is the server packageset. [12:52] cjwatson: well, I learned from my own mistakes :) as I said you, I did that accidentally and this happens very rarely; most sponsors want me to work on other tasks other than "just" merges, but I work closely with Debian [12:52] persia: yes but I'm interested in mostly of the packages in the main component, too [12:54] BlackZ: The server packageset contains stuff in main, too. [12:54] As do a number of packagesets (most of them, really) [12:54] soren: yeah but I'm talking generally :) [12:54] how is the grub merge going, anyway? ;-) [12:54] cjwatson: I'd say 66 % :) [12:55] cjwatson: I didn't have a lot of time in the last week to look at it, but it's in progress [12:55] ok [12:56] how can i check which package is in the server package set? i sponsored a bunch of merges which are probably not in this set. [12:56] edit_acl.py -P server -S natty query [12:56] hm, or not [12:57] It's ubuntu-server, isn't it? [12:57] edit_acl.py -P ubuntu-server -S natty query [12:57] http://people.canonical.com/~cjwatson/packagesets [12:57] LINK received: http://people.canonical.com/~cjwatson/packagesets [12:58] no [12:58] for example, irssi, and most of the packages which I take care aren't in the server package set [12:58] please don't point people at that [12:58] cjwatson: Apologies. [12:58] s/which I take care/which I take care of [12:58] cjwatson, Is it no longer accurate? [12:58] the list that's actually in Launchpad is always better [12:58] Less accessible, though. [12:58] ~cjwatson/packagesets may contain things that haven't been applied yet [12:58] it's really just a convenience staging URL [12:59] I'll see if I can provide something accessible and generated from Launchpad at some point [12:59] (it's painful because LP doesn't seem to let me query package sets while logged in anonymously) [13:00] BlackZ: as for main packages, many packages are handled by delegated development teams. Many are part of the core as well. I saw you around the time you became contrib-dev and when you became MOTU. What made you feel that you have enough experience to be a core-dev? [13:00] bilalakhtar: well, I touch many core packages and some people advised me to do that (for this reason, too) :) [13:01] obviously I will not work on "just" merges but on other tasks too; however as I said, I'm working closely with Debian (for example to fix bugs to the packages there and get our fixes there to minimalize our delta) [13:02] i checked the sponsored packages. most of them are in the core package set [13:02] need to go, bbl [13:03] BlackZ, When working on packages that affect multiple flavours, what are some of the important concerns? [13:03] * cjwatson looks at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=602406 - shouldn't that have been multiple bugs? [13:04] BlackZ: as for the bug which cjwatson pointed out, patch debian/patches/notification-append seems ubuntu-specific [13:04] it shouldn't have been forwarded to debian [13:04] persia: well, when touching *any* package (that affects multiple flavours or not) I try firstly to get in touch with the last person who touched it and I look for any single change; also, I test the package first to upload it [13:05] cjwatson: right but usually I forward them with one patch that contains all changes [13:05] but you shouldn't :) [13:05] just as Ubuntu bugs should be one bug per logical issue, so should Debian bugs [13:05] patches.ubuntu.com does that for us. Lots of folk find it hard or unpleasant to read. [13:05] cjwatson: ok, then I will do like you said in the future [13:06] I know submittodebian sort of fails to discourage that, but you are meant to edit the patch [13:06] thanks - it'll be easier to get Debian maintainers to look at patches this way [13:06] cjwatson: yes but I forward them manually :P [13:07] BlackZ: splitting the ubuntu changes is important. then the debian maintainer can decide what to pick and what to reject [13:07] bdrung: agreed; that's why in the future I will do that [13:07] more importantly, can make those decisions at different times and keep track [13:07] cjwatson: thank you for pointing that out [13:08] Any outstanding questions? [13:08] bdrung: you mentioned that you encouraged BlackZ to apply for core-dev; what made you feel differently from the other folks on his wiki page? [13:08] cjwatson: i sponsored more than the others. [13:09] cjwatson: a big bunch of sponsor requests came from BlackZ. [13:09] not an unreasonable point [13:10] his requests were all fine, he forwarded the ubuntu changes, the sync requests were all ok [13:12] I think I would classify that as a required condition for core-devs, by no means a sufficient one. [13:14] OK. Moving to voting: [13:14] [VOTE] Lorenzo De Liso to become core-dev [13:15] Please vote on: Lorenzo De Liso to become core-dev. [13:15] Public votes can be registered by saying +1/-1/+0 in the channel, private votes by messaging the channel followed by +1/-1/+0 to MootBot [13:15] E.g. /msg MootBot +1 #ubuntu-meeting [13:15] +1 [13:15] +1 received from bdrung. 1 for, 0 against. 0 have abstained. Count is now 1 [13:15] -1 : I'd like to see a clearer plan and stronger support in endorsements. [13:15] -1 received from persia. 1 for, 1 against. 0 have abstained. Count is now 0 [13:15] -1 at this point, sorry. [13:15] -1 received from soren. 1 for, 2 against. 0 have abstained. Count is now -1 [13:17] +0 - acknowledged bdrung's point but I really have a hard time saying yes with most of the endorsements being kind of lukewarm. I think if you're ready for core-dev you should be able to persuade people to be actively enthusiastic about you. :-) It looks as though you're going in the right direction though ... [13:17] Abstention received from cjwatson. 1 for, 2 against. 1 have abstained. Count is now -1 [13:17] [ENDVOTE] [13:17] Final result is 1 for, 2 against. 1 abstained. Total: -1 [13:17] That's below threshold, even if everyone else votes in favour. [13:18] [TOPIC] Ken VanDine's application for core-dev [13:18] New Topic: Ken VanDine's application for core-dev [13:18] [LINK] https://wiki.ubuntu.com/KenVanDine/DeveloperApplication [13:18] LINK received: https://wiki.ubuntu.com/KenVanDine/DeveloperApplication [13:20] kenvandine, Hey. So, what work have you been doing that requires core-dev? [13:21] kenvandine: can you give some examples of your work outside of ubuntu-desktop? [13:23] kenvandine, Are you here? [13:24] Perhaps a bit early there yet. Moving to the next applicant. [13:24] [TOPIC] AlessioTreglia's application for core-dev [13:24] New Topic: AlessioTreglia's application for core-dev [13:25] [LINK] https://wiki.ubuntu.com/AlessioTreglia/CoreDeveloperApplication [13:25] LINK received: https://wiki.ubuntu.com/AlessioTreglia/CoreDeveloperApplication [13:25] Hi all! here I am [13:26] * ari-tczew is saying all the best for quadrispro [13:27] quadrispro, You mention that we don't collaborate enough with Debian: what steps do you think we should take to increase that? I know you tend to do most of your work in Debian directly: do you think this model makes sense more widely? Why or why not? [13:28] persia, thanks for the question [13:28] we should encourage our contributors to work on the both side [13:28] because [13:28] ok, some minutes to elaborate.. [13:29] I don't know if my approach is the right one, asfaik I take care of quality on both D&U, and yes, it's difficult and it means more work [13:30] sorry [13:30] * kenvandine waves [13:30] depending on how you look at it - making changes as far upstream as possible is often less work in the long run [13:30] kenvandine, We'll get back to you in a bit, if we can. [13:30] quadrispro: do you have plans for main packages where collaboration fails? [13:31] thx [13:31] yes, for instance: simple-scan [13:31] sorry i was late, didn't put this on my calendar... [13:31] I admire robert's work, but he doesn't answer my question, he ignores the work on the Debian side [13:32] and with my next uploads I'll adopt some changes for the patch system [13:32] i.e. divering quilt series file, in order to apply ubuntu-specific patches just from my side [13:33] persia, we should encourage contributors to: 1) know better how debian works: it's not enough to know that it's different, they should know *where* and *how* is different [13:34] (and sorry for my bad english...) [13:34] quadrispro: did you talked with robert about simple-scan? [13:35] bdrung, yes, I tried, not everyday [13:35] I've sent a mail to u-devel-discuss some time ago: got no replies [13:36] quadrispro: and direct e-mailing him? [13:36] yes, done too [13:36] :) [13:37] I've asked him if he would like to help me maintaining the package on Debian too, I told him: "please, merge rather than upload new -0ubuntuX revisions" [13:37] "i'm open to suggestions, criticism, whatever you want: please let me know" [13:37] no replies [13:38] BTW, I'm forwarding bugs,patches for simple-scan [13:38] I don't see a problem in having packages flow the other way, really. [13:38] quadrispro at least deserves a response though [13:38] If upstreams only have time to really focus on one distro and they choose that one distro to be Ubuntu, that's ok. [13:38] I think cooperation is more important than direction, although I think most of us tend to push to Debian when the same source works for both. [13:38] Certainly. [13:39] persia, you got the point [13:39] persia: Certainly. Me too, for upstream stuff I package. For stuff for which I'm upstream... Not so much. [13:39] ...but that's not really the topic of discussion here anyway. [13:40] the question is: how to resolve such cases (main packages are more affected by a lack of collaboration) [13:40] soren, but if the package works fine for Debian and Ubuntu and the delta is not so intrusive, why should we diverge? BTW, I agree, this is not the point [13:40] OK. New question: when working on packages that affect multiple flavours, what are some of the concerns? [13:42] quadrispro: Responded in #ubuntu-motu. We can pick up the discussion there once we're over here. [13:42] well, they should work at all, and much of testing is needed [13:43] soren, thank you, I will :) [13:43] they *do* work [13:44] core packageset contains essential items that need paying particular care, a small mistake might mean large breakage [13:44] sorry for offtopic, just semi-related to this discussion: from my point packages should be clean merged till FeatureFreeze, as Debian-based system. [13:47] Anyone else have questions? [13:47] not I [13:48] [VOTE] Alessio Treglia to become core-dev [13:48] Please vote on: Alessio Treglia to become core-dev. [13:48] Public votes can be registered by saying +1/-1/+0 in the channel, private votes by messaging the channel followed by +1/-1/+0 to MootBot [13:48] E.g. /msg MootBot +1 #ubuntu-meeting [13:48] +1 [13:48] +1 received from cjwatson. 1 for, 0 against. 0 have abstained. Count is now 1 [13:48] +1 [13:48] +1 received from bdrung. 2 for, 0 against. 0 have abstained. Count is now 2 [13:49] +1 : good history, strong endorsements, lovely work [13:49] +1 received from persia. 3 for, 0 against. 0 have abstained. Count is now 3 [13:49] +1 [13:49] +1 received from soren. 4 for, 0 against. 0 have abstained. Count is now 4 [13:49] [ENDVOTE] [13:49] Final result is 4 for, 0 against. 0 abstained. Total: 4 [13:49] Congratulations quadrispro [13:50] congrats quadrispro [13:50] thank you persia, thanks all [13:50] [TOPIC] Ken VanDine's core-dev application [13:50] New Topic: Ken VanDine's core-dev application [13:50] :) [13:50] [link] https://wiki.ubuntu.com/KenVanDine/DeveloperApplication [13:50] LINK received: https://wiki.ubuntu.com/KenVanDine/DeveloperApplication [13:50] i apologize for being late [13:50] kenvandine, The questions asked before were mostly for examples or work outside the desktop set. Could you share some? [13:50] kenvandine: no problem, we had enough in the pipe [13:50] sure [13:51] they are of course things that are used by desktop components [13:51] most recent examples come to mind are x264 and ubuntu-geoip [13:51] x264 bug fix which was breaking video calls in empathy [13:51] and ubuntu-geoip is a new package [13:52] kenvandine: why did you use the "2:0.98.1653+git88b90d9-3ubuntu1" version for the SRU? [13:52] i end up fixing the bugs and doing or reviewing the packaging then i need to steal some valuable time from someone to sponsor [13:52] was that for x264? [13:53] yes, x264 [13:53] that was what dch gave me... to be honest :) [13:54] it was our first change on top of the latest debian one we had [13:54] it seems fine to me to use that version, since natty already has something latere [13:54] but i suspect that should have been 0ubuntu1 [13:54] *later [13:54] yeah [13:54] kenvandine: did you check that this version doesn't exits in natty? [13:54] yes [13:54] natty was already later [13:54] 0.106 something [13:55] i think [13:55] which already had the fix from upstream [13:55] so i didn't need to touch that [13:56] kenvandine: but there could be a 2:0.98.1653+git88b90d9-3ubuntu1 in between. [13:56] i doubt i checked all the versions in between [13:56] just the latest [13:56] the upload would just have been rejected in that case, and no harm done [13:57] true [13:57] ok [13:57] also [13:58] it would be very useful if i could assist other team members with the sponsor queue [13:58] kenvandine, When working on a package used by multiple flavours, what are some of the most important concerns? [13:58] seb128 for example has plenty to do... [13:58] ubuntu-geoip is in universe [13:58] it needs to go to main [13:58] kenvandine, Why? [13:58] new dep for indicator-datetime [13:59] That would put it in the desktop set then, no? [13:59] ultimately, yes [13:59] but getting it to that point meant using seb128's time to get it uploaded, etc [13:59] so a motu could do it... [13:59] Sure. [14:00] kenvandine: have you more examples? [14:00] not specifically off hand... last cycle was much worse when the desktop set didn't have everything it should [14:00] cjwatson probably remembers that well :) [14:01] also the patch pilot program [14:01] then it's an issue with the set [14:01] i am on that rotation, so would be useful if i could sponsor what i review [14:01] kenvandine, How often do you find that you end up needing to work on something before it can be included in the packageset? [14:01] instead of just shoving that off on others [14:01] persia, every cycle... [14:01] it's happened maybe a half-dozen times [14:01] usually at the beginning [14:01] getting less frequent now I think [14:02] it does happen a lot for new packages though [14:02] kenvandine, And similarly, if there was a way to get stuff into the packageset *before* it got added to the image, would that still be as high? [14:02] cjwatson, for the perms it was every week ... i was just having seb128 sponsor [14:02] persia: image, there is; archive, there isn't [14:02] that would help a lot [14:02] persia, but i think i could also be useful helping to reduce the sponsor queue [14:02] cjwatson, Yes, but we don't use that much. [14:02] reviewing patches, etc [14:02] persia: use what? [14:03] cjwatson, Add stuff to packagesets before they are seeded. [14:03] you said "added to the image", that's not quite the same thing. :) [14:03] actually, there's a fairly substantial list of exceptions [14:04] Well, trye, although for the desktop packageset I presume it's fairly close. Anyway, off-topic (but I'd like to learn more later) [14:04] i probably have a direct need to have someone sponsor something for me at least once a week [14:04] grep '^[^#]' exceptions | wc -l [14:04] 64 [14:04] http://paste.ubuntu.com/535206/ [14:04] LINK received: http://paste.ubuntu.com/535206/ [14:04] like this week, i'll need to get an upload of connman sponsored to go along with indicator-network [14:04] (was discussed at UDS) [14:05] kenvandine: what's your relation to debian? [14:05] i would rather help reduce the sponsor queue, instead of making it worse [14:05] personally I'm confident that Ken would make fairly frequent use of these privileges if granted, and that they're proportionate to the work he's doing [14:05] conman is in universe [14:05] bdrung, not much i am afraid, i have done some merge requests [14:05] i should do more [14:06] I'd very much like ken to be able to add new packages to the archive, and work on stuff that is about-to-be-in-the-desktop-set. I'm less convinced for stuff widely outside GNOME Desktopy stuff. [14:06] Do we have any way to do that? [14:06] bdrung, yes, but just an example of something else that is a dep [14:06] persia: Um... "motu"? [14:06] not really. MOTU allows adding new packages to the archive, but stuff that's about to be in desktop often gets sucked into main earlier for one reason or another. [14:07] I see. [14:07] so I'm sure Ken would use MOTU privileges, but I doubt it would be a complete answer [14:07] and with core-dev i could lighten the load a bit for seb128 and didrocks [14:08] kenvandine, Well, how much of that load lightening is problems with the packageset, and how much is stuff that needs to be core? [14:08] not sure exactly [14:08] heh... people says "I'll help reduce sponsors queue" but what about if you won't meet election promises? delete upload access? [14:08] but there are plenty of pieces that the desktop depends on that aren't in the desktop packageset [14:09] examples? [14:09] Well, X, for one :) [14:09] x264 is one... upower i don't think is in the desktop packageset either [14:09] indeed [14:10] and actually during the mesa fiasco with unity [14:10] at the end of the maverick cycle... the X guys wanted me to sponsor the fix [14:10] x264 was one SRU. the package is mainly maintainer by siretart [14:10] because folks had holiday [14:11] bdrung, well that was just a recent example... i don't have every instance memorized :) [14:11] there was a last minute mesa upload that broken unity, during the RC of maverick [14:11] and folks were out on holiday, and with my relation to the DX team everyone was looking to me [14:11] but we had to find a sponsor [14:14] are there further questions here? people seem to disagree on need, but we seem to be going round in circles at this point [14:15] hi geser [14:15] :) [14:15] * geser waves [14:15] kenvandine: re merges. do you forward relevant changes to debian? [14:15] i have [14:15] not sure i have been perfect [14:16] and i have helped sync changes for our packages after they made it in debian [14:17] kenvandine: do you contact the debian maintainer and offer collaboration? the desktop packages seems to differentiate much. [14:17] for example, when the indicator stack made it in debian they sent back their changes to the packaging and i made sure we merged it [14:17] not usually direct contact [14:17] i haven't really had a need to [14:17] the debian maintainer for the indicator stuff was awesome [14:18] he made the effort to send us the changes [14:18] which wasn't much, but we of course prefer to be as close as possible [14:18] in that case it is kind of weird, we are upstream for the packages but debian is ubuntu's upstream [14:20] kenvandine: i saw that the indicator stuff in maintained by the pkg-ayatana group. joining that group could increase collaboration [14:21] sure, i could do that [14:21] would be a good way for me to do more in debian [14:22] kenvandine: joining a debian group is the best entrance point [14:22] i'll do that [14:22] kenvandine: do you have specific plans for the sponsors-queue? [14:23] nothing specific, i'll be doing the patch pilot reviews once a month [14:23] and where ever i can to help reduce seb's load [14:23] kenvandine: i see 12 open bugs for the ubuntu-desktop set. [14:23] that seems low :) [14:24] kenvandine: that's more than the requests for universe and multiverse combined [14:25] how do you see bugs on the package set? [14:25] kenvandine: http://reports.qa.ubuntu.com/reports/sponsoring/ -> origin (and the stats on the bottom) [14:25] kenvandine: that's specifically sponsorship requests, not bugs in general [14:25] oh origin [14:25] kenvandine: how much experience do you have with sponsoring work? [14:26] quite a bit, i review all the DX uploads weekly and upload them [14:27] for all the indicator-* packages, tedg does the packaging work in their ppa and he sends them to me for sponsoring [14:27] and they do weekly releases for all their projects that have had changes that week [14:27] kenvandine: and sponsor requests from outside the DX team? [14:27] ubuntuone and desktopcouch [14:27]