2016-03-15, 14:36
So looking beyond the few small changes to the current version, are folks signing up for the dev and support for the rather large and technical changes that will come in Kodi V17 with this new repo? This comment:
tends to make me think that there's not a full understanding of what's going on here. I think anyone who contributes to plugin-repo would understand my concern. The YT 3.0 API is a flawed API and IMHO will continue to have problems, at least with the approaches to fixes that I've seen to date. Kodi V17 is going to open a world of potential opportunity for the YT add-on as well as several other services like Amazon Prime, Netflix and Hulu. Folks need to understand that they need to be committed to that long term, as well as these short term issues.
I think that the group idea is great, but people who get involved need understand that the current issues are minor compared to the real work that needs to be done in the not too distant future.
(2016-03-15, 13:44)DjSlash Wrote: @Martijn: I wonder if it would be possible to transfer the plugin-repo to Team Kodi and set up a team for it. This way the plugin gets somewhat protection and not easily lost.
tends to make me think that there's not a full understanding of what's going on here. I think anyone who contributes to plugin-repo would understand my concern. The YT 3.0 API is a flawed API and IMHO will continue to have problems, at least with the approaches to fixes that I've seen to date. Kodi V17 is going to open a world of potential opportunity for the YT add-on as well as several other services like Amazon Prime, Netflix and Hulu. Folks need to understand that they need to be committed to that long term, as well as these short term issues.
I think that the group idea is great, but people who get involved need understand that the current issues are minor compared to the real work that needs to be done in the not too distant future.