My First OSS Contribution as a Non-Developer: What I Learned and Why It Matters

Francois Altwies — Sat, 21 Mar 2026 20:46:33 +0000

I'm not a developer. My background is in neurotechnology and neurofeedback. I run a practice in Luxembourg. And a few weeks ago, I made my first ever open source contribution — and it landed in a real project that people actually use.

This is that story.

The Project: Veritas Kanban

Veritas Kanban is a lightweight Kanban board built specifically for AI coding agents. It's git-native, local-first (no cloud dependency), and uses Markdown files for tasks and YAML for workflows.

The premise is simple but genuinely useful: most project management tools fight AI agents instead of working with them. Veritas Kanban was built to solve that.

When v4.0 dropped, it shipped with something I hadn't seen before: a real governance layer for agent behavior. We're talking:

Agent Policy Engine — configurable guardrails that define what an AI agent can and can't do
Decision Audit Trail — every agent decision is logged with assumptions and outcomes
Behavioral Drift Detection — catches when agents start going off the rails
Output Evaluation Scoring — quality metrics for what agents produce
33+ MCP tools for Claude, Codex, Copilot, and other compatible agents

It also has a self-hosting guide, 11 new operational SOPs, and a full API reference. Over 620 GitHub stars and growing.

What Does a Non-Dev Contribute?

You might be wondering what someone with no coding background could possibly contribute to a software project. Fair question.

OSS contributions aren't just code. They can be:

Documentation fixes — catching errors, improving clarity, adding examples
Issue reporting — describing bugs or missing features from a user's perspective
Community engagement — showing up in discussions, asking good questions
Testing — using the software and providing real-world feedback
Advocacy — telling people about a project that deserves attention

I contributed in ways that matched my skills. And honestly? The maintainer, Brad Groux, was welcoming and made the process straightforward.

Why This Mattered to Me

I've been watching the AI tooling space closely for my work in neurofeedback. The intersection of AI agents and knowledge work is something I care deeply about. When I found Veritas Kanban, I immediately saw its potential — not just for developers, but for anyone building systems where AI plays an active role.

Contributing, even as a non-developer, felt like a way to be part of something moving in the right direction.

The Takeaway for Other Non-Devs

If you've ever thought "OSS isn't for people like me" — I want to challenge that assumption. The barrier to contributing is lower than you think, especially when you find a project whose mission resonates with you.

Start by starring the repo. Then look at the issues. See if there's something you can help with — a question you can answer, a use case you can describe, documentation you can clarify.

You don't have to write code to make an impact.

If you're building with AI agents and haven't looked at Veritas Kanban yet, I genuinely recommend it. The governance features in v4.0 are a real step forward. Check it out at github.com/BradGroux/veritas-kanban.

Forem: Francois Altwies

My First OSS Contribution as a Non-Developer: What I Learned and Why It Matters

The Project: Veritas Kanban

What Does a Non-Dev Contribute?

Why This Mattered to Me

The Takeaway for Other Non-Devs