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.
Scribe is a keyboard application for language learners. It sources its data from Wikidata. 1. Adding a menu to the application: - Currently, the Scribe application only displays the installation guide and a link to the open-source repository. - The design for the menu as seen in the figma file found in the repository of Scribe-iOS suggests the creation of multiple different screens that navigate to sections -- Installation, Settings, About and further sub-sections. - We can assume a simple navigation stack where the bottom most layer is the main ViewController. This is achieved using a NavigationController on the first view that is presented. 2. Adding more languages to the application - The data used by Scribe-iOS is generated and processed in the Scribe-Data project repository. - The deliverables here will include generating data for all the planned languages that need to be added to Scribe, cleaning and processing data to obtain language data files, creating and assigning corresponding files and variables in Xcode for all languages and user testing.
Currently, GCP Scanner does not support the parallel enumeration of GCP resources and parallel scanning of GCP targets. This project is aimed to address this shortcoming. Also, GCP Scanner has one giant scanning loop from where it launches GCP resource crawlers. We need to split each crawler into individual modules with proper error handling that will improve code readability and quality. We can leverage python classes for the state of execution control, config parsing, and enabling/disabling certain functionality in the scanner.
Original project proposal: https://projects.freifunk.net/#/projects?project=openwrt_ppa_part_2&lang=en Currently, compiling OpenWRT packages for a device router requires dealing with the non-standard build system SDK. It would be very useful if this could be abstracted away by a generic build system. This project proposes integration with OpenSUSE's OpenBuildService, which also provides automation and remote compilation. The plan currently looks like the following: 1. Document the existing approaches on automating the build system. 2. Write a build script that integrates with the obs-build repository. 3. Get security approval, as documented in https://github.com/openSUSE/obs-build/blob/master/HOWTO.add_another_format. 4. Verify the system works by testing on https://openbuildservice.org. I have already contacted zoobab (Benjamin Henrion), the mentor for this project and I have successfully verified that cascading Docker images successfully compile a package.
This project will upgrade the popular command-line tool Wget2 to support the latest HTTP/3 protocol. Due to this, the users will get the advantage of performance improvements, including reduced latency, better handling of packet loss, and fast and efficient file download. The deliverables of the project will include a modified Wget2 codebase which will integrate with the nghttp3 and ngtcp2 libraries for QUIC support and GnuTLS for TLS encryption. It will also test and verify that the HTTP/3 implementation is correct and performs as expected. This project will benefit the open-source community by making it easier for users to adopt the latest protocols and improve their web browsing experience.
On-machine Inspection (OMI) is a valuable tool used in CNC commercial manufacturing to ensure proper tolerances of the manufactured piece. This is done by attaching a probe to the tool head of the machine and scanning the surface of the finalised product to see if there are discrepancies between the expected result and actual measurements. Including such a tool on FreeCAD, which already has a dedicated set of tools for CNC milling in the Path Workbench, will not only bring it closer to proprietary solutions but even surpass some of them that don't have this feature. This would save time for the machinist and also increase the inherent accuracy of the whole process. Building upon this, sensing solutions can introduce novel approaches to improve the CAM workflow and even generate new solutions not seen before. This proposal argues for an automatized post-processing of, for example, 3D prints by milling them to correct tolerances and inherent defects of the manufacturing process like layer patterns, over-extrusion or limited resolution. For On-machine inspection, there are already commercial solutions available so it's a matter of replicating their implementations on Python for FreeCAD. For the post-processing tool, a more involved overview of optimization algorithms for closely-matching volumes will be needed but it's surely available in the literature. If not, my background in mathematics and physics should prove valuable in the development of such an algorithm. Thus, the main goals for the proposal are to prodive the FreeCAD Path Workbench with two new tools, On-machine Inspection and automatized post-processing of already manufactured pieces, and also to properly test and document these new tools in the FreeCAD wiki.
Pycxxwrap is a versatile Python decorator used to wrap C++ code into Python using Pybind11. It serves as a wrapper around Pybind11, a lightweight, header-only library that facilitates the exchange of C++ types between Python and C++. The primary goal of this project is to provide a Pythonic interface for C++ libraries, simplifying their usage and enabling the creation of Python libraries from existing C++ ones. Additionally, Pycxxwrap includes special support for the HPX library, a C++ Standard Library for Concurrency and Parallelism, using custom header files.
Snowflake is a pluggable transport that helps users bypass censorship and access the Tor network. It uses webRTC technology to create a peer-to-peer connection between the user's browser and a volunteer proxy server. The Tor project aims to create a new and improved website for Snowflake that provides a better user experience for both new and existing users. As the Snowflake has gained a lot of popularity recently, it has seen a significant increase in the number of visitors with various doubts and queries The existing website does not effectively address these concerns, so our goal is to create a user-friendly static & secured website that is easy to navigate and provides clear information about Snowflake and its proxies. At the End of this summer: 1. A new static website with a modern and intuitive layout for desktop and mobile devices integrated with other Tor Web products & follows tor's brand guidelines. 2. Improved Snowflake proxy guide for new and existing user 3. Ensuring the website is sustainable and easy to maintain by new contributors & developers over the long term.
Funded by GSoC this summer, I propose to add collision detection to CGAL in a way that naturally builds on and extends CGAL’s existing AABB-tree functionality. The project will focus on implementing trusted collision-detection methods, which are attested to by their use in projects like the Godot game engine as well as their continued academic propagation through works like Ericson’s “Real-Time Collision Detection” and courses like UT Austin’s “CS395T: Physical Simulation”. I envision the project having the following deliverables: - Modifications to CGAL’s existing AABB tree functionality where necessary, e.g. to handle moving bounding boxes and dynamic restructuring of the bounding volume hierarchy - Broad-phase collision detection routine that utilizes CGAL’s AABB tree to quickly rule out unnecessary collision queries and identify potential collision pairs - Narrow-phase collision detection routine that performs fast collision tests on the pairs of primitives identified in the broad phase - Tests to cover all changes and new functionality - Documentation of the above The full proposal can be found here: https://hackmd.io/@1V1uNkwcQMiMbp_OanOjUA/r1kG1v_-3
Submitty currently has unit and integration tests that take over an hour to complete, the goal is to reduce the run time of the tests by at least half, while adding more tests to increase the code coverage, in order to limit the amount of inaccurate changes being merged.
I am excited about the opportunity to contribute to the LibreHealth EHR project by migrating the User's Module to the new Laravel codebase, revamping the User Interface, and updating the documentation. The primary objective of this project is to migrate the User's Module to the new Laravel codebase without any loss of data or functionality. As a developer, I have the necessary skills and expertise to work with both the Legacy codebase and the Laravel framework. I will work closely with the LibreHealth EHR team to ensure that any required adjustments to the current codebase are made to ensure compatibility with the new framework. In addition to the code migration, I am committed to enhancing the User Interface of the User's Module. With my extensive experience in UI/UX design, I will work closely with the LibreHealth EHR team to gather feedback on the current UI and design an updated version that aligns with their needs. I believe that this will enhance the overall user experience and make the application more user-friendly. Finally, I understand the importance of documentation in ensuring that developers can easily understand and work with the codebase. As such, I will update and improve the project's documentation to ensure that other developers can easily understand the codebase and contribute to the project. I will document the migration process, including any adjustments made to the current codebase, to ensure that it is clear and understandable to other developers. In summary, I am excited to contribute to the LibreHealth EHR project by migrating the User's Module to the new Laravel codebase, revamping the User Interface, and updating the documentation. I believe that my skills and expertise make me a strong candidate for this project, and I am committed to ensuring its success and helping it achieve its mission of providing high-quality medical software to medical practices and clinics globally.
Supervised learning might be challenging in cases where there are extremely few known instances in a given category. This is a common occurrence in the case of Strong gravitational lensing images when samples from one or more classes are scarcer than others. On the other hand, when there are few data labels available for supervision, Self-Supervised Learning (SSL) has been shown to perform better than conventional supervised learning. SSL can also create meaningful representations from very vast unlabelled datasets that would be challenging or impossible to label manually. Additionally, transformer-based architectures recently have emerged as a paradigm to solve a wide range of tasks in computer vision from image classification to object detection. They have a number of advantages over traditional methods, including dynamic weight adjustment based on input features, global context, and improved generalization. Thus, the project aims to train transformer architecture in Self-Supervised Learning fashion to learn generic features. These features could then be used in different downstream tasks such as image classification or regression.
One of the weak points of most unikernel projects has always been application support, often requiring that applications be ported to the target unikernel OS. In this area, Unikraft has made significant progress by prioritizing POSIX compatibility. Through its binary compatibility mode, Unikraft allows unmodified ELFs to be executed, with resulting syscalls wrapped and redirected to the Unikraft core via the app-elfloader. Currently, Unikraft supports loading both statically and dynamically linked ELFs in binary compatibility mode. However, Unikraft has not been able to fully support all behaviors of glibc and user applications, which causes certain programs to fail in initializing or crash. Additionally, running applications in binary compatibility mode incurs performance loss compared to ported programs, due to the TLS switching and system interrupts caused by binary syscalls. To address the issues mentioned above, this project focuses on expanding Unikraft's binary compatibility mode by: * Using vDSO (virtual dynamic shared object) and vsyscall (virtual system call) to bypass binary syscalls. * Expanding supported syscalls to provide compatibility for a wider range of applications. * Adding AArch64 architecture support for app-elfloader and syscall-shim layer. * Implementing a faster way to port new applications by externally compiling. * Establishing a CI/CD system to ensure that new commits do not break libc compatibility.
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.