KTp: Difference between revisions

From KDE Community Wiki
(make last column show up properly)
Line 36: Line 36:
| NOT STARTED || [[Real-Time_Communication_and_Collaboration/Components/Logger|Logger Application]] ||  ||  |
| NOT STARTED || [[Real-Time_Communication_and_Collaboration/Components/Logger|Logger Application]] ||  ||  |
|-
|-
| IN PROGRESS || [[Real-Time_Communication_and_Collaboration/Components/Buddy_List|Buddy List App]] || George Goldberg <grundleborg googlemail com> || Not yet online |
| IN PROGRESS || [[Real-Time_Communication_and_Collaboration/Components/Buddy_List|Buddy List App]] || George Goldberg <grundleborg googlemail com> || Not yet online
|-
|-
| NOT STARTED || [[Real-Time_Communication_and_Collaboration/Components/Desktop-wide_Approver|Desktop Wide Tp::Approver]] ||  ||  |
| NOT STARTED || [[Real-Time_Communication_and_Collaboration/Components/Desktop-wide_Approver|Desktop Wide Tp::Approver]] ||  ||  |
|-
|-
| IN PROGRESS || [[Real-Time_Communication_and_Collaboration/Components/Integration_Daemon|Telepathy Integration Daemon]] || George Goldberg <grundleborg googlemail com> Help much appreciated || Not yet online |
| IN PROGRESS || [[Real-Time_Communication_and_Collaboration/Components/Integration_Daemon|Telepathy Integration Daemon]] || George Goldberg <grundleborg googlemail com> Help much appreciated || Not yet online
|-
|-
|}
|}

Revision as of 18:51, 26 January 2010

Introduction

Real time Communication has traditionally been a detatched feature of Desktop Computing, provided via stand-alone Instant Messaging clients with poor integration into the desktop experience. One of the primary goals of the KDE 4 series is to tighten integration between different components of the environment. The Realtime Communication and Collaboration (RTCC) project aims to tackle just this.

Our aims are:

  • To integrate Real Time Communication deeply into the KDE Workspaces and Applications
  • To provide a infrastructure to aid development of Collaborative features for KDE applications.

If you find these goals appealing, why not consider getting involved. C++ programming is *not* a necessity.

Technical Information

  • The RTCC project uses the cross-desktop Telepathy Framework as the basis for our work.
  • We should try and reuse code from Kopete/other already existing code wherever possibly. However, this should be balanced with the need to refactor/rewrite where appropriate to keep the new code true to Telepathy idioms.

Getting Involved

At this stage, the best way to get involved is to contact the existing team, either on IRC (#kde-telepathy channel on irc.freenode.net) or on our mailing list.

The Work

What we need to get done. This is divided into two sections:

  • Phase 1 contains the tasks which *must* be completed in order for us to make a first release.
  • Phase 2 contains other speculative major features that we will probably implement once Phase 1 is complete.

Phase 1

These are the essential tasks which must be completed before we can make a first release. Adding or removing tasks from this list requires a consensus on the kde-telepathy mailing list first. Click on a task title for further information about that task.

Status Task Developers Source Code
IN PROGRESS Account Management GUI George Goldberg <grundleborg googlemail com> Web SVN Link
NOT STARTED Chat Window App/Lib Matt Rogers <>
NOT STARTED Logger Application
IN PROGRESS Buddy List App George Goldberg <grundleborg googlemail com> Not yet online
NOT STARTED Desktop Wide Tp::Approver
IN PROGRESS Telepathy Integration Daemon George Goldberg <grundleborg googlemail com> Help much appreciated Not yet online

Phase 2

This section contains features that will *probably* be implemented once the first release has been made.

Status Task Developers Source Code
NOT STARTED Port Kopete plugins to Telepathy infrastructure
NOT STARTED Add voice/video call support to Chat UI
SPECULATIVE Add a internal Tp::Approver to Kopete