New organizations on GitHub for kodi-adsp, kodi-vfs, kodi-codecs, and more?
#1
Can I suggest some reorganizations of source code repositories for different types of binary addons?


Team-Kodi currently in addition have separate logical organizations on GitHub for a few different binary addon types, like kodi-pvr, kodi-game, and kodi-web:

https://github.com/kodi-pvr
https://github.com/kodi-game
https://github.com/kodi-web

But looks like Team-Kodi is missing its own logical organization on GitHub for other types of binary addons (which at least Kodi master / nightlies also support today).

https://github.com/xbmc/repo-binary-addons

As you can see there on repo-binary-addons repository are also links to binary addons for "audiodecoder", "audioencoder", "inputstream", "peripheral", "screensaver" and "visualization". For which the source code is linked to but is non-the-less spread across multiple repos by different individuals instead of in an logical organizations on GitHub administrated by Team-Kodi.


In addition Kodi also recently have also support for ADSP (Audio Digital Signal Processing) addons and VFS (Virtual File System) of which most repos are not yet linked from repo-binary-addons, and where the addon source code for those are currently hosted mostly in notspiff and AchimTuran own personal repositories on GitHub:

https://github.com/notspiff?utf8=%E2%9C%...ries&q=vfs
https://github.com/AchimTuran?utf8=%E2%9...ies&q=adsp
https://github.com/AchimTuran/kodi-adsp-addons-repo-dev


The consequence if notspiff, AchimTuran, or any other individual developer who currently host one or more binary addon should decide to remove it or even delete their GitHub account would be bad. If you do not like this idea and instead prefer to keep all source code spread across multiple repos by different individuals then at the very least it might be a good idea to for Team-Kodi to mirror those repositories in forks somewhere so that you have a backup of the source code of all binary addons just in case.


If you don't mind the suggestion I would like to recommend that Team-Kodi consolidate all binary under a new organization on GitHub (a new organization called example; "kodi-binary-addons-code").

One other perhaps better alternative could be to create multiple new logical organizations on GitHub each type of binary addon, such as Team-Kodi already have today for kodi-pvr, kodi-game, and kodi-web.

Anyway, missing is consolidating the source code for binary addon which could use logical organization on GitHub, such in for example this:
  • kodi-dsp-addons = Consolidate all "adsp" addons here and in the future maybe also "vdsp" addons if Kodi ever gets those too?
  • kodi-codecs-stream-addons = Consolidate all "audiodecoder" + "audioencoder" + "inputstream" + "vfs" addons here?
  • kodi-peripherals-addons = Consolidate all "peripheral" addons here?
  • kodi-scr-vis-addons = Consolidate all "screensaver" and "visualization" addons here?
Reply
#2
i don't see the point in doing this. IF we do anything it should all go under the xbmc org and splitting it whatever orgs as that makes it a big mess. Spiff maintains his add-ons and it not part of the team and he decides how he maintains his add-ons.
The rest is all WIP.

Yes if some one deletes his account the code will be gone but simply start mirroring whatever isn't that easy. We did this with PVR and it's a mess imo cause you kinda have two upstreams and is a pain.
Read/follow the forum rules.
For troubleshooting and bug reporting, read this first
Interested in seeing some YouTube videos about Kodi? Go here and subscribe
Reply
#3
(2017-05-05, 10:51)Martijn Wrote: i don't see the point in doing this
What about the argument to better orginize binary addons to make it easier for developers new to Kodi?

I would also think that a third-party company like example Netflix or Google would not upstream code if a binary addon is hosted by a random individiual instead of an orginazation on GitHub administrated by the XBMC Foundation / Team-Kodi.

Hopefully someone at Team-Kodi have an open mind and can see the big picture when it comes to making it easier for third-parties to work with Kodi's code, especially when it comes to binary addons which looks to quickly becoming a larger part of Kodi.


Edit below after Martijn edit his post above:
(2017-05-05, 10:51)Martijn Wrote: IF we do anything it should all go under the xbmc org
That would probably be the optimal solution if possible. My suggestions was ideas on how to consolidate if you for whatever reason can not just consolidate every binary addon as their own repositories under your existing xbmc organization on GitHub.
Reply
#4
I have an open mind and more than enough knowledge how stuff works what should be done. Just so you know.
Read/follow the forum rules.
For troubleshooting and bug reporting, read this first
Interested in seeing some YouTube videos about Kodi? Go here and subscribe
Reply
#5
(2017-05-05, 11:07)Martijn Wrote: I have an open mind and more than enough knowledge how stuff works what should be done. Just so you know.
No offence meant. FYI, my first reply was based on you only writting "i don't see the point in doing this" in your post and nothing else, which you have to admit is not exactly constructive criticism, and IMHO would have been better to not to post anything at all then only posting that and nothing more. Glad that you changed your post, thanks!
Reply
#6
hey, i promise you i will not do anything as unresponsible as nuke my repos without organizing new takeovers. i've been around since 2004 so it's not like i'm joe random. the reason the addons are hosted under my user is that i'm the only guy stupid enough to volunteer to maintain all this shit for the community!

this means i do not want more hoops to hop. either they stay or somebody else takes over.
Reply

Logout Mark Read Team Forum Stats Members Help
New organizations on GitHub for kodi-adsp, kodi-vfs, kodi-codecs, and more?0