[Ekiga-devel-list] Setting the goals for Ekiga 3.4
Hi everyone, In the last few months, Ekiga has been evolving in various directions following the own will of each of its developers. It is right that, on the contrary of other major Open Source projects, we are all coding in our spare time. The envy is great to do that the way we like it. However, if we want the project to survive and to evolve in a *stable* way, I think it is important to define goals between releases. Here are the goals I would like the project to reach for next release. I'm talking about user-visible changes, not about internal changes. Actually, things should be designed in Ekiga to improve the user experience, not the developer experience. 1) Having the possibility to add to the roster people with more than one phone number (from the address book). 2) When a contact has been added from the address book, renaming it in the address book will trigger renaming in the roster. Changing contact information (cellphone number) will have the same effect. 3) A stable Pulse plugin, which will be the default. We will take the advantage of all Pulse features (stream tagging so that music is automatically stopped when receving or giving a phone call, and so on) 4) Having the ability to handle several calls simultaneously, with attended transfer support. (I need this at the office to take calls with Ekiga). We should also work on related aspects : 1) Ekiga.org website 2) Ekiga.net website 3) Ekiga.net service Comments ? -- _ Damien Sandras (o- //\Ekiga Softphone : http://www.ekiga.org/ v_/_ Be IP : http://www.beip.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsand...@ekiga.net ___ Ekiga-devel-list mailing list Ekiga-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-devel-list
Re: [Ekiga-devel-list] Setting the goals for Ekiga 3.4
Damien Sandras a écrit : Le dimanche 27 septembre 2009 à 12:38 +0200, yannick a écrit : I think it is a good idea to add TCP support; atm the lack of TCP signaling for SIP broke some setups (calls fail), and as a packager I do not package extra codecs (non free) because of this bug. This means those non free codecs are undertested (e.g. it seems latest x264 lib do not compile with Ekiga anymore), and we lose some interoperability with other software/hardware out of the box. Agreed. However, that's more an OPAL feature and it requires serious work on Ekiga.net to add support for TCP and NAT traversal. I'm not sure of the result of having 1 active TCP connections to Ekiga.net either. hm... we are back to my secret project to take over the world... Thus I have a fix, but it will be released in 5 years :P I also think we should add some automatic workarounds. e.g. for freephonie.net which only works if video is disabled. Those issues hurt our reputation (even if the culprit is on the registrar side for not supporting well enough the standard). We have discussed that with Eugen, and he has some ideas to not clutter much our code... /me launching the hot patato to Eugen ;) I hate workarounds :-) Imagine we disable video for freephonie and they fix their stuff: we will ship broken stuff. But that's something we need to think about. Is that possible to contact them and ask them why we are rejected when offering video? Indeed, I need to ask them... thanks for the reminder. Still, I'm quite sure we will need some workarounds. Plugins maybe? ___ Ekiga-devel-list mailing list Ekiga-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-devel-list
Re: [Ekiga-devel-list] Ubuntu package/logs for testing the incoming stable release
yannick a écrit : yannick a écrit : yannick a écrit : Hi, With the help of Eugen Dedu (thx), I packaged The actual stable branch of Ekiga for Ubuntu 9.04 (last ubuntu stable): https://launchpad.net/~sevmek/+archive/ekiga-stable-prerelease This is *not* a release, the intent is for testing and paving the way for packaging the release. I updated my packages with today's stable branch. This time it should update flawlessly, i.e. automaticaly. I just packaged 3.2.7 testing branch... I'll update on a ~weekly basis. btw, Michael did it too for windows: http://wiki.ekiga.org/index.php/Windows_Users#Experimental_Releases Best regards, Yannick ___ Ekiga-devel-list mailing list Ekiga-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-devel-list ___ Ekiga-devel-list mailing list Ekiga-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-devel-list
Re: [Ekiga-devel-list] Setting the goals for Ekiga 3.4
On Sun, Sep 27, 2009 at 11:50 AM, Damien Sandras dsand...@seconix.com wrote: Le dimanche 27 septembre 2009 à 12:38 +0200, yannick a écrit : I think it is a good idea to add TCP support; atm the lack of TCP signaling for SIP broke some setups (calls fail), and as a packager I do not package extra codecs (non free) because of this bug. This means those non free codecs are undertested (e.g. it seems latest x264 lib do not compile with Ekiga anymore), and we lose some interoperability with other software/hardware out of the box. Agreed. However, that's more an OPAL feature and it requires serious work on Ekiga.net to add support for TCP and NAT traversal. I'm not sure of the result of having 1 active TCP connections to Ekiga.net either. Can we support it on ekiga and just not use it on ekiga.net so that those people that wish to use it have the advantage of it? Peter ___ Ekiga-devel-list mailing list Ekiga-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-devel-list
Re: [Ekiga-devel-list] Opal 3.6.6 build problem
László Monda wrote: Hi List, I've just hit the wall with Opal: l...@whisper:~/download/opal-3.6.6$ make [CC] src/opal/manager.cxx In file included from /home/laci/download/opal-3.6.6/include/opal/mediafmt.h:49, from /home/laci/download/opal-3.6.6/include/opal/connection.h:44, from /home/laci/download/opal-3.6.6/include/opal/call.h:41, from /home/laci/download/opal-3.6.6/include/opal/manager.h:41, from /home/laci/download/opal-3.6.6/src/opal/manager.cxx:40: /home/laci/download/opal-3.6.6/include/rtp/rtp.h:870: error: ‘PSafePtrMultiThreaded’ was not declared in this scope /home/laci/download/opal-3.6.6/include/rtp/rtp.h:870: error: wrong number of template arguments (2, should be 1) /usr/include/ptlib/safecoll.h:584: error: provided for ‘templateclass T class PSafePtr’ make: *** [/home/laci/download/opal-3.6.6/lib_linux_x86/obj/manager.o] Error 1 Hi, Here manager.cxx compiles very well. You should: - provide information about configuration parameters you have used - the ptlib version you use -- Eugen ___ Ekiga-devel-list mailing list Ekiga-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-devel-list
Re: [Ekiga-devel-list] Setting the goals for Ekiga 3.4
On 09/27/2009 05:19 AM, Damien Sandras wrote: Comments ? How about performance profiling? Ekiga may not be responsible, but on a good video phone call I will see at least one core at 100% CPU usage on a brand new Core 2 Duo system. Would it be good to profile the OPAL and/or ptlib as well as Ekiga to get CPU usage down? Skype, even though it's pretty much junk, uses less CPU. This CPU power draw reduces battery life on laptops, causes higher heat output, etc. ___ Ekiga-devel-list mailing list Ekiga-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-devel-list
