<div dir="ltr"><div><div><div>Name: Mayank Jha<br></div>IRC Nicks: mjnovice,mapyth on freenode.<br></div>Email: <a href="mailto:mayank25080562@gmail.com" target="_blank">mayank25080562@gmail.com</a> <br>Blog: <a href="http://mjnovice.wordpress.com/" target="_blank">http://mjnovice.wordpress.com/</a><br>
</div><div><a href="https://github.com/mjnovice/" target="_blank">Github Profile</a> <br></div><div>KDE identity Username: jhamayank<br><br><div><div><img src="https://mail.google.com/mail/u/0/images/cleardot.gif"></div>
</div><b><br>Why are you the right person for this task?</b><br>I
am a keen FOSS enthusiast and a regular contributor. Am well versed
with the languages and technologies used in ktp-telepathy, and am using
it for quite some time now. I am passionate and dedicated to the work I
undertake. <br><br><b>To what extent are you familiar with the software
you're proposing to work with? Have you used it? Have you read the
source? Have you modified the source?</b><br>I am very much familiar
with telepathy, and have submitted 5-6 patches. Am fairly comfortable
with the codebase of different components of telepathy.<br><b><br>How many hours are you going to work on this a week? 10? 20? 30? 40?</b><br>
I
can easily manage 45 hrs a week during my summer holidays (May 19 to
July 21, 2014), and 40 hrs a week when my college reopens. <br><b><br>Do
you have other commitments that we should know about? If so, please
suggest a way to compensate if it will take much time away from Summer
of Code.</b><br>I have no other commitments during the summer holidays,
ie May 19 to July 21, 2014. After that my classes would restart, but I
can manage, and easily devote the stipulated time to my work.<b><br><br>Are
you comfortable working independently under a supervisor or mentor who
is several thousand miles away, not to mention 12 time zones away? How
will you work with your mentor to track your work? Have you worked in
this style before?</b><br>I am perfectly comfortable with working under a
mentor sitting far away. I have worked before as a student for the
Google Summer of Code 2013.<br><br><b>If your native language is not
English, are you comfortable working closely with a supervisor whose
native language is English? What is your native language, as that may
help us find a mentor who has the same native language?</b><br>My native language is Hindi, but I perfectly comfortable and fluent in English.<b><br><br>Where do you live, and can we assign a mentor who is local to you so you can meet in a coffee shop for lunch? <br>
</b><div>I live in Forbesganj, India. It would be great if you could assign a mentor who lives near to my place.<br></div><br></div><div><br></div><b>Short Description:</b><br clear="all">
<div><div class="im">Currently telepathy supports 1-to-1 video call
for various services like gmail, facebook, jabber. But it lacks
multiparty conference call support, where you could have a google
hangout like group video chat. This project aims at implementing a full
fledged video conferencing feature into telepathy.<br>
<br></div><b>Synopsis:<br></b></div><div class="im"><div>Telepathy does not have conference
call support. The main dependencies telepathy-farstream and farstream implement the necessary RTP stream handling and codecs for call video conferencing. Telepathy gabble is buggy with respect to the features necessary to make the conference, so that needs to be fixed and apart from that the UI needs to be done
properly to allow user to make conference calls.<br>
<br></div></div><div class="im"><div><b>Implementation Details:<br></b></div><div>To implement the conference calls, we need to rewrite the current code in ktp-call-ui, to accomodate for conference calls. <br>
<br>For the UI, what we could do is, have the mainVideoWidget (
from the qtgstreamer library ), as the main video widget, and the
participants of the conference (including me) have their thumbnails sort
of videoWidgets at the bottom of the call window arranged, and clicking
on any of the bottom widgets would allow you to see the enlarged view
on the mainVideoWidget. Also currently there is restriction on the frame
per seconds rate of the video being streamed ie 15. We could add a
menu, which can have options to modify the frame rate. <br>
</div></div><div><div class="im">Since all of the work is done in Qt. So we would also need to
check while doing the User Interface, that the methods used are
optimum, and consistent, keeping in mind the efficiency of the feature.<br><br>The backend work, would involve rewriting the classes and the
methods of the ktp-call-ui to accomodate for multiple video streams. At
some places the fsconference is incomplete. This would involve
rewriting, the call-handlers and the call-managers, and also the classes
defined in ktp-call-ui/src/ as well as ktp-call-ui/libktpcall . <br>
<br><br>We might also need to make changes to
telepathy-gabble the main connection manager, to add support for
conference protocol if it lacks. </div><div class="im"><div><div><img src="https://mail.google.com/mail/u/0/images/cleardot.gif"><br></div><div>Finally
the conference feature needs to be tested rigourously through the
various test cases/scenarios. This I plan to do by making video calls
with an alias account, and prefereably with a second machine. And
eventually with real people.<br>
</div></div></div></div><div><div class="im"><br><p> <b>Phases/milestones with dates:</b></p><p>------------:Community Bonding Period:----------<br></p></div><p><i>21 April - 28 April</i> :<i> </i>I
am going to re-discuss my implementation plans with the telepathy
community, incorporating in the suggestions recieved, and clarifying the
design issues (if any). Most importantly I would test and judge the
completeness of telepathy-gabble in terms of supporting conference video
calls. I would use the test app, modifying it if required, to test the
conference call functionality.<br>
</p>
<p><i>29 April - May 06</i> : Getting familiar with the telepathy
codebase in particular ktp-call-ui, solve few bugs and getting
acquainted with the coding style/conventions. <br></p><p><i>May 07 - May 14</i>
: Start using the classes/methods in telepathyqt, telepathy-farstream
libraries pertaining to conference such as fsconference, make test
scripts and get to know how they work. <br>
</p><div class="im"><p><i>May 15 - May 18 </i>: Planning out the changes needed as a
part of the rewrite of the call interface. Making small scale
integration of the methods into ktp-call-ui call handlers.<br></p>
<p><br></p><p>------------:Coding Period Begins:-------------</p></div><p><i>May 19 - May 26 </i>:
Make changes to the UI to incorporate multiple videoWidgets, and make
the neccessary changes to the callwindow, call managers to allow for
display of multiple video widgets.</p>
<p><i>May 27 - June 4</i> :<i> </i>Check if the multiple videoWidgets
made, work fine without crashing. Implementing support for multiple
audiosinks, and separate volume controllers for each audio/video sink
pairs. <br>
</p>
<br></div><div><i>June 5 - June 19</i> : Integrating the multiple videoWidgets and their respective audio/video sinks with callChannels, and rigourously testing it.<div class=""><div id=":1iq" class="" tabindex="0"><img class="" src="https://mail.google.com/mail/u/0/images/cleardot.gif"></div>
</div><div class=""><br><br></div></div><div class="im"><div><i>June 20 - June 23</i> : Testing for consistency and efficiency of the Qt methods used. Check for consistency in coding style/conventions.<i><br>
<br></i></div><div><i>June 24 - June 27</i> : Discussing with the mentors about the current development, and getting their reviews/comments on the reviewboard.<br><br></div><div>:::::::::::::Mid term deliverables:::::::::::;<br>
</div></div><div class="im"><div>The UI would be capable of handing multiple audio/video streamings.<br><br></div><div><i>June 28 - July 12 :</i>
Use protocols defined in telepathy-gabble to make video calls. Adding
in the missing methods for the wrappers for fsconference and related
methods defined in telepathy-qt and telepathy-farstream. <br>
<br></div></div><div class="im"><div><i>July 13 - July 20</i> : Rigourously testing the integration of the conference gabble into ktp-call-ui .<br><br></div><div><i>July 21 - August 1</i>
: Getting reviews/feedbacks from telepathy developers and making any
changes suggested (if any).Testing the code by making actual calls with
kde developer community, on <a href="http://kdetalk.net" target="_blank">kdetalk.net</a> <br>
<br></div><div><i>August 2 - August 5</i> : Documenting the code. Testing the code by making actual calls with kde developer community, on <a href="http://kdetalk.net" target="_blank">kdetalk.net</a> <br><br></div><div>
<i>August 5 - August 22</i> : Backup time for unforeseen delays.<br>
</div><div><br></div></div><div>Post GSoC ----------> Maintain ktp-call-ui and telepathy in general. Become a part of the telepathy community. <br><br></div><div><b>About Me</b>:<br></div><div>I
am a FOSS enthusiast and a rabid open source contributor. I am
currently a 3rd yr undergraduate pursuing Computer Science at NIT,
Durgapur, India . I believe in the core principle of FOSS. Since I was
introduced to the warm, loving and inspiring world of Open Source I am
in love with it, as they offer great opportunity to both learn and
teach. <br>
</div><div>I was a student for the Google Summer of Code 2013, with
Ankur India and developed a font-metric tool for Indic fonts which could
differentiate fonts on the basis of their aesthetic quality and allow
font developers to contribute more and better fonts. <br>
</div><div>I have regularly contributed patches to applications like <i>Konversation, Kate, Telepathy, Trojita, Rekonq.</i> I also made a plugin for the Geany IDE, which would allow people to submit their code online at SPOJ through the editor. <br>
</div><div>I have also explored the Telepathy source code, and submitted few patches too on the same.<br>
</div><div>I am skilled in C/C++, Qt, Python, HTML, JAVA, CSS and PHP.<br>I am very passionate and done to the task I take under, and I can devote 40 hours a week, to my work. <br></div><div>After
GSoC I would continue and maintain my code and be a part of the
telepathy community, helping new people to join in the community. <br>
</div>Apart from remaining stuck to my laptop, I love to eat chocolates, listen to Michael Jackson, sleeping and eating.</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Sun, Mar 16, 2014 at 12:17 AM, Diane Trout <span dir="ltr"><<a href="mailto:diane@ghic.org" target="_blank">diane@ghic.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
> *Synopsis:*<br>
<div class="">> Kde telepathy does not have conference call support. The libraries (<br>
> telepathy-qt, telepathy-farstream ) on which it depends however has the<br>
> necessary classes and methods to allow you to integrate the conference<br>
> feature into the main UI. Main dependency telepathy-farstream is feature<br>
> complete. I would be implementing video conference support with connection<br>
> manager telepathy-gabble which also has most of the methods in it, and<br>
> might require some minor additions/changes. So, the UI needs to be done<br>
> properly to allow user to make conference calls.<br>
<br>
</div>I might write part of that as:<br>
<br>
The main dependencies telepathy-farstream and farstream implement the<br>
necessary RTP stream handling and codecs for call video conferencing.<br>
<br>
><br>
><br>
> *Implementation Details:*<br>
<div class="">> To implement the conference calls, we need to rewrite the current code in<br>
> ktp-call-ui, to accomodate for conference calls.<br>
><br>
> For the UI, what we could do is, have the mainVideoWidget ( from the<br>
> qtgstreamer library ), as the main video widget, and the participants of<br>
> the conference (including me) have their thumbnails sort of videoWidgets at<br>
> the bottom of the call window arranged, and clicking on any of the bottom<br>
> widgets would allow you to see the enlarged view on the mainVideoWidget.<br>
> Also currently there is restriction on the frame per seconds rate of the<br>
> video being streamed ie 15. We could add a menu, which can have options to<br>
</div>> modify the frame rate.q<br>
<br>
I think the UI of a main window plus strip of smaller thumbnails is a good way<br>
of handling this. And for a first implementation clicking to select who is the<br>
lead is reasonable. It would probably be a good idea to provide a good API to<br>
allow other selection algorithms. (e.g. signaling based off of whoever is<br>
talking).<br>
<div class=""><br>
> For the backend we would need to make changes to telepathy-gabble the main<br>
> connection manager, in call-muc-channel to add support for conference<br>
> protocol if it lacks. However since the gabble MuC is implemented over<br>
> muji, and services like facebook and gmail does not support, video<br>
> conferencing over XMPP, as it is closed, so in the end we would be having<br>
> multi-party video conference on muji based service like jabber.<br>
<br>
</div>I don't think there's any client that currently supports muji, It was just an<br>
experimental protocol. However, once the UI supports multi-party chat that<br>
will be useful when other protocols like COLIBRI are implemented.<br>
<br>
I'm not sure how specific the UI needs to be to the different multi-party<br>
protocols.<br>
<br>
Muji is based on a room concept - users join a room and then can join that<br>
conference.<br>
<br>
COLIBRI which implemented by Jitsi seems to be based around a conference<br>
organizer invites people into a conference.<br>
<span class="HOEnZb"><font color="#888888"><br>
Diane<br>
</font></span><div class="HOEnZb"><div class="h5">_______________________________________________<br>
KDE-Telepathy mailing list<br>
<a href="mailto:KDE-Telepathy@kde.org">KDE-Telepathy@kde.org</a><br>
<a href="https://mail.kde.org/mailman/listinfo/kde-telepathy" target="_blank">https://mail.kde.org/mailman/listinfo/kde-telepathy</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br><div dir="ltr">Mayank Jha<br><a href="http://mjnovice.wordpress.com/" target="_blank">http://mjnovice.wordpress.com/</a><br></div>
</div>