Roadmap

Daniele E. Domenichelli daniele.domenichelli at gmail.com
Wed Jul 28 16:23:17 CEST 2010


On 07/28/2010 11:39 AM, George Goldberg wrote:
> If there's anything I've
> missed out (or any more specific bugs come along) then please do add
> them as blockers to the tracker bug [1].

Hello,

This is a list of other features and technical issues that are in my
opinion important and that we will probably need to resolve, but I don't
know which of them are blocking or necessary for the preview release:


* Standard method to retrieve "myself"

* Accounts KCM should be shown in System Settings

* A model (like contact lists model) for user accounts (in progress)

* Fix the remove account and remove contacts bugs (I started working on
  them before gsoc, but I don't have time right now)

* Some useful proxy models
  - grouped model (fixes required?)
  - filter by status (in progress)
  - filter by capabilities
  - filter by group
  - filter by preference/tag?

* Widgets and Menu using models. In my opinion we need at least:
  - A menu (populated using a model) to run an action when a
    contact/metacontact/account is selected (in progress)
  - A widget (populated using a model) to allow a single
    contact/metacontact/account choice (QComboBox/KComboBox can
    probably work, but a method to retrieve a Nepomuk::Resource could
    be useful)
  - A widget (populated using a model) to allow a multiple
    contact/metacontact/account choice

* Static methods to start KJobs instead of using bridge?

* Methods to retrieve best account for an operation and use them
  instead of using bridge? (in people library?)

* Do we really need a "bridge"?

* Contacts model (and accounts model) should be singleton (it's nonsense
  to create several connection to nepomuk from the same program to do
  the same thing, but a programmer using the library could be unaware
  of this) and tha connection should be created as early as possible
  (so that, for example, when populating a widget there is no chance to
  find the model still empty.

* Order by preference: I made some tests, some days ago, and it is
  possible to use the standard "5 stars" to set a preference to any
  resource, also for contacts (also tags can be used). This can be used
  in Nepomuk queries to retrieve the contacts ordered (in people
  library?)

* Better MetaContact/PIMO::Person handling
  - Do we really need fake metacontacts? Can we create real
    metacontacts instead? If someone is using Nepomuk instead of
    telepathy stuff won't know anything about their existence
  - Investigate the advantages of using libfolks (and eventually switch
    to) for metacontacts management. (folks-qt4?)

* Better isBuddyOf/PublishesPresence/Subscription handling: in my
  opinion it is a little confusing and somehow buggy at the moment.

* DBus peer to peer patch integrated in Qt master (requires writing
  unit tests)

* DBusTubes integrated in telepathy-qt4

* StreamTubes integrated in telepathy-qt4

* Add some sort of dbus interface in t-i-d at least with a "quit"
  method, and hopefully also a "reload" method.


Cheers,
 Daniele


More information about the KDE-Telepathy mailing list