Explore Projects

<p>Project:</p> <p>Stackle is a web communication portal aimed at providing Open Source organizations a platform to have discussions on their GitHub projects and their issues. It provides GitHub integration which allows the administrator of an organization to create a forum thread for the particular organization. Users signing in are able to view forums of the organizations they contribute to and engage in the forum discussions.</p> <p>Problem:</p> <p>Structure the Routes of Stackle and make REST-APIs more robust and easy to consume.</p> <p>Technology Stack:</p> <p>Javascript/Nodejs/ExpressJS</p>

<p>With the growing popularity of BitCoin in the last couple of years, other blockchains have been in development for solving various problems that need distributed consensus. Ethereum blockchain is one example, that gives users to develop "smart contracts" that runs in the blockchain. This gives the ability to develop decentralized applications (or dApps).</p> <p>This framework has given many developers to write a decentralized application without much effort, without needing distributed systems or cryptography knowledge. Unfortunately, because the technology being used is bleeding edge it is inevitable that attacks or hacks will target these apps for monetary reasons. Because of the immutability property of Ethereum after publishing even if developers identify a critical bug in the contract it is not possible to correct it.</p> <p>Thus, in order to fill the gap of not having a proper 'smart contract' compatible monitoring service, we propose to build a web application that can monitor other smart contracts in Ethereum and give the capability to safeguard its critical functions (Ether send and receive) and interact and visualize with smart contract functions in a much simpler way.</p>

<p>This is a project that is intended to support Public Health Inspector (PHI) to find and investigate “Dengue(mosquito) breeding sites in a given location.” Breeding of mosquitoes is becoming a severe issue in Sri Lanka and it is difficult to investigate the breeding places in urban areas mainly due to the height of the buildings. Currently PHI’s are investigating such locations by themselves where possible.</p>

<p>ImageLab is an image analyzing platform. Users can load large set of images to ImageLab and then they can perform analyzes by labeling and clustering them by using different object detection modules. ImageLab also have a user management component as well as an image analyzing component.</p>

<p>This project aims at improving Purr Data's documentation browser and leveraging it to an autocomplete feature for objects and messages:</p> <ul> <li>Object - the suggestion box will propose previously created objects and as the user writes, a fuzzy search will rank suggestions based on title, keywords, description and related objects;</li> <li>Message - the suggestion box will propose previously created messages</li> </ul> <p>The idea is to improve the user experience and increase the fluency of the day to day patching.</p>

<p>Clang is a C/C++/Obj-C compiler spawned from the LLVM project, famous for its modular design, rich diagnostic messages, non-intrusive license, etc. Some Unix flavors, including FreeBSD and OS X, have already adopted a purely clang/LLVM based toolchain. It would be interesting and beneficial to have clang as a first-class compiler, in place of GCC, on Gentoo as well. This task involves bootstrapping a freestanding clang along with its supporting libraries, and deploy them on Gentoo.</p>

The goal of this project is to provide comprehensive documentation of the LALRPOP Parser, Intermediate Code Representation (ICR), and Code Optimization techniques utilized in Solang. Solang is a compiler for the Solidity Programming language, targeting the Ethereum Virtual Machine (EVM) and WebAssembly (Wasm) platforms. The documentation will encompass a detailed exploration of the parser's functionality, the structure of the intermediate representation, and various code optimization strategies employed within Solang. Additionally, we aim to propose improvements and enhancements to these components based on the latest research and advancements in compiler construction. Specifically, we will focus on suggesting advancements in error handling techniques, enhancing the ICR, and introducing more effective code optimization techniques.

Problem: Brian2CUDA offers significant GPU acceleration for neural simulations, but its current "beta" state contains friction points that hinder widespread adoption. Key issues include unreliable Windows support due to POSIX-specific build assumptions, slow incremental compilation that often exceeds simulation time, silent GPU failures that are difficult to debug, and startup crashes related to preference file validation. Solution: This project aims to make Brian2CUDA "production-ready" by modernizing its backend infrastructure without adding heavy external dependencies. The plan involves: Stabilizing the Windows workflow by implementing a robust nmake/MSVC build path and platform-independent path handling. Optimizing compilation speed through deterministic source grouping and granular dependency tracking in generated Makefiles. Implementing a synchronized C++/Python logging system with structured CUDA error-checking to eliminate silent failures. Resolving preference validation conflicts to ensure reliable configuration loading. Deliverables: - A validated cross-platform build system supporting Windows (nmake) and Linux/macOS (Makefile). Optimized code-generation templates for faster incremental builds. A unified diagnostic logging framework. A suite of regression tests and "Getting Started" documentation for Windows users.

