(15:05:07) API: well people, if I didn't get dazed and confused for this UTC thing
(15:05:12) API: its meeting time
(15:05:28) API: for the ones missing the previous one
(15:05:29) bnitz: gk4:Just found it today. I think this is up to date: http://download.freedesktop.org/ldtp/html/window.html
(15:05:31) API: http://live.gnome.org/Accessibility/Minutes/20100902
(15:05:42) API: and the agenda for this one
(15:05:44) API: http://live.gnome.org/Accessibility/Minutes/20100902#Agenda_for_the_next_meeting
(15:06:07) API: so point 1. is AEGIS updated
(15:06:09) API: sorry
(15:06:12) API: AEGIS update
(15:06:30) API: just to comment that the travel committe have started to communicate to the people
(15:06:36) API: about the sponsorship
(15:06:40) korn: API: can we hold off on that for a moment?
(15:06:49) korn: I'll be done with my other meeting very shortly...
(15:06:52) API: ok
(15:07:16) API: lets go to 2.
(15:07:22) ***API checking
(15:07:30) API: First impressions about the "weekly meetings and format" on the mailing list 
(15:07:37) API: well, I have sent a mail to the list
(15:07:50) API: not too much feedback, but it seems
(15:08:09) API: that people still prefers weekly meetings
(15:08:20) API: mainly for the timetable
(15:08:25) API: so lets continue with that
(15:08:31) clown: +1
(15:08:35) joanie: +1
(15:08:41) joanie: (sorry for not responding)
(15:08:41) API: some people also felt that just to know the "flip-flop"
(15:08:46) API: its not enough
(15:08:58) API: to know the date of the current meeting
(15:08:59) heidi: +1
(15:09:12) API: eeejay, for example, proposed google calendar or something similar
(15:09:34) API: other option could be just add that information on the live.gnome.org
(15:09:44) clown: yes, I have it in my own iCal, and that usually suffices.
(15:09:50) joanie: I like the google calendar option though
(15:10:01) ***clown agrees with joanie 
(15:10:04) joanie: we could even c&p agendas into the google calendar
(15:10:11) joanie: then I would have the agenda on my android :-)
(15:10:11) API: and what about just create the template for the rest of the meetings in live.gnome.org?
(15:10:17) API: I mean, in the minutes page
(15:10:29) API: create the page for the rest of the year
(15:10:36) prlw1: Feel free to try out dasher on your android and let us know how it goes ;-)
(15:10:39) joanie: API: we could do that
(15:10:50) API: hmm, although after think a little about it
(15:10:54) joanie: prlw1: (cool)
(15:15:12) API: the problem is sync with your mobile, personal google calendar, and so on
(15:15:20) joanie: what problem?
(15:15:23) gk4: bnitz: is there documentation for ooldtp as well?
(15:15:35) aleiva: you can subscribe to google calendar from everywhere
(15:15:41) API: I mean that if we create that on google calendar
(15:15:48) API: yes just what aleiva have just said
(15:15:49) API: ;)
(15:15:58) joanie: So I don't get why that is a problem?
(15:16:11) aleiva: joanie: it's not a problem :-)
(15:16:16) API: I mean comparing that with my option
(15:16:23) joanie: ohhh
(15:16:28) API: just write it on the live.gnome.org
(15:16:40) joanie: gotcha API sorry. Still on my first pot of coffee
(15:16:47) API: np
(15:16:54) joanie: So we're all saying we like the Google Calendar idea. (right?) :-)
(15:16:56) API: anyway, as Bryen is not here 
(15:16:57) aleiva: API: I like the ics at live.gnome.org for release schedule
(15:13:05) API: is my mission to say: too much detail here ;)
(15:13:07) joanie: aleiva: (I *depend* on it)
(15:13:18) ***joanie shuts up
(15:13:21) clown: +1 to google calendar idea, since I think I sync with that.
(15:13:23) aleiva: joanie: I know, I start to depend, but I want to have a life...
(15:13:25) API: we can move that to the list again
(15:13:38) API: with the options proposed here
(15:13:49) aleiva: API: nice, +1
(15:13:57) API: the other thing commented
(15:14:02) API: by eeejay 
(15:14:07) API: was again the timetable
(15:14:41) API: in the previous meeting we concluded that it isn't worth to find a new one
(15:14:49) API: but it seems that some people find it odd
(15:15:09) joanie: I cannot imagine what other times we could try
(15:15:34) API: ok, lets answer that to eeejay in the ml ;)
(15:16:04) API: the other thing is the agenda items
(15:16:19) API: as I said on the list, I prefer several proposal and discard 
(15:16:25) API: instead of have 0 proposals
(15:16:29) API: opinions?
(15:16:37) joanie: I agree with you
(15:16:38) aleiva: who provide that proposals?
(15:16:40) aleiva: devs?
(15:16:43) joanie: anyone aleiva
(15:17:01) joanie: right now it's pretty much API and me
(15:17:06) aleiva: why people are not proposing now :-D
(15:17:06) joanie: it should be the team
(15:17:18) ***joanie shrugs
(15:17:24) joanie: we ask
(15:17:32) korn: Hi gang - I'm good to go
(15:17:40) aleiva: I like proposal format, but I don't know if it will rock
(15:17:41) korn: Thanks for holding off on the AEGIS stuff
(15:17:41) ***clown waves at korn
(15:17:54) API: aleiva, well, in previous "gently reminder" I wrote "feel free to add sensible topics"
(15:18:04) aleiva: korn: hi Peter
(15:18:13) API: I hope not to scare people with this "sensible" word here 
(15:18:18) API: anyway, as joanie said
(15:18:19) ***joanie chuckles
(15:18:31) API: it should be proposed by anyone from a11y tem
(15:18:35) heidi: I haven't added to the agenda because I didn't know what was acceptable.
(15:18:37) API: team
(15:18:47) joanie: heidi: it is. Please add. :-)
(15:18:54) heidi: It wasn't clear to me if things like asking for input on student projects was OK.
(15:18:55) joanie: it is == whatever is
(15:18:58) heidi: :-) Thanks 
(15:19:00) joanie: heidi: sure
(15:19:02) API: heidi, well, just add something, and then we can decide that
(15:19:06) API: in fact all is interesting
(15:19:14) API: the onely reason to discard things
(15:19:15) API: imho
(15:19:17) heidi: Right, I'll go ahead and be bold and let you filter as needed. :-)
(15:19:18) API: would be time
(15:19:21) joanie: (or postpone them)
(15:19:30) joanie: (rather than discard them)
(15:19:47) yippi: is the problem that the meeting changes time and this confuses people?
(15:19:57) joanie: yippi: apparently
(15:20:07) ***joanie just shows up when her calendar tells her to
(15:20:13) yippi: perhaps it might be better to just stick to a single time for a while and see if that works better
(15:20:14) API: yippi: well, as far as I see, meeting time doesn't change
(15:20:25) API: yippi, we already tried that
(15:20:30) joanie: yippi: but we have people in Beijing
(15:20:34) joanie: and Australia
(15:20:36) joanie: and ....
(15:20:39) API: and the problem is that several people missing most of the meetings
(15:20:44) clown: and around the world
(15:20:55) API: with this approach, several people misses just most half of the meetings
(15:21:10) ***API guesses if "most half of the meetings" exists
(15:21:22) joanie: (we know what you mean API)
(15:21:29) yippi: have you tried using doodle?
(15:21:45) joanie: yippi: I believe Will did a long time back
(15:21:50) API: wel, 20 minutes, a last comment about "2. # First impressions about the "weekly meetings and format" on the mailing list "?
(15:21:51) joanie: and everyone got confused
(15:22:12) yippi: perhaps a doodle survey would help find a good time.
(15:22:21) Pendulum: are doodle surveys accessible?
(15:22:40) Pendulum: we've stayed away from using them on the Ubuntu accessibility team because they didn't look like they'd work well with screen readers
(15:22:43) yippi: i don't know, might be good to find out.
(15:22:58) paul_h: point me to one and I'll tell you
(15:23:34) API: well, about the specific tool (doodle, google calendar, and so on)
(15:23:39) API: we can talk in the mailing list
(15:23:44) joanie: +1
(15:23:44) API: as we said before
(15:23:48) API: so lets move
(15:23:55) API: and take again AEGIS
(15:24:04) API: travel committe is 
(15:24:11) API: notifying people about the decision
(15:24:22) API: some people has fallen down from the hackfest
(15:24:23) clown: paul_h: here is a doodle example: http://www.doodle.com/BSPpsfem34pktd9y
(15:24:30) API: like li yuan and slee 
(15:24:38) API: when we get a final list of people going
(15:24:45) API: we could make the booking
(15:24:54) API: aleiva, I have been talking with german
(15:24:59) aleiva: API: yep
(15:25:14) API: the idea is us making the book, and then the foundation would pay it
(15:25:21) API: I ask german about the confirming people
(15:25:29) API: and foundation data
(15:25:39) API: btw, about the "group force"
(15:25:48) API: anyone knows anything about fer?
(15:25:53) API: Fernando Herrera
(15:25:58) korn: API: do we know if all notifications have done out?
(15:26:16) API: korn, you mean if travel committe has notified all people?
(15:26:20) API: yes AFAIK
(15:26:21) korn: API: yes.
(15:26:36) API: I mean that it would be strange to just notify some people
(15:26:39) korn: API: do you have the list from them? Or are we waiting for notified folks to update the wiki
(15:27:01) API: korn, this is a good point
(15:27:11) API: I was waiting a list from the travel committe
(15:27:25) API: but it would be good that the people confirmed that on the wiki
(15:27:45) API: although people sometimes showed somewhat lazy updating the wiki ...
(15:27:45) korn: OK. It would be helpful to have folks move from the "Want to go" table to the "Am going" table once they know they are getting fundind.
(15:28:04) API: korn, yes good idea, I will sent a "gently reminder mail" about that
(15:28:08) API: well, this is all from my side
(15:28:13) API: korn, something from your side?
(15:28:16) yippi: here is a test doodle page: http://www.doodle.com/c7bp328ty43zqyhk
(15:28:21) korn: Yes, thanks API
(15:28:49) korn: A request from the AEGIS Seville conference committee: please register for the AEGIS conference (if you are attending that)
(15:29:11) korn: Also - perhaps this is just for Bryen? - do we know which groups will be submtting posters?
(15:29:21) korn: Or rather, which projects?
(15:29:25) API: korn, Bryen is not present sorry
(15:29:31) API: he said that he couldn't assist
(15:29:47) korn: API: OK. Do we know who is doing which posters?
(15:30:12) clown: korn: would that be something to add to the wiki?
(15:30:13) korn: Also - I see you here tomeu - if there are other open source projects related to accessibility which would like to have a poster, we can accomodate that.
(15:30:29) paul_h: clown: I find that doodle example very confusing when looking at it with Orca. I say avoid...
(15:30:42) ***tomeu reads
(15:30:54) korn: Turns out we have significant space for posters. So - for example - a poster on sugar, a poster each on various GNU/Linux distros, etc. (emphasizing accessibility work of course)
(15:30:55) tomeu: is this posters as in banners or something like that?
(15:31:05) korn: Ah. Sorry tomeu. Some background...
(15:31:17) clown: paul_h: understood (I wasn't advocating it, just passing along an example)
(15:31:20) korn: Our upcoming hackfest is at PHP 5.2.4 (cli) (built: Oct 28 2007 17:13:14)
(15:31:28) korn: (sorry, paste error: http://live.gnome.org/Accessibility/HackfestAEGIS2010)
(15:31:39) yippi: paul_h, did you also try switching to calendar view?
(15:31:56) korn: This takes place alongside / within the AEGIS conference, at http://www.aegis-conference.eu/
(15:32:31) korn: At the AEGIS conference, we will have a room filled with posters (I forget the exist size; I can track it down), and as folks have lunch, coffee, etc., they will stroll through the posters and see what is going on in this space.
(15:32:37) tomeu: yup, talked with API at guadec about it, was considering attending
(15:32:56) yippi: paul_h, if their interface is not a11y, it might be good to click on their "Contact" link (at the bottom of the page) and let them know. Perhaps they can fix the issue if we could provide some feedback.
(15:33:08) tomeu: hmm
(15:33:14) korn: Great. I think it would be quite useful for you to attend tomeu. I have access to the registration list, and I see several folks coming from countries outside of "the west"
(15:33:17) korn: (e.g. ghana)
(15:33:35) API: tomeu, you are still considering or have you already decided that?
(15:34:45) tomeu: well, to be honest, I was expecting a bit more of helping hands from the sugar community on this
(15:35:12) korn: Anyway... we welcome posters. It would be great to have a series of posters on all of the wonderful GNOME a11y work. E.g. one on Orca, one on Dasher, one on Caribou, one on MouseTweeks.
(15:35:30) fer: ey API I'm here now
(15:35:32) korn: Likewise, one on Ubuntu a11y, one on the Speakup-modified Fedora, ...
(15:35:39) ***tomeu hates he doesn't have much time of his own to invest on accessibility :(
(15:35:39) ***joanie waves to fer
(15:35:39) ***clown hi fer
(15:35:55) korn: OK. Enough of my poster advertising.
(15:36:04) clown: korn: suggest that we add poster info to the wiki.
(15:36:13) clown: as in who, what, etc.
(15:36:15) korn: Back to registration-related stuff...
(15:36:23) korn: [clown - I don't suppose you might do that?]
(15:36:46) korn: [clown - link to info at / within http://www.aegis-conference.eu/]
(15:36:47) clown: korn: I can start it, but would ask that other add their stuff.
(15:36:51) yippi: have you tried contacting Walter Bender at Sugarlabs? Also Sean Daly is a good contact.
(15:37:05) korn: So, back to registration-related stuff.
(15:37:17) korn: Have folks (who are going) chosen their hotels? I recommend doing that soon...
(15:37:32) tomeu: sean is a bit busy lately
(15:37:46) tomeu: I still think I can get resources for a11y on sugar, but looks like will take a bit more
(15:37:53) clown: korn: being funded by GF means they choose the hotel.
(15:38:05) clown: and that's still to be decided, right?
(15:38:08) joanie: korn: and I think the rest of us are planning to stay with the group
(15:38:10) clown: which hotel I mean
(15:38:13) joanie: aleiva: picked out the hotel
(15:38:15) API: korn, as I said before we are getting for the final list
(15:38:21) joanie: Tryp Macarena(?sp)
(15:38:25) API: and yes we are going to be as fast as possible
(15:38:36) aleiva: joanie: I'll call today again
(15:38:37) yippi: I find contacting Adam Holt at OLPC often he puts me in touch with good contacts for SugarLabs when I have trouble getting in touch with them (holt@laptop.org).
(15:38:49) korn: I'm at the Tryp. Y'all don't have to be there (though being all there would be cool).
(15:38:59) korn: Just suggesting that reservations get made ASAP.
(15:39:02) aleiva: korn: it's the best place
(15:39:06) clown: API, aleiva : I sent email to add a name to the group for the hotel -- did you get it?
(15:39:22) aleiva: korn: near the venue, near seville center
(15:39:49) API: clown, I saw the mail, not the hotel
(15:39:52) ***API checking
(15:39:55) tomeu: yippi: I'm a sugar maintainer and member of the SL oversight board, so just tell if you need anything sugar-related
(15:40:02) aleiva: clown: umh, I don't remember to received that
(15:40:20) clown: API: I meant a person to add to the group for the group rate
(15:40:30) API: clown, ah ok, yes
(15:40:34) yippi: oh sorry, you are cleraly plugged in already
(15:40:37) API: we will add him
(15:40:52) korn: alevia/API: you guys getting a group rate diferent from the AEGIS group rate?
(15:40:57) API: aleiva, I will forrward that mail
(15:41:05) aleiva: korn: umhhh
(15:41:11) aleiva: korn: what's the AEGIS group rate?
(15:41:16) clown: aleiva, right you were not cc'ed -- do you need the info?
(15:41:30) aleiva: clown: I suposse API can forward it to me, dont worry
(15:41:31) API: korn, have you already commented that AEGIS group rate?
(15:41:33) korn: It was booked for me (god I love minions...), so I don't know the amount.
(15:41:41) API: first new, at least from our side
(15:41:50) clown: aleiva, API, okay. I can also add his name to wiki, if that helps. ;-)
(15:41:53) korn: But I believe that is part of what we arranged when we chose the hotels.
(15:42:06) ***clown wishes he had access to korn's minions
(15:42:13) korn: Ah. Yes. See http://www.aegis-conference.eu/pages/hotels.html
(15:42:24) korn: 76EUR for a single room, 85 EUR for a double.
(15:42:37) API: korn, but I guess that you need to be registered for that
(15:42:49) API: AFAIK, most of the people assisting to GNOME hackfest
(15:43:00) clown: didn't korn say above that if you are attending, you have to register?
(15:43:03) API: are not being registered on the AEGIS event, like CSUN
(15:43:23) clown: good point.
(15:43:24) korn: clown: you do not have to register for the AEGIS Seville conference to attend the GNOME AEGIS hackfest.
(15:43:28) API: clown, if you are attending to the AEGIS event yes
(15:43:36) API: but the hackfest is a parallel event
(15:43:50) clown: ah, i get it now. reaches for joanie's pot of coffee.
(15:43:54) korn: And if you are doing the hackfest, you get to use the discount rate for AEGIS event. Put "GNOME" as your student id.
(15:43:59) ***joanie pours clown a cup
(15:44:10) mgorse: If we might be at the booth, then do we need to register for the conference?
(15:44:31) korn: mgorse: hmmm... I would say not.
(15:44:44) korn: Booth will be open during lunches & in the evening.
(15:45:00) korn: Sessions are in different rooms from the exhibit hall (and poster hall).
(15:45:11) API: korn, in this case, we still need a group discount just for the people going to the hackfest
(15:45:22) korn: API: you mean for the hotel?
(15:45:26) ***aleiva learn a new word today "booth", awesome :-)
(15:45:32) API: korn, yeah, for the hotel
(15:45:36) ***joanie smiles
(15:45:39) korn: API: I really suspect if you say to the hotel "I want the AEGIS rate", you will be fine.
(15:45:49) korn: Perhaps I'm wrong, but I do suggest at least trying it.
(15:45:57) API: aleiva, could you try that?
(15:45:58) korn: In my experience with hotels, all you need is the "password"
(15:46:01) API: I mean, ask that
(15:46:04) aleiva: API: I'll do
(15:46:07) aleiva: API: yes
(15:46:12) API: aleiva, ok, thanks
(15:46:20) aleiva: API: I'll negotiate with them
(15:46:27) korn: OK. Next topic...?
(15:46:35) API: well, people anything else about AEGIS?
(15:46:40) bnitz: korn:I wasn't clear on the registration either. Could you put something on the wiki?
(15:46:44) API: or move to next topic?
(15:46:59) korn: I believe Stormy suggested holding a virtual hackfest on GNOME a11y at the same time as our physical one.
(15:47:16) aleiva: yup
(15:47:17) korn: Sounds like a great idea to me. What do y'all think?
(15:47:24) Pendulum: I think it's a great idea :)
(15:47:24) stormy: I thought it would be a good way to get other people involved.
(15:47:27) aleiva: what exactly mean "virtual hackfest"
(15:47:54) aleiva: irc/ml activity during hackfest?
(15:48:01) API: aleiva, yes more or less
(15:48:01) clown: would video conferencing be possible for virtual attendance?
(15:48:08) tomeu: we had some remote attendants to our python hackfest
(15:48:09) korn: bnitz: yes, should do that. But also, please simply go through http://www.aegis-conference.eu/ - all info about registering is there (but just do so as a student, with your school as "GNOME")
(15:48:11) API: is just ask the people of other programs
(15:48:11) tomeu: just irc
(15:48:17) API: to try to focus on a11y tasks
(15:48:25) API: as we would be available during the hackfest
(15:48:35) korn: clown: I think we could perhaps make audio work as well, via freeswitch or some such.
(15:48:44) clown: skype?
(15:48:48) clown: breeze?
(15:48:49) aleiva: API: ok, nice
(15:49:04) korn: clown: could use skype, but skype client accessibility isn't fabulous.
(15:49:11) clown: i see
(15:49:12) API: hmmm ok, I think that I misunderstood the virtual hackfest
(15:49:17) korn: And us being GNOME and all, I figured we might want to use a GNOME SIP client.
(15:49:20) API: korn you are thinking on something on runtime?
(15:49:28) API: I mean, on real time?
(15:49:28) korn: 'runtime'?
(15:49:36) korn: Ah, yes. API - I was thinking about both.
(15:49:46) korn: E.g. we declare the week to be GNOME a11y week.
(15:49:57) korn: and then we consider whether certain sessions should be "live simulcast"
(15:49:58) API: in that case it wouldn't be a virtual hackfest, it would be just a tele-hackfest
(15:50:13) aleiva: hehe, or a live-hackfest :-D
(15:50:25) API: stormy, that was your idea? or just ask people to try to focus on a11y work during the hackfest?
(15:50:54) korn: E.g. if folks who are involved in sugar stuff want to connect to a discussion on at-spi over dbus, or folks from the gnome-release & testing teams want to connect to the testing discussion.
(15:51:44) API: well, I see that, from the infrastructure pov really hard to achieve
(15:52:24) korn: API: perhaps, but maybe not. With a USB speakerphone, we could have fairly reasonable audio pick-up in our room.
(15:52:38) korn: API: I am *not* suggesting video.
(15:52:52) korn: And I am not suggesting we do this for the entire hackfest.
(15:52:58) API: korn, ok
(15:53:02) API: anyway in this case
(15:53:14) API: we would require to add more explicit spots on the agenda
(15:53:25) korn: API: yes, absolutely. That's where I was headed next...
(15:53:27) API: http://live.gnome.org/Accessibility/HackfestAEGIS2010
(15:53:34) API: there are some specific items
(15:53:37) korn: And http://live.gnome.org/Accessibility/HackfestAEGIS2010Schedule
(15:53:38) API: like the documentation and testing
(15:53:56) API: but not those
(15:54:00) API: at-spi etc
(15:54:38) API: from stormy mail
(15:54:41) API: "Ask everyone in the GNOME community to
(15:54:41) API: fix any bugs related to GNOME a11y in their project during that week."
(15:54:47) API: anyway, we can try both
(15:54:52) API: as korn said before
(15:55:00) API: just ask other teams to try to focus on a11y work
(15:55:10) API: and try this tele-assistance to relevant meetings
(15:55:13) korn: So my suggestion to y'all is:
(15:55:13) korn: - figure out who isn't attending in person, who would really like to be part of a *specific* discussion
(15:55:13) korn: - figure out who we want to have part of a *speicific* discussion (e.g. sugar folks, gnome-release folks, Mozilla folks)
(15:55:13) korn: - nail those specific things down to a time on the agenda
(15:55:13) korn: - have an IRC and audio connection gonig during those times
(15:55:43) API: ok, lets try that on the ml (not too many people here)
(15:55:43) stormy: Also maybe have people available on IRC.
(15:55:47) stormy: Maybe during specific times.
(15:55:55) stormy: So that if people are trying to fix other a11y related bugs
(15:56:01) stormy: they have someone to ask questions of.
(15:56:41) API: stormy, yes of course, if we ask other projects to focus
(15:56:52) API: on thisi work, we should also give something in exchange 
(15:56:53) korn: So... is someone able to own this, and make sure it happens (both the general A11y week and specific schedule nailing)?
(15:57:28) korn: korn looks at API...
(15:57:32) API: korn, I will send (and try soon) a mail to the list about the specific schedule nailing
(15:57:34) korn: (and stormy)
(15:57:43) API: then we can ...
(15:57:58) korn: Great. OK. I have two more AEGIS topics (in the 3 minutes left of the hour...)
(15:57:58) API: hmm, a planet.gnome.org or a mail to desktop devel
(15:58:03) API: for the rest of the temas
(15:58:11) API: korn, shoot fast
(15:58:22) stormy: If someone can put together the list of bugs that a11y needs fixed
(15:58:22) ***clown can stay past the hour
(15:58:31) korn: Plans are coming together for an eSpeak improvement effort at the AEGIS conference.
(15:58:33) stormy: I can start trying to spread the word of a virtual hackfest
(15:58:58) API: stormy, ok, thanks
(15:59:09) korn: Alas we won't have Jonathan there in person. But we do expect to have a room running most of Thursday & Friday for folks speaking all languages to come in for language tuning.
(15:59:13) API: korn, you mean hackers working on espeak during the hackfest=
(15:59:15) stormy: API, can someone put together the list of bugs we want people to work on.
(15:59:35) ***API API looks to joanie
(15:59:39) korn: API: less hackers than native speakers helping tune the languages/voices
(15:59:40) joanie: :-)
(15:59:54) aleiva: joanie: 3.0! list, sure :-D
(15:59:58) joanie: stormy: API: It is already on my to-do list
(16:00:07) API: korn, hmmm, well, as we would be in spain
(16:00:08) joanie: aleiva: (This would be many of the "blocking" bugs)
(16:00:14) korn: But... given that our AEGIS eSpeak expert will be in attendance, we might try to get him onto the Mon or Wed hackfest agenda.
(16:00:14) API: you mean spanish native speakers?
(16:00:36) korn: API: we will be in Spain, but we will also have attendees from all over the world.
(16:00:51) bnitz: joanie: 2 meetings ago you mentioned a specific kind of bug which affects orca and which I need to talk to you about how to test for.
bnitz bnitz1 
(16:00:59) korn: Looking at the registration list (did I mention I want y'all to register if you are attending?), we have folks from many European countries coming.
(16:01:03) clown: you mean people who don't speak in acronyms and other coding jargon?
(16:01:06) joanie: bnitz: on my list. :-)
(16:01:09) API: korn, you mean, for example, ask joanie to add american voices?
(16:01:12) korn: Also from India, Africa, etc.
(16:01:13) bnitz: joanie: Thanks.
(16:01:25) aleiva: clown: hoho :-D
(16:01:36) slee: hhe
(16:01:37) clown: :-)
(16:01:41) korn: API: I'm most concerned with the "less well developed" languages.
(16:01:49) korn: So definitely clown for Candadian...
(16:01:50) bnitz: joanie: If it can be described in a bug or series of bug, I propose that that should be a focus of a hackfest activity.
(16:01:52) joanie: So Texan
(16:02:06) clown: yes, I speak Canuck expertly
(16:02:10) korn: Candudian?
(16:02:11) clown: oot and aboot, and all that.
(16:02:15) joanie: eh?
(16:02:23) clown: y'know?
(16:02:41) korn: OK, so as that gets finalized, spreading the word here would be useful too (hackers who are interested in helping out)
(16:02:45) API: korn, ok, and the other item (as we are officially out of time=
(16:02:46) API: ?
(16:03:04) Pendulum: I'll see if I can get some of the Ubuntu a11y people to work on stuff too :)
(16:03:05) korn: Final item: y'all may have heard of Gregg Vanderheiden's "National Public Inclusive Infrastructure" effort
(16:03:22) korn: See http://npii.org
(16:03:39) mgorse: Is that a new name for Raising the Floor?
(16:03:57) korn: This is an effort to get gov't funding to help build the various components needed for an inclusive, public infrastructure for a11y
(16:04:02) clown: yup, mgorse 
(16:04:03) korn: mgorse: it's a facet of RtF, yes.
(16:04:32) korn: Anyway, he's the Friday morning keynote speaker, and we'll likely have a BOF for it sometime Friday late morning / afternoon.
(16:05:05) korn: We're working on finding a room for the BOF. If we can't find an additional room, we might ask to use some hackfest space for 1-2 hours on Friday...
(16:05:36) korn: Given that much of what the NPII is trying to do is get gov't $$ to fund FOSS a11y work, I think it is very relavent to us.
(16:05:46) korn: tomeu: also of potential interest to sugar
(16:06:16) korn: S'anyway, that's all I had.
(16:06:21) API: korn, just to know, this is USA gov right?
(16:06:31) korn: API: no, not US only.
(16:06:41) tomeu: interesting, I can float around the idea in the sugar lists and see what happens
(16:06:41) korn: NPII has become "NPIIs" which are all part of a larger GPII
(16:06:48) korn: (Global Public Inclusive Infrastructure).
(16:07:00) API: korn, ok
(16:07:08) korn: Idea is that different things could be funded by different gov'ts, but as all would be open & shared, all could be used by all.
(16:07:24) API: korn, ok it seems a good idea
(16:07:35) korn: You might also imagine NPII(my-country) might fund (my-country)-specific stuff, localization, TTS, etc.
(16:07:47) API: ok, thanks for the explanation
(16:07:49) API: anything else?
(16:08:09) slee: korn - thanks thats cleared up my confusion too
(16:08:19) korn: Anyway, I thought hooking y'all up to that might be useful. And again, if I can't scare up another room, any objection to using hackfest space on Friday for 1-2 hours for this?
(16:08:59) korn: OK, that's all I had.
(16:09:02) API: korn, not from my side
(16:09:03) API: ok
(16:09:09) API: 10 minutes over the time
(16:09:34) API: we can conclude the meeting unless someone has a last (quick) shoot
(16:09:46) ***clown bang!
(16:09:54) ***clown apologizes
(16:10:07) ***API s/shoot/shot
(16:15:14) API: ok, meeting over folks, thanks for attend