Explore Projects

<p>The project consists of multiple pieces that incrementally add to the strength of the development and testing infrastructure.</p> <ul> <li>Address High priority tickets</li> <li>Bridge the gap between development and production</li> <li>Add mypy Django-stubs to utilize type annotations</li> </ul>

<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 proposal consists of bundles of projects aimed primarily at open source communities using Zulip along with various user centric features.</p> <p>They can be grouped as followed:-</p> <ul> <li>New notifications category and user muting options.</li> <li>Group default streams which caters to differing audiences.</li> <li>Make Zulip chat data more accessible and shareable.</li> </ul>

<p>My proposal is focused on making certain improvements in Zulip that are considered prioritary, with the goal of providing high-value contributions in consonance with the project's roadmap.</p> <p>Most of Zulip's REST API is currently undocumented, which is a pity considering how powerful it is. The first project in my proposal is to solve this by working in our <strong>Swagger/OpenAPI docs</strong> until we have a 100% documented REST API. The relevant code examples will also be updated so we can provide fully functional scripts that show how to use it, as well as extending our Python bindings to cover all the endpoints the API provides.</p> <p>The role that API keys play is also quite important, especially now that our integrations system is becoming more and more robust and we have many different clients for interacting with Zulip. That's why having <strong>multiple API keys per user</strong> could be very useful in terms of user account security and convenience. The second part of my project consists in implementing this feature in Zulip's backend, so normal users can have as many API keys they consider necessary (e.g. one per client), keeping authentication tokens isolated between applications.</p>

This proposal aims to make Zulip's stream and group management features easier to use. The project will focus on simplifying the way users manage permissions, organizing permissions neatly within the group settings, improving the process of creating streams, adding a new tab for exploring unsubscribed streams, allowing users to reset stream notification settings easily, and letting organization admins choose default colors for streams. These changes will help users navigate Zulip more smoothly and efficiently, making it simpler for them to manage their streams and groups. Ultimately, the goal is to create a more user-friendly User groups and Stream settings in Zulip

This project aims at general improvement of the Zulip web app by addressing and resolving many high priority issues related to compose box, modals etc. It also fixes many bugs that have persisted for a long time, and brings to completion some old issues and pull requests.

<p>Proposal for commited work over the summer, built on my already acquired experience and knowledge of the Zulip codebase - continuing my work on implementing PGP email features, addressing any current or future email mirror and rate limiter issues/TODOs (areas of the codebase that I'm most familiar with) as well as a couple of other interesting issues in other areas.</p>

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.

This project will focus on implementing a number of high priority features for Zulip web app focused around left sidebar and stream settings. This includes addition of new features, improving user experience and working across different areas if needed.

This proposal aims to improve Zulip integrations by making them more accessible and user-friendly. It introduces a backend permissions system to enforce bot access levels at runtime, the project replaces API key-based authentication with an OAuth 2.0 flow using django-oauth-toolkit. Additionally, it redesigns the integrations UI to use a “Add to Zulip” button which eliminates the manual bot setup. Together, these changes simplify integration workflows for non-technical users while making the integrations more secure.

In Zulip, each message has a sender (linked to UserProfile) and a recipient (referencing the Recipient model). The Recipient model supports three types: 1. Personal -- linked to a single UserProfile 2. Stream -- linked to a Stream 3. Direct Message Group -- linked to a DirectMessageGroup Currently, 1:1 direct messages use the Personal type that directly links recipients to individual users. This project aims to migrate them to use the Direct Message Group type instead. The migration should be seamless with minimal downtime. It involves: 1. Updating the codebase to support 1:1 DMs using DirectMessageGroup. 2. Running a backfill migration to create a DirectMessageGroup for each user pair with existing 1:1 messages. 3. Cleaning up legacy code and adding additional fields that are needed. This migration enables per-conversation settings for direct messages, and features like pinning or hiding DM conversations can be implemented more easily.

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

For my GSoC project, I wish to implement bigger full-stack features while continuing to investigate and fix bugs in the areas I'm familiar with. These areas include the settings panel, user Profile, compose box, popovers, message feed UI, and left sidebar. The issues I specifically aim to solve this summer are: - Unmute Topics within a muted stream - Add subscribe widget to user profile popover - Unsubscribed tab in stream settings - Make it possible to cancel uploads - Show empty conversation in left sidebar - Migrate manage user/bot to user profile - Special title and bug fixes for narrow titles. - copy drafts feature - Major bug fixes in user profile modal.

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.

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>The primary goal of this project is to automate setup and configuration for integrations and webhooks on Zulip’s end.</p>

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.

<p>The project is focused enhancing current "stream settings" features. Project also includes stream settings code refactorization and improving user experience with stream settings.</p>

The Primarily aim of this project would be to improve the overall UI/UX experience of Zulip users. Since last 2 months, I’m consistently participating in UI-redesign discussions on #design channel and I truly love the first draft proposal of UI-redesign of complete web application by Vlad Korobov, and would love to contribute in making it live! I would also like to work on some feature projects revolving around node tests, stream settings.

<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>The proposal for GSoC - Zulip aims to improve the overall experience of the Zulip web app by means of implementing full stack features such as <strong>send later feature</strong>, <strong>remind about message feature</strong>, <strong>clear status text after time feature</strong>, <strong>deny guest users access to other users</strong>, etc. I would like to see Zulip able to cater the needs of its growing user base by implementing features essential for a smooth and high-performance team chat system.</p>

The main focus of this project will be to work on various full-stack and frontend related features or issues like restoring drafts, adding a drafts tab for drafts in current narrow features, fixing invalid narrow API calls, and various other frontend related projects. I also plan to pick up some tooling related projects.

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