<p>The Kuadrant Console Plugin provides a web interface for managing API gateway policies in OpenShift, but currently relies heavily on YAML editing for most policy types. While DNSPolicy and TLSPolicy already have user-friendly form-based interfaces with dual Form/YAML views, validation, and guided workflows, the remaining core policies (RateLimitPolicy, TokenRateLimitPolicy, AuthPolicy, Plan, and OIDC) still require users to manually write YAML. This creates a steep learning curve and error-prone configuration experience. This project aims to bring RateLimitPolicy, TokenRateLimitPolicy, AuthPolicy, Plan, and OIDC policies to feature parity with the existing DNS and TLS form implementations. Form designs will be provided by the Kuadrant team. The mentee will implement these designs as PatternFly-based form interfaces following the established patterns from the DNS and TLS policy forms. These forms will allow users to configure policies through validated form fields while maintaining the flexibility to switch to YAML view for advanced use cases. The forms must support both creation and editing of policies, include proper field validation, handle complex nested structures (such as rate limit configurations and authentication rules), and synchronize seamlessly between form and YAML representations using the same patterns already proven in the DNS and TLS implementations.</p><p><br></p><p>Expected Outcome:</p><p>&nbsp;- Form-based creation and editing interfaces for RateLimitPolicy, TokenRateLimitPolicy, AuthPolicy, Plan, and OIDC policies implemented using the same patterns, components, and structure as the existing DNSPolicy and TLSPolicy forms</p><p>&nbsp;- Dual view toggle (Form View / YAML View) with bidirectional synchronization using js-yaml for all five policy types</p><p>&nbsp;- Field validation following the established validation pattern covering required fields, numeric constraints, conditional dependencies, and Kubernetes resource naming conventions</p><p>&nbsp;- PatternFly component integration matching existing forms: expandable sections for complex nested configurations, validated text inputs, dropdowns for enum fields, and reuse of gateway selection components</p><p>&nbsp;- Policy-specific form fields for: rate limit units and counters (RateLimitPolicy), token-based rate limiting (TokenRateLimitPolicy), authentication strategies and credentials (AuthPolicy), plan tiers and quotas (Plan), and OIDC provider configurations (OIDC)</p><p>&nbsp;- Error handling using the existing error modal and inline validation message patterns</p><p>&nbsp;- Internationalization support for all form labels and validation messages using i18next following the existing localization structure</p><p>&nbsp;- Both create (`/~new`) and edit (`/:name/edit`) routes for each policy type matching the DNS/TLS routing pattern</p><p>&nbsp;- Unit and component tests covering form validation, YAML synchronization, and error states following the established testing patterns</p><p><br></p>

<p>This project aims to add features to improve the usability of NetLogo IDE for desktop. The features that will be implemented in this project are -</p> <ol> <li>Auto-complete - Will also suggest similarly-named primitives when a user attempts to use a primitive that doesn't exist</li> <li>Jump to definition</li> <li>Find usage in the code</li> <li>Support Undo for widgets</li> <li>Show all compilation errors in the editor's "gutter"</li> </ol>

<p>As Eclipse 4diac allows programming of many different devices, such as Plcs, RaspberryPies, Lego Mindstorms, a runtime environment has to be compiled for each device. If you then want to extend the functionality with custom function blocks, a new runtime environment has to be compiled every time, a new function is created. However, compiling is complicated and takes time, therefore a Lua engine is integrated into the runtime environment, which then is able to execute Lua code, without having to compile it first.</p>

