Community:SummerOfCode13:Brainstorming: Difference between revisions

→‎Instantbird: Add Instantbird ideas from https://etherpad.mozilla.org/ib-gsoc-2013
(→‎Instantbird: Add Instantbird ideas from https://etherpad.mozilla.org/ib-gsoc-2013)
Line 415: Line 415:
! Mentor(s)  
! Mentor(s)  
! Comments
! Comments
|-
| FileLinks in Instant Messages
| '''Goal:''' File transfers that work reliably for every protocol.
'''Description:''' The Thunderbird Filelink feature allows users to upload attachments to an online storage service, replacing the email attachment with a link. This existing code could be used to implement file transfer. While some protocols support file transfer directly, this approach would provide a fallback that should always work. Designing and implementing a good UI frontend would also be required.
| JavaScript, XPCOM, XUL
| Florian Quèze
| Florian Quèze
| The frontend should be flexible enough to be able to handle other file transfer methods when they are implemented, e.g. WebRTC for XMPP or DCC for IRC.
|-
| Additional JavaScript protocol plug-ins
| '''Goal:''' Implement new protocol plug-ins in JavaScript, or create more stable implementations of existing ones.
'''Description:''' Instantbird supports protocol plugins implemented in JavaScript, in addition to the C libpurple plugins. The student will either add support for new protocols in Instantbird (if so, explain why this protocol matters) or reimplement in JavaScript a protocol that is poorly supported by libpurple (if so, explain what will be  better supported in the new implementation, or why the current implementation is not adequate). All new protocol plugins will go through a strict code review to ensure high code quality. The student working on new protocols should take every opportunity to improve the code and APIs shared by all JS protocol plugins.
| JavaScript, XPCOM, maybe js-ctypes
| Patrick Cloke
| Florian Quèze for JS-SIP, Patrick Cloke for other protocols
| IRC, XMPP, Twitter and OSCAR (AIM/ICQ) have been (or are in the process of being) implemented and should not be considered.
|-
| Improve JS-XMPP
| '''Goal:''' Ease working with the JavaScript XMPP implementation and implement new features.
'''Description:''' Include better syntax for XML handling, implementing handling of MUCs and other features. Feature-parity with libpurple's XMPP support is one of the prerequisites for replacing the libpurple XMPP plug-in that is currently used. One possible improvement would be to support voice and video calls between a JS-XMPP client and a Jingle client using WebRTC.
| JavaScript, maybe XUL, XPCOM
| Florian Quèze
| Florian Quèze
|
|-
| Skype protocol plug-in
| '''Goal:''' Support Skype chat features as protocol plug-in.
'''Description:''' Microsoft will soon dropping support for MSN/WLM, they suggest that all users migrate to Skype. The student is expected to implement support for Skype chat (private messages and multi-user chats) using the SkypeKit SDK.
This project does not need to support voice/video chat to be considered a success. Access to SkypeKit can be provided to a student participating in this project. This may need to be implemented as an extension.
| C++, XPCOM
| Patrick Cloke
| Patrick Cloke
|
|-
| "Awesometab"
| '''Goal:''' Create a tab that "knows" what conversation you want to open (like the "[http://www.dria.org/wordpress/archives/2008/04/17/628/ awesomebar]").
'''Description:''' The current "Join Chat" dialog is ugly and difficult to use. A user should be able to open a new tab to create a new conversation which will auto-complete fields based on history and server information (e.g. LIST from IRC).
| JavaScript, XPCOM, XUL, maybe some protocol interactions?
| Florian Quèze
| Florian Quèze, aleth
|
|}
|}


Confirmed users
161

edits