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

document how to create and publish a demo #415

Open
3 tasks
goern opened this issue Jun 22, 2022 · 6 comments
Open
3 tasks

document how to create and publish a demo #415

goern opened this issue Jun 22, 2022 · 6 comments
Assignees
Labels
kind/documentation Categorizes issue or PR as related to documentation. kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. needs-triage Indicates an issue or PR lacks a `triage/...` label and requires one. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/user-experience Issues or PRs related to the User Experience of our Services, Tools, and Libraries.

Comments

@goern
Copy link
Member

goern commented Jun 22, 2022

Problem statement

During our last retrospective, we identified, that we want to enable any one of the team to create and publish feature demos asynchronously. To do so, we need to have a little guidance on how to create a demo session, how to publish it to our YT channel and which meta-information needs to be present.

Acceptance Criteria

/priority important-soon
/kind feature
/kind documentation

@goern goern added the kind/feature Categorizes issue or PR as related to a new feature. label Jun 22, 2022
@sesheta sesheta added priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. kind/documentation Categorizes issue or PR as related to documentation. needs-triage Indicates an issue or PR lacks a `triage/...` label and requires one. labels Jun 22, 2022
@sesheta
Copy link
Member

sesheta commented Jun 22, 2022

@goern: This issue is currently awaiting triage.
If a refinement session determines this is a relevant issue, it will accept the issue by applying the
triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@goern
Copy link
Member Author

goern commented Jun 22, 2022

/sig user-experience

@sesheta sesheta added sig/user-experience Issues or PRs related to the User Experience of our Services, Tools, and Libraries. and removed needs-sig labels Jun 22, 2022
@mayaCostantini
Copy link
Contributor

/assign @shreekarSS
/assign

@sesheta
Copy link
Member

sesheta commented Sep 21, 2022

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

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

/lifecycle stale

@sesheta sesheta added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Sep 21, 2022
@goern
Copy link
Member Author

goern commented Sep 22, 2022

any update on this @shreekarSS

@harshad16
Copy link
Member

/remove-lifecycle stale
/lifecycle frozen

@sesheta sesheta 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 Oct 4, 2022
@mayaCostantini mayaCostantini removed their assignment Dec 1, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/documentation Categorizes issue or PR as related to documentation. kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. needs-triage Indicates an issue or PR lacks a `triage/...` label and requires one. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/user-experience Issues or PRs related to the User Experience of our Services, Tools, and Libraries.
Projects
Status: 📋 Backlog
Development

No branches or pull requests

5 participants