Explore Projects

Scope: To create a standalone React component from MatchMiner that will use Firebase to provide trial curation across multiple projects uses Requirements: • Familiarize with React, MatchMiner, OncoKB Angular and Firebase Execution • Study previous MatchMiner implementations to leverage that information into the current implementation plan • Refactor Match Miner component • Code formatting • Create standalone component that can be reused across multiple projects • Employ best practice on naming conventions and proper de-structuring Constraints: • Time • Lack of working experience in Angular Risks: • Can only build upon the component, cannot transform or remove features • Unexpected consequences of changes and ensuring failures will be localized to the component Deliverables Task 1: Strip down Match MinerAngular to base component, its most reusable part, via a DRY method. Task 2: Re-factor MatchMiner in React that will be extendable as a stateless component Task 3: Ensure library component in React is developer friendly in order to not burden the End Dev Task 4: Testing in staging environment to ensure proper functionality

<p>*APPLICATIONS ONLY OPEN TO US BASED COLLEGE STUDENTS*</p><p><br></p><p>1. Problem Statement</p><p><br></p><p>Today, SONiC KVM-based PR testing validates functional correctness (test pass/fail) but does not track resource consumption or performance characteristics over time. This creates several blind spots:</p><p><br></p><ul><li>Performance regressions (CPU spikes, memory leaks, excessive I/O) introduced by PRs go undetected until they reach production or nightly pipelines.</li><li>There is no historical baseline of resource utilization per feature branch, making it impossible to distinguish normal variance from genuine degradation.</li><li>Nightly test environments lack systematic profiling, so gradual performance erosion across releases is invisible until a tipping point is reached.</li><li>Root-cause analysis of production incidents is hampered by the absence of correlated profiling data from the CI/CD stage where the regression was introduced.</li></ul><p><br></p><p>Without a structured profiling database and automated anomaly detection, the team operates reactively—discovering performance issues in production rather than catching them at the PR gate.</p><p><br></p><p>2. Proposed Solution</p><p><br></p><p>Build an end-to-end performance profiling pipeline that runs alongside SONiC KVM-based test execution, stores results in a centralized database, and automatically flags regressions at the PR gate.</p><p><br></p><p>2.1 High-Level Architecture</p><p><br></p><p>The solution is composed of four core components that integrate into the existing CI/CD and nightly test workflows:</p><p><br></p><ul><li>Profiler Container – A lightweight Docker container packaging the community profiler (e.g., py-spy, perf, cProfile) that runs in sidecar mode alongside the SONiC KVM during test execution.</li><li>Profiling Database – A remote time-series/relational database (e.g., PostgreSQL + TimescaleDB or InfluxDB) that stores per-run profiling snapshots keyed by feature branch, commit SHA, test case, and timestamp.</li><li>Analysis Engine – A statistical analysis module that performs comparative, clustering, and outlier detection on profiling data to identify spikes against historical baselines.</li><li>PR Gate Integration – A CI pipeline step that queries the analysis engine after test completion and fails the PR if any metric exceeds the configured threshold.</li></ul><p><br></p><p>3. Mentorship Objectives</p><p><br></p><ul><li>Help the mentee learn about SONiC OS architecture, container ecosystem, and KVM-based testing infrastructure.</li><li>Help the mentee gain hands-on experience with performance profiling tools (py-spy, perf, pidstat) and statistical analysis techniques.</li><li>Help the mentee understand CI/CD pipeline integration and automated quality gates.</li><li>Work with virtual SONiC testbeds (vsonic) to develop and validate the profiling pipeline without physical hardware.</li><li><strong>This is a summer term program, Mentees are expected to work 40~ hours a week</strong></li></ul>

This proposal aims to enhance MIT App Inventor by developing artificial intelligence (AI) components for iOS platforms. By re-implementing existing AI features, the project seeks to democratize AI development and empower users to seamlessly integrate AI functionalities into their mobile applications. The deliverables include designing and implementing these components, integrating them into the MIT App Inventor platform, providing comprehensive documentation and tutorials, and conducting thorough testing for reliability and performance. Ultimately, this endeavor strives to foster innovation and creativity in mobile app development while making AI accessible to a broader audience.

<p>Gensim is an NLP library which claims to be highly effective during training and produce linear performance growth with increasing the number of threads.</p> <p>Currently, that is not true on machines with a large number of cores (&gt;10) and large data files. The reason of this is that almost all Gensim models which support multithreaded training work in the following way. There is <strong>single job producer</strong> -- worker which reads the data and pushes the chunks into the job queue. Also, there are <strong>many job consumers</strong> -- workers which pull the chunks and update the model parameters in parallel.</p> <p>The problem is that consumers' code is optimized well, so this leads to <strong>workers starvation</strong> problem. Job producer just can't fill the queue at such a high pace. This is the case even using fastest <code>read the line, split it and yield</code> corpus iterator.</p> <p>This problem could be solved by allowing users to pass <code>K</code> data streams (currently only single-stream == single job producer thread is supported), e.g. which point to <code>K</code> large files and use <code>K</code> job producers to fill the job queue.</p>

