Discussion about project governance

[dagwieers]

Given that script.module.routing is a critical piece of any add-on using it and in light of recent events I would like to discuss this project's governance. I count at least 4 active contributors which is a good foundation for a close collaboration. And the momentum is here now to make this happen.

Note that even though what happened was not directly caused by this project, in my opinion it is a symptom of governance issues.

cc @bigretromike @da3dsoul @michaelarnauts

[dagwieers]

I count at least 25 add-ons using this routing add-on and v0.2.3 has an installation base of 12 million.

[dagwieers]

As it stays pretty quiet here since I opened this issue, let me add a list of things we could consider to advance this project. (in no particular order, just off the top of my head)

• Triage of issues and PRs using labels and milestones
• Form a group of people to review and test changes
• Define rules for getting things merged (wrt. review, docs, tests, etc.)
• Create releases in GitHub
• List stakeholders and reach out to them (i.e. for testing new releases)
• Make use of the Wiki for documentation and collaboration
• Timely review of PRs (faster feedback so things don't get stale)
• Coverage support (my pet peeve 😄)
• Well-defined release-management (using labels and milestones)

Everyone, actively involved in this project, has a vested interest in a stable, versatile, maintained and tested routing library.

[zach-morris]

@tamland What is the state of this addon? As a developer I'd like to continue to use it for Kodi v19, but I see it's quite stale with a lot of bug fixes stuck in pull request.

[da3dsoul]

No idea tbh. Those that manage the project left my suggestions, fixes, etc stale, so I gave up. After much deliberation, since team-kodi doesn't have time to improve the plugin API, and it is indisputably terrible to work with, I have moved on from Kodi. I could go back to it, but it needs a lot of improvements to the player, plugin API, and for the devs to generally not be so closed-minded to their plugin dev community. I'm not pointing fingers, but there were several issues with Leia's plugin system that are "by design" with no discussion from the people actually using the API.