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 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.
This project aims to implement a set of high-priority features in Zulip, focusing on improvements to the search filter and settings areas. On the search side, it introduces new filters such as `channels:all`, `channels:subscribed`, support for searching in multiple channels, and exact phrase matching. In the settings section, it proposes adding group-based, channel-level permissions for resolving and creating topics, along with a channel-level setting to enforce mandatory email notifications for users.
There are a ton of issues/feature requests open in the repository which must be implemented. Some of them even have pull requests with work already partly done, they just need a little more attention. I want to fix these problems and add the high priority features that people really want. This idea will have a main focus on the features related to the settings area with many features improving the user experience.
Zulip Terminal is a TUI-based Zulip client, this project aims to enhance the user experience of Zulip Terminal by integrating more features from the Zulip webapp. Focus areas include improving the test suite, interface enhancements, hotkeys, message rendering and refactoring code to cleaner forms.
For my GSoC project I wish to move onto implementing bigger full stack features, while continuing to investigate and fix bugs in the areas I’m familiar with, that is the compose box and the typeahead system. The issues I specifically aim to solve this summer are: - Paste URL to create a named link - Show profile pictures in search auto-complete suggestions - Use additional characters as separators for stream filtering - @mention lists should be scrollable - Add support for unmuting certain topics within a muted stream - Subscribing to topics within a stream for push notifications - Make it easier to insert numbered and bulleted lists - Create a UI for inserting polls
The main target of this project would be to work on migration to user groups for permissions which aims to replace every setting in Zulip that currently allows organizations to assign permissions based on role (admin, moderator, etc.) with a setting based on arbitrary “user groups”. I would majorly work on areas of settings and stream settings, migrating the existing settings to the new model and adding new settings based on the new permission model.
Zulip has a huge codebase for it's web app but it's currently written in JavaScript, this project is aimed at migrating at least ~80% of the zulip's codebase to TypeScript. TypeScript is an awesome language migrating to it will improve the quality, maintainability, and scalability of Zulip's frontend codebase. Also by using TypeScript we will be able to enforce consistent coding standards, document the code better, and leverage powerful IDE features.
<p>My primary targets for the summer are as follows:</p> <ul> <li>Solve issues across Zulip's message rendering pipeline.</li> <li>Assist in converting the Zulip webapp frontend codebase to typescript.</li> <li>Develop experimental features.</li> <li>Try to make Zulip's markdown easier to use.</li> </ul> <p>I've covered the above four points in detail inside my proposal.</p>
This project focuses on implementing a cluster of high-priority features in Zulip across the message feed, compose box, and channel settings. In the compose box, it introduces reply-without-quoting, collapsed recipient pills for DM conversations, and auto-pillify on blur. In the message feed, it adds always-visible read receipts for DM conversations, multi-message deletion, a "New Messages" divider, move-by-recency for topics, and completes the zulip-icon-at-sign rollout to mention pills. In channel settings, it adds group-level unsubscribe for channels and shows inherited permissions as uneditable pills. The work builds on existing patterns in the Zulip codebase and focuses on shipping well-integrated, user-facing improvements across these areas.
This project aims to mainly address issues and implement features and functionalities requested by users to make using Zulip's mobile app a more enriching experience. I will address 17 issues in the zulip-flutter repository over 350 hours, encompassing improvements to various aspects of the app, including but not limited to content parsing, message composition, API handling, tooling, and home view.
Zulip has over 120 native integrations, where many of these integrations still have bugs to be fixed and further improvements to be made. There are also new integrations that can be added which will benefit many users. On the backend side, there are multiple issues to be worked on, including but not limited to solving database deadlock bugs and optimising critical API latency.
This project proposal focuses on implementing a set of high-priority features in the zulip/zulip repository, specifically around enhancing channel-level settings and introducing support for creating and managing channel groups within an organization.
<p>This project will focus on high priority issues in the area of search. The project aims at maintaining a consistent user experience in terms of search and make the search process smoother for the user.</p>
My main objective is to implement on a cluster of priority features and complete some unfinished projects. I feel that these issues would greatly improve the utility and UX of the Zulip web app. I am familiar with many areas of the codebase, and have been exploring those which are relevant to the issues in the proposal. Same goes for the unfinished projects, some of which are my own from the previous year.
The current Alpha One Labs platform (alphaonelabs/website) is feature-rich but built on an older Django-based architecture, while the new alphaonelabs/learn repository introduces a modern Python Cloudflare Workers stack with an encrypted database model that is not yet fully complete. This project focuses on migrating all relevant features from the existing platform into the new Learn repository, while adapting them to the Workers based architecture and ensuring full frontend integration. Along with migration, the project will also strengthen the existing encryption model and ensure secure handling of user data within the constraints of the Cloudflare Workers environment. The goal is to build a fully functional, production-ready system that preserves core learning workflows such as courses, sessions, study groups and communication features. The migration will follow a structured approach starting from backend logic, then database integration using Cloudflare D1 and finally connecting the frontend for complete end-to-end user flows. Along with this, the system will be improved by modularizing backend services, removing unnecessary components and maintaining a clean, scalable and secure architecture for future development.
<p>Packit-as-a-Service is a GitHub App that helps developers continuously ensure that their project works in Fedora. Packit Service validates pull requests by building that project in Fedora so that others can install and test those built rpms before merging.</p> <p>A very barebones dashboard for packit-service exists. In this project, I want to convert it into a full-featured dashboard/information-center for packit-service. This is a twofold process. We need to properly build the API so that data can be retrieved from packit-service. Then, we need to use that data and build the dashboard itself.</p>
<p>The aim of this project is to create a framework that can help people create a web based demo out of their machine learning code and share it. Others can test the model without going into the implementation details. Usually testing models by other people involves a lot of preparation and setup. This project aims to cut that down.</p>
The proposal targets enhancing CloudCV by improving its admin dashboard, optimizing costs, and enhancing infrastructure monitoring. Key initiatives include developing EC2 admin actions, integrating Slack for streamlined challenge approvals, and automating resource management for cost efficiency and performance optimization.
<p>Release-bot helps upstream maintainers deliver their software to users, via automated releases at GitHub and PyPI. However, release-bot can be smarter in many ways. The workflow of the bot would be much easier if we create Github app and get rid of some bothering configuration. In the current state release-bot work with Github releases, one of the possible improvements is to extend functionalities for more git forges as pagure.io which is used by many projects in Fedora world. Also, release-bot can work with a single project at one time, let’s change it.</p>
<p>Packit (<a href="https://packit.dev/" target="_blank">https://packit.dev/</a>) project has native support exclusively for GitHub now. There were numerous requests from the community to add support for GitLab as well. So here we are - are you up for the challenge to implement support for GitLab in packit-service (<a href="https://github.com/packit-service/packit-service" target="_blank">https://github.com/packit-service/packit-service</a>) so that it can process events from GitLab API and return feedback of successful builds or failed tests back into the merge request? Please bear in mind that GitLab and GitHub use slightly different workflows (pipelines vs. external CI systems) so design work needs to be done before writing code.</p>
<p>Linux System Roles is a project related to Ansible, a tool for automating configuration management, application deployment and software provisioning. The goal of linux system roles is to provide a consistent user interface, abstracting from any particular implementation of the linux subsystems, but trying to get the most out of the particular libraries on each one of them.</p> <p>The Network Linux System Role, the one that aims to be improved in this proposal, currently provides a unique configuration interface for network-scripts and NetworkManager. This tool requires many improvements in several areas as it is a relatively new tool.</p> <p>In the proposal, all the issues are addressed, ordered from the tasks that the candidate considered to be better for the start in the project, to the ones that seems more challenging. The main goal of the summer will be to add Pytest support to the integration testing of the project.</p>