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

[MENGUAL Jean-Philippe <texou actux eu org>]

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,