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>vulture is a tool which detects and reports dead (unused) code and coala is an automatic linter. The motivation of this proposal is to:</p> <ul> <li><strong>Extend vulture as an API</strong> which respects the Bear's Input Output method</li> <li><strong>Refactor VultureBear</strong> such as to use the new API - this would highly optimize it's performance.</li> <li><strong>Enhance python whitelist</strong> and making it <strong>default</strong> for every run.</li> <li>Implement a method to <strong>acquire the source range of dead code</strong> - currently, only the beginning of the dead code is reported.</li> <li>Revamp vulture's scavenging property by additional <em>detection of the cases which render the <strong>code unreachable</strong> </em>.</li> <li>Implement a <strong>confidence value with results</strong> - this would be necessary when implementing <em>auto</em> removal, as we would need a proportion of surety or certainty with which we report dead code.</li> </ul>
<p><strong>corobo Enhancement</strong></p> <p>The goal of this project is to make corobo secure by reducing its surface vulnerability. It also includes implementing a better testing infrastructure to test plugins like LabHub, as well as to make the existing plugins configurable so that they can also be adapted by other communities to cater their needs.</p>
<h4>GitMate for all!</h4> <p>This time with user configurable plugins!</p> <h3>About the product</h3> <p><strong>GitHub</strong>, <strong>GitLab</strong> and <strong>BitBucket</strong> support webhooks for common events like opening/closing/commenting on Merge Requests, creating Issues, etc. These webhooks could be configured for automated response using their own API's for comments, tests/integrations, etc. <strong>GitMate</strong> merely acts as a tunnel for these events and responds accordingly. The interface for these API's is held by its wrapper library, IGitt.</p> <h3>Aim of the project</h3> <p>This project is aimed at extending the support for <strong>GitMate</strong> to <strong>GitLab</strong> and <strong>BitBucket</strong> repositories. This adds up to unified and automated code analysis and maintenance on the big three code hosting platforms.</p> <h3>Implementation</h3> <p>This project consists of implementing <strong>GitLab</strong> and <strong>BitBucket</strong> interfaces in <strong>IGitt</strong>, following the already implemented <strong>GitHub</strong>'s convention, while simultaneously creating webhook responders and tasks for the same on <strong>gitmate-2</strong>.</p> <p>Extending plugins is quite easy on <strong>gitmate-2</strong> following <code>gitmate_testplugin</code> as an example, thanks to its plugin-based architecture.</p>
<p>This idea is aimed to improve the experience of Bone101 to make the most use of it to be friendly to novice developers, allowing them to work with BBUI inside tutorials, write python code beside Javascript, and discover new experience of Bone101 in Cloud9 IDE.</p>
<p>Gitmate, a git workflow management bot created by coala, hasn't been actively maintained in the last 3 years. My project aims to update it and bring it back to active use for the coala community. I plan to undertake various improvements to Gitmate as well as IGitt, the underlying library that powers Gitmate's git operations.</p> <p>My primary goal is to set up Gitmate for the coala community. I will also upgrade both Gitmate and IGitt to the latest API versions of Github, Gitlab and Jira and add support for the latest python versions by upgrading the dependencies. Along with this, I will update various aspects of the documentation of both these projects, improve testing, and ensure that the Continuous Integration setup is in perfect condition. The last phase of my project will involve merging three pull request plugins into a combined plugin and improving various pull request events. Throughout the project, I will work on feedback from the coala community and try my utmost best to improve their experience with using Gitmate.</p>
<p>Goal of this project is to use coala's json output format, convert it to various test result formats and then integrate these test format reports to various tools like CricleCI, Appveyor, Jenkins and Phabricator. Result format inconsistencies has been a problem for a long time but the benefit of converting the static analysis results into a test result format can provide tight integration with various systems. This project also aims to provide our upstream linters with some of these test formats using the Result Reporter Tool library and help developers in extending this project to other formats and uses in the future.</p>
<h3>Debug and Profile Bears</h3> <p>The aim of this project is to create a better quality Bears by creating a tool which will have the ability to jump directly into Bear code and move through it using a debugger interface such as pdb and make debugging of Bears as easy as writing the Bear.</p> <p>A Debugger should also have the ability to investigate the settings passed to the Bear and inspect the results created by the Bear.</p> <p>Implementation of a Profiling Interface which will help Bear writer to create a Better Performant Bear.</p>
<p>coala community has grown substantially over last few months. To make it easier on maintainers to cope up and still be a welcoming community for new contributors.</p> <p>Currently, cobot is a hubot instance, scripts for which are written in Coffeescript. This project is about porting the existing functionality of cobot to a python bot framework errbot and adding topic modelling to cobot to auto respond with correct(probably) answer when someone asks a question.</p> <p>Another reason for porting: coala is python inclined community, cobot will receive more contribution if the devs can write plugins for cobot in python.</p> <h5>Addition of an interesting feature: Topic-Modelling for auto-responding FAQs</h5> <p>As previously mentioned, coala has been growing substantially and there are new contributors frequently and same questions are asked frequently. This feature aims at using Natural Language Processing and matching the asked questions with the sections in docs and then respond with a relevant section. This saves time for the users as well as developers significantly. Also, since this a bot interaction one doesn't tire out the opposite person responding.</p>
<p>Currently, the coala Online module lacks support for all the bears. Bears with non-optional settings are ignored. The first goal of this project is to have a powerful online module that provides backend and frontend interface to be able to do code analysis with any given bear. The project focusses on enhancing coala-html by introducing results and bear search and filtering on basis of parameters. The next thing where the project will help us is that it will provide an effective bear search mechanism on coala.io and make projects.coala.io configurable and extensible.</p>
<p>It is tough for a new user to quickly grasp and start using the settings provided by coala. The user needs to be aware of the bears he might possibly need for his project and also the settings provided by the bears. Many of them directly opting for individual linting softwares when coala can provide a unified environment for them. This way many are never able to unleash the true power of coala. The first runs of coala should involve as less user interaction as possible, so that new users can realize how hassle free it is to use coala <strong>over</strong> a collection of linting technologies. Quickstart should be able to learn the bear settings from the project.</p> <p>This project adds the capabilities to coala-quickstart by making smart analysis, depending upon the format already followed by the users, may it be separate formatting used for separate files or for a separate group of files (eg. grouped in a specific folder) or for different language files.</p> <p>Many major communities don't use a fixed coding styles that the bears provide. The quickstart should be able to adapt itself and generate a config file which matches as closely to the codebase as it possibly can for easy and quick adoption.</p>
Bela is an open hardware and software platform for creating beautiful interaction with sensors, sound and it is designed for artists, musicians, researchers and makers, Bela brings the power of ultra-low latency interactive audio and sensors to digital systems. Bela Platform uses the Bela software which is a customised Debian distribution including a custom xenomai kernel, minimal clutter, and custom systemd configurations and It takes advantage of features of the BeagleBone computers and can achieve extremely fast audio and sensor processing times. Bela Image development repo is heavily based and which was initially inspired by Beagleboard Image-builder scripts. Currently, the Beagle board Image development repo diverged greatly from a common functionalities of building Images. Now, there is a requirement to "rebase" the functionalities of the Bela Image builder repo to the Beagleboard Image builder one. As the two codebases are drastically different. This project is to Improve the maintainability of the Bela Image development by adding the functionalities of the Bela Image builder repo to the BeagleBoard Image builder repo.
<p>The idea, here, is to integrate <strong>pyflakes-enhanced AST</strong> into coala as a <strong>metabear</strong> which can then be used to develop various plugins. The second part of the project involves redesigning flake8 plugins <strong>flake8-future-import</strong> and <strong>flake8-builtins</strong> in such a way that they use pyflakes-enhanced AST over python AST. Finally, a wrapper is to be created which supplies a python AST to flake8 plugins so that they work as it is.</p>
<p>The project focuses on improving coala's dependency management for installing bear and their dependencies on multiple platforms. Specifically, the core focus is on trying to automate dependency management using Ansible playbooks and roles. Additionally, improving the existing dependency management API by introducing a <code>PlatformRequirement</code> class for system specific package managers and fixing and improving the exiting cib install bears tool which uses the dependency management API by adding complete test coverage.</p>
<p>This project aims to implement a library that integrates with the existing coala code and allows writing native bears for coala that can leverage the power of ANTLR and enable them to advanced linting routines based on the parse-tree of a language with a given grammar.</p>
In the existing Karmada architecture, each component should have its own unique certificates to ensure clear identity and security. Best practices dictate that each component's name be used as the Common Name (CN) in its certificate to facilitate identity differentiation. However, currently, all Karmada components share same identical certificate content, leading to confusion and potential security risks. The objective of this project is to enhance the compliance of the Karmada certificate system by ensuring that each component possesses distinct certificates that reflect its identity. This will improve system security, reduce management complexity, and align with industry standards. This project aims to achieve the following standards: 1. Utilize a single CA certificate for the entire Karmada system. 2. Issue individual server certificates for each server component, using the component name as the CN. 3. Issue individual client certificates for each client component, using the component name as the CN, same client can use consistent certificate for different servers. Expected Outcome: 1. Complete the issuance of different certificates for 8 server components and import the certificate content into the corresponding certificate Secrets. 2. Complete the issuance of different certificates for 11 client components and import the certificate content into the corresponding certificate Secrets or Config Secrets.
<p>This project automates the task of sensing the health of the many Red Hen Lab remote capture stations, which are Raspberry Pi devices, and provides a responsive web dashboard that the management entity can use to easily perform her monitoring tasks. This has been achieved by implementing a set of scripts, whose execution in the capture stations is controlled over SSH and a comprehensive monitoring system using a centralized server (called Coop) built on the MERN stack - MongoDB, Express, React, Node.JS.</p> <p>The server consists of a Telemetry component which can communicate with the capture stations through SSH, a Control component which performs tasks like addition and updation of station metadata in the mongo database as well as report generation and backup upon user command and a frontend that allows visualization through a centralized dashboard that can be accessed through a desktop or mobile device with appropriate security credentials.</p>
<p>jQuery Mobile currently has a large number of open issues (~300). To maintain JQM’s vitality, this backlog should be necessarily cleared. This summer project aims to bring down this number to 50 (fifty) and categorize them in a proper and manageable manner and on the same time handle the communication and response to community both during and after the summer.</p>
<p>The advantages of organizing a program into several files or modules are similar to authors organizing a book into several chapters and sections. The structure helps people who aren’t yet familiar with the code find what they are looking for and makes it easier for the programmer to keep things that are related close together. This project aims at developing a module system for the wonderful Hammer.js library that is flexible, predictable and extensible in the new ES6 version of javaScript.</p>
<p>Testings of JavaScript application sometimes include modification of their own environment, such as global/native objects extensions and DOM manipulations. To avoid undesirable side effects, they have to be executed in a clean environment as much as possible.</p> <p>Since Intern JavaScript testing framework doesn't have this as the core feature yet, users have to manually reset or sandbox everything they care. The aim of this proposal is to solve this issue by implementing “sandbox interface” to Intern core API and make users get rid of the difficulties.</p> <p>The timeline of this proposal includes the following:</p> <ul> <li>Make friends with Intern's codebase</li> <li>Investigate and discuss with my mentors how this feature will be implemented</li> <li>Write actual codes</li> <li>Fix bugs</li> <li>Test and document everything I implemented</li> </ul>
<p>The goal of this project is to develop a framework for the development and presentation of interactive tutorials in order to provide a full learning experience.</p>
<p>Projects like jQuery and Angular JS are written primarily with javascript and make extensive use of git as their version control system. Using git means that developers write commit messages. Nice and clean commit messages that adhere to an agreed-upon style are very common. So, implementing a way to validate these messages, like the commitplease project, makes a lot of sense. Currently, the commitplease project supports the jQuery style commit messages. Extending its support to the Angular-style ones (and possibly others) is a logical goal.</p>
<p>My project aims to improve the development of testing tools through a common interface for reporters. It is hard because there are already so many tools and each one has its own interface and they will no renounce so easily, but we will try.</p> <p>To achieve this we will implement the specification in a quite popular testing framework, Qunit, and then we will try to engage also other people, mainly maintainers of other open source testing solutions.</p> <p>This way any one that will build in the future a new testing tool will be encouraged to use this interface, because it is time saving and less code to write, it is in the spirit of code reuse.</p>
The OpenPrinting website is an essential platform for Linux printing resources. The current system lacks modern UI enhancements and optimized SEO. Additionally, the existing Foomatic lookup page relies on SQL and dynamic web technologies, which I will be migrating to a fully static implementation. This transition will eliminate dependencies on an SQL server and a web server, with everything being managed exclusively on GitHub. This project aims to modernize the OpenPrinting website by migrating it to Next.js, a powerful React framework that ensures scalability, performance optimization, and maintainability. The transition will include: - Rebuilding the site with a modular, component-based Next.js architecture. - Migrating the Foomatic lookup page to a static page for improved efficiency. - Implementing Server-Side Rendering (SSR) and Static Site Generation (SSG) to optimize performance. - Deploying the new website with a CI/CD pipeline for automated updates and maintenance.