Difference between revisions of "Summer of Code 2012"

Feel free to talk or chat with developers at any of the above resources about potential Summer of Code ideas. Also have a look at the ideas list below, and get in touch with potential mentors for any projects that take your fancy.

|}

In general, we consider your GSoC project to be a summer job, so try to provide detailed information that will enable us to decide if you deserve to earn the money Google will be paying. Our project ideas are like "RFPs" -- your application is your proposal to get the job. Please treat it seriously. Thanks!

=Project Ideas=

** Git version control

** Understanding of XMPP server-side history technology

** Media streaming

** Understanding of XMPP 'Jingle' technologies

** Git version control

** An understanding of a range of XMPP technologies.

=== Multi-account Support ===

** Ability to work with Qt GUIs, creating potentially complex UIs

** Git version control

** Git version control

** An understanding of a range of XMPP technologies.

=== User activity/profile ===

** Git version control

** An understanding of the "PEP" range of XMPP technologies.

=== Screen sharing ===

** An understanding of the Jingle range of XMPP technologies.

** An understanding of screen sharing technology, such as VNC.

=== Whiteboarding ===

** Ability to work with complex Qt GUIs

** Git version control

== Spectrum ==

* '''Details''': Admins are usually running more Spectrum 2 instances and there is a need for easy interface to manage them and gather the statistics. A student would create web-interface in any language (but Python/Ruby/PHP is preferred) allowing the admin to manage Spectrum 2 instances. The web-interface would communicate with Spectrum 2 instance using the XMPP by sending/receiving messages (Spectrum 2 part of this communication is already implemented and is not part of this project). C++ knowledge is not strictly needed for this project, but would be useful. This is often requested feature and there is a place for student's creativity.

* '''More info''': http://spectrum.im/projects/spectrum/wiki/Summer_of_Code_2012#Web-interface

=== Ad-Hoc commands ===

* '''Details''': The goal of this project is to design an interface for creating Ad-Hoc commands either by Spectrum 2 and also by its backends and create simple Ad-Hoc commands for Spectrum 2 instance maintenance (like "Send message to online users" and so on). A student would use Swiften XMPP library (already used in Spectrum 2) to add Ad-Hoc commands support. Then the student has to map Ad-Hoc commands and data forms into the Google Protobuf to let backends to use it.

* '''More info''': http://spectrum.im/projects/spectrum/wiki/Summer_of_Code_2012#Ad-Hoc-commands

=== Twitter backend ===

* '''Details''': Spectrum 2 supports Twitter network using the Pidgin's microblog-purple plugin. This plugin is not designed to be easily used in the way Spectrum 2 uses it. The goal of this project is to implement standalone Twitter backend. Backend is a console application which connects the main Spectrum 2 instance and then handles XMPP user's requests and map them to the Twitter network. Backend can be written in any language with Google Protobuf support, but C++ or Python is preferred.

* '''More info''': http://spectrum.im/projects/spectrum/wiki/Summer_of_Code_2012#Twitter-backend

== Prosody ==

* '''Details''': Although spam and abuse isn't prevalent on XMPP as it is on most other networks, it's on the rise. Implement a range of features to help stop this trend, and help service administrators keep on top of abuse on the network.

* '''More info''': http://prosody.im/gsoc#spamabuse_prevention

=== Web Interface ===

* '''Details''': An XMPP-based web interface to monitor and control Prosody instances (and at some level, other servers). We have an initial version as mod_admin_web, but it has some way to go to become nice and usable.

* '''More info''': http://prosody.im/gsoc#web_interface

=== Websocket support ===

* '''Details''': Now that the [http://dev.w3.org/html5/websockets/|websockets specification] has settled down somewhat, update Prosody's mod_websocket to support it.

* '''More info''': http://prosody.im/gsoc#websocket_support

=== XMPP network monitoring ===

* '''More info''': http://prosody.im/gsoc#xmpp_network_monitoring

** http://doomsong.co.uk/extensions/render/message-archive-management.html  

** http://xmpp.org/extensions/xep-0136.html

=== The "it 'effing works as expected" Project ===

** http://www.tigase.org/project/testsuite

** http://seleniumhq.org/projects/

=== buddycloud places ===

** http://m.buddycloud.com/tmp/proofs/20100129-buddycloud-architecture.png  

** http://m.buddycloud.com/tmp/proofs/Android%20place%20handling.png

** https://github.com/buddycloud/iphone-client

** https://github.com/buddycloud/android-client

=== buddycloud media server ===

** http://salon.io/

** https://buddycloud.org/wiki/Buddycloud_media_server

=== ncurses buddycloud ===

The Pubsub browser interface must be simple and straightforward, but it does not have to be intuitive.

* '''XEPs used''': 0060

=== PEP User additions ===

The «?set?» part of all those additions will an easy task, but displaying the data of people in the roster might need some thinking in order to not overload the interface.

* '''XEPs used''': 0080, 0107, 0108, 0118, 0163,  0172

=== PEP microblogging ===

And again, an UI has to be designed.

* '''XEPs used''': 0163, 0277

=== Buddycloud-like microblogging ===

The student will have to keep in mind that the UI must integrate nicely (remember this is a console client!).

* '''XEPs used''': 0060, Buddycloud custom

=== File transfers ===

* '''XEPs used''': 0166, 0234, 0260, 0261

== Gajim ==

* '''XEPs used''': 0278

=== Last Message Correction ===

== Jitsi ==

[http://jitsi.org Jitsi] is an XMPP audio/video and chat communicator that also supports other protocols such as SIP, AIM/ICQ, Windows Live, Yahoo! as well as many other useful [http://jitsi.org/features features]. Jitsi's XMPP projects are also available [http://jitsi.org/index.php/Development/GSoC-XMPP here]. Teaser tasks can be found [http://jitsi.org/index.php/Development/TeaserProjects here]

=== XMPP Echo and Mirror ===   

{| border="0"

* '''XEPs used''': 0166, 0167, 0176

* '''More info''': http://jitsi.org/index.php/GSOC/XMPPEchoAndMusic

|}

* '''XEPs used''': 0166, 0167, 0176

* '''More info''': http://jitsi.org/index.php/GSOC/LibJitsi

|}

* '''Details''': Implement support for the DNSSEC protocol in Java and replace the existing libunbound implementation in Jitsi so that XMPP services (among others) could be securely recovered before connection.  

* '''More info''': http://jitsi.org/index.php/GSOC/DNSSEC

|}

* '''Details''': Ever noticed how GoogleTalk allows you to exchange files directly with peers and the speed is so awesome? Well, an important part of that is a tiny TCP implementation that works on top of UDP. Would you like to work on it with us?   

* '''More info''': http://jitsi.org/index.php/GSOC/PseudoTCP

|}

{| border="0"

|-

* '''Details''': Implement support for various XMPP related features such as user search, last message correction and retrieval of messages sent through other locations.  

* '''More info''': http://jitsi.org/index.php/GSOC/XMPPGoodies

|}

{| border="0"

|-

* '''Details''': JingleNodes provide services that can proxy (relay) media when all participants are in a call. This project is about making this possible over TCP for JN's Java implementation.

* '''More info''': http://jitsi.org/index.php/GSOC/TCPJingleNodes

|}