Changes/X2Go

From FedoraProject

< Changes(Difference between revisions)
Jump to: navigation, search
(Scope)
 
(20 intermediate revisions by 2 users not shown)
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-05-30
+
* 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: [https://bugzilla.redhat.com/show_bug.cgi?id=998551 #998551]
  
 
== Detailed Description ==
 
== Detailed Description ==
Line 19: Line 30:
  
 
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.
 
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 ==
 
== Benefit to Fedora ==
Line 29: Line 39:
 
<!-- What work do the developers have to accomplish to complete the feature in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->
 
<!-- What work do the developers have to accomplish to complete the feature in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->
  
* Review the new nx-libs package which will replace the current nx package.
+
* Review the new [https://bugzilla.redhat.com/show_bug.cgi?id=969209 nx-libs] package which will replace the current nx package. - Done
 
* Confirm that existing packages that use nx work with the new package (if they worked before).
 
* 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.
+
* Review and include the rest of the X2go suite:
 +
** [https://bugzilla.redhat.com/show_bug.cgi?id=969220 x2goserver] - done
 +
** [https://bugzilla.redhat.com/show_bug.cgi?id=969212 x2goclient] - done
 +
** [https://bugzilla.redhat.com/show_bug.cgi?id=990815 x2godesktopsharing] - done
 +
** [https://bugzilla.redhat.com/show_bug.cgi?id=990817 python-x2go] - done
 +
** [https://bugzilla.redhat.com/show_bug.cgi?id=991286 pyhoca-gui] - done
 +
** [https://bugzilla.redhat.com/show_bug.cgi?id=991292 pyhoca-cli] -done
 +
** [https://bugzilla.redhat.com/show_bug.cgi?id=1004094 cups-x2go] - done
  
 
== Upgrade/compatibility impact ==
 
== Upgrade/compatibility impact ==
<!-- What happens to systems that have had a previous versions of Fedora installed and are updated to the version containing this change? Will anything require manual configuration or data migration? Will any existing functionality be no longer supported? -->
+
 
 +
The current nx package contains both server (nxagent) and client (nxproxy) components.  nx will be obsoleted by the nx-libs, nxagent and nxproxy packages.  This allows updates to be without updated clients to be seamless. 
 +
 
 +
However, clients such as remmina-nx should change to require nxproxy, and server components such as freenx-server should change to require nxagent.
  
 
== How To Test ==
 
== How To Test ==
Line 50: Line 70:
 
3. What are the expected results of those actions?
 
3. What are the expected results of those actions?
 
-->
 
-->
 +
 +
For a server, install x2goserver.
 +
 +
For a client, install x2goclient.
 +
 +
Run x2goclient and connect to your server.
  
 
== User Experience ==
 
== User Experience ==
 
<!-- If this feature is noticeable by its target audience, how will their experiences change as a result?  Describe what they will see or notice. -->
 
<!-- If this feature is noticeable by its target audience, how will their experiences change as a result?  Describe what they will see or notice. -->
 +
N/A (not a System Wide Change)
  
 
== Dependencies ==
 
== Dependencies ==
<!-- What other packages (RPMs) depend on this package?  Are there changes outside the developers' control on which completion of this feature depends?  In other words, completion of another feature owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate?  Other upstream projects like the kernel (if this is not a kernel feature)? -->
+
 
 +
freenx-server
 +
qtnx
 +
remmina-plugins-nx
 +
 
 +
As a provenpackager I can make the needed small changes in requires.
  
 
== Contingency Plan ==
 
== Contingency Plan ==
Line 68: Line 100:
 
== 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 ==
* See [[Talk:Features/X2Go]]  <!-- This adds a link to the "discussion" tab associated with your page.  This provides the ability to have ongoing comments or conversation without bogging down the main feature page -->
+
* See [[Talk:Changes/X2Go]]  <!-- This adds a link to the "discussion" tab associated with your page.  This provides the ability to have ongoing comments or conversation without bogging down the main feature page -->
 +
 
  
 +
[[Category:ChangeAcceptedF20]]
 +
<!-- 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-->
  
[[Category:FeaturePageIncomplete]]
+
<!-- Select proper category, default is Self Contained Change -->
<!-- When your feature page is completed and ready for review -->
+
[[Category:SelfContainedChange]]
<!-- 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 -->
+

Latest revision as of 20:02, 10 September 2013

Contents

[edit] X2Go

[edit] 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.

[edit] Owner

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

[edit] Current status

[edit] 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.

[edit] Benefit to Fedora

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

[edit] Scope

[edit] Upgrade/compatibility impact

The current nx package contains both server (nxagent) and client (nxproxy) components. nx will be obsoleted by the nx-libs, nxagent and nxproxy packages. This allows updates to be without updated clients to be seamless.

However, clients such as remmina-nx should change to require nxproxy, and server components such as freenx-server should change to require nxagent.

[edit] How To Test

For a server, install x2goserver.

For a client, install x2goclient.

Run x2goclient and connect to your server.

[edit] User Experience

N/A (not a System Wide Change)

[edit] Dependencies

freenx-server qtnx remmina-plugins-nx

As a provenpackager I can make the needed small changes in requires.

[edit] Contingency Plan

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

[edit] Documentation

[edit] Release Notes

To be completed by the Change Freeze!

[edit] Comments and Discussion