10:37 <@API> lets start 
10:37  >>> joanie sits
10:37 <@API> the meeting
10:37 <@API> we are here for that
10:37  >>> clown is afraid of API's arms.
10:37 < jhernandez> xD
10:37 < |Lupin|> nice to meet you all
10:37 < clown> hi Lupin
10:37 <@API> |Lupin|, just in case
10:37 <@API> we have this page
10:37 <@API> http://live.gnome.org/Accessibility/Meetings
10:37 <@API> to organize the meetings
10:37 ::: API changed the topic of #a11y-meeting to: http://live.gnome.org/Accessibility/Meetings
10:38 <@API> with a agenda and so on
10:38 <@API> so if in the future you want to talk about something specific, feel free to add any item on it
10:38 <@API> normally the meeting is about following the agenda
10:38 <@API> sooo
10:38 <@API> as the meeting started
10:38 <@API> 1. GNOME 3 
10:39 < |Lupin|> ok API thanks a lot !
10:39 <@API>  1.1 General updates/news? 
10:39 <@API> |Lupin|, you are welcome
10:39 <@API> well about this point
10:39 <@API> a new gentle reminder
10:39 <@API> GNOME 3.0 is near
10:39 <@API> so it would be good to update this page
10:39 <@API> in order to know the current status
10:39 <@API> in fact, after GNOME 3.0 release
10:40 <@API> I guess that this page will help us to track issues to GNOME 3.2
10:40 ::: mgorse [mgorse@SDF.ORG] joined #a11y-meeting
10:40 < mgorse> Hi. Sorry I'm late
10:40 <@API> mgorse, no problem just starting
10:41 ::: Bryen [~Bryen@c-24-12-98-169.hsd1.il.comcast.net] left #a11y-meeting []
10:41 <@API> GNOME 3
10:41 <@API>     General updates/news? 
10:41 <@API> well, anything about this point
10:41 <@API> ?
10:41 <@joanie> Matthias say Orca is largely working (yay!)
10:41 <@joanie> but it doesn't quit when he disables screen saver. So I'm going to look at that today
10:42 <@joanie> but at least it's a positive step. He says gnome-shell was presented too. ;-)
10:42 <@API> joanie, yep, frederic tested that
10:42 <@API> and then I guess that the work of mgorse and colin walters helped to avoid some 
10:42 <@API> upstart racy things
10:42 <@joanie> way to go mgorse and colin!
10:43 <@joanie> (I'm done)
10:43 <@API> well, so next
10:43 <@API> 1.2 Is Accerciser still broken? 
10:43 <@API> after read the minutes of previous week
10:43 <@API> and based on my own experiences
10:43 < mgorse> yeah; that was Colin's patch really
10:44 <@API> some people have some problems with accerciser running on gnome3
10:44 <@API> soo
10:44 <@API> what about rising accerciser risk level?
10:44 <@API> right now is medium, but not sure if it applies now
10:44 <@API> bnitz, what do you think?
10:44 <@joanie> +1
10:44 < mgorse> Are there bugs filed?
10:44 < bnitz> Yes raise the level
10:44 <@API> as far as I know, you are now focused on gnome 2 things
10:44  >>> bnitz needs bugs and more information
10:44 < bnitz> other than "some people" and some problems
10:45 <@API> yes it is true
10:45 < bnitz> hard to work with that so yeah it's high risk.
10:45 <@joanie> lol
10:45 <@API> these days
10:45 <@API> those errors
10:45 <@API> are mostly managed as
10:45 <@joanie> msanchez: last week Aleiva said you couldn't start Accerciser at all. Is this (still) the case?
10:45 <@API> "it is not working for me, lets ping mgorse or bnitz"
10:45 < mgorse> lol
10:45 <@API> we need something more "homogeneus"
10:46 <@API> homogeneous in fact
10:46 <@API> but ok, it seems that all agree
10:46 <@API> so, actions:
10:46 < bnitz> Can anyone tell me if it works in jhernandez's iso?
10:46 <@API> 1. increase risk
10:46 <@API> 2. people with problems, please report bugs
10:46 < mgorse> but then sometimes it's hard to tell whether there's a problem with at-spi or accerciser vs. a packaging problem vs. something not configured or installed, etc
10:46 <@joanie> mgorse: Aleiva (whom I've pinged) last week said it didn't build
10:47 <@API> mgorse, well yes, but this is one of the accerciser purposes
10:47 < msanchez> joanie: yes, I had problems with that, but finally "fixed" it by hiding the API Browser tab
10:47 <@API> checks if a11y doesn't work
10:47 <@joanie> You can browse API?
10:47 <@API> if accerciser doesn't work fine, we can suppose that a11y in general will have problems
10:47 <@joanie> (sorry)
10:47 < msanchez> I'll check if it's still failing and file a bug accordingly if so
10:47 <@joanie> msanchez: thanks!!
10:47 < bnitz> API true.
10:47  >>> bnitz is running in a virtualized environment where gnome-3 or anything 3D sux.
10:48 <@joanie> bnitz: do you have a spare machine you could use for gnome 3?
10:48 < bnitz> Which reminds me, that fallback mode we get when 3D accel isn't available, will that stick around and is it meant to be accessible?
10:48 < clown> bnitz, good question.
10:48 <@API> bnitz, the fallback mode
10:48 <@API> in theory has two purposes
10:48 <@API> people with no 3d accel
10:48 <@API> and *a11y*
10:48 < jhernandez> bnitz, accerciser is compiled/installed fine in testing distro, but there are problems with at-spi
10:48 < bnitz> joanie:not at the moment.  My laptop doesn't even support 3D on ubuntu 10.04 
10:49 <@API> because current a11y support on gnome-shell is not enough
10:49 <@API> improving but not enough, and planned for 3.2
10:49 <@API> so testing gnome 3.0 should also test the fallback mode
10:49 < bnitz> API: That I can do ;-)
10:49 <@API> in fact, from our a11y pov, the main test should be done on the fallback mode
10:50 < bnitz> I'll see if I can get a 3D capable machine so I can run gnome-shell and see what other people are seeing.
10:51 < bnitz> jhernandez: Can you elaborate on at-spi problems?
10:51 <@API> bnitz, as I said, fallback mode should be also tested
10:52 <@API> well, I think that accerciser thing was clarified
10:52 <@API> so lets move
10:52 <@API> 2. The (still-largely-outdated) 'Status Page' 
10:53 <@API> hmm, I already included that on the previous item
10:53 <@API> but anyway
10:53 <@API> please update gnome 3.0 page
10:53 <@API> please write down current state, not how it was one year ago
10:53 <@joanie> On that topic....
10:53 <@API> yes?
10:53 <@joanie> There are some things on that page that will just not get updated if we leave it to people to do so
10:54 < jhernandez> bnitz, I'll comment problems with you ok? ;)
10:54  >>> mgorse adds that to his already-long to-do list :)
10:54 <@joanie> jhernandez: I'd like to hear them too
10:54 < bnitz> jhernandez: Thanks I was going to ask that.
10:54 <@joanie> but first things first
10:54 <@joanie> so about the page
10:54 < jhernandez> joanie, that's the way!
10:54 < jhernandez> go ahead with "the page"
10:54 <@joanie> I am wondering if we should not just have a status page .... subcommittee and spend an hour at some point 
10:55 <@joanie> discussing, updating, and concluding 
10:55 <@joanie> (sorry kvm fail)
10:56 <@joanie> I mean, CSPI, libgail-gnome, etc.
10:56 < clown> +1
10:56 <@joanie> can (some of us) conclude what the deal is with them once and for all
10:56 <@joanie> ?
10:56 <@API> well joanie, in fact this is related
10:56 <@API> imho
10:56 <@API> with the testing thing
10:56 <@joanie> And perhaps make an "Ain't gonna happen" section
10:56 <@API> at least in some items
10:57 <@joanie> API go on (please elaborate)
10:58 <@API> joanie, well, for example
10:58 <@API> about the a11y indicators 
10:58 <@API> on gnome 3
10:58 <@API> etc
10:58 <@API> they are something that are required to be tested with the distro
10:58 <@joanie> ohhh. You mean we test and then we update.
10:58 <@API> although it is true that with your examples
10:58 <@API> cspi, libgail-gnome it is also a thing
10:59 <@API> about see his status
10:59 <@API> anyway
10:59 <@API> Im not sure about it
10:59 <@API> I never touched libgail-gnome for example, so I don't know 
10:59 <@API> if a meeting
10:59 <@API> and say "I don't know" about it could solve it
11:00 <@joanie> okay, then I will keep pinging people
11:00 <@joanie> and see if we can get a definitive (or any) answer out of them
11:01 <@API> joanie, so, moving on?
11:01 <@joanie> yessir
11:02 <@API> s
11:02 <@API> 3. A11y testing distro, and how to make a bootable USB (Joseph). 
11:02 <@API> clown, ?
11:02 < clown> okay...
11:02 < clown> I used a tool from the "Made of Easy" site to make a bootable USB ...
11:03 < clown> See: http://gnome3.org/tryit.html
11:03 < clown> and, it worked fine for that iso, but...
11:03 < clown> I couldn't build a bootable USB from the a11y testing distro iso.
11:03 < jhernandez> clown, i have crashed with this problem too
11:03 < clown> it builds fine, but boots not.
11:03 < clown> jhernandez:  so, I'm not alone.
11:04 < jhernandez> I supposed to make usb as with fcrozat spin, but it doesn't work
11:04 < jhernandez> i burned to a cd and it works
11:04 < jhernandez> so, at this moment, don't know what's the problem here
11:04 < clown> ah, okay, I could try that for now.
11:04 < clown> the cd I mean.
11:04 < jhernandez> :)
11:05 <@joanie> jhernandez: and you built the usb option available in susestudio?
11:05 < clown> The main reason I'm doing this is to make sure the mag prefs dialog I sent to  the distro page actually works.
11:05 < jhernandez> ok, anyway, i'll sure myself next spin will be bootable with USB :s
11:05 < clown> the good news:  it does work on the with "made of easy" iso.
11:05 < clown> great jhernandez!
11:05 < bnitz> jhernandez : Another data point, I'm running from VirtualBox and it worked.  (though 3d sucked)
11:06 < clown> will you include the mag prefs app I submitted?
11:06  >>> joanie thinks this might be a good time for jhernandez to elaborate on the at-spi issue
11:06 < clown> bnitz:  yeah, I did the same with virtualbox -- same outcome.
11:07 < jhernandez> clown, I'm waiting for stabilization in some gnome code, 2.91.92 packages were broken by a vuntz patch
11:07 < jhernandez> :S
11:07 < clown> jhernandez:  okay, keep me posted.
11:07 < jhernandez> but, include this in the distro isn't a problem
11:07 < bnitz> clown: FWIW if you have good 3D support for the host OS you can enable 3D and it won't be too horrible.
11:07 < clown> btw, peter korn thinks this test distro is a very good idea.
11:07 < jhernandez> :)
11:07 < jhernandez> i'll choke you! :)
11:08  >>> joanie snickers
11:08 < jhernandez> yes, for us is a great idea
11:08 <@joanie> What a mean thing to say clown :-P
11:08 < clown> bnitz, let's touch base later, and you can tell me how to do that
11:08 < bnitz> ok
11:08 < clown> ??
11:08 < jhernandez> bnitz, ok!
11:08  >>> clown clown's are not mean.  just scary sometimes.
11:08 < jhernandez> virtual machines are virtual machines :S
11:09 <@API> well, so ... please
11:09 <@API> conclusion, and action items?
11:09 ::: aleiva [~gloob@petersburgo.euler.es] joined #a11y-meeting
11:09 < clown> API:  I wait for the next spin from jhernandez, and use a CD for the time being.
11:09 <@API> ok
11:09 < jhernandez> well, I added to my backlog booteable USB thing
11:10 < jhernandez> so, for me, this point is ended
11:10 <@API> so, can I move to next item?
11:10 <@API> ok, thanks
11:10 < clown> fine with me.
11:10 <@joanie> I bet clown 
11:10 <@API> 4. Banning of DST -- along with Joseph's wiki-editing privs (Joanie). 
11:10 <@API> joanie, ?
11:10 <@joanie> Clown put it there (the first part)
11:10 <@joanie> moving on
11:10 < clown> no time for that item.
11:11 <@API> ?¿
11:11 <@API> ok, as you wish
11:11 < clown> just spring forward to the next
11:11 <@joanie> API check the wiki history for that page
11:11 <@joanie> ba-dum-dum
11:11 <@API> 5. New subscribe-able calendar has arrived! 
11:11 <@API> joanie, your point
11:11 <@joanie> https://www.google.com/calendar/ical/gnome.a11y%40gmail.com/public/basic.ics
11:11 <@joanie> It's a done deal
11:11 <@joanie> meetings (and the Atk Hackfest) are in there
11:12 <@joanie> subscribe
11:12 <@joanie> or don't
11:12 <@joanie> (done)
11:12 <@joanie> well, not quite done: I'll also add a link to the meetings page
11:12 <@joanie> and the main team page
11:12 <@joanie> and include it in my weekly reminders
11:12 <@joanie> (now done)
11:12  >>> clown tries it out..
11:13  >>> clown works for me.
11:13 < clown> thanks joanie
11:13 <@joanie> yay!
11:14 <@joanie> thank aleiva. It was his idea.
11:14  >>> clown thanks aleiva
11:14 <@API> joanie, anything else?
11:14  >>> joanie is just a humble minion.
11:14 <@joanie> not on this topic
11:14 <@API> ok
11:15 <@API> so, last item on the meeting
11:15 <@API> 6. Action Item update 
11:15  >>> API checking
11:16 <@joanie> AI's are getting out of control
11:16 <@API> well fer
11:16 <@API> is not here
11:16 <@API> joanie, yes it is true
11:16 <@API> but some of them were already solved
11:16  >>> joanie nods
11:16 <@API> but
11:16 <@API> soemthing that it is required to be done remembered:
11:16 <@API> Q4 update!
11:16 <@API> me included
11:16 <@API> should update Q4
11:16 <@API> as in brief
11:16 <@joanie> yup
11:16 <@API> it would start the Q1-2011 update
11:17 <@joanie> The other thing that would be helpful now that more team members are stepping up (thank goodness!)
11:17 <@joanie> is that if you get an AI and do that AI, remove the AI from the list
11:17 <@API> I think that this is the most thing to be solved
11:17 <@API> soon thing on the action list
11:17 <@joanie> I remove 'em when I know they're done
11:17 <@API> so
11:17 <@joanie> but I cannot keep up with them all
11:17 <@API> ok
11:17 <@API> so
11:17 <@API> lets start with misc time
11:18 <@API> first: as Bryen said on #a11y
11:18 <@API> although we have a page about "missing things on GNOME 3.0"
11:18 <@API> we lack a page about "new things" 
11:18 <@API> and about 
11:18 <@API> ejem
11:18 <@API> "cool" things
11:18 <@API> this triggered my memory
11:18 <@API> as recently all teams were asked about the release notes
11:18 <@API> AFAIK
11:19 <@API> targetted due GNOME 3 release
11:19 <@API> so
11:19 <@API> what about create a quarter report similar page?
11:19 <@API> about GNOME 3.0 new things and so on?
11:19 <@API> or at least to gather release notes?
11:19 <@joanie> release notes usually go on the release notes page afaik
11:20 <@API> ok
11:20 <@API> so this leads to 
11:20 <@API> a GNOME 3.0 page
11:20 <@API> anyway
11:20 <@joanie> https://live.gnome.org/TwoPointNinetyone/ReleaseNotes
11:20 <@API> other approach 
11:20 <@API> would be 
11:20 <@API> update our current gnome page
11:21 <@API> http://projects.gnome.org/accessibility/
11:21 <@API> as it is mostly gnome 2.0 oriented
11:21 <@API> I think that this was and old item
11:21 <@API> not included explicitly on the current action items?
11:21 <@joanie> which?
11:21 <@joanie> release notes
11:21 <@API> sorry, forget that last ? mark
11:21 <@joanie> or update the wiki?
11:22 <@API> I mean that some months ago
11:22 <@API> we started to check our accessibility pages
11:22 <@API> as some were outdated
11:22 <@joanie> and we (I) deleted a lot
11:22 <@API> ie
11:22 <@joanie> and put pointers on other pages
11:22 <@API> http://library.gnome.org/devel/accessibility-devel-guide/nightly/gad-how-it-works.html.en
11:22 <@joanie> yeah, that one I missed
11:23 <@API> anyway, I guess that this is a item too long to misc time
11:23 <@API> so using my own gentle reminder
11:23 <@API> we would talk about this in other occasion
11:23 <@API> so, in the remaining misc time
11:23 <@joanie> next week
11:23 <@API> jhernandez, could we go back to the at-spi problems on the distro?
11:23 <@API> could you elaborate that?
11:23 < jhernandez> ok
11:25 < jhernandez> at this moment, accerciser isn't exploring all atk components/applicationsç
11:26 < jhernandez> don't know if problem is accerciser
11:26 < jhernandez> or at-spi
11:26 <@joanie> what's "missing"?
11:26 < jhernandez> so, now, that we have lot of a11y bugs fixed with 2.91.93
11:27 < bnitz> jhernandez: in fallback mode (your distro) accerciser sees itself but doesn't see other stuff.
11:27 < jhernandez> bnitz, that's it!
11:27 <@API> bnitz, only accerciser is registered?
11:27 <@API> jhernandez, did you check if there are two registries running?
11:27 < bnitz> I see errors failure to load pk-gtk-module and canberra-gtk-module when I launch stuff (e.g. eog)
11:27 <@joanie> bnitz: does it see other stuff launched after accerciser?
11:27 <@API> on frederic crozat test
11:27 <@API> he had that problem
11:28 < jhernandez> API, just confirmed that
11:28 <@API> bnitz, that shouldn't be a problem for a missing a11y support
11:28 < clown> bnitz, if I launch gnome shell "by hand", I get that stuff about pk-gtk-module and canberra-gtk-module as well.
11:28 <@API> jhernandez, ok confirmed, but the output?
11:28 < bnitz> I only see one registry
11:28 < jhernandez> there are at-spi-registryd and at-spi2-registryd!
11:28 <@API> jhernandez, I mean, confirmed one registry, or confirmed two
11:28 <@joanie> lol
11:28 < bnitz> I see only at-spi2-registryd
11:28 <@API> jhernandez, well, that means that the distro has both at-spi running
11:29 < mgorse> Sounds similar to what nagappan was running into. I'll see if I can reproduce after the meeting
11:29 <@API> as a gnome 3 thing
11:29 <@API> IMHO
11:29 <@API> it should only include at-spi2
11:29 < jhernandez> yes, so, I'll add to testing distro request list
11:29  >>> mgorse agrees with API if it's GNOME 3
11:30 <@API> jhernandez, ok, thanks
11:30 < jhernandez> thanks you all, i really needed that feedback from all of you
11:30 < jhernandez> ;)
11:31 <@joanie> jhernandez: thanks for doing it!
11:31 <@joanie> you're our hero
11:31 < bnitz> jhernandez: Thanks for the test distro!
11:31 < bnitz> Hey this test distro is a good idea ;-)
11:31 < |Lupin|> thanks to everybody for having acceptedmy silent participation
11:31 < clown> jhernandez, thanks you.
11:32 < jhernandez> :P
11:32 < |Lupin|> (oops, a bit too early perhaps, sorry)
11:32 <@joanie> heroes don't stick out their tongues
11:32  >>> joanie kicks jhernandez 
11:32 <@joanie> ;-)
11:32 < jhernandez> xD
11:32  >>> clown wonders if we should start a improv group.
11:33  >>> joanie is suprised API allowed us to be this silly
11:33 < aleiva> clown: you mean improvement?
11:33 < clown> I wish, aleiva
11:33 < clown> improvisation
11:33 <@API> joanie, well, it is miscellaneous time
11:33 < clown> silly time?
11:33 <@API> anyway, as this seems to be concluded
11:33 <@API> meeting over!!