Open rtaniwa opened 3 years ago
@rtaniwa @elsony @slemeur @resios I have updated this issue with a list of subtasks to complete to submit the proposal.
Marking the logo complete. @elsony will share the design at one of the upcoming cabals.
I have prepared the following doc with the question / answer for the submission form https://docs.google.com/document/d/1nIJRuxTBGQ2u26bnReTnVHaWH_uvHQvVCK0gS649_80/edit#
Analytics transfer requirement done: https://github.com/cncf/toc/issues/773#issuecomment-1035389764
Added CNCF project contribution: https://github.com/cncf/contribute/pull/94
Added devfile artworks: https://github.com/cncf/artwork/pull/327
To work with DevWorkspace Operator, we need editor and editor injectors. Currently, the editors are in a different project(eclipse-che/che-incubator) and are differently licensed. For example, if we were to follow the devworkspace-demo, it uses the following projects
There are some other editors which are being used in the demo but they would mostly be out-of-scope for this.
It would be really helpful to have at least the Che-Code and Jetbrains IDE projects move from che-incubator to devfile while we are submitting the proposal to CNCF. I suspect it might involve more work that just transferring the repository. Let me know if it would be better to move this to a separate issue.
Problem We would like the devfile to be spreading accross different CNCF tools. There are different initiatives that are already existing: Tilt.dev, garden.io and not to mention things from gitpod or codespaces.
Goal Unifying over a community effort on a commun definition of developer environment would be critical.
Why is it important? Increase reach and community awarness/engagement on devfile.
Subtasks