Posts: 168
Joined: Sep 2013
(2016-10-03, 09:15)trogggy Wrote: (2016-10-03, 02:25)Bluesmanuk Wrote: This should be an easy thing to resolve.
Where a legitimate addon that cannot be part of the official Kodi repository because of stated rules is concerned, then a simple rule should be in place that states that the developer must, in the first post of a thread, state what modifications their addon makes that could potentially affect the ability for another addon to not work as expected.
Add to that a mandatory use at your own risk statement.
Then any user that wishes to consider using such an addon can do so in a more informed manner and make decisions based upon the information given about the effect that it could have elsewhere in a Kodi setup.
The thread can then be used for users to ask questions, make suggestions and give feedback.
The result is clarity and no more need for conflict or bad feelings, which also means a happier user, developer and owner community.
That's assuming the reasons given are genuine of course. In which case lots of other repos will no doubt be disappearing.
I'm not holding my breath.
If such things were implemented though, then most, if not all doubt would be removed.
Posts: 3,901
Joined: Sep 2013
Reputation:
358
It depends on people visiting here though doesn't it ? There must be a huge userbase that isn't even aware of this site and judging by many of the support requests, they are simply not aware of what they are installing anyway much less of potential conflicts between add-ons.
I can understand the 'we can't let you host something that might break add-on compatibility within our own repo', but given that it was re-named to avoid doing just that, I would have expected that the issue was resolved in a satisfactory way. Obviously the team don't think so, and I'd be interested in hearing any comments that they might like to make regarding all this.
Silence however I'm sure will prevail although I cannot understand how effectively shutting down a respected add-on developer shows any kind of respect for Kodi's users or indeed any respect for the community members here. Particularly in light of the fact that no official team statement has been made regarding this.
Learning Linux the hard way !!
Posts: 2,770
Joined: Mar 2011
Reputation:
95
I don't think "owing us something" or "entitlement" is the issue here. Any FOSS project of this size survives based on cooperation, and there are obvious cracks and tensions within the team that people are trying to understand. Much of the time, they don't matter, because developers (and users here in this forum) come and go all the time - but, sometimes, those issues impact users, and that's the case here: addons that some folks use are being separated away, the support threads binned, and the author is effectively hanging up his IDE as a result.
There are similar issues in other aspects of the project, and it makes people nervous. My worry is that we head into fork territory, which is always a scary time (c/f OpenElec vs LibreElec, OpenOffice vs LibreOffice, ffmpeg vs libav). I hope not, and that it's simply a combination of personality and philosophical clashes coupling with a need to tighten things up on a project of this magnitude and complexity.