Explore Projects

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.

<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 project is aimed at migrating Zulip's existing JavaScript codebase to TypeScript. This includes creating precise types, refactoring inefficient code and increasing overall code readability.

<p>Work on backend and frontend of the areas Authentication, Settings(admin/org) and Settings(user), focusing on solving high priority and enhancement issues.</p>

<p>The Slash Commands act as easy-to-use shortcuts for specific actions, whereas widgets are interactive messages which enables Zulip users to interact with external and internal services directly from the messages. My main aim is to create a feature different widgets and slash commands for Zulip, and also work on the ephemeral message system "zgrams". Apart from this, my project also includes building a bridge between IRC and Zulip and Improving the current import/export infrastructure.</p>

Throughout the project, I want to focus on Zulip's native integrations and incoming webhooks framework by working on incomplete and pending features, fixing and enhancing integrations, and improving the user experience. I am willing to commit 40 hours per week over a span of 12 weeks, delivering high-quality, impactful contributions in this area.

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.

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

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

The Project aims at doing work on planned features around the UserTopic model. The other area I am planning to work on is API documentation. Zulip has a nice framework for writing API documentation based on the OpenAPI standard with built-in automated tests, but there are around 40 endpoints that are missing, several of which are quite important.

For my GSoC project, I wish to implement larger full-stack features while continuing to investigate and fix bugs in the areas I'm familiar with. These areas include the message feed, message editing, emojis, popovers, search, sidebars, settings, and invitations. The issues I specifically aim to solve this summer are: Dates should be “Jump to Date” buttons, Add a “Block a User” feature, UI for message reminders, Make read receipts always visible in direct message conversations, Limit who can resolve a topic to those who can post, Allow the deletion of items in a message’s edit history, Add a “Frequently Used” section to the emoji picker, Ensure the search filter updates with a single click when a filter is removed, and Indicate on the user card when an imported account has not been activated.

<p>Zulip Terminal is now being actively developed. Also, the user base for it has been steadily growing; but most of them only use it as a temporary client. So, this summer my goal would be to convert Zulip Terminal from being a temporary client to a primary client by implementing the necessary features.</p>

<p>The main focus will be on frontend-related issues particularly, compose features, message area, user interface. Besides that, I’ll work on fixing the issues labeled as bugs. I’m also interested in making the CSS more organized.</p> <p>The plan is to make the user experience more user-friendly and bug-free. Here is the current list of issues and features that I plan to complete in this project.</p> <ul> <li>Easy drag and drop of files so that users can instantly share files.</li> <li>Easily quote and reply "some selected small part of a message".</li> <li>Making the compose box a full-fledged editor with tools for easily writing messages using markdown.</li> <li>Making the experience of message failures easy to handle.</li> <li>Adding some more features and fixing various old-time bugs.</li> </ul> <p>It is highly unpredictable to guess what issues might come up later. So, the main outline will be to solve any new issue that might get opened later which is related to the frontend, compose box, message area with the ultimate goal of making Zulip much better than before.</p>

<p>Right now PRs have to be manually tested by commiters and some commiters aren't aware of new PRs at all. Also certain information like whether the PR is submitted by the port maintainer have to be checked manually.</p> <p>I plan to implement a bot in Go dealing with PRs for macports-ports and utilize Travis CI to test commits and PRs.</p>

This project will focus on improving Zulip web app and shipping new features. Deliverables focuses on zulip message system and permission settings but this will probably end up reaching wider areas of Zulip.

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.

<p>In this project, I will focus on the desktop(electron) project of Zulip. The major aim would be to fix up most of the high priority issues, polishing up the UI, refactoring code along with improving the current test suite and implement few of the required new features. It'd also incude actively respond to user issues and quickly suggest responses or implement quick fixes. My main aim is to make Zulip desktop app at par with the other major desktop apps and make it more user-friendly.</p>

<p>A MacPorts installation is designed to work with a particular OS and a particular hardware architecture. After major system changes like an OS upgrade or hardware change, currently, MacPorts users have to follow a set of manual migration instructions to ensure a smooth transition.</p> <p>The purpose of this project is to automate the processes described in the migration documentation, so that following the migration steps is no longer challenging for casual users or for anyone. The migration tool would install a new port command and using PortIndex, it would deactivate and reinstall the requested ports with variants.</p>

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.

<p>In this project I will add Python 3 support to Zulip, without breaking Python 2 compatibility. I will also add type annotation (see <a href="https://www.python.org/dev/peps/pep-0483/" target="_blank">PEP 483</a> and <a href="https://www.python.org/dev/peps/pep-0484/#suggested-syntax-for-python-2-7-and-straddling-code" target="_blank">PEP 484</a>) to all code.</p>

The main target of this project proposal would be to work on a Cluster of priority features, I will be working on improving existing features or adding new features which will be a high priority to complete in zulip-web. I am planning to complete this project with a clear discussion and well guidance from mentors.

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

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