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.
The RISC-V Certification Steering Committee is developing certification tests to prove that RISC-V processors conform to the ratified specifications. The goal of this mentorship project is to run the tests on as many open-source RISC-V cores as possible, and improve the usability of the tests, debug any issues found in the tests, and report any real bugs that might be found in the cores. This work will involve: * Identifying multiple open-source cores to test * For each core: - Develop a Unified Database (UDB) file specifying the extensions and parameters supported by the core - Implement trick box macros to trigger interrupts, print characters to a console, and terminate a simulation in a core- specific manner - Create a linker script appropriate to the memory map of the core - Compile the tests with the core-specific trick box and linker scripts - Run the relevant tests on the core * Identify and fix any problems in the tests that make them hard to run on a core * Identify and fix any problems with the flow or documentation * Identify and report any bugs found in the cores The work will start with Phase 0 tests of the RVI20 profile with the RV{32/64}IMACDF extensions in machine mode. As time permits, it will continue to the Phase 1 MC100 microcontroller profile with machine mode, traps, Zicsr, and Zicntr, and then to the Phase 2 RVA23 application processor profile with all privilege modes, vector and hypervisor.
Kai is a tool designed to leverage AI for application modernization by analyzing code, identifying issues, and suggesting fixes. We aim to enhance Kai by developing a robust data querying mechanism to facilitate fine-tuning processes. This enhancement will lay the groundwork for potential future integration with InstructLab, an open-source AI project enabling community contributions to Large Language Models (LLMs) by adding new skills or knowledge. The primary focus will be on creating mechanisms to query and utilize data effectively, with a stretch goal of integrating static analysis tools and implementing an agent-based workflow. - This project will significantly enhance Kai’s backend, making it more scalable and capable of providing deeper code insights while also contributing to the enrichment of LLMs through InstructLab. It will offer a rich learning experience for participating students, covering backend development, workflow management, and contributing to open-source AI projects. - Expected Outcome: - Successfully develop and implement a data querying mechanism in Kai to facilitate fine-tuning processes. - Demonstrate the enhanced backend with improved data querying capabilities. - Participate actively in community meetings, presenting progress and insights. - Create a detailed blog post documenting the project, its outcomes, and potential future directions, including the possible integration with InstructLab. - (Stretch Goal) Develop a reusable module fo
<p>I am applying to work on the GSoC 2017 Augmented RNNs project. I am currently a first-year Software Engineering student from Astrakhan State University (Astrakhan, Russia). I have already taken some coursework on machine learning. For example, I have finished the Machine Learning and Data Mining specialization on Coursera (Russian-language specialization from Moscow Institute of Physics and Technology, certificate link: <a href="http://bit.ly/2nnuh03" target="_blank">http://bit.ly/2nnuh03</a>). I also passed Artificial Intelligence course at UC Berkeley (on edX, certificate link: <a href="http://bit.ly/1K6B2sR" target="_blank">http://bit.ly/1K6B2sR</a>). I’m already fairly familiar with deep learning. For example, recently I implemented optimality tightening from “Learning to play in a day” (<a href="https://arxiv.org/abs/1611.01606" target="_blank">https://arxiv.org/abs/1611.01606</a>) for the AgentNet (“Deep Reinforcement Learning library for humans”, <a href="https://github.com/yandexdataschool/AgentNet" target="_blank">https://github.com/yandexdataschool/AgentNet</a>). Here is the merged pull request: <a href="https://github.com/yandexdataschool/AgentNet/pull/88" target="_blank">https://github.com/yandexdataschool/AgentNet/pull/88</a>. I am interested in this project because it offers me a challenge while sharpening my knowledge of machine learning.</p>
Problem: While Large Language Models (LLMs) like ChatGPT can generate R code, they often lack precision when answering questions about third-party R packages or contributing to the R language itself. This can limit their usefulness for R users, particularly for new contributors seeking to understand the R core or engage in package development. Furthermore, many of these AI tools are proprietary or resource-intensive, excluding users with limited hardware or funding. Solution: ChatR proposes a specialized R chatbot that is lightweight, locally runnable (even without a GPU), and customized to provide reliable support on R packages, documentation, and contribution practices. The project will use Retrieval-Augmented Generation (RAG), prompt engineering, and a lightweight open-source LLM (via Ollama and llama3.2:3b-instruct) to deliver targeted responses. It will be delivered as an R package with both CLI and Shiny UI interfaces. Deliverables: An R package wrapping the chatbot and customizable prompts Local model integration using Ollama and ellmer RAG-based indexing of documentation (e.g., CRAN, Writing R Extensions) A Shiny widget interface for interactive usage in RStudio Documentation, test suite, and demo applications This project will significantly support learners, developers, and contributors by democratizing access to reliable AI-based R support and onboarding tools.
<p>This project is focused on incorporating a multiscalar segregation metric into the Python Spatial Analysis Library (<a href="https://pysal.org/" target="_blank">PySAL</a>) toolset.</p> <p>Following on from the suggestion of a methodology to provide <a href="https://doi.org/10.1073/pnas.1900192116" target="_blank">“Segregation through the multiscalar lens” (Olteanu et al., 2019)</a>, it has been the goal of the PySAL community to create a convenient function to undertake this methodology; computing the levels of divergence between different sub-areas and the total population of the area, using the <a href="https://en.wikipedia.org/wiki/Kullback%E2%80%93Leibler_divergence" target="_blank">Kullback-Leiber (KL)</a> technique (also referred to as relative entropy).</p> <p>Building on the work of this paper, the pre-existing <a href="https://github.com/pysal/segregation/issues/142" target="_blank">discussions within the PySAL community</a> regarding this function, and the code contributed by <a href="https://github.com/ceciledebezenac/segregation_index" target="_blank">Cécile de Bézenac</a> to compute this measure, this project will provide an efficient, easy-to-use function to compute this divergence-based metric of segregation. It will provide workbooks that walkthrough how the function can be ran, as well as examples of how to use the output to produce informative visualisations that help unpick the complex patterns of segregation between multiple groups.</p>
To protect a free software project worked on by several contributors against regressions caused by a committed change, one needs frequent, automated testing of the code base, ideally triggered by every commit into the repository. This is called Continuous Integration (CI). What is triggered on each commit is usually some static analysis of the code using common, specialized tools and build and execution tests, usually doing `./configure; make; make test` on different system platforms. This naturally requires test scripts/programs compiled and run by the `make test` step. For CUPS, for example, the daemon is started (on an unprivileged port so that it does not need root), queues created and listed, jobs sent, and the logs checked whether everything went OK. For Ghostscript, a large collection of input files (gathered from bug reports) is processed and converted into raster formats. The task here is to write test programs for the different OpenPrinting projects so that `make test` does something useful, efficiently catching regressions. They should exercise important functionality of the software with different parameters and analyze logs and output files to check whether the program did the expected work. Test programs are also needed for the so-called 'autopkgtest' tests which are added to Debian packages and executed whenever the package is uploaded to Debian or Ubuntu. In addition, instruction files and shell scripts are needed to build the software on different platforms/environments, run tests, and create GitHub Actions (for the automatic triggering on each commit)
This project aims to enhance the monitoring capabilities of OneBusAway (OBA), an open-source platform that provides real-time transit information to riders across multiple cities. The focus is on improving Watchdog, a Go-based backend service that tracks the health and data integrity of OBA servers by reporting detailed metrics to Prometheus. In the past, a Python script was used to monitor the system by checking real-time API data and identifying issues such as expired transit bundles or data mismatches. However, this legacy solution lacked flexibility and scalability. The current Watchdog framework, built in Go, addresses these shortcomings but still requires the addition of several key metrics. The proposed solution builds on the existing Go codebase, expanding and refining the metrics to ensure accurate, real-time tracking of issues such as unmatched trips, stale data, and anomalies in transit information. The project also prioritizes maintainability by refactoring code, implementing robust error reporting through Sentry, and ensuring comprehensive test coverage to maintain reliability. Key deliverables include: Implementation of multiple high-priority metrics Complete test coverage and improved modularity of the codebase Clear, user-friendly documentation A production-ready, extensible monitoring service for OBA This work will provide transit agencies with better insights into data health and system performance, ultimately enhancing the experience for thousands of daily riders.
Institutional departments, such as the Biomedical Informatics (BMI) Department of Emory University School of Medicine, manage vast amounts of data, often reaching petabyte scales across multiple Linux-based storage servers. Researchers storing data in these systems need a streamlined way to modify ACLs to grant or revoke access for collaborators. Currently, the IT team at BMI is responsible for manually handling these ACL modifications, which is time-consuming, error-prone, and inefficient, especially as data volume and user demands grow. To address this challenge at BMI and similar institutions worldwide, a Web Management Interface is needed to allow users to modify ACLs securely. This solution would eliminate the burden on IT teams by enabling on-demand permission management while ensuring security and reliability. The proposed system will feature a robust and highly configurable backend, high-speed databases, orchestration daemons for file storage servers, and an intuitive frontend. The proposal includes an in-depth analysis of required components, high-level and low-level design considerations, technology selection, and the demonstration of a functional prototype as proof of concept. The goal is to deliver a production-ready, secure, scalable, and reliable system for managing ACLs across multiple servers hosting filesystems such as NFS, BeeGFS, and others. This solution will streamline access control management and prepare it for deployment at BMI and other institutions worldwide, significantly reducing the manual workload for IT teams.
We study the sampling of correlation matrices from a given probability density, which has applications in various scientific, engineering and business areas (biology, finances,...). This problem is technically difficult due to the constraints of correlation matrices (entries in [-1,1], positive semi-definiteness). The current methods can only scale to a few tens of dimensions. This project aims to provide efficient C++ implementations for new geometric-flavored algorithms to sample correlation matrices (Arakelian, Chalkis 2021) and integrate them into VolEsti, an open-source high-performance software for sampling, volume computing and geometric statistics. Our main tasks consist of implementing a new class of convex bodies to represent the space of correlation matrices and geometric operations for performing two random walk sampling algorithms (the accelerated billiard walk and Reflective Hamiltonian Monte Carlo algorithm) over those convex bodies. These tasks can be supported by the already existing geometric facilities of VolEsti and the theoretical results found in related works. We will focus mainly on building an optimized C++ code to achieve better scalability for those algorithms and carry out intensive experiment and benchmark with other competitors to justify our efficiency. The expected duration of this project is 175 hours spread over 7 weeks of coding period (June 13 - July 29). The C++ implementation obtained by the end of this project will expand VolEsti towards an all-in-one high-performance statistic tools for research and business uses.
The Mifos community has grown significantly over the years, along with the increasing number of projects and discussions happening across its platforms. Newcomers, as well as contributors unfamiliar with specific parts of the ecosystem, often struggle to navigate and understand the breadth of information shared. While the general Slack channels host a wealth of discussions, support is inconsistent and depends on the availability and responsiveness of community members. Similarly, valuable insights are often scattered across community blogs, mailing lists, and Jira tickets, making it challenging to locate relevant information quickly. To address these challenges, this project proposes the development of an AI-powered chatbot that leverages messages from Slack channels, posts from community blogs, updates from Jira, and other conversational and announcement platforms used by the Mifos Initiative. The chatbot will be capable of answering queries related to project updates, community decisions, usage guidance, and more—based on real-time information and past conversations. The core system will utilize a Retrieval-Augmented Generation (RAG) pipeline to dynamically pull relevant data from these sources and serve accurate responses to user questions. The system will also evaluate different vector stores and embedding strategies to optimize retrieval from unstructured conversational data. By the end of the project, the Mifos Initiative will have an intelligent AI assistant that significantly improves community support, provides instant clarity on ongoing discussions, and makes the ecosystem more approachable for contributors at all levels.
The Flexible Network Tester (Flent) is an industry-standard tool for evaluating Bufferbloat and network performance. However, benchmarking simulated networks in ns-3 currently requires researchers to rely on external, error-prone parsing scripts to translate simulator events into Flent-compatible data. This project solves this disconnect by natively integrating the Flent Application API into the ns-3 mainline. The proposed solution involves modernizing a legacy C++ wrapper, eliminating artificial queue constraints used in prior proof-of-concepts, and refining the linear interpolation logic to accurately translate discrete ns-3 trace callbacks into strict periodic data points. A critical phase of the project involves scientific validation. comparing the simulated ns-3 outputs against real-world Linux hardware benchmarks (using tc and ss) to guarantee mathematical and statistical accuracy. Deliverables: 1) A robust, memory-safe FlentHelper C++ API that allows users to seamlessly configure tests and directly output visualization-ready .flent JSON files. 2) A scientific validation report proving the parity between the simulated network metrics and physical Linux network namespaces. 3) Expanded support for complex multi-flow Bufferbloat tests (including RRUL, Best Effort, and VoIP). 4) Comprehensive user documentation and automated example scripts merged into the ns-3-dev mainline.
The OWASP Web Application Honeypot is the only open community project focused on the HTTP application layer, but it currently sits as a dormant proof-of-concept with an outdated logging format, no fingerprint detection, and no path to push threat data into community platforms like MISP. This proposal evolves it into a production-ready, adaptive, and intelligence-grade platform. The solution is built around 8 interconnected deliverables: 1. Versioned JSON logging schema (v1.0) with GeoIP2 and MITRE ATT&CK enrichment 2. Automated CRS version management via nightly GitHub Actions 3. CRS 4.x honeytrap plugin with hot-reload daemon (no container restart required) 4. Shodan Honeyscore-triggered chameleon engine for automatic persona rotation 5. Vulnerable application fingerprint library with 4 personas (Apache, IIS, phpMyAdmin, WordPress) 6. Multi-region AWS deployment framework using Terraform with centralised Kibana 7. MISP and STIX 2.1 threat intelligence exporters with optional TAXII push 8. Industry segment profiles for education, financial, and general deployments switchable via a single environment variable Each deliverable has measurable success criteria and risk mitigation. Built on prior production work in DICOMHawk, GreedyBear, and IntelOwl where identical problems were already solved. Total effort is 350 hours across 13 weeks.
This project aims to create a high-quality custom dataset using PaLM API and create a high-quality text summarization model by fine-tuning a pre-trained model with the custom dataset. The custom dataset will be a CSV file with 10K rows and 4 columns: id, prompt, document, and summary. The document should vary in different writing styles such as news articles, blog posts, legal papers and so on, and the length of a summary will be between 1/3 and 1/4 of the length of the original document. This will make the custom dataset to be far superior to most publicly available datasets like CNN-Daily-Mail or XSUM, which typically generate 1-2 sentence summaries. Then I will create a few text summarization models with different pre-trained models, improving each fine-tuned model’s accuracy by implementing strategy driven from bias/variance and error analysis. After creating a few fine-tuned models, I will pick the best performing one based on the evaluation metric. Based on this, I will work on creating a tutorial covering the whole process, such as creating a custom dataset using PaLM API, fine-tuning pre-trained models using Keras API, and selecting the best performing one based on a evaluation metric. As a result, by creating this comprehensive tutorial, the project will encourage other developers to explore/use Keras API and PaLM API in their projects.
Problem to Solve : Build a system which performs the following: Enables full-text search of documents; filtered by agency, date, views Recommends similar documents based on semantic similarity of document contents Extracts significant document features such as topics, persons, locations, etc. Clusters and sorts documents by artifact topic (i.e. aerospace, environmental, nuclear, civil rights, etc.) Including: Natural language summaries for each artifact in the collection. Solution: To build the requested system, we will need several components and technologies. Here are the basic steps to achieve the functionality we require: Data ingestion: Loading the documents from a data source and extract the relevant information such as the document ID, title, content, agency, date, and views. Full-text search: Indexing the documents in a search engine such as Elasticsearch and enable full-text search with filters on agency, date, and views. Semantic similarity: Using a natural language processing model such as Doc2Vec to calculate the semantic similarity between documents and recommend similar documents. Document feature extraction: Using a named entity recognition model such as Spacy to extract significant document features such as topics, persons, locations, etc. Clustering and sorting: Using a clustering algorithm such as KMeans to group the documents into clusters based on artifact topic and sort them accordingly. Natural language summaries: we can use a summarization algorithm such as Gensim to generate natural language summaries for each document in the collection.
etcd is a distributed key-value store that serves as the backbone for Kubernetes and other cloud-native systems, storing critical configuration and state data. However, at scale, multiple applications constantly querying etcd for current state and watching for changes can overload the server and create expensive catch-up scenarios for slow subscribers. This project developed an experimental caching solution that brings Kubernetes' proven watch cache pattern to any infrastructure project without depending on the Kubernetes codebase. Core Components: (1) Watch Demultiplexer: Consolidates multiple client watch subscriptions into a single upstream etcd connection, then broadcasts events to all subscribers, reducing server load; (2) Event History Buffer: Maintains an append-only ring buffer of recent watch events, enabling lagging watchers to catch up from local history rather than reopening expensive upstream watches; (3) B-Tree State Mirror: After an initial snapshot, builds and maintains an in-memory B-Tree of current key/value state, applying watch events incrementally for fast range queries and lookups; (4) Point-in-Time Snapshots: Preserves historical B-Tree snapshots in a ring buffer, allowing exact stale reads at specific revisions without hitting etcd; (5) Resilient Control Loop: Handles initialization, upstream errors, compaction events, and automatic cache rebuilding with proper client notification.
Financial factor investing relies on rigorous quantitative research to explain asset returns and generate alpha. While many academic models and institutional frameworks exist, open-source tools that replicate these methods — especially in R — are few and far between. This project aims to close that gap by contributing to the ExpectedReturns package, developing clean, modular functions that implement and generalize key factor construction techniques inspired by Antti Ilmanen’s Investing Amid Low Expected Returns. The focus will be on engineering reusable code for factors like value, momentum, profitability, and investment using raw or semi-structured financial data. These will be built using lightweight, testable components supported by packages like FactorAnalytics, PerformanceAnalytics, and tinytest, while following conventions used by Chen, Zimmermann, and Kelly. Also included will be vignettes and documentation that show how to reproduce these concepts in practice — making the tools both transparent and portable. This will be a two-month project. Deliverables will include: – Core functions for factor construction and data prep – Lightweight unit tests and clean vignettes – Documentation of inputs, outputs, and assumptions – A reproducible build setup that works across systems The goal is to make these concepts accessible — not just for researchers, but for anyone trying to understand and apply factor models in real-world contexts. If successful, this project will leave behind a set of tools that are as useful to the open-source community as they are to academic replication.
The goal of this project is to enhance the existing Dual Contouring (DC) method in CGAL by implementing manifold contouring methods. While the classical DC is a powerful isosurfacing method, it may produce non-nonmanifold surfaces, leading to topological inconsistencies and computational challenges. Manifold dual contouring methods overcome this issue by introducing manifold constraints to ensure the generation of 2-manifold surfaces. The project will begin with a detailed study of existing literature, including Manifold Dual Contouring by Schaefer, Ju and Warren, and other related methods. Based on the research, we will determine an algorithm that combines the most robust aspects of these methods. The next phase is to review current DC implementations in CGAL to identify gaps that require modifications, particularly in routines such as the Quadratic Error Function (QEF) minimization, octree traversal, and polygonalization. Lastly, additional features will be added, including manifold criterions like the Euler characteristic test, and the support for multiple vertices per cell. The final deliverables will be a robust implementation of the enhanced DC method integrated into CGAL under the Isosurfacing subroutine. The implementation will adhere to CGAL’s existing coding conventions to ensure flexibility, consistency, and maintainability within the library. The documentation will include a test file under Isosurfacing 3/test/Isosurfacing 3, visualization of test cases under Isosurfacing/fig, and a theoretical background under Isosurfacing 3/doc/Isosurfacing 3/Isosurfacing 3.txt.
During GSoC, I propose to build a carbon-aware fitness tracker application from scratch that combines personal health tracking with environmental awareness while prioritizing user privacy. The project addresses two key problems: the lack of privacy in existing fitness apps, which often rely on external servers, and the absence of tools that help users understand their daily carbon footprint. To solve this, I will develop a Flutter-based mobile application along with a Wear OS companion app, integrating them using the Data Layer API and platform channels to seamlessly transfer fitness data such as steps, heart rate, and activity metrics from the watch to the phone. On the Wear OS side, I will use the Health Services API to collect real-time data, while the mobile app will feature a transport logging system that calculates carbon emissions or savings based on user travel choices, along with a dashboard displaying weekly summaries, visual charts, and actionable sustainability suggestions. All user data will be stored locally using SQLite to ensure complete privacy, and the application will be supported by comprehensive unit, widget, and integration testing to ensure reliability. The final deliverables will include a fully functional mobile and Wear OS application, a secure local data management system, a carbon footprint tracking and visualization module, and a production-ready app prepared for deployment on Android and Wear OS platforms.
<p>The ability to easily handle advertisements in phpBB is often requested. <a href="https://www.phpbb.com/community/viewtopic.php?f=64&t=2314201" target="_blank">Latest pool for next official extension</a> results in Advertisement Management being tightly at the second position, while it’s <a href="https://www.phpbb.com/community/viewtopic.php?f=496&t=2255691" target="_blank">extension request topic</a> is far more active (with 126 replies and almost 8000 views) than pool’s winner Paypal Donations (which <a href="https://www.phpbb.com/customise/db/extension/paypal_donation_extension/" target="_blank">already exists</a>). <a href="https://www.phpbb.com/customise/db/mod/advertisement_management/" target="_blank">EXreaction’s modification</a> is 9th most downloaded MOD with more than 66000 downloads. Clearly, there is a big demand for this extension.</p> <p>My goal will be creating an advertisement management extension that allows admins to add HTML/JS advertisement code to number of locations in the template. If time allows, many additional features will be implemented, i.e. end date, hide ad for specific groups, adblocker friendly message, ad priority, views and clicks counting, ad owners, banner uploads, extensible and/or additional template locations and PHP event hooks for other extensions to further enhance usage experience.</p>
The ROS 2 ecosystem has made significant leaps in performance over the last few years, supported by benchmarking tools like buildfarm_perf_tests and ros2-benchmark-container. These tools take care of profiling middleware and client library performance under various configurations. As of now, the recurring monitoring path in continuous integration (CI) is mostly rclcpp-centric, providing good regression visibility for C++ implementations. However, a current limitation of the ecosystem is that it lacks periodic performance monitoring for other heavily used client libraries like rclpy (Python) and rclrs (Rust). This leaves these libraries with weaker regression visibility, making it difficult to measure the performance impact of new topologies involving remote host subscriptions or track the performance of ROS actions and services reliably. This project focuses on vastly extending the suite of tests that run regularly in buildfarm_perf_tests by porting C++ benchmark instrumentation for use with the other client library implementations. This project thus aims to add high-signal, recurring CI coverage across rclcpp, rclpy, and rclrs with minimal CI cost overhead. Furthermore, to enhance the contribution, there will also be a focus on updating the performance test result graphs in CI to use modern observability tools. The final deliverable includes an updated web dashboard (built with Grafana) that tracks key compute metrics such as latency, CPU usage, and memory over time, providing the community with a complete, cross-language performance diagnostic ecosystem.
Problem: Imbalanced datasets pose a significant challenge in machine learning, where standard metrics like accuracy can falsely evaluate a model that simply predicts the dominant class. Currently, the R community lacks a comprehensive and unified framework for handling imbalanced data and X-Risks problems natively integrated into the mlr3/mlr3torch ecosystem. Solution: This project, mlr3torchAUM, provides a comprehensive solution for imbalanced classification in R. It will bridge the current gap by integrating state-of-the-art loss functions, advanced evaluation metrics, and various data sampling techniques directly into the mlr3/mlr3torch pipeline. Deliverables: 1. State-of-the-Art Loss Functions: Implementation of algorithms including log-linear all-pairs squared hinge loss, Area Under Min (AUM) loss, and cost-sensitive logistic loss. 2. Sampling Operators: A robust suite of over-sampling techniques including SMOTE and ADASYN, alongside under-sampling techniques, all implemented safely under a `lazy_tensor` mechanism to avoid memory issues. 3. Advanced Evaluation Metrics: Integration of Precision-Recall curves, Macro/Micro AUM/AUC, and MCP/IMCP to fully support multiclass imbalanced scenarios. 4. LibAUC Integration: Porting cutting-edge losses and optimizers from the Python LibAUC library into R. 5. Engineering & Release: Comprehensive Test Driven Development, GitHub Actions for CI/CD, detailed vignettes, and a final submission to CRAN.
<p>In GSoC 2020, The TFLite team and I released the <a href="https://docs.google.com/document/d/1zm9Ifiql4aFKTXMdEe0FXlEU83g6l5jWCO8a3BtHeI0/edit?usp=sharing" target="_blank">TensorFlow Lite Support Suite</a> consisting of TFLite Flutter Plugin, TFLite Flutter Helper Library, and a couple of example apps with tutorials. The project is receiving excellent comments from the community, as they are finally able to build performant Flutter ML apps with models and TF versions of their choice. The recent release of Flutter 2.0 should attract even more users. This year, we plan to extend the TFLite Flutter Support Suite based on the users' feedback and latest developments in the TensorFlow Lite ecosystem.</p> <p><a href="https://github.com/am15h/tflite_flutter_plugin" target="_blank">TFLite Flutter Plugin</a> will be improved for better handling errors and supporting more platforms along with Android and iOS.</p> <p><a href="https://github.com/am15h/tflite_flutter_helper" target="_blank">TFLite Flutter Helper</a> will be updated to match developments in its Java counterpart.</p> <p><strong>Flutter Task Library</strong> based on the TFLite Android Task Library to provide out-of-box support for popular use cases like detection, question, and answer, etc. The Flutter Library will leverage the performance and capabilities of the C++ Task APIs through dart ffi bindings. Example apps to demonstrate the usage of Task Library.</p>
Dear Sir, I hope you are doing well. My name is Tianyou Liu, and I am writing to submit my GSoC 2026 proposal for Mogan STEM: “Julia Plugin with Virtual Environment Support.” In the proposal, I describe an implementation plan to enable Julia-powered, reproducible computing directly inside Mogan. The key technical components include: Mogan-side Julia plugin to identify and extract Julia code sections and provide an in-editor execution workflow. A persistent local Julia kernel process to execute code on demand and maintain session state across runs. A lightweight IPC layer between Mogan and the kernel (socket-based, request/response), returning structured execution results for rendering. Output and error capture (stdout/stderr, stack traces, and rich results where applicable) to present execution feedback clearly inside Mogan. Project-aware environment activation by automatically locating the nearest Project.toml (and using Manifest.toml when present) and executing code in the corresponding Julia environment. Integration with Julia’s Pkg workflows to support reproducible dependency management (e.g., activate/instantiate and related environment operations). My resume is enclosed in the attachment. More details are discussed in the proposal enclosed in the attachement. Thank you for your time and consideration. I look forward to the possibility of contributing to Mogan STEM this summer. Best regards, Tianyou Liu Email: liuty2025@mail.sustech.edu.cn GitHub: https://github.com/AXeonV
The RISC-V movement has massive potential to unify a fragmented industry behind a single instruction set architecture (ISA). If the participants in the industry can agree to focus their efforts on a single processor architecture, rather than duplicating efforts among incompatible architectures, the entire computing ecosystem benefits. Inefficiency in critical base components of the ecosystem hampers this consolidation. There are separate efforts in documenting the RISC-V ISA, succinctly describing the semantics of the ISA in the RISC-V Sail implementation, and the numerous projects which directly serve as the base components of the software ecosystem, including assemblers, disassemblers, compilers, linkers, loaders, simulators, emulators. In summary, the tasks in this project will include: Improving the RISC-V Sail specification. (Sail language, git/GitHub) Improving the Sail parser’s JSON backend to extract more complete and accurate information. (OCaml, git/GitHub) Improving the RISC-V ISA interactive web site with new functionality and information. (Javascript, React, Carbon, or similar web frameworks, git/GitHub) Survey downstream projects which have dependencies on the RISC-V ISA. (C, C++, RISC-V assembly) Implement transformations of RISC-V ISA representation in JSON into downstream project content. (Python or similar, C, C++, RISC-V assembly) Engage with upstream projects (Sail, RISC-V Sail specification) to submit change proposals and see that they become acceptable.