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.
<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>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>
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.
<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>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>
<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>
This project aims to implement a set of high-priority features in Zulip, focusing on improvements to the search filter and settings areas. On the search side, it introduces new filters such as `channels:all`, `channels:subscribed`, support for searching in multiple channels, and exact phrase matching. In the settings section, it proposes adding group-based, channel-level permissions for resolving and creating topics, along with a channel-level setting to enforce mandatory email notifications for users.
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.
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>Adding a completely new Notification Panel for the Web app. Additional work on miscellaneous features, UI changes and relevant test suites.</p> <p>Major bug fixes for the LDAP Integration. Also, added and improved the test suite for it.</p>
This project proposal aims to implement a cluster of priority features in zulip/zulip related to the settings system and write API documentation for various endpoints.
For my project with Zulip, I propose to elevate the platform by finalizing and expanding incomplete features, enhancing webhook integrations, and resolving existing issues. I will commit 25-35 hours per week over the 12-week project period to deliver impactful, high-quality improvements, including creating configurable navigation views, enabling administrators to reset user settings, addressing integration bugs, adding new integrations, and strengthening the integration framework. Throughout, I'll leverage my skills and community support to deliver impactful contributions while prioritizing code quality and collaboration.
<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>
<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>
Zulip has a huge codebase for it's web app but it's currently written in JavaScript, this project is aimed at migrating at least ~80% of the zulip's codebase to TypeScript. TypeScript is an awesome language migrating to it will improve the quality, maintainability, and scalability of Zulip's frontend codebase. Also by using TypeScript we will be able to enforce consistent coding standards, document the code better, and leverage powerful IDE features.
This GSoC project aims to significantly enhance the user experience of Zulip, an open-source team chat app, by implementing several features that will improve the user interface and usability of the application. The project will specifically focus on redesigning crucial areas of the application, including the top bar, sidebars, Compose box, and Topics, to make them more intuitive, user-friendly, and visually appealing.
<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>
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.
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.
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>The primary aim of this project is to make enhancements to Zulip’s REST API Documentation framework, which allows writing API Documentation based on the OpenAPI standard with built-in automated tests.<br> Major tasks include modifying the framework and testing to allow generating API pages directly from OpenAPI data and removing the redundant templates, and adding support for auto-generated API bindings by integrating different tools into the framework.<br> The docs will also be visually enhanced by improving the organisation and UI of /register and /events endpoints, and /api pages in general. This would include major design changes to the documentation pages to improve the overall user experience. Further, the OpenAPI data for currently undocumented /api endpoints will be added to improve the endpoint coverage by the docs.<br> This project would also involve fixing the currently open issues related to API Docs area, majority of which improve the testing of OpenAPI data, as well as making various API migrations with appropriate updates in OpenAPI data. Also, improvements would be made to the organisation of OpenAPI data and its testing/error messages to make it easier to maintain and work with.</p>
<p>The project aims at making the logged out pages more attractive by improving the visual design, adding illustrations and making a consistent design across all pages. Furthermore, CSS refactoring to SCSS nesting will be done. In the end, a presentation video of the Zulip system will be done, which is a nice to have on the website.</p>
<p><strong>Zulip Terminal</strong> (<strong>zulip-term</strong>) is a TUI based Zulip’s client. It targets a niche group of users who like to work primarily from their terminal. For the summer, my goal would be to bring the Zulip Terminal’s experience closer to the web app. At least, to the extent where a user would not have to switch to the web app frequently. In addition to this, the aim would be to improve the code and test suite, test coverage and work on other issues that may come into the picture with the course of time.</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>