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.
OpenFASOC, an automated SOC generator, is enabling chip enthusiasts to develop circuits/macros with a software approach. Circuits must not only be functionally proven but also need to be implemented under the rules defined by the technology to make it silicon-proven. To meet its functional and technology requirements, the generator needs to be constantly improved and with every update, the tool must be tested for its core functionalities. This proposal includes the detailed CI flow which can check the functionality and performance of the designs generated. It also includes the method to test small changes in the circuits and developing pythonic APIs for each generator to import them into larger software programs built on these generators. These APIs can also enable OpenFASOC to move from a CLI based tool to a GUI based tool.
Currently, the mobile app is in the development phase with zero releases, hence the main motive for this year would be to make the app production-ready. The main motive of this project is to implement the member management. The aim is to implement the following: - Implementing a way to allow only certain organization members to approve new members. - Implementation of push notification for the organizations to be able to send notifications to all, or groups of members in case of any natural disasters, fundraisers, functions or other significant events. - Adding unit tests and widget tests for all the necessary views. - Adding an app guide for onboarding users - Adding documentation for the users about new features. - Signing the APK and Playstore release.
Tardis is an open-source project designed for rapid spectral modelling of supernovae. Astrophysicists widely use it to model supernovas. When new astrophysicists start using the Tardis, they will use the help of past projects to understand the simulated spectra. So it is crucial to continuously update the simulated spectra of past projects as the code of Tardis gets modified. Currently, three past projects are stored in the tardis-setups repository. Each time there is a change in the codebase of Tardis, it is hard to run the projects and update the spectra manually. So a CI/CD framework should be created to automate comparing and publishing the results. To achieve this, we intend to use GitHub Actions. The existing projects have different ways to run the simulations. So the existing projects will be modified to be integrated into the pipeline. Guidelines will also be put in place to allow future contributors to add more projects.
The aim of this project is to provide two enhancements to the exploration editor page (for creating lessons) for lesson creators: (a) Development of a new "Git-Blame" like feature allowing users to see and navigate through the history of changes to a specific state card of an exploration. (b) Modification in the existing "version-comparison feature" allowing users to see the changes in the metadata properties of an exploration such as title, category etc., while comparing two versions of an exploration. The proposal contains details of calculation of the data related to the history of changes with the help of a beam job. It also contains details about unit tests and end-to-end tests used for testing the correctness of the changes.
Checkstyle focuses on code quality but it isn't the only tool to do so. There are a lot of static analysis tools for Java language, Checkstlye is one of them. Checsktyle currently uses other tools like PMD, Sonar, Eclipse, IntelliJ IDEA Inspection, pitest, etc. to inspect its source code. Though integrating these tools has improved the code quality by a lot but there is still room for improvisation. The main focus of this project will be to take code quality to the next level by integrating tools like Error-Prone, Checker Framework, and ArchUnit and extending the usage of Pitest to all active mutators.
Description: Implement the ability to forward messages to another channel, thread, or discussion. This is a high-demand capability that is currently missing in Rocket.Chat. It can significantly improve the user's experience and her/his productivity. The scope of this project will be limited to web applications and not to mobile apps. Deliverables: 1. Being able to forward messages and files to multiple users and rooms 2. Being able to add additional messages on top of forwarded content. 3. Being able to add text formatting in the optional message field. 4. Being able to provide a preview of the message before sharing it. 5. Ability to show “posted from this channel” below the forwarded message
Zulip's frontend makes heavy use of Bootstrap 2. In this project, my goal will be to remove it. I will also work on improving the shared components used in the codebase. Along with this, I will work on improving the integrations and fixing other subtle bugs present in the web app
Currently, Talawa has three major software components which are talawa, talawa-api and talawa-admin. Among these, talawa-admin is a web-based portal and talawa is a mobile application whereas talawa-api provides access to user data and features. We also have talawa-docs, which is a website that contains most of the documentation and can be found at “https://palisadoesfoundation.github.io/talawa-docs/”. Currently, the documentation website is being powered by numerous Markdown files which are being rendered into a static website with the help of Docusaurus. The challenge is to find and implement a way to generate documentation (in the form of static HTML files) from comments within the files, which can then be hosted on the site used for documentation. This will enable the documentation to grow organically with the codebase. We target to automate the creation of our documentation using the content of our code repositories on our existing documentation website. This will give Palisadoes the flexibility to maintain its Markdown documentation and its website more efficiently.
LiDAR and Camera could be considered the most important senses of autonomous vehicles. The camera can help to create a 2D map of the surroundings and LiDAR can help to make sense of depth and how far other objects are from the vehicle. This project implemented driver modules to establish reliable communication between a microcontroller and sensors/actuators. In the project, we implemented drivers for a Garmin LiDAR, an angular encoder, and a servo motor. We also implemented Constant Panning mode and Range at Angle mode.
1. At the bottom of the picker, there will be two buttons "Upload" to start the Upload Wizard with the selected pictures (replacing the already implemented ✔️ button currently available at the top-right) and "Mark as not for upload" to mark these pictures with a 🚫 overlay icon (and grey them out). For instance, family pictures are not meant to be uploaded to Commons. This state will be remembered even after restarting the app. Tapping "Not for upload" when all selected pictures are already marked as "Not for upload" has the opposite effect, a bit like pressing "Italic" twice in a text editor makes the selected text in Italic then normal. 2. Switch to hide/unhide pictures that are either marked as "Not for upload" or have been uploaded already. Hiding them allows the contributor to more easily spot pictures they might want to upload. 3. Currently, when selecting 3 pictures, they are numbered "1", "2", "3". Instead, please make all numbers always show the number of selected pictures, for instance, if 3 pictures are selected, they should all have the number "3", and be uploaded in the same order as their thumbnails are shown. 4. Add a fast scrollbar (ideally a Bubble scroll showing the date at which the pictures shown were taken). 5. UI when in full-screen mode -fullscreen starts when you long-press any picture in the custom picker 5.1. Show a small overlay indicating whether the picture is selected or not, showing the number of selected pictures. 5.2. Gestures: Left/right swipe to go from one picture to another. Swipe up to select the picture and show the next picture, skipping pictures that have either already been uploaded or ignored. Swipe down to immediately mark that picture as "Not for upload" and show the next picture.
This project sets up an authentication micro-service for the open source organization OpenFoodFacts. The project entails migrating all users to the authentication micro-service giving OpenFoodFacts authentication new features and a new UI.
This project will implement Interpolated Corrected Curvature Measures for triangular meshes based on “Lachaud, J.-O., Romon, P., Thibert, B. and Coeurjolly, D. (2020), Interpolated corrected curvature measures for polygonal surfaces''. Using the Boost Graph Library and CGAL’s extensions to it, the implementation will be data-structure-independent. The project will hopefully investigate and implement possible extensions to the algorithms to cover different use cases.
Compared to Casbin for Golang, PyCasbin has many shortcomings, especially the lack of RBAC interface and its bad performance compared to Go. Therefore, parts such as performance need to be optimized. This proposal is mainly dedicated to implementing the encapsulation of casbin-cpp for pycasbin. In addition, this proposal also introduces the implementation of redis-adapter and etcd-adapter, the performance optimization of Enforce, the integration of Django and casbin, and the resolution of daily issues of casbin-cpp such as bugs and features to build a better access control system.
My entire project aims to bridge Qiling with other static analysis software, thus providing users with high-level concepts like stack frame, CFG and even symbolic execution. The robustness and usability of the project should also be improved to make everything tidy, which may involve some refactoring.
While developing apps using MIT App Inventor, students often need help. For this MIT App Inventor has a community where students can reach out for help. While the community is very helpful and makes development easier, it would be even more convenient and time-saving to have a user interface on the app inventor website itself from which users can directly ask questions in the community and project files can be automatically uploaded on community website along with that .
The Primarily aim of this project would be to improve the overall UI/UX experience of Zulip users. Since last 2 months, I’m consistently participating in UI-redesign discussions on #design channel and I truly love the first draft proposal of UI-redesign of complete web application by Vlad Korobov, and would love to contribute in making it live! I would also like to work on some feature projects revolving around node tests, stream settings.
Agora vote iOS allows users to create elections, invite voters, view results etc. This application uses Agora Web API as a backend application. It allows for elections to be held by using multiple algorithms such as Oklahoma, and RangeVoting. The iOS project has started in 2020 and some initial UI was implemented back then, but there was no functional API support or any business logic integration up until now. This year's project is focused on exploring and implementing The Composable Architecture (TCA) as well as on adding the remaining features and continuing the implementation of SwiftUI while following the User Interface Guidelines and iOS best practices. My goal is to build an authentication and authorisation layers, as well as to connect together Create Election flows and remote API, as well as to update and clean up the UI.
Jenkinsfile Runner Action creates the containerized pipeline execution in GitHub Actions by modifying the current structure of Jenkinsfile Runner and several predefined docker images. The default version without configuration and JCasC style version with user's configuration are expected in the final pull requests.
This project aims to introduce a metric system to calculate the health score of each plugin within the Jenkins ecosystem and reflect the final scores on the Plugin Site for the plugin maintainers and users. The health score of each plugin would be shown on the UI with a detailed report of strengths and areas of improvement, making it easier for maintainers to maintain their plugins, and for users to decide if they should install/use a plugin.
Computational models, based on detailed neuroanatomical and electrophysiological data, are heavily used as an aid for understanding the brain. An increasing number of studies have been published over the past, but remain available in simulator-specific formats. NeuroML is a standardized data format to describe the biophysics, anatomy, and network architecture of neuronal systems at multiple scales in an XML-based language. Hence, to improve accessibility, exchange, and transparency in the research of neuronal models, this project aimed to make neuronal mouse models in the Allen cell types database available in a simulator-independent format, using NeuroML.
Artifacts are parts of a measured signal generated from sources other than those of interest. For electroencephalography (EEG) data, artifacts from a variety of physiological and environmental sources must be excluded or repaired to ensure that appropriate interpretations are applied during clinical evaluation and downstream analyses. We will develop a suite of web-based tools for facilitating artifact annotations for the Global EEG Norms project of the Global Brain Consortium (GBC). This project will enable clinical neurophysiologists to upload EEG data in standardized formats; annotate data with artifacts, such as electrical noise and movement artifacts, using a novel ontology that is interoperable with the Hierarchical Event Descriptors specification; and export this data to the Brain Imaging Data Structure standard. While the resulting libraries of this project will be integrated into a Progressive Web Application for clinical neurophysiologists, they will also be released standalone as tools to further facilitate the development of neuroscience tools on the Open Web. This could reduce the barriers to entry for neurophysiology research by enabling standalone data management and analysis applications to be released on modern browsers. In the long run, this may enable the rapid diagnosis of neurological disorders in lower to middle-income countries with unreliable internet connections.
The project aims at implementing Boost Graph Library Algorithm Hawick_circuits in pgRouting.Hawick circuit is an algorithm used for searching circuits in a graph. It can be used to enumerate all the circuits in a directed multigraph. Specifically, it can also enumerate self-loops and redundant circuits caused by parallel edges which is not detected by other available algorithm for circuits.It enumerates the circuits in linear order of vertex.This algorithm is an extension of Johnson's algorithm for circuits and presents a memory efficient and high-performance implementation.
This project is to enable the selection of multiple blocks at the same time and allow moving and doing actions on multiple blocks on Blockly. This behaviour is pretty much the same as when you try to manage your files on your Operating System, and you can drag a rectangle to select multiple files, then moving them around, copying, deleting. The design is that the Blocks multi-select feature will be only functional when you hold the Shift key, so that users can still drag the workspace when not. Users can simply click on the blocks to select or unselect them, or drag a rectangle to select a set of them at the same time. A button would also be added to enable multi-selection feature in case users are unable to access the keyboard. It sounds like a little bit easy, but actually, I would say that it's not. Multiple selections can become a crazy-complex feature when you start thinking about the details. When dragging two blocks, you have to think about how the connections will work. When you right-click on multiple selections, you also have to make sure that those options apply to all blocks. And the touch screen problem would also need to be addressed. The feature request (https://github.com/google/blockly-samples/issues/267) has remained open on the GitHub Issues for 6 years, but it's still in the discussion phase and far from the beginning of Implementation there. So I hope we can implement that during GSoC 2022 if possible.
Create new user interface for the web application of OWASP OWTF, use SASS instead of CSS, remove the additional dependencies to make code more reusable, add more unit tests to the frontend, write the proper documentation and fix the state issues present in the application.