Explore Projects

<p>Nowadays, Ceph supports Kafka, HTTP and AMQP(ver 0.9.1) endpoints natively from the Ceph Rados Gateway. However, to allow for a large variety of endpoint types to integrate with Ceph, we are encountered with some inconvenience on these various protocols from different service infrastructure. The workaround for the notification brings the burden of adaptor deployment, communication and translation overhead.AMQP 1.0 is the latest standard for AMQP. It focuses on core features which are necessary for interoperability at Internet scale, and it contains less explicit routing than previous versions. Even though Ceph has supported the AMQP(ver 0.9.1) natively, the gap between these two protocol specifications cannot be ignored. The next level AMQP(ver 1.0) requires a completely different client library. AMQP 1.0 brokers are supported by Apache Qpid/ActiveMQ project and Azure platform, etc. To address this problem, we should support the AMQP 1.0 natively in the Ceph Rados Gateway. This requires adding the qpid-proton client library to the Rados Gateway code base, and use it to send notifications to AMQP 1.0 compatible brokers.</p>

<p>The cohort module is quintessential for providing an integrated, user-friendly and customizable monitoring tool for Households (generalized as cohorts) in a Medical Informatics System.</p> <p>Currently, the cohort module provides significantly limited functionality for displaying, managing, editing and keeping track of cohorts.</p> <p>The primary objective of this project is to extend this module to provide enhanced functionality and extended support for Cohort Forms, In-depth Cohort Search Mechanism, Detailed Data Display and an Expressive and Navigable UI.</p>

<p>Click boards are a flagship hardware product line of MikroElektronika with over 600 add-on boards ranging from wireless connectivity clicks to Human Machine Interface clicks for interfacing with peripheral sensors or transceivers. Most of the Click boards use the common protocols like SPI,I2C or UART to communicate with the Beaglebone and thus the support for them now is accomplished via device tree overlays via the bb.org-overlays repository. This requires /boot/uEnv.txt to be modified to load the drivers at boot, requiring at least one reboot to enable the support in a potentially error-prone way.</p> <p>The Greybus Simulator is a tool which simulates an AP Bridge, SVC, and an arbitrary set of modules plugged into Greybus. Greybus already provides most of the interfaces used on click boards and utilises manifest files to enumerate hardware at run-time.This project aims to enable Click Board Support via Greybus Simulator by writing suitable Manifests according to the Click board Specifications and by simply copying the manifest to a hotplug-directory a click board can be loaded,which would make the interfacing a lot easier.</p>

<p>This project goal is to make Linkerd officially support ARM architecture</p>

<p>Develop new modules to build list and Improve/extend selection base solution infrastructure for WP1.</p>

<p>The main goal behind this project is to create a Rocket.Chat app that adds the support of transcribing previously sent audio messages on demand, and new audio messages sent with the transcription selected.</p>

<p>libModSecurity (aka ModSecurity v3) is a major rewrite of standalone ModSecurity (v2.x) which have high dependencies on 3rd party project including Apache. Now the project is splitted into two components namely connectors and core. Where the core is underlying library and connectors are the consumer of this library. This way ModSecurity cores becomes completely independent of underlying web server. In this project we will be extending the support of ModSecurity to Node.js by creating a ModSecurity connector for Node.js. This will provide ModSecurity support to a large community of Node.js developers as there are not many waf available in Node.js.</p>

<p>The project titled "Integrated Personal Email Gateway" aims at facilitating users with an ability to reply messages by directly replying to emails they received whenever they are away. This allows them to interact with their fellows and provide support to the community even offline. Thus providing community with another great feature to boost communication.</p>

The ultimate goal of the project is to create a full-stack React component node module of the RocketChat application that would be fully configurable, extensible, and flexible for use. It will allow users to integrate RocketChat into their React web-based applications easily also providing an amazing developer experience while creating in-app chat applications.

<p>The aim of this project is to add support for HEIF/HEIC files in FFmpeg. High Efficiency Image File Format (HEIF) specifies the storage of individual images, image sequences and their metadata into a container file conforming to the ISO Base Media File Format (ISOBMFF). This format has increasing usage in mobile devices.</p>

KubeArmor is a cloud-native runtime security enforcement system that restricts the behavior (such as process execution, file access, and networking operation) of containers and nodes (VMs) at the system level. This project aims to support KubeArmor on OpenShift. The work will include compatibility analysis of KubeArmor on OpenShift, finding limitations (if any), and eventually testing it on OpenShift.

This integration will bring the support of Figma right into Rocket.Chat using Rocket.Chat Apps. With the help of this plugin, teams can create new comments on Figma files, reply to comments, and get notified on different activities in Figma directly from Rocket.Chat. This will help in improving workflow and extending the functionality of the design system.

Create a simpler desktop application where there is a simple channels list on a little window and each chat will open in another separated window, making it possible to talk with people without opening a big window. Making the usage of Rocket.chat more seamless. This project will make extensive use of Rocket.Chat's In-App Chat APIs (REST APIs). The application will be deployable on all platforms supported by Electron - Windows, Mac, Linux, and more

