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.
RDMA can be implemented with many different network backends, including InfiniBand, RoCE and Soft-RoCE, TCP/IP and UDP via iWarp, Cray GNI, and Amazon EFA. However, rFaaS presently only supports a verbs backend, such as RoCE or InfiniBand. This project expands support of rFaaS to include a more extensive range of networking backends using libfabric. As a result, rFaaS is now much more versatile, accessibly, and widely deployable. Complete with a proper configuration system, users of rFaaS are now able to easily choose the protocol they wish to use on their cluster.
My proposal is to develop a NextFlow pipeline that will efficiently and accurately perform repeat annotation and masking on large genome sequences that are filled with repetitive elements. The pipeline will be designed to handle genome chunking and multiprocessing to ensure efficient use of computational resources. The pipeline will take a genome sequence in FASTA format as input and use the RepeatModeler tool to generate a de novo repeat library for the input genome sequence. It will then use RepeatMasker to mask and annotate the repeats in the input genome sequence. Additionally, it will use Dust to mask and annotate low complexity sequences and TRF to mask and annotate tandem repeats in the input genome sequence. The pipeline will combine the results from these steps to output a masked genome sequence in FASTA format and annotated repeats in GTF format. Furthermore, the pipeline will use the tool RED to perform additional masking and output an additional masked genome sequence in FASTA format. The pipeline will be deployed in the cloud using the Embassy Cloud within the EMBL-EBI infrastructure to allow for testing and scaling, with the aim of determining the cost of running it at scale. The main problem that this proposal aims to solve is the challenge of identifying and masking repetitive elements in large and complex genome sequences. The pipeline will provide a detailed and informative annotation of the repeats within the genome, making it easier for researchers to analyze the non-repetitive regions of the genome. The deliverables of this proposal will include a NextFlow pipeline for repeat annotation and masking, a de novo repeat library for the input genome sequence, a masked genome sequence in FASTA format with repeat, low complexity, and tandem repeat annotations, an annotated repeats file in GTF format, and an additional masked genome sequence in FASTA format generated using the tool RED.
Currently InVesalius does not support simultaneous visualization of structural MRI and fMRI volumes. This is however of large interest to visualize both modalities for people involved in the clinical and analytical domain. Indeed a direct implication would be to have functional connectivity induced graphs visible along with structural connections (white matter). On top of which, after generating 3d maps, it may then be possible to visualize in space the functional connections versus structural connections. First of all, this project would be a useful feature to InVesalius, but secondly also to the neuroscience community. By having InVesalius open source and in a UI format it would enable clinical experts or neuroscientists without engineering background to have ready to go visualization of fMRI and structural MRI volumes. In general this could be extended to other modalities as well. Two possible ways to simultaneously visualize structural MRI and fMRI are: 1. Overlay different masks or contrasts (need to be carefully picked) for each of the two modality. There might be a need to apply some color distribution matching between structural and functional (e.g histogram equalization) since one would be T1 and the other T2 to have better visualization. Both slices would need to be co-registered prior to overlaying. The effect on the generation of 3D visualization would also be cared for. 2. Having two views or preview of fMRI in each orientation (sagittal, coronal, axial and 3d). Two views or one main view and a preview would require to have a tracker (dot) that points to the same voxels in the two views. This could be a way for the user to match regions for instance and essentially avoid crowding the visualization. The language I plan on using and believe fits the project would be python. The potential libraries used during the project would include already required ones for InVesalius (e.g scipy,opencv)
Clang includes libInterpreter, a framework for incrementally JIT compiling and executing C++ code. The goal of the project is to port this to WebAssembly and run inside a Javascript engine in a browser. This would involve modification to libInterpreter to run in WASM and produce WASM JIT code. These separate WASM modules need to be linked together and executed in the JS engine. If possible, the final goal is to integrate this with JupyterLite, a version of Jupyter that runs WASM kernels entirely on the client side.
The project "iOS versions of Android components" aims to develop iOS counterparts of popular Android components that are widely used in mobile app development. The objective is to provide iOS developers with an easier transition between the two platforms, by providing iOS versions of Android components that they are already familiar with. The project will involve identifying and analyzing popular Android components, understanding their functionality and behavior, and then developing their iOS counterparts using Apple's development tools and technologies such as Xcode and Swift. The iOS versions of Android components will be designed to be compatible with the latest versions of iOS, including iOS 14 and higher. The components will be thoroughly tested to ensure compatibility and reliability across different devices and operating system versions. This project will be beneficial to developers who are familiar with Android development and are looking to transition to iOS development. It will also be useful for iOS developers who want to incorporate popular Android components into their iOS apps. Overall, the project aims to improve the ease of transition between Android and iOS development, and ultimately enhance the user experience of mobile apps across both platforms.
Create a new system panel to provide users with a unified interface for managing various settings. we can achieve it by merging Date & Time, Users, Region & Language, and About panels, and Implementing a Remote Desktop page into the system panel. It will provide a more streamlined and user-friendly experience for GNOME users.
25% of engineering time is spent on devops chores. The aim of this project is to automate those 25% to free researchers to do science full time instead of hoping between research and technical support.
The short term goal is to improve unit test coverage for PEcAn base packages. The overall PEcAn ecosystem of packages (e.g, models and analysis modules) are heavily dependent upon these packages, thus having a good test coverage for these would improve overall system reliability. The medium term goal is to increase the reliability of PEcAn’s integration tests, and thus my second round of package testing and refactoring will prioritize the packages that are most associated with overall workflow bottlenecks (e.g., PEcAn.data.atmosphere, which is focused on downloading and processing meteorological data). An added long term goal would be to document testing approaches to make adding tests more smooth and consistent across packages for future packages or functions that get on-boarded, thereby making them more maintainable and reliable.
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.
PyBaMM has a tedious installation process for development , which proves to be difficult for developers & researchers or anyone who wants to develop it. This project aims to simplify the installation process through Dockerization and make PyBaMM more accessible. In addition to that present Continuous Integration(CI) would also be modified in order to integrate dockerization with current workflow.
Cookiecutter is a powerful command-line utility that generates project templates. Open science lab has developed a template that aims to provide the workflow, library, and tool recommended by PyOpenSci. This project aims to improve the document and add a different tool, add build systems, testing libraries, and more static analysis tools, and change the template engine from cookiecutter to cookieninja.
The main target of this project would be to work on migration to user groups for permissions which aims to replace every setting in Zulip that currently allows organizations to assign permissions based on role (admin, moderator, etc.) with a setting based on arbitrary “user groups”. I would majorly work on areas of settings and stream settings, migrating the existing settings to the new model and adding new settings based on the new permission model.
The primary format to share resources in Krita is a Resource Bundle, which is a compressed file containing all the resources together. It also contains some other information like metadata and a manifest so Krita can check there’s no errors in the file. Krita’s Bundle Creator allows one to create their own bundle from the resources of their choice. The project aims to improve the user interface of the current Bundle Creator, and allow the ability to edit bundles (which is currently not supported in Krita).
The main goal of this project is to create a dedicated repository for the R interface code of Volesti, a tool developed by GeomScale for volume computation and sampling in high dimensions. Currently, both the C++ and R interface code reside in the same repository. To achieve this, the existing codebase will be split into two separate repositories. This separation will involve modifying the package description file, R documentation files and R source code files in the new R interface repository. Additionally, the existing tests will be adjusted to match the new package structure and a comprehensive set of test cases will be developed to cover all the essential features of the R interface. Furthermore, the R interface code will be updated to ensure compatibility with the latest versions. Lastly, thorough documentation will be created for the new R interface, explaining the functionality of various functions and arguments, providing practical examples of package usage and demonstrating how the R package integrates with the wider Volesti ecosystem.
Macro is a metaprogramming feature that allows programmers to analyze and synthesize code at compile-time. Scala 3 supports a powerful yet type-safe macro system that allows analysis of the structure of code fragments via quote pattern matching. In this project, we aim for two goals: 1. The current implementation of quote pattern matching does not have many tests and is expected to be unstable. I propose making the feature more reliable by creating a checklist that captures which language features should be supported and adding more automated tests based on the checklist. 2. The current quote pattern matching does not support extraction of polymorphic functions. I propose extending HOAS patterns to support pattern matching against polymorphic functions based on formal definitions.
The goal of this project is to develop a cli-based software deployer that will allow anyone to quickly spin up a payment stack consisting of Fineract and Mojaloop with Payment Hub EE as the middlewear. This will allow for easy testing by potential adopters. It will serve as a proof of concept for what kind of transaction use cases can be achieved using Mojaloop and Fineract connected via Payment Hub EE. I will collaboratively develop a deployment script that will adapt the already existing deployment methods for the Fineract, Mojaloop and Payment Hub EE and fuse them into one seamless deployment workflow
Qaul is an Internet independent wireless mesh communication app. With qaul, you can communicate directly from one device to another. The aim of this project is to create a matrix bridge between Matrix and qaul which can further help us to broadcast messages over many mediums of communication which are supported by Matrix. Main aim is to implement the relay bridge and double puppeting.
The aim is to develop a desktop application (GUI) that allows users to run their Deep Learning experiments that is integrated with PyTorch library via drag&drop environment. The users should be able to construct a pipeline visually, without dealing with the code, and apply the selected/designed deep learning models to the data easily.
RADIS is a fast line-by-line code for synthesizing and fitting infrared absorption and emission spectra, such as encountered in laboratory plasmas or exoplanet atmospheres. It uses a line-by-line approach, where each absorption or emission line of a molecule is computed by accounting for the influence of environmental parameters. High-temperature spectral calculations require resolving the shape of tens of millions of lines, which is the usual performance bottleneck. RADIS implements a new algorithm to compute these lineshapes and is already one of the fastest line-by-line spectral codes available. It can also compute many different types of spectra (absorption/emission/equilibrium / non-equilibrium). However, although the algorithm is very CPU/GPU efficient, the RADIS code is still memory hungry. Databases are currently loaded in RADIS using the VAEX [3] package, but the operations to calculate the spectra are performed using the PANDAS library. VAEX is a similar table management tool to PANDAS but uses memory mapping, a zero-memory copy policy, and lazy computations for the best performance. The main goal of the current project is to refactor RADIS so that dataframes are only manipulated via the VAEX format. Potentially, this work would make it possible to compute spectral databases of up to billions of lines (hundreds of GB or terabyte-scale databases).
Discovering new music can be quite an adventure and may lead to finding music which you will hear on repeat for a long time. Currently, ListenBrainz offers many ways to do it, like Fresh Releases, Hue sound, Similar Users and many more. Another powerful discovery tool which can be added to suite is an Artist Similarity Graph. It will provide an intuitive way for the users to analyze relationships between artists. In this way, the users can get exposure to new artists with a music style similar to their favorite artists. This project aims to provide a pleasant UX for the same, while delivering the following features in the UI: 1. Display a graph of related artists. 2. Link to artist's MusicBrainz profile. 3. Play artist's most popular album. 4. Play the most popular recording.
SE-0249 introduced key path expressions as functions to the Swift language, to allow Swift users to write a more concise \Root.value in place of the more verbose { $0[keyPath: \.<member>] } wherever key paths are used as literal expressions. During compilation, the key path expression root and value are sequentially type-checked to resolve a key path type from this context. However, the current design of how the type-checker evaluates key path component types, their relationships to each other, and key path capabilities results in incongruous compiler errors for otherwise valid Swift code. This proposal briefly explores how key path expressions are type-checked today and suggests how this type-checker process can be made more robust, dependable, and faster.
KomMonitor is an open-source web client developed by the Bochum University of Applied Sciences as a research project. It has been developed in Angular JS and it provides users with a range of features, including the ability to search for and view data, customize maps, and perform spatial analyses, statistical visualization, etc. The web client uses Angular JS as its main framework. The current KomMonitor client is developed in AngularJS, there are some potential disadvantages to consider, include compatibility issues, limited community support, reduced performance, and limited scalability. As a result the solution to overcome the problem is to consider using a more modern and widely-supported framework in the development of the KomMonitor Web Client, such as the latest version of Angular supports Typescript, a superset of JavaScript that provides strong typing and data binding, Services & other features that help developers write more maintainable and error-free code, improves performance, scalability, etc.
Contributing to an open-source project offers novices the opportunity to join a community of practitioners, build a technical portfolio, gain experience with industry tools and technologies, and have a real-world impact. This project seeks to invite and support broader, more diverse participation in open source by supporting early contributors – especially those who have been historically minoritised within tech. The project will aim to accomplish the following tasks: Creating content that anyone with some Open Source experience can use to help and guide other completely new students to the journey of OpenSource, GitHub, and all the relevant technologies. This step would involve creating content in the form of transcripts, markdown guides, blogs, and some video content, which would serve as instruction manuals or workshop notes. Providing a medium and a platform for all contributors to share their various OpenSource experiences and testimonials. The same can be done in textual or multimedia formats like videos and photographs. Conducting an Open Source Themed Hackathon/Scavenger Hunt: We can organise a simple scavenger hunt for students on GitHub, where they can be provided simple tasks like creating issues and commits! GitHub workflows are an excellent tool for auto-evaluation of the same. Technical documentation will also be provided on how other users can create their own hunts. Social Media Engagement: Social media is where most youngsters are these days. Thus, we should be leveraging the power of the same to get young minds acquainted with the technical and open-source world at a young age so they can consciously choose to explore it further.
The ultimate goal of the proposal is to develop a feature that provides users the ability to effortlessly add closing credits to their edited video. This is achieved by making use of wpe plugin in gstreamer that is able to turn an HTML file into video