=== pi-rho is now known as pi-rho|away === Logan__ is now known as Logan_ [20:15] anyone on the bugsquad here actually read the mailing list stuff? [20:26] TheLordOfTime: when? The last email is in 2012/08/29 in "core vs non-core definition".. what do you mean? [20:33] mapreri: that's the one :p i need an opinion of the wording for that one, and nobody seems to respond except bdmurray (and even then i have to ping him) [20:33] main issue is it modifies the bugsquad documentation on bug importance, so anyone's opinion(s) on bugsquad are valid [20:34] since there seems to be semi-consensus on using a package's "task" field to determine whether its core or not *shrugs* [20:37] the issue still in the permission of the bugsquad: we can't change bug importance, so we don't consider it relevant (at least I think so..) :) [20:37] mapreri: the issue is the docs are in bugsquad [20:38] TheLordOfTime: anyway, in my opinion this is a good way to valutate the importance of a bug... [20:38] mapreri: bugcontrol (or me, micah, a few others here, and bdmurray) could make a unanimous decision, but i sent it to the bugsquad so triagers could comment [20:38] say "THis is an okay idea" or "This idea sucks" [20:38] hence the whole point for the discussion [20:40] so, I think I'll follow your suggestion and I'll write two words in ML, is it ok? [20:40] the mailing list is open to all its subscribers [20:41] right, but, as I wrote, I did't consider the importance of those emails [20:42] ah :P [20:42] :) [20:42] well, since this technically makes a solid(ish) definition of the whole "core vs. non-core" concept, which sometimes decides the difference between low and medium, or medium and high, its important :P [20:42] i think micahg and i discussed the need to actually define it back during UDS on IRC [20:43] UDS-r? [20:43] what was the last UDS, UDS-q? [20:44] i think it was at uds-q [20:44] yep [20:44] i wasnt on bugsquad during uds-p, so... [20:44] yeah, would've had to be uds-q [20:44] :P [20:44] i wasnt *at* uds, but he had a break and was on IRC, and we briefly touched on the fact we need to define it [20:44] ah, I misunderstood you sentence... sorry ;) [20:44] so i took it to the mailing list xD [20:44] ah, no problem :P [20:45] UDS-r will be during this november, so.... :) [20:45] * TheLordOfTime is "too valuable" to take off the time to go to UDS [20:45] (according to my employers) [20:48] :( The UDS is a dream for a far future... also because I can't understand English very well, above all the when it is apoken... so.. :( [20:48] ah [20:48] * TheLordOfTime is a native speaker of American English, and a partial speaker of British English [20:50] * mapreri is Ialian.. [20:50] ah [20:52] I think I haven't a good English. Have you not noticed this?? [20:52] :P [20:52] mapreri: pretty good thus far [20:52] although... [20:53] having said this, you don't have to deal with people who can't speak english to save their life in various IRC channels every day :p [20:53] * TheLordOfTime has adapted to mostly-understand the not-the-best-english-speakers [20:56] :D well, but I will be happy if somebody sometimes tell me I miswrote something... [21:33] :) [21:36] TheLordOfTime: can I ask you waht is trekweb? :) [21:37] trekweb's an internet services provider, but right now we provide IRC bouncers [21:37] http://en.wikipedia.org/wiki/BNC_%28software%29 is a good explanation of that [21:37] https://trekweb.org [21:37] if you're curious to see what TrekWeb provides [21:37] or ask in #trekweb :0 [21:37] :) [21:38] I know what is a BNC :) i'm looking at trekweb.org.. [21:39] mapreri: just one of many ZNC providers [21:39] (we have a LOT of freenode bouncers) [22:19] micahg: when you're not busy, can I ask your opinion on something? [22:20] TheLordOfTime: see you in 2020? :D [22:20] lol [22:20] TheLordOfTime: better to ping and ask then ask when you can ask [22:20] micahg: https://lists.ubuntu.com/archives/ubuntu-bugsquad/2012-August/003870.html <-- opinions on the wording posed for this? [22:20] micahg: better to see if you're busy, saw you chatting away in -motu :P [22:23] TheLordOfTime: there's one problem, those task headers change per release as can the component [22:23] micahg: voice that in the mailing list? [22:23] TheLordOfTime: so, more work for me, eh? :), j/k, will send a followup [22:23] i'd like to see more activity there of course, but since we kind of had a small consensus, perhaps my idea of just plain nixing the "core" or "non-core" definitions should be implemented. [22:23] (i brought that up with bdmurray on IRC a few days ago, so...) [22:24] * micahg also encourages TheLordOfTime to not top post [22:24] micahg: *Shrugs* [22:24] micahg: blame gmail [22:24] actually... [22:24] lame excuse [22:24] blame Evolution [22:25] blaming your mail app for being to lazy to click once in the window to have your cursor at the bootom of the mail ? [22:26] ogra_: actually, blaming the system because it is weird [22:26] * TheLordOfTime is yelling at PHP right now for segfaulting three times in one hour in a test environment [22:26] * ogra_ never managed to top post with either evo, TB or gmail if i didnt want to [22:27] well, then there's the iPhone, where I don't have a choice :/ [22:27] micahg: should bugcontrol's mailing list be CC'd? [22:27] i'm sure the rest of bugcontrol would have something to say [22:27] (if they bother to read it) [22:28] TheLordOfTime: done [22:29] TheLordOfTime: you can if you want [22:29] i might, to see what they say on it [22:30] micahg: i'm going to forward it to them later, the network here's going down for some maintenance. [22:31] but i personally think that the core vs. noncore definition for bugs is slightly obscene [22:31] (one of the options initially was to nix that from the bug importance docs, but we decided not to in the mailing list) [22:34] TheLordOfTime: well, stuff affecting images are definitely a higher priority for the project as a whole as the images are generally only spun once [22:34] indeed. [22:34] then perhaps core should be defined to be part of the seeds for the images [22:34] but if something is worth making RC, then do so [22:34] ... ooops network's going down now