Meeting Summary

Concluding which project(s) will be proposed for use of the FoG funds

We talked about the proposed projects and use of the FoG funds at the last meeting.
The tentative conclusion was well accepted by the people at the meeting.
We mentioned that FoG was the main topic on previous meeting, and this one, on the list. No feedback received.
Should we assume that as a implicit approval from the a11y team, and just write the proposal and send to the board?
During the last meeting, Joanie's proposal included two "to be refined" statements.
Joanie thinks we should either do the refining or remove the "to be refined."
Joanie also thinks we should identify who will draft these proposals.
Joanie proposes that Joseph draft the caret and focus tracking one.
Joanie is willing to draft the Document one.
It is anticipated that Bastien will be contacting us regarding this as he is the one who received this task that was on Karen Sandler's plate. (Karen is on maternity leave.)
There is a small, but unexpected, chance that Bastien will reject this idea.
ACTION: Joanie was already planning to report this back to the Board at the next meeting.
After the next Board meeting (see previous action) we should have some idea regarding what the "deadline" really is.
Therefore, it is suggested that we have our ideas fleshed out sufficiently that we can answer Bastien/Board questions should they occur.
But not necessarily spend significant time on writing them perfectly now.
Board meetings are every two weeks -- just now moved to Tuesdays.
The next Board meeting is on 18 Sept at 14:00 UTC.

Monday, 17 September, is code freeze.
For the ones not used to that: that means no code change until final release, unless something really important (crashes, etc) appears.
When testing, Piñeiro didn't find anything relevant.
This Tuesday some people were talking on #gnome-os about leaks related to a11y, e.g. 683317
But after some tests, Jon McCan found that there are more leaks in other parts (specifically gtk css support).
So a11y will not take the blame.
Another concern mentioned is about performance loss and memory.
Jon was asking for data.
Piñeiro mentioned that we performed some assessments last year, and that we did a lot of work to ensure that without AT listening the system will not be affected. Where "we" is mostly mgorse (kudos). Anyway, some people would be "more happy" with more data.
Piñeiro did some more tests and found that accessible objects are still created even when no AT is listening, something that he thought was not happening. Probably we could change that, but not *now*.
Piñeiro will do some more tests, and check if "some data" could be achieved.
Piñeiro will be grateful if others do the same: specifically testing all of the desktop and see if there are some kind of crash of freeze.
In order to make "user oriented tests" there are some ISOs with the latest releases.
LINK: http://napoleon.acc.umu.se/pub/GNOME/misc/testing/GNOME-3.5.91-LiveUSB.iso
liveUSB here: https://mail.gnome.org/archives/release-team/2012-September/msg00066.html

Juanjo has been working on the a11y section for the release notes.
This time the notes are short, but Juanjo thinks we have some good features for the release.
Juanjo encourages people to review the notes and provide constructive feedback.

And from the academic front, Western New England University and colleagues from Drexel and NCC have recieved an NSF grant.
The grant is to provide funding to get faculty members to workshops to learn about FOSS and humanitarian FOSS in particular.
The work is still ramping up so look for more announcements in the coming months.
And if you know of any faculty who want some help getting started, send them to Heidi: ellis@wne.edu.
Joanie is still interested in seeing if we could do some of her "outreach program for professors" work in partnership with this new program.
Heidi thinks this is a really good idea and welcomes all input.

Joanie:
- Mention to the Board the current status of the team's determining how to use the FoG funds.

Team members:
- Look over Juanjo's draft about how to improve accessibility by promoting a11y to developers and designers.
Joanie
- (with Piñeiro) touch base to see if that evince a11y could be moved forward
- Draft the final Q2 report for the team and get Piñeiro's review.
- Do a full evaluation of the accessibility breakage in Evolution 3.6 and file bugs accordingly.
Juanjo:
- Take a look at the current a11y material in order to make an action plan.
Piñeiro:
- (with Joanie) touch base to see if that evince a11y could be moved forward
- List some of "touch-friendly" accessibility features (ie: possibility to define a gesture to control a11y features like zoom), and send it to design team(?)
- Send a mail to bastien to know 1. if he has specific features for the bridge 2. if he plans to work on that.
- Update the AtkObject:children-changed documentation, as this could be also used on ATK implementors.