Hi, On 04/20/2011 01:58 PM, Dave Neary wrote: > I'd really like to get some help for this - it's a straightforward task, > but it'll definitely need more hands to get it done quickly. I'd like to > see a comment saying whether the bug still applies to the trunk > post-Verona merge, and whether it should be on the 3.0 milestone.
One thing I need to be clearer on is what should & shouldn't be on the 3.0 milestone. We had a chat earlier with Laurent, Nikita & Vadim about what we felt we could reasonably aim for for the 3.0 release. Some principles we agreed on are that we wanted to build a solid foundation for the future, and guarantee that core features worked well. We also want to ensure that the software is available for Windows, Mac and Linux, and works well on all 3. There are some features we've lost since the move to Verona: * SIP SIMPLE presence & status * Video calls - device detection, codecs & transport all have issues * Hold/Resume - isn't quite stable, and is untested on video calls * Assisted Call transfer - needs hold/resume to be stable, and is currently not coded. The priorities for 3.0 should be, in my opinion: * Making & receiving (and terminating!) audio calls, incl. DTMF * Hold/resume of audio & video calls * Handling of default audio devices needs work on Linux (if you launch the software on Ubuntu 11.04, it should Just Work if the sound card works with Pulseaudio) * Echo cancellation * Log off/log on should not result in lost functionality :) * No reproducible crasher bugs (it's possible that the software will crash in situations we can't reproduce, and thus can't fix) * IM with SIP SIMPLE should work, even if we don't get presence working properly again, presence and IM for libpurple should work & be thread safe. * Interop - we should work with the most common SIP platforms, and should interoperate with other SIP clients where it's straightforward to do so. * I'd like to see a way for us to federate SIP parameters for different services & offer the user the option of just selecting a VoIP supplier, and not have to worry about what the realm, gateway, etc. should be. This should be a fairly straightforward feature, but will have a big user impact. So, explicitly, that means that the following will not be priorities for 3.0: * Video calls - improving webcam detection, supporting more codecs, improving the rendering pipeline - all need work, and all can be done as part of a 3.1 release cycle * Call forwarding (3.1) * SIP SIMPLE presence (3.1) * XCAP config & contact list storage (later... needs platforms that support it to be useful) * Interop - if there is major surgery needed to interoperate with a client, we won't do it. In brief: given the limited resources on the project, let's concentrate on getting back as many features as we can from the 2.3 branch and making them rock solid in the short term, and then work on adding new compelling features. How does this sound? Cheers, Dave. -- Dave Neary Email: dne...@free.fr Jabber: nea...@gmail.com _______________________________________________ QuteCom-dev mailing list QuteCom-dev@lists.qutecom.org http://lists.qutecom.org/mailman/listinfo/qutecom-dev
