From Fedora Project Wiki
< Features
m (Features/TightVNC moved to Features/TigerVNC: TightVNC has been forked and fork is called TigerVNC) |
No edit summary |
||
| Line 1: | Line 1: | ||
= Replace RealVNC by | = Replace RealVNC by TigerVNC = | ||
== Summary == | == Summary == | ||
Make | Make TigerVNC the default VNC client in Fedora. | ||
There was no update from RealVNC upstream since May 18 2006 and upstream is focused on their enterprise non-open vnc. Trunk | There was no update from RealVNC upstream since May 18 2006 and upstream is focused on their enterprise non-open vnc. Trunk TigerVNC 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 14: | Line 14: | ||
* Last updated: 2009-01-21 | * Last updated: 2009-01-21 | ||
* Percentage of completion: 95% | * Percentage of completion: 95% | ||
== Detailed Description == | == Detailed Description == | ||
TigerVNC 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.6 and supports more extensions. Fedora changes have to be carefully merged to TigerVNC upstream and then we will use it as default Fedora vnc system. | |||
== Benefit to Fedora == | == Benefit to Fedora == | ||
| Line 23: | Line 22: | ||
== Scope == | == Scope == | ||
Merge Fedora changes to upstream and make | Merge Fedora changes to upstream and make TigerVNC ready for Fedora | ||
== Test Plan == | == Test Plan == | ||
| Line 34: | Line 33: | ||
* Better encodings save bandwidth and processor time | * Better encodings save bandwidth and processor time | ||
* Viewer internationalization | * Viewer internationalization | ||
* IPv6 support | * IPv6 support in viewer | ||
== Dependencies == | == Dependencies == | ||
Anaconda has to use | Anaconda has to use tigervnc package instead vnc | ||
== Contingency Plan == | == Contingency Plan == | ||
| Line 43: | Line 42: | ||
== Documentation == | == Documentation == | ||
* http://www. | * http://www.tigervnc.com/ | ||
== Release Notes == | == Release Notes == | ||
* | * TigerVNC is used as default VNC project. Package names were changed to tigervnc, tigervnc-server and tigervnc-server-module. Binary names are same as in previous version, libvnc.so module has been moved to tigervnc-server-module subpackage. Otherwise there should be no difference | ||
== Comments and Discussion == | == Comments and Discussion == | ||
See [[Talk:Features/ | See [[Talk:Features/TigerVNC]] | ||
Revision as of 12:15, 2 March 2009
Replace RealVNC by TigerVNC
Summary
Make TigerVNC the default VNC client in Fedora.
There was no update from RealVNC upstream since May 18 2006 and upstream is focused on their enterprise non-open vnc. Trunk TigerVNC 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: Adam Tkac
Current status
- Targeted release: Fedora 11
- Last updated: 2009-01-21
- Percentage of completion: 95%
Detailed Description
TigerVNC 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.6 and supports more extensions. Fedora changes have to be carefully merged to TigerVNC 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 TigerVNC ready for Fedora
Test Plan
- Check that libvnc.so module to Xorg works fine
- Check that vnc installation works as expected
- Check that viewer works fine when you connect to Xvnc and to different servers (vino)
- Check that Xvnc works with other viewers (vinagre)
User Experience
- Better encodings save bandwidth and processor time
- Viewer internationalization
- IPv6 support in viewer
Dependencies
Anaconda has to use tigervnc package instead vnc
Contingency Plan
- Use Fedora 10 codebase
Documentation
Release Notes
- TigerVNC is used as default VNC project. Package names were changed to tigervnc, tigervnc-server and tigervnc-server-module. Binary names are same as in previous version, libvnc.so module has been moved to tigervnc-server-module subpackage. Otherwise there should be no difference
Comments and Discussion