[Opentts-dev] Speech-dispatcher, OpenTTS, and the outcome of my discussion with Brailcom staff.

[Trevor Saunders]

Hi,

I'd like to make a few comments and raise a few concerns.

On Wed, Jul 28, 2010 at 11:39:27PM +0200, Tomas Cerha wrote:
> Hello,
> 
> I will react to what is relevant for me.  My colleagues will comment on
> other things soon.
> 
> On 28.7.2010 13:19, Luke Yelavich wrote:
> > The contribution agreement form hasn't been put up yet, because there has
> > not yet been anybody who has approached Brailcom to discuss things. If
> enough
> > people wish to become regular contributors, Brailcom will update the
> site with
> > appropriate forms to be filled etc.
> 
> Where "enough" is actually >= 1. ;-)  It would probably have been there
> already anyway if it was not the time of vacations and conferences.

While I'm not quiet sure what you mean "regular contributor" I'm not
sure I like having to fill out a form to contribute.  I don't see how
it helps anyone to make people fill out a form before they send
patches.

> > I did ask them about getting git commits to be posted to a mailing list,
> > and I think they said they would look into it.
> 
> Yes, Boris has just created the new mailing list.  Please, see
> http://lists.freebsoft.org/cgi-bin/mailman/listinfo/speechd-commits for
> subscription information.  The speechd git is set to send notifications
> automatically to this list.

ok, sounds good, I noticed that some of the commit messages in the
speechd tree didn't follow the standard format for git commit
messages, sometimes weren't very descriptive, and had some rather
obvious spelling errors.  I understand that english may not be your
native language, it is mine, but I'm a terrible speller anyway :-),
but would you guys mind being a little better about this? it should
help everyone I would think, if nothing else it means git shortlog
gives you something useful.

> > As for bug tracking et al, I didn't ask them about that, as I forgot,
> > but I am sure they could ensure that the bug tracker is easier to
> > find, and is usable and useful for filing and tracking bugs.
> 
> We are going to use the bug tracking system which is integrated with our
> internal information system.  This would be very practical for us and we
> hope that it will not cause any inconvenience to the community.  We
> actually believe that it will be an advantage as its interface is
> heavily optimized for accessibility (based on our accessible web
> application development platform).

Ok, I'm not sure what the idea or reason for a special accessible web
developement platform is but anyway this sounds good.  What are the
chances bugs could be minipulated with email?  This is a useful
feature of a few bug trackers I know of.

> > As far as I understand it, their entire site is wiki-like, so having
> > a wiki area probably wouldn't be to much of a problem either.
> 
> No, that should not be a problem too.  Just let us bring these tools one
> step at a time.

ok, again sounds good.

> Thanks again to Luke for his pragmatic approach.  I believe that is the
> users who is going to benefit.

ok, I hope users do benefit my main concern is this.  Supose Braille
Comm doesn't have money  to work on speech dispatcher etc, will
mechanisms be put in place to allow the comunity to move forward with
developement while Braille Comm waits for funding, or will the
community be stuck with the current status until Braille Comm gets
more money like happened previously?

a few other random things.
1. Personally I tend to prefer kr / kernel style to gnu,but whatever,
however I think autoformating with Lindent or something similar is a
good policy.
2. unless someone has an objection, I can't imagine why they would
though, I think setting up a irc channel to discuss developement work,
and help work out issues with users is very useful.  What I mean is
that while email is good, sometimes something more real time is
better.
3. it would be nice if there was a little bit more discussion on the
speechd list about what developement was happening, and what was about
to get committed, however this is everyones responsibility.

best
Trev

> 
> Best regards, Tomas
> _______________________________________________
> Opentts-dev mailing list
> Opentts-dev at lists.opentts.org
> http://lists.opentts.org/listinfo.cgi/opentts-dev-opentts.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: 
<http://lists.freebsoft.org/pipermail/speechd/attachments/20100729/deaa111e/attachment.pgp>