CDCF Project Types: Foundation Projects and Community Projects
The Catholic Digital Commons Foundation (CDCF) recognises two distinct categories of projects within its ecosystem: Foundation Projects and Community Projects. This distinction reflects the Foundation’s dual commitment to rigorous governance of the technology it endorses, and to the visibility and flourishing of the wider Catholic developer community.
Foundation Projects
Foundation Projects are technology initiatives that have been formally submitted for CDCF consideration and have passed through the Foundation’s vetting process.
Key characteristics
- Vetting and governance. Foundation Projects undergo the full two-gate evaluation process (Incubation and Graduation) defined in the Project Vetting Criteria and the Project Lifecycle.
- Intellectual property. Upon acceptance as an active (graduated) project, the intellectual property of a Foundation Project belongs to the CDCF itself. This ensures long-term stewardship, continuity, and protection of the project on behalf of the Catholic community it serves.
- Hosting and distribution. Foundation Projects are hosted under the CDCF’s organisational infrastructure (e.g., github.com/CatholicOS) and are distributed and endorsed by the Foundation.
- Ecclesial governance. The CDCF is not a top-down bureaucracy, but neither is it an independent democratic body. The Foundation is participated and governed by Church institutions themselves — dioceses, episcopal conferences, and bodies of the Holy See — and operates in filial submission to the Church hierarchy. This means that governance is collaborative and community-engaged, while remaining firmly rooted in ecclesial authority and communion. Project Management Committees (PMCs) and the broader contributor community participate actively in the stewardship of Foundation Projects, but always within the framework of the Church’s teaching authority and institutional structures, and in accordance with the principle of subsidiarity.
- Lifecycle stages. Foundation Projects progress through defined stages: Proposal → Incubation → Graduation → Active Status (and eventually Retirement). See lifecycle.md for details.
Why Foundation Projects matter
By bringing a project under the CDCF umbrella, the Catholic community gains:
- Assurance that the project meets standards rooted in Catholic Social Teaching, Canon Law, and technical best practice.
- A named, accountable governance structure for every project.
- Long-term continuity independent of any single developer or institution.
- A trusted channel through which Catholic institutions can discover and deploy mission-aligned technology.
Community Projects
Community Projects are independently developed and maintained technology initiatives that serve the Catholic community but have not been submitted for or accepted into the CDCF vetting process.
Key characteristics
- No formal vetting. Community Projects do not undergo the CDCF’s two-gate evaluation. They are not assessed against the Foundation’s criteria for mission alignment, accountability architecture, or deployment governance.
- Independent ownership. The intellectual property of a Community Project remains with its original developers or maintainers. The CDCF does not hold, govern, or assume responsibility for the project.
- Not hosted or distributed by the CDCF. Community Projects are hosted on their own infrastructure and distributed through their own channels. The CDCF does not endorse them in the same way it endorses Foundation Projects.
- Visibility and collaboration. The CDCF maintains awareness of Community Projects and may list them in a community directory or catalogue. The purpose is not endorsement but visibility — helping Catholic developers, institutions, and ministries discover one another’s work, avoid duplication of effort, and find opportunities for collaboration.
Why Community Projects matter
The Catholic technology landscape is rich with locally driven initiatives — parish apps, diocesan tools, liturgical software, catechetical platforms — built by developers who serve their communities with dedication and skill. Many of these projects may never seek or need formal CDCF governance, but they are an essential part of the ecosystem.
By recognising Community Projects, the CDCF:
- Acknowledges and honours the work of Catholic developers worldwide.
- Creates a space for networking, mutual support, and knowledge sharing.
- Lowers barriers to collaboration across geographic and institutional boundaries.
- Provides a natural pathway for projects that may eventually choose to pursue Foundation status.
Comparison
| Foundation Projects | Community Projects | |
|---|---|---|
| Vetting | Full two-gate process (Incubation → Graduation) | None |
| Intellectual property | Belongs to the CDCF | Remains with original developers |
| Hosting | Hosted by the CDCF | Hosted independently |
| Distribution & endorsement | Distributed and endorsed by the CDCF | Not endorsed by the CDCF |
| Governance | PMC and CDCF governance structures, in ecclesial communion | Self-governed by maintainers |
| CDCF role | Steward and governing body | Visibility and community building |
A note on the relationship between the two
The boundary between Foundation Projects and Community Projects is not a wall but a bridge. Community Projects are welcome to apply for Foundation status at any time. The CDCF’s vetting process is designed to be transparent, supportive, and accessible — not a gatekeeping mechanism but a service to the community.
Similarly, the Foundation’s recognition of Community Projects is an expression of the Catholic principle of solidarity: we are stronger together, and every contribution to the digital commons — whether formally governed or independently maintained — serves the mission of the Church.