[14:12] so did all of the documentation/outreach stuff just kinda get dropped from UDS? [14:13] (sorry, vaguely online now, but not really here, just looking at the session notes from Tuesday finally) [14:13] we did talk about outreach a bit... [14:13] (also, glad you traveled safely :) ) [14:14] okay, just no notes on the etherpad... [14:14] hi Pendulum [14:14] * Cheri703 was taking notes, did a crappy job, sorry [14:14] Pendulum: there is audio too [14:14] or very little [14:14] http://mirrors.tumbleweed.org.za/uds-o/ [14:14] AlanBell: bad auditory processing so listening without the discussion won't help me :-/ [14:15] Cheri703: no worries! [14:15] Pendulum: there weren't necessarily specifics about it, just "we should probably do more outreach" I think [14:15] I guess the documentation/outreach stuff that was on the etherpad from our last meeting just never made it onto the UDS etherpad :-/ [14:15] (so didn't get discussed) [14:16] well, I think some of the testing classes charlie-tca and I were talking about would be outreach at least to a degree [14:16] yes [14:16] true [14:16] I was mostly thinking personas and that side of stuff [14:16] yeah, we didn't talk much about that [14:17] and the fact that we need to look at what documentation needs updating/overhauling/to be created [14:18] we did talk about creating a document that would explain exactly what accessibility things exist and how they fit together (I think that was in the meeting you're talking about) [14:26] but there has been done a lot of outreach onto various sessions regarding a11y and docu [14:26] cool :) [14:26] where appropiate I dropped achecker.ca [14:27] so they themselves can test for it [14:27] which is better then no attention to it at all [15:12] feedback appreciated: https://live.gnome.org/Hackfests/ATK2011/Agenda/EnablingAccessibilityProposal [15:13] maco: ^ [15:15] fregl: i don't know anything about dbus, but in #kde-accessibility someone wondered whether the reason QT_ACCESSIBILITY had to be set first is that the widgets have to be created post-ATK-startup.. not the case? [15:15] right, I can also post in kde-accessibility ... too many channels :p [15:15] widgets created post atk startup? [15:15] I don't understand [15:16] jpwhiting: dbus signal would work, but I wonder if the qt-bridge assumes its loaded at the start of execution [15:16] ah, as in it only creates accessible objects for widgets as they are created? maybe [15:16] but maybe not, it seems to work right on windows where a signal turns on accessibility (I think from fregl's email) [15:16] jpwhiting: yeah, its cetainly a possibility, I just mean that it might take some work on the bridge to make it work [15:16] well, if I am going to implement this inside Qt, then it's going to work (I hope at least :p) [15:16] no, I can create everything at any time, it just needs a bit of work. but that is required no matter what [15:17] cool