Re: [orca-list] Have we chosen the good way to contribute?

[kendell clark <coffeekingms gmail com>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

hi
This is something I can get behind 100 percent. I'm glad someone
succeedded where I failed, because I've been trying to do this for
ages, and gotten little interest, if not outright disinterest. If we
don't have an irc channel, we need to make one, assuming I can join
the team, because I've been wanting linux accessibility to become
something that's vastly easier to improve than it currently is. In
fact, I can create one on freenode, probably #hypra, if I can figure
out how to change the topic. I doubt joanie has had a chance to look
at this pull request, if she has even seen it, she's probably filed it
away somewhere. IMO we need more python and c programmers to study
orca and the layors beneath it so she doesn't have to manage
*everything*. I'll gladly join in, and I suspect some of the members
of the sonar team will as well. Phew, what a relief
Thanks
Kendell clark
 MENGUAL Jean-Philippe wrote:
> Hi,
>
> In order to improve, but especially maintain without regressions,
> the GNU/Linux accessibility, I am building a team who can work
> fulltime about this. We work in the communities, especially Debian,
> given their a11y level. But of course, we are aware of the
> importance of supporting upstream communities.
>
> While we promote a11y in free software world, helping projects to
> be or stay or become accessible, such as MATE, we try giving to
> Orca new useful features so that it provides to users with similar
> capabilities as for NVDA. It's also a way to work without
> interferring with Joanie's dev, working on modularity and with her
> control.
>
> That's why I reported to Debian bug: 
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757635
>
> ksamak, member of our team, provides this fix via a pull request 2 
> months ago: https://github.com/GNOME/orca/pull/1
>
> Indeed, we want to give our developments to the community. Its for
> us easier to be involved in projects instead of maintaining our own
> repo, and community is a quality assurance to make the free
> software we want to improve clean.
>
> Was this pull request studied/seen? What is the status we can
> consider it (not seen, refused, in progress)? Will be in next Orca
> release? Does this way of working suit to orca team and gnome-a11y
> team? Would other ways be better?
>
> FYI, our team will be named Hypra. Due to development and next to
> it, this project expect to interface between newbie users (don't
> know English and express bugs, wishes, etc), to report to upstream
> and distros, and helping improving the general quality of our
> tools.
>
>
>
> Regards,
>
>
> _______________________________________________ orca-list mailing
> list orca-list gnome org 
> https://mail.gnome.org/mailman/listinfo/orca-list Visit
> http://live.gnome.org/Orca for more information on Orca. The manual
> is at 
> http://library.gnome.org/users/gnome-access-guide/nightly/ats-2.html
The FAQ is at http://live.gnome.org/Orca/FrequentlyAskedQuestions
> Log bugs and feature requests at http://bugzilla.gnome.org Find out
> how to help at http://live.gnome.org/Orca/HowCanIHelp
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBCgAGBQJUtJyjAAoJEGYgJ5/kqBTdaVEP/R8I0/yA/X5wN0eZyOojXCh7
cEOnWRA6krIvTcEWpR9qqCop0WqI7MKsRu1R0ETRnpolxZRUe0bfXiGGBaj95AWY
/x5Wl8+Q4NiWHiu05SDr1jPtPoXPLUKhDmTTxgVyCvTKDDQ0zYgDc2C+4sWVFBy8
iiQsbyLaSJvabL92Es9onKQ0FgP9et0nW8uubCRcI33UqxqpDGRDOiXAFgOtsgNE
3bSj0delo7E1RU5bHmjYlsATNctUHsiO2+/7EKWc/bezj+CuFdR73N7y2ogSEIHR
pVeSkrAarG7vQFEj5GcK/SJmuUAFMn5XRNeWFK5igoQrmgc1Mk8p0n76E09h1Ujg
/vX0cM3MtBxzbosrBBspZg4gS9A3N7bCsSytZciwIH+XK1KvOwEzjKjeNiOYi5AT
fGfQ3TVGyTcVPTeUgSqVcpU90nsKWg38gurrbKq8V6cOBGS7NbJGr0nUocC67Pzc
6vxKGvA9B5RVBQKh0wBVt0qD7IKSWYUTBUJv2CX1GoWNvGtRZOmdeBglu5YFUjV5
bfvR1mlCsa7E69JV4yDBumjwyTht4npODKtMmW2DHk8kIJEn+0VGGnk7PoQxZnDt
lV/BAGuZkIJk+8r4VKwCSkIR1FcXH5gLMFuHisFWgRwRRNP6/Z6E3j2V2FvlnllT
7iSpNFvKw94VOXxxl00H
=uajg
-----END PGP SIGNATURE-----