Login at Kodi Home

Gracus · 2017-08-30, 12:10

(2017-08-30, 01:59)learningit Wrote: This is a good start. Personally, I would like to see only the kodi.org repo installed in the official release of Kodi. Anyone who wants to install 3rd party repos would be required to install a non-official build which is not supported by team kodi. We need to ensure that the reputation of the bona fide Kodi project is maintained and not diluted by any 3rd party interests.

Best way to kill almost all addon development in kodi...

**Martijn** · 2017-08-30, 12:25

(2017-08-30, 12:10)Gracus Wrote:
(2017-08-30, 01:59)learningit Wrote: This is a good start. Personally, I would like to see only the kodi.org repo installed in the official release of Kodi. Anyone who wants to install 3rd party repos would be required to install a non-official build which is not supported by team kodi. We need to ensure that the reputation of the bona fide Kodi project is maintained and not diluted by any 3rd party interests.

Best way to kill almost all addon development in kodi...

That's your opinion and certainly incorrect cause saying "all" development is just so wrong in every way possible

nickr · 2017-08-30, 12:30

No but it certainly stifles development.

Many addons start with people playing around and installing their "homemade" addon directly in their kodi install. They shouldn't have to put their addon in the repo or compile kodi themselves to be able to install from a zip file or their own repo.

**Martijn** · (This post was last modified: 2017-08-30, 12:34 by Martijn.)

(2017-08-30, 12:30)nickr Wrote: No but it certainly stifles development.

Many addons start with people playing around and installing their "homemade" addon directly in their kodi install. They shouldn't have to put their addon in the repo or compile kodi themselves to be able to install from a zip file or their own repo.

And where does it say that that will be the situation? Exactly, it's not stated any where.
Install from .zip or dump the addon in their own local install would still work. The proposal from learningit was to not allow other repos with auto updates which does not hinder development at home

V8MEM · 2017-08-30, 12:55

instead of this minor stop-gap, why not put the tivoization of kodi into full gear and only allow signed addons by selected elite coders.

Koying · 2017-08-30, 12:59

What Martijn says.

You *don't* need a repo for addon development.
Even if the addon has dependecies, you *still* can install the dependency manually, assuming the dependency is meant to be added to the official repo,

I suspect 99.99% of the addon developers use a desktop OS, anyway, so they even can develop in-place, without "installing" anything...

**da-anda** · (This post was last modified: 2017-08-30, 13:05 by da-anda.)

from what I gathered, the PR does nothing else than to ensure that add-ons with the same ID that exist on multiple repositories AND the Kodi repository will only be available from the Kodi repository. If people would like to fork/modify one of these add-ons and put it in their repository, all they have to do is to use a different add-on ID (which they should do anyways). This change basically only forces third party repositories to use different add-on IDs for add-ons that are copies/modifications of add-ons from the official repository. This simply ensures that users will get what they intended to install

trogggy · 2017-08-30, 13:12

(2017-08-30, 12:33)Martijn Wrote: The proposal from learningit was to not allow other repos with auto updates which does not hinder development at home

I can't see how this:

(2017-08-30, 01:59)learningit Wrote: This is a good start. Personally, I would like to see only the kodi.org repo installed in the official release of Kodi. Anyone who wants to install 3rd party repos would be required to install a non-official build which is not supported by team kodi. We need to ensure that the reputation of the bona fide Kodi project is maintained and not diluted by any 3rd party interests.

doesn't go completely against this:

Quote:At no point will any user be prevented from using Kodi Media Center as they so choose, nor will they be prevented from adding additional Addons not in the Kodi Addon Repository or additional addon repositories.

(2017-08-30, 08:27)Koying Wrote: PS. Any "setting" is a waste of time, as the "wizards", "builds" and whatnot will instantly override it.

A question - probably to the wrong audience, but you're the ones making it happen so presumably you know...
Can wizards / builds override settings without a user input? As I understand it the third-party repo switch was introduced with exactly that in mind - users now have to make a decision. Doesn't it work? Or is it that users are making the wrong decisions?

The override repository sounds like a reasonable idea - until I read the comments and get the impression it's somewhere near the top of a slippery slope to a one-stop packaged locked-down kodi in at least some people's minds.
Obviously I'd like a setting to disable it; obviously I won't get one. Probably I wouldn't use it anyway, I've had no reason to so far, if only because I've been too dumb to manage to set up my own working repo.

Gracus · 2017-08-30, 13:58

(2017-08-30, 12:25)Martijn Wrote:
(2017-08-30, 12:10)Gracus Wrote:
(2017-08-30, 01:59)learningit Wrote: This is a good start. Personally, I would like to see only the kodi.org repo installed in the official release of Kodi. Anyone who wants to install 3rd party repos would be required to install a non-official build which is not supported by team kodi. We need to ensure that the reputation of the bona fide Kodi project is maintained and not diluted by any 3rd party interests.

Best way to kill almost all addon development in kodi...

