< KTp

Difference between revisions of "KTp/Developers"

m (Drdanz moved page Real-Time Communication and Collaboration/Developers to KTp/Developers: As discussed at IRC meeting Real-Time_Communication_and_Collaboration is too long, we are moving all our pages to KTp)
(No difference)

Revision as of 00:31, 10 November 2012


Welcome to the KDE Telepathy Development Wiki

Current Version: 0.9.0
     commits_spark.pngStats at ohloh.net


Real time Communication has traditionally been a detached 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.

Frequently Asked Questions

You can find a list of answers to frequently asked questions here: FAQ.

See also https://gkiagia.wordpress.com/2010/09/20/what-is-telepathy-kde/

The Plan

1) Build components equivalent to a traditional IM application, using Kopete code as much as possible, and integrating with other Pillars of KDE where appropriate.

2) Add advanced Telepathy features such as voice/video.

3) Build components and Convenience classes to enable real-time communication and collaboration features in any KDE SC app that wants them.

Current Ongoing Large Tasks



If you want to work on a feature, clone the git repository on the server side and then clone your personal clone on your local machine. Make a new git branch and start working there. Try to keep commits small and meaningful. Once you are finished, push the branch on your server-side clone and ask someone of the team to review it. Once it is reviewed, you can merge it on the master repository (or ask someone else to merge it).

Use of Milestones

We're trialling a clever use of milestones suggested by Jeroen van Meeuwen.

How it works

All bugs by default have the milestone "future" to say "we'll do it at some point". If we have no intention of doing it, it should not be in bugzilla.

For each (upcoming) release there is a version-next, such as 0.4-next. This contains everything we want fixed in the 0.4.x series.

As we approach release we create the milestone 0.4.0. Any bug we really want fixed before we can make a release then has the milestone changed from 0.4-next to 0.4.0. Any bug that we are happy to release 0.4.0 with, but still want fixed in the lifespan of 0.4.x, remains in 0.4-next. We then repeat this for every release.

  • 0.5.0 = really aiming to fix this in 0.5.0
  • 0.5.1 = really aiming to fix this 0.5.1
  • 0.5-next = aim to fix this at some point in the 0.5 series.

What should have a milestone

Bugs that we know how to fix, have a solid plan and have resources to do. Assigning everything to "0.4.0" when there's no way we can get it done will help no-one.

It should remain a small list of high priority tasks such that developers can see what is important.

What bugs should I prioritise working on

Anything tagged for the next release such as 0.4.0, then anything in 0.4-next, and finally anything in Future.

Obviously being free software you're free to work on what the hell you want.

Naming policy

Naming Policy



This page was last edited on 10 November 2012, at 00:31. Content is available under Creative Commons License SA 4.0 unless otherwise noted.