Wikidata is one of the largest hosts of open data. Missing or new information needs to be added by community members. Otherwise, the knowledge base will dry out and be obsolete after a while. My project's goal is to create an ecosystem that will consist of Web service interfaces to push data from different sources, s.t. researchers. The industry can easily integrate it into their systems and efficiently help to extend the Wikidata knowledge base. The impact of this will be data donations will be possible directly via different sources. The process will become easier and less time-consuming for contributors. Hence, the quality and quantity of the open data offered by Wikidata will increase. I will later try to implement a recommendation engine that suggests agreeable facts to Wikidata editors that are likely to be in their area of expertise. Also, gamification features to show appreciation to Wikidata editors, e.g., a badge Web service allowing users to integrate their score/rank into their profiles on social networks. That will be encouraging for the editors. Goals (1) Implement Webservice interfaces for data donations, i.e., sets of approvable facts (which should also contain links to evidence, etc.) (2) Implement a recommendation engine that suggests agreeable facts to Wikidata editors that are likely to be in their area of expertise. (3) Extend the gamification features to show appreciation to Wikidata editors. Example: a badge Web service allowing users to integrate their score/rank into their profiles on social networks (e.g., on Wikidata’s user page, GitHub profile, Linkedin profile) to show their dedication and activate other users. Impact (1) Data donations are possible and at the same time, an efficient approval process is supported. (2) More fact ingestions with the help of the Wikimedia community. (3) Faster integration of new facts into Wikidata.

The RISC-V Mentorship Program enables one or more 12-week internship-style projects per session, funded by RISC-V, to match mentors/project leaders together with mentees/interns . Mentees are guided through a series of milestones by one or more project mentors, with whom the mentees meet on a weekly basis. Spidermonkey is the JavaScript Engine inside Firefox. It has JIT compilers for generating native binary codes on the fly. This project aims to porting Spidermonkey to RV64GC platform. Basic knowledge of compilers and language virtual machines are needed. Deliverables: - Cross-compile Spidermonkey to RV64GC Linux (Fedora) platform. - Patches that let Spidermonkey running on RV64GC Linux under interpreter mode. - Porting the baseline compilers so that Spidermonkey can enable at least one JIT compiler on RV64GC platform - Submit all patches to upstream for code review (merging into upstream is encouraged but not required) Acceptance criteria: - Pass the regression tests in the Spidermonkey. - Get performance data by running SunSpider, Octane and Kraken benchmarks on the RISC-V machine (RV64GC) or software simulator (QEMU).

The Debian LSP Language Server currently provides only basic features — field completion, parse-error diagnostics, and simple quick fixes — leaving Debian maintainers without the rich IDE experience available in other ecosystems. This project significantly expands its capabilities across five areas identified from direct codebase exploration: clickable links and URL navigation in packaging files, richer hover documentation sourced from Debian Policy, improved completion quality with context-aware and deduplicated suggestions, consistent editor integration (with a focus on Helix), and formatting and structural editing support including folding ranges and auto-formatting. Each area will be delivered as an independent, tested pull request. The work integrates with debian-analyzer and the deb822-lossless crate to support multiple Debian control-file formats (debian/control, debian/copyright, debian/changelog, debian/watch ...) and lays the groundwork for real-time validation and go-to-definition across multi-file packaging trees.

*OPEN TO US BASED STUDENTS ONLY* - Accepting applications until May 23, 2025 This mentorship program focuses on optimizing netlink usage during large-scale LAG deployments in SONiC. Internship Objectives: The objective of this internship is to implement the proposed optimizations. The key ideas include: - Creating a standalone process to receive all netlink messages from the kernel, minimizing excessive message copying within the kernel. - Improving message handling reliability by potentially setting a higher process priority or binding the process to a dedicated CPU core for reducing the risk of losing netlink messages. - Dispatching netlink messages from the standalone process to all teamd instances and the teamsyncd process. Expected Outcomes and Deliverables: - Complete the development and validate the performance improvements. - Submit a pull request and upstream the code changes to the SONiC project. Recommended Qualifications: Education: - Current undergraduate student. Skills & Interests: - Eager to contribute to the SONiC open-source community. - Willingness to dive into netlink, LACP, and other foundational networking protocols. - Solid proficiency in C/C++. - Academic background in Computer Science, Computer Engineering, or a related field.

