Contribute to tasks in Kde-telepathy

[George Kiagiadakis]

2010/11/22 Chinmaya Padhi <padhi.chinmaya at gmail.com>:
> Hi ,
>
> Yesterday , I was an observer to the discussion that happened in the
> kde-telepathy channel . With the wiki updated with some latest tasks ,
> I am interested to contribute to these items :
>
> (Re-)write the contact list UI.
> (Re-)write the call UI (just the UI, not the actual call mechanism).
>
> I am not aware of the current development state , but would prefer the one
> which can be tested easily . I believe these tasks require QML
> and it will be a great practical experience for me to use my QML knowledge
> in this project.
>
> Please share your inputs !!


Hello and welcome,

You are welcome to adopt these tasks, or parts of them. The problem
with both of these tasks is that no functional backend  exists yet.
The contact list requires a contacts model, which will be provided by
libktelepathy. Before implementing it, some issues need to be fixed in
the nepomuk integration service.  The call ui needs a functional
backend as well, which is blocked on missing functionality from other
libraries (farsight, telepathy-qt4, see the wiki for details).

However, we decided that both could be implemented in parallel with
the development of the backends, using a fake backend for testing. For
the contact list, you could implement a fake model with some static
contacts on it, and for the call ui, you could implement a small
testing library that implements the same interface as the call library
that will be (re-)written.

I think that in both cases, having those testing backends will be
useful even when we have the real backends working, so that we can
make unit tests for the ui or make ui changes easier (so that for
example I don't have to start a conference just to test a change in
the ui).

Perhaps the contact list is easier to start with, so you could start
experimenting if you wish. Just make sure to coordinate the model
interface with others, so that the real model can be implemented with
the same interface. Similarly for the call ui, of course.

Best regards,
George