Explore Projects

This project aims to support the detection and reporting of SPDX License Expressions. Currently, FOSSology uses regular expressions, full-text match, and fuzzy match to scan licenses, stores all types of license expressions as a list of licenses, and wrongly classifies them as conjunctive licenses or disjunctive licenses. It also stores license exceptions as licenses and does not differentiate exceptions from licenses. In the project, I will be working on scanning license expressions using regular expressions with Ojo, storing them in the database, creating UI components to see license expressions in the file clearing page, and finally updating reports to export the expressions in the correct format.

<p>The common requirement of Collect users is to share forms between devices. This is important for forms that need to be filled out in multiple steps by different enumerators. And sometimes form need some review before actually getting submitted to the server. A supervisor will be able to review the forms and upload the good ones and send back the bad ones for improvement. So this project will allow enumerators to share partially/completely filled forms with each other and also help supervisor in reviewing the forms. The main focus of this project is to see the pros/cons of different communication strategies possible in Android devices and select the one which is both robust and reliable.</p>

Mutter is the Wayland display server and compositor library powering GNOME Shell. Currently, an unexpected GPU reset causes the compositor to freeze as the EGL context becomes defunct and all allocated GPU memory is lost. This project aims to implement a robust recovery mechanism by leveraging the `GL_EXT_robustness` extension to detect resets, re-create the EGL context, and re-upload all GPU resources, including client textures, glyph caches, background image, etc. This work will ensure system resilience and prevent session-ending freezes, allowing the compositor to resume rendering seamlessly after hardware-level failures.

This project focuses on improving the accuracy and clarity of the detection_log by explicitly identifying when extra-words are detected during license rule matching. These extra-words often represent variable components within license texts, which previously caused the match score to drop below 100 even when the overall match was correct. To resolve this issue, the implementation now checks whether the extra words appear in the expected position within the license text. If their position is valid, the match score is adjusted to 100, and it is also reflected in detection_log. This enhancement leads to more precise license rule matching and provides users with clearer, more reliable detection results.

Seata Go currently lags behind the Java version in registry support and operational diagnostics. This proposal introduces a shared multi registry foundation for Seata Go, implements Nacos, ZooKeeper, Consul, and Redis support in a phased and reviewable way, addresses NamingServer and path compatibility issues needed by the Go SDK baseline, and extends seata ctl with server and config self checks, transaction and lock diagnostics, and structured output. The project deliverables include the shared registry layer, four registry adapters with tests, a bounded diagnostic command set, and follow up TUI, sample, and documentation polish.

Webpack's extensive API definitions are currently locked inside raw types.d.ts files, creating a significant manual maintenance burden to keep the public documentation synced. My proposal solves this by building an automated, version-aware CI/CD pipeline. I will extract TypeScript ASTs using TypeDoc, format them via typedoc-plugin-markdown with a custom webpack-doc-kit theme, and integrate them into @node-core/doc-kit. The final deliverable is a polished, searchable React-based UI that matches Webpack's visual identity, completely removing the manual documentation overhead from the core team.

<p>The objectives of the project are as:</p> <ol> <li>Completing the build matrix - testing on different compilers, different architectures, different Boost versions. For this, building a number of Docker containers, each with a different set of libraries and compilers, that can be used to build mlpack and run the tests.</li> <li>Running docker with Jenkins for continuous integration and continuous deployment. Using plugins to automate the build and deploy process with the Jenkins server.</li> <li>For testing on windows and os x, docker images will be supplied for the end users to just say a “docker pull” and get things running.</li> </ol>

<p>Clearly Defined is a collection metadata of licences, copyrights and the source codes. Clearly Defined clarifies data on open source components, and mostly focus over the open source licence, source location and attribution parties. This helps in providing more information about what their obligations are and feel more confident in meeting them.</p> <p>The project aim is to connect the Clearly Defined REST API and query through the metadata provided by Clearly Defined. This will help in importing the data and reducing the manual clearing task for users. Moreover, the FOSSology can lead to contribute to clearly defined by providing new license metadata and helping the community.</p>

