GSoC/2017/StatusReports/DavideRiva: Difference between revisions

From KDE Community Wiki
< GSoC‎ | 2017‎ | StatusReports
(Moved citations outside "work done")
Line 13: Line 13:
* [http://rivadavide.blogspot.it/2017/07/stop-writing-code-like-were-in-90s.html Stop writing code like we're in the '90s: a practical approach (PART I)]
* [http://rivadavide.blogspot.it/2017/07/stop-writing-code-like-were-in-90s.html Stop writing code like we're in the '90s: a practical approach (PART I)]
* [https://rivadavide.blogspot.it/2017/08/brooklyn-02-released-ready-for.html Brooklyn 0.2 released, ready for production]
* [https://rivadavide.blogspot.it/2017/08/brooklyn-02-released-ready-for.html Brooklyn 0.2 released, ready for production]
=== Citations ===
* [https://phoronix.com/scan.php?page=news_item&px=KDE-Brooklyn-0.1 KDE Brooklyn Chat Bridge Sees Its First Release]
* [https://sempreupdate.com.br/2017/06/conheca-o-kde-brooklyn-chat-messenger.html Conheça o KDE Brooklyn Chat, um IM versátil para múltiplos protocolos]
* [https://www.phoronix.com/scan.php?page=news_item&px=KDE-Brooklyn-0.2 KDE Brooklyn Chat Bridge Declared Production-Ready]


=== Code ===
=== Code ===
Line 34: Line 29:
=== Binaries ===
=== Binaries ===
* [https://mvnrepository.com/artifact/org.kde.brooklyn/canaveral Canaveral Maven repo]
* [https://mvnrepository.com/artifact/org.kde.brooklyn/canaveral Canaveral Maven repo]
== Citations ==
* [https://phoronix.com/scan.php?page=news_item&px=KDE-Brooklyn-0.1 KDE Brooklyn Chat Bridge Sees Its First Release]
* [https://sempreupdate.com.br/2017/06/conheca-o-kde-brooklyn-chat-messenger.html Conheça o KDE Brooklyn Chat, um IM versátil para múltiplos protocolos]
* [https://www.phoronix.com/scan.php?page=news_item&px=KDE-Brooklyn-0.2 KDE Brooklyn Chat Bridge Declared Production-Ready]

Revision as of 18:25, 9 August 2017

Brooklyn

Chat Bridge (now called Brooklyn) is intended to be a protocol-independent chat-bridge to allow messages forward to and from various chat systems.

It has to support Telegram, RocketChat and IRC but it has to be modular (for future expansions).

Current solutions do not offer an adequate integration because, besides generic text, not much is implemented. A big missing feature is the ability to exchange complex formats, such as images or file attachments.

Work report

Blog posts

Code

Contributions to external repos

Binaries

Citations