Dear Martjin,
it's easy for myself following these steps. Imagine someone don't even know how to start a terminal and you want them to explain how to put files into their systems hard drive? Hmm ...
Woho, don't start talking about a lobby store like Google. Your are OpenSource, not a money laundry machine.
Hypocrite? Naw, not even a bit
. I smell some hierarchy. An idea could be to build up a own XBMC Git GUI for devs, but like you already said. If you start adding a
repo add-on to xbmc's official repo someone might mess it up one day or use piracy add-ons. I don't want to host them, you don't want to host them, so why do we not leave the responsibility to users? No one wants to get in trouble of some dev's might mess it up. What is not allowed in your country, is welcome in others. But I don't want to get responsible for it.
XBMC's repo might be easy to handle like GitHub but it doesn't allow me to look behind closed doors. More than one dev is not allow to update add-ons. But GitHub can manage groups of devs. Don't get me wrong, but do someone proof the updates via git each add-on?
Adding a link is a one way solution. Where do you get so much steps out of it? I do not understand why this might be so hard to type in a link
I browse the third-party wiki, type in short link in XBMC's GUI, voilà!
A yes or no would be totally enough. Or are there any interests kinda like that way?