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.
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.
<h3>git-bug</h3> <p>git-bug is a distributed bug tracker imbedded in git.</p> <h3>Current state</h3> <p>Currently the project provides a large set of tools and functionalities (command line, web UI, and terminal UI) to deal with issues locally and supports Github and launchpad issues imports.</p> <h3>GSoC program</h3> <p>During the GSoC program this project aim mainly to:</p> <ul> <li>Complete bidirectional syncing with Github by implementing it exporter. </li> <li>Support bidirectional syncing with Gitlab by implementing it exporter and importer.</li> </ul>
<p>The <a href="http://www.creative-technologies.de/linux-based-low-latency-multichannel-audio-system-2/" target="_blank">CTAG face2|4 Audio Card</a> is a multichannel I2S soundcard based on the <a href="http://www.analog.com/media/en/technical-documentation/data-sheets/AD1938.pdf" target="_blank">AD1938 audio codec</a> by Analog Devices. Currently the soundcard can only be used with a <a href="http://beagleboard.org/black" target="_blank">BeagleBone Green/Black</a>. Due to CPU intensive calculations in digital audio the <a href="http://beagleboard.org/x15" target="_blank">BeagleBoard-X15</a> seems to be a perfect alternative to realize more complex audio effects and synthesizers and achieve lower latencies. Moreover the BeagleBone-X15 (<a href="http://www.ti.com/lit/ug/spruhz6e/spruhz6e.pdf" target="_blank">TI AM5728 SoC</a>) offers two separate DSPs (<a href="https://www.ti.com/lsds/ti/processors/dsp/c6000_dsp/c66x/overview.page" target="_blank">C66x</a>) which can be used to offload cpu-intensive multimedia tasks in asymmetric multiproccesing (AMP) configurations. The goal of the project is to port the soundcard drivers to the BeagleBoard-X15 and create an user-space library to make use of C66x DSPs via TI OpenCL and TI DSPLIB.</p>
<p>Integrate an optimized version of the current caching mechanism with the Nextgen core. The objective is to take the improvement suggested to optimize the old core's cache like Ignoring directories and some newly proposed improvements like cache controls, proxy objects, etc and try to implement them within the current Nextgen core architecture.</p>
<p>SPI slave driver implementation. The task is to create a driver controlling SPI hardware controller in slave mode, and to ensure optimal performance through the use of DMA and interrupt. Creating an easy to implement realization of SPI slave would definitely help the BeagleBone community members to write applications based on SPI much more easily. The first implementation of my protocol driver is going to example of a bidirectional data exchange. This application will provide the BeagleBone community with valuable experience and will be a good example of SPI slave. Hardware limitations make it impossible to perform any realization of the device using SPI slave. Sending away data to the master during one transaction is not possible. One transaction is enough to receive data by slave device. To receive and send back data, two transactions are needed. The data received from master device in a single transaction is transferred to the user after completing the transaction. The user's reply to received data is sent in the next transaction.</p>
<p>This project aims to provide an API for different programming languages to load firmware, start/stop and communicate with the BeagleBone PRUs (Programmable Realtime Units) from user space using the RemoteProc, RPMsg drivers. Example firmware and user space software are provided to demonstrate the use of the project.</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>
This project intends to introduce LLVM support for PRU, to enable us to use clang rather than pru-gcc. As Clang provides extremely clear and simple diagnoses and is considerably faster and requires less memory, it will be beneficial. The LLVM support will offer greater tooling, compatibility, and optimization. I will therefore build the LLVM Backend for PRU.
<p>coala currently has few generic bears which are not very useful or are not maintained well. The objective of the project is to get most of the generic bears in a working state so that they can be used in production.</p> <p>Apart from the current bear, this project brings many new generic bears which have been requested by the community from a long time but they were not worked upon. Such bears include <code>OutdatedDependencyBear</code>, <code>FileModeBear</code>, <code>FileExistsBear</code>, <code>RequirementsCheckBear</code>, etc. Apart from these, there are several improvements to <code>PEP8Bear</code> and <code>PycodestyleBear</code>. All of the bears are to be well tested and documented. This project also aims to bring a few improvements to coala core and upstream repositories.</p>
@nightwatch/mobile-helper is a tool that allows developers and testers to set up a fully functional Android Emulator environment in just a few minutes, without the need to download the complete Android Studio IDE software. This tool comes in very handy, especially for testers who wish to perform end-to-end tests for their website or native app on Android Emulators, by allowing them to set up everything they need in under 5 minutes, as opposed to having to set up the hefty Android Studio IDE and figuring everything out themselves.This project aims to take this tool one step further, by building on its usability and allowing users to do much more with the tool such that it not only benefits the testers but the developer community as a whole, or anyone who wish to quickly set up Android Emulators on their machines, while only downloading what is necessary, saving both internet bandwidth and storage capacity. To achieve this, this project proposes: a) Adding support for wireless adb connection to avoid the inconvenience of using USB cable. Users will be able to connect and manage multiple devices, both real and emulator. b) Adding support for downloading and managing multiple system images and emulators to facilitate use of a wider range of emulator devices. c) Adding functionality to update the installed SDK tools. d) Document all important SDK commands for easy accessibility of the users. The tool will help users to perform all these tasks with a very interactive and easy to use command line interface.
<p>The main purpose of this project is to make the text-editors of coala more robust and active. This will be done through ensuring that the plugins are up-to-date with proper tests and continuous integration, to make maintenance more simplified for contributors in the future. This project will be completed through the use of several open-source tools. Further, the completion of this project will lead to other developers having the freedom to use coala in their favourite text editors. The ease of usage in different text editors may also help potentially serve as a way to popularize coala.</p>
<p>This project aims to increase the usability and easiness for all the open-source enthusiasts by enhancing and improving the coala <a href="https://community.coala.io/" target="_blank">Community website</a> as well as coala <a href="https://projects.coala.io/" target="_blank">Projects website</a> for <strong>newcomers</strong>, <strong>developers</strong> as well as <strong>for other communities</strong>. A community website plays an essential role for an open-source community because it spreads the idea of offerings that community provide to other organizations, with information about the active community by exploring their skills as well as their precious contributions to it. So, the major focus of this project proposal is to enhance the architecture of websites. In addition, new API Endpoints will be created in coala <a href="https://gitlab.com/coala/landing" target="_blank">webservices</a>. These new endpoints will manage the user-database as well as coala database in a more structured form.</p>
<p>The goal of project meta-review is to track emoji responses to review comments. These responses would be collected, processed and displayed. This project builds a meta-review system on the community site and gh-board to display score ranking statistics and meta-reviews in need, respectively, and encourage people to do meta-review.</p>
<p>coala has come a long way from its early days in terms of its usability, although all the changes that have been made are improvisations. A proper and planned overhaul of the user interface would help coala become much more user friendly and intuitive. At its core any software is as good as its interface with the user and this project aims to improve that.</p>
<p>coala is a linting and code fixing tool with support for many languages. Having a configuration file is essential to make full use of coala. Having a standardised configuration format like TOML helps. coala currently has an INI style configuration. Also, INI style configuration has certain limitations when it comes to custom sub-level parsing. The LineParser and ConfParser becomes complex and error-prone. This project will allow developers to quickly implement new features and will allow users to write configuration files in a format that they are already familiar with.</p> <p>This project would focus on :</p> <ol> <li>Allowing the user to create configuration files in TOML</li> <li>Providing coala with the functionality to create TOML configuration files from sections</li> <li>Creating a tool to convert .coafile to TOML configuration file</li> <li>Allowing coala-quickstart to generate configuration files in TOML as well.</li> <li>Creation of TOMLLintBear and a repository of good configuration files to allow users to easily bootstrap their projects.</li> </ol>
In this GSoC project, I worked on developing a multimedia processing system, focusing on commercial detection and replacement using deep learning. I have developed a real-time, efficient solution that enhances media consumption experiences by seamlessly integrating custom audio streams during commercial breaks.
On several BeagleBone boards, there are an ultra-low latency 32-bit RISC CPUs called Programmable Real-time Units (PRUs) with register-mapped I/O directly to pins that is a custom architecture. The programmable nature of the PRU, along with its access to pins, events, and all SoC resources, provides flexibility in implementing fast real-time responses, specialized data handling operations, custom peripheral interfaces, and in offloading tasks from the other processor cores of the system-on-chip (SoC). To provide the capability of a Programmable Real-time Unit Industrial Control SubSystem (PRU-ICSS), I propose to deploy an existing RISC-V 32IM core with a customized Instruction Set Architecture on FPGA Fabric present on BeagleV-Fire. The goal of this deployment is to provide high bandwidth between the CPU and I/O, resulting in a on-board microcontroller. At project conclusion, BeagleV-Fire will host a fully functional PRU system that can execute Risc-V based instructions, and can be controlled by invoking specific functions within a C code using a PRU C library.
<p>Bitbanging an SPI or/an I2C device in Linux leads to a lot of problems.It consumes a lot of valuable CPU cycles.And since Linux is an non-preemptive OS(And not an RTOS),once we start bitbanging,other important tasks that require CPU time would suffer.Thus,there are a lot of software overheads in doing the same. To avoid this on the BBB,we could offload the task of bitbanging I2C,SPI,UART, to the PRU.The PRU is a separate core and,hence,not affected by the Linux Scheduler. Hence the motivation for exposing the PRU as an I2C,SPI,UART device comes from the fact that they would be no software overheads in doing it and hence,we would gain extra serial interfaces without wasting valuable CPU cycles in bitabanging.</p> <p>This project involves writing Device Tree Overlays,Device Drivers and PRU firmware code for Bitbanging I2C,SPI and UART.</p>
This project contain two parts which are Bb-Config Improvement and GPIO Benchmarking. For bb-config improvement, I will implement some new features on top of it making more user interactive and functionable. For GPIOs benchmark, We needed data to help ourselves and developers to decide which method accessing GPIOs suit them better. We compare the latency performance of different methods to access GPIOs.
<p>This project aims to create a tool that allows anyone to become a market gardener, given some space. As a first step, a user will merely sign up and enter the amount of space that they want to use. The system will then trigger tasks the user has to do to farm on his space efficiently. Those tasks are triggered by simple rules and may depend on weather events, dates, and later also other triggers. Thus, anyone can be a market gardener, and this tool will be beneficial and easy to use.</p>
<p>I aim to improve the existing diff handling capability of coala so that it is possible for bears to offer multiple fixes for an issue. I also plan to implement interactive diff behavior where the user input is used to generate interactive diffs using appropriate placeholders in the code. For achieving this I plan to have a generic approach for bears to pass their own applicable actions which can then be used to write a generic bear which can offer multiple patches. This can be followed by Implementation for templated patches and interactive diff behavior along with writing tests supporting these new functionalities. Finally thorough testing and exception handling should be done to fix bugs and designing alternate approaches if necessary(e.g. resolve conflicts of multiple bears on a single issue by git like conflict markers through IDE). I would be updating the documentation throughout the project. An optional task would be implementing output formats for the enhanced features and their processing functions being implemented in the Linter class if time permits.</p>
<p>This project is part of adding the 'aspect' functionality to coala-bears.</p> <p>Through this functionality coala users will no longer have to worry about searching for the bear or remembering the name of the bear appropriate for their work. They will be able to fix their code with the help of an ‘aspect’, which is nothing but a keyword that relates to the action they want the bear to perform on their code.</p> <p>This project aims at adding the aspect support to at least five more bears. Plus having properly defined and documented aspects for the same bears. After this project, these bears will get executed by using their respective aspects.</p>
<p>The aim of the project is to ease the process of testing bears in coala by significantly improving the testing API to yield favorable, easy to understand results, add support for at least 8 additional useful linter bears, integrate the MarkdownBear with useful plugins, include <code>remark-lint</code> to report error messages and get the MarkdownBear to a bug free state, and enhance documentation to include the newly written Linter bears.</p>
<p>The aim of this project is to implement the architecture that enables the support for nested - languages by default. The users of coala would not have to concentrate on writing new bears/ analysis routines. This project would perfectly work with the existing bears.</p> <p>On the successful completion of project, coala would have the support for the following programming languages:</p> <ol> <li>Codeblocks in RST</li> <li>PHP and HTML</li> </ol> <p>It is important to note that the aim of the project is not to provide a full fledged support for all nested languages , but to lay the foundation of architecture. It’s not possible to provide the full fledged support for languages until coala has a new feature where the bears can accept AST’s and lint through them, instead of taking files as input.</p>