[Tickets #12180] Unification of instant messenger attributes

[noreply at bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/12180
------------------------------------------------------------------------------
  Ticket             | 12180
  Created By         | Thomas Jarosch <thomas.jarosch at intra2net.com>
  Summary            | Unification of instant messenger attributes
  Queue              | Turba
  Version            | Git master
  Type               | Bug
  State              | Unconfirmed
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


Thomas Jarosch <thomas.jarosch at intra2net.com> (2013-04-15 15:20) wrote:

Hi,

while testing the transfer of every contact attribute via ActiveSync + Kolab,
I realized the instant messenger field is not synced to/from my device.

Turns out Kolab uses an attribute named "instantMessenger" while
the attributes used for ActiveSync were added as "imaddress",  
"imaddress2" and "imaddress3".

At first I thought replacing "instantMessenger" with "imaddress" would
be a no-brainer. Grepping through the code showed that other
places like vcard import/export use that field, too. So vcard import/export
is currently not playing nice with ActiveSync regarding the instant  
messenger field.

My current plan looks like this
- Adapt Kolab attribute mapping to use "imaddress"
- Fix up code to use "imaddress"
- Use _("Instant messenger") label for the "imaddress" UI
- Remove "instantMessenger" from attributes.php


Unifying everything to "imaddress" is IMHO the only way to maintain BC
when Horde_ActiveSync gets updated and turba is hold back.

Objections?