I will be developing DashBot - the AI assistant for API Dash which supercharges developer productivity by helping developers automate tedious tasks, follow best practices, interact & obtain contextual suggestions, all via natural-language input. DashBot will be designed in a modular and extensible manner and provide the following list of features: 1. Explain responses & identify any discrepancy 2. Debug requests based on Status codes & Error messages 3. Generate API documentation 4. Understand API and generate tests 5. Generate plots & visualizations for API responses along with ability to customize 6. Generate API integration frontend code for frontend frameworks like React, Flutter, etc. For each of the tasks benchmark evaluations will also be done so that it is easier for end users to choose the right backend LLM. Add support for various API Authentication Methods such as, Basic authentication, API Auth, API key, Bearer token, JWT Bearer, Digest Auth, OAuth 1.0, OAuth 2.0.

Build a Headlamp plugin to surface Kubeflow resources (Pipelines, Katib, PipelineRuns, Notebooks, TFJob/PyTorchJob/TrainJob, Spark) so operators and ML engineers can discover, monitor, and manage ML workloads alongside standard K8s resources. Link to Kubeflow UIs when deeper functionality is needed. - Expected Outcome: - New Kubeflow sidebar with cross-namespace lists for Pipelines (Experiments, Runs), Katib experiments, Notebook servers, Training and Spark jobs. - Detail pages per resource showing metadata, status, metrics, logs and common actions (start Run, open Jupyter, view best hyperparams). - Links/embed to Kubeflow Central Dashboard or Pipelines UI for advanced tasks. - Headlamp Map integration: show relations to Deployments/Pods, Argo workflows, Spark driver/executors. - Metrics via Prometheus or /metrics: basic charts for experiment objectives and pod resource use. - Polished UX: icons, pagination, filtering, error handling. - Outreach: README/User Guide and a demo blog post with screenshots.

