So, here we are, back in the roo atm after a day of sidebar meetings, coding, hacking, experimenting, and general conferencing. Time for some more structured sessions, starting with some of our partner projects.
Chewitt started us off with an overview of LibreELEC: hardware updates and changes, new chip set support, some challenges with older SoCs, plans for standardising e.g. kernel trees more, and so on. He also covered topics such as the challenges around supporting set-top box DVB tuners, p
This is a little later in the development cycle than would normally be the case, but I'm sure you'll understand why.
It's traditional, as we move towards the release of a new version of Kodi, to begin the process of naming what will become its successor. In recent years, "Leia" gave way to "Matrix", which moved aside for "Nexus", and then on to our current version, "Omega". There's a clue there to the pattern, so P-something it is.
Our normal process would be to ask the forums and team for suggestions, edit these down to a shortlist, and then run an internal poll and choose a winner. However, the shortlisting was done a little quickly this time, and we ended up picking a P-name that was already in use for a problematic add-on (arrr, shiver me timbers, and all that - absolutely not a connection we'd wish to make). The obvious solution was to skip that one, then, and move to the second choice - except that turned out to be the name of a legitimate streaming service. And the third? Another problematic add-on.
As the team deliberated the need for another poll, we heard sad news about a colleague and team member whose contributions to Kodi have been so immensely valuable. His death at such a young age gave everyone pause, and with his name just-so-happening to begin with exactly the right letter, it seemed fitting to mark his passing with more than just a blog post.
So with muted fanfare, we memorialise our good friend, and continue development towards Kodi v22, "Piers".
You will, of course, hear more about this as the development branch takes shape, and you can follow development on GitHub as you wish.
View the full article