Mike wrote:
the cause may be partly a process issue.
I just looked at roughly twenty issues from the first page. Two of them are about to be closed,because the problem has been fixed. Roughly ten of them require legal man to walk thru them. Roughly five of them are users who don't know how to use OOo. The rest require testing on a couple of different configurations of OOo.
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
current feeling is that 99% of what I have and might in the future contribute would be a waste of my time, contributing primarily to a
Frustration of that type has caused quasi forks of OOo.
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. The issue is whether or not the functionality can be coded,and included in a stable release within 6 months. 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.] xan jonathon --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
