📹 Incorporate old meeting recordings

[JFWooten4]

What problem does your feature solve?

There is a large amount of contextual knowledge held in prior developer meetings on Zoom. I sincerely appreciate the recent move to Discord for community-lead collective growth. That said, it could still be quite useful to import these old archives for maximum context. 🫱🏻‍🫲🏾

What would you like to see?

To the extent that there are public records across the networks' organizations, perhaps we could aggregate past recordings into the meeting-notes folder? This should be a simple addition of the existing doc style for this year's recordings. ⏯️ Moreover, might we consider segmenting the left sidebar by year and implementing slightly more readable titles like "October 24?"

What alternatives are there?

When making meaningful network amendments, it could help to have an easy place to reference past decision discussions. Presently, this involves extensive web search for community articles and viewpoints, since YT video descriptions alone rarely show up via SEO. Given the material number of SDF blog posts I've seen associated with these tremendous chats, it could also work to just make all embedding legacy posts include a meetings tab in the RSS feed. 📺

[briwylde08]

Want to confirm, are you looking for the dev meetings? https://developers.stellar.org/meetings - they're stored here. Or are you looking for something else?

Note: we are going to link to YT and Twitch in the footer.

[JFWooten4]

Thanks for diving into the details @briwylde08! Yes, I am referring to the /meetings endpoint when I talk about the more readable titles. Love the idea of linking to the YouTube and Twitch pages, especially since a lot of the Discord events can get lost on the general public!

As for the historic series, there is a general playlist here, and many of these videos are embedded in the SDF's associated blog posts. I'm proposing a single comprehensive record of these past discussions and descriptions in the present meetings tab, which I believe requires further involvement from other team members. Reason being: this playlist, along with others by the SDF's YouTube channel, shows that there are hidden videos visible only to internal members:

As someone who recalls watching unlisted videos linked in blog posts over the years from the channel, it'd mean a lot to have all material made public and generally formatted readably and searchably in the docs. Do you think this would help with introducing new developers to important protocol design decisions and future upgrading opportunities?