Features/TigerVNC

From FedoraProject

< Features(Difference between revisions)
Jump to: navigation, search
(need email and more detailed test plan--see hidden comments for suggestions)
Line 1: Line 1:
 
= Replace RealVNC by TightVNC =
 
= Replace RealVNC by TightVNC =
 
 
  
 
== Summary ==
 
== Summary ==
Line 8: Line 6:
 
== Owner ==
 
== Owner ==
 
* Name: AdamTkac
 
* Name: AdamTkac
 +
* '''FIXME'''--please add your email address so you can be notified about the meeting where FESCo will discuss your feature
 +
  
 
== Current status ==
 
== Current status ==
Line 27: Line 27:
 
== Test Plan ==
 
== Test Plan ==
 
* Push TightVNC based vnc to rawhide as soon as possible and users will test it
 
* Push TightVNC based vnc to rawhide as soon as possible and users will test it
 +
 +
<!-- This does not need to be a full-fledged document.  Describe the dimensions of tests that this feature is expected to pass when it is done.  If it needs to be tested with different hardware or software configurations, indicate them.  The QA team will turn this information into a more complete test plan.  The more specific you can be, the better the final test plan will be.
 +
 +
Remember that you are writing this test plan for interested testers to use to check out your feature - documenting what you do for testing is OK, but it's much better to document what *I* can do to test your feature.
 +
 +
A good Test Plan should answer these four questions:
 +
 +
0. What special hardware / data / etc. is needed (if any)?
 +
1. How do I prepare my system to test this feature? What packages
 +
need to be installed, config files edited, etc.?
 +
2. What specific actions do I perform to check that the feature is
 +
working like it's supposed to?
 +
3. What are the expected results of those actions?
 +
 +
-->
  
 
== User Experience ==
 
== User Experience ==
Line 37: Line 52:
  
 
== Contingency Plan ==
 
== Contingency Plan ==
Use Fedora 10 codebase
+
* Use Fedora 10 codebase
  
 
== Documentation ==
 
== Documentation ==
None needed
+
* '''FIXME'''
  
 
== Release Notes ==
 
== Release Notes ==
Not needed
+
* '''FIXME'''
  
 
== Comments and Discussion ==
 
== Comments and Discussion ==
Line 52: Line 67:
 
----
 
----
  
[[Category:FeatureReadyForWrangler]]
+
[[Category:FeaturePageIncomplete]]
 +
<!-- When your feature page is completed and ready for review -->
 +
<!-- remove Category:FeaturePageIncomplete and change it to Category:FeatureReadyForWrangler -->
 +
<!-- After review, the feature wrangler will move your page to Category:FeatureReadyForFesco... if it still needs more work it will move back to Category:FeaturePageIncomplete-->
 +
<!-- A pretty picture of the page category usage is at: https://fedoraproject.org/wiki/Features/Policy/Process -->

Revision as of 17:20, 3 December 2008

Contents

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
  • FIXME--please add your email address so you can be notified about the meeting where FESCo will discuss your feature


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

  • FIXME

Release Notes

  • FIXME

Comments and Discussion

See Talk:Features/TightVNC