Explore Projects

<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>

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>The aim of this project is to make a breakpad server for VLC and other VideoLAN projects, similar to <a href="https://github.com/mozilla/socorro" target="_blank">Socorro</a> from Mozilla.</p>

George Vaindirlis coded a MPD server module for VLC last year. This project aims at finishing his work by adding support for more features from the MPD protocol and testing it with several MPD clients.

<p>This project will bring the JPF Inspector debugging tool up to date with the most recent version of JPF and Java, and it will add additional features, among which are a command-line interface, new commands and JPF introspection.</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>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>

<p>Data retriever provides a number of publicly available datasets. These datasets are not stored at a single location but are downloaded from various publically available data repositories. New datasets are being added to retriever regularly so it becomes crucial to check the <strong>availability</strong> and <strong>installation</strong> of all datasets. This is a tedious task so the process needs to be automated.</p> <p>The goal of this project is to create a status server and dashboard where maintainers and users can see the status of datasets i.e. whether the datasets are installing properly or not and the changes that have been made to the dataset.</p>

<p>DIRAC is a highly-scalable software used for accessing distributed resources from various distributed systems. DIRAC’s main contributor is LHCb and also its initiator. LHCb uses the different type of computing technologies in order to distribute and process the collected physics data and DIRAC is one the software which is used because of its scalability and the level of orchestration and monitoring it provides for the distributed resources which is the main requirement of the LHCb collaboration. Further, my task will be to upgrade DIRAC’s monitoring system further by assuring high-scalability as when the LHCb gets upgraded there can be an unpredictable type of data which needs to be molded easily by DIRAC for which we will use ElasticSearch which is one of the widely used NoSQL technology. With this, I will have to migrate the Service and Agent components and DIRAC's RequestManagementSystem and DataManagementSystem to support ES backend along with tests and documentation.</p>

This project addresses a key challenge in biomedical data management: enabling secure, standards-compliant access to clinical FHIR data while integrating with the Gen3 platform. The goal is to develop an open-source, containerized FHIR proxy that enforces Gen3 access control via Arborist and supports asynchronous API interactions for high-performance data access. The solution includes: 1) A proof-of-concept FastAPI proxy that routes FHIR requests to a HAPI FHIR JPA server, adding Gen3 security tags for each resource. 2) Scripted ingestion of synthetic NCPI FHIR resources to facilitate testing and reproducibility. 3) Comprehensive unit tests and example configurations for local and cloud deployment. 4) Full containerization with Docker and Docker Compose, with plans for Kubernetes deployment via Helm. By providing a secure, FAIR-aligned, and standards-based framework for FHIR data, this project empowers researchers and developers to access and manage biomedical data efficiently while maintaining strict compliance with security and privacy requirements.

This project implements a debuginfod-compatible server within Debusine to provide automated debug symbol resolution for Debian developers. Currently, debugging binaries built by Debusine requires manual installation of -dbgsym packages. This project aims to eliminate this manual labor by allowing tools like gdb to fetch symbols automatically via HTTP. Based on an analysis of the elf_classify logic in elfutils, I have designed and prototyped a pipeline that identifies and extracts .debug ELF files from -dbgsym.deb packages and parses their Build-IDs. The implementation integrates this extraction into the isolated sbuild worker task. These symbols are then indexed as debian:debug-symbol artifacts and served via a custom Django view that supports the buildid/<id>/debuginfo and executable endpoints, including HTTP Range requests for partial content. Key Deliverables: 1) An isolated extraction pipeline using pyelftools within the sbuild task. 2) A Django-based artifact storage and indexing model (debian:debug-symbol). 3) debuginfod-compliant HTTP endpoints (/debuginfo and /executable) with support for mandatory headers and 206 Partial Content. 4) Documentation and integration tests for gdb symbol resolution.

This project aims to develop an application that has the ability to delegate membership of a room based on the user’s interaction with other third party services. A user can either be invited, kicked or put in a “standby” state for a room based on their past interactions. There are five main components in this project: 1) A reusable frontend component that handles the login UI for both Matrix and other third-party services. 2) A server-side component and a bot that verifies a user’s authorization to a room and decides their membership. 3) An admin panel to configure the relationship between matrix rooms and groups in third party services. 4) An external invite URL that can be used to get an invite to a room. 5) Token authenticated account registration for existing authorized users. I will be using the matrix-nio library mainly for building the bot since it has most of the functions required for interacting with the server and building a feature-rich tool.

<p>'LOKLAK SERVER' is a distributed message search server to anonymously collect, share, dump and index social media search results.</p> <h3>CURRENTLY</h3> <p>SearchServlet in Loklak Server only able to scrape the tweets from Twitter according to query input. To use other scrapers, one needs to use it separate endpoints.</p> <h3>PROPOSAL</h3> <ul> <li>The idea is to integrate scrapers to SearchServlet to make scrapers capable to work concurrently through one endpoint.</li> <li>Make the system Easy-To-Integrate with any scrapers to be added in future.</li> </ul>

This proposal aims to implement the Menu, Sidebar, and Floating Action Button (FAB) components in iOS for MIT App Inventor, ensuring feature parity with Android as introduced in PR #2299. The Menu Component will introduce a dropdown-style menu supporting nested items, icons, and keyboard navigation. The Sidebar Component will provide a sliding navigation panel with swipe gestures, tap-to-close functionality, and essential navigation links like Home, Profile, Settings, and Logout. The Floating Action Button (FAB) will be a circular, floating button positioned at the bottom-right, supporting custom actions, animations, and a shadow effect for a modern UI experience. A key aspect of this project is ensuring feature parity with Android, maintaining UI/UX consistency across both platforms. I chose this project because it bridges the gap between iOS and Android, ensuring that MIT App Inventor provides a seamless cross-platform experience. It also enhances user experience by introducing smooth, intuitive navigation and interactions, making iOS-built apps more functional and engaging. Additionally, this project will expand MIT App Inventor’s capabilities by adding essential missing features, making the platform more versatile and user-friendly. The estimated timeline for this project is 175 hours, covering implementation, testing, and final integration. Upon completion, this update will significantly enhance MIT App Inventor’s iOS version, making it a fully-featured, cross-platform development tool that aligns with modern app-building standards.