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 LibreHealth Radiology AI Model service aids radiologists with AI to produce fast and accurate medical diagnoses. It communicates with LibreHealth RIS module to output labels on DICOM viewer. Currently, CheXnet model is integrated to the AI Model service, but the proposal expands to apply other models to imaging modalities like Mammo, Head CT, Abdomen CT. The project aims to understand what radiologists need in terms of AI and implement it. The goal is to help radiologists perform better by implementing algorithms for new imaging modalities. To tackle the problem we start by looking at research that have looked deep into model architectures and methods that work well with imaging modalities, for example Alexnet have proven to work on modalities like Head CT. We then collect the imaging data necessary to train out models and also decide on the method of training like transfer learning on pretrained models or do we go ahead with training a model from scratch. Appropriate feature engineering and tuning will be part of the problem solving process. Once we establish a model to perform well on a modality we proceed to integrate the model to the AI Model service application. The deliverables will include - Collate information on data sources, methods and models that will be used for implementation and review with mentor(s) - For any modality, start with data preparation, feature engineering, training and evaluation until satisfactory performance is achieved. Here we will trial different augmentation techniques and hyperparameter tuning methods. - Integrate the model inferencing code and retraining code to the application for all modalities - Add methods to the Flask API to appropriately call the specific AI model for a modality. Modify existing methods as necessary so as to include the new AI models - Perform unit tests, integration tests, functional tests and end to end tests for the implementations. Necessary coding standards will be used.
This project aims to implement the necessary infrastructure for the Discontinuous Galerkin method in the finite element toolbox Ferrite.jl. This will include writing examples, documentation, and tests. DG method is a FEM like the continuous Galerkin (CG) method where the test functions are chosen to be the same as the trial functions. However, DG elements do not share degrees of freedom (DoF) at common nodes, introducing extra DoF and adding the process of choosing coupling between elements through numerical fluxes. The main deliverables are: • Methods to integrate on inner faces. • Extend the methods to integrate over subfaces. • Sparsity pattern methods for DG. • Implement infrastructure for handling boundary conditions for DG approximations. • 1-D, 2-D, and 3-D steady heat equation using DG example. • Testing and documentation for all implemented methods.
This project aims to port the remaining tree elements to the new object-oriented design of the Outliner codebase. The project will involve creating new subclasses, modifying existing code, thoroughly testing changes, and documenting the modifications made. The deliverables for this project include a detailed report and updated code of new AbstractTreeElement sub-classes representing the remaining tree elements. The project will contribute to the ongoing development efforts of the Outliner by providing a necessary refactoring that will make future development work easier and more efficient, and the Outliner module's documentation will be improved.
LibAFL, a library written by Rust, helps people develop a fuzzer tailored to specific needs, but due to the lack of the running status information of LibAFL, we are difficult to grasp some key metrics in a fuzzing campaign. so I propose adding AFL-style UI to the TUI monitor. LibAFL will have an AFL-style UI encompassing some key status metrics such as the status bar, process timing, and so on.
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.
This project focuses on migrating JavaScript codebase to Typescript. Zulip is in the process of porting the main web app JavaScript codebase to TypeScrip. Zulip’s 8% of lines have been migrated while the goal for this summer will be to get that to ~75%. The challenges for migrating JS to TS include circular imports, a large number of interdependent modules, tracking down complex cycles, multiple cycles in one module, order of conversion, and understanding types and their relationships. The proposed solutions include classifying circular imports, passing callback workaround, extracting common functionality into a third module, and writing unit and integration tests to ensure the migrated codebase functions properly.
The idea is to add thumbnail preview on the UI while seeking. Tasks to be accomplished include: extend the preparser to take snapshot of a video every few minutes/seconds, and adding qt and/or macOS support: display the snapshot taken by the prepaser while seeking.
This project proposes novel evaluation metrics for anomaly segmentation in computer vision, taking into account pixel-level and spatial information. The aim is to provide a more comprehensive evaluation of anomaly segmentation algorithms, aiding researchers and practitioners in selecting and fine-tuning models. The first proposed metric is the False Positive Blob Relative Volume (FP-BRV), which accounts for the visual nuisance of false positive pixels, complementing the Per-Region Overlap (PRO). The proposed metric will be evaluated on popular anomaly segmentation public datasets and visually validated. Milestones: prototype implementation, testing and validation on public datasets, production implementation, optimization/unit testing/documentation, and research paper writing. See "Section 5 Detailed project proposal" in the PDF for details and a timeline.
Mathesar is an open-source, web-based database management tool that is easy to use, flexible, and scalable. It provides users a simple, intuitive interface for managing their databases, including creating and editing tables, defining relationships between tables, and querying data. Mathesar UI allows users to import data from CSV and TSV files. We aim to expand this functionality into importing JSON and Excel files too. The project will allow users to import JSON and Excel files and create a table from the imported data. The user can preview the table, remove/rename columns, change data types, and more. If the imported file is not in a suitable format for creating a table, we will develop algorithms to convert the file into a suitable format. If the algorithm doesn’t work, the system will refuse to import the file and give the user a readable error.
The Airavata Django Portal is a web interface to the Apache Airavata API implemented using the Django web framework. Gateway admins need period reports on user count, running experiments, resource usage, and other relevant information to aid in their reporting and planning activities. The primary task is development of dashboards where admins can get quick statistics. Data to be displayed on the dashboard is to be taken from Airavata databases making use of Airavata APIs. Apache Superset along with other libraries can be employed to create the required dashboards using Vue.js.
The C++ Standard Template Library (STL) provides many algorithms to sort, search, and perform a variety of operations on numerous data structures in its algorithms library. However, a major issue with the STL is that it is not optimized for parallel programming. Despite the fact that nearly all processors ship today with multithreading available, the STL is currently single threaded, leaving its algorithms library running at suboptimal efficiency. Taskflow is a C++ parallel programming library that organizes functions into tasks that it then can run concurrently or consecutively, depending on the user’s goal. My project will reimplement the STL’s algorithm library using Taskflow so that it can take advantage of multithreading.
This project aims to improve the scale and navigation inside the Phoenix application which is basically an Angular-based web application written in the ThreeJS library to visualize high-energy physics events in 3D. The application renders a detector that detects the collisions of particles that have been accelerated up to speeds comparable to that of light, along with the event data that consists of tracks, jets, missing energy, etc. after the collision. The problem statement is to improve the visualization of the event, for example, by developing a customizable and interactive cartesian grid functionality, so as to better give the idea of the locations and distances of the particles to the researchers. Also, the user should be able to view the dimensions of the individual detector parts. Apart from this, the users should be able to navigate to the individual detector parts. My plan for the first problem is to introduce a 3D cartesian grid with multiple equally spaced XY, YZ, and ZX planes, as well as, to be able to display the 3D coordinates of a point on clicking. For this, I will make use of the ThreeJS raycaster intersects. Also, I am planning to render the Euclidean distance between any two points clicked. To view the dimensions of the detector, I am planning to render the dimensions of the bounding box of the component. The solution for the second problem would be to list the detector parts and let the user select any one of them, after which it will be highlighted using a ThreeJS outline pass.
In particle physics, a cross section is a measure of the likelihood that particles will interact or scatter with one another when they collide. It is a fundamental quantity that is used to describe the probability of certain interaction occurring between particles. The determination of cross-sectional area necessitates the computation of the squared amplitude, as well as the averaging and summation over the internal degrees of freedom of the particles involved. This project aims to apply symbolic machine learning techniques to predict the squared amplitudes and cross section for high energy physics.
Make the developer experience for Carbon developers better by adding support for Carbon to editors and IDEs. Possible tasks include: Create an "official" VSCode extension with a mirror repo and packaging similar to the Vim repo we provide. Add syntax highlighting using a Tree-sitter grammar for Carbon. Create a language server for Carbon Deliverables • A working language server for Carbon that supports features like code completion, diagnostics, and go to definition. • A parser that can handle incomplete or erroneous input and produce a Carbon AST. • A test suite that verifies the correctness and performance of the language server. • A tree-sitter parser for Carbon that passes the explorer test suite. (Optional)
LuCI is a framework used to build web interfaces for configuration and monitoring on embedded devices such as WiFi routers, etc. In the old CBI based system, pages were rendered on the router and delivered as HTML to the browser, leading to a higher load on the embedded devices. To address this issue, LuCI applications must be migrated to JavaScript-based framework to reduce the load on embedded devices and improve performance. This migration involves rendering pages on the client-side using JavaScript, rather than on the router. To facilitate this migration, LuCI provides a JavaScript API that will be used to build web interfaces that can be rendered in the browser. To make this migration possible, new RPCD services will be developed to provide data to the client side that was formerly used directly on the router. This data will be provided in JSON format via RPCD (Remote Procedure Call Daemon) and UBUS. These new RPCD services will need to provide the same functionality as the old system but in a format that can be used by client-side JavaScript. The migration of LuCI to JavaScript-based framework will offer several benefits to OpenWrt community and other users of OpenWrt-based devices. One of the primary benefits is improved performance and reduced load on embedded devices such as WiFi routers. By rendering pages on the client-side using JavaScript, rather than on the router, this will reduce the workload on the router and improve the UX for those interacting with the LuCI web interface. This will be particularly beneficial for users with lower-specification routers etc. Another benefit of the new system is increased flexibility for developers. The use of a client-side JavaScript framework provides developers with more options for customizing and extending the LuCI web interface. And this also provides a standardized way for developers to interact with the router's services which should make it easier to develop and maintain LuCI-based applications.
Some programs should be created and curated using Arti to illustrate to other developers how they can use its APIs and to also find bugs. This includes 3 example programs to let developers get their feet wet with Arti and 2 bigger projects which would have a legitimate, production use case and can benefit from all that Arti provides, even in its current infancy. There will also be documentation improvements made, especially to APIs that these example projects rely on, in order to more directly contribute upstream to Arti.
This proposal aims to simplify the use of Jenkins with Docker by creating easy-to-use Docker Compose files with suitable examples. The process of getting started with Jenkins with docker is too complex and the available documentation is also hard to understand making it challenging for new users to get started. By simplifying the use of Jenkins with Docker, we can enable more developers to take advantage of these powerful tools together and accelerate their software development process. The main point of the project is to simplify the spinning up of the container to run a Jenkins instance with a single command. That’s where Docker-compose comes to the rescue which uses YAML files to spin up multi-container setups. The expected outcomes after completion of the project are an elegant docker-compose file, comprehensive documentation on the workings of these docker-compose files with examples, a Jenkinsfile will be added to ci.jenkins.io with instructions to check the docker-compose files and as these docker-compose files will be able to run on Gitpod we will be able to create a one-click setup for Jenkins using docker and Gitpod.
The introduction of external plugin extends the functionality of the Kubebuilder CLI tool by allowing users to create and use custom plugins. These plugins can be written in any programming language, as long as they implement the interface specifications to interact with Kubebuilder. This proposal aims to provide best practices based on tutorials, testing and documentation. It also suggests the kube-state-metrics plugin as a sample project, which would scaffold the configuration for KSM to load and populate metrics for CR/CRD. The overall efforts are attempted to guide Kubernetes developers to learn how to write, install, and use their own Kubebuilder plugins.
I am writing to express my interest in contributing to GitLab's Pajamas Migration project as part of the Google Summer of Code program. As a computer science student at South Asia University, I am eager to gain more experience in the open-source community, and I believe that contributing to Pajamas Migration would be an excellent opportunity to do so. In Pajama Migration We have to ensure that all of the frontend components we use are GitLab-UI components, there are still some pages that are not using the right components. I am already Involved with Gitlab through MLH Fellowship and am working with the Foundation Team under the mentorship of our maintainer (James Rushford). James was a really great leader and mentor. I have worked on the following issue so far 112392, and 115432, and right now I am working on Pajamas Migration with our maintainer(James) on issues #395782 and #396775. my Deliverables will include~ : Complete Pajamas migrations. : Build out the design system. : improve user experience My plan~ May 4 - May 30: read project-related documents and codes, and get started quickly. May 30 - July 5: reasonably divide the work with another contributor, and record the corresponding documents at the same time. july 5 - august 21: will continue work on our plans and will try to complete our mission and also will get feedback from the mentor. my previous experience at MLH with Gitlab was incredible. I gained valuable technical and soft skills, and I had the opportunity to work on real-world projects with experienced developers. Working with Gitlab helped me gain a better understanding of DevOps.So, I am looking forward work with GitLab again. I am looking forward to hearing back from you and learning more about how I can get involved in this project in your way. Maybe by giving more details? Knowing the Scope. Thank you for considering my application.
OpenMRS is a medical record system that has previously allowed the uploading and visualisation of patient conditions through diagrams. This feature has been critical in helping doctors better explain patient conditions to their patients. However, the module lacked certain essential functionalities that could improve the user experience. Therefore, this project aims to improve the diagramming feature in OpenMRS by allowing the upload of any diagram as an image, annotation of certain areas of the diagram with different shapes, saving and retrieving these diagrams, and additionally downloading them as an image with the edited annotations. The project has two parts, essential and desirable objectives. The essential objectives aim to provide the basic functionalities for uploading and editing diagrams while the desirable objectives enhance the user experience by adding more features. Essential Objectives: Allow users to upload any diagram as an image to the module Enable users to annotate certain areas of the diagram with different shapes such as circles, squares, and single points, etc.. Allow users to save the annotated diagrams for future reference Enable users to retrieve diagrams from a list of already saved ones Desirable Objectives: Allow users to draw free shapes on the diagram and annotate them with a description text Enable users to download the diagrams as images with the edited annotations, allowing for easy sharing and printing.
The proposal outlines a plan to increase compatibility for two classic games, "Total Distortion" and "The Journeyman Project," on the ScummVM platform. The project aims to fix bugs, thoroughly test the games, and ensure they are production-ready by the end of the timeline. The project's benefits include increased access to classic games, increased community engagement, improved stability of the Director engine, and increased interest in the engine. The deliverables include identifying and fixing bugs, prioritizing issues, regression testing, and rigorous testing for official support!
SMT solvers are widely utilized in computer-guided verification of computer programs and artificial intelligence. With a multitude of theories employed in these solvers, it is beneficial to have access to a diverse range of solvers and to minimize the challenge of learning a new API for each of them. Using the solver’s own API directly makes it difficult to switch to another solver without rewriting extensive parts of the application, as there is no standardized binary API for SMT solvers. Also, since these SMT solvers have varying degrees of capabilities and performance and may not accept the same input, frameworks were created, that offer a unified API to several SMT solvers. JavaSMT has exactly these attributes, a common API for SMT solvers. The framework provides access to a variety of solvers created using Java and other programming languages. Although most solvers share a common set of supported theories and features, their availability of extra theories and performance may differ. Therefore, the inclusion of additional solvers in the framework is advantageous to its users. SMT formulas over the real numbers can encode a wide range of problems in theorem proving and formal verification. Such formulas are very hard to solve when nonlinear functions are involved. For that reason, the SMT solver dReal will be implemented in JavaSMT. The SMT solver dReal is a solver that solves nonlinear formulas over the reals. The solver can handle various nonlinear real functions such as polynomials, trigonometric functions, exponential functions, etc. The goal of the project will be to integrate the SMT solver dReal into the JavaSMT framework and to include it in the existing JavaSMT tests.
Concore is a lightweight framework for closed-loop peripheral neuromodulation control systems. Control-editor is a React-based frontend environment for concore. It allows users to create studies as graphml files and program files. This project will allow the users to upload their examples to the concore repository automatically without using GitHub.These examples will help new or existing users to generate and understand studies quickly.
At present, selecting a radius or bounding box to cover a desired region and then filtering the retrieved points is a viable option for narrowing down results by a specific region of interest. However, this method can become sluggish when dealing with expansive areas and entails handling location data separately in a database. Introducing a more efficient feature for intricate geo-filters would 1) speed up the process, 2) create opportunities for novel applications, 3) open the door for further opportunities of optimization. Such a feature would be particularly beneficial for Qdrant's users dealing with vast data sets or intricate geometries