Fetching the latest programs, projects, and workspace data.
Find open source projects actively accepting contributors. Search repositories, filter by program milestones, difficulty tags, or tech stack.
Use our Orbit AI Matcher to find out! Get instant matching scores based on your developer skills, preferred frameworks, and contribution experience.
Convert your selected open-source project into a winning GSoC, LFX, or Outreachy application using Proposal Studio.
<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>
<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>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>
Build a dashboard that tracks contributor activity across GitHub repos — commits, PRs, issues — and gamifies the experience with badges and streaks.
Implement conflict-free replicated data type (CRDT) synchronization for synchronous multi-author document drafting.
Build a mobile-first catalog of active scholarships, GSoC roadmaps, and interview preparation materials.
<p>Chassis aims at defining open standards for various CSS/JS libraries and the web in general. The project aims to complete and deliver base styles for at least 5 UI components (e.g. tabs, modals, menus e.t.c) by the end of GSOC 2016. The project makes use of advanced SASS and JS for testing the components integration.</p>
<p>The Tails Server should provide a user-friendly way to start onion services that facilitate group collaboration, communication, and data sharing. See the <a href="https://tails.boum.org/blueprint/tails_server/" target="_blank">Tails Server Blueprint</a> for further information on the entire Tails Server project.</p> <p>During GSoC 2016, I plan to implement the basis of the Tails Server. It should be possible to use a GUI or CLI (I will implement both) in Tails to automatically install a service and set everything up so it is reachable as an onion service. It should be a generic solution which makes it easy to add many different services (web server, Etherpad, Mumble server, file sharing service, etc.), but I don't plan to add many of them during this project, because that might go beyond scope. I will instead use a simple web server serving a static page as a first service.</p> <p>The user should be able to choose:</p> <ul> <li>whether s/he wants to require client authentication (using HiddenServiceAuthorizeClient).</li> <li>whether the server's configuration and data and the onion service's keys and address are stored persistently (i.e. being restored after reboot) or not.</li> <li>whether the service is supposed to automatically start after booting Tails.</li> <li>whether it should allow LAN connections.</li> </ul>
Problem: Modern-day web browsers are pretty standardized and come with a certain guarantee that if a web page works in one browser, it will work in another web browser too except for a few minor cases. However, this is not true for email clients yet. The current state of the problem: The developer community is thus aligned to certain tricks and hacks to make sure the emails sent are properly rendered by these different email clients. There is no such package that solves this problem of creating responsive emails easily which can also handle cross browsers and clients compatibility issues. Proposed Solution to this problem: The end goal will be to implement a React-based component and utility methods-based lightweight library to provide a common interface for email building that users can install and use to build clean and responsive emails easily.
Create standalone Web Components for WCAG 2.1 AAA color contrast validation and palette generation.
<p>about:telemetry is present on all builds of Firefox as a way for users to view the data being stored and sent via Telemetry. It was built before Firefox had multi-process Telemetry and without a clear design. This has resulted in a confusing HTML UI and barely-comprehensible JS.</p> <p>The redesign will allow any users to understand what telemetry is and what data is sent, but it will also make it possible for developers to access the data faster, and in a more simple way.</p>
<p>The Moira API microservice serves as the backend for the web UI and it would be nice if the engineers who use Moira are able able to automate routine operations such as managing triggers with tools like Ansible. However, the API is undocumented currently and they have to study Moira’s source code or inspect the network requests from the web client to know the network requests they have to make and the responses to expect.</p> <p>As part of the 2020 Google Summer of Code, I wish to:</p> <ul> <li>Develop an up-to-date OpenAPI/Swagger description of the endpoints exposed by the API.</li> <li>Generate language-specific client libraries from the API description file - with special focus on a Golang client.</li> <li>Setup automated contract tests to test the OpenAPI document against the actual implementation.</li> </ul>
<p>The aim of the project is to implement the D3D11 backend for the gfx hardware abstraction layer (HAL) in order to get it ready to be used by WebRender for its rendering.</p>
<p>Mozilla Investigator(<a href="http://mig.mozilla.org/" target="_blank">MIG</a>) is a platform that provides distributed and real time digital forensics at the speed of the cloud i.e. obtaining forensic information from large numbers of systems in parallel. This project aims to implement a Linux Audit module for MIG which will provide support for syscall monitoring via the Audit daemon. This will enhance the capabilities of MIG to aggregate, mark, alert on related syscall events and store them in logs.</p>
<p>The goal of this project is to develop and implement a scheme to verify a library crate's adherence to the semantic versioning specification in the Rust language. This would allow to simplify the process of stabilizing and releasing libraries on <a href="https://crates.io" target="_blank">crates.io</a>, as many mistakes can be automatically guarded against.</p>
<h3>Problem:</h3> <p>JSON is a nice format to store data and it has become quite prevalent. If we are not overwhelmed by the diversity of JSON now, we soon will be. There will be more JSON, of more different shapes, as the number of connected devices and the information they generate continues to increase. Unfortunately, databases do not handle it well, often a human is required to declare a schema that can hold the JSON before it can be queried.</p> <h3>Project:</h3> <p>Created a Python SQLite connector to store JSON documents in SQLite so that they are accessible via SQL(using JSON Query Expressions). This will serve a basis for a general document-relational map(DRM), and leverage the database’s query optimizer. It is also responsible for making the schema and changing it dynamically as new JSON schema are encountered and to ensure that the old queries against the new schema have the same meaning.</p> <p>There is a test suite to confirm the expected behaviour: testing a variety of JSON forms and the queries that can be performed on them. Most tests are further split into three different output formats: list, table and cube. There is also a connector for Elastisearch and these two will be merged sometime in future.</p>
<p>I have good experience with TypeScript development, look inside to check it. It`s reason why preferenced project for me is “Flow to TypeScript migration”. And I bet then my experience will be helpful for community.</p>
<p>The goal of this project is to fully implement off main thread, speculative HTML parsing. Performing HTML parsing on a separate thread gives rise to the following performance gains:</p> <ol> <li>Web pages become more responsive, because the main thread becomes available to perform other functions, such as parsing CSS or handling input events.</li> <li>The parser thread can perform speculative parsing on the rest of the document while the main thread evaluates scripts. This ensures that the parser is not fully blocked while evaluating Javascript.</li> </ol>
<p>The goal of this project is to prevent sites from bombarding the browser with multiple non user initiated downloads. This would mean that a mechanism to differentiate between user initiated and automatically initiated downloads has to be established as it is undesirable to annoy the user with unnecessary warning and permission prompts even when the user himself has requested for a download.</p> <p>The project also involves implementing some form of data collection technique (via telemetry) to measure the effectiveness of the implemented logic.</p>
<p>Session Restore is important as a key feature of Firefox. Many people rely on it to re-open a tab from the past or recover from an unfortunate power outage. This project's goal is to make the process snappy and blazing fast.</p>
<p>At present, <a href="https://bugzilla.mozilla.org" target="_blank">bugzilla.mozilla.org</a> uses enter_bug.cgi to file bugs. This is particularly unwieldy due to a lot of reasons like two hop db access, backend template rendering and multiple views. This project aims at improving the current bug filing scenario by creating a new single page interface to file bugs, thereby increasing the overall performance and usability</p>
<p>In this project, File API and related functionalities will be completely implemented in the <a href="https://github.com/servo/servo" target="_blank">Servo browser engine</a>. With these features landed, the end users can upload files through form submission and interact with the local file content directly in browser; the developer will be endowed the ability to read local file content programmatically in either sync or async way, create Blob URL and use them in a very flexible way. In addition, a dialog UI will be integrated to support file picking.</p> <p>For more information, see <a href="https://github.com/izgzhen/gsoc-file-support" target="_blank">the meta-tracker of this project</a>.</p>
<p>The purpose of this project is to allow the selection of several tabs in Firefox and thus perform specific actions on them at once. These actions include closing or moving tabs into a new window. The Shift and CTRL/Cmd keys could respectively be used for a range select or for individual item select.</p>
<p>Design and partially implement a research operating system that uses WebAssembly to implement software-isolated processes (SIPs) that run in ring 0 in order to allow architecture-agnostic compiled binaries and possibly attain higher performance due to not needing page-table switches and interrupt-based system-calls.</p>