<p>Writing XMPP components is a good way to enhance the functionality of XMPP servers like ejabberd. Jabber Component Protocol (XEP-0114) is used today for this goal. However, this protocol is quite limited. The goal of this project is to implement XEP-0356 Privileged entity and XEP-0355 Namespace delegation server extensions to XMPP that will allow to run more powerful component on ejabberd. Implementation of these extensions can help to extend ejabberd functionality with existing powerful components like Collecta or SàT and give an impulse to create new services.</p>

<p>The Open Event Project offers event managers a platform to organize all kinds of events including concerts, conferences, summits and regular meetups. The components support organizers in all stages from event planning to publishing, marketing and ticket sales. Automated web and mobile apps help attendees to get information easily. There are FOUR components of the project:-</p> <ol> <li>The Open Event Format Definition</li> <li>The Open Event Server</li> <li>The Open Event Android App Generator</li> <li>The Open Event Web App Generator</li> </ol> <p>The Open Event Server offers features for events with several tracks and venues. Event managers can create invitation forms for speakers and build schedules in a drag and drop interface. The Open Event Server exposes a well-documented JSON:API Spec Compliant REST API that can be used by external services (like the Open Event App generators and the frontend) to access &amp; manipulate the data. I would work on adding more features and deploying the V2 version. These features would then be added to the web frontend as well as the android app.</p>

<p>Goal of this project is to rewrite the current OpenDF frontend using React and make the UI fully component based . Also will use ES6, SCSS and Gulp for development. Also do component testing for the new frontend.</p>

This program incorporates server-based deployment workflow files to the server in a secure manner. It allows composing the workflows, aware of the existing programs in the server. it also allows the upload of the user programs, so that workflows can be composed with those, in addition to existing programs in the server.

<p>The Proposal focuses on the improvement of App Inventor in the following aspects: Component Enhancements and Runtime Instantiation. Component Enhancement mainly targets the improvement in the features of components (ListView) so that the user can add more forms of information into the component. The Proposal focuses on the improvement of Listview so that after the final enhancements, the user can add Images and Text in the order they wish. Runtime Instantiation of Components enables the user to instantiate components by just using the blocks. This in turn gives the user, the ability to add components at runtime and instantiate them when necessary. This feature can boost the memory management in App inventor by assigning memory when needed. The proposal also marks the enhancement of file access. The app inventor currently doesn't support the access of External Storage in general. The proposal focuses on adding this feature so that many apps such as file managers can be made. Now, app inventor need not call an intent to access a file. Finally the proposal focuses on adding animation properties to the components so that the user is able to give a "Living" feel to their application.</p>

The project "iOS versions of Android components" aims to develop iOS counterparts of popular Android components that are widely used in mobile app development. The objective is to provide iOS developers with an easier transition between the two platforms, by providing iOS versions of Android components that they are already familiar with. The project will involve identifying and analyzing popular Android components, understanding their functionality and behavior, and then developing their iOS counterparts using Apple's development tools and technologies such as Xcode and Swift. The iOS versions of Android components will be designed to be compatible with the latest versions of iOS, including iOS 14 and higher. The components will be thoroughly tested to ensure compatibility and reliability across different devices and operating system versions. This project will be beneficial to developers who are familiar with Android development and are looking to transition to iOS development. It will also be useful for iOS developers who want to incorporate popular Android components into their iOS apps. Overall, the project aims to improve the ease of transition between Android and iOS development, and ultimately enhance the user experience of mobile apps across both platforms.

<p>The goal of this project will be to move the existing functionality of the angular code over to react. The new components will be using web standards as much as possible, avoiding extensive use of third-party libraries.</p>

This project aims to complete and modernize the React-based UI of FOSSology by aligning it with the updated REST API v2 and current frontend best practices. The work includes finalizing the incomplete interface, upgrading React to 19.1.0 for improved performance and concurrency, and migrating from yarn to pnpm for faster, space-efficient development. It will also implement UX improvements from the FOSSology UX and UI redesign project and create a reusable component library with Storybook. Comprehensive documentation and deployment guidelines will be provided to ensure long-term maintainability and contributor onboarding.

<p>Currently, EOS delivers icons via a set of well-documented methods, which chiefly include EOS-Icons Package, CDN, or direct download of icons in SVG/PNG formats. This project will be based on developing an npm package that can deliver EOS Icons to its users as an independent component library and create a unified central system that will enable EOS to deliver its icons to various frameworks (e.g. React, Vue and Angular) independently. This npm package will be as lightweight as possible in order to reduce the load put on the browser (using the tree shaking approach), which will result in providing a much smoother workflow to the users. Creating a package of EOS Icons for React, Vue, and Angular frameworks will go a long way in having a more consistent user experience as well as boost capability to accommodate users who migrate from one framework to another.</p>

