Explore Projects

The Whiteboard Integration project enhances collaborative experiences in Rocket.Chat by introducing a powerful Whiteboard App. This integration facilitates real-time visual communication, making it easy for users to create and share diagrams, drawings, and more. With a user-friendly interface and features like slash commands and action buttons, users can effortlessly create and collaborate on whiteboards. The project also offers a convenient local setup guide, allowing users to deploy the app locally for testing. This integration adds a new dimension to communication within Rocket.Chat, fostering creativity and efficient collaboration.

<p>To create an Angular 4 based Progressive Web App (PWA) lite client that would be able to used as an alternative of native clients like Rocket.Chat.Android or Rocket.Chat.iOS client.</p>

Currently, Rocket.Chat Room Header actions follow rigid layout rules, often hiding critical tools in overflow menus and reducing workspace flexibility . This project proposes a configurable layout engine that allows administrators to define action ordering and pinning (featured) via a workspace-level JSON setting. Key deliverables include a dynamic administration UI built with Fuselage, a per-user Feature Preview for progressive rollout, and a comprehensive test suite using Jest, Playwright, and axe to ensure 100% scenario validation and zero accessibility violations .

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>This project aims to create a new kind of channel where instead of sending messages, users would be able to create task cards with several custom fields.</p> <p>Those tasks would then work as a thread header, allowing comments in the format of a thread.</p> <p>The tasks will be stored in a new collection in MongoDB and MiniMogo</p> <p>The client would then render this task message with a different renderer, displaying the assigned user and the current task status</p>

GitHub is the largest centralized repository for hosting open source projects and this app will enable the users to perform many GitHub activities right from Rocket.Chat. In this project, I plan on developing the GitHub app for Rocket.Chat which will improve the overall collaboration between developers. This app will enable users to fetch data from a repository, subscribe to various repository events, perform extensive GitHub search queries, open new issues, assign issues to team members, review pull requests and do much more right from Rocket.Chat.

<p>Lightning has traditionally been using XUL for its user interface. To modernize, we would like to convert dialogs, tab content and other parts of the user interface to HTML. The new components should use web standards as much as possible, avoiding extensive use of third party libraries.</p>

<p>In the Debugger tab of the Firefox DevTools when the debugger is paused on a breakpoint users can see the values of variables by hovering over them. This project will add inline values beside the variable name so that the user can get a quick overview of all the relevant variables easily without having to hover over each one of them.</p>

<p>Balrog is the new age update server used by Mozilla to serve updates to Firefox. This project aims to address a situation in Balrog where multiple locale updates caused a race condition, leading to unnecessary retries by submitter jobs. This project proposes to resolve this situation by using an algorithm similar to a three-way merge algorithm, but for nested JSON data.</p>

<p>In a matter of weeks, HTC and Oculus will begin shipping the first generation of VR to tens of thousands of consumers. While VR content is easy to consume, it is hard to produce. A-Frame, with its HTML-like syntax, has the potential to enable far greater participation in this new medium; but for this to happen, more documentation needs to be created, tutorials made available, functionality extended, and showcases created. I propose to help meet these needs with two projects: (1) producing a component to wrap d3.js, and (2) developing support for 3D panoramas.</p>

<p>The custom element API allows javascript authors to create reusable web components. The author can create custom element constructors and setup callbacks for when various reactions occur on the element such as when its attributes are mutated. While this was possible in the past with non-standard elements, this API allows authors to have more functionality and ensures that these custom elements will not be broken by future changes to the web platform. While this is a new API, new web frameworks such as A-Frame and Polymer are built using custom elements. As the usage of custom elements increases, it will be important that Servo supports this API.</p>

<p>Currently Thunderbird uses mbox as primary storage format for mails (locally). All the mails in a folder are stored in the same file with the same name as the folder and no extension. The messages are separated from each other by a "From - " line. The maildir format is also supported, but there is no converter for it yet. The goal is to implement a component to migrate a store from the mbox format to maildir format. In order to achieve the goal a new store should be created and all the messages from all the folders of the old store should be moved to respective folders of the new store in maildir format. The folder hierarchy of the old store needs to be maintained in the new store. The message copying should be carried out in a worker using OS.File to prevent other tasks from getting locked up for long.</p>

<p>An update to the public suffix list (PSL) is shipped bundled with Firefox releases. The current system creates the DAFSA binary file at build time. The list has to be manually updated with every new release and cannot be updated for people running old versions of Firefox. I will be working to create an update system using the remote-settings API in Firefox to deliver an updated list to the client periodically, the period is yet to be determined. The list will be published on the Mozilla remote-settings servers and be shipped as a binary. This file format allows for shipping the list quickly over the network as it is orders of magnitude smaller in size an can be parsed much faster than raw text.</p>

<p>This proposal is about developing Fretboard: an A/B testing framework for Android written in Kotlin, taking as foundation the Switchboard fork used in Firefox for Android.</p> <p>The goal is to make a reusable library decoupled from both the client and server storage mechanism which will allow to make A/B tests on Android apps: check if a user is part of an experiment, schedule frequent updates, get experiment associated metadata, as well as force specific experiments value in order to test the app, for example.</p> <p>It will also allow security features: certificate pinning and experiment collection signature verification. The library will be deployed to jcenter and also integrated into Firefox Focus.</p>

