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

Re-think the current Serving structure #5703

Open
ReToCode opened this issue Oct 3, 2023 · 5 comments
Open

Re-think the current Serving structure #5703

ReToCode opened this issue Oct 3, 2023 · 5 comments
Labels
lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. triage/accepted Issues which should be fixed (post-triage)

Comments

@ReToCode
Copy link
Member

ReToCode commented Oct 3, 2023

Context

See https://github.com/knative/docs/pull/5651/files#r1282636966

We should potentially improve our current ordering in the Serving section.
@Cali0707
Copy link
Member

@ReToCode Eventing is also thinking about improving the current ordering. I've spoken to @mmejia02, and the UX WG is going to do user interviews to find out what structure makes the most sense (ideally it will be the same for Serving & Eventing)

/assign @knative/ux-wg-leads

@Cali0707 Cali0707 moved this to Ready to Work in UX WG Roadmap Oct 19, 2023
@Cali0707 Cali0707 mentioned this issue Oct 19, 2023
Closed
@ReToCode
Copy link
Member Author

Perfect, any feedback is welcome.

@github-actions GitHub Actions
Copy link

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 19, 2024
@ReToCode ReToCode 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 19, 2024
@Cali0707
Copy link
Member

Cali0707 commented Jan 19, 2024 •
edited
Loading

/remove-lifecycle stale
/triage accepted

@knative-prow knative-prow bot added the triage/accepted Issues which should be fixed (post-triage) label Jan 19, 2024
@Cali0707 Cali0707 added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. labels Jan 19, 2024
@mmejia02
Copy link

mmejia02 commented Feb 6, 2024

  • Apply findings from the Eventing Documentation study to Serving study
  • Think about conducting another study to the Serving Documentation

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. triage/accepted Issues which should be fixed (post-triage)
Projects
UX WG Roadmap
Status: Ready to Work
Milestone
No milestone
Development

No branches or pull requests
3 participants
@ReToCode @Cali0707 @mmejia02