Contents
Meeting Summary
- Meeting started by Joanie at 16:06 CET.
- Meeting ended at 17:15 CET.
- Participants (Lines Said):
- Magdalen - magpie2 (127)
- Joanie - joanie (108)
- Joseph - clown (64)
- Juanjo - jjmarin (18)
- Mike - mgorse (14)
GSoC Update
- Magdalen has made progress on the UI additions for the universal access panel for the system settings (gnome-control-center).
- ACTION: Magdalen will file a bug about the ui.
- A. Day said it would be unlikely my proposal for the ui would be accepted into 3.10 but he seemed to like the look. Magdalen hopes to find more out when filing the bug.
- A. Day was asking about the GSettings and what they are for. He wanted to speak to joanie about that. Magdalen suggests Joseph could talk to him as well to help clarify that.
- Joseph told Magdalen she has delivered the coding deliverables by completing a suggested glade ui prototype but Magdalen is going to try to get it working with the GSettings since Joanie and Joseph have given good guidance to help get that done. However she is started at university this week and has a lot of time constraints so it may have to be fully working after GSoC in case the time runs out.
- the deliverable codes completed thus far are the following links:
- Relevant bugs:
- ACTION: for GSoC code submission, Magdalen will take all of her submitted patches that were committed from gnome's bugzilla, tar them up, and sent the tarball to GSoC.
GSoC code submission guidelines: http://www.google-melange.com/gsoc/document/show/gsoc_program/google/gsoc2013/codeguidelines
- The code for the ui is not up on github or git.gnome.
- ACTION: Magdalen will do the github today in case the ui is not fully working for the gnome-control-center ui bug Magdalen is filing today
- ACTION: Magdalen will maybe add the code link to my github and say that it is not complete and upload the pictures for today and try to get a patch ready before Monday
- ACTION: Magdalen will also put the ui snaps on the wiki and make sure all work completed during the GSoC is properly referenced to make things easier.
- ACTION: Magdalen is to finish a 'final GSoC' blog contribution to the planet feed and she will base that around the ui work and include the things she learned from Joseph and Joanie recently, in that post so it explains about about the accessibility control center ui and how that should work.
- Magdalen thinks the Admin, Mentors and the G-S team (especially Jasper) have been really, very amazing and she is delighted to have been able to learn from their expertise this summer.
- There was a commit to the magnifier code that disabled the initialization of atspi on the condition that the magnifier was not used.
- Apparently, the desktop freezes for 30 sec when atspi is running if the Display control panel is accessed.
- There was much discussion about whether this commt should be reverted, while mgorse is working on fixing atspi.
- gnome-shell can deadlock if a process calls it via D-Bus while gnome-shell is trying to make an AT-SPI call to that other process via D-Bus.
- Magdalen found out that atspi had a bug yesterday after finding the default atspi initialisatin had been removed yesterday and told Joanie and Mike. Mike is infoing his progress.
- It is exasperated by a hack made to AT-SPI a while ago that makes it not time out on a call for up to 15 seconds fo ran app that immediately started
- Magdalen Jasper Mike, Joseph, Giovanni and Joanie discussed this yesterday.
- Mike is working on a patch that makes AT-SPI calls enter a main loop, rather than just dispatching D-Bus messages, and thinks that this is safe, but any change of that sort seems to have a bit of risk.
- If the issue is not fixed there is a danger the feature will not be working in 3.10 as planned.
Other Issues Related to GNOME 3.10
- In general we seem to have caught all the accessibility-related regressions.
But Frederic Peters caught a gui issue https://people.gnome.org/~fpeters/a11y-zoom-prefs.png.
- ACTION: Joanie will investigate the Zoom preferences GUI issue.
- Magdalen has been rethinking her post-gsoc TODO goals and following the conversations yesterday she would like to try to learn something from Mike and try to make sure all the atspi codes that need to be in javascript for gnome-shell are working as they should and asks for Mike's thought on that possibility.
"Boston" Summit and the possibility of Wayland Accessibility Hacking
If you are planning on coming to the summit, you need to add yourself to the wiki.
If you need sponsorship, you need to fill out the table on Montreal2013/travelsponsorship
W3C Updates
- No news specifically from W3C, but in ARIA-related news, Joseph will giving a talk at the jQuery accessibility summit Oct 10-11.
http://www.deque.com/deque-partners-jquery-create-accessibility-summit
- Joanie has requested, and appears very like to get, "Invited Expert" status.
- Joanie will be looking at current "mappings" for HTML and ARIA with the aim of adding new API to ATK/AT-SPI2 where needed for better a11y support.
Marketing
- The release notes for GNOME 3.10 are done, and now it is in the translation phase.
- Unfortunately, the magnifier's focus and caret tracking notes have been dropped because the lack of GUI.
- The accessibility bits has been consolidated with the rest of the notes, instead of having a separated section.
Miscellaneous Time
- (Nothing logged)
Action Items
- Joanie:
- Investigate the Zoom preferences GUI issue.
- Magdalen:
- File a bug about the ui.
- For GSoC code submission, take all of her submitted patches that were committed from gnome's bugzilla, tar them up, and sent the tarball to GSoC.
- Do the github today in case the ui is not fully working before Monday.
- Maybe add the code link to my github and say that it is not complete and upload the pictures for today and try to get a patch ready before Monday.
- Put the ui snaps on the wiki and make sure all work completed during the GSoC is properly referenced to make things easier.
- Finish a 'final GSoC' blog contribution to the planetfeed and she will base that around the ui work and include the things she learned from Joseph and Joanie recently, in that post so it explains about about the accessibility control center ui and how that should work.
Ongoing / Rolled-Over
- Joanie:
- Do some testing and update the Evolution a11y bugs.
- Juanjo:
- Take a look at the current a11y material in order to make an action plan.
- Piñeiro:
- Ping mousetweaks maintainers in relation with their plans towards Wayland.
- Send a email to accessibility-dev, just in case the Wayland Accessibility section needs to be filled.
- Compose a "what accessibility needs from Wayland, how to use it" email, ask for review, send to the Wayland Developer's list.
- Ping GNOME designers, so hopefully some default keybinding will be available for 3.8.
- Create some usability-configurability related bugs, using Bryen's mail as a starting point.