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.
The goal of this project is to add CAN Framework and DCAN peripheral support for BeagleBone Black System on Chip in RTEMS. CAN protocol is a robust, reliable and multi-master serial communication protocol used to achieve real-time message transfer between devices within the CAN network. RTEMS being a real-time operating system, CAN peripheral support would increase the potential to meet real-time demands. BBB has two CAN 2.0 A, B (ISO 11898-1) controllers with 1 Mbps data transfer rate and DMA support. It also has inbuilt RAM which can hold 64 CAN messages. There is a loopback support also, which can be used for debugging purposes. By adding driver support for CAN modules, will enable the use of this potential hardware. With the help of the Am335x reference manual, TI’s starterware firmware and CAN specification I could understand the initialization and working of the CAN module. With the help of existing RTEMS supported CAN drivers I could understand the CAN framework and develop the support for CAN modules for BBB in RTEMS. I chose this project because I started learning embedded systems from BeagleBone Black and developed firmware from scratch with few peripherals and shell support https://github.com/slpp95prashanth/Beaglebone-mBootloader/tree/cpsw. As SoC and RTEMS are open source computing platforms, I would like to contribute to this project and learn more about RTEMS operating systems.
<p>DHIS Connector module is a module that is used to send aggregated data from OpenMRS to DHIS2 Instance. The module provides several user interfaces which can be used to configure the process easily. It already have important functionalities such as Drag-and-drop type mapping UI, Scheduled and Automated reporting, Import Export functionality for mappings, etc. The module can be improved with many other new functionalities. The project aims to develop the DHIS Connector module with new features and updates such as location mapping, extended period support, etc.</p>
Thrift for Zephyr Module aims to support the mature Remote Procedure Call (RPC) framework Apache Thrift on the Zephyr operating system (OS). This would enable lots of existed cloud services built upon Thrift to be seamlessly ported to the Zephyr ecosystem. New IoT applications can be developed rapidly without much boilerplate leveraging this module and the Thrift framework, too.
Currently, OpenAFS provides the afsio command that supports read, writes, and locks to both files and directories in the AFS environment without going through the cache manager. However, it does not support mount point control, ACL manipulation, or directory operations, which would allow a fully functional cell to be created without the cache manager; This would be convenient for administrators, as it avoids the kernel module having to be installed on the machine setup is being performed from, as well as allowing setup in environments not compatible with the kernel module. To address this problem, I will implement all three types of subcommands of afsio; Key deliverables include the code for all of these types of commands, as well as documentation such that administrators know how to use them.
The Entity Display Manager module aims to simplify how entity displays are handled in Drupal. Currently, managing view modes and form displays across different entities can be tedious and repetitive. This project will introduce a centralized, user-friendly interface to configure, duplicate, and synchronize entity displays efficiently. By providing intuitive tools and supporting bulk operations, the module will improve developer productivity and site-building experience in Drupal.
Description: Cluster API Provider GCP (CAPG) enables the creation of Kubernetes clusters in GCP with Cluster API. With increasing adoption of Cluster API (CAPI) in general and of CAPG we want to improve the supportability of CAPG, especially for production environments. The first part of this is to add telemetry/tracing using OpenTelemetry so that we can understand and visualize the flow of reconciliation within the provider. The next part is to add a **pprof** endpoint that can be optionally enabled to enable operations/support users to collect profiling information from a running instances of CAPG. Expected Outcome: This work will enable tracing and profiling of a running instance of CAPG (along with supporting docs) to supports operations/support engineers.
<p>The SunPy JSOC Client is a very rudimentary client to JSOC's export data CGI. The drms module provides a more complete implementation of the DRMS protocol. The drms module needs testing, and some other packaging improvements to automatically run the tests. This might involve adoption of some of the Astropy packaging code such as astropy_helpers, if necessary. Once the drms package has been well tested, CI added and a conda package created, the SunPy JSOC client could be improved and extended to enable use of the majority of the drms functionality through the unified search API of SunPy. While the SunPy implementation would not need to provide all the features of the drms library, it would strive to provide a simple API for most queries supported by drms.</p>
<p>In this project, my goal is to update the existing ANN facilities within mlpack and the deliverable is an improved ANN module. This includes adding many different functionalities, including layers like Pixel Shuffle layer and Spatial Dropout layer among many others. I have also proposed to add extended support for reduction facilities to be integrated into many different loss functions to bring to the table a degree of flexibility offered in other major machine learning libraries. I will also be building on the work done in a GSOC project last year, the mlpack-Tensorflow translator and mainly I will be updating it with all the latest changes in the source code to support new functionalities which have become a part of mlpack since last year. And finally, I have also proposed to begin work on improving the documentation of all layers, by adding inline examples within the header descriptions to improve usability for a wider range of end-users.</p>
<p>Although RDKit is a widely used extremely versatile chemoinformatics software package, it still lacks efficient 3D molecule visualization capability. In this circumstance, 3Dmol.js is easy to use and an excellent molecule visualization library that works in web browser. Another important platform is jupyter that allows communication with python from web browser through notebook like interface. Jupyter has also made the codes easily readable with clean output by dint of markdown. So, keeping python as operational core engine that expectedly works as interface of RDKit while utilizing support from jupyter notebook and 3Dmol.js should be a very good combination to ensure high productivity in drug discovery settings. In this project, I would like to turn these combination to more viable solution by binding 3D molecule visualization (protein-ligand complex), ligand editing panel, conformer scrolling system, and channel for sending ligand from jupyter interface to force field that exists in RDKit for energy minimization. Needless to say, I would like to use openbabel for file format conversion and molecular data extraction system.</p>
<h4>This proposal consists of 3 sub tasks of kapitan which is elaborated below.</h4> <h3>Task1 : Remote Inventory Federation</h3> <p>This work would add the ability to Kapitan to fetch parts of the Inventory from remote locations (https/git). This would allow users to combine different inventories from different sources and build modular infrastructure reusable across various repos.</p> <h3>Task2 : Support for Helm binding in OSX</h3> <p>This project can be subdivided into the following three tasks:</p> <ul> <li>Complete the Helm binding pipeline so that continuous integration (travis) also builds binding for osx and releases them to GitHub release.</li> <li>Packaging the binding to the pypi release.</li> <li>Add a brew manifest for osx so that users there can install Kapitan in a simpler way.</li> </ul> <h3>Task3 (bonus): Modularize kapitan</h3> <p>This project would modularize kaitan into core dependencies and extra modules.</p> <h3>Documentation and tutorial</h3> <p>Along with all the other tasks, documentation of all new and existing features will be done and displayed to kapitan.dev and walkthroughs will be made for the examples given in the documentation.</p>
<p>Hyperledger Fabric-X introduces a new architecture for Fabric, with decomposed services for ordering, endorsement, validation, and committing, but its current developer workflow is still centered around dedicated deployment scripts and Ansible-based setup.</p><p>Fablo, on the other hand, is widely used to start Hyperledger Fabric networks quickly from a single configuration file for local development, CI, and experimentation.</p><p>This project will explore and implement the best path to support a simple local Fabric-X network through the Fablo experience. We will evaluate architectural options such as a new engine, a separate repo, or an extension/wrapper approach, then build a minimal but practical MVP that can generate configuration, bootstrap the required components, and start/stop a working local Fabric-X network. The goal is to reduce setup friction for contributors and users, and provide a repeatable developer workflow, examples, and documentation that make Fabric-X easier to try, demo, and extend.</p><h3>Learning Objectives</h3><ul><li>Understand the architecture and deployment model of Hyperledger Fabric-X, including how it differs from classic Hyperledger Fabric.</li><li>Learn how to design contributor-facing tooling for distributed systems with evolving architecture.</li><li>Gain experience in open source development across CLI/tooling, configuration generation, testing, and documentation.</li><li>Develop practical skills in Docker-based environments, and debugging multi-component systems.</li></ul><h3>Expected Outcome and Deliverables</h3><ul><li>A design proposal describing the recommended integration path between Fablo and Fabric-X (for example: separate repo, pluggable engine, or wrapper-based approach).</li><li>An MVP implementation that can bootstrap a simple local Fabric-X network and manage its lifecycle.</li><li>Example configuration(s) and sample workflow for running Fabric-X through the proposed Fablo-based experience.</li><li>Automated tests and/or validation scripts covering the supported MVP scenario.</li><li>Contributor and user documentation explaining setup, architecture decisions, and next steps.</li></ul><p><br></p><p>Lean more at <a href="https://github.com/LF-Decentralized-Trust-Mentorships/mentorship-program/issues/83" rel="noopener noreferrer" target="_blank">https://github.com/LF-Decentralized-Trust-Mentorships/mentorship-program/issues/83</a></p>
<p>The development of GPUs for general purpose computing has revolutionized the field of deep learning. They are critical for training large deep neural networks (DNN) and improve the performance of inference.</p> <p>The OpenCV’s DNN module has a blazing fast inference capability on CPUs when compared to other popular libraries such as TensorFlow or PyTorch. It supports inference on GPUs using OpenCL but not CUDA. NVIDIA’s GPUs support OpenCL, but their capabilities are limited by OpenCL. A separate CUDA backend is required to reap maximum performance out of NVIDIA's GPUs.</p> <p>This project aims at adding a complete CUDA backend for OpenCV’s DNN module. By the end of the project, the DNN module should be capable of performing inference on CUDA enabled GPUs nearly as fast as or faster than existing deep learning frameworks such as TensorFlow or PyTorch.</p>
Kiwix is useful because it can provide a lot of content to people without internet access. Therefore, the easiest it is to generate content that is available offline, the more users can be reached. Nautilus is a powerful tool for creating ZIM files from collections of documents (PDF files, videos, etc.), but it currently requires the user to run commands from the command line. This makes it challenging for users (usually schools) who are not familiar with the command line or who prefer a graphical user interface. The goal of this project is to build a web-based user interface for Nautilus, making it easier for users to convert their collections of documents into browsable ZIM files. The web UI will be built using Python, JavaScript, HTML, and CSS and will provide an intuitive and user-friendly interface for Nautilus.
There are many secondary goals for this project, but the main goal is to make the fuselage compatible with React Native. But also, we have figthing against the bundle size of the fuselage, and of course performance which is always a concern. Using the tamagui as a base, we can components that are compatible with both platforms, and in a efficient way.
<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>
<p>The project aims to add the functionality of Service Accounts in the existing Rocket.Chat application. Service accounts will be an upgrade to regular user accounts, they will have a well-defined purpose. Regular users can subscribe to this account to get information regarding the context mentioned in the description of the Service account.</p>
<p>This project is about improving the UI/UX experience of kiwix-serve which is used to host library.kiwix.org and other local servers for hosting zim files. My main focus on this project will be to build a better search and presentation experience for users.</p>
Ruqola, a Qt-based Rocket.Chat client, currently lacks a robust implementation of end-to-end encryption (E2EE), making user communications vulnerable to interception. This project aims to design, implement, and integrate a complete E2EE workflow into Ruqola, ensuring secure messaging through strong cryptographic techniques. The project consists of two phases: Phase 1: Encryption Sandbox Develop a standalone Encryption Test GUI to prototype and validate E2EE workflows. Implement Master Key derivation (PBKDF2), RSA key pair generation, AES message encryption, and session key exchange. Create unit tests for core encryption processes. Phase 2: Ruqola Integration Integrate encryption into Ruqola’s communication system. Encrypt outgoing messages with session keys and decrypt incoming ones. Provide a user-friendly UI for encryption settings. By the end of the project, Ruqola will have a fully functional E2EE system, securing user messages with cryptographic best practices while maintaining an intuitive user experience.
<p>Currently, scrapers are used to generate ZIM files and contain code that is difficult to maintain. A new library called scraperlib is being developed to facilitate automated testing and code coverage of shareable code. The task is to rationalize the usage and maintenance of those by limiting them to their specificities only and move any reusable logic into the well-tested scraperlib.</p>
<p>Create a Kiwix hotspot application that would be an extension to the kiwix android application. It would allow the users to share their ZIM Files with others over the same network. This can be made possible by:</p> <ul> <li>Creating a layout for the user to select the files he wishes to host.</li> <li>Working with a web server i.e. kiwix-serve. We can communicate with it via JNI(Java Native Interface).</li> <li>Working with WIFI hotspot(without using data).</li> <li>Presenting the IP address where the files have been hosted.</li> <li>Some networking tricks to polish the application.</li> </ul> <p>Other devices can access the ZIM files by just connecting to the hotspot and simply entering the ip address into their browser.</p> <p>This project would be really beneficial in areas especially where internet is not so easily available/accessible. For example, a teacher who has the kiwix android application would be able to share the ZIM files with all the students offline.</p>
MWoffliner is a tool for scraping MediaWiki content into ZIM files for offline access, but its current architecture has significant maintainability and testability issues. The codebase suffers from singleton patterns preventing parallel execution, monolithic files, circular dependency cycles, code quality issues and tests that require full infrastructure that take a while to run. I'll deliver a comprehensive architectural refactoring that introduces dependency injection, breaks up monolithic files and singletons, implements storage abstraction for fast unit testing, restructures the directory organization, and optimizes the article processing pipeline all along with improved code quality. This refactoring will eliminate circular dependencies, enable tests to run without infrastructure, improve code modularity and architecture along with performance.
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>Search is a fundamental operation performed by Kiwix that helps users to find the content they want in a quick and efficient manner. Though it is highly functional right now with many more enhancements coming in libzim7, there are still some missing features and room for improvement. Namely:</p> <ul> <li>Drop wrapper structures from kiwix for performance and usability enhancements</li> <li>Improve relevant suggestion results and their snippets by optimizing Xapian implementation</li> <li>Introduce a versatile suggestion API that is able to work even in the absence of a Xapian index</li> <li>Make suggestion handling more stable in kiwix-serve and other sub-projects</li> </ul> <p>The project addresses these issues such that kiwix users can have an overall improved search experience.</p>
<p>This project aims to enable all the essential functionalities of Rocket.Chat to be accessed through any Alexa and Google Assistant device by creating and deploying a Rocket.Chat Google Action and an Alexa Skill to their respective stores.</p> <p>The main goals and improvements to be made for this term will be:</p> <ol> <li>Adding more functionalities to the backend to make the skill/action more practically usable and efficient.</li> <li>Improve the voice interface of the skill/action.</li> <li>Adding more functionalities to skill and action.</li> <li>Resolving existing bugs.</li> <li>Making it consistent across all languages.</li> <li>Finally deploying the skill/action to store.</li> </ol>