<p>Bring access of Rocket.Chat into the world of 100 million+ Alexa enabled devices. The project's aim is to create innovative, high valued user experiences to the Alexa ecosystem - powered by open source Rocket.Chat. An Alexa skill will be developed for Rocket.Chat with various new features and support for upcoming features along with improved Voice User Interface using the latest SDKs made available.</p>

<p>End-to-End encryption is a highly important feature in chat clients, allowing users to talk to each other securely without fear of message interception or surveillance. The current implementation of OTR in Rocket Chat has a number of limitations, including no support for offline chats. In this project, I will improve Rocket Chat functionality by integrating the Signal protocol, which provides confidentiality, integrity, authentication, forward secrecy and asynchronicity, among other security features, with Rocket Chat.</p>

<p>This project aims to extend the current DSL based component code generator to also generate RoboComp components that can be run in the browser. The new components generated will be using javascript and as an html file should be able to be deployed in the browser and also to communicate with the non JS components already developed earlier (laser, keyboardcontroller, joystick etc.). It is an interesting diversion from current robotics technologies based on C++/ python to use JavaScript to code some highly concurrent components.</p>

<p>The v2+ of the android app of Rocket Chat is already under progress and seems to work well so far. For the summer of code'18, I intend to extend Rocket Chat to be used in ubiquitous platforms like android <strong>wear</strong>. I'll be building the wear app from scratch this summer. Apart from this, I also intend to work on more advanced features for the android app like integrating <strong>google smart lock</strong> , adding support for <strong>private chat groups</strong> , and will keep working on issues reported during the GSoC period to improve the user experience for the mobile app.</p>

Every year, it is understandable that open-source organisations invest a significant amount of time and effort in preparing for GSoC. That's why the Google Summer of Code Community Hub will act as an essential tool to help prepare and support every organisation before and during the program. The GSoC Community Hub is designed to be a one-stop-shop for open-source groups to interact, collaborate, and monitor their progress before and during GSoC. It provides an all-in-one platform that combines chat rooms, forums, custom leaderboard, community meetings, communication over specific GitHub repositories, and other essential features, making it easier for mentors and mentees to find and collaborate on relevant projects.

Microsoft Teams is unquestionably the most popular and frequently used closed source team collaboration system in the world. Many administrators and users of open source Rocket.Chat team chat will have needs to bridge between their open source users and legacy users still on Teams. This project will create a Rocket.Chat App that will act as a bridge between Rocket.Chat and Microsoft Teams. Users on one system should be able to chat with the other through shared channels. Rich interactions including DM, emojis, embedded graphics, shared youtube links and so on should also be supported. A Teams Bridge Rocket.Chat App will be published on Rocket.Chat Apps Marketplace together with documentation for how to use it.

<p>Integration with Google cloud storage is a long requested feature in Rocket.Chat. This project aims to integrate Google Drive and Dropbox storage with Rocket.Chat, thereby allowing users to authorize Rocket.Chat to access their Drive/Dropbox accounts in exchange for a bunch of features. These include (i) upload content to Drive/Dropbox accounts directly from Rocket.Chat, (ii) create Google docs, slides and spreadsheets in Rocket.Chat for enhanced real-time collaboration, (iii) browse and download Drive/Dropbox content from Rocket.Chat using GUIs that respective APIs provide, (iv) supporting features such as file preview for Drive content and finally, rigorous tests for the project implementation.</p>

This project proposes a short-lived, cryptographically signed QR code on the Rocket.Chat's web client login screen, which authenticated mobile app users can scan to log in to the web client instantly—eliminating the need for manual credential entry. By leveraging ephemeral tokens that refresh every 60 seconds and real-time notifications over WebSocket, the approach safeguards user sessions while streamlining the login experience. Specifically, the solution integrates secure token generation and validation in Node.js, a React-based desktop UI displaying the QR code, and a React Native-based scanner accessible only to authenticated mobile users. This modern, frictionless authentication method enhances both usability and security within the Rocket.Chat ecosystem.

<ul> <li>Create a new initial landing page with suggested ZIM files that a user might want to download and improve the download management UI to flow more intuitively, guiding users to get the content that they want.</li> <li>Make the switching of tabs more intuitively and also show the preview of tabs.</li> <li>Improve language selection functionality allowing users to find the supported languages easily.</li> <li>Improve the bottom toolbar to make it more user-friendly.</li> <li>Improve the bookmarks screen with an option to show bookmarks from the current ZIM file or from all ZIM files.</li> <li>Add a screen to show the history of pages visited by the user.</li> <li>Move help to a separate screen.</li> </ul>

A Rocket.Chat channel could be embedded into some existing web applications via the Embedded Chat component. Currently, the available integration surface and features of Embedded Chat are rather limited. This project aims to significantly expand the applicability of Embedded Chat to a wider range of web/mobile applications built on the most popular frameworks such as React, React Native, and more; and hosting platforms such as WordPress and Ghost via HTML embedding. The goals of the project are: ● Separating various parts of the project into their package - API, react, react native, auth, etc. ● Reducing the bundle size. Currently, it is very large. ● Replacing HTTP calls with real-time DDP communication wherever necessary. ● Creating libraries for react-native, react, etc. ● Giving more flexibility in authentication methods. ● Slash command support ● Introducing theming for client libraries ● HTML embed