Just to summarize the long discussion on debian-devel and give the Jitsi
community an opportunity to respond:
- does it work with GCJ?
I doubt someone has ever tried this. I'm guessing it would run partially if
at least Felix (the OSGi implementation) works.
- space is limited on disk 1 of Debian
- can dependencies be reduced?
Yes, thanks to the OSGi infrastructure, e.g. the protocols other than SIP
and XMPP could be removed. All that's necessary for this would be to remove
the jars from the directory (and to remove them from a config file to
That is good news - the package can recommend and suggest JARs that are
not mandatory dependencies, so people will still have an easy way to get
You could also have meta packages:
jitsi-minimal - with SIP and XMPP
jitsi-all - with all modules
and then individual packages
- can you split up JARs that contain stuff Jitsi doesn't use?
We already have a lot of JARs, each for a specific task or plugin. I don't
see what could or should be split even more. Are you thinking of something
There was no specific example in mind. However, I do know that
sometimes people use just 1% of classes from a JAR library and then the
other 99% and the related dependencies are wasted.
Linux desktop integration
- what is the current status of integration with GNOME, KDE, XFCE, etc?
We use the JDIC components that went into Java 1.6 with all its drawbacks.
This is especially noticeable with the non-transparent tray icon. We haven't
done anything special for a specific Linux desktop environment (other than
maybe a little hack here and there).
- what can be achieved by August (when the Debian desktop decision to
use XFCE will be reviewed)?
We had put up a project for a new systray implementation as part of GSoC,
but at least on the mailing list this hasn't drawn much attention. (See next
- this hasn't come up on debian-devel, but I have personally observed
problems with the settings windows not appearing properly. E.g. if I
click to add an account, the window for selecting account type appears
underneath the account list window. This means it is invisible and
unpleasant for people who don't know it is hiding there. My desktop is
configured for focus-follows-mouse and I notice that if I change to
click-to-focus, the windows appear correctly. Focus-follows-mouse is
popular with Linux developers, so this may impact the perception of Jitsi.
We want to switch the whole UI from Swing to HTML5, based on Chromium
Embedded Framework. As dependencies were also mentioned a lot, this will
certainly not make it any easier. On the other hand, I guess it will solve a
lot of the problems we currently have, like the focus issues you mentioned.
Given this UI framework change, it's unlikely we're going to put much effort
into the existing Swing UI.
ICE for SIP
- this may be the missing link, as it would enable full integration with
mainstream WebRTC (both SIP and XMPP) solutions
Emil is working on it...
Parts of it are already in master.
Some other points that come to mind:
- Bonjour support is still in the master tree, but disabled because it's not
stable and not maintained.
Yes, that is something else that has been requested on debian-devel
- Rolf Leggewie recently complained about our build setup for Debian.
I avoided complaining about that so far - I need to review the
dependency JARs and see if I can help you get them into standalone packages.
- What are those amazing integrations of Empathy/Telepathy the others were
I built a Debian Live DVD for several people, each with a pre-configured
XMPP account in Empathy. I posted the DVDs out to them and they can
just boot and call me.
So, Empathy does work, but that is a very specific use case where I
control the server and I control both ends of the connection to
guarantee that it works.
Empathy is great as a quick way to start doing XMPP chat - it is really
quick to set up and just works. For VoIP, however, it is limited by the
lack of TURN support and the demands of WebRTC.
On 31/03/14 21:29, Ingo Bauersachs wrote: