Re: Orca's external dependencies

On 04/21/2011 03:24 PM, Super Bisquit wrote:
Since Orca is for the visually impaired, have you asked a blind person
to test out gnome3?

We didn't asked specifically to a blind person to test out gnome3, but in general, we asked any person interested in accessibility to test GNOME 3, provide feedback etc.

GNOME Accessibility team is working on an accessibility testing distro:

The purpose of this distro is test the accessibility support on GNOME 3, and in the same way, provide updated packages in order to solve the issues that we found on this test.

Just a simple yes or no and not an explanation.
You can see the explanation that you didn't asked in my previous paragraph. As you wanted a simple yes or no: no.

I work with the Vinux project and would like to pass this information to them.

Please, if you do that, pass them the link to the testing distro. Any feedback is welcome.

On 4/21/11, Frederic Peters<fpeters gnome org>  wrote:
Hi Joanmarie,

Looking at the 2.91 External Dependencies list [1], I see neither Speech
Dispatcher nor OpenTTS. OpenTTS got approved for the prior cycle. [2]
But they've since re-merged (unforked?) with Speech Dispatcher. So....
Do I need to propose Speech Dispatcher as an external dependency needed
by Orca, or can I assume that because OpenTTS got blessed, Speech
Dispatcher inherits that blessing and simply needs to be added to future
lists of dependencies?

Similarly, Orca has always depended upon BRLTTY [3] for refreshable
braille. Thus I was surprised to discover that BRLTTY was not listed as
a dependency. Distros seem to know to include it, but should BRLTTY be
something officially made an external dependency of GNOME?

Finally, if the answer to my question about BRLTTY is "Yes, it should be
proposed/considered" by the Release Team, then I'd like to toss out one
more for consideration: Liblouis. [4] Liblouis provides Orca users with
the braille translation tables needed for contracted/"grade 2" braille.
We are moving away of the idea of approving/rejecting individual
modules and considering the features we want in GNOME. In that
direction we'd say that whatever is needed for Orca to do its work
is ok. Of course this calls for some common sense, to keep some
coherence in our stack, but in the specific case of Orca we are not
adding liblouis to our development platform, it just happens to be a
library that is used to provide Orca users an important feature.

But we want to have some guidelines, they are still to be discussed,
but the current proposal for modules developed outside of GNOME, and
with no consideration for our schedule, to require modules to depend
on released versions only.

Does this answer your question clearly enough?

desktop-devel-list mailing list
desktop-devel-list gnome org

desktop-devel-list mailing list
desktop-devel-list gnome org


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]