Changes

Jump to navigation Jump to search
16 bytes removed ,  19:27, 24 July 2010
m
no edit summary
Line 17: Line 17:  
Thanks for your interest, and good luck!
 
Thanks for your interest, and good luck!
   −
=How to Apply=
+
= How to Apply =
 
Application instructions are available at the main GSoC site -- see [http://groups.google.com/group/google-summer-of-code-announce/web/guide-to-the-gsoc-web-app-for-student-applicants here].
 
Application instructions are available at the main GSoC site -- see [http://groups.google.com/group/google-summer-of-code-announce/web/guide-to-the-gsoc-web-app-for-student-applicants here].
   Line 124: Line 124:  
* The Open Source Erlang/OTP distribution includes many libraries that implement common small tasks, and can be used freely because they are available in any ejabberd deployment
 
* The Open Source Erlang/OTP distribution includes many libraries that implement common small tasks, and can be used freely because they are available in any ejabberd deployment
 
* The erlang declarative programming language allows easy prototyping: no need to declare functions, variables, etc just to implement a function/module and try it.
 
* The erlang declarative programming language allows easy prototyping: no need to declare functions, variables, etc just to implement a function/module and try it.
      
=== Page for Account Registration & Password Recovery ===
 
=== Page for Account Registration & Password Recovery ===
Line 146: Line 145:  
* There is an old and experimental contributed module, mod_passrecover, that implements part of task 3. It could be used as an example
 
* There is an old and experimental contributed module, mod_passrecover, that implements part of task 3. It could be used as an example
 
* Example of registration page, this one is written in PHP: http://www.jabberes.org/jrt/
 
* Example of registration page, this one is written in PHP: http://www.jabberes.org/jrt/
      
=== Time Tracker ===
 
=== Time Tracker ===
Line 185: Line 183:  
== Openfire ==
 
== Openfire ==
 
Here are some nice features that would be nice to have in Openfire. We are still working on the list which should be ready for early next week (March 25th). If you have other ideas not listed here feel free to send us an email to discuss it or post it [http://www.igniterealtime.org/community/community/developers/gsoc08?view=discussions here].
 
Here are some nice features that would be nice to have in Openfire. We are still working on the list which should be ready for early next week (March 25th). If you have other ideas not listed here feel free to send us an email to discuss it or post it [http://www.igniterealtime.org/community/community/developers/gsoc08?view=discussions here].
  * File Repository and Sharing (including WebDAV)
+
* File Repository and Sharing (including WebDAV)
  * File transfers for gateways
+
* File transfers for gateways
  * Group Chat for Gateways
+
* Group Chat for Gateways
  * Update and improve BOSH support
+
* Update and improve BOSH support
  * Complete XMPP RFC implementation in XIFF and work on web client
+
* Complete XMPP RFC implementation in XIFF and work on web client
    
For more details, visit the [http://www.igniterealtime.org/community/docs/DOC-1490 Summer of Code 2008 Projects].   
 
For more details, visit the [http://www.igniterealtime.org/community/docs/DOC-1490 Summer of Code 2008 Projects].   
   −
===Contacts===
+
=== Contacts ===
 
Mentor: Gaston Dombiak (email: [mailto:gaston@jivesoftware.com gaston@jivesoftware.com] / jid: [xmpp:gato@jivesoftware.com gato@jivesoftware.com]).
 
Mentor: Gaston Dombiak (email: [mailto:gaston@jivesoftware.com gaston@jivesoftware.com] / jid: [xmpp:gato@jivesoftware.com gato@jivesoftware.com]).
   Line 230: Line 228:  
Since most IRC servers are written in C or C++ it seems to be best that this component is written in C or C++ as well.
 
Since most IRC servers are written in C or C++ it seems to be best that this component is written in C or C++ as well.
   −
Libraries you can use are found under http://jabber.org/
+
Libraries you can use are found under http://xmpp.org/software/libraries.shtml
    
=== XMPP Transport/Gateway ===
 
=== XMPP Transport/Gateway ===
Line 268: Line 266:  
=== Project description ===
 
=== Project description ===
 
Further develop [http://iss.im/ ISS (Instant Syndicating Standards)], built on top of [http://xmpp.org/extensions/xep-0163.html PEP (Personal Eventing via PubSub)].
 
Further develop [http://iss.im/ ISS (Instant Syndicating Standards)], built on top of [http://xmpp.org/extensions/xep-0163.html PEP (Personal Eventing via PubSub)].
Please see website or contact [http://wiki.jabber.org/index.php/User:NickVidal Nick Vidal] for more details.
+
Please see website or contact [[User:NickVidal|Nick Vidal]] for more details.
    
== PubSub Wordpress and Drupal plugins ==
 
== PubSub Wordpress and Drupal plugins ==
Line 318: Line 316:     
=== Links ===
 
=== Links ===
[http://flyspray.org Flyspray]
+
* [http://flyspray.org/ Flyspray]
[http://xmpp.org/extensions/xep-0050.html Ad-Hoc Commands]
+
* [http://xmpp.org/extensions/xep-0050.html Ad-Hoc Commands]
       
== Client-Independent Serverless IM component ==
 
== Client-Independent Serverless IM component ==
* Proposed Mentor: [http://el-tramo.be Remko]
+
* Proposed Mentor: [http://el-tramo.be/ Remko]
    
Currently, only some clients (iChat, Gajim) support server-less chatting, a feature which is very interesting to be able to discover and communicate with people on a local network, without the need to be connected to the internet. The reason behind the slow adoption of this protocol is probably that it breaks with the very fundamental way Jabber is designed (client-server architecture), and as such is a significant amount of work for an existing client to adapt its codebase. The aim of this project is to bring server-less messaging to every XMPP client, by implementing it outside of the client.
 
Currently, only some clients (iChat, Gajim) support server-less chatting, a feature which is very interesting to be able to discover and communicate with people on a local network, without the need to be connected to the internet. The reason behind the slow adoption of this protocol is probably that it breaks with the very fundamental way Jabber is designed (client-server architecture), and as such is a significant amount of work for an existing client to adapt its codebase. The aim of this project is to bring server-less messaging to every XMPP client, by implementing it outside of the client.
190

edits

Navigation menu