-
Notifications
You must be signed in to change notification settings - Fork 20
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
[WIP] Create Episode Proposal Template #19
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,37 @@ | ||
Episode Proposal Template | ||
|
||
# [TITLE] | ||
|
||
* Proposal: [PR#n]([link to PR]) | ||
* Authors: [Name]([github profile], ... | ||
* Review Manager: [Name]([github profile]) | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. The concept of a review manager could be interesting where a member of the podcast core team or review managers team (which hopefully can expand in the future) can take on this role to ensure adequate support and stewardship is applied to each episode. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I like this, especially to have one contact person for questions and to keep the status up-to-date. |
||
* Status: [Proposed, Pre-production, Production, Post-production, Published](link to episode if published) | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. status would be updated overtime just like swift evolution. could be tedious but could be fun :) |
||
|
||
## Introduction | ||
|
||
Brief description of episode topic and format | ||
|
||
## Motivation | ||
|
||
Brief description of your motivation behind this episode | ||
|
||
## Proposed contribution | ||
|
||
Brief description of how you intend to contribute to this episode and help make it a reality | ||
|
||
## Source compatibility | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 😄 |
||
|
||
Brief description of how this episode fits with the overall theme of the show | ||
|
||
## Alternatives considered | ||
|
||
Brief description of how the purpose of this proposed episode is not already served by existing content and why a podcast episode it the best format for it | ||
|
||
## Roles | ||
|
||
- Lead Host: | ||
- Co-hosts: | ||
- Editor: | ||
- Publisher: | ||
- Marketer: | ||
- Community Follow up handler |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would this need an associated pull request, or will it just be an issue?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Or are you thinking to have all proposals be a pull request, like with swift-evolution?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think all proposals would be a PR and that the proposal would be updated to include the PR# and link to PR. Might be overkill but I will try and see. what do you think?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think that sounds good!