A finishable public objective
A release-sized scope, prepared contribution paths, named review responsibility, lifecycle clarity, and a public story that connects every artifact.
About Elixpo / established 2023
Open work needs more than a repository.
Elixpo is an open-source project foundry. We bring maintainers and contributors together around active software, open research, and public services, then help that work reach a clear, attributable release.
Why Elixpo exists
Publishing code is the beginning, not the finish.
Useful open-source work often stalls between “the code exists” and “people can understand, trust, contribute to, and cite it.” A public repository provides storage and collaboration tools, but it does not automatically provide a shared objective, prepared work, responsive review, accurate status, or a coherent release.
Elixpo works on that missing distance. It creates a bounded frame around the next meaningful outcome and connects the repository to its documentation, research, packages, contributors, decisions, and history. The result is easier to discover because it is easier to understand.
The practical value
What people receive.
Elixpo does not replace the people who understand a project. It makes their work easier to enter, finish, explain, and carry forward.
Work that leads somewhere
A clear outcome, an accountable reviewer, visible decisions, and durable credit connected to the released work—not an isolated commit count.
A record that can be trusted
One place to inspect what is active, paused, completed, or archived and follow the code, research, packages, services, people, and evidence.
The operating unit
An Elixpo Chapter has an end condition.
A Chapter is a time-bounded period of public work. It is neither a permanent ownership claim nor a vague promise to maintain a project forever.
- 01
Frame
Agree on one release-sized objective, its boundaries, evidence, and accountable maintainers.
- 02
Prepare
Document the project, open useful contribution paths, and name who can review the work.
- 03
Build
Develop in public, record decisions, review contributions, and keep the outcome in view.
- 04
Release
Publish the software, research, hardware, or infrastructure with usable documentation.
- 05
Record
Preserve status, attribution, artifacts, decisions, and custody as a durable public record.
How work relates to Elixpo
One commons. Different responsibilities.
Relationship, lifecycle, custody, and license are recorded as separate facts. Being visible through Elixpo never silently changes who authored, owns, maintains, or may reuse a project.
Core projects
Software and services created or operated as part of Elixpo. Each repository still publishes its own lifecycle, maintainers, license, and support boundary.
Chapter participants
Projects working toward a defined public outcome. Participation does not require repository transfer and ends with a release or documented result.
Member Projects
Projects with an ongoing relationship to Elixpo whose original maintainers keep visible authority. Membership is earned through real collaboration, not a listing fee.
Research projects
Experiments, papers, models, datasets, and hardware records published with honest maturity, review, license, and reproducibility information.
Custody without erasure
A transfer changes administration, not authorship.
Repository transfer is optional. A project may remain with its current owner while participating in a Chapter. When a maintainer chooses organization custody, the original author can retain documented project authority and normal administrative access.
Existing copyright and licenses remain in force. Elixpo does not silently relicense contributor work, absorb a project’s identity, or turn organization membership into ownership. The public registry records the actual relationship and names the evidence behind it.
See the responsibility modelThe durable layer
Continuity is a system, not a slogan.
Elixpo cannot guarantee that every maintainer, service, or project will continue forever. It can make change legible. The canonical registry, repository standard, project dossiers, custody records, licensing evidence, contributor records, release narratives, and lifecycle history remain useful when people or priorities change.
What Elixpo is not
- 01A SaaS portfolio assembled around growth claims.
- 02A directory that accepts projects only to display them.
- 03A graveyard that presents abandoned work as active.
- 04A certification authority for projects or contributors.
- 05A guarantee of hosting, funding, uptime, or permanent maintenance.
Direct answers
The questions that matter.
The model should be understandable before anyone contributes code, moves a repository, or attaches their name to the work.
Why would a maintainer build with Elixpo?
To turn a concrete roadmap into prepared public work with clearer contribution paths, accountable review, coordinated discovery, a release narrative, and a durable record of the people and decisions behind it.
Does Elixpo require a repository transfer?
No. A project can participate in a Chapter while remaining under its existing owner. If a repository is transferred, the custody record changes, but authorship, copyright, licensing, and maintainer authority do not silently change with it.
Does Elixpo provide hosting, funding, or permanent maintenance?
Not as an organization-wide promise. Individual public services may be operated by Elixpo, but the foundry itself provides coordination, standards, publication, discovery, attribution, and continuity records—not guaranteed compute, funding, uptime, or indefinite maintenance.
Is Elixpo a home for abandoned repositories?
No. Chapters begin with active ownership and a meaningful next outcome. Paused, completed, and archived work remains visible because honest history is useful, but it is never presented as currently supported work.
Start with the work
Bring a real artifact, an accountable maintainer, and a meaningful next release.
Begin in the public discussion forum. Describe what exists, what the next outcome should be, who can review contributions, and what evidence will show that the Chapter is complete. A discussion is a starting point, not automatic acceptance or a request to transfer a repository.