19:06 <rowboatnick> #startmeeting
19:06 <meetingology> 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 <meetingology> 
19:06 <meetingology> 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 <rowboatnick> #chair elfy
19:06 <meetingology> Current chairs: elfy rowboatnick
19:06 <elfy> back - sorry bout that
19:06 <rowboatnick> hehe
19:07 <pleia2> you snooze, you become a chair
19:07 <lderan> its the law of the land
19:07 <elfy> so - shall I kick it off then
19:07 <rowboatnick> So. Anyone have any specifics they want to discuss? I have a smaller list of things
19:07 <rowboatnick> Do that
19:08 <elfy> 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 <elfy> 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 <elfy> we're never going to be able to do advanced testing - so that's going to be manual it seems
19:10 <rowboatnick> How come?
19:10 <elfy> perhaps some install tests - they are being worked on
19:10 <elfy> issues with gtk I think rowboatnick
19:10 <rowboatnick> An automated installer/test would be great :P
19:11 <rowboatnick> Oh
19:11 <lderan> that it would
19:11 <elfy> <balloons> 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 <elfy> <balloons> for you guys, I think the automating installer work is your best bang for the buck at the moment
19:11 <elfy> basically those two quotes sum up what I got from the chat with him :)
19:11 <elfy> BUT
19:11 <lderan> ah okay
19:12 <elfy> 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 <elfy> I know I haven't
19:12 <rowboatnick> I would probably use it for a VM
19:12 <lderan> do we know the percentage of testing done on VMs?
19:13 <rowboatnick> We did have testers fill in their equippment prior
19:13 <rowboatnick> Im not sure where that data has gone, or if its updated
19:13 <elfy> lderan: I don't know - my next thing to dig at is how to drag stats from the reports the tracker produces
19:13 <elfy> rowboatnick: agreed - I could do so with VM's
19:14 <rowboatnick> So automated tests are low priority, in general?
19:14 <elfy> apparently someone is working on these installer tests
19:15 <elfy> rowboatnick: I think that if people 'ubuntu' orientated are looking at those - let them
19:15 <elfy> our time would be better used in doing basic app tests I'd think for the future
19:15 <rowboatnick> We have a lot of unique software tho
19:15 <elfy> ^^
19:16 <rowboatnick> But yes, I do see the point
19:16 <elfy> I'd rather have autotest to do abiword/gnumeric etc
19:16 <elfy> install is install
19:16 <lderan> agreed, basic testing is best way
19:16 <elfy> that's my thinking - I'm looking at trying to have things there for the LTS
19:17 <elfy> don't know what you're thoughts are
19:18 <rowboatnick> 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 <elfy> this is the crux of my problem with it - how many people do we have :)
19:19 <elfy> as far as I know there are you and lderan
19:20 <elfy> at least looking at our things
19:20 <rowboatnick> 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 <elfy> yep
19:22 <elfy> 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 <rowboatnick> Btw, how bad is it, tester wise, are there any non-irc people doing them+
19:23 <elfy> I know of a few
19:23 <elfy> I think we'll have a better idea when alpha1 is out for a week
19:23 <rowboatnick> Yes it sounds like a plan
19:23 <lderan> yeah list idea sounds good
19:23 <elfy> the manual stuff is working well like that - getting picked off one by one
19:24 <elfy> 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 <rowboatnick> okay
19:24 <lderan> okay
19:25 <elfy> so that's the general part sorted for the moment -  plan A
19:26 <elfy> I can co-ordinate this - but the specifics are beyond me - I'm no coder
19:26 <elfy> so if I can look to you both to help that'll be great
19:26 <rowboatnick> sure
19:26 <lderan> aye will do all that i can
19:27 <elfy> thanks :)
19:27 <elfy> so - rowboatnick you had some specifics?
19:28 <rowboatnick> 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 <rowboatnick> (typing with 1 finger, so its a bit slow ;))
19:30 <rowboatnick> So, yes, I dont really have anything to add I suppose
19:31 <elfy> ok - lderan ?
19:31 <lderan> all stuff covered for me
19:32 <elfy> #action elfy create list of apps for autopilot for prioritisation
19:32 * meetingology elfy create list of apps for autopilot for prioritisation
19:32 <elfy> #action elfy set up bugs for required autopilot tests
19:32 * meetingology elfy set up bugs for required autopilot tests
19:33 <elfy> #idea point people mailing -dev list at a/pilot bugs
19:33 <elfy> rowboatnick lderan - anything else needing action or idea ?
19:34 <rowboatnick> not that i can think of
19:34 <lderan> same
19:34 <elfy> k
19:34 <elfy> thanks then :)
19:34 <rowboatnick> thank you :)
19:35 <lderan> thanks :D
19:35 <elfy> not sure I did much other than get confused by the whole thing earlier :)
19:35 <elfy> #endmeeting