Hi, This is an issue I raised a while back and I keep coming across people who do not see TigerVNC as a viable alternative because of the lack of documentation. Just recently in this thread on xorg: http://lists.freedesktop.org/archives/xorg/2011-May/053094.html http://lists.freedesktop.org/archives/xorg/2011-May/053095.html http://lists.freedesktop.org/archives/xorg/2011-May/053098.html
The information exists out there, it's just not very accessible to newcomers and packagers. A simple basic wiki would probably do the job. IMO, here are some of the things that should be documented: * information on vnc.so usage (config, options) * build process. (the debian packages that I provide were built the "wrong way" - the only way I knew about then, not using the host's headers but using the build-xorg script) * MS Windows build * authentication mechanisms * tls libraries etc It doesn't have to be pretty or maintained in sync with every commit, but anything has got to be better than the void that is there now as this is clearly putting off some users. I do not have access to the servers hosting the tigervnc.org website, so there's not much I can do to help. (I considered setting up a repository copy just to be able to setup a trac instance against it, but decided it was just too much effort) Cheers Antoine ------------------------------------------------------------------------------ Simplify data backup and recovery for your virtual environment with vRanger. Installation's a snap, and flexible recovery options mean your data is safe, secure and there when you need it. Data protection magic? Nope - It's vRanger. Get your free trial download today. http://p.sf.net/sfu/quest-sfdev2dev _______________________________________________ Tigervnc-devel mailing list Tigervnc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tigervnc-devel
