| hobgoblin | morning - if anyone's awake - what should I file a usb not opening thunar against ? | 04:38 |
|---|---|---|
| hobgoblin | nvm - google fu was weak in this one today :p | 04:40 |
| hobgoblin | while I think about it https://wiki.ubuntu.com/Xubuntu/Roadmap/ has got grandr on the list - shouldn't be there as it's not in the repos now | 05:17 |
| astraljava | hobgoblin: You could ping GridCube about it when he's present. | 05:42 |
| hobgoblin | okey doke | 05:42 |
| Unit193 | I'm pretty sure he's aware. | 05:53 |
| hobgoblin | that's alright then - just seems a bit daft to have it on there :) | 05:54 |
| Unit193 | Aye, it's not an option really. | 05:54 |
| ochosi | hobgoblin: yeah, i think it was discussed previously, removed it from the list now | 06:44 |
| ochosi | madnick: ping | 06:54 |
| madnick | ochosi: pong | 07:04 |
| madnick | as for what you said yesterday | 07:04 |
| madnick | I've been reviewing the code | 07:04 |
| madnick | I've just not implemented anything or uploaded a branch | 07:05 |
| hobgoblin | ochosi: thanks :) | 07:06 |
| ochosi | madnick: ok, just wanted to get back to you on that | 07:07 |
| madnick | ochosi: if i wanted to use bazar on this, could i? | 07:08 |
| madnick | Do I have any rights | 07:08 |
| ochosi | i haven't created a team or anything yet, but we can quickly look into that now if you have time | 07:08 |
| madnick | okay awesome | 07:09 |
| madnick | Maybe we could just assign it to Xubuntu artwork? | 07:09 |
| ochosi | are you in that team? | 07:10 |
| madnick | i think so | 07:10 |
| madnick | 1 sec | 07:10 |
| madnick | Hm I seem to have been kicked off that team | 07:10 |
| ochosi | that must've been knome_'s spring cleaning | 07:11 |
| madnick | how about xubuntu team? | 07:11 |
| ochosi | too many people in there | 07:11 |
| madnick | i see | 07:11 |
| ochosi | but actually i'm wondering whether i messed up something, because the /code page says that we host our code @ unity-greeter .) | 07:11 |
| Unit193 | https://code.launchpad.net/~dr.madnick should show all places you can upload. | 07:12 |
| ochosi | guess i should've pulled their code and then pushed it to our repo, will quickly inquire in #launchpad | 07:12 |
| madnick | i see | 07:12 |
| madnick | Im not sure where this belongs, seeing as plymouth stuff was decided to be "artwork", i think this should be aswell, the problem with seperating people who "do artwork" and others, is this hehe | 07:14 |
| ochosi | yeah, i agree | 07:14 |
| ochosi | are there any plans/blueprints for plymouth yet? | 07:14 |
| madnick | https://blueprints.launchpad.net/ubuntu/+spec/other-q-xubuntu-new-plymouth | 07:14 |
| ochosi | "Prepare refreshed drafts for the theme" > can they be found anywhere? | 07:15 |
| madnick | But I have not been hearing anything specific this cycle, about the things that should be implemented | 07:15 |
| ochosi | ok | 07:15 |
| ochosi | i see | 07:15 |
| madnick | ochosi: I'd say its the old one | 07:15 |
| madnick | Refreshing has not been done | 07:16 |
| ochosi | well personally i think the circular progress-indicator would be nice | 07:16 |
| madnick | Yeah | 07:16 |
| ochosi | just any kind of spinner | 07:16 |
| madnick | I think a general review of the code used for feedback should be done | 07:17 |
| madnick | Currently we have a lot of "last minute" code | 07:17 |
| ochosi | you mean feedback like "running fsck"? | 07:17 |
| madnick | yeah | 07:17 |
| ochosi | how many of those feedback scenarios are there? | 07:18 |
| madnick | And the most annoying aspect is the fact that testing plymouth stuff in a VM is almost impossible | 07:18 |
| ochosi | mhm | 07:18 |
| madnick | ochosi: there is fsck, cryptsetup, indicator, press X key | 07:18 |
| madnick | etc | 07:18 |
| === knome_ is now known as knome | ||
| ochosi | could you make a (complete) list? | 07:18 |
| ochosi | then we could discuss each one of them | 07:19 |
| ochosi | ideally create a spec in the wiki and link it to the roadmap | 07:19 |
| madnick | That would not be useful, seeing as we do not implement all of them, we should instead review the possibilities | 07:19 |
| knome | hmm, i can't remember droppint madnick off the art team | 07:19 |
| knome | *dropping | 07:19 |
| madnick | I don't remember being dropped either | 07:19 |
| ochosi | knome: tbh i think xubuntu-dev would be more appropriate for the lightdm engine/theme | 07:19 |
| madnick | No mail | 07:20 |
| knome | ochosi, yeah, but that's problematic | 07:20 |
| ochosi | knome: i can also create a separate lp-team | 07:20 |
| knome | hmh, art is fine for that | 07:21 |
| madnick | ochosi: http://paste.ubuntu.com/1046805/ | 07:21 |
| madnick | these are the possibilties | 07:22 |
| knome | ochosi, if you want to propose a new xubuntu LP team, add that to the meeting agenda | 07:22 |
| madnick | ochosi: but those are just callbacks, the "messages" is what decides actions | 07:22 |
| knome | ochosi, i'm not sure if we need any new, rather drop the old ;) | 07:22 |
| knome | ochosi, we were thinking with pleia2 that maybe -marketing would work well, and we could drop -website then | 07:23 |
| ochosi | madnick: actually there is another greeter we could use/fork | 07:26 |
| ochosi | madnick: that one doesn't even use gnome-settings-daemon | 07:26 |
| madnick | okay? | 07:26 |
| ochosi | it's pantheon-greeter from the elementary project | 07:26 |
| knome | don't confuse him (us) | 07:27 |
| ochosi | ? | 07:27 |
| knome | ;) | 07:27 |
| knome | "there's yet another..." | 07:27 |
| madnick | The thing that is quite awesome with the unity-greeter is it comes complete with code for screenreader and virtual keyboard, aswell as other neat stuff | 07:27 |
| knome | ^ that | 07:28 |
| knome | 's ++ | 07:28 |
| ochosi | madnick: yeah, not sure pantheon-greeter has that | 07:28 |
| madnick | http://bazaar.launchpad.net/~elementary-pantheon/pantheon-greeter/1.x/view/head:/src/indicators.vala | 07:29 |
| madnick | would seem it likes gnome-settings-daemon | 07:29 |
| ochosi | yeah, weird. then maybe it's just bad packaging | 07:30 |
| ochosi | http://www.zimagez.com/zimage/screenshot-06182012-093032am.php | 07:30 |
| ochosi | knome: i think i'm more or less done with the greybird-revamp | 07:30 |
| knome | :) | 07:31 |
| ochosi | i even created a pixmap panel-background for the launcher-panel in case we won't use the compositor | 07:31 |
| ochosi | not sure you'll like it though :p | 07:31 |
| knome | heh | 07:32 |
| ochosi | here it is: http://www.zimagez.com/zimage/screenshot-06182012-093211am.php | 07:32 |
| knome | i got to test that sometime | 07:32 |
| ochosi | haven't pushed the vast changes i did yesterday yet | 07:32 |
| knome | hmmh. | 07:32 |
| ochosi | wondering whether i can retrospectively split them up in smaller commits | 07:32 |
| ochosi | not really sure about that | 07:33 |
| knome | that's not completely bad :) | 07:33 |
| ochosi | :) | 07:33 |
| ochosi | if the panel is on autohide, it looks a bit as if it would slide in underneath the wallpaper | 07:33 |
| ochosi | because of the drop-shadow | 07:33 |
| ochosi | pixmaps have the disadvantage that people have to change/modify them if they make the panel higher than the height of the pixmap (bg-repeat), but it's easy enough to change now in the panel-properties | 07:34 |
| ochosi | madnick: we could also try to convince robert_ancell to drop gnome-settings-daemon | 07:34 |
| ochosi | madnick: hehe, just realized i already tried that before | 07:41 |
| knome | eh | 07:41 |
| ochosi | > Were not going to modify Unity greeter to support different use cases, | 07:41 |
| ochosi | > as we want to be able to quickly adapt it in it's current form. A | 07:41 |
| ochosi | > forked version however shouldn't be too hard to keep in sync if you were | 07:41 |
| ochosi | > willing to maintain it. | 07:41 |
| madnick | hehe | 07:44 |
| madnick | Well, lets just fork it | 07:44 |
| ochosi | yup | 07:45 |
| ochosi | madnick: if you apply to xubuntu-artwork lp-group i can approve you and then you can push to bzr | 07:48 |
| ochosi | (just changed the maintainer of xubuntu-greeter to xubuntu-artwork) | 07:49 |
| knome | ochosi, note that you an add people directly too | 07:51 |
| ochosi | true | 07:52 |
| ochosi | madnick: you've been added | 07:53 |
| madnick | Technically I think I could add myself aswell :P I just need to get some login stuff | 07:53 |
| madnick | ah thanks :) | 07:53 |
| ochosi | np | 07:53 |
| ochosi | madnick: if you could do an initial push now so that we have just the fork there, that'd be great. i just wanna make sure everything works | 07:55 |
| madnick | ochosi: I do not have a suitable dev environment for that, I will need to setup a VM with the new images and get the tools, I will download the required things today | 07:56 |
| ochosi | ah ok, in that case please ping me as soon as you've done that | 07:56 |
| madnick | will do :) | 07:57 |
| ochosi | k, thanks | 07:57 |
| ochosi | :) | 07:57 |
| knome | astraljava, how was the QA meeting? | 10:11 |
| knome | astraljava, i forgot that completely, but turned out i couldn't have made it anyway :) | 10:11 |
| knome | astraljava, i quickly looked at backlog, was there something you needed to check from me? | 10:12 |
| * knome reads the chanlogs | 10:15 | |
| hobgoblin | I thought it went well | 10:15 |
| ochosi | knome: there are meetings @ml | 10:15 |
| knome | ochosi, ? | 10:16 |
| knome | ochosi, "minutes" ? | 10:16 |
| ochosi | meeting minutes? | 10:16 |
| knome | you said "meetings" :D | 10:17 |
| knome | i'm lost. | 10:17 |
| knome | what meetings are on the ml? | 10:17 |
| ochosi | yeah, sry, i meant meeting minutes :) | 10:17 |
| knome | hmm. | 10:17 |
| ochosi | (i'm kinda focussing on something else right now) | 10:18 |
| knome | why did i miss that mail? BLAH | 10:18 |
| knome | wait... | 10:18 |
| knome | i haven't received it? | 10:18 |
| knome | oh, hmm | 10:19 |
| knome | weird | 10:19 |
| knome | that's at my inbox | 10:19 |
| knome | ok, fixed | 10:20 |
| knome | heh, "fix committed" on the bug GridCube pasted :) | 10:25 |
| knome | i suppose the buttons are coming this cycle, at least based on the discussions with stgraber :) | 10:26 |
| astraljava | knome: It's the world's slowest meeting. Takes only a few years to complete. | 10:26 |
| knome | yeah, i notice. :) | 10:26 |
| knome | maybe using meetingology in a more relaxed way is not too bad | 10:26 |
| knome | i mean, just use #startmeeting, #topic and #info, and gathering the meeting minutes is a breeze | 10:27 |
| astraljava | Well, I found I could not create strict topics, nor give out any precise info lines either, so didn't see a real reason for starting it properly either. | 10:28 |
| astraljava | It was more of a conversational meeting. | 10:28 |
| knome | hmm. | 10:30 |
| knome | imo "failed" should be filed only if you weren't able to *finish* the test | 10:30 |
| astraljava | Yes. Why? | 10:31 |
| knome | even if something failed, just link the bugs, then mark as passed | 10:31 |
| astraljava | Hmm... | 10:31 |
| knome | because: | 10:31 |
| knome | if you mark it as "failed", it looks like the xubuntu iso's are not ready for release | 10:31 |
| knome | because that's the stats people are looking at | 10:31 |
| astraljava | Is there a case you're referring to? | 10:31 |
| knome | astraljava, If anything failed, you mark the image as failed. If you didn't stumble upon anything unexpected, you'll mark it as Passed. | 10:32 |
| knome | ^ from the meeting log | 10:32 |
| astraljava | I think we might have a mixed understanding of 'releasable'. | 10:32 |
| astraljava | Are you referring to "installation failed"? | 10:33 |
| astraljava | Releasable to me covers a bit more than just "being able to install". | 10:33 |
| knome | astraljava, only critical bugs should fail the image | 10:39 |
| knome | astraljava, there will be bugs on releases anyway, those shouldn't stop us from releasing non-final milestones | 10:40 |
| knome | astraljava, especially not alphas | 10:40 |
| astraljava | Yeah ok, maybe that needs a little bit refining. I'll remember that for the next meeting, and post corrections. Thanks! | 10:40 |
| knome | astraljava, that's why there are the "bugs" and "critical bugs" sections in the QA tracker | 10:40 |
| knome | astraljava, i've seen some tests with some really minor bugs marked as "failed" | 10:41 |
| hobgoblin | astraljava: so mine should be a pass with a bug - is that right? | 10:41 |
| knome | if those turn up, and the test pass rate is, say 50%, that isn't completely accurate | 10:41 |
| astraljava | hobgoblin: From the recent discussion, yeah I think that's how it is. | 10:41 |
| hobgoblin | k - cool - so long as I know | 10:41 |
| knome | hobgoblin, depends on the bug; if it's something that is seriously interfering from installing, it should be "bug", not "critical", and thus the test should not fail | 10:42 |
| knome | astraljava, example; the terminal help doesn't open; should that be a "fail", just because there is that bug? :) | 10:42 |
| hobgoblin | knome: it was nothing like that | 10:42 |
| astraljava | knome: But we shouldn't be talking about "interfering from installing". That's different from being releasable. | 10:42 |
| knome | astraljava, i think it would be meaningful to ask the QA team too what they think of this | 10:43 |
| knome | astraljava, and what is generally the difference between a bug and a critical bug | 10:43 |
| astraljava | yeah I agree. This is a little too vague now. | 10:43 |
| knome | yup. great :) | 10:43 |
| knome | i'll continue with the log | 10:43 |
| hobgoblin | knome: so if "hobgoblin, ..... it should be "bug", not "critical", and thus the test should not fail" what would be critical? | 10:44 |
| hobgoblin | cos I would expect something that stops you installing to be critical - logically speaking | 10:45 |
| astraljava | hobgoblin: That's what we have to specify. | 10:45 |
| hobgoblin | ok :) | 10:45 |
| astraljava | hobgoblin: Depends. | 10:45 |
| astraljava | If we're talking about "being releasable", you wouldn't ship a product that's installable, but not usable, right? | 10:45 |
| knome | hobgoblin, well at least something that stops you from following the testcase; eg. if you are testing the "encrypted home", but can't encrypt home, the bug that prevents you to encrypt should be critical + fail the image | 10:45 |
| knome | yes, "pass" should mean "the image is installable and usable" | 10:46 |
| knome | but that doesn't mean the image can't have any bugs | 10:46 |
| knome | "fail" should be "the image is either not installable or not usable" | 10:46 |
| hobgoblin | ok - I understand that | 10:46 |
| astraljava | True. If we're thinking about hobgoblin's case, then I don't know if I'd again switch sides. We need to clarify which steps are required to work, and which are just bonus. | 10:47 |
| knome | astraljava, usb doesn't mount autmatically? | 10:47 |
| knome | astraljava, if you can mount manually, it's a pass. if not, it's a fail. | 10:47 |
| astraljava | If the case says to try USB sticks, and you can't browse them, then is it a fail or pass? | 10:47 |
| knome | see prev comment ^ | 10:48 |
| knome | or was it about mounting by default | 10:48 |
| knome | or not being able to access at all generally | 10:48 |
| astraljava | Well what fun is it being able to mount, if you can't browse? | 10:48 |
| hobgoblin | knome: it was in dmesg - not in thunar - in fact none of the other partitions that I would see in thnar normally are there - didn't bother trying to manually mount it | 10:49 |
| knome | i suppose it boils down to "is the stick browseable on other systems" and "what's the filesystem" | 10:49 |
| knome | if it is browseable, and the fs is FAT, i'd say it might be a fail | 10:49 |
| astraljava | knome: Have fun trying to open that up in the testcase. :D | 10:49 |
| knome | if it's not browseable, or the filesystem is NTFS, i'd say that's a pass | 10:49 |
| knome | just use common sense. | 10:49 |
| astraljava | You're talking about plain users here. *smirk* | 10:50 |
| knome | i think there should be a way to mark "failed" tests "passed" by some "product admins" at a later stage | 10:50 |
| knome | and the other way too | 10:50 |
| knome | well that ^ | 10:50 |
| astraljava | knome: No, we don't need that. The results don't have to be used by cold numbers. | 10:50 |
| knome | i understood there's going to be some "product admins" anyway | 10:50 |
| knome | or sth, ask stgraber :) | 10:51 |
| hobgoblin | I've got common sense - a usb that was used to install from should be bwoseable when you reboot after install in my opinion :) | 10:51 |
| astraljava | Okay, well, I wouldn't mind, but it's not a pre-requisite IMHO. | 10:51 |
| knome | the point was that there's going to be more granularity in the permissions | 10:51 |
| hobgoblin | as a plain user :) | 10:51 |
| astraljava | hobgoblin: I wasn't comparing you to a plain user. Sorry if that was confusing. :D | 10:51 |
| knome | astraljava, yes, agreed in "cold numbers" | 10:51 |
| hobgoblin | lol | 10:51 |
| knome | astraljava, but the -release list is getting those pass/fail percentages, so i'd rather get them right | 10:52 |
| astraljava | knome: I'd like that very much. (re: granularity) | 10:52 |
| astraljava | knome: Yeah ok, then it makes sense. | 10:52 |
| knome | astraljava, so to say, those are not just for us | 10:52 |
| astraljava | I have been a little out from the -release for this cycle. I'll try to do better. | 10:53 |
| knome | np :) | 10:53 |
| knome | i've been out too, and while i've been in, there hasn't been anything | 10:53 |
| knome | the things i refer to regarding QA tracker was discussed mostly last cycle with stgraber personally | 10:54 |
| ochosi | knome, pleia2: could one (or both) of you please proof-read my article on x.org? | 10:54 |
| knome | i can do later today | 10:54 |
| * astraljava was scolded for missing the deadlines for the emails, too | 10:55 | |
| knome | astraljava, oh, oops. no, i didn't make changes to the Long document | 10:55 |
| knome | astraljava, but i remember most of it anyway | 10:56 |
| knome | astraljava, what should be left is not the big thing, the big thing is making it readable in addition | 10:56 |
| astraljava | Okay, maybe I recall that incorrectly anyway. But I thought we started going through that, did we not? | 10:56 |
| knome | yeah, we quickly did, but i didn't make any specific notes (except mental) | 10:56 |
| astraljava | I just remember saying I was too tired at one point, and that we ought to switch to NHL '11 at that point. :D | 10:57 |
| knome | yup! | 10:57 |
| astraljava | Right, so if you remember anything at all, could you throw a draft somewhere, and we could go through it with the princess as well? | 10:57 |
| ochosi | knome, pleia2: btw, i consciously decided against including something like a "changelog", i think pictures speak louder than words anyway | 10:57 |
| knome | i can do that later too :) | 10:58 |
| astraljava | Sweet! Thanks. :) | 10:58 |
| knome | ochosi, looks fine, though i'd probably change the last <p> to either remove the "(if you know how)" or quickly paste the command | 11:18 |
| knome | ochosi, also, it's lacking your "the writer is"... | 11:18 |
| ochosi | oh true, i forgot that we still add that manually | 11:19 |
| knome | yup :P | 11:19 |
| ochosi | i was also wondering whether i should try to structure the text more by formatting it | 11:21 |
| ochosi | i mean adding <em> etc | 11:21 |
| knome | if you want to emphasize some thing specifically, then maybe | 11:22 |
| ochosi | or i could add headers | 11:22 |
| knome | that works too | 11:22 |
| ochosi | knome: ok, updated | 11:25 |
| knome | astraljava, sent my notes about the long test to you and pleia2 | 11:32 |
| knome | ochosi, make the "feedback" a separate <p> and <strong> it | 11:33 |
| * astraljava kisses knome on the mouth | 11:35 | |
| knome | umm, eww | 11:36 |
| knome | :D | 11:36 |
| ochosi | knome: ok done. if you approve it, please press publish | 11:38 |
| hobgoblin | astraljava knome - if either of you are here = so is grub install failed - this is a fatal error - critical - not critical - and a fail regardless ? | 11:38 |
| ochosi | bbl | 11:38 |
| astraljava | hobgoblin: That's a sure-fire fail, and very critical indeed. | 11:39 |
| hobgoblin | ok - 'but' I did 'fiddle' with the install - did a entire disc install - but went to the partitioner and changed grub from sda to sdc - would that change your thinking? | 11:40 |
| hobgoblin | in my mind it's a fail still | 11:41 |
| astraljava | Hmm... well if you're sure the system _should_ be able to boot from that, then yes. Have you checked the BIOS boot section? | 11:43 |
| knome | ochosi, btw, it's *Quantal* | 11:43 |
| knome | ochosi, fixed that though. | 11:44 |
| knome | ochosi, and publsihed | 11:44 |
| knome | -typo | 11:44 |
| hobgoblin | oh I know that it would normally be ok astraljava | 11:44 |
| astraljava | Ok, yeah. You should mark the test as failed, and provide the bug report with grub messages attached (on the bug, not on the tracker). | 11:45 |
| hobgoblin | k | 11:45 |
| hobgoblin | where do you get grub messages from - never had an install fail on me before lol | 11:46 |
| astraljava | hobgoblin: So how exactly does it fail, then? I'm sorry, I assumed that it fails to boot after grub was installed on another partition/drive. | 11:48 |
| hobgoblin | hang on - just found the next bit lol | 11:48 |
| astraljava | Ugh... going through an image _bit by bit_ is much more hardcore I could ever imagine myself doing testing. *smirk* | 11:49 |
| hobgoblin | finished without installing grub - apport started mpw | 11:49 |
| hobgoblin | bah - it was my fail | 11:51 |
| hobgoblin | but at least I've seen an install fail now :) | 11:51 |
| astraljava | http://astraljava.kapsi.fi/fail-set-sail-for-fail1.jpg | 11:52 |
| hobgoblin | yep that works for me too :)( | 11:53 |
| astraljava | Love that pic. | 11:53 |
| hobgoblin | so in future - don't tell the installer to install grub to somewhere it is set to do something to - extreme confusion ensues :) | 11:54 |
| astraljava | Yep, even that description confuses the konfutse out of me. | 11:54 |
| hobgoblin | :) | 11:54 |
| hobgoblin | confused me - and I did it ... | 11:54 |
| hobgoblin | so if you've done a bunch of tests - and you have the same bugs - should you put them against each test you did ? | 12:50 |
| === yofel_ is now known as yofel | ||
| madnick | ochosi: got the environment all setup, going to bed now :) | 15:44 |
| madnick | Ill be up in 12h | 15:44 |
| ochosi | madnick: ok, ttyl then | 16:07 |
| ochosi | knome: thanks for correction and publication then | 16:07 |
| knome | ochosi, np | 17:05 |
| ochosi | pleia2: could you share today's post on x.org by me on g+? i mean i can do it via my own profile, but i think the "official" xubuntu channel would be better. if you do so, please change the last paragraph to "feedback is welcome _here_" instead of irc and ml :) | 17:05 |
| ochosi | knome: btw, currently i'm using the lower panel not as launcher, but as "dock", meaning i have my open windows there | 17:06 |
| knome | ochosi, aha | 17:06 |
| ochosi | knome: it's really nice, but otoh makes the top-panel almost useless ;) | 17:06 |
| knome | ochosi, i'm currently using a non-default, not-completely-conservative-layout too | 17:07 |
| pleia2 | ochosi: yep | 17:07 |
| ochosi | reminds me of the days when xubuntu had the gnome2-panel setup | 17:07 |
| ochosi | pleia2: thanks a bunch! | 17:07 |
| ochosi | knome: what's your setup then? | 17:08 |
| knome | sec, upping a shot | 17:08 |
| knome | ochosi, http://temp.knome.fi/other/shot-panel-layout.png | 17:08 |
| knome | ochosi, both are 90% of the monitor width, non-hide | 17:08 |
| knome | ochosi, the top panel only has the window list | 17:08 |
| knome | ochosi, and the top panel expands automatically to 100% if needed (== if many windows open) | 17:09 |
| ochosi | mhm | 17:09 |
| ochosi | actually xfce4.10 panel has quite a few nice feats | 17:09 |
| knome | ochosi, and both the panels have separators at both ends, bringing some visual "breathing space" | 17:09 |
| ochosi | you should really pull latest greybird to tell me about the panel-style :) | 17:09 |
| knome | heh | 17:09 |
| ochosi | mhm, i noticed | 17:09 |
| knome | oh, you noticed the top panel right-hand separator? ;] | 17:10 |
| ochosi | but actually i'm so happy about the new panel style that on second thought maybe don't tell me about it :) | 17:10 |
| ochosi | hehe, yeah of course... :) | 17:10 |
| knome | heh, maybe i should | 17:10 |
| ochosi | anyway, off for dinner | 17:10 |
| ochosi | ttyl | 17:10 |
| knome | ba | 17:10 |
| knome | pleia2, hai | 17:10 |
| knome | pleia2, you prolly got my mail about the long testcase | 17:10 |
| pleia2 | knome: yeah, I'll try to have a look at it tonight | 17:11 |
| knome | pleia2, yup, np; if you have questions though, feel free to ping | 17:11 |
| pleia2 | thanks :) | 17:12 |
| knome | well, i have much more time for these kinds of things now | 17:13 |
| knome | as i put it to my friends; | 17:13 |
| knome | i, as the XPL, decide the direction of the project and about any new features/changes and janne, as the QA lead, makes sure the quality stays | 17:14 |
| knome | ;) | 17:14 |
| knome | (that's not the serious reason) | 17:14 |
| GridCube | knome: o/ | 17:15 |
| knome | hey GridCube | 17:22 |
| GridCube | when can we meet to talk? not today | 17:32 |
| knome | i discussed this with ochosi today, we need to schedule soon | 17:33 |
| GridCube | good :) | 17:34 |
| ochosi | pleia2: one more thing, would you mind to change "GreyBird" to "Greybird"? | 17:39 |
| pleia2 | ochosi: fixed, sorry :) | 17:40 |
| ochosi | pleia2: np, thanks again!:) | 17:40 |
| ochosi | pleia2: btw, i think i completely forgot about the xubuntu/ubuntu-women-stickers | 17:41 |
| pleia2 | ochosi: yep you did! | 17:41 |
| ochosi | pleia2: i wanted to order some from you, if you still have some | 17:41 |
| pleia2 | I think I'll do a personal blog post about giving them away | 17:41 |
| ochosi | sounds good | 17:41 |
| pleia2 | yeah sure, just email me your address: lyz@ubuntu.com | 17:41 |
| ochosi | ok, email me back your account details so i can send you some retribution | 17:41 |
| ochosi | ok, sent | 17:43 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!
