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>Taverna is a comprehensive workflow engine which has several ways of creating work flows and there are multiple layers/interfaces exposed to interact with the workflows, such as desktop workbench, command line tool, web interactions through a dedicated Taverna server which expose REST/SOAP interfaces.</p> <p>When creating workflows, there can be various use cases to talk to external environments/systems and execute/pull information from them. OSGi based Taverna core platform provides plugins architecture to install custom plugins in ad hoc manner. This project is basically about creating a new Taverna activity plugin for Docker. With this feature, Taverna users will be able to invoke/run docker images inside their workflows.</p>
This project has three main modules: indicator collection, local aggregation and indicator push. 1.indicator collection : Define MetricsCollector under the common package to collect various internal indicators of Dubbo, and count the basic indicators (total number of requests, total number of successes, total number of failures, number of requests being processed, number of threads, request response time) when the service is invoked. 2.local aggregation : The result of index collection is used as the basic index, and the sliding window algorithm is used to calculate some quantile indexes. This function is controlled by XML label and is disabled by default. 3.indicator push : Encapsulate collected and aggregated indicators and push them to a third-party server in a specific way.
<p>This project aims to come up with a pan-octave implementation that could be used to connect to the Octave wiki's <a href="https://wiki.octave.org/" target="_blank">webserver</a> with appropriate credentials for publishing octave scripts that could be hosted on the above mentioned server for distribution using the MediaWiki API. Currently, no formal implementation is there but a proof of concept which is implemented as a bash script which was later refactored to use JAVA’s interface to octave. To maintain a stateless HTTP protocol, some information that would be needed will be stored as cookies with the help of Libcurl library.</p> <p>The next task would be to set up RESTful services for GNU Octave which could be further extended to support the compatibility with MATLAB’s RESTful interface (webread, webwrite, weboptions, etc.)</p>
<p>This project’s purpose is to replace or rather migrate the existing persistence schema of LibreHealth toolkit which uses hibernate mappings to a more modular spring data persistence mechanism.<br> LibreHealth toolkit currently uses xml style mapping provided by hibernate which is harder to maintain and provides very little modularity in terms of switching to a different data source.<br> Using spring data instead will make the system easier to maintain i.e lesser components to change in case a single entity needs to be modified, whereas in the current scenario to modify a single entity we might need to change the model class, the mapping file, the dao, the service, etc. This makes for a more resilient system.</p>
This project aims to complete and productionize the FOSSology UI by finalizing the ongoing migration to Next.js and ensuring full integration with REST API v2. Building on the previous GSoC work, the project focuses on implementing the remaining pages, standardizing the interface using a reusable design system with ShadCN and Tailwind CSS, and improving overall consistency, accessibility, and user experience. The application will be upgraded to the latest Next.js version to leverage advancements in performance, caching, and rendering. Additionally, the project will emphasize modular architecture, component reusability, and comprehensive Storybook documentation. Thorough testing, codebase refactoring, and detailed developer and user documentation will be completed to ensure scalability, maintainability, and ease of future contributions.
Unikraft is an automated system for building specialized POSIX-compliant OSes (unikernels). These unikernels are configured for the needs of specific applications. It is based around the concept of small, modular libraries, each providing a part of functionality found in an operating system (e. g. memory allocation, scheduling, network stack etc.). All components of Unikraft’s architecture are micro-libraries. Despite its “everything is a library” concept, Unikraft should have some architectural changes that can improve the program’s modularity and everybody’s experience. For example, some of the changes that can be made are: source code’s layout to be changed, APIs written as libraries (e. g. paging.c), moving drivers outside ‘common/’, implementing per-platform configuration etc.
Most components of Kiwix-Desktop are written in QT C++, except for the library (aka content manager). The library is the view which allows you to handle books, locally (when books are already downloaded) or remotely (from the online catalog) to download them. Although the whole Kiwix-Desktop software is written in C++, this part is a HTML rendering widget and the details are handled in HTML/JS/CSS with the framework vue.js. The problem with vue.js is that it needs a special effort to keep the visual coherence with the rest of the app in Qt. The filters panel in the library also suffers from being outdated. Unlike other kiwix apps, it has a predefined set of libraries and categories, doesn’t save user preferences and the overall display is not too pleasant. This project aims to fix such problems.
This project aims to enhance the Jenkins Tekton Client Plugin by implementing full CRUD (Create, Read, Update, Delete) operations for Tekton resources, including Tasks, Pipelines, PipelineRuns, TaskRuns, Triggers, TriggerBindings, and TriggerTemplates. By adding Read and Update capabilities, the plugin will support complete lifecycle management directly from Jenkins, improving CI/CD workflows and reducing context switching. Deliverables include a fully functional plugin with CRUD support, improved error handling, integration with Jenkins credentials, user-friendly UI components, comprehensive testing, and detailed documentation. This enhancement will streamline cloud-native CI/CD management within Jenkins, making Tekton resources more accessible and manageable.
<p>The sheer number of social media users has been increasing exponentially along with social media websites. Day by day, Social Media is integrating deeper with people's lives. Social Media Integration with CiviCRM will allow users to quickly login securely to the website without the hassle of remembering another extra password and provide access to features such as event registration and petition signing quicker. On the other hand, organizations using CiviCRM can have their different events, campaigns and petitions promoted and publicized in different social media platforms and analyze how people react to them all at one place. Social Media Integration with CiviCRM will boost the exposure of CiviCRM as a platform and make it even easier for people to connect.</p>
Large digital designs are prone to consume lots of power and thus, a tool for power analysis is needed. There are two types of power analyses: static, which is more of an estimation that ignores circuit operations, and dynamic, which simulates the circuit behavior in conjunction with switching power. These tools are Verilog gate level-simulations and SPICE simulations, respectively, but the former can be inaccurate while the latter is computationally demanding. IRSIM, a tool intermediate between these two simulation tools, simulates the circuit as a network of transistor capable of turning ON and OFF, serving as a tradeoff between speed and accuracy in dynamic power analysis. The goal of this project is to develop and enhance a command-line interface compatible with up-to-date transistor components in the IRSIM library to ensure the analysis accounts for various power domains.
This project aims to overcome Blender's limitations with spreadsheets and other functionalities. The goal is to have a web interface running alongside Blender. This web interface ideally should be able to show tabular data for objects that Blender knows about, have real-time updates, and execute operators on them. Key tasks for this project include setting up an HTTP web server or a WebSocket connection for communication between the web interface and blender, Sending data from Blender to the web interface, and vice versa, displaying data on the web interface with the ability to execute operators that reflect in Blender, and If time permits, a dynamically generated Gantt Chart for work schedule. Deliverables: 1) Showing tabular data 2) Ability to execute operators 3) Dynamically Generated Gantt Chart
<p>Performance Co-Pilot is a framework which provides measurement for system performance and analysis. There are also several widely used simple tools for monitoring system information. These tools do not consider the historical data and thus fail to analyze such information. Also these tools monitor only for the local processes which restricts them from using on remote servers. Performance Co-Pilot provides rich APIs to access historical information about local as well as remote processes. The project proposes to build the PCP Clients for reading archive as well as remote processes data using PCP APIs to make some of the popular monitoring commands such as htop, pidstat, mpstat and nfstat. The proposal also discusses the solution and its implementation along with the time line.</p>
This proposal entails revamping the existing Processing error message system so that it resembles the P5.js Friendly Error System (FES). The problem is that the current error messages are often vague and not easily understood by beginners. I plan to remedy this by ensuring each error message four components: the original error generated by the JVM, an identification of the problem an explanation of the problem and when possible, a solution to the error. The error messages should convey the severity of the error and in beginner friendly language, explain the cause of the error. The error message should also provide links to relevant documentation to contextualize the issues and also include the original JVM message. Time permitting, additional features such as translation into other languages, a log of previous errors and a button to accept user feedback.
<p>Large-scale cancer genomic research, such as TCGA project generated huge amount of high-dimensional data, yet most features are under-explored for clinical application. Previously, our mentor has developed a cox neural network model that can predict patients' survival time using TCGA genomic data with extremely high accuracy. Here we propose to explore methods that rank the importance of input genomic/clinical features for this cox model based on both prediction accuracy and biological information of these features to understand the underlying biology of cancer and translate the existing implementationin Theano library to TensorFlow with comprehensive documentation and hopefully develop a user-friendly web-server for average biologist/clinicians to use and draft a manuscript.</p>
<p>If Musescore was being built today using web technologies like React etc., it would have definitely been built with a tree-like model for the score with each element in the score containing the smaller elements, like Score -> Staff -> Measure -> Note -> Accidental. In the case of Musescore, the code was written manually for QT, with all the drawing and file handling code written manually. So the classes in libmscore follow this tree-like model somewhat informally, but not explicitly. I will be refactoring the code, such that the classes in libmscore follow this model exactly by adding a "children" list to the ScoreElement class. Many operations can then be written as tree traversals. This would prevent a lot of duplication in code, and simplify the code in a lot of places.</p>
This project focuses on redesigning Wagtail’s Bakerydemo so it better represents modern, real-world websites and larger content needs.The content strategy will broaden beyond breadmaking (e.g., city/community storytelling) while keeping templates and blocks generic and reusable. The work will be delivered incrementally through small pull requests, adding a theme-ready design system, reusable StreamField components, and broader content sections beyond breadmaking while keeping the architecture simple and maintainable. It will also strengthen multilingual and RTL support, improve mobile and zoom behavior, and expand demo data coverage for scale testing. The goal is to provide a more practical, accessible, and reusable demo experience for Wagtail users and contributors.
DeepChem supports transformer-based foundation models for chemistry (ChemBERTa, MolFormer) but has no equivalent for genomic data. This project fills that gap by integrating DNABERT-2 into DeepChem, following the same design pattern used by ChemBERTa and MolFormer. The implementation consists of two components: (1) a DNABert model class that wraps HuggingFace's DNABERT-2 inside DeepChem's HuggingFaceModel/TorchModel hierarchy, supporting masked language modeling pretraining and fine-tuning for classification, regression, and multitask regression; and (2) a DNABertTokenizer that serves as both a HuggingFace tokenizer and a DeepChem featurizer, making it compatible with DeepChem's data loading pipeline. Deliverables include the fully integrated model and tokenizer classes, tests across all task modes, and benchmarks on a suitable genomic dataset.
<p>Airavata based science gateways store data in the gateway storage which is typically mounted in the portal's hosting server. Each user's data is organized within user directories on these storage devices. As storage reaches its limits, it often creates an issue in rationing the disks. So, a single user running a finite number of experiments can adversely cause issues for other users in the gateway.</p> <p>This is similar to modern memory attacks. A hacker can write a script that continuously creates new experiments causing the storage space in the gateway to be depleted.</p> <p>The goal of this project is to mitigate such scenarios by implementing a storage limit for each user in a gateway. This way, one user can never adversely affect other users.</p>
<p>Currently, many components of Git are still in the form of Shell or Perl scripts. This choice makes sense especially when considering how faster new features can be implemented in Shell and Perl scripts, rather than writing them in C. However, in production, where Git runs daily on millions of computers with distinct configurations (i.e. different operating systems) some problems appear (i.e. POSIX-to-Windows path conversion issues).</p> <p>The idea of this project is to take “git-stash.sh” and reimplement it in C. Apart from fixing compatibility issues and increasing the performance by going one step closer to native code, I believe this is an excellent excuse to fix long-standing bugs or implement new minor features.</p>
OpenHPC is accepting applications for a new mentorship program that aims to give students practical experience contributing to an open-source project and an opportunity to work with volunteers from the project’s Technical Steering Committee (TSC). OpenHPC is a software stack that aggregates a variety of software components ranging from administrative tools like bare metal provisioning and resource management to end-user development that span a range of scientific/numerical uses. If your interest is in the domain of high performance computing , scientific computing or cluster management, this might be the right program for you. This program will occur during the Summer of 2022. See our website for details and project ideas - https://bit.ly/ohpcmentorship2022. For questions feel free to email - mentorship@openhpc.community
As an agent-based modeling (ABM) framework, Mesa is easy to use and applicable for a wide range of simulations. But traditional ABM agents rely on simple rules and patterns that are chosen by the users themselves, which can limit their adaptability. The objective of this project is to develop an extension of Mesa that give agents access to LLMs for reasoning, decision-making, and communication, that can be used not only for simulations, but also to study the impact of different paradigms and reasoning modules in ABM. The work involves designing a very modular LLM-agent API (with memory, reasoning, and tool-use components), that integrate with Mesa’s existing architecture (Model, Agent, Scheduler), as well as studying and solving LLM-related problems like memory management, consistency and computing-related challenges.
<p>One of the selling points of new LLVM ORC Concurrent JIT APIs is we can speculatively compile functions before we need it, with the hope that when we call it in run-time it is already compiled. However, if we speculatively compile the whole module and its transitive dependencies we’re quickly going to overload the CPU/Memory resources and increase the start-up time of the application. To avoid this, we can select the functions ahead of time which are likely going to execute next and compile them speculatively, using runtime profiles from previous app executions and/or static program analysis.</p> <p>It helps to use leverage the performance of Just-in-time compilation using modern multi-core machine. It also helps to reduce the JIT compilation latency.</p>
This year's goal aims to enhance the TensorMap web application by addressing technical challenges and introducing functionalities to improve usability and efficiency. Key issues, such as dependency management and server-side complexity, will be tackled by Dockerizing the backend for easier deployment. Fixing the neural architecture design workflow will also be the main focus of this year's contribution. New features planned to be introduced into the project include support for image datasets with Convolutional Neural Networks (CNNs), addition of linear regression models for regression tasks, and dataset preprocessing for a better user experience. Finally, documentation on introducing new nodes for future contributors and users along with improved testing coverage for client-side reliability will also be implemented.
Description: To integrate KubeArmor with OpenTelemetry, an adapter needs to be created. OpenTelemetry is a standard for telemetry data, including distributed tracing, metrics, and logs, and has an SDK and a collector component that can run on Kubernetes. Applications can directly expose OpenTelemetry data through in-app instrumentation using the OpenTelemetry SDK. The collector can then gather data from multiple applications in a cluster and send it to various backends for storage and visualization, such as Jaeger. Expected Outcome: The mentee's task is to develop an OpenTelemetry adapter for KubeArmor that can receive logs, alerts, and telemetry from the kubearmor-relay-service and convert it into the OpenTelemetry format. They are also expected to create documentation and usage guides that describe how to set up and use the adapter, as well as demonstrate the integration with a backend that supports OpenTelemetry.