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.
Cancer patients navigating clinical trial databases face complex search interfaces with dozens of technical filters, making it difficult to find relevant trials without medical expertise. This project builds a patient-facing clinical trial chatbot with an interactive map that removes this barrier through natural language. The system features a three-panel interface: a chat panel powered by an LLM agent that elicits patient information and matches it against the Cancer Trials Canada database, an interactive map that displays geocoded trial site locations and a summary panel that shows trial details when a pin is clicked Built using Chainlit server mounted inside FastAPI, React application with Mapbox GL for the interactive map. Trials are stored in PostgreSQL with pgvector for semantic and full-text search. An open-source LLM served via Ollama and Pydantic-AI. Multi-layered guardrails prevent off-topic or harmful responses, RAGAS for evaluation and Langfuse for observability and tracing throughout development.
The project aims to implement a Virtual Digital Audio Interface (DAI) for the Sound Open Firmware (SOF) to facilitate debugging, rapid prototyping. The Virtual DAI will support two directions: playback, which consumes data similarly to /dev/null, and capture, which generates data like /dev/zero or /dev/urandom. Expected outcomes include successfully merging the Virtual DAI component upstream, enabling simple playback and record pipelines, logging and discarding output frames for playback, and generating zero-filled frames for recording.
This project aims to improve playlist management in ListenBrainz by making it easier for users to search, organize, and interact with their playlists. Currently, while some backend support exists, the user experience lacks intuitive features for managing personal playlists effectively. To address this, I plan to implement four main features. First, I will complete and enhance playlist search directly on the user playlists page. Second, I will introduce tag-based organization, allowing users to categorize and filter playlists efficiently. Third, I will add in-playlist track sorting options such as sorting by title, artist, date added, and shuffle. Finally, I will enable users to view their MusicBrainz collections as playlists and optionally save them within ListenBrainz. The project will involve backend changes such as adding new database tables and API endpoints, along with frontend integration using React to provide a smooth and consistent user experience. The final deliverables will include a fully functional playlist search feature, tag-based organization system, track sorting functionality, and MusicBrainz collection integration, along with tests and documentation for all components.
The project has the aim of providing offline data entry capability into the CARE form-based data collection system. Currently, users experience interruptions when network connectivity is lost, preventing data entry while in the field with the application opened in a disconnected state. This project will maintain coordination with CARE forms during offline status, allowing users to continue using the app normally.The approach will implement an offline-first architecture that includes application caching, local storage, and sync capabilities. I plan to implement caching while using Workbox and Service Workers to cache the appropriate application assets and form definitions so that the user interface can load and continue to operate without a network connection. I plan to use IndexedDB, managed through Dexie.js, to store the form responses as local data storage on the user’s device. After connectivity is re-established, an automatic background sync process will use React Query and PQueue to ensure reliable and conflict-free data sync with the established database on the central server. Conflict resolution strategies will be included to maintain integrity, safe and complete data from being 'lost' when multiple users could be updating the same data at the same time.
<p>The Haskell Language Server is a popular, comprehensive Haskell IDE; however, it is yet to implement a core feature: symbol renaming. With the recent addition of HieDB (a database for references in Haskell code), there is sufficient infrastructure to implement this feature.</p> <h3>Problem Benefits</h3> <p>Having an accessible renaming feature could encourage improving names, leading to clearer naming across the Haskell community. Renaming is especially useful in Haskell since short names are common, meaning they are often reused and difficult to disambiguate when renaming manually.</p> <h3>Project Aims</h3> <pre><code> - To support workspace-wide renaming of all names, including type synonyms, data constructors, and functions. - To support renaming of qualified imports. </code></pre>
This project involves the integration of AlphaMissense, an innovative tool for predicting the pathogenicity of missense mutations, into two established platforms: Genome Nexus and cBioPortal. My Objectives and Deliverables are: - Integrate AlphaMissense pathogenicity predictions into Genome Nexus API responses, enriching genetic variant analysis with detailed pathogenicity scores. - Display AlphaMissense predictions within the Genome Nexus variant pages and add dedicated data columns in the cBioPortal mutation tables, complete with functionalities for sorting, filtering, and downloading. -Add AlphaMissense pathogenicity prediction and score into Genome Nexus annotation pipeline as two new columns in the annotation result file The project will be executed in phases, starting with initialization and planning, followed by backend and frontend development to integrate and visualize AlphaMissense data. Subsequent phases will focus on testing, deployment, and documentation, concluding with a final review and official launch. Post-launch, the project will enter a maintenance and support phase to address any arising issues and incorporate user feedback. Backend development will utilize Java and Spring Boot for integrating the AlphaMissense plugin into the Genome Nexus API. Frontend components will be developed using React and TypeScript, ensuring a dynamic and user-friendly interface for displaying genetic predictions.Comprehensive testing phases, including unit, integration, and User Acceptance Testing, will ensure the reliability and accuracy of the integration. This integration represents a significant leap forward in personalized medicine. By making pathogenicity predictions more accessible and interpretable, this project aims to support advancements in genetic research and clinical decision-making, ultimately contributing to improved patient outcomes.
<p>Both Link Time Optimization (LTO) and C++20 Modules will benefit from a closer interaction between build system and compiler. LTO benefits from parallelizing the LTO step by spawning separate compilations and Modules can discover new dependencies during compilation. Both of these task are traditionally under control of a build system.</p> <p>Currently, GCC's LTO can use GNUMake's jobserver protocol to control its direct spawning subjobs. C++20 modules can make use of a proposed protocol[*], or use pre-scanning. This project aims to unify these approaches providing (a) client/server librar{y,ies} to manage communication (b) extend the proposed protocol to cover LTO requirements (c) provide a sample implementation for GCC/GNUmake.</p> <p>[*] <a href="https://wg21.link/p1184" target="_blank">https://wg21.link/p1184</a></p>
My project aims to bridge the gap between single-cell gene expression data analysis and existing cancer genomics workflows, particularly within the cBioPortal platform. Currently, cBioPortal lacks support for visualizing single-cell data alongside bulk genomics data, hindering researchers from gaining a comprehensive understanding of cancer biology. To address this, I propose the development of a dedicated single-cell analysis module within cBioPortal, focusing on the MSK Spectrum dataset. The key problem I am addressing is the inability to integrate single-cell gene expression data with existing cancer genomics workflows. By incorporating single-cell data into cBioPortal, researchers will be empowered to identify specific cells with altered gene expression, understand their contribution to overall expression patterns, and connect this information with genetic alterations. My solution involves developing a custom Single-Cell Tab within cBioPortal's study view. The tab will include features such as dataset information, gene selection, interactive visualizations (boxplots, scatter plots, stacked bar graphs, and pie charts), filtering options, and download capabilities. To achieve this, I will aggregate the single-cell data to a gene-cell type-sample level, creating a pseudo bulk representation to manage the large dataset size effectively. I will utilize existing charting libraries like CanvasJS and React primitives for visualization components, ensuring seamless integration with cBioPortal's design language. My deliverables include: Custom Single-Cell Tab within cBioPortal study view. Dataset information panel for study description and cell type/sample details. Gene selection panel with autocomplete functionality. Interactive visualizations including boxplots, scatter plots, stacked bar graphs, and pie charts. Filtering options for focused data exploration. Download options for data and plots in common file formats.
<p>The goal of the project is to provide production ready, autoconfigured service that will be using all the AeroGear Voyager Server functionalities and will provide a command line tool for building and extending GraphQL based Node.js server. The client will help with developers getting started by generating standalone Node.js Server that can provide out of the box features for developers looking for RealTime DataBase capabilities and easing development effort required to build and deploy functional server to production.</p>
Summary: The OBA project aims to develop official OneBusAway REST API client libraries in TypeScript and Python, enhancing accessibility and user experience for developers interacting with OneBusAway servers. These libraries will support all REST API methods, handle diverse data types, include comprehensive tests, and provide helpful examples for new users. About Me: I am Ahmed Hossam, a senior information technology student with a passion for technology and problem-solving. With experience in backend engineering and competitive programming, I am excited to contribute to the OBA project and make a positive impact. Investigations: I have familiarized myself with OneBusAway endpoints, built a beta version of the TypeScript package, and experimented with different structures for scalability and maintainability. Detailed Design: The API client follows a modular structure, with each endpoint encapsulated within its own module. It employs a combination of factory and dependency injection patterns and includes a base class for foundational HTTP request functionality. Implementation Plan: I will collaborate closely with mentors to understand API client requirements and plan implementation details. Error handling and unit testing will be prioritized, followed by thorough testing and the publishing of final packages. Proposal Timeline: The timeline spans 14 weeks, beginning with communication and research in the first three weeks, followed by official coding in TypeScript. Python implementation will commence in week 9, with completion and finalization in week 14. Why Me: I find joy in making OBA APIs accessible to everyone and am dedicated to contributing positively to the project. My experience in API development, along with continuous learning, makes me well-suited for this role.
<p>Agones is a Kubernetes-native platform for hosting, running, and scaling dedicated game servers. This project builds a Headlamp plugin that adds an **Agones** section to Headlamp, surfacing Agones CRDs so operators can **view and manage game servers, fleets, and allocations** from the Headlamp UI. The plugin follows Headlamp UX patterns with list and detail views, links between related resources, and visibility into lifecycle and allocation state.</p><p><br></p><p>Expected Outcome:</p><p> - Plugin exposes key Agones CRDs: GameServer, Fleet, GameServerSet.</p><p> - List views, with summary columns (name, namespace, state, address, port, node, replicas).</p><p> - Detail pages, showing config, status conditions, lifecycle state, and sub-resources (game server pods).</p><p> - Relational navigation, fleet → game servers; game server → fleet.</p><p> - Consistent Headlamp UX, icons, tables, detail layouts, Map view enhancements.</p><p> - Structured config display (collapsible sections/YAML toggle), humanized lifecycle states (Ready, Allocated, Shutdown).</p><p> - README with prerequisites and limitations; blog post demoing usage.</p><p><br></p>
The aim is to reimplement the Sugarizer Core architecture using Vue.js components, in order to update and improve the current implementation that relies on Enyo.js, a deprecated web framework. By utilizing Sugarizer Vue.js components, we can ensure that Sugarizer remains a modern and efficient tool for its users. The proposed project involves a comprehensive redesign of the Sugarizer Core UI, which includes developing new Vue.js components and integrating them with the existing Sugarizer codebase. The new components will be designed to improve the user experience, increase efficiency, and enhance the functionality of the app.
<p>Community of today used to use mobile phones to make their life easier and Community based mobile applications are famous among them. There are several kind of community based applications in use and most of them are relating to a specific domain. But core components have similar features. Address this issue and saving development time by Introducing a common app template with customizable components for community based mobile applications , is the main purpose of this project.</p>
<ul> <li>Improve the current Open Event Organizer Server application. Write tests for existing models and views. Provide bug fixes and enhancements.</li> <li>Create REST APIs to create/update/delete data at the server. Write tests and documentation for the same.</li> <li>Design and develop Organizer Server Permissions System.</li> </ul>
The kworkflow project has a GitHub Actions hosted CI pipeline that restricts testing possibilities for core kworkflow features, such as kw deploy, which would be better tested in real kernel deployment scenarios. I propose an implementation of a new Jenkins CI pipeline on a self-hosted server infrastructure for kworkflow, enabling more customizable and realistic testing cases and allowing specific hardware testing. The new server infrastructure will also be used for a data telemetry system.
This project focuses on extending the existing React based Mifos X Web App to make it a strong candidate for the primary Mifos X web interface. The application will be enhanced using React and TypeScript, with improved integration to the Apache Fineract backend through the OpenAPI TypeScript client. This project will result in fully functional multi-step workflows and the implementation of missing or partially developed features. The final outcome will be a stable web application with feature parity with the existing Mifos X platform.
<p>JBoss Web Servers consists of Apache Tomcat 7, Apache Tomcat 8 and Apache Tomcat 8.5 servers. JBoss Core Services consists of Apache HTTP server and its dependencies. The project’s goal is to develop a tool that will scan and parse the upstream security advisories of Apache Tomcat and Apache HTTP Server along with their dependencies. This tool’s purpose is to populate Bugzilla by tracing down any new public CVE on every JWS and JBCS related upstream project. The tool will be built in Python3, scripts will be fired via Jenkins job and scripts will be running as a shell script.</p>
The project aims at helping researchers find journals that require open source code easily. I aim to create a user interface that could seamlessly help users submit, edit and delete journals and a user-management system that could help with admin and user roles. React forms can replace the outdated google forms to sign manifestos by individuals or organizations, which comes with proper authentication and spam prevention. Apart from working on having maximum functionalities integrated, I shall be removing the frontend dependencies like React-Bootstrap to make the project more user-friendly. With that, CI pipelines shall be integrated through Github actions along with E2E tests written with Cypress.
<p>At the time of writing this, the frontend and the backend in <a href="https://github.com/fossasia/open-event-orga-server" target="_blank">open-event-orga-server</a> are tightly coupled with each other. The goal of the project is to refactor the current project and properly implement a json-api spec compliant API for Open Event Server. Other goals include setting up documentation testing using <a href="https://github.com/apiaryio/dredd" target="_blank">Dredd</a>.</p>
The Konveyor project helps modernize applications by providing open source tools to rehost, replatform, and refactor applications to Kubernetes and cloud-native technologies.We’re looking for help on building integration tests on application level as well as work on missing parts of Konveyor component tests.There is open testing work to better applications analysis, tasks coverage, more detailed Hub API tests and Hub integration with addons. All of those use the Hub API that is covered with basic tests already. Based on existing Hub API tests, it is expected to continue work to cover more Konveyor functionality with tests. The development environment is based on golang and Kubernetes. A minikube instance will work well for local development on Linux or Mac systems. - Expected Outcome: - Integration test suite and components testing added to existing Konveyor upstream automated test suite
This proposal aims to describe how to add inlay hints support to the Haskell language server. Inlay hints can provide a more fancy, intuitive, and convenient ui view of the current state of the code, such as the fixity of operators, the type of bound symbols in `let`, the type of holes, etc. Some basic work already exists in the current HLS that makes it feasible to implement inlay hints, such as the basic type library already in use: https://github.com/haskell/lsp; and the hls plugin system. Prior to submitting this proposal, I had already started working on trying to make some implementation work, and had made some progress. I submitted a draft pull request (https://github.com/haskell/haskell-language-server/pull/4131) to hls's github repository, which lists some todo's, but it should be noted that there is more to this proposal than just the pr's, and any suitable information that can be presented with the help of inlay hints will be included in the work. Since the ability to configure inlay hints is already in the todo, even if inlay hints that are too informative are implemented, they will not be a bother to the user: the user has the ability to configure the information that inlay hints will display. In the body of the proposal, I detailed the timeline and details for implementing the idea. I'll continue to build on the progress of this pull request, gradually implementing more inlay hints usages and important configuration capabilities.
<p>The project is a demo for the Hydra draft proposed by the W3C. It aims to build a smart client and server that is able to exchange information in an efficient manner over a RESTful API using a Hydra based vocabulary. A smart client is able to communicate with the server even without previously knowing the supported methods of the server. This is made possible using Hydra's API documentation method. Hydra is a push towards the idea of semantic web and it's potential as a mean of communication is demonstrated in this project. This project lays the foundation for a larger project that showcases Hydra's full potential.</p>
This project proposes building a new, modern web UI for Mifos X using React, Tailwind CSS, TypeScript, and ShadCN components. The new Mifos X will be integrated with the Apache Fineract backend using the official TypeScript API client to ensure seamless data flow and backend connectivity. Deliverables include a fully responsive, modular UI for Mifos X modules and complete integration with Fineract APIs. The new Mifos X will enhance user experience and provide a solid foundation for future improvements.
<p>Smart HTTP/2-based protocol for Infinispan.</p> <p>The Infinispan Server distribution contains a server module that implements Infinispan’s custom binary protocol called Hot Rod. The protocol was designed to enable faster client/server interactions compared to other existing text based protocols and to allow clients to make more intelligent decisions with regards to load balancing, failover and even data location operations.</p> <p>In 2015 the 2nd version of HTTP protocol (simply HTTP/2) was finally introduced. HTTP/2 provides a lot of features that are also implemented in Hot Rod protocol. For example, using the HTTP/2 will be more preferable than Hot Rod because the size of the requests and responses will be smaller.</p> <p>Expected results of this project are:</p> <ol> <li>Modify current REST Server endpoint for Infinispan to handle HTTP/2 protocol. Modification will be based on implementing features from Hot Rod protocol to HTTP/2.</li> <li>Create HTTP client on Java.</li> </ol>