< Features
No edit summary |
No edit summary |
||
| Line 4: | Line 4: | ||
== Summary == | == Summary == | ||
There was no update from RealVNC upstream since May 18 2006 and upstream is focused on their enterprise non-open vnc. Trunk TightVNC is RealVNC fork with many improvements/bugfixes so it makes sense | There was no update from RealVNC upstream since May 18 2006 and upstream is focused on their enterprise non-open vnc. Trunk TightVNC is RealVNC fork with many improvements/bugfixes so it makes sense to use it. Main problem is that current Fedora vnc has also many changes so patches have to be merged. | ||
== Owner == | == Owner == | ||
| Line 17: | Line 17: | ||
== Detailed Description == | == Detailed Description == | ||
TightVNC has successfully implemented "Tight" protocol enhancements which save bandwidth and are generally better than the original RealVNC's RFB 3.8 protocol. On the other hand Fedora vnc has by far a much better server (Xvnc) which is based on X 1.5 and supports more extensions | TightVNC has successfully implemented "Tight" protocol enhancements which save bandwidth and are generally better than the original RealVNC's RFB 3.8 protocol. On the other hand Fedora vnc has by far a much better server (Xvnc) which is based on X 1.5 and supports more extensions. Fedora changes have to be carefully merged to TightVNC upstream and then we will use it as default Fedora vnc system. | ||
== Benefit to Fedora == | == Benefit to Fedora == | ||
| Line 23: | Line 23: | ||
== Scope == | == Scope == | ||
Merge Fedora changes to upstream and make TightVNC ready for Fedora | |||
== Test Plan == | == Test Plan == | ||
| Line 52: | Line 52: | ||
---- | ---- | ||
[[Category: | [[Category:FeatureReadyForWrangler]] | ||
Revision as of 09:54, 2 December 2008
Replace RealVNC by TightVNC
Summary
There was no update from RealVNC upstream since May 18 2006 and upstream is focused on their enterprise non-open vnc. Trunk TightVNC is RealVNC fork with many improvements/bugfixes so it makes sense to use it. Main problem is that current Fedora vnc has also many changes so patches have to be merged.
Owner
- Name: AdamTkac
Current status
- Targeted release: Fedora 11
- Last updated: 2008-10-17
- Percentage of completion: 80%
- tightvnc package hit F11 CVS branch
Detailed Description
TightVNC has successfully implemented "Tight" protocol enhancements which save bandwidth and are generally better than the original RealVNC's RFB 3.8 protocol. On the other hand Fedora vnc has by far a much better server (Xvnc) which is based on X 1.5 and supports more extensions. Fedora changes have to be carefully merged to TightVNC upstream and then we will use it as default Fedora vnc system.
Benefit to Fedora
vnc will have more features and will get benefit from upstream development instead of the current one man show in Fedora CVS. Overall quality should be better.
Scope
Merge Fedora changes to upstream and make TightVNC ready for Fedora
Test Plan
- Push TightVNC based vnc to rawhide as soon as possible and users will test it
User Experience
- Better encodings save bandwidth and processor time
- Improved keyboard handling when server and viewer uses different keyboards
- Viewer internationalization
Dependencies
Anaconda has to use tightvnc package instead vnc
Contingency Plan
Use Fedora 10 codebase
Documentation
None needed
Release Notes
Not needed
Comments and Discussion