-
Notifications
You must be signed in to change notification settings - Fork 24
Open
Labels
kind/documentationCategorizes issue or PR as related to documentation.Categorizes issue or PR as related to documentation.kind/featureCategorizes issue or PR as related to a new feature.Categorizes issue or PR as related to a new feature.lifecycle/frozenIndicates that an issue or PR should not be auto-closed due to staleness.Indicates that an issue or PR should not be auto-closed due to staleness.needs-triageIndicates an issue or PR lacks a `triage/...` label and requires one.Indicates an issue or PR lacks a `triage/...` label and requires one.priority/important-soonMust be staffed and worked on either currently, or very soon, ideally in time for the next release.Must be staffed and worked on either currently, or very soon, ideally in time for the next release.sig/user-experienceIssues or PRs related to the User Experience of our Services, Tools, and Libraries.Issues or PRs related to the User Experience of our Services, Tools, and Libraries.
Description
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
- short guide on how to record a demo, published on
core/docs, maybe on the support website? - configure YT so that any of https://github.com/orgs/thoth-station/teams/devs/members can publish
- document which meta-information needs to be added to the YT publication, doc on
core/docs
/priority important-soon
/kind feature
/kind documentation
Metadata
Metadata
Assignees
Labels
kind/documentationCategorizes issue or PR as related to documentation.Categorizes issue or PR as related to documentation.kind/featureCategorizes issue or PR as related to a new feature.Categorizes issue or PR as related to a new feature.lifecycle/frozenIndicates that an issue or PR should not be auto-closed due to staleness.Indicates that an issue or PR should not be auto-closed due to staleness.needs-triageIndicates an issue or PR lacks a `triage/...` label and requires one.Indicates an issue or PR lacks a `triage/...` label and requires one.priority/important-soonMust be staffed and worked on either currently, or very soon, ideally in time for the next release.Must be staffed and worked on either currently, or very soon, ideally in time for the next release.sig/user-experienceIssues or PRs related to the User Experience of our Services, Tools, and Libraries.Issues or PRs related to the User Experience of our Services, Tools, and Libraries.
Type
Projects
Status
📋 Backlog