A CODEOWNERS management cli in Rust
CODEOWNERS parser in Rust, but GitHub's native CODEOWNERS feature handles 90% of use cases.

Sosreport collaboration tool, but ticketing systems already handle this workflow.
Linux support engineers and technical support teams
Splunk · Graylog · Jira Service Management
I'm a developer and 2nd level support engineer for many years for a Linux based appliance (the name of the product is not relevant for this post).
When I started in this position, I couldn't believe how customer technical support was handled (an eternal send me the output of this command, email-cycle) so I built a script to collect diagnostic data and an interface to explode the data and share it with the team.
Back then I didn't know about sosreport command (now sos) but it was very much alike.
Based on this experience, I decided to build sos-vault. A secure vault to store sosreports, manage them and more importantly, analyze them with your team.
I been working on this project for a while now and decided to provide it as a SaaS which has turned out to be not the best approach.
I'm currently working on a self-hosted open-source version based on the SaaS version.
Just login with you Google account and you will find a shared sosreport for you to look at and interact with.
If you have any question I'm more than happy to answer to the best of my ability. Any feedback is welcome.
Thank you all.
CODEOWNERS parser in Rust, but GitHub's native CODEOWNERS feature handles 90% of use cases.
Markdown files as database with 1000-token context summaries for AI assistants via MCP.
Figma-to-App-Store screenshot localization with one-click upload saves real workflow pain.
AI agents with approval gates for infra changes, but execution-oriented AI is still unproven in production.
AI photo analysis automates trade classification before dispatching to multiple contractors.
Heat profile breakdowns are clever, but AI recipe analysis is becoming commoditized.