Question about managing the lifespan of external integrations

Development
1

Hello,

I was wondering a question that I think is interesting.

If a developer no longer maintains an integration and we want to take it over, how does that work?
Because if we copy it to another repo and publish it, 2 integrations will appear on the store :sweat_smile:
Same question but if 2 people publish the same external integration? :sweat_smile:

Thanks

2

Excellent questions!

You can go take a look at the Jeedom market and you’ll see that it’s a bit of a mess.
After that, there are community and paid options, so you often find several plugins for the same service, and I haven’t seen any solution, things come and go without disappearing in the same place.

I don’t know, maybe there needs to be an « analysis committee Â» for duplicate integrations or those that have bugs and aren’t updated, but in any case, there’s a real issue here.

3

Personally, I wouldn’t be surprised if an integration that’s not well maintained gets removed from the store (still active for people who’ve installed it, but not listed / not installable). Otherwise, it’s going to be a jungle!

4

This is one of the weaknesses of Open Source. It depends on the time and investment of the person maintaining the project. It is always possible to give « maintainer Â» rights to several trusted people, which limits the risks.

5

Exactly, shouldn’t we give the rights now to @pierre-gilles or one or two other trusted people?
What do you think?