That's your opinion and certainly incorrect cause saying "all" development is just so wrong in every way possible

Maybe you should read all word and not only those that you do not agree with...
My post was about learningit proposal and not about the PR annouced in the OP

Some addon dev got their own repo to give people beta update in order to have beta testing and fix issue
Some skin need you to install a repo to be able to install the skin

So what could be the solution for those ones?
Stop beta testing?(and release bugged addon)
Be added to the official repo? (the skin I use probably won't be accepted)

I understand the need to seperate kodi from all the piracy world but I do not think Learningit proposal is the solution (but that is just my 2 cent and nothing else)

**Lunatixz** · (This post was last modified: 2017-08-30, 14:09 by Lunatixz.)

(2017-08-30, 11:05)RayW1986 Wrote:
(2017-08-30, 11:00)Martijn Wrote: You will still be able to as for you nothing changes.

Ok I think I must have misread then.

I thought the discussion moved to not allowing any repo outside of the Kodi repo, but I'm looking at the Github link and I see that isn't actually the case.

Thanks.

That was my suggestion... In hope it may foster rebranding habits when forking.

Sent from my SM-G935T

**Lunatixz** · 2017-08-30, 14:07

(2017-08-30, 12:10)Gracus Wrote:
(2017-08-30, 01:59)learningit Wrote: This is a good start. Personally, I would like to see only the kodi.org repo installed in the official release of Kodi. Anyone who wants to install 3rd party repos would be required to install a non-official build which is not supported by team kodi. We need to ensure that the reputation of the bona fide Kodi project is maintained and not diluted by any 3rd party interests.

Best way to kill almost all addon development in kodi...

I don't see how? He is talking about repositories, not plug-in.

Sent from my SM-G935T

Gracus · 2017-08-30, 14:10

(2017-08-30, 14:07)Lunatixz Wrote:
(2017-08-30, 12:10)Gracus Wrote:
(2017-08-30, 01:59)learningit Wrote: This is a good start. Personally, I would like to see only the kodi.org repo installed in the official release of Kodi. Anyone who wants to install 3rd party repos would be required to install a non-official build which is not supported by team kodi. We need to ensure that the reputation of the bona fide Kodi project is maintained and not diluted by any 3rd party interests.

Best way to kill almost all addon development in kodi...
I don't see how? He is talking about repositories, not plug-in.

Sent from my SM-G935T (typie typie)

See my answer to Martijn

**learningit** · 2017-08-30, 14:28

Um, I apologize for throwing a turd in the punch bowl here. I did begin the thought with the word "personally", but that might not be well understood by all.
Sorry @ronie, I'm sure you opened this thread to discuss the PR at hand, not my personal desires.

**anxdpanic** · (This post was last modified: 2017-08-30, 16:08 by anxdpanic.)

This seems like it would make testing repos obselete and install from zip would end up being goto for user testing.
'.dev' as test releases doesn't really seem feasible to me. External apps, other add-ons depending on addon.in.dev, or add-ons relying on dependency.in.dev would require all hardcoded add-ons id's changed for users to properly test. (No thank you)
Don't see it fostering debranding or forking either really, as it'd be much easier to long term maintain a service.unknown_source.updater

An alternate option might be to use official as the default override and always the override if official addon version > than x.repo addon version. Then if a user does a manual update and chooses an add-on from a repo that is not the current override*, prompt and allow the user to set that repo as the default override for that add-on(except for official addon version > than x.repo addon version). This should allow for test repositories and normal flow while providing control of unexpected/unintended add-on updates.

* edit: unknown source repo -> repo that is not the current override

Eldorado · (This post was last modified: 2017-08-30, 15:59 by Eldorado.)

(2017-08-30, 14:07)Lunatixz Wrote:
(2017-08-30, 12:10)Gracus Wrote:
(2017-08-30, 01:59)learningit Wrote: This is a good start. Personally, I would like to see only the kodi.org repo installed in the official release of Kodi. Anyone who wants to install 3rd party repos would be required to install a non-official build which is not supported by team kodi. We need to ensure that the reputation of the bona fide Kodi project is maintained and not diluted by any 3rd party interests.

Best way to kill almost all addon development in kodi...
I don't see how? He is talking about repositories, not plug-in.

Sent from my SM-G935T (typie typie)

And then what's the next step after that's put in? Right... slippery slope indeed

It won't kill *all* development, but you sure will have a very high number of pissed off dev's who will leave, who don't believe pushing their addon to the Kodi repo is the holy grail that some make it out to be, and there are a good number of non-pirate addons out there in this boat

IMO learningit is blinded by his hatred towards TVA and isn't thinking about those dev's and their interests and I really hope no one takes that suggestion any further

But I'm afraid with this PR the slide has already started.. a hard handed rule doesn't feel right to me and actually comes off as something done out of spite, if anything I would hope an override of sorts is provided, something the user manually could do

edit - agree with suggestion from post above