Epic Goal

Adopt the pipelines-as-code project into the `tektoncd` organization to provide an opinionated, quick-start CI/CD component for the Tekton ecosystem.

—

Why is this important?

Adopting `pipelines-as-code` provides the Tekton ecosystem with a critically
needed, opinionated "quick-start" component. This lowers the barrier to entry
for new users, making it easier for them to get up and running with a
production-ready, GitOps-based CI solution built on Tekton.

By bringing the project into the `tektoncd` organization, we provide it with a
stable, long-term home under a recognized foundation. This ensures its future
development and sustainability ("perenity") by leveraging Tekton's governance,
infrastructure, and community outreach. This move strengthens both projects:
Tekton gains a mature component that enhances its adoption story, and
`pipelines-as-code` secures its future and expands its community.

—

Scenarios

• Project Migration:* Transfer ownership of the `pipelines-as-code` project to
  the `tektoncd` organization. This includes creating the
  `tektoncd/pipelines-as-code` repository and migrating the codebase.

• Infrastructure & Process Integration:* Set up the necessary infrastructure (e.g., Kubernetes cluster, release mechanisms) and integrate the project into Tekton's community processes, including documentation on `tekton.dev`, Code of Conduct, and CLA.

—

Acceptance Criteria (Mandatory)

• The `tektoncd/pipelines-as-code` repository is created and the codebase is fully migrated.
• The original project maintainers are onboarded and have the necessary permissions to continue their work under the `tektoncd` org.
• The project's CI is successfully running on Tekton's infrastructure, ideally using `pipelines-as-code` itself.
• A plan for migrating the documentation from `pipelinesascode.com` to `tekton.dev` is defined and executed.
• The project's release process is aligned with Tekton standards and is functional.

—

Dependencies (internal and external)

• Internal:
  • Tekton infrastructure team to provide a Kubernetes cluster for the control plane.
  • Approval and analysis of potential increases in infrastructure costs.
  • Access and support for migrating documentation to `tekton.dev`.
• External:
  • Migration of any required VMs (e.g., for GitHub Enterprise, Bitbucket Server) and licenses.

—

Previous Work (Optional)

• Initial proposal and discussion: community#883
• Document comparing Tekton workflow goals with pipelines-as-code.

—

Open questions:

• What is the definitive plan to manage and minimize the increase in infrastructure costs?
• What are the specific technical steps for porting the Hugo-based documentation to `tekton.dev`?
• Can we define a clear roadmap for sunsetting Prow and replacing its functionality with `pipelines-as-code` and GitHub features (e.g., merge queues)?
• How will the existing release process, which uses `pipelines-as-code` to release itself, be fully integrated with Tekton's release tooling and standards?