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.

Sign up for GitHub

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

Jump to bottom

Remove implementation details from Admin Guide #17266

Closed
skabashnyuk opened this issue Jun 27, 2020 · 5 comments
Closed

Remove implementation details from Admin Guide #17266

skabashnyuk opened this issue Jun 27, 2020 · 5 comments
Labels
area/che-server area/doc Issues related to documentation kind/task Internal things, technical debt, and to-do tasks to be performed. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. severity/P2 Has a minor but important impact to the usage or development of the system.
Milestone
7.28

Comments

@skabashnyuk
Copy link
Contributor

Is your task related to a problem? Please describe.

These details didn't help much in the admin's daily work.
They are more like guides for Che developers and perhaps their place is better to move closer to original code.

Describe the solution you'd like

Remove or move it to the che server code.
@skabashnyuk skabashnyuk added kind/task Internal things, technical debt, and to-do tasks to be performed. area/doc Issues related to documentation area/che-server severity/P2 Has a minor but important impact to the usage or development of the system. team/platform labels Jun 27, 2020
@rkratky
Copy link

rkratky commented Jul 7, 2020

@skabashnyuk, thanks for identifying these. Do we need PM or other confirmation, or can we go ahead a remove the content.

Also, you're linking CRW docs. Am I correct in assuming that the content can also be removed from Che docs?

@skabashnyuk
Copy link
Contributor Author

Do we need PM or other confirmation, or can we go ahead a remove the content.

I think that is not necessary since it has no impact on end-user. Only for Eclipse Che committers. CC @l0rd

Am I correct in assuming that the content can also be removed from Che docs?

Yes, I was planning to involve platform team for that. They precisely know what to do. If you don't mind.

@rkratky
Copy link

rkratky commented Jul 7, 2020

Yes, I was planning to involve platform team for that. They precisely know what to do. If you don't mind.

OK, thanks. Re-adding the team/platform label.

@che-bot che-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 20, 2021
@che-bot
Copy link
Contributor

che-bot commented Jan 20, 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.

@skabashnyuk skabashnyuk added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jan 20, 2021
@yhontyk
Copy link

yhontyk commented Jan 25, 2021

Docs Jira issue https://issues.redhat.com/browse/RHDEVDOCS-2539

@skabashnyuk skabashnyuk mentioned this issue Mar 3, 2021
Closed
12 tasks
@skabashnyuk skabashnyuk added this to the 7.28 milestone Mar 3, 2021
This was referenced Mar 15, 2021
Merged
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/che-server area/doc Issues related to documentation kind/task Internal things, technical debt, and to-do tasks to be performed. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. severity/P2 Has a minor but important impact to the usage or development of the system.
Projects
None yet
Milestone
7.28
Development

No branches or pull requests
4 participants
@skabashnyuk @rkratky @yhontyk @che-bot