​One thing we’re learning: creating a broad consensus on adopting a new feature, across multiple companies + platforms, is challenging.

• A feature has to be useful to a critical mass of Creators/Listeners, or have some other broad utility for hosting providers, apps, and partners.
• And, it has to have a chance of getting implemented broadly (what are we willing to spend our limited “social capital” on?)

​Proposal:

​I’d like to formalize how the Podcast Standards Project adopts new features and standards (how we move from idea to adoption):

You can view the whole proposal on GitHub.

​We need a clear, transparent process that balances community input with practical implementation.

​We also need a process that allows us to backtrack if we feel like a specific feature doesn’t merit broad adoption.

​Let me know what you think here.

Cheers,
Justin Jackson

Want to contribute to the HLS video podcast specification? Join the discussion on GitHub or learn more about the Podcast Standards Project.