Maemo 5 uses various extended interfaces beyond what's in telepathy-spec.
We should review those interfaces, and either include them in telepathy-spec (with improvements or as-is), or explain how they can be done better. After an initial scan through them, this bug can become a metabug blocked by those extensions.
RTCom-Telepathy-GLib is a small library containing spec extensions, either drafts of things for the main spec or Nokia-specific interfaces:
Mission Control also contains some drafts and some Nokia-specific additions:
Mission Control extensions
(OMC here refers to osso-mission-control, a proprietary wrapper around MC 5 code used in Maemo 5 to add device-specific policy.)
In Mission Control 5, the following interfaces are already in telepathy-spec, but are shipped in MC 5 either to keep libmcclient backwards-compatible or to avoid needing a new telepathy-glib:
A draft version of contact caps, shipped in MC 5 for compatibility with Gabble 0.8.x. We don't need to integrate it.
Alberto's proposal for how requesting channels should work. I consider it to be flawed (requesting channels like this can't work without a ChannelDispatcher, so it should be a method on ChannelDispatcher) and propose to remove it during the 5.3.x cycle. libmcclient still uses it, so it's necessary to either make libmcclient use the standard API instead, or delete libmcclient in favour of telepathy-glib.
This is a miscellaneous dumping ground for unrelated features used to be compatible with Mission Control 4:
* Profile is Bug #24897
* SetHasBeenOnline is Bug #24898
* SecondaryVCardFields is Bug #24899
* AvatarFile is Bug #24900
This is Bug #24896.
This is Bug #24895.
List accounts that match a filter applied to their properties. I propose to drop this one during the 5.3.x cycle: listing all the accounts, and filtering them client-side, is no more difficult.
These are already in telepathy-spec and so can be removed.
These are drafts in telepathy-spec: Bug #13347 and Bug #13350, respectively. We should finish them.
We have declared Stream Engine to be Maemo-specific: talking to a daemon to stream media has some important disadvantages compared with just using telepathy-farsight directly, so we recommend using telepathy-farsight directly, and everyone doing media streaming outside Maemo seems to be doing so. As such, this is out of scope for telepathy-spec.
Bug #24907 covers the SMS bits. Bug #24909 is presumably related to the Privacy property; this leaves the IMSI, which is obviously rather GSM-specific, and is Bug #24910.
The other interfaces have quite a simple mapping to other bugs:
* mailbox-extensions.h, docs/mailbox.txt, Channel_Interface_Voicemail_Skype - Bug #24901
* Channel_Interface_Dial_Strings - Bug #24902
* Channel_Interface_Mute - Bug #21846
* Connection_Interface_Forwarding - Bug #13351
* Connection_Interface_Skype_CreditInfo - Bug #24903
* Connection_Interface_StoredMessages - Bug #24904
* Channel_Interface_Emergency, Connection_Interface_Emergency: Bug #24905
* Channel_Interface_Conference, Channel_Interface_Conference_Member: Bug #24906
* Channel_Interface_SMS - Bug #24907
* Channel_Interface_Persistent, Channel_Interface_Skype_GroupChat - Bug #23151
* Connection_Interface_Skype_CommunicationPolicy - Bug #24908
* Channel_Interface_Privacy, Connection_Interface_Privacy: Bug #24909
-- GitLab Migration Automatic Message --
This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.
You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/telepathy/telepathy-spec/issues/43.