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.
AF_XDP is an address family that is optimized for high performance packet processing. AF_XDP redirects raw network packets to user mode through the XDP program. AF_XDP, like DPDK, can be used to bypass the Linux kernel to gain high-performance processing network packets. DNSDist acts as a load balancer and often needs to process and forward packets. Therefore, in order to forward DNS requests DNSDist needs the raw network packets processed by the Linux kernel network protocol stack, read its request, and send the same request to the downstream DNS server again through the Linux kernel network protocol stack. The repeated processing of the same or similar data by the Linux kernel network stack is an unnecessary overhead for the server deploying DNSDist. This overhead can be effectively avoided by bypassing the Linux kernel through AF_XDP.
<p>Boost.uBLAS employs numerous compile-time optimizations which improve the performance of matrix operations. However, there is no implementation of any application on matrices which can exploit this performance - like mean, variance, factorization etc. Providing some such fundamental functionalities for vectors and matrices in a single package would be a great addition to the uBLAS library. The goal of this project is to lay out the foundation of uBLAS to support basic statistical analysis methods and machine learning algorithms. More specifically, I am interested in implementing the following fundamental components:</p> <ul> <li>Basic statistics</li> <li>Running statistics</li> <li>Histograms - with custom number of bins and edges</li> <li>KMeans clustering</li> <li>Principal Component Analysis (PCA)</li> <li>Gaussian Mixture Model - Expectation Maximization</li> </ul>
<p>Cytoscape is a highly popular open source bioinformatics software platform for visualizing, analyzing, and publishing graphs or networks representing molecular interactions, gene expression, and other biological data. As a desktop platform, Cytoscape is one of the most successful open source projects in biology, and it is capable of integrating observational data from numerous sources.</p> <p>Currently, when users are working with a network of connected genes or proteins, they have to use external web tools to perform simple enrichment analyses, e.g., using g:Profiler. However, g:Profiler provides a web service interface, so it would be relatively simple to provide access to this same service from within Cytoscape. More advanced tools for enrichment already exist as Cytoscape apps, such as BiNGO and ClueGO. The goal to produce an app that could eventually be included in the core distribution of Cytoscape.</p>
Meshery Models are declarative representations of infrastructure and applications. Within these models, Relationships define how different Components (e.g., Kubernetes resources, Cloud services) interact and depend on each other. These relationships are crucial for visualizing, understanding, and managing complex cloud native systems. This internship focuses on significantly expanding the breadth and depth of Meshery Relationships across a wide array of technologies supported by Meshery. As Meshery continues to integrate with more cloud-native technologies (Kubernetes, public clouds, and all CNCF projects), there's a growing need to accurately model the intricate relationships between their components - vital for providing users with comprehensive insights and control over their deployments. Expected Outcome: - A multitude of new relationships defined both intra and inter GCP services. - Policy Contribution: For advanced interns, there may be opportunities to contribute to the Rego policies that evaluate and enforce these relationships.
Meshery Models are declarative representations of infrastructure and applications. Within these models, Relationships define how different Components (e.g., Kubernetes resources, Cloud services) interact and depend on each other. These relationships are crucial for visualizing, understanding, and managing complex cloud native systems. This internship focuses on significantly expanding the breadth and depth of Meshery Relationships across a wide array of technologies supported by Meshery. As Meshery continues to integrate with more cloud-native technologies (Kubernetes, public clouds, and all CNCF projects), there's a growing need to accurately model the intricate relationships between their components - vital for providing users with comprehensive insights and control over their deployments. Expected Outcome: - A multitude of new relationships defined both intra and inter Azure services. - Policy Contribution: For advanced interns, there may be opportunities to contribute to the Rego policies that evaluate and enforce these relationships.
NeoRoo currently talks to DHIS2 through raw HTTP calls with no offline support, so if a nurse loses connectivity while entering baby data, that data is just gone. I'm proposing to integrate the d2 Android SDK as the primary sync engine and build a Flutter abstraction layer on top of it that works across both Android and iOS. The main deliverables are: a Pigeon-based platform bridge to d2 (Android) and DHIS2 REST API (iOS), an offline-first sync queue using Drift/SQLite with automatic retry, a server-wins conflict resolution system with a review log, real-time sync status indicators in the UI, background sync with battery optimization, push notifications for server-side changes, and a testing + monitoring toolkit. By the end, healthcare workers should be able to use NeoRoo reliably regardless of connectivity.
Meshery Models are declarative representations of infrastructure and applications. Within these models, Relationships define how different Components (e.g., Kubernetes resources, Cloud services) interact and depend on each other. These relationships are crucial for visualizing, understanding, and managing complex cloud native systems. This internship focuses on significantly expanding the breadth and depth of Meshery Relationships across a wide array of technologies supported by Meshery. As Meshery continues to integrate with more cloud-native technologies (Kubernetes, public clouds, and all CNCF projects), there's a growing need to accurately model the intricate relationships between their components - vital for providing users with comprehensive insights and control over their deployments. Expected Outcome: - A multitude of new relationships defined both intra and inter AWS services. - Policy Contribution: For advanced interns, there may be opportunities to contribute to the Rego policies that evaluate and enforce these relationships.
<p>ALICE (A Large Ion Collider Experiment) is a heavy-ion detector on the Large Hadron Collider (LHC) ring. It is designed to study the physics of strongly interacting matter at extreme energy densities, where a phase of matter called quark-gluon plasma forms. The new ALICE synchronous data reconstruction facility for Run 3 needs a real-time conditions and calibration data distribution mechanism. New calibration objects are produced at up to 50Hz and have to be propagated to about 2000 servers. For efficient data distribution in this environment a network multicast delivery mechanism has to be used. There will be two sides to be implemented for this project: a library to send the newly produced objects and a caching service to run on each of the 2000 servers to receive and keep in memory the objects, making them available to the localhost running processes via a REST API.</p>
When a Cassandra node shuts down, clients experience timeout errors because drivers cannot distinguish planned shutdown from a crash. CEP-59 introduces a GRACEFUL_DISCONNECT event in the native binary protocol that lets the server signal drivers before closing connections. My implementation uses a self-draining mechanism that hooks into the existing cleanup() callback in CQLMessageHandler — each connection closes itself when its last response flushes out, after a grace period that accounts for network-latent requests. Three conditions added to an existing callback, no new threads or timers. Deliverables: server-side four-phase shutdown (SEAL, SIGNAL, DRAIN, DEADLINE), Python driver support with DRAINING host state, configuration and observability metrics, protocol spec update, and unit/integration tests. Java driver support as a stretch goal. JIRA: CASSANDRA-21265 (7 sub-tasks).
I will migrate the eos-icons.com website to TypeScript and Next.js and also implement proper file management and state management in the project ensuring a cleaner and more scalable codebase. I will also do certain changes to improve the website's UI. I plan to add a navigable menu to the landing page showing all categories of the icons. Also, adding a new and improved HowTo section which contains information about the usage of icons in all places like React, Vue2/3, & HTML, and moving it into a side drawer panel along with the icon editor. I plan to add unit tests by using Jest & React-testing-library, and end-to-end(e2e) testing with Cypress.js. I will integrate these tests with Github CI/CD pipelines and ensure proper development workflow using es-lint, prettier and husky.
<p>Energy system components are modular in nature and interact across multiple scales. There is a need for a modelling framework that can easily construct and configure systems of modular entities (energy demands, sources, converters, storages and network links). These systems should be hierarchically nestable, facilitating the construction of large systems at high levels of detail. The framework should also facilitate the approximation of sub-systems, to aid model solvability. The above framework should be implemented in an object-oriented fashion, making use of the modular >>Open Energy System Modelling Framework<< (Oemof). Components should be specified in a common format that integrates with a database of available entities. The implementation should allow particular systems to be duplicated and reconfigured as well as reused as subsystems in larger models. Configuration parameters of multiple sub-systems should be readable from an external table.</p>
Thunar is a modern file manager for the Xfce Desktop Environment. It supports 3 types of views - List View, Icon View & Compact View. As a part of my project I will be adding the functionality of tree-like expansion of non-empty folders in the List View. Additionally I will be adding a feature to enable file highlighting in Thunar. This will enable the user to highlight their favorite/important files with the color of their choice. Xfce also offers a terminal application called Xfce-Terminal. My project also includes working on Xfce-Terminal to introduce Profiles. Currently all settings in Xfce-Terminal are global. I will be adding the functionality and feature set to allow users to create profiles, amongst which they can quickly switch between across tabs. This allows the user to have different settings on different tabs/windows and simultaneously work with them.
Meshery Models are declarative representations of infrastructure and applications. Within these models, Relationships define how different Components (e.g., Kubernetes resources, Cloud services) interact and depend on each other. These relationships are crucial for visualizing, understanding, and managing complex cloud native systems. This internship focuses on significantly expanding the breadth and depth of Meshery Relationships across a wide array of technologies supported by Meshery. As Meshery continues to integrate with more cloud-native technologies (Kubernetes, public clouds, and all CNCF projects), there's a growing need to accurately model the intricate relationships between their components - vital for providing users with comprehensive insights and control over their deployments. Expected Outcome: 1. A multitude of new relationships defined both intra and inter AWS services. 2. Policy Contribution: For advanced interns, there may be opportunities to contribute to the Rego policies that evaluate and enforce these relationships.
Meshery Models are declarative representations of infrastructure and applications. Within these models, Relationships define how different Components (e.g., Kubernetes resources, Cloud services) interact and depend on each other. These relationships are crucial for visualizing, understanding, and managing complex cloud native systems. This internship focuses on significantly expanding the breadth and depth of Meshery Relationships across a wide array of technologies supported by Meshery. As Meshery continues to integrate with more cloud-native technologies (Kubernetes, public clouds, and all CNCF projects), there's a growing need to accurately model the intricate relationships between their components - vital for providing users with comprehensive insights and control over their deployments. Expected Outcome: 1. A multitude of new relationships defined both intra and inter AWS services. 2. Policy Contribution: For advanced interns, there may be opportunities to contribute to the Rego policies that evaluate and enforce these relationships.
<p>HsYAML is a pure Haskell idiomatic implementation of the YAML 1.2 data serialization language with a strong emphasis on compliance with the YAML 1.2 specification.<br> Currently, HsYAML is used for loading data in Haskell data types from a YAML character stream but there is no implementation for dumping data from Haskell data types to a YAML character stream. So, I am planning to work on the following features this summer:</p> <ol> <li>Implement YAML pipeline for dumping/emitting YAML </li> <li>Extend data-model to allow for load/dump round-tripping while preserving order, anchors, and comments.</li> <li>Improve error handling - More accurate error messages are always a great relief for programmers. Providing proper source-locations and/or fragments in a higher native/representation layer will do the needful.</li> </ol>
<p>The ultimate goal of the project is to develop & rework the Faces of GNOME website using modern site generators & JavaScript to showcase past, current GNOME contributors. It has the intention to let users create, maintain profile pages, add custom information and blogs etc.</p> <p>The project includes introducing bots for automating markdown profiles, adding RSS related features, managing SEO, setting up localization capabilities, reworking search queries, improving web performance, replacing old legacy code written in jQuery with modern JavaScript alongside deploying the website using GitLab CI services.</p> <p>The project aims to have a full code-complete solution, with documentation, guidelines, and all the pages complete and ready to be launched which would allow the Faces of GNOME to succeed not only as a project and but also as a program.</p>
The future is already here - it's just not evenly distributed” - William Gibson We’d like to introduce an idea for a new open-source project: Racklet. It’s a fully-integrated, Raspberry Pi form-factor server rack and software stack that aims to be a scale model of hyperscaler datacenters. All layers of the stack are 100% OSS/OSH, and will be developed together with the community. It’s reproducible through open PCB designs, 3D printed casing, and commodity, off-the-shelf hardware. We want to lower the barrier of entry for becoming cloud native. Racklet aims to inspire users to explore how modern server architectures work, in a tangible and educational way. Emphasis is put on security, knowledge sharing, extensibility, and portability. The goal is to conceptually map to real environments and provide an accessible and well-documented path to welcome future talents to the world of cloud native.
This project aims to enhance Wayshot by implementing the newly standardized ext_image_capture_source_v1 Wayland protocol, which provides a standardized method for display and window capture, replacing the current dependency on the non-standard wlr-screencopy protocol. I will develop a new backend that fully utilizes this official protocol while maintaining the existing wlr backend for backwards compatibility, enabling native top-level window capture capabilities and improving user experience. The implementation will include a security notification system utilizing D-Bus to alert users which applications were captured by Wayshot clients, enhancing transparency and user privacy. Additionally, I will integrate the standardized protocol with xdg-desktop-portal-luminous to enable WebRTC streaming capabilities, The deliverables of this project are: a complete solution that includes the new backend, backwards compatibility, security notifications, WebRTC streaming support, and comprehensive documentation.
<p>Flow Completion Time (FCT) has been the core metric to optimize via scheduling, congestion control, load balancing in Data Center Networks (DCN). As a user-perceived metric, FCT is one of the most important networks' performance metrics, as the users typically want their flows to complete as quickly as possible during their interactions with the network, e.g., webpage download, file transfer. The past decade has witnessed significant interest in studying the FCT minimization in networked systems research, especially in DCN.</p> <p>Current NS-3 are less friendly to researchers in this domain. This project aims to augment NS-3 with related components to support the simulation in the domain so that researchers would try out with a minimal amount of coding. The framework will supplement the NS-3 ecosystem with components such as Multi-Level Feedback Queue scheduling, topology helper, load balancing algorithms and so on.</p>
The Service Mesh Performance standard captures and characterizes infrastructure capacity, service mesh configuration, and workload metadata. When we run a performance test the service mesh performance capture these details as performance profiles and gives the complete analysis of the test run. I will be working on making a visual representation of these data that gives us a clear understanding of what the characteristics of the test are. It will provide us with a better understanding of the performance profile values sent by the CNCF infrastructure. To facilitate this I will be working on a benchmarking dashboard, where users will be able to analyze and compare the different performance test results. The project can be divided into two parts: 1. Working on the backend to fetch the SMP test results and query be able to query it on the frontend 2. Working on the frontend to discern these values, plot, analyze the data and give the user an ability to view these results and compare the effectiveness of the results.
Time Series models constitute an integral part of the machine learning stack. Time series tasks can span a wide range of tasks such as classification, regression, forecasting, etc. This project would aim to build elements of the FastAI.jl library, including high-level components for quickly generating state-of-the-art solutions for time-series tasks and low-level components for creating new novel techniques. The project would include adding support to load time series datasets using the FastAI.jl data registry, developing new methods for time series tasks, and training the models using best practices. We would also aim to write detailed tutorials on using, modifying, and creating new time series models for various tasks. We wish to achieve these goals without compromising on the simplicity of use, flexibility or performance that FastAI.jl can offer.
One of the most requested features for GIMP is support for CMYK and desktop publishing - there's even an FAQ entry on their site specifically for it! While GIMP is primarily focused on digital editing, their backend systems and libraries are more than capable of CMYK workflows. The goal of this project is to enable users to begin using GIMP for creating images for print. A basic implementation consists of three milestones: 1) Allowing users to import and export the most common "print" file formats (.tiff, .pdf/.eps/.ai, .psd) with CMYK profiles. 2) Developing a Dockable Dialogue to simplify the process of changing profiles, enabling soft-proofing, and other related tools. 3) Identifying and improving existing issues with Color Management as part of GIMP's Color Space Invasion initiative. While this basic implementation would not fully implement the "High-end CMYK support" goal in GIMP's roadmap, it would be a step in that direction, and could encourage users and developers to contribute further to that effort.
<p>The Akonadi framework is responsible for providing KDE PIM applications with a centralized database to store, index and retrieve the user's personal information. The data can be stored either in local files or can be synced via a host of services like Google Calendar, Microsoft Exchange WebServer (EWS) or a number of Groupware servers like Nextcloud, DAV etc.</p> <p>The proposed project is to add to this list a secure, end-to-end encrypted, FLOSS sync solution for your contacts, calendars and tasks, called EteSync. EteSync clients are available for Android, iOS, the desktop (Cal/CardDAV bridge) and the web, and a Thunderbird plugin is in the works. The server too is open-source and can be self-hosted.</p> <p>The idea is to implement an Akonadi backend resource to enable KDE users to use EteSync to easily end-to-end encrypt and sync their contacts, calendars and tasks.</p>
<p>Migrate Chat, Skill, Account SUSI.AI under a common app SUSI.AI. Create a set of common and modular components. For styling 1 common approach should be used, like styled-components. Enhance Admin section by adding Reported Skills tab, Mail configuration, Email Messages(with reCaptcha configuration), User, Skills Statistics for Admin Panel.</p> <p>Add more functionality to settings for users. Make the whole application mobile responsive. Integrating Redux and removing flux architecture for data flow. Implement stop action, SoundCloud action on chat. Fix preview chat code and scroll interactions.</p> <p>Implement slideshow slider, Google Analytics, multi-search for skills CMS. All the above features will be integrated on frontend as well on the backend. Integrate support for SUSI.AI Speaker with SUSI.AI web client.</p>