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>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>This project aims at providing network-wide Ad-blocking in Amahi HDA and to develop a centralized SSL Certificate Management Interface for Amahi.<br> Network-wide Ad-blocking feature would prevent a client from being served with any advertisements whether browser-based or in-app. This would also eradicate the need for installing any ad-blockers on every device separately within a HDA local network.<br> The centralized SSL Certificate Management Interface would enable Amahi to provide SSL certificates to the subdomains, Amahi provides to each HDA user in form of Amahi Dynamic DNS after installation. This would enable the HDA to serve the content intended securely. This subdomain is used by the Amahi user for connecting to their HDA remotely, using remote desktop applications or even hosting a website.</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.
<ul> <li>Push Health is a new Dashboard being built inside Treeherder to determine if a push is good based on calculations of Tasks and Tests success rate within the push and historically. The main aim is to add and enhance features which would make it more efficient for users like handling the bulk actions efficiently.</li> <li>InfraStructure Compare View is also a new Dashboard built inside Treeherder which would provide parity. There could be different machines and large changes to OS which one needs to verify and monitor the changes well.</li> <li>Improve Log parsing UX and general improvements to log viewer</li> </ul>
<p>MetricsGraphics is a great data visualization library. We hope to add natively support brushing and zooming feature (this part can also be used to create an overview plot) and provide some API to allow highlighting some data points. And we will also make some changes in the hover and click event to make it easier to create a tooltip.</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>AOM (Accessibility Object Model) is a JavaScript API that allows for modifying an accessibility tree like DOM. In this project, AOM phase 1 & 2 is implemented.</p> <h3>phase 1</h3> <p>The accessibleNode property is added to DOM Element. The properties of AccessibleNode correspond to ARIA attributes one-to-one, and web browsers can modify accessibility tree via this property. Note that if both an AccessibileNode property and its corresponding ARIA attribute are present, the AccessibleNode property overrides the ARIA attribute.</p> <h3>phase 2</h3> <p>AccessibleNode interface is derived from EventTarget so that accessibility input events and assistive actions become able to be processed via AccessibleNode. This enables web developers to check whether users are using an assistive technology or not, and this may leads to discrimination against some users. So, web browsers should ask users for permission of listening for accessiblity events before propagating those events to AccessibleNodes.</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>
<p>We have tons of testing jobs for a push but we don't want to run each of them, as they are time consuming and requiring hardware resources. The SETA (Search for Extraneous Test Automation) is a tool to help us find out which test job is necessary for detecting the failures. To make it more maintainable and more reliable, we need to re-write SETA and we may want SETA to support Taskcluster as well. Furthermore, we want Taskcluster can use SETA to schedule job and add document for SETA.</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>Perfherder is the dashboard which monitors and analyses performance tests run against Mozilla products. Currently, Perfherder provides aggregated results and graphical visualization of various test suites, but not for the individual test numbers that are used to generate them. For tests where there is a large natural variation in these individual numbers, it can be difficult to determine if there is a regression when the summarized values change because there could be many different underlying reasons for that. For these cases, a detailed view of the individual test results would be extremely helpful.The project will be about creating an easy-to-use web interface for visualizing this data that integrates well with the existing Perfherder views.</p>
<p>The project involves the redesign of Firefox Reader as well as working on the functionality related issues the current reader is facing. The redesign of the Reader has to be done so that it complies the Photon Design System and also offers a better user experience to it's users. Thus, using the knowledge of JavaScript, CSS, and web experience, the project aims at revamping the Reader View considering all the three reader modes ie. Light Mode, Dark Mode and Sepia Mode to enhance the reader's reading experience.</p>
<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>The goal of this project is to significantly increase test coverage and test quality in the WebAssembly Studio project. This will make it easier to detect bugs and breaking changes as the project evolves. While doing so, the idea is to simultaneously work on open issues related to the code that is tested during each iteration.</p>
<p>This is a project to implement new features, fix some existing issues and improve maintainability of the <a href="https://github.com/w3c/respec" target="_blank">ReSpec</a> project.</p> <p>Majority of time is expected to be spent in implementing a cross references feature. It includes creating a web service that integrates with ReSpec and expands the existing reference system to allow references across specifications. This task will require some investigation first as to how we can leverage the CSSWG’s <a href="https://api.csswg.org/shepherd/" target="_blank">Shepherd API</a> and its database. The web service may require creating a custom datastore that allows efficient search for multiple keywords. In the end, it'll provide an easy way to deep-link specifications to each other without much hassle.</p> <p>Other smaller tasks that I plan to work upon include:</p> <ul> <li>auto-normalizing references</li> <li>implementing automatic linking of pluralized words </li> </ul> <p>I would also like to work on some of the issues that might come up during the GSoC period.</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>