41
edits
Difference between revisions of "Summer of Code 2010 Project Ideas"
Jump to navigation
Jump to search
Summer of Code 2010 Project Ideas (view source)
Revision as of 16:03, 1 April 2010
, 16:03, 1 April 2010no edit summary
| (2 intermediate revisions by the same user not shown) | |||
| Line 67: | Line 67: | ||
The deliverables for this project would be a working implementation and code snippets and deployment recipes to build the future of location sharing. You would be helped to understand some of the challenges of working with location, building scalable xmpp-based services and turning this into a working deployment. | The deliverables for this project would be a working implementation and code snippets and deployment recipes to build the future of location sharing. You would be helped to understand some of the challenges of working with location, building scalable xmpp-based services and turning this into a working deployment. | ||
=== XMPP-based roaming support === | |||
''Proposer:'' Dave Cridland | |||
I have, apparently, almost unique needs in the world. | |||
I have more than one computer, indeed - a desktop *and* a laptop. Not only that, I have a new fangled mobile telephony device - commonly called a mobile, by those in the know. | |||
I can tell I'm one of a kind, because whenever I install an XMPP - or email, or web - client on a computer, I have to reconfigure the damn thing, even thought it's talking to a server which - in principle - could store all my configuration for me, and keep it in sync between my laptop, my desktop, and my mobile client. | |||
Once, many years ago, I wrote such a system based around ACAP - now, I think a winning idea would be based around XEP-0223. | |||
There's a few tricky bits to this project - first, you'd have to figure out the common configuration items between clients, next you'd have to decide how to store them effectively and efficiently. The output would be (at least one) client having fully roaming configuration in at least proof of concept form, and a specification to take through the XSF - with your name on. | |||
== Specific Client Projects == | == Specific Client Projects == | ||
| Line 144: | Line 157: | ||
=== Openfire === | === Openfire === | ||
[http://www.igniterealtime.org/projects/index.jsp Openfire] is the award-winning, open alternative to proprietary instant messaging based on the Java programming language. It is modular and extensible via its plugin architecture. | [http://www.igniterealtime.org/projects/index.jsp Openfire] is the award-winning, open alternative to proprietary instant messaging based on the Java programming language. It is modular and extensible via its plugin architecture. | ||
==== Network application framework porting from Apache MINA to Netty ==== | |||
''Proposer:'' Safa Sofuoglu | |||
''Difficulty:'' Medium | |||
Openfire is using [http://mina.apache.org/ Apache MINA] library for its network infrastructure, but MINA 1.x has some known flaws (it can easily get OutOfMemory, also problems with processing of multibyte characters have been reported) and MINA 2.0 is not released yet. On the other hand, [http://www.jboss.org/netty Netty] looks promising with its feature set, active community, cleaner documentation and shorter release cycle. According to testimonals, migration from MINA to Netty has led to noticable performance boost and we believe that Openfire will benefit from this migration. | |||
==== Ideas ==== | ==== Ideas ==== | ||
* [http://www.igniterealtime.org/issues/browse/OF-162]: Multi-domain support | * [http://www.igniterealtime.org/issues/browse/OF-162]: Multi-domain support | ||
| Line 150: | Line 171: | ||
* [http://www.igniterealtime.org/community/docs/DOC-1925]: Constructive performance enhancements, which would include finding a structural solution to Openfires Achilles' heel | * [http://www.igniterealtime.org/community/docs/DOC-1925]: Constructive performance enhancements, which would include finding a structural solution to Openfires Achilles' heel | ||
* [http://www.igniterealtime.org/community/message/202083#202083]: Constructive spec compliance enhancements | * [http://www.igniterealtime.org/community/message/202083#202083]: Constructive spec compliance enhancements | ||
* [http://www.igniterealtime.org/community/docs/DOC-1992]: Clustering solution development | * [http://www.igniterealtime.org/community/docs/DOC-1992]: Clustering solution development | ||
* [http://www.igniterealtime.org/community/message/202083]: Automated functional testing | * [http://www.igniterealtime.org/community/message/202083]: Automated functional testing | ||