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.
Zulip Terminal is a TUI which caters to users who use Zulip through their terminal. But, many functionalities in Zulip Web App are not currently implemented in Zulip Terminal. The features/areas this project will focus on are a) Achieving the same level of notification functionality as Web App. b) Add the feature of file upload along with other related issues. c)Support muting/unmuting of users d)Support Alert-Words. Most of the issues need work on multiple areas such as event handling, UI changes/additions, Migrations etc.
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>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>
There are dozens of issues and features to be implemented in the issue trackers. As well as a bunch of pull requests that have quality work done already, but just requires a bit of revival. We want to cut down on these issues and implement highly requested features from the community.
<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>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>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 aims at general improvement of the Zulip web app by addressing and resolving many high priority issues related to compose box, modals etc. It also fixes many bugs that have persisted for a long time, and brings to completion some old issues and pull requests.
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>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>
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>Very often even if an application has a robust backend, the user interface is often the factor that decides whether it will be taken up or not by the end user. Or in other words, apps definitely get points for being pretty. The Zulip mobile application can be regarded as a work-in-progress. I shall work the on the following areas and improve it so the application may move closer towards completion.</p> <ul> <li><p>Overhaul and rebuild several major elements of the interface to achieve a more even, symmetric and uniform look.</p> </li> <li><p>Adopt principles of Material Design for the application.</p> </li> <li><p>Fix many small but annoying issues such as broken alignment in some menus, ripple and other effects overflowing into other elements, non-standard icons, animation delays, asymmetric margins etc.</p> </li> <li><p>Improve support for different resolutions and pixel densities so nothing is out of place on a 18.5:9 or 18:9 display, or in landscape mode.</p> </li> <li><p>Add to the documentation and improve it where possible.</p> </li> </ul>
The Zulip community has been actively requesting improvements to video call functionality and Atlassian integrations, and addressing this cluster of features would meaningfully expand Zulip's appeal for organizations that depend on these tools. On the video call side, I will implement a Google Meet provider, help take a native LiveKit integration prototype to a mergeable state, build a cold-call ringing experience and add support for multiple simultaneous video call providers per organisation. On the Atlassian side, I will implement a bidirectional Jira integration extending the existing webhook with richer filterable notifications and outbound actions (comment, assign, change priority) directly from Zulip, and a new Confluence incoming webhook integration covering the full page and blog lifecycle. All deliverables include full test coverage, API documentation, changelog entries, and help center articles. The work builds directly on my existing merged and open PRs in Zulip's video call and Atlassian integration areas.
<p>My proposal describes my approach of how we could implement a Zulip incoming webhook API that allows Slack to post into Zulip with the additional goal of further integrating as many of Slack's own third-party integrations as possible.</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>
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>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>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>
<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 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>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>
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.