{
  "id": 9294288,
  "title": "From Zero to 3 Merged PRs: Contributing Python CLI Recipes to BasedHardware/omi",
  "url": "https://urgent.news/2026/09/23/from-zero-to-3-merged-prs-contributing-python-cli-recipes-to",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-09-23T07:39:54.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/elvingts/from-zero-to-3-merged-prs-contributing-python-cli-recipes-to-basedhardwareomi-50lp"
  },
  "original_language": "en",
  "account": "Over the past few weeks, the author has been contributing to the open-source AI wearable project BasedHardware/omi. Three pull requests have been officially approved and merged into the main branch by core maintainers and Omi's founder Nik Shevchenko. This article provides a brief overview of the projects, the lessons learned, and the next steps.\n\nThe trio of Python CLI Recipe projects were all focused on making it easy for Omi users to export and structure their conversational data without using complex setups or external dependencies. The first recipe, PR #13701, converted raw conversation JSON dumps into Markdown that works with Obsidian, Notion, and local notes. It handled UTF-8 character encoding and atomic file writing to prevent corrupt exports.\n\nThe second recipe, PR #14458, exported Omi's memory stream, organizing insights by date and category tags. The third and most rigorous recipe, PR #13960, extracted action items and checklists into formatted task lists. This recipe was subjected to thorough testing, with 9 comprehensive unit tests written in Python’s standard unittest library that all passed in just 0.05 seconds.\n\nThree key engineering lessons were taken away from the experience. Firstly, relying on Python's standard library over third-party libraries is always beneficial. This avoids dependency bloat and eliminates potential breaking changes across user environments. Secondly, constructive feedback from maintainers should be welcomed, as it serves as mentorship that can improve the code. Lastly, maintaining a clean and atomic Git history is crucial for simplifying the review and merge process.\n\nLooking ahead, the author plans to expand these recipes to support direct third-party REST API payloads, such as Todoist tasks and Notion blocks. Participating in active AI hardware/software projects is a fast way to enhance real-world software engineering skills. The author invites readers to share their experiences with contributing to open-source projects and what they have learned from working with repository maintainers.",
  "summary": "Over the past few weeks, I’ve been contributing to BasedHardware/omi , the open-source AI wearable project. As of this week, all three of my pull requests have been officially approved and merged into main by core maintainers and Omi's founder Nik Shevchenko ( @kodjima33 ). Here is a quick recap of the journey, the recipes built, and 3 key engineering lessons learned along the way. 🚀 What We…",
  "key_points": [
    "Three Python CLI Recipe pull requests merged into main branch",
    "Recipes converted data to Markdown, memory stream, and task lists",
    "Author learned to rely on Python's standard library and welcome feedback"
  ],
  "editors_take": "The author's contributions to BasedHardware/omi showcase the value of relying on Python's standard library and embracing maintainer feedback to create robust, dependency-free code that benefits open-source projects.",
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}