Changes/X2Go

From FedoraProject

< Changes(Difference between revisions)
Jump to: navigation, search
(Scope)
Line 6: Line 6:
 
== Owner ==
 
== Owner ==
 
* Name: [[User:orion| Orion Poplawski]]
 
* Name: [[User:orion| Orion Poplawski]]
 
 
* Email: orion at nwra dot com
 
* Email: orion at nwra dot com
 
* IRC: orionp
 
* IRC: orionp
 +
* Release notes owner: <To be assigned by docs team> <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> -->
 +
<!--- UNCOMMENT only for Changes with assigned Shepherd (by FESCo)
 +
* FESCo shepherd: [[User:FASAccountName| Shehperd name]] <email address>
 +
-->
  
 
== Current status ==
 
== Current status ==
 
* Targeted release: [[Releases/20 | Fedora 20 ]]  
 
* Targeted release: [[Releases/20 | Fedora 20 ]]  
 
* Last updated: 2013-7-15
 
* Last updated: 2013-7-15
* Percentage of completion: 10%
+
<!-- After the change proposal is accepted by FESCo, tracking bug is created in Bugzilla and linked to this page
 
+
Bugzilla states meaning as usual:
 +
NEW -> change proposal is submitted and announced
 +
ASSIGNED -> accepted by FESCo with on going development
 +
MODIFIED -> change is substantially done and testable
 +
ON_QA -> change is code completed and could be tested in the Beta release (optionally by QA)
 +
CLOSED as NEXTRELEASE -> change is completed and verified and will be delivered in next release under development
 +
-->
 +
* Tracker bug: <will be assigned by the Wrangler>
 
== Detailed Description ==
 
== Detailed Description ==
 
<!-- Expand on the summary, if appropriate.  A couple sentences suffices to explain the goal, but the more details you can provide the better. -->
 
<!-- Expand on the summary, if appropriate.  A couple sentences suffices to explain the goal, but the more details you can provide the better. -->
Line 76: Line 86:
 
== Release Notes ==
 
== Release Notes ==
 
<!-- The Fedora Release Notes inform end-users about what is new in the release.  Examples of past release notes are here: http://docs.fedoraproject.org/release-notes/ -->
 
<!-- The Fedora Release Notes inform end-users about what is new in the release.  Examples of past release notes are here: http://docs.fedoraproject.org/release-notes/ -->
<!-- The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns.  If there are any such changes involved in this feature, indicate them here.  You can also link to upstream documentation if it satisfies this need.  This information forms the basis of the release notes edited by the documentation team and shipped with the release. -->
+
<!-- The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns.  If there are any such changes involved in this feature, indicate them here.  You can also link to upstream documentation if it satisfies this need.  This information forms the basis of the release notes edited by the documentation team and shipped with the release.
*
+
 
 +
Release Notes are not required for initial draft of the Change Proposal but has to be completed by the Change Freeze.
 +
-->
 +
'''To be completed by the Change Freeze!'''
  
 
== Comments and Discussion ==
 
== Comments and Discussion ==
Line 83: Line 96:
  
  
[[Category:ChangePageIncomplete]]
+
[[Category:ChangeReadyForWrangler]]
<!-- When your change proposal page is completed and ready for review and announcement -->
+
<!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler -->
+
 
<!-- The Wrangler announces the Change to the devel-announce list and changes the category to Category:ChangeAnnounced (no action required) -->  
 
<!-- The Wrangler announces the Change to the devel-announce list and changes the category to Category:ChangeAnnounced (no action required) -->  
 
<!-- After review, the Wrangler will move your page to Category:ChangeReadyForFesco... if it still needs more work it will move back to Category:ChangePageIncomplete-->
 
<!-- After review, the Wrangler will move your page to Category:ChangeReadyForFesco... if it still needs more work it will move back to Category:ChangePageIncomplete-->

Revision as of 22:49, 15 July 2013

Contents

X2Go

Summary

The X2Go project has taken over development of the old NX libraries and has developed new clients and server code around it. We will move to use the X2Go NX library in Fedora and include the full X2Go suite.

Owner

  • Name: Orion Poplawski
  • Email: orion at nwra dot com
  • IRC: orionp
  • Release notes owner: <To be assigned by docs team>

Current status

  • Targeted release: Fedora 20
  • Last updated: 2013-7-15
  • Tracker bug: <will be assigned by the Wrangler>

Detailed Description

The current nx package in Fedora is based on the last open source release from NoMachine. NoMachine is no longer developing nx as an open source project. The X2Go project has taken the nx code and is maintaining it as well as developing new client and server code around it.


Benefit to Fedora

Fedora will contain a maintained, secure remote desktop/application access solution that works well over slower Internet connections.

Scope

  • Review the new nx-libs package which will replace the current nx package.
  • Confirm that existing packages that use nx work with the new package (if they worked before).
  • Review and include the rest of the X2Go suite:

Upgrade/compatibility impact

Should be transparent. Packages will be obsoleted and replaced as needed.

How To Test

For a server, install x2goserver.

For a client, install x2goclient.

Run x2goclient and connect to your server.

User Experience

Dependencies

Contingency Plan

We could perhaps revive the old nx package (with epoch bump if necessary), but this seems unlikely.

Documentation

Release Notes

To be completed by the Change Freeze!

Comments and Discussion