[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#534750: ITP: telepathy-mission-control-5 -- management daemon for Telepathy real-time communication framework



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Package: wnpp
Severity: wishlist
Owner: Simon McVittie <smcv@debian.org>

* Package name    : telepathy-mission-control-5
  Version         : 5.1.2
  Upstream Author : the Telepathy project (© Nokia Corporation, Collabora Ltd.)
* URL             : http://mission-control.sourceforge.net/
* License         : variously LGPL (= 2.1) and LGPL (>= 2.1)
  Programming Lang: C with GObject
  Description     : management daemon for Telepathy real-time communication framework

Telepathy Mission Control 5 is an account manager and channel dispatcher for
the Telepathy framework, allowing user interfaces and other clients
to share connections to real-time communication services without conflicting.
It implements the AccountManager and ChannelDispatcher D-Bus APIs as described
by telepathy-spec.

The account manager part stores real time communication account details,
connects to the stored accounts on request, and sets the accounts' presence,
nickname and avatar according to requests from Telepathy user interfaces and
other components.

The channel dispatcher part responds to incoming communication channels
(message streams, voice/video calls, file transfers etc.) by dispatching
them to suitable user interfaces, and requests outgoing communication
channels according to requests from a Telepathy UI.

This is not a compatible replacement for Mission Control 4 (in the
telepathy-mission-control package), but they can be installed in parallel.

- ------

Notes regarding this ITP:
* MC 4 will be removed when the programs that use it (I think that's just
  Empathy) have been ported to MC 5. That porting will take a while, though,
  so this is a new source package and the versions will exist in parallel for
  a bit.
* There's packaging for 5.1.0 on git.debian.org already; I just need to update
  it for a couple of new upstream releases, which should be pretty easy.
-----BEGIN PGP SIGNATURE-----

iD8DBQFKRThFWSc8zVUw7HYRAjStAJ9If6vzQb7oX2Tcxr52CQjpK5glhwCg8D+e
ZN69rkuCKHJt9rVE1lSIfpQ=
=KExX
-----END PGP SIGNATURE-----



Reply to: