Difference between revisions of "Summer of Code 2005"

Jump to navigation Jump to search
1,036 bytes added ,  22:20, 24 July 2010
m
no edit summary
m
 
(18 intermediate revisions by one other user not shown)
Line 2: Line 2:


== News ==
== News ==
 
2005-07-05: Projects have been chosen and posted on this page. Look for updates throughout the summer.
2005-07-05
 
Projects have been chosen and posted on this page. Look for updates throughout the summer.


== Projects ==
== Projects ==
=== DBus Transport Layer ===
=== DBus Transport Layer ===
Goal: Ease the integration of XMPP into existing applications by providing a unified way to send arbitrary (but valid) stanzas via the DBus IPC protocol using only one resource and connection to the Jabber server.
Goal: Ease the integration of XMPP into existing applications by providing a unified way to send arbitrary (but valid) stanzas via the DBus IPC protocol using only one resource and connection to the Jabber server.


Student: Jakub Piotr Cłapa
Student: Jakub Piotr Cłapa


=== Shockwave Lingo Library ===
=== [[Shockwave Lingo Library]] ===
 
Goal: Create a library for Jabber/XMPP development in in Lingo, the Macromedia Shockwave Script language.
Goal: Create a library for Jabber/XMPP development in in Lingo, the Macromedia Shockwave Script language.


Student: Samuel Shoji Fukujima Goto
Student: [http://www.ic.unicamp.br/~ra017335 Samuel Shoji Fukujima Goto]


=== Xmppd.py Improvements ===
=== Xmppd.py Improvements ===
Goal: Add support for privacy lists, delayed delivery, non-SASL authentication, private XML storage, vCards, and several other features to the xmppd.py server.
Goal: Add support for privacy lists, delayed delivery, non-SASL authentication, private XML storage, vCards, and several other features to the xmppd.py server.


Line 28: Line 21:


=== Gloox Library ===
=== Gloox Library ===
Goal: Help the gloox C++ library to full XMPP compliance.


Goal: Help the gloox C++ library to full XMPP compliance and add Publish-Subscribe support.
Result: I was able to complete my goal in time and additionally added support for several XEPs to gloox.


Student: Jakob Schröter
You can find more information about the current status, planned work and source code releases at gloox' homepage: [http://camaya.net/gloox camaya.net/gloox]
 
Student: Jakob Schröter


=== XMPP/JADE Integration ===
=== XMPP/JADE Integration ===
Goal: Develop a new XMPP-based Message Transport Protocol for the Java Agent Development framework.
Goal: Develop a new XMPP-based Message Transport Protocol for the Java Agent Development framework.


Student: Shawn Drost
Student: Shawn Drost


=== Piorun Client ===
=== [[Piorun Client]] ===
 
Goal: Develop a strong code foundation for a Gnome Jabber client using Mono, C#, and Gnome#.
Goal: Develop a strong code foundation for a Gnome Jabber client using Mono, C#, and Gnome#.


Student: Dominik Zabłotny
Student: Dominik Zab?otny


=== Jive Messenger Security Enhancements ===
=== Jive Messenger Security Enhancements ===
Goal: Add support for SASL and TLS (as defined in RFC 3920) to Jive Messenger.
Goal: Add support for SASL and TLS (as defined in RFC 3920) to Jive Messenger.


Line 52: Line 45:


=== Compliance Testing Project ===
=== Compliance Testing Project ===
Goal: Develop the basis for a Java-based XMPP compliance platform for testing both servers and clients.
Goal: Develop the basis for a Java-based XMPP compliance platform for testing both servers and clients.


Line 58: Line 50:


=== Ruby Code Library ===
=== Ruby Code Library ===
Goal: Develop a clean Ruby library that implements the XMPP specifications.


Goal: Develop a clean Ruby library that implements the XMPP specifications.
Project page: http://jabberstudio.org/projects/netxmpp-ruby/project/view.php


Student: Yuki Mitsui
Student: Yuki Mitsui


=== HTTP Jabber Interface ===
=== HTTP Jabber Interface ===
Goal: Develop a PHP-based implementation of [http://xmpp.org/extensions/xep-0124.html XEP-0124] and [http://xmpp.org/extensions/xep-0025.html XEP-0025] for improved integration between web applications and XMPP.
It will use a database to store messages and forward it to the Jabber server. It relays those messages and returns the response from the jabber server to the client.
The HTTP is used to relay the jabber messages and hence it can be used with any HTTP server and doesnt need any new port permissions to be assigned. Hence making the Jabber to work in even restricted environments.


Goal: Develop a PHP-based implementation of JEP-0124 and JEP-0025 for improved integration between web applications and XMPP.
Project WebPage: http://jabberstudio.org/projects/japper/project/view.php


Student: John Jimmy Dondapati
Student: John Jimmy Dondapati
Address:
Door No. 7-212,
Mercy Home,
Ramavarappadu,
Vijayawada-8
Andhrapradesh,
India - 521108
[http://johndondapati.com Click here to visit Johns Website]
216

edits

Navigation menu