[07:40] pleia2: Technically compressed is fine, lossey isn't. [09:24] ochosi, pursue [09:50] knome: ok good, so we need to contact all the authors of those pics i guess [09:50] yup === Gryllida is now known as randomgry [17:59] * rowboatnick appears [19:04] anyone here for the meeting [19:04] ?* [19:04] 2 ticks [19:04] yup [19:05] I dont really know much about the meeting bot [19:05] once you #startmeeting it will tell you lots of commands [19:05] okay [19:06] and you can always add more chairs to help you with #chair elfy [19:06] etc [19:06] okay cool, lets get this going :) [19:06] #startmeeting [19:06] Meeting started Wed Jun 19 19:06:30 2013 UTC. The chair is rowboatnick. Information about MeetBot at http://wiki.ubuntu.com/meetingology. [19:06] Available commands: #accept #accepted #action #agree #agreed #chair #commands #endmeeting #endvote #halp #help #idea #info #link #lurk #meetingname #meetingtopic #nick #progress #rejected #replay #restrictlogs #save #startmeeting #subtopic #topic #unchair #undo #unlurk #vote #voters #votesrequired [19:06] #chair elfy [19:06] Current chairs: elfy rowboatnick [19:06] back - sorry bout that [19:06] hehe [19:07] you snooze, you become a chair [19:07] its the law of the land [19:07] so - shall I kick it off then [19:07] So. Anyone have any specifics they want to discuss? I have a smaller list of things [19:07] Do that [19:08] k - I was chatting to balloons in the qa channel - trying to get a handle on whether it's going to be much use to us before we spend a lot of time [19:09] and we can probably make it easier to do some of the more basic tests - but whether we'll find it's a good use of our time I'm not so sure [19:10] we're never going to be able to do advanced testing - so that's going to be manual it seems [19:10] How come? [19:10] perhaps some install tests - they are being worked on [19:10] issues with gtk I think rowboatnick [19:10] An automated installer/test would be great :P [19:11] Oh [19:11] that it would [19:11] ahh.. well, gtk apps are a little notorious, but we have a branch of working testcases we've done for the ubuntu desktop apps [19:11] for you guys, I think the automating installer work is your best bang for the buck at the moment [19:11] basically those two quotes sum up what I got from the chat with him :) [19:11] BUT [19:11] ah okay [19:12] given how many people we tend to have testing - how many are likely to have machines they can let an automatic test loose on? [19:12] I know I haven't [19:12] I would probably use it for a VM [19:12] do we know the percentage of testing done on VMs? [19:13] We did have testers fill in their equippment prior [19:13] Im not sure where that data has gone, or if its updated [19:13] lderan: I don't know - my next thing to dig at is how to drag stats from the reports the tracker produces [19:13] rowboatnick: agreed - I could do so with VM's [19:14] So automated tests are low priority, in general? [19:14] apparently someone is working on these installer tests [19:15] rowboatnick: I think that if people 'ubuntu' orientated are looking at those - let them [19:15] our time would be better used in doing basic app tests I'd think for the future [19:15] We have a lot of unique software tho [19:15] ^^ [19:16] But yes, I do see the point [19:16] I'd rather have autotest to do abiword/gnumeric etc [19:16] install is install [19:16] agreed, basic testing is best way [19:16] that's my thinking - I'm looking at trying to have things there for the LTS [19:17] don't know what you're thoughts are [19:18] My thoughts were, I suppose, try to get people on writing core function test cases, and like you said before, elaborate them later [19:19] this is the crux of my problem with it - how many people do we have :) [19:19] as far as I know there are you and lderan [19:20] at least looking at our things [19:20] But its kinda low hanging fruit too. One can simply write and suggest a testcase, so those people mailing the list relatively frequently could perhaps be pointed in that direction [19:21] yep [19:22] how about if we try and at least get some sort of list together and get bugs done for them - something to point people towards [19:22] Btw, how bad is it, tester wise, are there any non-irc people doing them+ [19:23] I know of a few [19:23] I think we'll have a better idea when alpha1 is out for a week [19:23] Yes it sounds like a plan [19:23] yeah list idea sounds good [19:23] the manual stuff is working well like that - getting picked off one by one [19:24] ok - so I'll get a list together - we can brainstorm some sort of priority for it then do some bugs and set importance [19:24] okay [19:24] okay [19:25] so that's the general part sorted for the moment - plan A [19:26] I can co-ordinate this - but the specifics are beyond me - I'm no coder [19:26] so if I can look to you both to help that'll be great [19:26] sure [19:26] aye will do all that i can [19:27] thanks :) [19:27] so - rowboatnick you had some specifics? [19:28] Yes, but we basically covered them, i had some points about; which apps are critical to test? contributors, core features and state of the install of autopilot [19:29] (typing with 1 finger, so its a bit slow ;)) [19:30] So, yes, I dont really have anything to add I suppose [19:31] ok - lderan ? [19:31] all stuff covered for me [19:32] #action elfy create list of apps for autopilot for prioritisation [19:32] ACTION: elfy create list of apps for autopilot for prioritisation [19:32] #action elfy set up bugs for required autopilot tests [19:32] ACTION: elfy set up bugs for required autopilot tests [19:33] #idea point people mailing -dev list at a/pilot bugs [19:33] rowboatnick lderan - anything else needing action or idea ? [19:34] not that i can think of [19:34] same [19:34] k [19:34] thanks then :) [19:34] thank you :) [19:35] thanks :D [19:35] not sure I did much other than get confused by the whole thing earlier :) [19:35] #endmeeting [19:35] Meeting ended Wed Jun 19 19:35:32 2013 UTC. [19:35] Minutes (wiki): http://ubottu.com/meetingology/logs/xubuntu-devel/2013/xubuntu-devel.2013-06-19-19.06.moin.txt [19:35] Minutes (html): http://ubottu.com/meetingology/logs/xubuntu-devel/2013/xubuntu-devel.2013-06-19-19.06.html [19:35] d'oh [19:36] what's up? [19:36] should have put noscjak's name against the actions :p [19:36] ah === yofel_ is now known as yofel [21:29] What package are the indicators at the logon screen from? [21:30] there's a graphical glitch in 13.10 [21:30] Noskcaj: screenshot plz [21:31] (if you refer to the session-menu and the language menu, then those aren't ubuntu indicators, but normal menus that are part of the greeter) [21:34] ochosi, http://imgur.com/6GawhHD [21:34] top right corner [21:35] Noskcaj: right, the fix is in Greybird already, could you try it from git? [21:35] how do i do that? [21:35] download here: https://github.com/shimmerproject/Greybird/archive/master.zip [21:36] extract to ~/.themes/ [21:36] (if that dir doesn't exist, just create it) [21:38] done [21:39] then logout again and check whether it's fixed [21:39] it's not. [21:39] i'll try restarting [21:39] nah, wait a sec [21:40] "ls ~/.themes/" looks like what? [21:40] (the folder inside should be called "Greybird", not something else) [21:40] Greybird-master [21:41] right, rename that ;) [21:41] or switch to Greybird-master in the appearance settings [21:41] or actually no, rename it, otherwise you also have to change the lightdm-gtk-greeter config file [21:42] done [21:42] after logging out then back in a crash report has appeared [21:43] and the bug still isn't fixed [21:44] i've tried both [21:45] well anyhoo, the new greeter (1.6) will hopefully land in saucy soon and as soon as greybird from git lands there as well, that glitch will be gone [21:45] so nothing to worry about [21:45] ok [21:45] yay, only 4 bugs this install [21:46] 8 is my record this cycle [21:46] * Noskcaj isn't sure if this is an achievement