docs: add publishing podcasts document to the community docs #2034
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| @@ -0,0 +1,76 @@ | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| --- | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| title: Publishing meetings as podcasts | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| weight: 40 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| --- | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| # FAQ | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| ## Publishing recorded meetings as podcasts on AsyncAPI | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| This document covers FAQs on publishing recorded AsyncAPI meetings as podcasts. It is intended to guide any AsyncAPI member who has the rights/access to stream and record meetings; on how to publish the recorded meetings as podcasts. For more information on streaming and recording meetings, check the [Meetings-Organization](https://www.asyncapi.com/docs/community/060-meetings-and-communication/MEETINGS_ORGANIZATION) document. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| ### Why do we need this feature? | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
bandantonio marked this conversation as resolved.
Show resolved
Hide resolved
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| - Some people prefer to listen to the video/livestream as an audio (podcast) instead of watching the video. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| - The goal is to upload our AsyncAPI video/live streams on `Spotify For Podcasters` platform, ultimately allowing the listener to play the episodes on Spotify. Almost every YouTube video can be converted into a podcast. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| - The goal is to upload our AsyncAPI video/live streams on `Spotify For Podcasters` platform, ultimately allowing the listener to play the episodes on Spotify. Almost every YouTube video can be converted into a podcast. | |
| - The goal is to upload our AsyncAPI video/live streams on `Spotify for Podcasters`, ultimately allowing the listener to play the episodes on Spotify. Almost every YouTube video can be converted into a podcast. |
🤖 Prompt for AI Agents
In docs/060-meetings-and-communication/publishing-podcasts.md around line 15,
the phrase "Spotify For Podcasters" uses incorrect brand casing; change it to
the official styling "Spotify for Podcasters." and update any other occurrences
in the file to match exact brand casing and punctuation.
bandantonio marked this conversation as resolved.
Show resolved
Hide resolved
bandantonio marked this conversation as resolved.
Show resolved
Hide resolved
coderabbitai[bot] marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
coderabbitai[bot] marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
Outdated
There was a problem hiding this comment.
Autolink the example and format the extracted ID
-Let's take this video link, for example: https://www.youtube.com/watch?v=3rg_7hIb9PQ.
+Let's take this video link, for example: <https://www.youtube.com/watch?v=3rg_7hIb9PQ>.
-Here the video ID is the word/entity after `https://www.youtube.com/watch?v=`, i.e., `3rg_7hIb9PQ`
+Here the video ID is the part after `https://www.youtube.com/watch?v=`, i.e., `3rg_7hIb9PQ`.📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| Let's take this video link, for example: https://www.youtube.com/watch?v=3rg_7hIb9PQ. | |
| Here the video ID is the word/entity after `https://www.youtube.com/watch?v=`, i.e., `3rg_7hIb9PQ` | |
| Let's take this video link, for example: <https://www.youtube.com/watch?v=3rg_7hIb9PQ>. | |
| Here the video ID is the part after `https://www.youtube.com/watch?v=`, i.e., `3rg_7hIb9PQ`. |
🧰 Tools
🪛 markdownlint-cli2 (0.17.2)
41-41: Bare URL used
(MD034, no-bare-urls)
🤖 Prompt for AI Agents
In docs/060-meetings-and-communication/publishing-podcasts.md around lines 41 to
44, the plain URL example should be made clickable and the extracted video ID
should be formatted as inline code; replace the raw URL with a Markdown/autolink
(e.g., <https://www.youtube.com/watch?v=3rg_7hIb9PQ> or a standard Markdown
link) and wrap the ID 3rg_7hIb9PQ in inline code formatting so it stands out as
an extracted identifier.
coderabbitai[bot] marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
coderabbitai[bot] marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
Outdated
There was a problem hiding this comment.
Wrap bare URLs in examples and fix invalid youtu.be domain.
- Address MD034 by autolinking example URLs.
- “www.youtu.be” is invalid; use “https://youtu.be/…”.
- `https://www.youtube.com/watch?v=VIDEO_ID`
- - Here, it can be https://www.youtube.com/watch?v=3rg_7hIb9PQ
+ - Here, it can be <https://www.youtube.com/watch?v=3rg_7hIb9PQ>
- `https://youtu.be/VIDEO_ID`
- - Here, it can be https://www.youtu.be/3rg_7hIb9PQ
+ - Here, it can be <https://youtu.be/3rg_7hIb9PQ>
- `https://www.youtube.com/embed/VIDEO_ID`
- - Here, it can be https://www.youtube.com/embed/3rg_7hIb9PQ
+ - Here, it can be <https://www.youtube.com/embed/3rg_7hIb9PQ>
- - `https://www.youtube.com/playlist?list=PLAYLIST_ID`
- - Here, it can be https://www.youtube.com/playlist?list=PLbi1gRlP7piiaD67o1F4EOPoZztg2r8l6
+ - `https://www.youtube.com/playlist?list=PLAYLIST_ID`
+ - Here, it can be <https://www.youtube.com/playlist?list=PLbi1gRlP7piiaD67o1F4EOPoZztg2r8l6>
- `https://www.youtube.com/shorts/VIDEO_ID`
- - Here, it can be https://www.youtube.com/shorts/3rg_7hIb9PQ
+ - Here, it can be <https://www.youtube.com/shorts/3rg_7hIb9PQ>
- `https://www.youtube.com/watch?v=VIDEO_ID&list=PLAYLIST_ID`
- - Here, it can be https://www.youtube.com/watch?v=deLUAobdVpw&list=PLbi1gRlP7piiaD67o1F4EOPoZztg2r8l6
+ - Here, it can be <https://www.youtube.com/watch?v=deLUAobdVpw&list=PLbi1gRlP7piiaD67o1F4EOPoZztg2r8l6>
- `https://youtube.com/shorts/VIDEO_ID?feature=share`
- - Here, it can be https://youtube.com/shorts/U5jUr8XAF_M?feature=share
+ - Here, it can be <https://youtube.com/shorts/U5jUr8XAF_M?feature=share>📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| - `https://www.youtube.com/watch?v=VIDEO_ID` | |
| - Here, it can be https://www.youtube.com/watch?v=3rg_7hIb9PQ | |
| - `https://youtu.be/VIDEO_ID` | |
| - Here, it can be https://www.youtu.be/3rg_7hIb9PQ | |
| - `https://www.youtube.com/embed/VIDEO_ID` | |
| - Here, it can be https://www.youtube.com/embed/3rg_7hIb9PQ | |
| - `https://www.youtube.com/playlist?list=PLAYLIST_ID` | |
| - Here, it can be https://www.youtube.com/playlist?list=PLbi1gRlP7piiaD67o1F4EOPoZztg2r8l6 | |
| - `https://www.youtube.com/shorts/VIDEO_ID` | |
| - Here, it can be https://www.youtube.com/shorts/3rg_7hIb9PQ | |
| - `https://www.youtube.com/watch?v=VIDEO_ID&list=PLAYLIST_ID` | |
| - Here, it can be https://www.youtube.com/watch?v=deLUAobdVpw&list=PLbi1gRlP7piiaD67o1F4EOPoZztg2r8l6 | |
| - `https://youtube.com/shorts/VIDEO_ID?feature=share` | |
| - Here, it can be https://youtube.com/shorts/U5jUr8XAF_M?feature=share | |
| - `https://www.youtube.com/watch?v=VIDEO_ID` | |
| - Here, it can be <https://www.youtube.com/watch?v=3rg_7hIb9PQ> | |
| - `https://youtu.be/VIDEO_ID` | |
| - Here, it can be <https://youtu.be/3rg_7hIb9PQ> | |
| - `https://www.youtube.com/embed/VIDEO_ID` | |
| - Here, it can be <https://www.youtube.com/embed/3rg_7hIb9PQ> | |
| - `https://www.youtube.com/playlist?list=PLAYLIST_ID` | |
| - Here, it can be <https://www.youtube.com/playlist?list=PLbi1gRlP7piiaD67o1F4EOPoZztg2r8l6> | |
| - `https://www.youtube.com/shorts/VIDEO_ID` | |
| - Here, it can be <https://www.youtube.com/shorts/3rg_7hIb9PQ> | |
| - `https://www.youtube.com/watch?v=VIDEO_ID&list=PLAYLIST_ID` | |
| - Here, it can be <https://www.youtube.com/watch?v=deLUAobdVpw&list=PLbi1gRlP7piiaD67o1F4EOPoZztg2r8l6> | |
| - `https://youtube.com/shorts/VIDEO_ID?feature=share` | |
| - Here, it can be <https://youtube.com/shorts/U5jUr8XAF_M?feature=share> |
🧰 Tools
🪛 markdownlint-cli2 (0.17.2)
43-43: Bare URL used
(MD034, no-bare-urls)
45-45: Bare URL used
(MD034, no-bare-urls)
47-47: Bare URL used
(MD034, no-bare-urls)
49-49: Bare URL used
(MD034, no-bare-urls)
51-51: Bare URL used
(MD034, no-bare-urls)
53-53: Bare URL used
(MD034, no-bare-urls)
55-55: Bare URL used
(MD034, no-bare-urls)
🤖 Prompt for AI Agents
In docs/060-meetings-and-communication/publishing-podcasts.md around lines 42 to
56, the example URLs are bare (triggering MD034) and one entry uses the invalid
domain "www.youtu.be"; update the examples by autolinking each URL (wrap each
example URL in <> so they render as links) and replace "https://www.youtu.be/…"
with the correct short-domain form "https://youtu.be/…", keeping all other
example URLs unchanged and ensuring consistent https scheme.
thulieblack marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
thulieblack marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
coderabbitai[bot] marked this conversation as resolved.
Show resolved
Hide resolved
coderabbitai[bot] marked this conversation as resolved.
Show resolved
Hide resolved
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.