I want to share with you some changes that are coming to the Shaka family of projects. This will be cross-posted to shaka-player-users, shaka-packager-users, and the GitHub Issues pages of all of our projects.
Shaka is moving within Google
After 7.5 years of Shaka under Chrome/Widevine, the Shaka projects are moving. The Cast team, who has been a primary user of Shaka Player within Google, will be taking over ownership of Shaka from Chrome/Widevine. We look forward to a closer relationship with Cast!
Seeking volunteer maintainers
We are now offering members of the Shaka community an opportunity to share in maintenance responsibilities, such as responding to issues, reviewing and merging PRs, and making releases. We think this is long overdue, and will help all Shaka projects move forward more quickly.
If you would like to volunteer as a maintainer for one or more of the Shaka projects, please email me privately at joeyparrish@google.com.
Infrastructure is moving to GitHub Actions
We are rewriting our internal tools and processes to make them more publicly accessible. Having Google-only tools (and even some Google-only tests) has become a barrier for contributors and has slowed down our release timelines.
We are migrating all testing, release, and deployment infrastructure to GitHub Actions, and improving access as much as possible. All contributors will be able to run the same tests and get faster feedback, and all maintainers will be equally able to create releases and deploy demos and docs.
We will also start sending our own contributions through the public PR process, rather than using a private code review process for Googlers.
Questions?
If you have any questions about these changes, please don't hesitate to ask! You can email me privately at joeyparrish@google.com or ask publicly via the GitHub Issues pages for any of our projects.
Hi everyone,
I want to share with you some changes that are coming to the Shaka family of projects. This will be cross-posted to shaka-player-users, shaka-packager-users, and the GitHub Issues pages of all of our projects.
Shaka is moving within Google
After 7.5 years of Shaka under Chrome/Widevine, the Shaka projects are moving. The Cast team, who has been a primary user of Shaka Player within Google, will be taking over ownership of Shaka from Chrome/Widevine. We look forward to a closer relationship with Cast!
Seeking volunteer maintainers
We are now offering members of the Shaka community an opportunity to share in maintenance responsibilities, such as responding to issues, reviewing and merging PRs, and making releases. We think this is long overdue, and will help all Shaka projects move forward more quickly.
If you would like to volunteer as a maintainer for one or more of the Shaka projects, please email me privately at joeyparrish@google.com.
Infrastructure is moving to GitHub Actions
We are rewriting our internal tools and processes to make them more publicly accessible. Having Google-only tools (and even some Google-only tests) has become a barrier for contributors and has slowed down our release timelines.
We are migrating all testing, release, and deployment infrastructure to GitHub Actions, and improving access as much as possible. All contributors will be able to run the same tests and get faster feedback, and all maintainers will be equally able to create releases and deploy demos and docs.
We will also start sending our own contributions through the public PR process, rather than using a private code review process for Googlers.
Questions?
If you have any questions about these changes, please don't hesitate to ask! You can email me privately at joeyparrish@google.com or ask publicly via the GitHub Issues pages for any of our projects.
https://github.com/google/shaka-packager https://github.com/google/shaka-player https://github.com/google/shaka-player-embedded https://github.com/google/shaka-streamer
Joey, on behalf of the Shaka Team