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 implement a handful of issues in the zulip-flutter repository to make it ready for the launch milestone. This will be a large project (350+ hours) with 25 issues planned for now, but most probably this number will fluctuate based on the feedback from the mentor(s). These issues are related to various areas in the Zulip Flutter application such as compose, message list, model, API, setting, and home. In my initial contributions, I have already addressed some issues related to different aspects of the app, i.e., inbox, compose, and message list. This has given me a relatively firm grasp of the project and I feel confident enough to complete the selected issues.
This project aims to optimize the performance and scalability of many code paths in Zulip, with a focus on performance sensitive code paths like Zulip major endpoints which have request volume and cost that makes them important. The project also aims to design and implement a new feature of “LLM conversation summary”, and includes fixing issues in other areas.
<p>Zulip-terminal is the official terminal client for Zulip which has been actively developing for the past few years and has already reached a certain level where it’s no longer considered a temporary client. It still has a long way to go to match the level of web-app, in terms of feature enhancements. So, my primary objective this summer would be to provide more feature support to Zulip-terminal and improve upon the existing ones by fixing bugs and potentially adding and improving upon the test suite. Some of the highlights of the work that I'll be doing:</p> <ul> <li>Adding support for Alert word handling. (events and UI)</li> <li>Improving zuliprc location/specifying.</li> <li>Adding support for specifying custom key-bindings</li> <li>Adding support for cross-platform notifications.</li> <li>Message rendering and event handling improvements.</li> </ul>
<p>My first project aims at building a GitHub Action, for optimizing various GitHub related workflows, which will not only help the maintainers in managing and monitoring the issues and pull requests across their repositories much more efficiently but will also help the contributors by providing them with a better workflow while they contribute to your projects, like allowing them to self-assign issues, label PRs, notifying them of merge conflicts, inactivity, and issues/PRs opened in their area of expertise and much more. All this will be available with the ease of just adding a few workflow files to your repositories.<br> This action is based on Zulipbot, which was built by Zulip a few years ago.</p> <p>My second project aims at building a data migration tool for organizations who wish to move their teams, along with all of their data, from Rocket.Chat to Zulip.</p>
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 solving several high priority issues related to the Installer and Tooling of Zulip. It mainly aims to add strength in the developing and testing experience.</p>
<p>Add different level of user authentications in streams, improve stream creation flow in UI and add new option to make creation of incoming webhook more user friendly.</p>
<p>My primary objective of this project would be building an efficient electron test suite (e2e and karma unit tests), Revamping the UI including some color scheme and font, completing the migration of the database to LevelDB, removing and replacing deprecated request module (and others) setting up a git commit linter and improving the user experience by adding necessary features.</p>
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.
<p>This project will span multiple high-priority areas of Zulip, some of which include:</p> <ol> <li>Zulip has support for older versions of RHEL-based GNU/Linux distros. Moreover, CentOS is dead now. Recently I <a href="https://github.com/zulip/zulip/pull/17719" target="_blank">added support for Fedora 33</a>. I will work on adding support for newer versions of said distros and look into supporting Rocky Linux, which aims to replace CentOS.</li> <li>Zulip provides a great way to import data from other chat platforms, such as Slack. I will work on making the transition to Zulip smoother and easier.</li> <li><a href="https://github.com/zulip/docker-zulip" target="_blank">docker-zulip</a> has many production users. However, the project hasn't received the requisite attention. In this project, I will work on revamping the project and troubleshoot any issues that may arise. Zulip 4.0 will be released in a few days. I will work on having it work smoothly on docker-zulip.</li> <li>Apart from these, improving the existing developer tools, integrations to other third-party services, and testing infrastructure will also be a priority.</li> </ol>
<p>The current android version of Zulip is little bit outdated and has some performance issues as well as it is using the old libraries. I will implement new designs as shown in the UI Design's and will use the new libraries for the internet activities which would definitely enhance the performance of the app.</p>
My project aims to contribute to the launch of Zulip's new mobile app by addressing issues identified during the beta phase to ensure a high-quality final product. The primary focus areas include enhancing the Zulip-Flutter project and reaching the summer-beta milestone. I propose a flexible 12-week timeline to accommodate Zulip's evolving requirements and priorities, ensuring alignment with the project's goals and mentorship guidance. By the end of the project, my objective is to support the successful launch of the mobile app and lay a solid foundation for ongoing enhancements.
The primary goal of this project is to improve the performance of Zulip, with a focus on the "upload" and "import/export" areas. Specifically, I will implement chunk file upload support for large-sized files and enable the direct importing of exports from other services via the web. Additionally, I will work on the images thumbnail part, Which currently places a significant load by downloading the full image.
This proposal aims to improve existing data import tools, such as better conversion of Slack to Zulip features when importing Slack's data export, as well as starting new data import and mirroring tools for Discord.
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.
There are dozens of issues and features to be implemented in the issue trackers. As well as a bunch of pull requests that have quality work done already, but just requires a bit of revival. We want to cut down on these issues and implement highly requested features from the community.
Notably, the project will focus on integrating django-stubs along with working on other general typing enhancement projects and porting JavaScript to TypeScript in the frontend. Apart from the type checking aspect, I will also work on side tasks for API, bots and integrations.
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.
<p>To improve existing features and add new features, to create a more robust and agile version of web version of Zulip which can handle large teams. A user will be able to use it more intuitively.</p>
<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>
Zulip has a vast library of native integrations, functioning through webhooks. Since this integrations subsystem relies heavily on third-party information and communication, there is a lot of scope to strengthen and secure the sub-system through improvements such as validating incoming webhook data via improving type annotations and handling, verifying webhook signatures/integrity, and documenting missing/incomplete webhook functionality. This project would also include the addition of more integrations quickly and efficiently based on issues raised, to make Zulip more helpful to teams irrespective of the tools and applications they use. Another important aspect is improving the existing webhook event-filtering system and generating documentation for it appropriately. This project would also monitor and keep this subsystem updated with developments in the incoming webhooks.
The main goal of this project is to improve the user experience of Zulip Terminal, a TUI that caters to Zulip's terminal users. My areas of focus are enhancing hotkeys, centralizing configuration and event handling improvements.
Zulip Terminal has TUI which caters to users who use Zulip through their terminal. But, there are many functionalities in Zulip Web App that are not currently implemented in Zulip Terminal. Some of the major functionalities that I would love to see in Zulip Terminal are to improve stream sorting similar to Zulip Web App, improve topic muting and moving across streams, add support for muting users, and UI/UX improvements based on Zulip Web App. The above improvements have been proposed in my GSoC proposal.