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>Implements a Share extension to iOS and Android OS to ReactNative client Rocket.Chat.</p>
This project is a significant upgrade to Rocket.Chat message composer elements to provide users, AI assistance in writing messages using Context-sensitive spelling corrections, inline grammar correction recommendations, and clarity-enhancing rewording, Inline hinting are among the major features. The project also provides language translation, summarization, emoji, and tone control features. This project majorly improves the speed and clarity of message writing for users.
<p>The project Rocket.Chat.ReactNative is already about 2 years old and there are lots of features. So the chances of introducing new bugs by changing the existing code or adding new features are really high. And before each build the application needs a thorough testing to make sure nothing is broken.</p> <p>Currently project has some end-to-end tests for IOS platform but unfortunately no tests for Android. And also the Continuous Integration job on Circle CI with IOS tests is failing, the build stays always ‘red’.</p>
Joplin's offline-first design is one of its best features, but it comes with a real cost when the same note is edited on two devices before either syncs, Joplin has no way to merge the changes. It saves one version as a conflict note and leaves the user to manually figure out what to keep. For long notes on mobile, most people just give up and pick whichever version looks more complete, which means changes get silently lost. This project adds an interactive conflict resolution UI to Joplin desktop and mobile. When a conflict note is opened, instead of seeing a raw copy with no context, the user gets a clear section-by-section view of exactly what each side changed. Non-conflicting changes like additions and deletions can be resolved in one click. Genuine conflicts where both sides changed the same part give the user full context to pick one side or edit manually. A Keep both option preserves both versions for users who want that. The same shared diff module powers both platforms so the behaviour is always identical. The core deliverables are a platform-independent diff module using node-diff3, a minimal addition to the sync pipeline to store a base snapshot for three-way merging, and a conflict resolution React component for desktop and React Native component for mobile. The implementation also handles edge cases including notes synced before the feature was deployed falling back to two-way diff, stale remote data being detected and reset on open, and second conflicts on the same note being handled gracefully. No existing conflict behaviour changes and sync is never blocked at any point.
<p>Libraries for <a href="https://github.com/apple/swift-log" target="_blank">Logging</a> and <a href="https://github.com/apple/swift-metrics" target="_blank">Metrics</a>, embraced by the Serverside Swift Work Group, have enabled many Swift projects to simplify their code bases by removing their own implementations. However, there’s currently no official story for distributed tracing.</p> <p>This project aims to kick off the work on a distributed tracing infrastructure for the Swift ecosystem by creating a context propagation library with integration points for Swift NIO, AsyncHTTPClient, Swift gRPC, URLSession, and more.</p>
Implement full WAI-ARIA 1.2 screen-reader keyboard interaction models with localized calendar formatting.
Re-engineer the browser extension interface to display real-time normalized cache entity graphs and invalidation cycles.
Developing a native Swift-etcd client aims to seamlessly integrate etcd, a distributed Swift key-value store into Swift applications. This project aims to enable developers to have efficient communication with etcd servers via gRPC API, by targeting authentication, key-value operations, watch operations, and lease management.
<p>GreenNav project requires fast and reliable server that supports computations optimal routing via efficient algorithms. I'm going to implement RESTful server that communicates with the persistence layer for getting coordinates and effectively computes optimal way to the destination.</p>
<p>Design System React (short for Lightning Design System for React) is a react implementation of the Salesforce Lightning Design System, which an Open Source lightweight, high performance web component framework that powers thousands of apps. This project aims to extend and improve the DSR library, by implementing different design patterns from the SLDS as React components in DSR. The goal of this project is to help non-UI engineers implement highly interactive web applications with ease, by extending the variety of components that are available to them through the DSR library. Adding more variety of components will also help DSR to be useful for a wide range of applications, and make it a go-to React UI library.</p>
<p>This project aims to provide a web app that will enable a Joplin user to collaborate on a note in real-time. Joplin is a free, open-source note-taking and to-do application that can handle many notes organized into notebooks. The web app uses <a href="https://webrtc.org/" target="_blank">WebRTC</a> for peer-to-peer communication. The project also aims to create a <a href="https://www.webrtc-experiment.com/docs/WebRTC-Signaling-Concepts.html" target="_blank">signaling</a> server for the web app. For Real-Time collaboration and conflict resolution <a href="https://github.com/yjs/yjs" target="_blank">Yjs</a> is being used.</p>
<p><strong>Problem:</strong> Many users use Joplin for research purposes, so it is natural for them to do citations all the time. Accordingly, adding a feature that supports citations and BibTeX will be of great benefit to Joplin.</p> <p><strong>Solution</strong>: The solution can be described as a plugin that can do the following:</p> <ul> <li>Read from a source of citations (a <code>.bib</code> file).</li> <li>Allow the user to choose from a list of previously imported citations.</li> <li>Insert references into the note content.</li> </ul> <p>There are other requirements that must be met. For example, the UI should be as user-friendly as possible, automated and manual tests are to be carried out, every component of the codebase will have a documentation.</p> <p><strong>Implementation:</strong> The implementation relys heavily on Joplin's plugin API to do all sorts of things such as showing dialogs, accessing settings, and modifying content.</p>
To improve user experience and remove the need for manual downloads and installations, this proposal aims to automate the Joplin desktop application's update process. The main objective is to make sure that, for users of Windows, Linux, and macOS, the app updates without any problems in the background, downloading and installing the updates automatically when the program restarts. Investigating real-time updates and creating plans for updating files that are already in use are secondary objectives. For application updates, the project will make use of Electron and electron-builder together with TypeScript and React. Using Electron's autoUpdater module to manage downloads and updates, setting up a background service for silent updates, constructing a non-intrusive user notification system, and ensuring flawless application restarts for updates are important tasks. There will be testing and documentation at every stage of the development process. The timeline spans 14 weeks, starting with initial setup and planning, followed by developing the background update service, implementing the automatic installer and notification system, integrating and testing the updates across all supported platforms, and addressing any unforeseen challenges. The final stages will focus on finalizing documentation, polishing the update mechanism for deployment, exploring live updates, and project wrap-up with mentor review and project submission to Joplin and GSOC.
The APAP MCP server currently routes every tool call through an internal HTTP loop back to its own Express server, adding unnecessary latency, making MCP handlers impossible to unit test, and discarding all HTTP error context behind generic error strings. The MCP layer has zero automated tests and no client-specific documentation beyond a basic setup guide. This project introduces a shared service layer that both MCP tools and REST routes call directly via Drizzle ORM, eliminating the HTTP round-trip. Structured error types replace generic strings with machine-readable codes and HTTP status preservation. Deliverables: 1. Shared service layer refactor with structured error types across all 8 MCP tool handlers 2. Four-tier test suite (unit, integration, contract, E2E) with 90%+ coverage enforced in GitHub Actions CI 3. Client-specific tutorials for Claude, ChatGPT, and MCP Inspector 4. Developer experience improvements: Docker Compose quickstart, Pino structured logging, /healthz endpoint, and updated CONTRIBUTING.md A working proof-of-concept implementing the core refactor with 53 tests and 98.55% statement coverage is already live at github.com/JayDS22/apap-mcp-poc.
The proposed project aims to build a lightweight, scalable, and extensible alternative to the Snowstorm Terminology Server by leveraging Django and etcd—a fast, atomic, and consistent key-value store—as the backend database. Unlike Snowstorm, which is resource-intensive, limited to SNOMED CT, and does not support concept authoring, the new server will support full FHIR operations like $lookup, $validate-code, and $expand, along with custom endpoints for authoring, updating, and deleting concepts. Data will be loaded into optimized in-memory data structures (DAG and description dictionaries) on server startup, enabling fast traversal, search, and filtering. Multi-language support, real-time syncing from etcd, and an intuitive micro-frontend UI will allow users to manage codes seamlessly. The project also includes full integration into the existing Care ecosystem via a dedicated backend plugin and a React-based admin dashboard, ensuring drop-in replacement with no changes required in existing workflows. This solution will empower open-source healthcare platforms in resource-constrained regions to build, customize, and manage terminology services without relying on costly proprietary systems.
<p>Joplin desktop application supports keyboard shortcuts to a certain degree. However, it doesn’t allow users to configure keyboard shortcuts according to their preferences. Custom keyboard shortcuts would be a great addition for all Joplin users including power users and those who are migrating to Joplin from other note-taking applications. People also do not have the same keyboard layout; not everyone has F6 necessarily. It would solve conflicts between different preferences of workflows, and increase discoverability for all keyboard shortcuts.</p>
Most Joplin users are researchers or workers in different fields. It's usually the university or company dealing with them via email, whether it's assignments, essays, or reports, so I built a plugin to add the ability to fetch email messages (including attachments) and convert them to Joplin notes in various formats, either by monitoring any new or unread messages from a specific email address or a specific mailbox by using IMAP or by uploading downloaded email messages to the plugin without having to be logged in.
<p>I propose creating a plugin for Joplin, which allows notes in a notebook to be organized in a kanban board. The board itself is a special type of note, which, when opened will show the kanban interface in a new panel. On the board each item is a note and each column is a tag or some other property of the notes. Dragging notes between columns updates their properties automatically. On mobile and on clients which don't have the plugin installed, the board note simply shows as a static markdown table, so that tasks can still be viewed.</p> <p>This proposal draws from the discussion in <a href="https://github.com/laurent22/joplin/issues/3567" target="_blank">this GitHub issue</a> and <a href="https://discourse.joplinapp.org/t/kanban-for-tasks/7342/4" target="_blank">this forum thread</a>, especially uxamanda 's designs and ideas. Big thanks!</p>
Being cross-platform and able to sync notes are crucial features of a note-taking app which Joplin implemented very well. Currently, Joplin is on these platforms: desktop, mobile, and terminal, it would be best to separate the current Joplin synchronizer as a standalone syncing library. Such re-implementation can decouple the ecosystem, and allowing more user control over the syncing process. Porting current Joplin's synchronization modules to a separate library. Integrate with some Cloud Providers: Onedrive, Dropbox,... Exposing services to allow more control over syncing process. Adding unit & integration tests for new library.
Joplin’s end-to-end encryption protects notes during sync, but not on the local device. This project adds local note encryption so users can lock sensitive notes behind a vault password while preserving compatibility with sync and existing E2EE. The implementation will use an option-gated save/load flow, on-demand decryption, protection against plaintext leaks through search and revision history, and a lock screen UI for desktop. Guaranteed deliverables are a working desktop implementation, vault password management, sync/backward-compatibility support, and tests for data-safety and conflict handling. Stretch goals include mobile support, resource encryption, and CLI/Data API integration.
Plugin plays an important role in the Joplin community. As there are more and more plugins it would be good to improve how they are discovered and to improve search - in particular, improve search relevance. To optimize the plugin discovery process, two things need to be done. Firstly, we need a plugin website that allows users to find and download the plugin. Secondly, the built-in plugin search function needs an upgrade to provide detailed information and improve search relevance.
The Joplin desktop app currently uses native built-in PDF renderer of electron to display PDF attachments, this has multiple limitations like lack of ability to link to a specific page number, loss of scroll position state on re-rendering, annotations etc, not to mention the built-in renderer’s UI does not match with rest of the Joplin app. The aim of this project is to replace the built-in PDF renderer with a new 3rd party library and add multiple new pdf related features and improvements to the app.
<p>Joplin had a templates feature in the main desktop application that enabled users to create templates and reuse them to create new notes and to-dos.</p> <p>Also, Joplin has an awesome plugin architecture that can be used by developers to create plugins that can extend some functionality to the desktop application.</p> <p>My project was to re-package the feature as a plugin and remove the feature from the main application while ensuring that all the existing templates are compatible with the new plugin and users have a smooth transition to the plugin.</p> <p>The main goal of this project always was to enhance the template system. Also, making it a plugin had various benefits like better maintainability, better scope of improvement, etc.</p>