<p>“Pontoon is Mozilla's localization tool, used by hundreds of contributors to translate Firefox, mozilla.org, and many other Mozilla products. It is critical to shipping Firefox to as many users as possible, all around the world.”</p> <p>Since active user participation and onboarding is one of the key components for the achievement of Pontoon’s goal towards localization, the idea is to improve the experience of first-time users of Pontoon by defining a "path to first contribution" explaining the basic flow and ins and out of contributing towards localising Mozilla applications by adding a guided interactive tour, a walkthrough for explaining basic functionality for unauthenticated user and a better “Learn More” link replacing the current gitbook link and making all of these as smooth as possible.</p>

<p>Firefox for Android is one of the most widely used browsers. The team is currently involved in reducing the size of the Android Package - APK. As a first step of this ongoing effort the fonts are excluded from being packaged along with the APK. The scope of reducing the size of the APK does not stop there. There are various opportunities and scopes for further reducing the size of APK such as excluding hyphenation dictionaries, translation and so on from being packaged. The task is to download the excluded assets from the server. This initiative can effectively reduce the size of the APK File.I propose to implement features that enables the browser to download the assets like hyphenation dictionaries at the runtime.I also propose to implement a helper class which can be used to smartly schedule the downloads based on the conditions and smartly reschedule the failed downloads and exclude other assets like localization files.</p>

<p>Firefox Developer Tools offers good tooling for monitoring HTTP traffic between the current page and the server. The existing Network panel allows intercepting and inspecting all data transferred over the wire including headers, GET/POST data, responses, detailed timings, etc. Unfortunately, Firefox Developer Tools doesn’t offer a way to inspect WebSocket (WS) traffic in Firefox Quantum.</p> <p>This project aims at providing support for WebSocket monitoring and inspection in Firefox Developer Tools. The feature should be built on top of the existing Network panel user interface (UI) and be responsible for visualizing data (i.e. WS frames) sent through a WebSocket connection. Users should be able to perform common tasks such as pausing/resuming monitoring, clearing frames, searching/filtering, looking at summary data etc. Light and Dark Themes should be supported.</p> <p>Furthermore, support for popular protocols such as Socket.IO, SockJS, plain JSON, and MQTT will be implemented. There is also ongoing work for supporting binary message viewer and showing WebSocket messages in HAR exports.</p>

<p>The android version of Amahi works well. For Summer of Code’ 17, I will mainly be focusing on adding the following functionalities to the app:</p> <ul> <li>Updating Designs &amp; provide backwards compatibility.</li> <li>Adding Chromecast Support.</li> <li>Developing a new module for Android TV.</li> <li>Adding support for secondary user.</li> <li>Adding upload functionality (Manual as well as Auto Upload).</li> <li>An Auto Back up setup which directly backs up your phone data to your HDA.</li> <li>Improving the caching mechanism for the Thumbnail Previews.</li> </ul>

<p>I would like to contribute to the mobile department of Amahi by adding new features to their iOS application and improving the user experience. I have many ideas to make the app look even better and to make it more user friendly.</p> <p>I would add a walkthrough screen to the app where the user can learn more about Amahi's services and also other features such as upload and delete functionalities. I would make it possible for the user to share files easily too via third party apps such as emal, iMessage or Facebook.</p> <p>I also believe that Chromecast support would be greatly appreciated by many users as well as improved searching and filtering features would be very useful too. I would love to work on these new features to provide an even better user experience to Amahi's users.</p>

<p>Improve the app installation process using docker. Dockerize existing applications and add support for more applications. Improve plugins and overall performance of the platform.</p>

<p>I propose to implement Home Assistant and many of its apps and features in Amahi App store and try to integrate well with Amahi. So, users can control their home assistant while being powered by Amahi platform. This will be better than HomeAssistant in Raspberry Pi. Pi is a low powered device. Compared to that, amahi works on a full-fledged PC. So, it will give more power to users to control their devices. I will also implement amahi 12 in Fedora 30 using anaconda addon, which is in PYTHON.</p> <p>If time left then I propose to improve the installation experience of Amahi by completely removing the method of INSTALL CODE and setting up basic Amahi HDA without an API key. This will remove the hassle of registration before using Amahi.</p> <p>Since, I have worked with Amahi before, especially with installing and setting up Amahi division. I have deep knowledge of how Amahi gets set up. I have done extensive app testing in my previous GSoC so, I have some knowledge of Amahi Apps.</p>

<p>The Aim of the project is to add more functionality to the Android app.</p> <p>Following features can be implemented in the app:</p> <ul> <li>Sharing of folders</li> <li>Secondary user login</li> <li>Support for remembering user preferences like audio position, video position, sorting option, etc.</li> <li>Support for displaying recent files</li> <li>Theme and Material Design implementation</li> <li>Adding automated UI testing protocol</li> <li>Implementing ExoPlayer for playing music</li> <li>And many more small features.</li> </ul>

<p>This proposal aims at implementing new features in the Amahi iOS project. Ease of use and efficient architecture is kept in mind while implementing every feature. The features that I'll be working on include :</p> <ol> <li>Upload/Delete Feature.</li> <li>Continuous Music play.</li> <li>Metadata Display.</li> <li>Thumbnails.</li> <li>Secondary User Login.</li> <li>Chromecast Integration.</li> </ol>