<p>I plan to address the idea "Develop a test framework for checking FreeType's rendering output". Frreetype needs to be able to compare images for correctness and continuity. I’ve implemented a similar system in the game engine ENIGMA (<a href="https://github.com/enigma-dev/enigma-dev" target="_blank">https://github.com/enigma-dev/enigma-dev</a>) where we use continuous integration services such as travis-ci, appveyor and azure pipelines. We use these services, in tandem with a test running program and some scripts which I co-authored, to check for compile errors, to check for function correctness using google tests and to do A/B testing for merge requests on master. The testing suite I helped write runs all the aforementioned checks on master and then reports back to GitHub by posting a pull request comment with diff images for manual review if there are any discrepancies. I plan to implement a very similar system for freetype using my past experiences. It is also worth noting that I wrote the freetype code used in ENIGMA, so I already have some familiarity with freetype’s codebase, as well.</p>

<p>The main goal of this project is to create a component that has a clear API that can provide autocomplete feature for the jupyter kernel - mariadb_kernel. And also I hope that component can be easily integrated with not just jupyter, but also VSCode and Atom … etc popular editor. The main feature has two:</p> <ol> <li>can get the latest MariaDB keywords and functions for autocompletion. (implement new table in MariaDB's information schema, and can use SQL command to get the information)</li> <li>provide an introspection feature that can inspect the word's info and some real data.</li> </ol> <p>And this project autocompletion feature is based on mycli's autocompletion engine. Then do some enhancement on that. Such as:</p> <ol> <li>Database suggestion before 「.」. Ex: 「insert into db_name_to_be_completed.table_name VALUES (...) 」</li> <li>add global and session variable suggestions</li> <li>can suggest system default database, table, column. Ex: add column suggest for system table like mysql.user.</li> <li>Autocompletion about database_name.table_name_to_be_completed could suggest the table, which not in the currently selected database</li> <li>fix some bugs related to the word of the user is the column name and also is the keyword</li> </ol>

<p>The aim of this project is to enhance some portions of the application that implement the Internet Message Access Protocol (IMAP). Specifically :</p> <h5>CONDSTORE</h5> <p>The Conditional Store extension, defined in <a href="https://tools.ietf.org/html/rfc7162" target="_blank">RFC 7162</a>, adds an additional mod-sequence value to every message. This makes it possible to reference changes made to the mailbox made since a particular point in time, which is extremely useful for mobile clients that are not always connected to the internet. Adding support for the CONDSTORE extension will help to greatly reduce the time and data spent on resynchronization.</p> <h5>Search</h5> <p>K-9 Mail has a basic search feature that searches the local database as well as the remote server for messages. The project aims to add features that make it more modern, such as suggestions, nested search, filters and proper full-text search.</p> <h5>Miscellaneous improvements</h5> <p>Support for some additional IMAP operations will also be added :</p> <ul> <li>Using the UID EXPUNGE command when available so that messages deleted by other clients are not expunged by accident.</li> <li>Switching between and modifying namespaces.</li> <li>Moving messages across different IMAP accounts.</li> </ul>

Astropy’s Python API is well-tested, but its underlying compiled layer (C, C++, Cython) lacks isolated testing. Because performance-critical extensions are currently only tested indirectly via high-level Python calls, deep bugs can easily be masked. This testing blind spot also blocks major architectural milestones, including the APE low-level package split, the Meson build system migration, and support for Python 3.15 free-threaded builds. This project will build a dedicated test suite to exercise each compiled extension module directly, entirely bypassing the public Python API. By engineering methods to probe these modules in isolation, including resolving complex runtime circular dependencies like `unit_list_proxy.c`; this work will establish a robust, reliable testing boundary between Python and the compiled code. Deliverables: C-API Audit: A mapped testing surface for active compiled extension modules. Isolated Test Suites: Direct pytest suites for compiled modules in astropy/table, time, timeseries, utils/xml, wcs, and erfa. Dependency Resolution: A C-level refactor (or minimal Python stub) to fix the `unit_list_proxy.c` circular dependency. Documentation: A new TESTING_EXTENSIONS.rst guide in Astropy's docs detailing how to run and extend these direct tests.

Apache Fory's compiler can generate type bindings for seven languages, but neither Swift nor Dart have gRPC service generation support. The generate_services() extension point exists in BaseGenerator and is wired into the CLI, but no language implements it yet. This project adds that support for both: Dart will get a new compiler generator (dart.py) covering messages, enums, and unions alongside gRPC stub generation, while Swift will extend the existing SwiftGenerator with generate_services(). Both will emit typed service interfaces and transport bindings using Fory's serialize/deserialize APIs as the codec, covering all four RPC streaming modes with a zero-copy decode path where possible, without introducing any gRPC dependency into the Fory runtimes. Deliverables include the Dart compiler generator, gRPC stubs with golden tests for both languages, runnable server and client examples, cross-language round-trip tests against a Java server, and compiler documentation for the --grpc flag.

<h3>The project</h3> <p>The goal is to capture the DNS data within a CoreDNS middleware and write it to a "dnstap log file" (prehaps over the network)</p> <h4>Steps</h4> <p>I can see from <a href="https://godoc.org/github.com/coredns/coredns/middleware/whoami" target="_blank"><code>middleware/whoami</code></a> that the message is to be constructed inside a <code>middleware.Handler</code> interface, from the parameters passed in <code>ServeDNS(context.Context, dns.ResponseWriter, *dns.Msg) (int, error)</code>, especially from <code>*dns.Msg</code>.</p> <p>The message is in fact a <code>dnstap.Message</code> nested within a <code>dnstap.Dnstap</code> structure which is <em>(satisfies)</em> a Protocol Buffer <code>proto.Message</code> to be marshalled by <code>proto.Marshal</code>.</p> <p>The serialized data can then be streamed over the network using the <code>dnstap.FrameStreamOutput</code>/<code>dnstap.FrameStreamInput</code> structures.</p> <p>In fact, according to <a href="https://github.com/dnstap/golang-dnstap/blob/master/dnstap/main.go" target="_blank">this</a>: encoding the serialized data with <code>dnstap.FrameStreamOutput</code>, and writing the output to a socket <em>(<code>dnstap.sock</code>)</em>, is enough to use the <a href="http://dnstap.info/Examples/" target="_blank">dnstap command-line tool</a>, for example: <code>dnstap -u dnstap.sock</code>.</p> <p>The log file can then be generated using: <code>dnstap -u dnstap.sock -w log.dnstap</code>.</p>