Hi all,

After consultation, here's the roadmap for the 3.0 release - we haven't
yet set a target date, which will depend in some sense on how long the
migration to CoIP Manager will take from the model, but I anticipate
that this release will be coming out before the end of 2007.

One thing to note about this roadmap are that it includes things which
are much requested features but which Wengo don't have the resources to
invest in here - I will try to be clear about what Wengo will be
spending time & resources on, and where we will be hoping for
contributions from outside the company. Another thing is that there are
several features here which depend to a large extent on what the goal of
the project is.

For example, when we say "support centralisation of contacts", do we mean:
 * All users of the WengoPhone should have the feature
 * Users of the WengoPhone connected to an industrial grade PBX should
have the feature, or
 * Users of the Wengo platform should have the feature

Each of these 3 positions is valid, and a different choice is probably
required in each case.

In each of these cases, the integration of the feature will be discussed
on wengophone-design and in the wiki before implementation.

And without further ado, here's the first revision of the WengoPhone 3.0
roadmap (from
http://dev.openwengo.com/trac/openwengo/trac.cgi/wiki/RoadMap):

** WengoPhone 3.0 - Quality, Cobranding, Customisation **

Must-have
=========

    * Integration of CoIP Manager
          o Publication of plug-in SDK
          o Definition of plug-in entry points (elements of the
application controllable from plug-ins)
          o Integration of IAX support from Code Camp

    * Quality of core components
          o Voice - adaptive ptime, improve codec support, improve audio
on Linux
          o Video - integrate support for H261, improve video over
H263/H263+

    * Co-branding
          o Allow theming of the interface
          o Create a cobranding pack (make it easier to change logos,
translations, sounds, name)

    * Enable centralisation of contact roster
          o Requires server support. Possible options: Jabber, XCAP, use
of a third party service for contacts

    * User experience
          o Integration with Outlook address book
          o Record audio calls
          o Re-enable voicemail notification
          o Refresh balance after calls and after SMSes

    * Interoperability
          o Allow a second SIP account to be open at the same time
          o Include support for MSN voice calls

Should have
===========

    * Integration of CoIP Manager
          o Integration of scripting interface from Code Camp
          o Integration of IPv6 support
          o Publication of example plug-ins: File transfer and VNC

    * User experience
          o Integration with other native address books (Thunderbird,
Mac Address book)
          o Integrate with audio conference facilities if available
          o Allow password storage and profile storage to be optional
for increased privacy

    * Interoperability
          o Include support for Jingle voice calls
          o Perfect interoperability with Asterisk & other SIP platforms

    * Quality of core components
          o Video - improved webcam support for Linux
          o Integrate support for Ogg Theora

Would be nice
=============

    * User experience
          o Integration with other native address books (EDS, Kontact)
          o Integration with system keyrings for passwords


Cheers,
Dave.



-- 
Dave Neary
OpenWengo Community Development Manager
Email: [EMAIL PROTECTED]
Tel: +33 9 51 13 46 45
Mob: +33 6 28 09 73 11
_______________________________________________
Wengophone-devel mailing list
[email protected]
http://dev.openwengo.com/mailman/listinfo/wengophone-devel

Reply via email to