YouTube: new maintainer or migrate here?

[kevinpapst]

Hi @Alkarex and everyone else from the Community!

I wanted to ask if someone wants to take over maintainership of the YouTube extension.
OR if we could/should move the code to this repository here, so more eyes and hands are available to keep it alive.

I don't have the resources to take care of the plugin and I am going to archive it.

Seeing that this commit was merged, instead of once contacting me beforehand and/or trying to get commit permissions on my repo I get the impression that this might not even be necessary, but would be good to get some feedback anyway.

Thanks for still working on FreshRSS after all these years 👍

[Frenzie]

A PR like that without trying to communicate with you is a bit weird. :-/

I'm fine putting it in this repo, but any maintenance from me would be shallow (i.e., the occasional update if needed to work with FreshRSS sure, but if YT greatly changed probably not unless it somehow piqued my interest.

[Alkarex]

Hello,
It is hard having an overview of third-party extensions and remembering which is actively maintained or not, so in particular for popular extensions, it could indeed be good to move them to https://github.com/FreshRSS/Extensions to facilitate collaboration and avoid forks (which I also dislike). There are also some automated tests on that repo.

[Alkarex]

For reference:

• xExtension-YouTube update #134 (comment)
• My comment on a related case Invidious Extension forked and updated #190 (comment)

[Alkarex]

And example of maintenance issue FreshRSS/FreshRSS#6190

[kevinpapst]

Awesome, thanks for your blazing fast feedback!

I am using a FreshRSS installation hosted by a friend, so I don't even have a dev system around to take care of issues like this one here.

Super simple to fix, but I am not applying any change without a test run before...

I will prepare a commit to move it here and then we should check the commits on the fork and bring them in as well.

[kevinpapst]

Closing, PR in #217