area/che-operator

Issues and PRs related to Eclipse Che Kubernetes Operator

area/che-server

Issues related to chectl, the CLI of Che

area/ci/multi-arch

Issues and PRs related to the release of images targeting architectures other than amd64

CI build and releases, PR testing, & whitelabel/productization issues

area/devfile-converter

library used to convert v1 to v2 or v2 to v1 devfiles

area/devfile-registry

area/devfile-spec

Issues related to Devfile v2

area/devworkspace-operator

Issues related to documentation

area/dogfooding

Using Eclispe Che to code, test and build Eclipse Che

area/editor/jetbrains/intellij

Issues related to the IntelliJ-based IDE for Eclipse Che

area/editor/jetbrains/pycharm

JetBrains PyCharm IDE support

area/editor/jetbrains

JetBrains IDEs support

area/editor/theia

Issues related to the che-theia IDE of Che

area/editor/vscode

Issues related to the Code OSS editor of Che

area/factory/dashboard

Issues related to factories frontend (che user dashboard side)

area/factory/server

Server side of factory implementation

area/getting-started

Issues related to the getting started samples https://www.eclipse.org/che/getting-started/cloud/

area/git/dev-environment-config

Issues and PRs related to the automatic setup of git within a cloud development environment

area/git/oauth-services

OAuth support to authenticate developers with their GitHub, GitLab, Bitbucket etc...accounts

area/hosted-che

area/image-puller

Issues related to image-puller https://github.com/che-incubator/kubernetes-image-puller

Issues related to installation, including offline/air gap and initial setup

Issues related to Language extensions or plugins integration.

area/machine-exec

Embedded open-vsx registry

area/plugin-broker

area/plugin-port

Issues related to the port plugin

area/plugin-registry

Issues related to Che telemetry feature

area/ts-workspace-client

Issues related to the Che workspace client https://github.com/eclipse/che-workspace-client/

Issues and PRs related to the universal developer image https://github.com/devfile/developer-images

Issues related to User Experience Design

An issue that has been filed automatically, for example by a bot or a script.

Pull requests that update a dependency file

e2e-test/failure

Issues that is related to a test failures reported by our CI platform and our QE.

engine/devworkspace

Issues related to Che configured to use the devworkspace controller as workspace engine.

good first issue

Community, this issue looks easy to start with for a new contributor. Just take it. We'll help you!

Community, we are fully engaged on other issues. Feel free to take this one. We'll help you!

Pull requests that update Java code

Pull requests that update Javascript code

Outline of a bug - must adhere to the bug report template.

kind/enhancement

A feature request - must adhere to the feature request template.

A long-lived, PM-driven feature request. Must include a checklist of items that must be completed.

A checklist of issues for planning a particular sprint.

Questions that haven't been identified as being feature requests or bugs.

Issue dedicated to a release (content, status, related PR, go/nogo/problem discussion, etc.)

Internal things, technical debt, and to-do tasks to be performed.

kind/technical-debt

Technical debt issue

A relatively easy issue that's well suited to being addressed by a pull request from the community.

lifecycle/frozen

Indicates that an issue or PR should not be auto-closed due to staleness.

lifecycle/stale

Denotes an issue or PR has remained open with no activity and has become stale.

new&noteworthy/che-only

Like 'new&noteworthy' but which do not apply to downstream (eg., plugins or devfiles)

For new and/or noteworthy issues that deserve a blog post, new docs, or emphasis in release notes

Epics that are planned to complete in the short term (12 months or more)

roadmap/3-months

Epics that are planned to complete in the short term (within 3 months)

roadmap/6-months

Epics that are planned to complete in the medium term (within 6 months)

severity/blocker

Causes system to crash and be non-recoverable or prevents Che developers from working on Che code.

Has a major impact to usage or development of the system.

Has a minor but important impact to the usage or development of the system.

Lower priority than a P2. Optional work that might get done, or not. See also help wanted issues.

status/analyzing

An issue has been proposed and it is currently being analyzed for effort and implementation approach

Issue that can’t be moved forward. Must include a comment on the reason for the blockage.

status/code-review

This issue has a pull request posted for it and is awaiting code review completion by the community.

status/doc-impact

This issue has an impact on documentation, it is required to provide a documentation update.

status/duplicate

Issue identified as a duplicate of another issue

status/in-progress

This issue has been taken by an engineer and is under active development.

status/info-needed

More information is needed before the issue can move into the “analyzing” state for engineering.

status/need-triage

An issue that needs to be prioritized by the curator responsible for the triage. See https://github.

status/open-for-dev

An issue has had its specification reviewed and confirmed. Waiting for an engineer to take it.

status/release-notes-review-done

Issues that have been reviewed by the doc team for the Release Notes wording

status/release-notes-review-needed

Issues that needs to be reviewed by the doc team for the Release Notes wording

status/validated

The issue resolution has been validated

Indicates that a PR will be merged into a branch other than master.

This team is responsible for the Che Operator and all its operands as well as chectl and Hosted Che

This team is responsible for the Web Terminal, the DevWorkspace Operator and the IDEs.

No labels found. Sorry about that.