<p>Rizin currently relies upon manually writing code for adding a new CPU or an IO port. This implementation is unfit as the vast and growing ecology of hardware components such as CPUs and SoCs regularly implement a part of architecture with custom instructions, registers, and address configurations with trivial differences, making it infeasible to maintain all of them inside Rizin.</p> <p>Providing a level of abstraction in handling this entropy in embedded systems, by supporting editable CPU and platform profiles is the goal of this project. This will also make adding and maintaining these ports easier with less interaction with Rizin’s core. This project also aims to add more flexibility in having a way of importing existing hardware data description documents so that reverse engineering on particular chipsets is easier. This will also help us to memory map the peripheral accesses and registers to provide a better reverse engineering experience. This, in turn, could also be extended to benefit Rizin in terms of compatibility and the end users in terms of user experience.</p>

Seccomp is a security facility from the Linux Kernel that prevents processes from executing unauthorised syscalls. By limiting the number of permitted syscalls, seccomp is being utilised in conjunction with Kubernetes to reduce the attack surface of the containers. KubeVirt already supports custom Seccomp profiles, but that is based on the default seccomp profile that cri-o uses. This static approach leaves room for the profile to block necessary syscalls or allow unnecessary syscalls, hence compromising the security. This project focuses on automating the process of generating a seccomp profile for the VirtLauncher pod.

I read the source code of libssh and I notice that there’re many switch-case in the sftp server code, while the implementation to handle different IO events in the server part is based on a call-based model, which has a quite clear logic. And sftp is a subsystem in libssh which can be established through a channel, as a subsystem having many sub-message type, it’s better to use a callback based method to implement a sftp server. Therefore, I’m going to modify the sftp part in libssh and write a sftp server with the api in libssh to achieve this goal.

<p>After a busy couple of days at the Bristol Hackathon, the developers behind ghcide and haskell-ide-engine merged efforts resulting in an exciting new, unified language server. Building upon ghcide's snappy shake based build system and with the extensible plugin support from haskell-ide-engine, it aims to be the de-facto language server for newcomers to Haskell. It is still new and there is plenty of work to be done throughout the ecosystem to get it ready for users:</p> <h3>Implicit cradle configuration</h3> <p>Improve how hie-bios implicitly detects and sets up cradles (sessions) without the need for a hie.yaml file</p> <h3>Update haskell-lsp with new LSP features</h3> <p>The LSP specification moves quickly, and the latest version 3.15 has lots of new features that many language servers, not just Haskell ones, would love to take support of in haskell-lsp.</p> <h3>Get haskell-language-server ready</h3> <p>Now that the ghcide base and plugin architecture is mostly in place, plugins and tests need to be moved over. Continuous integration and distribution also need to be set up.</p>

<p>WSO2 Identity Server is the first Identity Server Bus in the industry which is capable of managing multiple user identities among applications, APIs, cloud, mobile, etc. One of the main components of the WSO2 Identity Server is user stores. Currently WSO2 Identity Server supports user stores related to LDAP, Microsoft Active Directory and Relational Databases such as MySQL, SQL Server, DB2 etc. With the fast growth of enterprise adoption of NoSQL databases in industry, WSO2 Identity Server needs to be expanded to support NoSQL Databases. In this project I will be implementing a user store support for WSO2 Identity Server based on MongoDB which is one of the most popular NoSQL database in industry today.</p>

<p>The aim of the proposed project is to improve support for the Dhall language in mainstream editors via the Language Server Protocol standard.</p>

<p>As a part of my GSoC proposal, I plan to integrate a Menu component in the existing MIT App Inventor. Menus are a common user interface component used to provide the user with a set of actions in an activity. Currently, this can be implemented using a number of buttons and setting their visibility appropriately. Developing a menu this way could be very tedious and complex for the user. Hence having a dedicated component in app inventor would be more convenient.</p>

<p>Zenodo is a great initiative for researchers and invenio is a collection of wonderful APIs. I have chosen this project because it targets every researcher and one of the basic and immediate requirements of the user from such a beautiful platform. It would also promote zenodo as researchers will start sharing their zenodo profiles in social media.</p>

Description: Update the CoRIM profiles used for provisioning Veraison services to align with the most recent specifications. Expected Outcome: - Add support for the updated formats to the `veraison/corim` package - Add support for the updated formats to the `veraison/cocli` command line tool - Allow the provisioning of endorsement and reference values specified using the updated formats to `veraison/services`

<p>During Google summer of code 2017, one student worked on making a backend that exposes information about Terasology servers. He also made a frontend using the ReactXP framework, which can build to multiple platforms, such as web, Android, and iOS. However, both the backend and the frontend need some work done on them to make them acceptable for end users. That is what this project is going to try to help accomplish.</p>