Hi all, it was some concern why TightVNC feature has been renamed to TigerVNC one minute before beta freeze. Let me try explain background. In Fedora 10 we have vnc based on RealVNC source but upstream doesn't put any effort to accept patches which we have so I decided replace RealVNC by TightVNC in F11. Current TightVNC "trunk", which was supposed to be our F11 vnc, uses same codebase as RealVNC. TightVNC adds Tight extension and some other useful features. I joined to TightVNC upstream about one year ago and successfully ported all Fedora changes to upstream. Unfortunately TightVNC lead developer wasn't able to create any plan for the next release of UN*X version. All UN*X developers asked him what features will be in next version, when the next version will be released etc. It was continual development without any milestones which was unacceptable for some developers thus we created fork called TigerVNC. TigerVNC is new project, it exists about two weeks. All active TightVNC UN*X developers left TightVNC and joined TigerVNC. Also lead developer of TurboVNC (VNC which is focussed on performance, 3D gaming etc) joined us so I think this project will have better future than TightVNC. You can read "official" statement from upstream - https://sourceforge.net/mailarchive/message.php?msg_name=alpine.LFD.2.00.0902271116020.25749%40maggie.lkpg.cendio.se. Due reasons written above I decided to switch to TigerVNC ASAP because I think it will be better than TightVNC. I hope I threw enough light on this topic. Regards, Adam -- Adam Tkac, Red Hat, Inc. -- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