<p>Abstract Dense (numerical) Linear Algebra plays an important role in scientific computing, and is typically implemented by the BLAS/LAPACK libraries. In Debian linux, these libraries have been well-organized and integrated into the system, forming a tiny ecosystem with the help of a runtime switching mechanism. To date, there are still many aspects from which this tiny ecosystem can be improved. For example, it lacks documentation and lintian checks; Some state-of-the-art implementations are still not incorporated yet; Deprecated components are still present in the packages. These items altogether requires a considerable amount of time, energy and skill. The goal of the project is to enhance the ecosystem from the mentioned aspects.</p>

<h3>Increase archive coverage</h3> <p>As Software Heritage works on archiving and sharing source code, one of the major tasks is to ingest the latest source code available from all the possible sources(forges and package managers). The goal of this project is to increase the archive coverage by making listers and loaders for different forges and package managers. Listers are components that crawl the APIs of software forges (e.g., Bitbucket, Gitorious, Sourceforge, ...) and return a list of the software available in it whereas Loaders take a bundle of software (tarball, Git repository ...) and load it into Software Heritage, by adapting it so that it matches the archive data model.</p>

ISAC & CTG are essential components of the RISC-V Architectural Testing(AT) ecosystem. CTG generates tests for AT using the coverpoints as stimulus to ensure that complete coverage can be achieved with minimal testing. ISAC measures the coverage of the tests and reports on the quality of the test suite. This mentorship involves adding multiple features to both these tools to improve the quality of the architectural test suite. For further information on the tasks to be done during your internship refer here - https://gist.github.com/pawks/e2dec6d67224a9f68bf96fc909398c45 As part of the selection process, all candidates are required to successfully complete the coding challenge described here before August 3rd : https://gist.github.com/pawks/98863e5eca71c8b80b18e060cb4d9558

<p>Software Package Data Exchange (SPDX) is “a set of standards for communicating the components, licenses, and copyrights associated with software”. You can find the latest (as well as the previous) standards at: <a href="https://spdx.org/specifications" target="_blank">https://spdx.org/specifications</a>. The Python SPDX library does not support the latest SPDX-2.1 standard (instead, it can handle SPDX-1.2) which makes it logical to add support for the latest standard. The aim of the project is to update the python SPDX library to SPDX 2.1 specification with a better Error Management system and an improved internal model.</p>

<p>Multi model databases are becoming more popular due its native support for polyglot persistence. Polyglot Persistence is a term to mean that when storing data, it is best to use multiple physical data models, chosen based upon the way data is being used by individual applications or components of a single application. Multi model databases acknowledge the need for multiple data models, combining them to reduce operational complexity, operational costs, extensibility and maintain data consistency. Apache Gora currently supports OrientDB datastore as a multi model database, the project proposes further extending multi model database support with ArangoDB</p>

The Project aims to finish up the development of the Vue simulator for production deployment and replace the current simulator in CircuitVerse. The project is divided into 8 Parts : - Fixing existing bugs and Completing the implementation of simulator components. - Designing and implementing a better UI/UX for the mobile version. - TypeScript Transition, jQuery Elimination, Transferring all DOM manipulations. - Developing a comprehensive test suite for the Vue simulator. - Moving the CSS styles and Finishing refactoring the codebase. - Integrating stability improvements and addressing any performance issues. - Merging updates and bug fixes from the main CircuitVerse repository. - Additional improvements to enhance the simulator's functionality, user experience, and stability.

<p>Data structures that complex networks (graphs) can model are present almost everywhere. Therefore, it is important to have a software that can visualize and provide insights into such structures. Unfortunately, the vast majority of network visualization and manipulation software currently available has several limitations. For example, Gephi (Java) does not scale well when the number of nodes increases and cannot deal with 3d layout algorithms. Because of those limitations in the currently available network visualization software, we propose to develop a client/server network visualization for FURY. Our proposed system is inspired by the following work: “Harnessing WebGL and WebSockets for a Web-Based Collaborative Graph Exploration Tool”.</p>

