OSS Stewardship

MoM’s laboratry offer the oppotunity to officially serve as CRA compliant OSS Steward for FOSS projects.

We offer to assume stewardship and transfer anything from hobbyist or manufacturer-led setup into a stewarded model that is prepared for long-term use, governance, and CRA-aligned stewardship.

Transition phases

Phase 1: Fit and viability assessment

We evaluate whether the project is a practical candidate for stewardship. This includes business relevance, product intent, maintainer capacity, and likely community traction.

Phase 2: Ethical and governance alignment

We review ownership posture, decision rights, contribution model, and governance expectations. The goal is to ensure the project can be stewarded credibly by an independent non-profit organization.

Phase 3: Technical due diligence

We assess code quality, architecture boundaries, test strategy, release hygiene, documentation, CI/CD, dev container setup, security posture, and AI instruction artifacts.

Phase 4: Platform and organization transition

We plan and execute the practical transfer of repository organization, permissions, issue workflows, project boards, release automation, and maintainer operations on either GitHub or Codeberg.

Phase 5: Value stream and operating roadmap

We map the current flow from intake to release, identify bottlenecks and risk concentration, and define a roadmap for the next operating period.

Phase 6: Stewardship launch and cadence

We establish recurring stewardship routines, to support DevOps and DevX, and we establish role boundaries, quality guardrails, and decision checkpoints so the project can run sustainably after transition.

When this service makes sense

• A project started as an internal experiment or side project has grown to become included in a commercial product and therefore must comply with EU’s CRA.
• The current maintainer model is too fragile for commercial use.
• You need to formalize stewardship before broadening adoption.
• The project should move from founder-led work to resilient shared ownership.
• You wish to secure the current contributors and maintainers bandwidth to innovation and seek help to handle the routines and formal stewardship.
• As a company, your employees are developing stuff, maybe even in their own free time, and that stuff is being used commercially in your business. I becomes unclear who owns it.

Engagement and pricing model

The transition can start as an assessment-only package and then move into implementation work. Most organizations combine this service with membership, because membership unlocks lower rates for ad-hoc work, prepaid bundles, and retainers.

For projects requiring sustained maintenance after transition, we usually recommend a retainer setup so stewardship capacity is predictable month by month.

What you can expect

The transition begins with an assessment of the codebase, the operating model, and the project’s social and technical fit. From there we define the minimum changes needed to make the project viable under stewardship, then we sequence the work so the move is realistic for both people and machines.