Explore Projects

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.

<p>To make Zulip's terminal application as robust as it's web counterpart I will be working on the following enhancements:</p> <ul> <li>Improve typeaheads ( auto-complete )</li> <li>Improve streams handling by adding abilities to mute topics, edit topics, and pin streams</li> <li>Visual improvements</li> <li>Viewing message edit history, handling links in messages and adding reactions to messages.</li> <li>Reviewing and working on old PRs</li> <li>Refactoring code</li> </ul>

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>This project will focus on solving several of the high priority issues related to the general user experience of Zulip. This would involve improving the user interface in some areas, adding requested features in some places, as well as fixing some areas where the behavior is not as expected. All of this, in the hopes that it would improve the feel of Zulip for existing users and make it easier for new users to adopt.</p> <p>Though it was not intentional, several of the issues to be tackled here are requests made by large communities as their major blockers to switching over to Zulip. This project consists of work that goes over a few areas, broadly, these could be clumped together as the following goals:</p> <ul> <li>Info density enhancement requests.</li> <li>Public streams and guest user support.</li> <li>Better support for appearance and interaction of muted streams.</li> <li>Misc UI improvements.</li> <li>markdown processing improvements.</li> <li>search behavior improvements.</li> </ul>

<p>The project aims to use RocksDB persistent storage as a state back-end for Jet batch processors that require large state and don't need cutting-edge throughput such as joins and aggregations.</p>

<p>The <strong>telemetry (or Phone Home)</strong> is a hazelcast feature that lets us gather usage information about how the community uses the Hazelcast product. Currently, it collects only the minimal information, including the <em>hazelcast version, java version, operating system, uptime, memory used, number of clients, number of clusters, etc.</em></p> <p>The ultimate goal of this project is to give a fine-grained view to this by collecting detailed usage information about the Hazelcast features being used actively by the community. For this, we need to collect various metrics of several data structures provided by the hazelcast and of the cloud configuration used for the deployment of hazelcast. The Phone Home of the hazelcast gathers this data daily, which will continually help to enhance the hazelcast product.</p>

<p>The project primarily focuses on working in the Message view area. They are adding configurability for stream typing indicators, adding read receipts and work on several other high priority projects.</p>

<ul> <li>Fix quality-of-life issues in the frontend</li> <li>Migrate the frontend to TypeScript</li> <li>Start the process of rebuilding the Zulip web UI in React</li> </ul>

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.

In my proposed project i plan to tackle some issues in the left sidebar. Specifically, i want to add the possibility to filter the recent topics by stream, i want to add a UI to view scheduled messages and i want to make it possible to convert personal messages to public topics.

Zulip Terminal (zulip-term) is a TUI based Zulip’s client, powered by Python module urwid. As mentioned in the proposal, I will be doing the following: handle updates of user data, migration to server version 2.1 and improve the search feature

This project aims to implement high-priority features in the 'Zulip server and web application' project, focused around topics and notifications (messages) areas. The issues I specifically aim to solve this summer are: ➔ Implement 'Follow a Topic' feature ➔ Develop @topic mention feature

<p>For Zulip Desktop:</p> <ul> <li>Quicker Response to Customer Issues</li> <li>Multi-Server Login</li> <li>Centralized Preference Panel</li> <li>Adjustments on Different OS Versions</li> <li>Testing</li> </ul>

<p>Main focus of my project would be to enhance the overall user experience of Zulip by adding some new features and also updating existing features which includes a wide range of organization permissions and settings, search realalted features, stream settings and a couple of onboarding features too.</p>

<p>The current react native project runs great for iOS but a little buggy for Android. I intend to make it more robust, easy to use by implementing a plethora of new features like a new compose message layout/action system, push notifications, drafts screen, settings screen etc. while fixing most of the bugs to make the project near perfect before my program ends.</p>

This project will include implementing cluster of new features, fixing existing performance or functional bugs and adding new testing infrastructure that will progress the Zulip Flutter app towards Launch, which is currently in Beta. Some of the features that I look forward to implement are video previews, Android inbox-style & conversation notifications, ASWebAuthenticationSession on iOS for webauth, Table message content, handling more server events.

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.

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

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>With its innovative threading model and robust web app, Zulip has received a lot of praise from remote teams that use it. While the desktop app is certainly complete in terms of features, it needs some polish and certain standout features to make it an obvious choice for a Zulip user to install. In this proposal, I suggest the implementation of multiple features like enterprise deployment, an updated server validation logic, migration to another database, and a resource manager to improve the overall performance and stability of the app.</p>

This project aims to implement high-priority features in the Zulip server and web application, focusing on message editing and settings. In message editing, the project aims to add support for moving messages by recency, improve permission checks by hiding specific message move options when not allowed, refine how message move history is displayed, and enable deleting items from a message’s edit history. In settings, the project aims to introduce group-based, per-channel permissions for those who can create and edit topics to give organizations better control over channel permissions.

<p>This project aims to revamp the Recent topic view with the addition of Multiselect Dropdown List Widget within Zulip frontend and to enhance it by providing better control over recent feed, allowing them to filter by topic unread count and stream unread counts.<br> This is an essential feature for users within large organizations assisting users to read only specific topics they are interested in and sort by unread topics that they are not caught up with.<br> The proposal also takes into consideration of reusing specific widgets across various areas (most likey, Settings and Message edit) which can potentially enhance the UI and minimize the user's effort in achieving the desired task.</p>

The project involves implementing a cluster of priority and user requested features: 1. Adding search operators for date and supporting new functionality in existing operators such as searching from multiple channels. 2. Copy and paste enhancements 3. Compose validation 4. User mention pills, markdown and typeahead support in /todo widget 5. Features around User groups 6. Adding new APIs and modifying existing ones. 7. Integrations around Zendesk, Vercel and GitLab. 8. UI improvements related to the extended stream description 9. Message reaction narrow and notifications for reactions. 10. Selecting multiple messages to perform bulk-delete, bulk-move operations.