OspreyFlowOpen-source project

Team

The people behind OspreyFlow

OspreyFlow was created at Solirius Reply and is developed in the open. These are the people who started it, and the roles anyone can grow into.

ContributeHow decisions are made

Project leads

Ayan Kar

Creator and Chief Architect

Conceived OspreyFlow, designed its architecture and directs its build. Decides questions of architecture and design.

Matthew Couldridge

Product Lead

Owns the roadmap. Runs OspreyFlow with the organisations evaluating it and brings what they need back into the product.

Founding contributors

The people who shaped OspreyFlow before its first public release.

Will Forbes

Founding contributor

Harrison Boyle-Thomas

Founding contributor

Graham Burnside

Founding contributor

Laurence Rawlings

Founding contributor

How it is built

The design, the architecture and every decision in OspreyFlow are the team's. Much of the code is written with AI coding tools working to that design, and every change passes the same reviews, tests and checks before it is merged. We say so because provenance matters in this product, and it matters in how the product is made.

Roles in the project

RoleWhat it meansHow someone gets there
ContributorAnyone whose change, guide, bug report or review has been accepted.Open an issue or a pull request.
MaintainerReviews and merges changes in an area of the product.By invitation of the project leads, after sustained contribution.
Founding contributorRecognition for the people who built OspreyFlow before its public release.A fixed group.
Project leadAnswers for the architecture or the roadmap.Named by the project's steward.

Solirius Reply is the project's steward. Governance sets out who decides what.

Want help to run it? Solirius Reply offers pilots, builds and support: ospreyflow.net.