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.
<p>Test new features that will help develop the application and work on all versions of the software.</p>
<p>Porting and Analysis of top solution algorithms from the TrackML challenge to ACTS framework. The algorithms include the combinatorial Mikado tracker, Cloudkitchen's Neural Network and DAG-based tracker and top-quarks' logistic regression and outlier density estimation algorithm. Added an example of running a PyTorch model in ACTS and testing genetic algorithms for optimization of the Mikado Tracker</p>
<p>This project aims to investigate application of ZSTD within the ROOT framework; benchmark it in comparison to the other algorithms; test it against real LHC data files; and investigate schemes to integrate dictionary-based compression in ROOT files. This will require careful analysis, research and benchmarking through all the stages of the project in order to ensure that the proposed changes are properly verified, documented and result in well-defined benefits for ROOT.</p>
<p>Brian 2 is the new version of Brian software. In 2010 the ModelFitting toolbox was developed for the original version (doi.org/10.3389/neuro.11.002.2010). The main aim of this project is to adapt the ModelFitting to the new version of the software. Access to the module will allow computational neuroscientists to fit the experimental data to the neuron models.</p> <p>The main goal of the module is to find the best mechanistic representation of the recorded spike trains. It has to be re-implemented for the needs of the new version of Brian and requires access to a new optimization library.</p>
<p>Bloom is the release creation tool for the ROS ecosystem. From a standard package manifest format bloom can generate debian or rpm metadata for building binary packages on different Linux distributions. In order to bring support for modular binary packages Windows, this project will refactor the existed generator in Bloom code base, then extended Bloom to generate Vcpkg's metadata for building package on Windows.</p>
<p>ZAP has good support for websockets, and allows them to be intercepted, changed and fuzzed. However, it doesn't currently support scanning, either passive or active, of websocket messages. Thus, it is necessary to start with an infrastructure that is going to support scans, both active and passive. The infrastructure should handle the addition and removal of plugins, providing appropriate utilities, run in a background thread, may store statistics of scanning, etc. On the other hand, a plugin implements a particular scanning method for a group of vulnerabilities. Script plugin is a special kind of plugin which is used to run scripts which are written by users and consequently processed by different scripting engines. Finally, API is useful for inter-connectivity of ZAP with other applications like ZAP HUD. I proposing a infrastructure which is going to support active and passive scanning. In addition, I am proposing feature which in my way of thinking is essential and plugins which are testing the most critical vulnerabilities.</p>
<p>Currently, pdftoraster uses the Poppler libraries which are unstable and change their function definition after updates due to which there are building and installation errors. When the pdftoraster filter was originally written, it used XPDF APIs of Poppler. However, those APIs were unsupported in the recent versions of Poppler and completely removed from Poppler's source code. This affected cups-filters repository since pdftoraster filter was now unable to build or be used by anyone in any operating system. This also affected cups-filters as a whole, because it was unable to build. Hence, it was very important to find a solution to this problem.</p> <p>The most plausible solution to overcome this problem is to instead of directly using the unstable internal APIs we can use stable APIs and rewrite any functionality which isn't even in stable APIs.</p>
<p>WebSim is a web-based robot simulator. It is used as a tool for learning robot programming. WebSim is currently programmable through JavaScript. This project aims to support programming the simulator in Python3 by building a transpiler that targets JavaScript.</p>
<p>Augur is fully functional prototyping web stack for CHAOSS metrics. It provides structured data mined from git repositories using a plugin architecture that incorporates other open source metrics projects like Facade and FOSSology. The main aim of this project is to extend Augur’s functionality by implementing Risk and Growth-Maturity-Decline CHAOSS metrics and use cases with a focus on the open source community manager use case. This project, with a focus on the community manager use case, will allow open source community managers to leverage Risk and Growth-Maturity-Decline metrics to better manage their communities and projects.</p>
<p>At the present stage, Apache OODT provides a web app to monitor the status of each component and ingested files, metadata and workflows. This main dashboard is known as OPS UI which is based on Apache wicket java web framework. Though it provides basic monitoring functionalities like retrieval of product status, metadata,workflow and platform health information etc. still it lacks of few important features like querying over products, product removal and workflow termination etc. Further the existing UI is not so user friendly and prints stack traces when backend errors occurred. Moreover users have to deploy the complete OPS UI, even whether they are embedding components individually in their applications. The intention of this proposed project idea is to address all those loop holes by implementing a new component based React UI with enhanced REST APIs. Moreover the implementation of the idea discussed here, is decided to be released with Apache OODT 2.0.</p>
<p>Currently, <a href="https://www.oppia.org" target="_blank">Oppia</a> is serverside rendered using the <a href="http://jinja.pocoo.org" target="_blank">jinja</a> templating engine. This poses some performance issues since each time a page is being loaded, the server has to generate a new copy of the page to be rendered hence, the pages can not be cached.</p> <p>This project aims at removing the jinja templates used in serving of pages to a more static method, fetch the dynamic content needed for each page via AJAX calls and update the page as needed.</p>
<h6>Notification System</h6> <p>Notification system mainly consists of two parts, In-app Navbar Notifications and Web Push Notifications.</p> <p>-In-app Navbar Notifications: Currently, notifications regarding likes/comments on a post for a user are sent out through emails and there is no notification dropdown on the navbar. I will be implementing a notification feature for each user on the navbar using activity_notifications gem.</p> <p>-Web Push Notifications : I will build a system on publiclab/plots2 for triggering Web Push Notifications for desktop when new comments/likes or posts are created using ActionCable.</p> <h6>UX Improvements</h6> <p>Enhancing the User experience by improving website response. This will be achieved by making backend queries faster, improving user interface, adding features for specially abled users etc.</p>
<p>This proposal aims to add support to include labeled and versioned dataset from the same source and also to build an efficient storage system that can store and maintain data efficiently.</p>
<p>Prombench the benchmarking tool for Prometheus will be extended to support even more tests, newer components, metrics which will help both developers and users in terms of identifying bugs and scalability tests. Another task the proposal aims to solve is the longstanding issue of Prometheus rule formatting.</p>
<p>The aim of the project is to allow users to upload the data in form of files(.csv, data table, google sheets, etc.) to BETYdb. It will done by creating an interface which will provide logical workflow to guide the user through the process of uploading to BETYdb. Crawler are used to increase the knowledge base.</p>
<p><code>Git-issue</code> is a minimalist issue management system based on <code>git</code>. It strives to be <strong>simple to use</strong>, <strong>decentralized</strong>, and in line with existing <strong>Unix software philosophy and design</strong>. Currently, <code>git-issue</code> can import data from GitHub's issue management interface, but <strong>not</strong> export them. This is limiting in the following ways:</p> <ul> <li>It can lead to out-of-sync issue databases between git-issue and <em>GitHub</em>, which means that users have to access both to get the whole picture</li> <li>It prevents usage of git-issue as an <strong>one-stop solution</strong>, since GitHub's interface still needs to be used to process issues opened in GitHub</li> <li>It limits potential use cases, since <code>git-issue</code> has to compete with ubiquitous issue management solutions such as <em>GitHub/Gitlab</em>, instead of synergizing with them</li> </ul> <p>Thus, adding export capabilities would complete the round-trip integration between <code>git-issue</code> and <em>GitHub</em>, and pave the way to wider adoption. The same argument can be made with <em>GitLab</em>, for which neither export nor import capability is currently supported. This proposal aims to add import and import/export functionality for GitHub and GitLab respectively.</p>
<p>Adding HTTP/2 + TLS support to the test library and h2 specific tests.</p>
<p>This project aims to improvise ListView in App Inventor. It was one of the most demanded improvements from users. Idea - Adding custom layouts to ListView. Expected Outcome - 1) Users will be able to select one of the pre-defined ListView layouts and use it in their applications. 2) Users will be able to create any custom row of ListView if it is not present in the pre-defined set of layouts.</p>
<p>The aim of the project is to dive into the internals of Shogun, refactor and clean old code, and apply modern C++ principles. This includes:</p> <ul> <li>Redesigning CFeatures to be immutable.</li> <li>Turning CDistance and CKernel into stateless APIs.</li> <li>Cleaning up and integrating CStringFeatures.</li> <li>Replacing obsolete code with modern C++, and other general cleanups.</li> </ul>
<p>This project focuses on creating an awe-inspiring game using pocket code with the goal of sending the message on “ what kind of unimaginable feats can be achieved using pocket code”. In order to realize this, the game being built will be inspired by the recently popular 2D title - “The binding of Isaac(BoI)”. Whilst certain characters and parts of the storyline will be the same as the BoI, I am also looking forward to implementing original cutscenes, characters, monsters, weapons as well as different endings and a seperate set of features varying from the original game.<br> Successful completion of this project will result in inspiring other audiences to use pocket code to create more apps, further enforcing the vision, “Computational Thinking for All with Free Visual Coding Apps”.</p>
<p>This project aims at integrating a JavaScript engine into VLC to enable extensions development and scripting support inside VLC in JS. This project should replace the already existing Lua engine.</p>
<p><em>Interoperability Model</em>Port the gen-api-models tool to OpenAPI v3</p> <p>I spoke with Mentor/managers on Slack (Leonardo Favario and Roberto Polli) Which I thank for giving me all the answers concerning the project. They told me that they must be maintained: I update Kong(Open Source API Gateway) Rate Limiting and edit it to fit the current system, I add a lot of test code(unit test, etc..) and update documentation. API rest maintenance and adapt them to the latest versions of OpenAPI v3. I'm in contact with mentors and managers, I hear them at least 3/4 times a week. Every time they update me on something about the project, I report it</p> <p><a href="https://docs.google.com/document/d/1Navvdxo6QONWg6zz7LaXka4iDZt6ERTIaisFCgiQbQA/edit?usp=sharing" target="_blank">https://docs.google.com/document/d/1Navvdxo6QONWg6zz7LaXka4iDZt6ERTIaisFCgiQbQA/edit?usp=sharing</a></p>
<p>This project aims to add a more flexible asynchronous file system cache server as an engine module. It will cache any IO operations, and provide more flexibility with respect to the caching behaviour. This is particularly useful on non-desktop platforms such as gaming consoles.</p>
<p>The coreboot project is automatically scanned by Coverity, a free static-analysis tool provided by Synopsis to open source projects. This tool analyzes the source code to check for common mistakes and errors, including static buffer overruns, null pointer dereferences, integer overflow, and other suspicious code. The coreboot project currently has over 380 flagged Coverity issues. The goal of this project is to make coreboot "Coverity clean". All outstanding issues will be classified, invalid reports will be marked as false-positives, and valid ones will be patched. This will address all issues with the current codebase, and ensure a common baseline for triaging new issues in the future.</p>