tektoncd / tektoncd/cli

🛠️ Feature Request: Migrate Fedora-Copr to Dedicated Tekton Copr

Open
#2,648 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

kind/feature
Dominant language
Go
Stars
461
Forks
277
Avg merge
16h 48m
Merged PRs (30d)
95

Description

Motivation

We currently use @chmouel personal Fedora-Copr repo for distributing our packages. To improve organization and management, we should migrate our current setup to a dedicated, Tekton-specific Copr repository.

A dedicated Copr will provide a clearer, more focused repository for Tekton packages, improving clarity for users and simplifying future package management and maintenance.

Proposal
  1. Establish a New Copr: Create a new Copr repository, preferably named tektoncd or tekton-cli.
  2. Migrate Packages: Move all existing Tekton-related builds and packages to this new dedicated repository.
  3. User Migration Plan: This change will require users to update their repository configuration. We must provide clear instructions and communication for users to migrate smoothly to the new repository URL.
Next Steps
  • Define the specific name for the new dedicated Copr repository (e.g., tektoncd).
  • Outline the technical migration plan for transferring the packages.
  • Prepare the user-facing communication and migration instructions.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the existing personal Fedora-Copr repository and the current Tekton package distribution setup. Decide the dedicated repository name, document how packages will move, and define the user-facing migration instructions and communication needed for completion.

Written by the indexing model from the issue text.

Assessment

Domain
documentation, release
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.