So, a slightly different topic for a change.
We talk a lot about the Kodi software, its development and releases, and that's fine, as that's what we're all about and that's what everyone ultimately sees. However, we thought we'd change the subject a little and explore what goes on behind the scenes: how "Team Kodi" is structured, and what else is going on in the background in support of that glorious code.
The Kodi Foundation and the Board of Directors
Kodi has a legal personality. We're inco
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