Meeting Summary

  • Meeting started by Piñeiro at 16:01 CET.
  • Meeting ended at 16:52 CET.
  • Participants (Lines Said):
    • Piñeiro - API (79)
    • Joanie - joanie (94)
    • Mario - msanchez (24)
    • Mike - mgorse (5)
  • Log

"Boston" Summit

  • Piñeiro is configuring his laptop in order to do the pre-event homework as agreed.
  • Talking with people led him to conclude that ubuntu was not the best to try wayland-gnome, so he is using f20 now.
  • Building all the stack right now, so it's a wip right now.
  • Joanie did much of her pre-event homework and is adding her findings to Accessibility/Hackfests/Montreal2013

  • Joanie also updated Wayland/Applications.

  • Orca was sometimes crashing upon launch with the Wayland backend. Joanie has since fixed that with a workaround, and will have it totally fixed by today's end (hopefully).
  • Accerciser reliably crashes upon launch with the Wayland backend. Joanie filed bug 709449 for that.

  • But accerciser has some other problems and has not be worked on in quite some time.
  • ACTION: Joanie will ping Javi about his plans w.r.t. his module.
  • LINK: https://wiki.gnome.org/Wayland/TryingIt

  • LINK: https://wiki.gnome.org/Accessibility/Hackfests/Montreal2013

GNOME 3.12 Planning

  • (Nothing infoed)

W3C Updates

  • (Nothing infoed)

Marketing

  • (Nothing infoed)

Miscellaneous Time

  • Joanie discovered that with pygobject, Wnck seems a bit broken. e.g. Wnck.Screen.get_default() in Wayland causes segfaults.
  • And in the non-wayland world wnck_screen_get_windows_stacked() returns an empty list.
  • Joanie suspects that Orca doesn't actually need the wnck code in question.
  • Joanie also suspects this might be why Accerciser is segfaulting on launch with the wayland backend.
  • ACTION: Joanie will investigate this for Accerciser and (hopefully) provide a patch so we can use Accerciser to test.
  • As an early idea of what we can do for webkitgtk hackfest, some ideas are appearing, such as:
    1. Review atk_text_get_text implementation.
    2. Look about moving atk tests to Webkit2 tests, as right now it only have one at-spi test related with the hierarchy
    3. Review the W3C ARIA mappings in order to check correctness and which needs new ATK API.

  • Disclaimer: all of the above are early ideas and subject to change.

Action Items

  • Joanie:
    • Ping Javi about his plans w.r.t. his module.
    • Investigate the Wayland-related breakage in Accerciser and (hopefully) provide a patch so we can use Accerciser to test.

Ongoing / Rolled-Over

  • Joanie:
    • Review current bugs about API additions and create new ones, with 3.12 target in mind.
    • Review the first public draft of ARIA 1.1 with specific attention to our current API.
    • 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:
    • Send a email to the -devel ml in relation with the informal agenda for the "Boston" Summit.
    • Send a feature proposal email to d-d-l, ideally before feature proposal period ends.
    • Ping Benjamin in order to know how much can be done on gtk+2
    • Compose a "what accessibility needs from Wayland, how to use it" email, ask for review, send to the Wayland Developer's list.

Accessibility/Minutes/20131010 (last edited 2013-10-17 12:52:25 by JoanmarieDiggs)