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.
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.
<p>I am interested in improving the general look of the site and its UI by working on Zulip's HTML/CSS/JavaScript, designing emojis for the chat, and making illustrations for various pages (landing/error pages, newsletter headers). I am excited to work on Zulip because the project is very eager to welcome beginners to Open Source and is interested in helping people grow-- I would be able to learn a lot by working with such a dynamic team. I believe this project would be able to showcase the importance of designers contributing to Open Source, demonstrating that spending a few months improving the front-end of a project can make it more appealing and easier to use!</p>
<p>This project will span multiple high-priority areas of Zulip, some of which include:</p> <ol> <li>Zulip has support for older versions of RHEL-based GNU/Linux distros. Moreover, CentOS is dead now. Recently I <a href="https://github.com/zulip/zulip/pull/17719" target="_blank">added support for Fedora 33</a>. I will work on adding support for newer versions of said distros and look into supporting Rocky Linux, which aims to replace CentOS.</li> <li>Zulip provides a great way to import data from other chat platforms, such as Slack. I will work on making the transition to Zulip smoother and easier.</li> <li><a href="https://github.com/zulip/docker-zulip" target="_blank">docker-zulip</a> has many production users. However, the project hasn't received the requisite attention. In this project, I will work on revamping the project and troubleshoot any issues that may arise. Zulip 4.0 will be released in a few days. I will work on having it work smoothly on docker-zulip.</li> <li>Apart from these, improving the existing developer tools, integrations to other third-party services, and testing infrastructure will also be a priority.</li> </ol>
<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>
For GSoC with Zulip, I aim to address completion candidate PRs, enhancing features and user experience. With a background in web development, I'll dedicate 25-35 hours per week over 12 weeks to tasks such as notifying users about unread messages, editing stream details, filtering users, customizing notifications, managing message moves, displaying profile images, adding anonymous polls, and allowing link preview removal. I'll leverage my skills and community support to deliver impactful contributions while prioritizing code quality and collaboration.
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's primary aim is to tackle high priority issues and features for the mobile app, Allowing users to be more in control of the zulip experience through their mobile devices. Currently from a user experience perspective notification functionality has a lot of potential to be improved and so I will dedicate a good part of my summer for improving this feature. Another key feature that many apps use today include deep linking which allows the app to open using web links directly on the screen the user desires. Besides other things, This will be useful especially with invite links. Lastly, and this is a much broader topic, I would dedicate my free time to work on clearing abandoned issues and just plain simple bug fixes, that will aim to keep the repository more clean.</p>
<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>Aims to improve the experience of using the application on both platforms by solving high priority issues related to how new/old messages are displayed, how unreads/different states of application are handled, and how notifications are displayed. The second part adds a slew of features previously only available on the web app like <code>linkifiers</code> and <a href="https://zulip.readthedocs.io/en/latest/subsystems/widgets.html" target="_blank"><code>Widgets</code></a>.</p>
The primary goal of this project is to improve the performance of Zulip, with a focus on the "upload" and "import/export" areas. Specifically, I will implement chunk file upload support for large-sized files and enable the direct importing of exports from other services via the web. Additionally, I will work on the images thumbnail part, Which currently places a significant load by downloading the full image.
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>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 improve existing data import tools, such as better conversion of Slack to Zulip features when importing Slack's data export, as well as starting new data import and mirroring tools for Discord.
My proposal aims to improve existing integrations of third-party services. Currently, some services only provide object ID in their webhook payload, not human-readable data. Some integrations also require users to download a script to be integrated, which is not ideal for non-technical users. To address these issues, I propose adding a proper callback system by extending the bot model and providing an additional UI for configuring the integration details. I also plan to improve several integrations by implementing newer features such as the proposed callback system and provide maintenance for ones with outdated payloads.
<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>
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>Improving Existing Settings and Administration UI by fixing this issues</p> <ol> <li>Add generic support for configuring organization default settings values for new users </li> <li>Delete a user </li> <li>Redesign Settings/users page </li> <li>Make the settings avatar delete/edit UI slicker 5.Dark mode: Date picker styling doesn't fit dark mode</li> </ol>
<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>
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.
This project aims to optimize the performance and scalability of many code paths in Zulip, with a focus on performance sensitive code paths like Zulip major endpoints which have request volume and cost that makes them important. The project also aims to design and implement a new feature of “LLM conversation summary”, and includes fixing issues in other areas.
<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>
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.
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.