=== mhall119_ is now known as mhall119
[18:14] <jay_> Hello. I'm interested in somehow getting involved with the accessibility team. I'm not sure exactly how I could help out - perhaps with application testing - but I'd like to do what I can.
[18:17] <jay_> Would anyone be able to point me in the right direction to get plugged in and involved?
=== jay_ is now known as Arcitens
[18:22] <AlanBell> hi Arcitens 
[18:23] <Arcitens> hi
[18:23] <Arcitens> how are you doing?
[18:25] <AlanBell> not too bad, you wanted to get involved in accessibility
[18:25] <AlanBell> which is great
[18:25] <AlanBell> in the topic there are links to the mailing list and the wiki area
[18:26] <Arcitens> yes, I've looked at the wiki a little bit, including the testing page
[18:32] <Arcitens> I'm interested in helping with application testing, but I'm not sure how or where to get started. I'm also interested in helping with wherever there needs help.
[19:10] <AlanBell> one thing that is coming up is testing of the new unity interface in Natty
[19:11] <charlie-tca> And we would like help with testing that, including trying to write up what works and filing bugs for what doesn't
[19:13] <Arcitens> Ok. I might be interested in that. I'm also interested in testing applications, since that also goes beyond Ubuntu.
[19:16] <Arcitens> But either way how would I get involved?
[20:10] <Arcitens> Ok. I'm going to head out. I'll be back tomorrow. Looking forward to getting involved.
[20:11] <charlie-tca> AlanBell: Do we need to make a list of things to test? or can we just create a wiki page and let testing happen?
[20:35] <Pendulum> charlie-tca: I think we need a good sense from TheMuso about what he thinks are most likely things to test
[20:36] <Pendulum> and then create a priority list so that we know at least the most important things get tested
[20:37] <charlie-tca> Okay. Right now, we know most things are broken in Natty, but we could have tests run on applications using Maverick. At least that was my thought 
=== JanC_ is now known as JanC