[opensuse-factory] [Proposal] Drop twinkle
That package is bit rotting since almost 5 years. This would also let us get rid of libzrtpcpp2. comments? darix -- openSUSE - SUSE Linux is my linux openSUSE is good for you www.opensuse.org -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Tue, 11 Feb 2014 21:59, Marcus Rueckert <darix@...> wrote:
That package is bit rotting since almost 5 years. This would also let us get rid of libzrtpcpp2.
comments?
darix
Question by the un-informed: What package(s) would you propose as replacement? (e.g. linphone -- I'm not sure about functionality) - Yamaban. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Tue, 11 Feb 2014 21:59:29 +0100 Marcus Rueckert <darix@opensu.se> wrote:
That package is bit rotting since almost 5 years. This would also let us get rid of libzrtpcpp2.
comments?
darix
Well, for me it is the best usable voip software that I use also in LXDE and XFCE even if it brings kde3 dependencies. If there is reasonable replacement that know all features and same reliability, then it would be nice to write it when we drop it. Josef -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Hi all.
That package is bit rotting since almost 5 years. This would also let us get rid of libzrtpcpp2.
comments?
darix
Well, for me it is the best usable voip software that I use also in LXDE and XFCE even if it brings kde3 dependencies. If there is reasonable replacement that know all features and same reliability, then it would be nice to write it when we drop it.
From my experience twinkle is still the best sip client for Linux. Best quality and good usability. Greets Marcus -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Tuesday 11 of February 2014 21:59:29 Marcus Rueckert wrote:
That package is bit rotting since almost 5 years. This would also let us get rid of libzrtpcpp2.
comments?
That would make me very unhappy. I tried both linphone and ekiga and liked neither. Michal Kubeček -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Wed, 2014-02-12 at 08:13 +0100, Michal Kubecek wrote:
On Tuesday 11 of February 2014 21:59:29 Marcus Rueckert wrote:
That package is bit rotting since almost 5 years. This would also let us get rid of libzrtpcpp2.
comments?
That would make me very unhappy. I tried both linphone and ekiga and liked neither.
Biggest manco for linphone is that it can not use a openldap as a phonebook directory. Ekiga can, but some of it's buttons/field operate counter intuitive. Jitsi (somewhere on the OBS) should be renamed obesi-phone, with regards to it memory usage. It has been reported on the jitsi-list to be using over 1GB. But it works great (sip + xmpp) as long as you still have mem. Only alternative might be slphone (qt and gtk skil) Just hope that the quality of the code is inversely proportional to the amount of docu :-)) hw -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Tuesday 11 of February 2014 21:59:29 Marcus Rueckert wrote:
That package is bit rotting since almost 5 years.
I must admit I hate this term; in my experience, it's only an empty phrase frequently used when someone is short of technical arguments. Bits don't rot. There are only unfixed (known) bugs, incompatible API/ABI changes and new requirements not addressed. So what exactly is wrong with twinkle? - are there serious known and unfixed bugs? - do we plan to drop Qt3 in the near future? - does it lack IPv6 support? (I don't know if it does - but I'm pretty sure there is a lot of other applications which do and noone accuses them of "bit rotting") - does it lack support for some important SIP features or audio codecs? Michal Kubeček -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 2014-02-12 08:31:47 +0100, Michal Kubecek wrote:
On Tuesday 11 of February 2014 21:59:29 Marcus Rueckert wrote:
That package is bit rotting since almost 5 years.
I must admit I hate this term; in my experience, it's only an empty phrase frequently used when someone is short of technical arguments. Bits don't rot. There are only unfixed (known) bugs, incompatible API/ABI changes and new requirements not addressed.
So what exactly is wrong with twinkle?
- are there serious known and unfixed bugs? - do we plan to drop Qt3 in the near future? - does it lack IPv6 support? (I don't know if it does - but I'm pretty sure there is a lot of other applications which do and noone accuses them of "bit rotting") - does it lack support for some important SIP features or audio codecs?
i will answer this mail and try to pick up the points from the others 0. replacements in no particular order linphone ekiga yate siphone any telepathy client via telepathy-rakia personally i had good experience with yate. 1. bit rot. yes the term sucks a bit. but bit rot doesnt only affect bugs. a) As you mentioned already Qt4 port would become necessary in the not too far future. b) libzrtpcpp is already a problem. currently we need to keep the old version around as libzrtpcpp2, so that we can build twinkle at all. While searching for patches to build it with the newer libzrtpcpp I stumbled over the fact that Fedora e.g. dropped it already. 2. IPv6 support. havent tested it. might actually work 3. audio quality: as most if not all SIP clients on linux should use the same libraries for codecs. i cant see how they would really differ. They might differ in things like voice normalization or echo cancellation. but codec wise... 4. KDE dependencies. those can actually be disabled at build time. Debian does that already. A question to all the people who raised their hand to keep the package: Would you step up to do the needed work to use the newer libraries? With kind regards, darix -- openSUSE - SUSE Linux is my linux openSUSE is good for you www.opensuse.org -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Dear darix.
On 2014-02-12 08:31:47 +0100, Michal Kubecek wrote:
On Tuesday 11 of February 2014 21:59:29 Marcus Rueckert wrote:
That package is bit rotting since almost 5 years.
I must admit I hate this term; in my experience, it's only an empty phrase frequently used when someone is short of technical arguments. Bits don't rot. There are only unfixed (known) bugs, incompatible API/ABI changes and new requirements not addressed.
So what exactly is wrong with twinkle?
- are there serious known and unfixed bugs? - do we plan to drop Qt3 in the near future? - does it lack IPv6 support? (I don't know if it does - but I'm pretty sure there is a lot of other applications which do and noone accuses them of "bit rotting") - does it lack support for some important SIP features or audio codecs?
i will answer this mail and try to pick up the points from the others
Thanks for pointing that out.
0. replacements in no particular order linphone ekiga yate siphone any telepathy client via telepathy-rakia
personally i had good experience with yate.
1. bit rot. yes the term sucks a bit. but bit rot doesnt only affect bugs. a) As you mentioned already Qt4 port would become necessary in the not too far future. b) libzrtpcpp is already a problem. currently we need to keep the old version around as libzrtpcpp2, so that we can build twinkle at all. While searching for patches to build it with the newer libzrtpcpp I stumbled over the fact that Fedora e.g. dropped it already.
2. IPv6 support. havent tested it. might actually work
3. audio quality: as most if not all SIP clients on linux should use the same libraries for codecs. i cant see how they would really differ. They might differ in things like voice normalization or echo cancellation. but codec wise...
That's true, but when it comes to e.g. echo cancellation Twinkle still does the best job.
4. KDE dependencies. those can actually be disabled at build time. Debian does that already.
A question to all the people who raised their hand to keep the package:
Would you step up to do the needed work to use the newer libraries?
At least I've now tried to contact the original author of the software to get his position about the future of twinkle. Greets Marcus -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (6)
-
Hans Witvliet -
Josef Reidinger -
Marcus Moeller -
Marcus Rueckert -
Michal Kubecek -
Yamaban