Explore Projects

<p>Project mainly involves working on authentication issues and other backend issues along with replacing CasperJS tests with Puppeteer. It also includes clearing TODO's in the area's I'm familiar with.</p>

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

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>Through this project, I wish to improve the chat-ops capabilities of Zulip by adding support for slash commands and outgoing webhooks. Outgoing webhooks are integrations which send data to third party services from Zulip on being triggered. Slash commands enable users to make use of services through chat messages. Example: change topic, archive messages, etc. I wish to build an outgoing webhook system which will enable users to easily add outgoing webhooks into their Zulip realm through UI. Users can also use their own code by adding it to the codebase for complex uses. I also wish to add support for slash commands which can be enabled, disabled and managed by users.</p>

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

This project focuses on enhancing the Zulip platform by implementing key user-centric features across the message feed, editing system, APIs, and test coverage. The proposed work includes adding a user blocking feature, always-visible read receipts in direct messages, improved message edit history controls, and bulk conversation management in the inbox. It also introduces backend improvements such as APIs for deleting user messages during deactivation, configurable mention permissions, and detailed audit logging. With prior experience contributing to Zulip, I aim to deliver scalable, well-tested solutions that improve usability while actively collaborating with the community throughout the project lifecycle.

<p>The first part of this project involves improving certain parts of Zulip's webhooks/integrations system.</p> <p>1.Make it much easier to quickly and conveniently test any incoming webhook integrations. This will make things a whole lot easier for developers creating or reviewing new bots. I plan on creating a web-based GUI for this purpose.</p> <p>2.Enable us to store the headers for each sample payload alongside their fixtures. But at the same time allow them to be dynamically generated (instead having them necessarily be fixed/static).</p> <p>3.Allow user's to configure their incoming webhooks bots based on certain parameters that we can specify on an integration-per-integration basis.</p> <p>4.Create a systematic and convenient way to allow integrations to make a callback request to a third-party API to gain extra information about events as required.</p> <p>5.Making miscellaneous improvements and tweaks that pop up over the course of the summer to specific integrations. Add new integrations as needed.</p> <p>The second part of this project involves improving Zulip's OpenAPI documentation system (the supporting code and tests, not necessarily writing the actual documentation itself).</p>

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

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

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

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

<p>Proposal proposes <strong>TypeScript migration</strong> for type-checking. Switch from Casper to <strong>Puppeteer</strong>. Lastly, high priority zulip features like <strong>Report Spam, Font Size</strong> that are requested by users.</p>

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>A tool for the Managers and the contributors to proposal/edit/approve changes as per fedoras change process.</p>

<p>Revamp the interface design according to the community standards and craft a better user experience for the Fedora Community application.</p>

<p>Complete support for <a href="https://github.com/openshift/origin" target="_blank">OpenShift</a> and <a href="https://github.com/kubernetes/kubernetes" target="_blank">Kubernetes</a> as a backend in <a href="https://github.com/fedora-modularity/conu" target="_blank">conu</a></p>

<p>This project involves fixing the last remaining kinks in the EvalAI UI. The goal of this project would be to improve the new UI as we replace the existing UI with the new UI. We will be improving on the new UI and incorporating the feedback we will receive from the challenge hosts and participants for the AI challenges organized this year.</p>

<p>This project involves building a webapp to replace the current user onboarding flow for centos.ci.org</p>

<p>As the number of challenges on EvalAI are increasing, we want to focus on improving the performance of our services. As a first step, we will focus on monitoring and measuring all the key metrics of our services. Insights from these will allow us to efficiently utilize our infrastructure, improve uptime and reduce costs. The project will concentrate on setting up metric reporting and alerts infrastructure, writing REST API’s, plotting relevant graphs and building analytics dashboards to help EvalAI admins maintain and monitor the services.</p>

<p>pkgs.fedoraproject.org is a place which hosts about 17k git repos for rpms. Presently, it uses cgit. But, we do have Pagure for hosting git repos. After addition of few more features, we will be able to host pkgs.fedoraproject.org on a pagure instance. It will make pagure even more flexible software for hosting git repos and sharing code. I am sure project maintainers of pkgs.fedoraproject.org will like the change.</p>