[X2go-dev] Looking for information on the future of x2go (and some other x2go-related stuff)

[Heinz-M. Graesing]

Hello Stefan,

Am 02.03.2011 13:55, schrieb Stefan Baur:
> Hi list,
> 
> I have been "playing" with x2go for a while and it looks very promising
> - a worthy successor to Nomachine NX - though I am unsure about a few
> things - maybe someone here on this list could provide some information?

Thank you for your commendation - I'll try to answer your questions.

> My questions are:
> 
> 1) With the recent announcement of Nomachine going closed source, what
> does the future of x2go look like?

As far as I know all Open Source components (existing or build in
future) will still be available on CD (if you ask them).

> 1a) As far as I understand, x2go uses parts of the GPL'ed Nomachine
> code, which will remain available in its current state due to the GPL,
> but will not be maintained by Nomachine any more. Are the x2go
> developers willing - and able - to maintain this part of the code, in
> case it requires maintenance and / or security patches?
> 1b) Or are you going to do a re-write of the Nomachine code currently
> in use?

The used used XOrg code isn't maintained since a long time. The only way
to get this construction supportable would be porting the functionality
as modules to a recent XOrg Version. We've been talking about this for a
very long time now. This all should be possible, but would take a lot of
time. It would be a decision about neglecting other parts of x2go for
some time. As Mike already mentioned, it will be a good idea to collect
some people to do this task.

I would suggest to discuss this topic after baikal (upcoming release) is
released.

> So I
> was wondering if there is a sufficient amount of other people backing
> the project that the loss of the lead developer (be it due to increased
> workload at his day job, health issues, or simply loss of interest) can
> be dealt with, should the situation arise? If that isn't the case right
> now, I would like to suggest making plans for it asap - the best time to
> install a fire escape ladder is before the house has a chance to start
> burning. ;-)

In the past we've been two people developing x2go and at the moment Alex
and I ares still interested in x2go. But during the last year more and
more people have been joined this list and we now have a usable python
client. X2go uses a lot of generic linux based projects (fuse, udev,
ssh, cups,...), which are maintained by themselves.

> 2) I read that Univention is using x2go for their desktop virtualization
> (see
> <http://wiki.univention.de/index.php?title=UCS_Desktop_Virtualization_Services>).
> Are they active supporters of x2go (i.e. donating money or manpower to
> the project)?
> (I ask because I'm hoping that a company planning a large-scale
> commerial deployment like Univention seems to be doing would have an
> interest in the x2go project staying alive and expanding.)

I didn't even know that they are using x2go. There were some contacts in
the past, but it was never mentioned that x2go would be a component of ucs.

> 3) I heard of legal issues regarding the project name and some other
> stuff. That was back in December. Since the project is still named x2go,
> and Univention is openly using this name, I was wondering if these
> issues have been resolved?

Yes and no, there is still a person left who claims x2go as
"werktitelschutz". A new name is the way to go if this problem can't be
solved.

> 4) Browsing the list archive, I saw that you are planning to provide
> packages for sid and wheezy via the official Debian repositories...

Mike answered this question before - all packaging topics will be
discussed and announced on the packaging mailing list.

> 5) I understand that you need some sort of full-screen application
> (similar to xdm/kdm/gdm) when running in thin client mode, and that this
> is why the current x2go client looks the way it looks, but I would
> really like to see a client that doesn't take up as much screen space,
> especially on Windows.

There are typically 3 Use Cases of x2goclient:

1.) You are sysop or supporter and you are required to have a lot of
sessions preconfigured. X1go will offer you a interface with easy
session management and search feature.

2.) You are a user of a device running the TCE (thin client
environment). You'll need to have a display manager to log into your
session.

3.) You are a desktop user and you only need one session configured.
Often the sysop has configured x2goclient using the "hidden mode" in
this case. This means, you only have an icon of the session/remote
application and if you use this desktop symbol, the remote application
will be started without showing x2goclient.

> Would it be possible to add an option for a "smaller" login window,
> similar to the one used by the current NX client:

Yes it would be possible - but it is not on our list for the upcoming
release. We already have been accepting to much features so baikal is
delayed more than we've expected. As Mike has already introduced his
solution: maybe pyhoca is an option.

>  when the session file was
> stored with a password, directly start the login process?

Maybe it is a better idea to work on a more usable solution for key
authentication.

> Regarding question 5, I cannot provide patches myself, as I am not a
> coder, but I would be willing to make a financial contribution either to
> the x2go project, if it is possible for them to accept such
> contributions, or to the coder providing the necessary patches (as long
> as the price quote seems reasonable and affordable to me) - if that
> helps motivate you to code. ;-)

It is very easy for us (I think I can speak for Mike too) to offer and
accept "orders - especially if the result can be used as part of the
mainstream distribution. Donations are somewhat critical, as they are
not addressed to a supply of service or product (as we need to pay tax
on the spend money).

Thank you for your mail and your questions. This way we've summarized a
lot of things into one place.

Regards,

Heinz