[00:12] djsiegel_: ping a ling [00:12] mrooney: hello [00:13] djsiegel_: do you know if it is possible/desirable to make me some sort of papercut member so I can mark papercut tasks as Triaged and perhaps attempt to assign Importance? [00:13] mrooney: that won't be possible, "not trivially fixable" :) [00:13] but you have a great point [00:14] we need to have a membership approval for ayatana [00:14] ayatana will have usability bugs filed against it [00:14] and we will need to give active ayatana contributors some sort of elevated authority on bugs, at least [00:14] well you could use an existing group like bugcontrol [00:15] I don't know anything about that. [00:15] I think we are ok though. [00:15] oh BugControl is the group in Launchpad that has permissions to set Triaged and Importance in Ubuntu [00:15] The best way you can help right now is marking invalid and triage [00:15] we are going to cut a set of 10 papercuts (actually, we have 10 triaged now) [00:16] and simulate the entire project workflow with them over the next week [00:16] well I can't set as "Triaged" without being a member [00:16] yeah, I know [00:16] I can triage in the non literal sense of course [00:16] one sec [00:16] if you were to make BugControl as a team a member, I think it would logically work out as it is an Ubuntu project [00:17] you could talk to bdmurray in #ubuntu-bugs he is probably wise in all these ways [00:18] we use the team for other privileges [00:18] we can't do that [00:18] but I did ask beuno to come in here and chat with you about your ideas [00:18] he is the launchpad workflow expert and design team member [00:18] speak of the devil [00:18] It'd be nice if there were a way to have stuff that gets nominated to be a papercut and then marked invalid not dump stuff into the inbox of everyone who's subscribed to the bug. [00:19] ScottK: filter it :) [00:19] so [00:19] one way to do the "nomination" workflow [00:19] is using series [00:19] and people propose them for the series [00:19] and we approve/decline [00:20] mrooney: we kind of want everyone to generate a continuous stream of paper cuts, and our team will just pick 100 each cycle [00:20] or it could be first come, first served [00:21] each time we get 100, we say "we have our 100" [00:21] and then swap them out if they fail [00:21] but I don't think our current definition of paper cut is sustainable [00:21] we may need to open it up to included apps more [00:21] but it's appropriate that this first round focuses on the space between apps [00:22] but I have been working way too long, need to get some exercise [00:22] see you, mrooney, beuno, ScottK [00:23] haha, see you later [00:23] beuno: I was just suggesting that it might be useful to the project if some larger, trusted group of people (like BugControl or ubuntu members) could mark paper cut tasks as Triaged and set Importance [00:30] mrooney, that may be a good idea, although it's hard because it opens the door for even more discussions [00:31] beuno: oh, what sorts of discussions? [00:32] mrooney, which ones are or aren't a papercut, and which ones make the cut or not [00:32] since it has a hard limit [00:32] there will be hard decisions to be made [00:33] beuno: that is true, though having people allowed to Triage and potentially set importance doesn't make more tasks, anyone can open the tasks. I am not sure how this would affect those decisions [00:34] which ones are or aren't a papercut can already be changed by anyone via the Invalid and Confirmed status [01:16] mrooney, I will look into it [01:16] it sounds like a good idea === rickspencer3 is now known as rickspencer3-afk [02:21] Would auto selecting the fastest mirror be a good papercut? [08:09] Greetings everybody! [12:04] * MacSlow -> lunch [12:06] The people who often are on #ayatana will have noticed that MacSlow seems to eat everyday :) [12:07] SiDi, surprised? [12:08] it's reassuring that our devs are getting the nutrition they need [12:09] Indeed. [12:09] We should put a "We feed our developers" in the release notes of Karmic [12:11] well really he feeds himself [12:11] we dont want to take that away from him === rickspencer3-afk is now known as rickspencer3 === Nafallo_ is now known as Nafallo === rickspencer3 is now known as rickspencer3-afk === doctormo_ is now known as doctormo === rickspencer3-afk is now known as rickspencer3 === rickspencer3 is now known as rickspencer3-afk === rickspencer3-afk is now known as rickspencer3 === SiDi is now known as IHateGimp [18:52] IHateGimp why oh why? [18:52] poor wilbur === rickspencer3 is now known as rickspencer3-afk [18:59] MacSlow: cause i suffer from its interface [18:59] it would require a billion paper cuts ! Currently trying to figure how to have a gradient with 3 damn colours [19:00] sounds more like you should be working in inkscape... no? [19:01] No, it's not gonna be vectorial [19:01] But i seriously prefer Inkscape :) [19:02] haha [19:02] meh, mrooney === IHateGimp is now known as SiDi [19:06] so far noone could tell me about the 3 colours gradient... [19:13] it's not possible [19:14] gimp just supports 2 color gradient [19:14] (plus the predefined ones) [19:16] artir: you must be kidding :| [19:16] as far as i know, you can't [19:17] maybe with a plugin [19:17] http://community.livejournal.com/gradiental/5791.html [19:17] here it's the tutorial [19:17] but u are better with inkscape [19:17] oh crap [19:17] im so gonna buy a new photoshop license [19:18] XD [20:22] rickspencer3-afk: you around? [20:54] djsiegel: just got back to my desk [20:55] 'sup? === rickspencer3-afk is now known as rickspencer3 [20:55] hey rickspencer3