konveyor/enhancements

Enhancements tracking repository for Konveyor

Hosted by Cloud Native Computing Foundation · part of Linux Foundation

View on GitHub ↗Jump to charts ↓

konveyor/enhancements has 40+ forks on GitHub and was last pushed on Oct 5, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 50 minutes ago
Added to GitGenius on October 15th, 2026
Created on April 24th, 2020
Open Issues & Pull Requests: 54 (+0)
GitHub issues: Enabled
Number of forks: 42
Total Stargazers: 4 (+0)
Total Subscribers: 19 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 4.9 days
Mean response time: 80.7 days
90th percentile: 227.0 days
Tracked items: 77

Maintainer activity

18 people did triage or write work on this repository in the last 12 months.

At least 72% of enhancements's 18 maintainers work at Red Hat. 14 say where they work, and 13 of those are Red Hat.

Counts unlabeled, assigned, unassigned, milestoned, demilestoned, locked, unlocked over the last 12 months. These are issue and pull request events that require triage or write permission. Commits and code review are not counted. labeled and renamed are excluded because GitHub issue forms record the issue author as the actor. Figures from October 18, 2026. This count is not comparable across projects: each project's automation decides which of these events a person emits. How this is counted.

How this project is maintained

72% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Work labelled "kind/feature" is answered fastest, typically in under an hour, while "RFE" waits about 6 weeks. Three people close 68% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 39
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 720 days
Stale 30+ days: 39
Stale 90+ days: 37

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • needs-priority (50)
  • needs-kind (49)
  • needs-triage (46)
  • stale (33)
  • triage/accepted (21)
  • kind/feature (17)
  • RFE (12)
  • kind/design (4)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Konveyor Enhancements is a centralized enhancement tracking and consensus-building repository for the Konveyor project ecosystem.

The repository addresses the challenge of coordinating significant features and changes across multiple Konveyor sub-projects, such as Container Migration and Virt Migration. Rather than managing enhancements scattered across individual repositories, this tool provides a single location where the community can discuss, debate, and reach consensus on design proposals before implementation begins. Enhancements are formalized through actionable design documents that clarify scope, effort, and cross-repository dependencies, helping the community understand how different parts of the system interact and ensuring the right approach is chosen before deep implementation work starts.

Teams should use this repository when proposing work that impacts how Konveyor operates, adds or removes significant capabilities, requires effort across multiple domains or repositories, or demands formal documentation. The repository is not necessary for bug fixes, additional testing, internal refactoring within a single component, or changes with minimal project-wide impact. The process requires circulating ideas to gauge community interest before filing an enhancement, and optionally prototyping in a fork first. Enhancements may span multiple releases and form the basis of a community roadmap. While anyone can file an enhancement, implementation and acceptance into a release require consensus from domain-specific project maintainers.

The project maintains an active community roadmap and accepts enhancement proposals through a structured issue-based workflow. The repository includes guidelines, templates, and a frequently asked questions section to help contributors understand the process and determine whether their proposed work qualifies as an enhancement or should be handled through standard issue tracking.