Re: [orca-list] Orca readmap?

[Joanmarie Diggs <jdiggs igalia com>]

New features don't need to be on the roadmap as far as I am concerned.
For instance, this release cycle I'm going to do the text attribute
presentation when reading even though it's not listed in the roadmap.
The roadmap is the big picture.

That said, there are periodically features that a few people want, but
are not widely wanted and/or are not something one would consider core
screen reader functionality. Those should be plugins which can then be
maintained outside of Orca. For that sort of thing we need to implement
libpeas support in Orca.

--joanie

On 11/05/2015 08:55 PM, MENGUAL Jean-Philippe wrote:
> Thanks. Very interesting. I see there are few new features, why? Is it a
> lack of time issue? Is it because any new feature/setting would be a
> problem as one part of roadmap is moving the settings way on Orca? In
> other words, could we usefully develop new settings or features; or
> rather waiting for the end of migration of settings organization
> (gsettings, etc)?
>
> Regards,
>
> Le 06/11/2015 02:11, Joanmarie Diggs a écrit :
> > https://wiki.gnome.org/Projects/Orca/Roadmap
> >
> > Patches are welcome and will be reviewed.
> > --joanie
> >
> > On 11/05/2015 07:58 PM, MENGUAL Jean-Philippe wrote:
> > > Hi,
> > >
> > > 1. Does an Orca roadmap exist? Or a guideline about Orca dev philosophy
> > > (what are prio!ities, do you privilege bugfixes or dev of new features,
> > > or compatibility with toolkits, etc)?
> > >
> > > 2. I'm wondering if, after discuss, you would accept if we would add new
> > > features to Orca (e.g. capability to choose more widely the Orca key),
> > > while you fix bugs and make Orca compatible with the hard Gecko, other
> > > toolkits, etc. Would such patches be accepted? How are handled such
> > > contributions if nhere are many?
> > >
> > > The interest, I think, is:
> > > - we can develop on a "simple" language, e.g. Python, making Orca
> > > improve (being aware that other things are involved such as
> > > speech-dispatcher and xbrlapi);
> > > - you can focus on more difficult tasks which require more experience
> > > with Orca code, and require to know the role of at-spi, toolkit, etc. to
> > > know what to do, what to ask to apps, etc.
> > >
> > > Note: new features are discussed here, to know their interest, the
> > > interest Orca can to handle itself them, and if it could be a hard work.
> > > We won't develop, patch without pre-discuss.
> > >
> > > Thanks for your answers.