43
edits
Difference between revisions of "GSoC/2019/Project Ideas"
Jump to navigation
Jump to search
→Prosody IM: link to web chat too
(→Poezio: poezio projects) |
(→Prosody IM: link to web chat too) |
||
| (19 intermediate revisions by 6 users not shown) | |||
| Line 8: | Line 8: | ||
More information about [[GSoC/2019 | XMPP and the XSF at GSOC 2019 can be found here]]. | More information about [[GSoC/2019 | XMPP and the XSF at GSOC 2019 can be found here]]. | ||
Please not that the student's final project proposals may, but are not required to, be for projects on the ideas list. Students with their own GSoC project ideas are encouraged to talk to the respective project contact persons about the feasibility of their idea. | |||
= How to add your project idea = | = How to add your project idea = | ||
| Line 75: | Line 77: | ||
== Ignite Realtime's Smack == | == Ignite Realtime's Smack == | ||
''Website:'' https://igniterealtime.org/projects/smack/ | ''Website:'' https://igniterealtime.org/projects/smack/<br/> | ||
''Source Code:'' https://github.com/igniterealtime/Smack/<br/> | ''Source Code:'' https://github.com/igniterealtime/Smack/<br/> | ||
| Line 99: | Line 101: | ||
''Deliverables / Expected Results:''<br/> | ''Deliverables / Expected Results:''<br/> | ||
* Being able to connect to XMPP services via WebSocket. | * Being able to connect to XMPP services via WebSocket. | ||
* Definition of a WebSocket interface on top of the used WebSocket libraries, allowing for different WebSocket implementations. | * Definition of a WebSocket interface on top of the used WebSocket libraries, allowing for different WebSocket implementations (one implementation must be OkHttp for Android support). | ||
''Milestones:''<br/> | |||
# Design and implement WebSocket interface to use by XmppWebsocketconnection | |||
# Implement automatic XMPP client to server transport discovery (Implicit TLS, TCP, WebSocket, BOSH) | |||
# Interoperability tests against a different implementation | |||
# Plug Smack with WebSocket into Spark, our FOSS XMPP client | |||
Currently Smack can establish connections via TCP/IP and HTTP via BOSH. WebSockets are yet another way to connect to a server. | Currently Smack can establish connections via TCP/IP and HTTP via BOSH. WebSockets are yet another way to connect to a server. | ||
| Line 105: | Line 113: | ||
== Prosody IM == | == Prosody IM == | ||
'Website:'' https://prosody.im/<br/> | ''Website:'' https://prosody.im/<br/> | ||
''Source Code:'' https://hg.prosody.im/<br/> | ''Source Code:'' https://hg.prosody.im/<br/> | ||
| Line 115: | Line 123: | ||
''List of Teaser Tasks:'' https://issues.prosody.im/?q=state%3Dopen+difficulty%3Deasy | ''List of Teaser Tasks:'' https://issues.prosody.im/?q=state%3Dopen+difficulty%3Deasy | ||
''Contact chat:'' [xmpp:prosody@conference.prosody.im prosody@conference.prosody.im] | ''Contact chat:'' [xmpp:prosody@conference.prosody.im prosody@conference.prosody.im] [https://chat.prosody.im/ web client] | ||
=== Standalone mod_firewall === | === Standalone mod_firewall === | ||
| Line 144: | Line 152: | ||
The project would include: | The project would include: | ||
* Protocol design: develop and document (in XEP form) a protocol whereby a server may submit a stanza to the standalone mod_firewall and receive a decision. | |||
* Coding (Lua): adapt mod_firewall's core code to run standalone, and connect to servers as a component implementing this protocol. | |||
* Coding: Additionally add support for the new protocol to an XMPP server of your choice. | |||
=== Prosody plugin installer === | === Prosody plugin installer === | ||
| Line 194: | Line 202: | ||
== Poezio == | == Poezio == | ||
''Website'': https://poez.io | |||
''Source Code'': https://lab.louiz.org/poezio/poezio | |||
''Description'': poezio is a free console XMPP client, written in Python 3 using the ncurses library. | |||
''Project Contact Person'': Emmanuel Gil “Link Mauve” Peyrot [mailto:linkmauve@linkmauve.fr <linkmauve@linkmauve.fr>], Maxime “pep” Buquet [mailto:pep@bouah.net <pep@bouah.net>] | |||
''List of Teaser Tasks'': https://lab.louiz.org/poezio/poezio/issues?label_name=Easy | |||
''Contact chat'': [xmpp:poezio@muc.poez.io?join poezio@muc.poez.io] | |||
=== Multi-account === | === Multi-account === | ||
''Brief explanation'': Implement multi-account support in poezio (https://lab.louiz.org/poezio/poezio/issues/3456) | |||
''Involved technologies'': Python 3, XMPP | |||
''Mentors'': Emmanuel Gil “Link Mauve” Peyrot, Maxime “pep” Buquet | |||
''Deliverables / Expected results'': | |||
* Poezio with multi-account support | |||
* Being able to switch from one account to another (a la irssi, ^X ?) | |||
* Adapt UI/UX where necessary | |||
* Tests for the added/rewritten parts | |||
''Milestones'': | |||
# Get familiar with slixmpp’s stream handling and poezio’s internals. | |||
# Break down the <code>core</code> module further, to make it more testable and easier to integrate changes | |||
# Allow <code>core</code> to use multiple streams | |||
# Integrate these changes in the UI | |||
=== Infinite scrolling using MAM === | === Infinite scrolling using MAM === | ||
''Brief explanation'': Implement infinite scroll using MAM in poezio | |||
''Involved technologies'': Python3, XMPP | |||
''Mentors'': Emmanuel Gil “Link Mauve” Peyrot, Maxime “pep” Buquet | |||
''Deliverables / Expected results'': | |||
* Infinite scroll in Tabs (https://lab.louiz.org/poezio/poezio/issues/3052) | |||
* Tests for the added/rewritten parts | |||
''Milestones'': | |||
# Get familiar with slixmpp’s xep_0313 plugin and poezio’s Tabs (MucTab, ConversationTab, etc.) | |||
# Display a bunch of mock messages on scroll | |||
# Integrate MAM fetching during this scroll | |||
=== PubSub browser / management === | === PubSub browser / management === | ||
''Brief explanation'': Add a new tab to poezio to let the user manage PubSub nodes. | |||
''Involved technologies'': Python 3, XMPP, ncurses | |||
''Mentors'': Emmanuel Gil “Link Mauve” Peyrot, Maxime “pep” Buquet | |||
''Deliverables / Expected results'': | |||
* List the nodes present on a service | |||
* Display the metadata of a node | |||
* Display the configuration of a node | |||
* Allow the user to change the configuration of a node | |||
* List the items present on a node | |||
* Let the user publish a new item, or edit an existing one | |||
''Milestones'': | |||
# Get familiar with slixmpp’s xep_0060 plugin and poezio’s internals | |||
# Write some views displaying mock data in a new poezio tab | |||
# Wire up the views to the data provided by slixmpp | |||
== Dino == | |||
''Website:'' https://dino.im/<br/> | |||
''Source Code:'' https://github.com/dino/dino<br/> | |||
''Description:'': Dino is a modern open-source chat client for the desktop. It focuses on providing a clean and reliable Jabber/XMPP experience while having your privacy in mind.<br/> | |||
''Project Contact Persons:'' fiaxh and larma [mailto:team@dino.im <team@dino.im>]<br/> | |||
''List of Teaser Tasks:'' https://github.com/dino/dino/issues | |||
''Contact chat:'' [xmpp:chat@dino.im chat@dino.im] | |||
=== Jingle File Transfer === | |||
''Brief explanation'': The XMPP protocol includes a signaling system to set-up peer-to-peer connections, dubbed Jingle. One usecase for Jingle is to transfer files without an intermediary. This project idea is about adding support for file transfers using Jingle, fully integrated with current Dino features. | |||
''Involved technologies'': XMPP, Jingle/WebRTC, Vala, Networking | |||
''Mentors'': Marvin W (larma), fiaxh | |||
''Deliverables / Expected results'': | |||
* Support for sending and receiving Jingle file transfers | |||
* Automatically detect when peer-to-peer file transfer usage makes sense instead of http file uploads | |||
* Support for WebRTC-based Jingle transport for compatibility with web-based clients | |||
* Implement OpenPGP and OMEMO encrypted file transfers | |||
=== Inline link preview === | |||
''Brief explanation'': When sharing links using chat messages, it is often hard to see what is behind the link. Many clients thus provide previews of the linked content. We'd like to add this functionality and give a preview or embed for all kind of links, for example by parsing the Open Graph protocol, similar metadata or heuristic approaches. We also want to explore ways to send preview information with the message to reduce workload for the receiving devices. | |||
''Involved technologies'': XMPP, Vala, GTK+, Web, OpenGraph | |||
''Mentors'': Marvin W (larma), fiaxh | |||
''Deliverables / Expected results'': | |||
* User interface widget to display metadata, suitable for preview image, title, abstract and the original url/domain. | |||
* Automatic generation of metadata, working with major websites. This should be done in a generic fassion, not targeting a specific website | |||
* Design or reuse a specification for sending metadata with XMPP messages | |||