2019-08-28, 15:19
With the switch to Python 3 I've been taking some time to hunt down dependencies for my addons to get an idea of where things are; and if updates will need to be done to them as well.
For addons that extend xbmc.python.module it's really hard to find the maintainer in many cases. The provider attribute for the addon has the original library author name, and all the source links refer to the original libraries as well. This definitely makes sense as these are just wrapped up versions of existing libraries and you want to point out where they came from. The issue though is that it's not clear which Kodi developer is maintaining these addons.
I think it would be great to add a "maintainer" attribute to either the module extension, or somewhere in the meta data for these types of addons. This would be really useful for those of us using these dependencies. We could simply check the addon.xml file and see who to contact. A lot of times it would make tracking down repositories on Github easier too if you do want to do a pull request or something to bring an addon up to date.
For addons that extend xbmc.python.module it's really hard to find the maintainer in many cases. The provider attribute for the addon has the original library author name, and all the source links refer to the original libraries as well. This definitely makes sense as these are just wrapped up versions of existing libraries and you want to point out where they came from. The issue though is that it's not clear which Kodi developer is maintaining these addons.
I think it would be great to add a "maintainer" attribute to either the module extension, or somewhere in the meta data for these types of addons. This would be really useful for those of us using these dependencies. We could simply check the addon.xml file and see who to contact. A lot of times it would make tracking down repositories on Github easier too if you do want to do a pull request or something to bring an addon up to date.