>From: Jonathon Blake <[EMAIL PROTECTED]> >Sent: Mar 15, 2007 6:20 PM >To: [email protected] >Subject: Re: [qa-dev] Nearly 1000 unconfirmed defects are open! > >Mike wrote: > >> general disquiet with the issue process, underlying which is a sense >> that the bug detection and correction process does not seem to set the >> right priorities, especially in terms of deadline for bugs in categories > >+1
Jonathan, I'm with both Maho and you. There are issues that have been open since 1.0.3 that look to have no solution, even today. Yes, they will take time to tackle, but if no one works on them they will NEVER be solved. > >> authority to set the target deadline for a small proportion of issues >> which are important to end users but not 'sexy' coding tasks for the > >I like the idea. Again, I agree. It may not be sexy to solve a problem that affects only a few users, but those users could bring hundreds to this project and might be the tipping point. Keep them away and thousands stay away. > >The issue is whether or not the functionality can be coded,and >included in a stable release within 6 months. > Are you capable of looking at code and finding issues? How about aiding in the Quality Assurance process? Sun cannot do it all (take a look at the 'smoketest' routines and you will see what I mean (not to knock the folks at Sun they were handed this mess)). We need folks who are willing to take on a 'slice of the pie' and look over at least one functional area with a critical eye. >Section 508 compliance issues would probably take more than 6 months >to implement. The a11y issues should be marked P-0 for both legal and >commercial reasons--- even though they will usually take more than a >year to correctly implement. [ I have a very basic, extremely >primitive a11y test suite. OOo fails every part of that test suite.] > Section 508 is just one small part. The government (US that is) could not sue us, we have no assets. However, this keeps away those users with less than full functional use of their bodies (and I always look upon them as heros, not to be pitied.) We need folks who are willing to work on a11y issues and make this program much more than it is. Right now, this program presents serious hurdles to those who have ability issues. JAWS does not work with OpenOffice.org and it should. I would like to see some of the speach to text programs be worked into OpenOffice.org. Sure this would increase its size, but maybe these could be additional packages, much like language pack. It appears that we have hit upon two separate issues: 1. The lack of concentrated triage for newly opened issues. 2. The lack of a11y support in OpenOffice.org. Can you assist with either of these issues? James McKenzie --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
