Here are the meeting minutes from the board call this past Monday. As always you can find the minutes in the wiki (https://en.opensuse.org/openSUSE:Board_meeting#Meeting_2013-03-25) and if you have questions, or concerns you may raise them on this list or contact the board directly on the board list.
Regrads, Your openSUSE Board
Board Meeting 2013-25-03
Present: Richard, Andrew, Robert
Excused: Raymond - Company Meeting Vincent - Customer call Will - MIA
1.) Review Action Items - No board report :( - CLT issues followed up
2.) Face to Face Meeting Agenda - Items collected, ready to post first draft of the agenda to the wiki
3.) Accessibility issue - The proposal raised on the board list is to add a new category to our Bugzilla to clearly mark accessibility issues as such.
There are two main concerns, one is that this is a technical issue and thus the board should keep its fingers out of this issue. The second concern is that creating a specific category may make it easier for people to "pass the buck" by expecting someone in the non existent accessibility team to fix the problem.
Having a separate category for accessibility (a11y) on the other hand will send a clear message that we as the openSUSE community care about people with disabilities. While we have no specific resources to address a11y issues it is important to acknowledge that an a11y issues can easily make the system unusable for a handicapped person.
While adding to the bug category list is definitely a technical issue, the a11y topic has a very large community component and thus the board thinks it is appropriate to act in this area. We can certainly not dictate any action, however a message will be sent to the -factory mailing list asking for consideration of the topic by the developers.
The argument was made that a11y bugs should fit into the categories we already have and that we might easier fall into a "pass the buck" situation with a new category. It is the consensus that we should be able to address the "pass the buck" issue with a policy/procedure. As far as using existing categories is concerned the problem might be that we get into a priority flip flop situation if we do not have a separate category. A person with a disability might mark a bug as Critical, but a developer not fully understanding the consequences might relabel it as category 2 or 3. Having an a11y category would address such priority flip/flop issues.
The board will, after additional discussion on the board list, send a proposal to the -factory list for consideration by the developer community. The proposal will recommend the addition of an a11y category to Bugzilla and a proposal on how to handle the bugs.