Contributing Changes

[Brandon Ibach]

Quoting Will Dean <will.dean "at" industrial.demon.co.uk>:
> I think you'll find that if you fix bugs or make other improvements, 
> they'll happily incorporate them.  This has been my experience on the 
> Windows side, anyway.  (Thanks James!)
> 
> I suspect they're all too busy on other stuff to set up the framework 
> necessary for all and sundry to check code in, if that's what you meant by 
> "development community".  They probably can't afford enough staff storming 
> out in a huff to make it really Mozilla-like, either.
> 
------
> I've successfully done this by mailing vnc "at" uk.research.att.com with 
> information of the changes I've made.  If they have time/are interested, I 
> expect they'll contact you.  I know that the guy responsible for the WinVNC 
> software is very busy elsewhere at the moment, so you might need to hang on 
> a bit.
> 
> Or you could check the license and decide if you want to release your own 
> version.
> 
   Don't get me wrong.  I certainly don't want to get down on the
people at AT&T.  They've given us a great set of tools, and are
clearly doing their best to improve them as their time allows.  The
problem, as I see it, is that there are a number of people, such as
myself, who want to contribute to improving VNC, but need some
support, and the AT&T people just don't have the time.
   For instance, I'd like to see another mailing list, dedicated to
development.  This way, regular users won't have to wade through
technical discussions, and developers won't have their discussions
lost in the stream of other messages.
   Also, I have a few ideas for improvements to WinVNC, and I'm even
willing to take a crack at coding them.  The problem is, I'm *not* a
Windows developer, so it'll be enough of a challenge for me to code
these, and then I won't even have the ability to compile them and see
if they work, much less debug them.  I'll need to rely on someone else
to help me with this process.
   I guess what I'd hope for from AT&T would be just a minimal effort
to coordinate things a bit.  I'd be willing to set up a mailing list
on my server for the development list, if they'd like.  I imagine we
might be able to find someone to host a CVS repository, if we felt
that was needed, as well.  Perhaps the most important thing, however,
would be someone to arbitrate the big decisions such as when new
versions will be released, and what goes into them.  In other words,
we need someone to do for VNC what Linus does for Linux, and I would
think that AT&T would have the first right to that role.

-Brandon :)

---------------------------------------------------------------------
To unsubscribe, send a message with the line: unsubscribe vnc-list
to majordomo "at" uk.research.att.com
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------