I noticed my struggle for Kodi repo approval wasn't being publicly documented on the mailing list, feel free to add your opinions on the matter.
---------- Forwarded message ---------- From: PseudoTV Live <pseudotvl...@gmail.com> Date: Thu, Feb 25, 2016 at 3:19 PM Subject: Re: PseudoTV Live To: Martijn Kaijser <mart...@xbmc.org> Cc: ronie <ro...@kodi.tv> Hi Martijn, I would like to know what acceptable alternatives exist to the method I'm using to parse dynamic youtube list from a GitHub file. Would it be acceptable to convert the list to JSON formatting? I can also host the lists on my website if that would make a difference? If you review the code you will see that I have made every attempt to limit external lists to YouTube and RSS feeds specifically. External lists can never be used to parse content beyond those specific sources. It's purely youtube and the few rss feeds that are still active. I've been reviewing a number of plugins currently available on the Kodi repository to find similarities. One that I've found is the Quake Live video plugin ( https://github.com/xbmc/repo-plugins/blob/helix/plugin.video.quake.live/resources/lib/main.py#L29 ) The above plugin points to an external list, in this case a PHP file, outside the control of Kodi and parses that information for use in the plugin. That seems to be parallel to what I'm doing with PTVL, and I'm sure you can see my confusion. There are a number of other add-ons currently in the official repository that use non-api, "list" or JSON parsing, some recently updated or added within the last year. In reviewing add-ons in the official repository, I have also found code specifically written to aid "illegal", "banned" plugins. I'm at a loss to explain why that's not an issue, but YouTube channels via an external list are an issue. Your cautiousness is completely understandable, especially given recent events, but YouTube (for example) controls their content rather well and currently has measures in place to prevent infringement which protects Kodi from any liability. I'm having trouble seeing the difference between PTVL users accessing a list on GitHub when compared with the Vevo plugin parsing their JSON of YouTube IDs. For the sake of transparency, let me explain how the external list function works. PTVL doesn't create channels directly from the lists, the lists act as a link/reference placeholder. For example, the Network YouTube List ( https://github.com/PseudoTV/PseudoTV_Lists/blob/master/youtube_channels_networks.ini#L78), if a user selects that channel, PTVL will parse the YouTube channel IDs using the official YouTube API and collect/pool all the video clips available to create a PTVL channel automatically. The other lists work exactly the same way. If you want the NASA channel, PTVL will use feedparser to collect video clips from the RSS feed ( https://github.com/PseudoTV/PseudoTV_Lists/blob/master/rss.ini#L32). The aggregation of YouTube content outside of YouTubes official API is being done all the time by companies like Vevo, Guidebox and Pluto.tv. All of which have multiple applications that are perfectly legal on all platforms. Content aggregation is exactly what PTVL does, which leaves the liability on the content provider. Only trusted sources are being used. I'm doing everything within my power to comply with Kodi rules, and I believe history will show that. As long as there is a standard in place and I'm not being judged with bias, I will absolutely comply with any requests for code revisions. All I want to do is make PTVL available to the entire Kodi community, and help elevate Kodi to be an innovator in the entertainment center space. If you would be so kind as to explain why one method (which parallels the method I'm using) is acceptable, but my methods are not, it would go a long way towards understand what needs to be done going forward. I'd also appreciate a full review of PTVL so that I can resolve any identified issues for submission. Some suggestions going forward: It would be very helpful to developers if Kodi created a standard that clearly outlined the broad issues with being allowed into the repository. It might also be a good idea to assemble a review and testing panel that could help with reviewing and testing submissions. I know that's not an easy job for one person to do, and honestly I think you've got quite enough on your plate. I'm happy to help in any way that I can. Thank You Kevin On Mon, Feb 22, 2016 at 3:27 PM, Martijn Kaijser <mart...@xbmc.org> wrote: > Took a 5 second look and it's denied > > https://github.com/PseudoTV/PseudoTV_Live/blob/master/resources/lib/ChannelList.py#L4338 > > It is not allowed to maintain channels outside repo control. After that i > stopped checking > > regards, > Martijn Kaijser > XBMC Foundation > Team-Kodi > > License and development: > Kodi® is a registered trademark of the XBMC Foundation. For further > details you can visit http://kodi.wiki/view/Official:Trademark_Policy > The code is fully Open-Source and released under the GPLv2.0+ license and > can be found at https://github.com/xbmc/xbmc. It includes many > third-party libraries which use compatible licenses. Due to the inclusion > of some GPLv3.0 libraries the entire application becomes GPLv3.0 as binary. > > On 20 February 2016 at 16:41, PseudoTV Live <pseudotvl...@gmail.com> > wrote: > >> Hi, >> >> Have you had a chance to review PseudoTV Live? I ask because the code is >> outdated now. >> >> I'd like to submit the updated code, but don't want to reset the review >> process time. >> >> >> Would it be easier to wait for ptvl repo approval, then send you an >> updated? or resubmit? >> >> >> Thanks >> Kevin >> > >
------------------------------------------------------------------------------
_______________________________________________ Xbmc-addons mailing list Xbmc-addons@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xbmc-addons
