[Opentts-dev] My analysis of things

[Steve Holmes]

In addition to how the opentts developers do, the Orca team uses
Bugzilla to track bugs and patches are accordingly attached to said
bugs.  After that, the review concept is similar, but less formal than
opentts developers' process.  I would hesitate to give too many people
update access to formal git without compromizing the integerity.  Not
that contributers are anything less but that way one can review
changes before going in.  Not sure if write access can be given to a
git repo for proposed branches but not master? I know less about git
than a lot of people out there.

My other thought concerns funding.  We just felt the impacts of Oracle
pulling financial support from gnome accessibility through the action
of eliminating Willy Walker's job at Sun.  In brief, Will headed up
the gnome accessibility office and accordingly, lead development of
Orca.  Since all that was done away with,, Joanmarie Diggs has assumed
the lead role for Orca development.  She is a volunteer; no funding
for her time.  I understand there has been some other financial
support making it into Orca's development in other areas but all and
all, Orca is now basically a volunteer supported project.  Fortunately
for all of us, that project has not really suffered as much as some
feared it would.  Government funding in this day of world-wide budget
cuts and massive debts, has got to be sketchy at best.  You may have
funding this year or next but after that, who knows? You can only take
it whenyou can and make the most of the money when it comes but be
able to carry on with it dries up.  So far, when funds dry up, speech
dispatcher has tended to suffer a lack of timely support.  A different
model is needed if speech dispatcher is to be a solid and viable
project with timely responses to changes in the world in which it
lives.

On Wed, Jun 09, 2010 at 09:04:29PM -0500, Chris Brannon wrote:
> Nolan Darilek wrote:
> > I'm not on anyone's "side" in this. I just want to see a standardized,
> > stable speech solution in the GNOME3 timeframe. Just who produces that
> > is immaterial to me.
> 
> Your analysis is very well-written.
> Hopefully, we all want the same thing that you want.
> 
> > First, set up infrastructure such that contributors have write access to
> > the standard git repository.
> 
> Exactly.  Even if contributors do not have write access, we at least need
> some sort of process in place, so we know that patches are being
> reviewed by the official developers.
> In other words, they shouldn't languish in an unofficial repository for
> months at a time.
> 
> > In closing, I'd recommend this free book:
> > 
> > http://producingoss.com/
> 
> It's on my "must read" list.  Thanks for the pointer.
> 
> -- Chris
> _______________________________________________
> Opentts-dev mailing list
> Opentts-dev at lists.opentts.org
> http://lists.opentts.org/listinfo.cgi/opentts-dev-opentts.org