Good morning dear KDE Telepathy team First I'd like to apologize for the confusion I created about this topic. I try to clear it with this email and will be ready to answer any questions of course.
Ok so here the history that preceded the confusion ;-): Some weeks ago I had a conversation with Martin Klepetek on IRC about what would be necessary (code and time) to have a simple audio/video chat solution (like Skype or Google Hangout) with KDE Telepathy technology. My idea was (and is) as well to find some money (if the necessary effort was manageable) to sponsor a developer to work on this. Martin then sent me the attached email and I had another conversation with Dario Freddi about what's necessary in Telepathy upstream and how cooperative Collabora would be. We three then planned a Skype or so discussion which didn't happen yet. Then came the Plasma Active 3 meeting where I participated and as I was already in contact with two of your KDE Telepathy guys I took over this task [1] (mainly to contact you what I do herewith ;-). So now the question are: - How do we proceed with the audio/video chat solution? - What the overhead for such a solution on Plasma Active (PA)? - Did somebody of you already worked with PA? - What do you think about the idea to find a sponsored developer? Thanks for your reading and best regards Mario [1] http://community.kde.org/Plasma/Active/Tasks#Audio.2FVideo_chat_and_IM_integration_in_PA
--- Begin Message ---Hi Mario, sorry, I didn't get to computer earlier. Here it goes: Tasks that need to be done: - Telepathy Call1 spec needs to be implemented in Connection Managers - this is almost done by Collabora (xclaesse), details unknown - Proper Qt bindings needs to be written - there are existing bindings for older call specin telepathy-qt-yell project, these needs updating to Call1 spec, which should be fairly easy/routine task - I estimate around 40-50 hours for someone familiar with Telepathy specs, glib and yell - Merge of telepathy-qt-yell into telepathy-qt - this step require unit tests and review from Collabora - 10-15 hours for someone familiar with unit testing - Port our KDE Telepathy call library to the new spec - 20-30 hours probably - Write good UI - 10-15 hours, provided there's a mockup from designer ready - System integration - this is simply the rest - proper working notifications (that is very tricky with current plasma notifications), integration with the current KDE Telepathy suite etc - shouldn't take more than 20 hours in total So by a rough estimate, it's something around 130 hours of work for skilled people who know they way around in Telepathy land, for people not familiar with it, I'd expect 170-190 hours, but that's my guess. Also unfortunately the work can't start before the Call1 spec is implemented upstream, otherwise we have nothing to work with. We also need QML bindings for GStreamer, which should be ready by the end of January. So that's all that's needed :) Cheers! -- Martin Klapetek | KDE Developer
--- End Message ---
_______________________________________________ KDE-Telepathy mailing list [email protected] https://mail.kde.org/mailman/listinfo/kde-telepathy