The 12 Factor Application project is a methodology for building and deploying scalable, maintainable, and suitable software applications. The project is based on 12 key principles that outline best practices for developing and deploying software applications. Project Goals are : 1. Make CircuitVerse a 12 factor application. 2. Progressively convert CircuitVerse previews and profile avatars to object storage. 3. Improve observability using OpenTelemetry. 4. Drop visitor tracking by storing user details and adopt HyperLogLog for project view count. 5. Zero downtime deployment pipeline with GitHub Actions and Kamal. 6. Monitoring server with Monit.

<p>I propose three independent projects that improve the usability of mitmproxy for new and existing users. The first project aims to improve the onboarding of new users. I want to create an application that interactively guides new users through a set of tutorials. The second project simplifies capturing machine-wide traffic by automatically setting up OS firewall rules to forward all traffic of the user’s machine to the local mitmproxy instance. The third project adds a “map remote/local editor” such that users can easily rewrite requests to new locations, eg. to serve parts of a page from another server or local files.</p>

kruise-game is being used by many game companies. It is imperative to build the stability of kruise-game components. With the rapid iteration of project functions, the current test coverage has not met expectations, so we need to add more UT and E2E use cases to ensure that there will be no problems with our basic functions. In addition, in a large-scale cluster environment, kruise-game also needs more indicators to reveal the performance of the current controller. Expected Outcome: 1. Expand End-to-End (E2E) Test Coverage 2. Improve Unit Test (UT) Coverage 3. Enhance Observability via Controller Metrics 4. Improve Logging Contextualization

<p>The SwagLyrics suite of repositories is an ecosystem of backend applications, a couple of python libraries, a chrome web extension (soon!) and even a discord bot. Over the course of this summer, we aim to work individually on these components as well as on how they interact together. The ultimate idea is to create a noops infrastructure, that is, a system that maintains itself and does not require any essential input from an actual human being, thus ensuring that such a proposal can never be created again (lol). Overall, the goal is to lend a degree of finality to the project and working on essential non-essential areas that cannot be simply ignored, as they have been until now. In essence, this proposal can be considered similar to the CCExtractor Sample Platform proposal last year.</p>

Jaeger UI provides several views to visualize service dependencies, also known as service topology maps. However, these views are using different drawing libraries, resulting in very different look & feel and inconsistent experience. One of the views is using a `plexus` library that was purposely built as part of Jaeger UI that provides rich capabilities for displaying graphs, which may be a good candidate for the other views. - Expected Outcomes: - Remove the dependency on react-vis library (https://github.com/jaegertracing/jaeger-ui/issues/1597). - Use a single library for graph visualizations. - Provide consistent look and feel of different graph views.

<p>In the current scenario, A user logs in the desired intermine and saves the results and the required data. The problem arises when the same user wants to access a different intermine, He/She will have to register again on this new mine and log in again. So , Currently Intermine community does not have a single common sign-in mechanism and thus it is authenticating users with the help of tokens (temporary and permanent one) or using google and Elixir services to log in. This project will modify the existing token mechanism by making the intermine as an OAuth2 provider with a single common Authorization server for all 30 mines so that user could access all the mines with the single set of credentials i.e just one time registration.</p>

Goal: ○ To add a Terraform module for SkyWalking deployment to facilitate users in conveniently spinning up a cluster for demonstration or testing. ○ To allow users to customize the Terraform provider according to their needs, making it feasible for them to use it in their production environment. ○ To mainly focus on the support for AWS in the Terraform module for SkyWalking deployment. ○ To provide a hassle-free solution to users where they only need to provide their access key/secret key, and the Terraform provider does the rest of the work, which includes creating VMs, creating database/OpenSearch or RDS, downloading SkyWalking tars, configuring the SkyWalking, and starting the SkyWalking components (OAP/UI), creating public IPs/domain name, etc.

This project aims to bring dark mode support to Django’s issue tracker and improve its visual consistency with the main Django website. Currently, the main site supports dark mode while the Trac-based issue tracker does not, creating an inconsistent user experience. The project will implement a maintainable dark mode styling system, add a theme toggle supporting light, dark, and system preferences, and improve readability and accessibility across key pages such as tickets, reports, and wiki pages. The final deliverables include the dark mode implementation, UI refinements for important components, and documentation to support future maintenance and improvements.