Skip to content

Conversation

@petr-muller
Copy link
Member

@petr-muller petr-muller commented Nov 30, 2022

CVO-specific user-targeting content will always partially overlap with other
documentation, like OCP docs about upgrades, the dev-guide in the openshift/enhancement
repository and perhaps other locations. Ideally we want avoid duplicating other
content here as much as possible: only cover the basics or really CVO-specific
content in this repository, and link elsewhere when needed.

The goals of the README are the following:

  1. Inform a technical, knowledgeable user about how CVO operates
  2. Inform a technical, knowledgeable user about how to interact with CVO in a cluster
  3. Redirect an incoming developer to another suitable location for information
    about development, testing and contributing
  4. Present CVO repository as well-maintained and visitor-friendly

This PR only brings the user-facing content. The developer-facing content is moved/updated in a separate #871

@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Nov 30, 2022
@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Nov 30, 2022
@petr-muller
Copy link
Member Author

/cc @wking @skopacz1 @obrown1205

@petr-muller petr-muller force-pushed the ota-560-user-centered-readme branch from aa7a073 to de36132 Compare November 30, 2022 16:49
@petr-muller petr-muller force-pushed the ota-560-user-centered-readme branch from de36132 to bf6cc77 Compare December 2, 2022 18:06
@petr-muller petr-muller force-pushed the ota-560-user-centered-readme branch from bf6cc77 to 59e0826 Compare December 6, 2022 17:52
But there are way more CVO consumers than there are CVO devs. We should
aim the README at "what does the CVO do for my clusters?"``
@petr-muller petr-muller force-pushed the ota-560-user-centered-readme branch from 59e0826 to 4d4d4b4 Compare December 6, 2022 17:54
@petr-muller petr-muller changed the title WIP: OTA-560: Modernize README.md to be user-centered OTA-560: Modernize README.md to be user-centered Dec 6, 2022
@openshift-ci openshift-ci bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Dec 6, 2022
@petr-muller
Copy link
Member Author

petr-muller commented Dec 6, 2022

4d4d4b4 contains all fixes for the formatting artifacts pointed out by @wking

I have moved this PR from WIP, @LalatenduMohanty pointed out that it's better to submit the "move developer-oriented content to new location" part of OTA-560 as a separate PR.

Copy link
Member

@wking wking left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Dec 9, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Dec 9, 2022

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: petr-muller, wking

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-merge-robot openshift-merge-robot merged commit fa80044 into openshift:master Dec 9, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants