Fetching the latest programs, projects, and workspace data.
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.
This project aims to finalize stalled pull requests and implement high-priority features in the Zulip web application, focusing on messaging, search, settings, and backend performance. In messaging and compose UI, the project aims to enable collaborative message editing, allow seamless messaging to unsubscribed channels with proper warning banners, and fix UI jitter during channel subscriptions. In search and settings, the project introduces wildcard, topic, and group-user mentions, revamps alert word notifications to integrate with topic-following, and adds Markdown support to custom profile fields. Finally, it optimizes backend performance by significantly reducing database queries for direct messages, stabilizing password reset email flows, and cleaning up legacy bot configuration logic.
Zulip's REST API documentation framework is well-built but incomplete, approximately 28 actionable endpoints remain undocumented, and the OpenAPI spec has accumulated structural debt through years of organic growth. This project has two phases. Phase 1 achieves complete endpoint coverage by documenting all remaining high and moderate priority endpoints following the full pipeline: OpenAPI schema, Python and cURL examples, sidebar registration, and changelog entries. Phase 2 refactors the spec's structure, promoting inline parameters to shared components, rationalising the Can*Group schema family, and cleaning up repeated inline response blocks. Deliverables: (1) Zero undocumented actionable endpoints in pending_endpoints. (2) A cleaner, more consistent OpenAPI spec with reduced duplication across parameters, schemas, and response blocks.
<p>Project involves working on improvements in Zulip which are priority and on project roadmap. Zulip is a team chat software so experience around searching and message view is a priority. My project involves improving this experience.</p> <ul> <li>Search entire organisation's public streams at once including messages sent by other members before a user joint.</li> <li>Not marking new unread messages as read when searching for older messages</li> <li>Fixing the ability to view/search messages sent by deactivated user in Group PM chats.</li> <li>Ability to create bot with admin privileges</li> <li>Some code refactoring and fixing few high priority bugs.</li> <li>Rebasing and fixing failing tests of an old PR which allows zulip users to have multiple api keys.</li> </ul>
The Zulip web application is being redesigned but there are several UI inconsistencies in various parts of the web app. After seeing the redesign-label issues, I understood that the modals, sidebars, icons, and interactive visual features are not all developed with an integrated look. This makes an inconsistent user experience with elements such as modal inputs being unstandardized, Icons and symbols lacking visual consistency across the web app components, and elements within the sidebar having improper alignment, scroll animation, and elements such as link styles, color logic, and interactions. The goal of this project is to standardize and improve these UI elements in a structured way. I will work on redesign-labeled issues along with UI tasks, improving design pattern consistency, improving CSS structure, and managing elements with modern UI standards. With careful testing and taking mentor feedback to ensure accuracy, have discussions on future design provided in Figma.
<p>Zulip provides powerful utility for bots and integrations, but parts of the system (like embedded bots) are still work in progress. To encourage more users to use the bots and integrations, and to also foster a better development experience with bots and integrations, this project aims at implementing better UI for the users to browse through available bots with verbose description, provide more developer-friendly interfaces for creating bots, and other related tasks to improve the bots system.</p> <h4>Improve the UI to Encourage Bot Usage</h4> <p>Display a list of available bots for all users and show accompanying descriptions or help messages. This sub-goal will be aiming at improving the UI to show more information about the bot.</p> <h4>Encourage Error Handling for Bots</h4> <p>Propose a way to raise custom errors from the API layer instead of leaving the error message from the server as is (e.g. {“result”: “error”, “msg”: “foobar”}) and requiring the developers to parse the error message to handle cases of error.</p> <h4>Create Standard for Bots Handling Commands</h4> <p>Support standard commands while keeping our layer of bot as thin as possible and allow standardized metadata to describe the behavior of our bots.</p>
<p>OSTree currently runs as root while doing all operations, including doing fetches from external repositories over HTTP. But libsoup is not exactly a secure well-tested library, and few projects use it. Running the fetch operations in a separate low-privileged process will add more security, as will switching to libcurl.</p> <p>Furthermore, the aria2 project implements a feature not found in Curl or LibSoup, namely multiplexing downloads from multiple servers. (e.g. for file A, aria2 can download 50% from server 1 and 50% from server 2). Moving to an external process will allow a pluggable fetching implementation, allowing the use of aria2's features for those who want it</p> <p>Further work may be done for the Fedora Modularization WG or ostree-related projects (such as GNOME Continuous)</p> <p>Full project proposal: <a href="https://fedoraproject.org/w/index.php?title=GSOC_2016/Student_Application_allangardner" target="_blank">https://fedoraproject.org/w/index.php?title=GSOC_2016/Student_Application_allangardner</a></p>
This project aims to enhance EvalAI's functionalities by automating large worker deployments in AWS, adding relevant features for efficient challenge management and also writing a robust and efficient test suite. The focus of the project is: To automate large worker deployment processes on EvalAI using AWS EC2 instances, reducing infrastructure running costs. Make challenge management seamless and less reliant on the admins reducing the dependency of challenge hosts on EvalAI admins. To make EvalAI more reliable and error-free by incorporating tests for different frontend and backend components. Having robust tests prevents making code-breaking changes to the codebase. This task will include adding unit tests for the API suite, prediction upload evaluation workers, code upload evaluation workers (on EKS), and integration tests for end-to-end testing of all components.
This proposal aims to implement a functional cloud storage integration for VLC Media Player using libcloudstorage Although the open merge request (!7526) introduces basic components such as service discovery and access modules, testing shows that the integration is not usable due to issues in authentication flow, threading, and state handling. For example, authentication cannot be triggered properly from the UI due to preparsing constraints, and token persistence issues lead to repeated login attempts. This project focuses on completing and correcting the integration so that users can reliably browse and access cloud storage within VLC. The work includes restructuring the authentication flow to work correctly with VLC’s threading model, fixing token storage and session handling, and ensuring proper navigation after login. In addition, necessary updates will be made in libcloudstorage to address outdated API usage and improve compatibility with current cloud providers. Testing will be included to validate authentication, directory access, and overall integration stability. By the end of the project, users will be able to log in once, browse their cloud directories, and stream media files directly within VLC.
<p>The goal of this project is to provide web components to users based on Patternfly patterns.</p>
<p>Improve the Demo creation in Origami and Provide REST API for demo access.Adding analytic server for optimising demo performance and for getting deeper Insights on demo functionality.</p>
This project aims to enhance and optimize the existing platform by implementing several important features and improvements. These changes include the addition of domains, tags, and a prize and sponsor page, as well as the introduction of a deregister process, a revamped profile page with a new tabular UI design, a participant team approval feature, and the inclusion of GMT time stamps and many more features.
This project aims to make EvalAI better for users. It will improve how errors are handled, add more tests to make sure things work properly, provide clearer documentation to help people understand, and make the user interface more user-friendly with new features like a "My Work" tab. The main goals are to create tests for important components like APIs and workers, develop guides for things like API usage and AWS setup, make error messages more clear, and add new features to enhance the overall user experience.
<h3>1. EvalAI Python Package.</h3> <p>Creating a python package for EvalAI which lets the participants to <code>import evalai</code> as a python package and then make submissions through their python script instead of logging in to the website and then doing it.</p> <h3>2. Submission Worker using SQS.</h3> <p>Currently, there are a lot of short-comings in the Submission worker like individual dependencies for Challenges which can be solved by switching to Amazon SQS.</p> <h3>3. Implementing RESTful web services.</h3> <p>Adding analytics, admin dashboard and API versioning to EvalAI.</p> <h3>4. Implement webhooks and data collection.</h3> <p>To retrieve the results of a challenge from some forked version of EvalAI to the main EvalAI server. Also, for adding integrations to external services using Slack, Gitter etc.</p>
<p><strong>EvalAI</strong> is an evaluation server that will host AI challenges like Visual Question Answering, Image Captioning. In recent years, it has become increasingly difficult to compare an algorithm solving a given task with other existing approaches. These comparisons suffer from minor differences in algorithm implementation, use of non-standard dataset splits and different evaluation metrics. By providing a central leaderboard and submission interface, we make it easier for researchers to reproduce the results mentioned in the paper and perform reliable & accurate quantitative analysis.<br> The task includes <strong>implementing RESTful web services for EvalAI</strong> which consists of <strong>building a news feed for the portal</strong>, <strong>implementing webhooks</strong>, <strong>creating dashboards</strong> for the participants as well hosts , <strong>setting up continuous deployment</strong>, <strong>writing unit tests</strong> to maintain its integrity and consistency and <strong>scaling it to large number of audience</strong>.</p>
<p>The Hurd is the kernel of the GNU system. It consists on the GNU Mach microkernel and several user-space servers that offer most of the functions that usually a kernel offers, one of these functions is a TCP/IP stack. Currently, in the Hurd this stack if offered by the pfinet server, a port of the Linux 2.2 TCP/IP stack. This stack should be replaced since it is obsolete and lacks important features like PPP support. In this project, we will port LwIP TCP/IP stack to the Hurd to replace pfinet.</p>
<p>While building software with Shaka, developers can import Player’s own user interface to receive bundled component classes that help them achieve a high-quality, accessible and localized experience.</p> <p>Natively, the library includes several configuration options, allowing applications to reach an ideal fit between the interactive aspects of the display and the intended content.</p> <p>This project aims to introduce enhancements for the options available in the user interface plugin, through the refactoring of existing components and the addition of new scalable interfaces, delivering a highly customizable experience for developers.</p>
Problem: VLC’s macOS interface has fallen behind modern design standards, creating a disjointed experience compared to its intuitive iOS/tvOS counterparts. The current AppKit-based UI lacks macOS Sequoia's visual polish, struggles with libvlc’s newer playback features (e.g., frame-accurate seeking), and suffers from inefficient media library management. This outdated design hinders usability and fails to make use of macOS’s native capabilities. Solution: Redesign VLC’s macOS interface using AppKit to implement a pre-approved, user-tested design that integrates into macOS visual aesthetics and libvlc’s advanced APIs. The overhaul will: 1. Replace legacy Carbon-era UI components with modern NSCollectionView and NSSplitViewController layouts. 2. Integrate libvlc’s latest playback controls (frame stepping, HDR metadata) into native transport UIs. 3. Rebuild the media library using Core Data for performance and NSDiffableDataSource for real-time updates. 4. Prioritize system consistency with SF Symbols, vibrant materials, and macOS accessibility standards. Deliverables: 1. Modern UI Components: - Unified toolbar with adaptive controls (NSToolbarItemGroup) - Redesigned media library with thumbnail grid (NSCollectionView) and smart filters (NSPredicateEditor) 2. Enhanced Playback: - Frame-accurate seekbar with NSSlider tick marks synced to libvlc’s next_frame() API - HDR tone mapping toggle using CAMetalLayer integration 3. Optimized Media Management: - Rules-based playlists backed by Core Data - Spotlight-like search using NSFetchRequest 4. Developer Documentation: - Migration guide for plugin developers - NSAccessibility implementation notes By collaborating closely with VLC’s core team and iterating on the existing codebase, this project will deliver a performant, native macOS experience that bridges the gap between VLC’s powerful engine and modern user expectations.
This project focuses on migrating JavaScript codebase to Typescript. Zulip is in the process of porting the main web app JavaScript codebase to TypeScrip. Zulip’s 8% of lines have been migrated while the goal for this summer will be to get that to ~75%. The challenges for migrating JS to TS include circular imports, a large number of interdependent modules, tracking down complex cycles, multiple cycles in one module, order of conversion, and understanding types and their relationships. The proposed solutions include classifying circular imports, passing callback workaround, extracting common functionality into a third module, and writing unit and integration tests to ensure the migrated codebase functions properly.
My primary focus for GSOC ‘22 at Zulip would be to enhance the UI/UX of the core Zulip Web Application. The web application UI is on its way to embrace modern design language while maintaining its solid performance and professional bug-free environment. I’m really excited to contribute to this initiative and put forward my efforts in making this proposal a success. I’ll be working on improving the UI/UX of the web application, implementing the redesign changes, making the CSS codebase maintainable and scalable, improving the Zulip settings and administrative pages, improving the accessibility, and working on improved markdown support. Besides this I’ll work on other high priority design, bug fixes and de-duplication issues, mainly in the front-end areas.
The Zulip messaging app currently relies heavily on JavaScript, which lacks certain types and safeguards for developers. To improve the experience and speed of creating modules, the project aims to migrate to TypeScript, which provides missing types and additional safeguards. In addition to the migration, improving the UI and Integrations of the Zulip Web App could bring significant enhancements to the app.
<p>Zulip Terminal is Zulip’s official terminal client, that provides a text-based user interface (TUI). The goal of this project is to improve the experience that Zulip Terminal provides. Some of the objectives include improving the user interface and experience around private messages, adding type annotations to all of the tests, improving the narrow model within the project, improving the current autocomplete for various features, and working on matching the general API expectations from the terminal client. This project would also include refactoring other related code to cleaner forms, enhancing the testing suite, fixing bugs that arise, and working on other miscellaneous issues.</p>
<p>This project's primary aim is to tackle high priority issues and features for the mobile app, Allowing users to be more in control of the zulip experience through their mobile devices. Currently from a user experience perspective notification functionality has a lot of potential to be improved and so I will dedicate a good part of my summer for improving this feature. Another key feature that many apps use today include deep linking which allows the app to open using web links directly on the screen the user desires. Besides other things, This will be useful especially with invite links. Lastly, and this is a much broader topic, I would dedicate my free time to work on clearing abandoned issues and just plain simple bug fixes, that will aim to keep the repository more clean.</p>
<p>Work have been focused upon:</p> <ul> <li>Refactor of code related to tests</li> <li>Cleaning up logging output and verifying it without printing in test output making CI test output clean</li> <li>Adding script to detect any unnecessary console output while running tests in CI</li> <li>Adding keyboard support for left and right sidebar popover menu.</li> <li>Making has:link, has:attachment, has:image work on client side.</li> </ul>