Attachment '20101021_log.txt'

Download

   1 Oct 21 15:42:34 <Pendulum_>	hey, is there any way to register concerns about some of the plans for various accessibility programs in Gnome 3.0?
   2 Oct 21 15:47:06 <mgorse>	Pendulum_: I'd suggest writing to gnome-accessibility-list or gnome-accessibility-devel, unless it's something that should be filed as a bug
   3 Oct 21 15:47:21 <mgorse>	Oh, right--we have a meeting in a little over an hour, too
   4 Oct 21 15:48:10 <Pendulum_>	yeah, I can't tell whether my concern is a bug or if it's something already being worked on (it's that removing direct imput from dasher may actually mean I can no longer use Linux regularly and especially heavily reduce my ability to contribute)
   5 Oct 21 15:49:50 <Pendulum_>	and something from March says that it'll likely just be compiled without AT-SPI (which would remove that capability), but other people are telling me that they've been told that it's being worked on to port it to dbus
   6 Oct 21 15:49:58 *	Pendulum_ is now known as Pendulum
   7 Oct 21 15:50:45 <mgorse>	Hmm. Not sure; you probably want to talk to Patrick Welch, but it doesn't look like he's in this channel right now
   8 Oct 21 15:51:06 <Pendulum>	yeah. I'll send him an e-mail :)
   9 Oct 21 15:51:55 <mgorse>	I think he was trying to port it to use dbus directly; he was asking me about it in Spain, anyway
  10 Oct 21 15:52:00 <mgorse>	Pendulum: Okay; cool
  11 Oct 21 16:03:04 *	sebsauer has quit (Remote closed the connection)
  12 Oct 21 16:10:46 <API>	Pendulum, although we can talk about it later
  13 Oct 21 16:10:55 <API>	Dasher is already in the "gnome3 issues list"
  14 Oct 21 16:10:57 <API>	http://live.gnome.org/Accessibility/GNOME3#Dasher
  15 Oct 21 16:11:29 <API>	although we need a update about his status here
  16 Oct 21 16:11:31 <API>	AFAIK
  17 Oct 21 16:11:38 <API>	things are still like in the description
  18 Oct 21 16:11:46 <API>	Dasher can be compiled without at-spi support
  19 Oct 21 16:11:47 <Pendulum>	API: that's why I was asking. because what was there concerned me.
  20 Oct 21 16:12:00 <API>	but in this case it would lose some features
  21 Oct 21 16:12:17 <Pendulum>	API: right, but that removes the direct-input capabilities. which for me makes it unusable for most of the things I do on a day-to-day basis (like IRC)
  22 Oct 21 16:12:55 <API>	:(
  23 Oct 21 16:13:08 <API>	ok, if you finally send that mail to Patrick
  24 Oct 21 16:13:13 <API>	Pendulum, and get any update
  25 Oct 21 16:13:17 <Pendulum>	tbh, I don't know anyone who uses dasher without direct input
  26 Oct 21 16:13:18 <Pendulum>	yeah, I will
  27 Oct 21 16:13:21 <API>	could you update that section on the wiki?
  28 Oct 21 16:13:27 <Pendulum>	I'll do my best :)
  29 Oct 21 16:13:29 <API>	well, the description says
  30 Oct 21 16:13:40 <API>	"Without this support, WillieWalker believes Dasher may still function standalone and can be used to type text by cutting/pasting between the Dasher GUI and another text area, which is how many people use Dasher today in GNOME"
  31 Oct 21 16:13:42 <API>	ok, thankis
  32 Oct 21 16:13:44 <API>	thanks
  33 Oct 21 16:13:49 <Pendulum>	I know what the description says, but I have no idea who their "many people" are
  34 Oct 21 16:14:12 <mgorse>	Chances are the description isn't accurate then
  35 Oct 21 16:14:14 <Pendulum>	(because it really isn't any of the people I know who use dasher often/for everything)
  36 Oct 21 16:15:31 <API>	Pendulum, ok, you can ask Patrick about that statement
  37 Oct 21 16:15:36 <API>	if the text is wrong
  38 Oct 21 16:15:39 <API>	please, correct it
  39 Oct 21 16:17:11 *	jsilva (~jsilva@205.211.169.2) has joined #a11y
  40 Oct 21 16:31:56 *	sshaw (~decriptor@137.65.133.12) has joined #a11y
  41 Oct 21 16:35:00 <Pendulum>	API: I've e-mailed Patrick and I'll certainly update things as I get more information :)
  42 Oct 21 16:35:14 <API>	Pendulum, ok, thanks
  43 Oct 21 16:36:46 <Pendulum>	personally I'll be happy with "it won't get done soon, but it's in the 1 year plan to port to dbus" ;-)
  44 Oct 21 16:39:21 *	joanie (~jd@c-98-217-239-60.hsd1.nh.comcast.net) has joined #a11y
  45 Oct 21 16:56:51 *	dexem (~dani@14.Red-88-26-177.staticIP.rima-tde.net) has joined #a11y
  46 Oct 21 16:57:06 <API>	Pendulum, sorry "1 year plan to port to dbus" ?
  47 Oct 21 16:59:07 <Pendulum>	API: that's what needs to happen to keep the functionality I need in dasher
  48 Oct 21 16:59:48 <API>	well, at it is a11y meeting time
  49 Oct 21 16:59:57 <API>	I think that it is worth to start with this ;)
  50 Oct 21 17:00:17 <API>	Pendulum, where did you read this "1 year plan"?
  51 Oct 21 17:00:35 <API>	I mean, what plan? plan deployed by?
  52 Oct 21 17:00:47 <API>	for the laters, we were talking about Dasher, and GNOME 3
  53 Oct 21 17:01:01 *	peppi_el_payaso waves
  54 Oct 21 17:01:25 <joanie>	API if the meeting is officially beginning.... Can we back up a tad: What exactly are we talking about?
  55 Oct 21 17:01:32 *	heidi (~chatzilla@virt61.vnet.wnec.edu) has joined #A11y
  56 Oct 21 17:01:59 <joanie>	(Or is this -- (10:57:07 AM) API: Pendulum, sorry "1 year plan to port to dbus" ?  -- all you know at this point as well?)
  57 Oct 21 17:02:52 <Pendulum>	API: I meant if that's their goal. no official plan :)
  58 Oct 21 17:02:58 <Pendulum>	API: sorry, language thing, I think :)
  59 Oct 21 17:03:12 <Pendulum>	joanie: we were ending that conversation, yes :)
  60 Oct 21 17:03:13 <API>	Pendulum, ah, you already talked with Patrick?
  61 Oct 21 17:03:34 <Pendulum>	API: no. I've sent the e-mail. that's just what I'm hoping for as a response ;-)
  62 Oct 21 17:04:17 <API>	ah ok, you were talking hypothetically ;)
  63 Oct 21 17:04:23 <Pendulum>	yes
  64 Oct 21 17:04:54 <API>	for the people that missed the conversation
  65 Oct 21 17:05:01 <API>	Pendulum was worried about Dasher
  66 Oct 21 17:05:08 <API>	and in fact, he thinks
  67 Oct 21 17:05:09 <API>	sorry
  68 Oct 21 17:05:10 <API>	she
  69 Oct 21 17:05:15 <API>	thinks that this statement
  70 Oct 21 17:05:27 <API>	"Without this support, WillieWalker believes Dasher may still function standalone and can be used to type text by cutting/pasting between the Dasher GUI and another text area, which is how many people use Dasher today in GNOME"
  71 Oct 21 17:05:33 <API>	is somewhat wrong
  72 Oct 21 17:05:58 <API>	as several dasher users requires at-spi features
  73 Oct 21 17:06:09 <API>	she will contact patrik about it
  74 Oct 21 17:06:15 <API>	Pendulum, Im missing something?
  75 Oct 21 17:06:19 <joanie>	aha
  76 Oct 21 17:06:41 <Pendulum>	API: nope :)
  77 Oct 21 17:06:42 <joanie>	Thanks for the recap API. That makes sense (the concern).
  78 Oct 21 17:07:13 <Pendulum>	joanie: for me it's personal so I'm hoping I can help make sure the functionality is around in the future ;-(
  79 Oct 21 17:07:17 <Pendulum>	*;-)
  80 Oct 21 17:07:20 <bnitz>	Hi.  Sorry I'm late.
  81 Oct 21 17:07:25 <API>	well, so we can continue with the GNOME 3.0 update
  82 Oct 21 17:07:29 *	API bnitz np
  83 Oct 21 17:07:43 <API>	first, from the AEGIS meeting about this list
  84 Oct 21 17:08:01 <API>	there are several "need to contact key contacts to update the module state"
  85 Oct 21 17:08:28 <API>	but, if anyone present have done something new in this module, please update the page
  86 Oct 21 17:08:35 <API>	http://live.gnome.org/Accessibility/GNOME3
  87 Oct 21 17:12:11 *	dpellicer has quit (Remote closed the connection)
  88 Oct 21 17:12:15 *	tomeu (~tomeu@148.128.broadband13.iol.cz) has joined #a11y
  89 Oct 21 17:12:30 *	sshaw has quit (Remote closed the connection)
  90 Oct 21 17:13:00 <API>	well, I gave some time so anyone have any question related to any module ;)
  91 Oct 21 17:13:02 <API>	anyone
  92 Oct 21 17:13:03 <API>	?
  93 Oct 21 17:13:19 <API>	question or if anyone wants to update the status of his module
  94 Oct 21 17:13:25 <API>	joanie, aleiva mgorse ?
  95 Oct 21 17:13:44 <joanie>	API: I will go back and look about updating our module statuses
  96 Oct 21 17:14:00 <joanie>	Although I think we did that at AEGIS
  97 Oct 21 17:14:10 *	sshaw (~decriptor@137.65.133.12) has joined #a11y
  98 Oct 21 17:14:43 <API>	two weeks since AEGIS ;)
  99 Oct 21 17:15:14 *	peppi_el_payaso just updated my section
 100 Oct 21 17:15:30 <joanie>	Ah, yes, but I have only just now returned. And our little team has been working on Profiles and other CFR related things
 101 Oct 21 17:15:38 *	joanie wonders who peppi_el_payaso is
 102 Oct 21 17:15:51 <peppi_el_payaso>	rough translation:  "joey the clown".
 103 Oct 21 17:15:52 <joanie>	ah
 104 Oct 21 17:16:05 <joanie>	(I just looked at the edited line on the wiki)
 105 Oct 21 17:16:56 <API>	ok, so, mgorse any at-spi update?
 106 Oct 21 17:16:58 <mgorse>	I need to update at-spi2. I'll do that in a few minutes.
 107 Oct 21 17:16:58 *	msanchez (~msanchez@155.99.117.91.static.mundo-r.com) has joined #a11y
 108 Oct 21 17:17:05 <API>	mgorse, ok thanks
 109 Oct 21 17:17:11 *	peppi_el_payaso msanchez: nice device.
 110 Oct 21 17:17:20 <msanchez>	peppi_el_payaso?
 111 Oct 21 17:17:31 <API>	peppi_el_payaso, something new?
 112 Oct 21 17:17:40 *	msanchez wonders how was peppi_el_payaso's pizza: estrellada
 113 Oct 21 17:17:50 *	peppi_el_payaso delicious.
 114 Oct 21 17:18:15 <peppi_el_payaso>	API:  see above -- just added note about "Common Mag Framework" wiki page that I created last week.
 115 Oct 21 17:18:40 <peppi_el_payaso>	http://live.gnome.org/Accessibility/GNOME3#GNOME_Shell_Magnification
 116 Oct 21 17:19:14 *	API checking
 117 Oct 21 17:19:33 <API>	hmm
 118 Oct 21 17:19:36 <API>	the link is broken...
 119 Oct 21 17:19:49 *	peppi_el_payaso fixing...
 120 Oct 21 17:19:51 <API>	I mean, this http://live.gnome.org/Accessibility/GNOME3/Accessibility/MagnificationFramework/
 121 Oct 21 17:20:14 <peppi_el_payaso>	in the meantime, here is the actual link: http://live.gnome.org/Accessibility/MagnificationFramework
 122 Oct 21 17:20:53 <API>	ok
 123 Oct 21 17:21:04 <API>	btw, just a quick note here
 124 Oct 21 17:21:25 <API>	peppi_el_payaso, you followed the last events of this "integrate orca inside gnome-shell thing"?
 125 Oct 21 17:21:51 <joanie>	API is there new stuff? :-/
 126 Oct 21 17:21:53 <peppi_el_payaso>	API:  I heard about it at the hackfest, but not the details.
 127 Oct 21 17:21:59 <joanie>	Or just that we're going to meet?
 128 Oct 21 17:22:00 <API>	joanie, you know all
 129 Oct 21 17:22:08 <joanie>	peppi_el_payaso: I'll send you the latest
 130 Oct 21 17:22:21 <API>	peppi_el_payaso, in summary that they still want orca
 131 Oct 21 17:22:35 <API>	but being transparent to the user as a feature
 132 Oct 21 17:22:44 <API>	and ui preferences and so on managed on gshell
 133 Oct 21 17:22:52 *	peppi_el_payaso thanks joanie
 134 Oct 21 17:22:58 <API>	probably this would affect your common thing
 135 Oct 21 17:23:17 <peppi_el_payaso>	API, but in summary, they want orca "built-into" gnome-shell?  Or just the preferences bit.
 136 Oct 21 17:23:18 <API>	ok, and about gnome shell
 137 Oct 21 17:23:19 <peppi_el_payaso>	?
 138 Oct 21 17:23:26 <API>	no
 139 Oct 21 17:23:34 <API>	they don't want orca code moved to gnome shell
 140 Oct 21 17:23:45 <API>	at least not the screen reader part
 141 Oct 21 17:23:49 <peppi_el_payaso>	that's good.
 142 Oct 21 17:23:55 <API>	but "better integration" and this includes the ui
 143 Oct 21 17:24:07 <API>	anyway, lets move, as joanie will sent you the details
 144 Oct 21 17:24:21 <peppi_el_payaso>	API:  okay, thanks.
 145 Oct 21 17:24:23 <API>	and probably she will talk with Jon mccan on boston
 146 Oct 21 17:24:29 <API>	my update about gnome-shell 
 147 Oct 21 17:24:43 <API>	is that dan winship uploaded new patches for the keyboard navigation
 148 Oct 21 17:24:49 <API>	and owen taylor is reviewing it
 149 Oct 21 17:24:55 <API>	I have started to check them again
 150 Oct 21 17:25:02 <API>	as there was a lot of changes
 151 Oct 21 17:25:05 <API>	<end_update>
 152 Oct 21 17:25:17 <API>	ok, any other issue about gnome3 modules?
 153 Oct 21 17:27:29 <API>	well, nobody saying anything, so I will move
 154 Oct 21 17:27:41 <API>	checking the agenda we have some reminders
 155 Oct 21 17:28:10 <API>	ie: heidi is waiting caribou feedback
 156 Oct 21 17:28:19 <heidi>	:-)
 157 Oct 21 17:28:40 <API>	one of the "easy questions" would be why GOK was deprecated
 158 Oct 21 17:28:51 <API>	it was explained on the gnome 3 list, but we removed it ;)
 159 Oct 21 17:28:58 <API>	I will recover it 
 160 Oct 21 17:29:16 <heidi>	Ah, yes, that would be helpful.
 161 Oct 21 17:29:25 <heidi>	We are also compiling more questions as we are heading into design.
 162 Oct 21 17:29:52 <API>	heidi, btw
 163 Oct 21 17:29:53 <heidi>	Perhaps the most helpful thing right now would be to have some direction as to the top needs for keyboards. 
 164 Oct 21 17:29:56 <joanie>	API as mentioned at AEGIS, I think there is a place for the issues like GOK deprecation, but let's start a new place for it
 165 Oct 21 17:30:15 <API>	joanie, ok, it is a good idea,
 166 Oct 21 17:30:27 <API>	better than just remove items for the list forever
 167 Oct 21 17:30:37 <joanie>	I think we should be able to show the outside world (rest of GNOME community) where we are at any given time w.r.t. GNOME 3. And that page is ideal for that
 168 Oct 21 17:30:53 <joanie>	but it should remain streamlined and only contain things we need the world to know
 169 Oct 21 17:30:55 <joanie>	imho
 170 Oct 21 17:31:03 <API>	heidi, about the tops needs for keyboards, I guess that this is more a question for experienced users
 171 Oct 21 17:31:29 <heidi>	So the list? Do we have an idea of how many users we have?
 172 Oct 21 17:31:36 <API>	not sure if the gnome-accessibility list is the best place
 173 Oct 21 17:31:44 <API>	I don't, joanie ?
 174 Oct 21 17:31:49 <heidi>	Any direction would be most appreciated. 
 175 Oct 21 17:32:24 <joanie>	heidi: API: As we look to writing our roadmap, I think we should add a study of some sort (and perhaps a survey initially) to figure these sorts of issues out
 176 Oct 21 17:32:37 <heidi>	Ah, thanks this would be helpful. 
 177 Oct 21 17:32:45 <joanie>	merely talking about it amongst ourselves, when we're not part of that community, is proving unsuccessful
 178 Oct 21 17:32:58 <heidi>	:-) 
 179 Oct 21 17:33:02 <joanie>	blindness is easier because we have a huge, active Orca community and it's my DayJob field
 180 Oct 21 17:33:22 <joanie>	failing our having that for users who need an OSK.... We need to do some more, proper, official legwork
 181 Oct 21 17:34:06 <heidi>	Yes, I'd be happy to help with that, but I don't know where to start. 
 182 Oct 21 17:34:27 <Pendulum>	I'm happy to help with legwork on that since I do use an onscreen keyboard-type thing for at least 1/2 the time :)
 183 Oct 21 17:34:37 <joanie>	heidi: We'll get it on our official to-do list as a roadmap item. And as we start planning, we'll definitely include you :-)
 184 Oct 21 17:34:47 <joanie>	Pendulum: Awesome thanks!
 185 Oct 21 17:34:47 <heidi>	Thanks. 
 186 Oct 21 17:35:16 <heidi>	Yes! Thanks Pendulum.
 187 Oct 21 17:36:17 <API>	heidi, btw, just the last shoot about caribou
 188 Oct 21 17:36:28 <API>	and related with the gnome shell integration
 189 Oct 21 17:36:41 <API>	gnome shell developers have in mid this:
 190 Oct 21 17:36:44 <API>	http://live.gnome.org/GnomeShell/Design/Whiteboards/ScreenKeyboard
 191 Oct 21 17:36:55 <API>	but trying to use current solutions as base
 192 Oct 21 17:37:21 *	peppi_el_payaso !
 193 Oct 21 17:37:22 <API>	perhaps another thing to investigate if how feasible could be get the common parts from caribou
 194 Oct 21 17:37:31 <API>	in order to be used on both
 195 Oct 21 17:37:40 <API>	just a quick thought anyway
 196 Oct 21 17:37:59 <heidi>	API, Thanks! This is really helpful. 
 197 Oct 21 17:38:23 *	danigm_out is now known as danigm
 198 Oct 21 17:38:26 <heidi>	And students were just starting to look at how Caribou integrates with GNOME so this is good. 
 199 Oct 21 17:38:36 <API>	heidi, anyway, doesn't spent too much time
 200 Oct 21 17:38:46 <API>	I mean, don't see that as the "main issue to solve"
 201 Oct 21 17:39:34 <API>	soooo ... lets move on 
 202 Oct 21 17:39:36 <joanie>	Heidi. In the shortterm... I don't know if it would be worth it but
 203 Oct 21 17:39:37 <joanie>	http://ma.easterseals.com/site/PageServer?pagename=MADR_DLRC
 204 Oct 21 17:39:42 <API>	the other reminder is
 205 Oct 21 17:39:44 <API>	http://live.gnome.org/Accessibility/QuarterlyReports/2010/Q3
 206 Oct 21 17:39:48 <API>	ups, overlapping
 207 Oct 21 17:39:52 <joanie>	my bad
 208 Oct 21 17:39:54 <joanie>	sorry API
 209 Oct 21 17:40:13 <heidi>	Thanks joanie!
 210 Oct 21 17:40:17 <API>	joanie,  np
 211 Oct 21 17:40:33 <API>	the last reminder is "if you have done something in Q3" please update this wiki
 212 Oct 21 17:40:37 <API>	http://live.gnome.org/Accessibility/QuarterlyReports/2010/Q3
 213 Oct 21 17:40:48 <API>	so Bryen can create the summary for the global quarterly report
 214 Oct 21 17:41:47 *	API checking agenda
 215 Oct 21 17:41:54 <API>	Thoughts on "Do we need more hackfests?" 
 216 Oct 21 17:42:08 <API>	in my opinion we should start this discussion on the mailing list
 217 Oct 21 17:42:41 <API>	but, if anyone wants to provide any comment about it...
 218 Oct 21 17:42:45 <joanie>	API: Are you going to do that then? :-)
 219 Oct 21 17:43:03 <joanie>	My comment in the meantime is that a hackfest for hackfest's sake is silly
 220 Oct 21 17:43:13 <joanie>	that they should be targetted for specific needs
 221 Oct 21 17:43:23 <joanie>	And that we need to figure out a way to better control things
 222 Oct 21 17:43:23 <heidi>	BTW, I have some 8 or so students coming to Boston in November
 223 Oct 21 17:43:27 *	peppi_el_payaso seconds joanie
 224 Oct 21 17:43:44 <joanie>	I'm interested in doing a post mortem on AEGIS
 225 Oct 21 17:44:37 <API>	?¿
 226 Oct 21 17:44:44 <API>	joanie, a post mortem on AEGIS?
 227 Oct 21 17:45:09 <joanie>	API yeah :-)
 228 Oct 21 17:45:19 <joanie>	i.e. there were a number of things that "didn't go as expected"
 229 Oct 21 17:45:20 <bnitz>	Has anyone seen a particularly good example of how hackfests should work?  Maybe we can structure the next around that.
 230 Oct 21 17:45:28 <joanie>	some were beyond our control
 231 Oct 21 17:45:36 <peppi_el_payaso>	joanie:  a post mortem on, specifcially, the aegis hackfest?
 232 Oct 21 17:45:38 <joanie>	but we didn't have a plan for handling such occurrences
 233 Oct 21 17:45:46 <joanie>	other things might have been within our control
 234 Oct 21 17:46:03 <joanie>	but the question of how to control them without hurting feelings and being overbearing remains to be answered
 235 Oct 21 17:46:24 <joanie>	I think this might be worth creating an ad hoc subcommittee for :-)
 236 Oct 21 17:46:29 <joanie>	peppi_el_payaso: yup
 237 Oct 21 17:47:14 <peppi_el_payaso>	an (obvious) suggestion:  make sure the internet works the week before the hackfest begins
 238 Oct 21 17:47:26 <API>	joanie, well, joanie, things like, "wifi is not working" are beyond our possibilities ;)
 239 Oct 21 17:47:53 <bnitz>	has anyone been to a conference where Nhackers > 255 and wifi does work?
 240 Oct 21 17:47:54 <joanie>	API yup, that was the first category 
 241 Oct 21 17:48:10 *	API peppi_el_payaso can read my mind
 242 Oct 21 17:48:29 <API>	bnitz, but in our case we were about 15 hackers ...
 243 Oct 21 17:48:31 <msanchez>	bnitz: not me, wifi problems in FOSDEM and GUADEC are a familiar issue afaik :-)
 244 Oct 21 17:48:47 <bnitz>	API, yeah 15 should've been OK.
 245 Oct 21 17:48:53 <peppi_el_payaso>	API:  i don't know about that.  someone could be given the task of laising (sp?) with the tech person responsible for network  prior to the meeting
 246 Oct 21 17:49:06 <API>	ok, but this is not the point
 247 Oct 21 17:49:12 <API>	so lets add as conclusion
 248 Oct 21 17:49:23 <API>	"do a AEGIS post mortem"
 249 Oct 21 17:49:31 <API>	as usual the question is
 250 Oct 21 17:49:35 <API>	"who will do that?"
 251 Oct 21 17:49:43 <joanie>	API I'll take the lead
 252 Oct 21 17:50:03 <joanie>	and I'll get in touch with you to follow up/move forward
 253 Oct 21 17:50:23 <API>	ok
 254 Oct 21 17:51:04 <API>	well, we are are out of "official items on the agenda"
 255 Oct 21 17:51:09 <API>	so lets enter in "misc"
 256 Oct 21 17:51:15 <API>	today we received a mail about
 257 Oct 21 17:51:24 <API>	" Google Code-In for GNOME: We Need Tasks!"
 258 Oct 21 17:51:37 <API>	it seems to be a google summer of code spin off
 259 Oct 21 17:51:39 <API>	smaller
 260 Oct 21 17:51:46 <API>	for high school students
 261 Oct 21 17:52:09 <API>	but I guess, that this is more a Bryen task
 262 Oct 21 17:52:12 <API>	not sure
 263 Oct 21 17:52:21 <API>	it seems similar to outreach and so on
 264 Oct 21 17:52:52 <joanie>	API yeah, I think you're right
 265 Oct 21 17:52:53 <API>	opinions? thoughts?
 266 Oct 21 17:53:07 <joanie>	I'm sure Bryen would want to handle that as outreach
 267 Oct 21 17:53:08 *	peppi_el_payaso reading that email...
 268 Oct 21 17:54:33 <API>	ok
 269 Oct 21 17:54:49 <API>	so, we are in misc time, so feel free to add something to the meeting ;)
 270 Oct 21 17:55:41 <Pendulum>	for those who don't know next week is the Ubuntu Developer Summit and there will be several sessions related to accessibility
 271 Oct 21 17:55:53 <peppi_el_payaso>	where is it?
 272 Oct 21 17:56:06 <Pendulum>	peppi_el_payaso: the summit is in Orlando, however you can also remote participate 
 273 Oct 21 17:56:23 <peppi_el_payaso>	is there an url (for more info)?
 274 Oct 21 17:56:43 <Pendulum>	http://uds.ubuntu.com/participate/remote/ has remote participation information 
 275 Oct 21 17:56:49 <peppi_el_payaso>	thanks.
 276 Oct 21 17:56:54 <Pendulum>	it's a combination of audio streaming & IRC
 277 Oct 21 17:57:15 <Pendulum>	schedule of what's happening is at http://summit.ubuntu.com/uds-n/
 278 Oct 21 17:57:34 <Pendulum>	we've got one general accessibility session, one about accessibility in unity, and one talking about on screen keyboards
 279 Oct 21 17:57:38 <Pendulum>	(so far)
 280 Oct 21 17:58:01 <Pendulum>	If people are interested I can e-mail all this (along with the current times/rooms for the accessibility-related sessions) to the list?
 281 Oct 21 17:58:32 <bnitz>	I'm still looking for suggestions on test reporting.  Would it make sense to log severity as well as what kind of AT a failure impacts (e.g. visual, keyboard navigation...)
 282 Oct 21 17:59:14 <API>	bnitz, on ubuntu summit?
 283 Oct 21 17:59:31 <bnitz>	No sorry, under misc.
 284 Oct 21 18:00:05 <bnitz>	Also under misc, if anyone would like to nominate bugs which indicate a kind of common a11y breakage which we'd like to avoid, point me to them.  Thanks.
 285 Oct 21 18:00:10 <API>	bnitz, ok sorry, I were reading Pendulum comments and suddenly read your comment :P
 286 Oct 21 18:01:42 <API>	bnitz, anyway, about your "testing feedback" I remember that you suggested that on the hackfest
 287 Oct 21 18:01:44 <API>	but ...
 288 Oct 21 18:01:49 <API>	have you sent any mail?
 289 Oct 21 18:01:56 <API>	or provide a wiki page or something?
 290 Oct 21 18:02:08 <API>	remember that only part of the community were there
 291 Oct 21 18:02:20 <bnitz>	API:No, put that on my action list.
 292 Oct 21 18:02:22 <API>	and probable people like Ara or nagappan could collaborate
 293 Oct 21 18:02:42 <bnitz>	API:Yes I've been working with them as well as Eitan.
 294 Oct 21 18:03:46 <bnitz>	btw thanks to Eitan and eveyone else who walked me through my first drop of an accerciser tarball, the four horsemen of the apocalypse haven't yet arrived.
 295 Oct 21 18:04:03 <eeejay>	bnitz, i didn't see an announce, it's out?
 296 Oct 21 18:04:07 <bnitz>	API:Is there a community wiki I should use?
 297 Oct 21 18:04:39 <API>	bnitz, the announcement of releases are done just by sending a mail
 298 Oct 21 18:04:44 <API>	to the proper lists
 299 Oct 21 18:04:53 <API>	but if you are talking about the testing thing
 300 Oct 21 18:05:00 <API>	create one on live.gnome.org
 301 Oct 21 18:05:14 <API>	not sure if it fits under accessibility umbrella
 302 Oct 21 18:05:22 <bnitz>	eeejay:I sent the announcement and someone else forwarded it to me so it did go out.
 303 Oct 21 18:05:29 *	danigm is now known as danigm_out
 304 Oct 21 18:05:36 <bnitz>	API yes, maybe it belongs under testing.
 305 Oct 21 18:06:20 <API>	bnitz, right now there are this one:
 306 Oct 21 18:06:22 <API>	http://live.gnome.org/DesktopTesting
 307 Oct 21 18:06:54 <API>	although this is for Mago
 308 Oct 21 18:07:16 <API>	but taking intou account their purpose
 309 Oct 21 18:07:19 <bnitz>	I'm definitely planning on using the mago framework so I'll see if it can go somewhere there thanks.
 310 Oct 21 18:07:22 <API>	"The Desktop Testing team aims to automate desktop testing through the AT-SPI layer."
 311 Oct 21 18:07:29 <API>	it is somewhat overlapping your objetives
 312 Oct 21 18:07:38 <API>	you should talk with Ara about it
 313 Oct 21 18:07:53 <bnitz>	API:I will.
 314 Oct 21 18:08:26 <API>	bnitz, ok, thanks
 315 Oct 21 18:09:22 <API>	ok, 10 minutes (almost) over time
 316 Oct 21 18:09:27 <API>	lets close the meeting
 317 Oct 21 18:09:30 <API>	meeting over

Attached Files

To refer to attachments on a page, use attachment:filename, as shown below in the list of files. Do NOT use the URL of the [get] link, since this is subject to change and can break easily.
  • [get | view] (2021-02-25 09:41:52, 23.0 KB) [[attachment:20101021_log.txt]]
 All files | Selected Files: delete move to page copy to page

You are not allowed to attach a file to this page.