Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

a Che sidecar running a lightweight Theia with co-editing/pair-programming capabilities #19728

Closed
sunix opened this issue Apr 30, 2021 · 2 comments
Labels
kind/enhancement A feature request - must adhere to the feature request template. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. severity/P2 Has a minor but important impact to the usage or development of the system.

Comments

@sunix
Copy link
Contributor

sunix commented Apr 30, 2021

Is your enhancement related to a problem? Please describe.

Co-editing/pair-programming is well known request from users/customers. See #8286
At the same time, we want to avoid giving full access to a workspace.

Describe the solution you'd like

In a dedicated Che sidecar, we could start a lightweight Theia with limited access/features and enable Co-editing with Atom Teletype.
That way, teams could the teams could enjoy pair programming, and only the workspace owner could have access to secrets or push to git, etc.
The Che sidecar would be packaged as a Che plugin.

@sunix sunix added the kind/enhancement A feature request - must adhere to the feature request template. label Apr 30, 2021
@che-bot che-bot added the status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. label Apr 30, 2021
@azatsarynnyy
Copy link
Member

dup of #8286

@JPinkney JPinkney added severity/P2 Has a minor but important impact to the usage or development of the system. and removed status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. labels May 3, 2021
@che-bot
Copy link
Contributor

che-bot commented Nov 4, 2021

Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.

Mark the issue as fresh with /remove-lifecycle stale in a new comment.

If this issue is safe to close now please do so.

Moderators: Add lifecycle/frozen label to avoid stale mode.

@che-bot che-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Nov 4, 2021
@che-bot che-bot closed this as completed Nov 22, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/enhancement A feature request - must adhere to the feature request template. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. severity/P2 Has a minor but important impact to the usage or development of the system.
Projects
None yet
Development

No branches or pull requests

4 participants