Take Ownership of the io.spacingbat3.webcord Flathub repo about webcord

[SpidFightFR]

Like we say, we are our own best advocates.
So i forked the manifest, we'll work on it with pals of mine. I'll see later on with the original maintainer, to continue their work.

So far i managed to make v4.8.0 run on a production system thanks to the clear work they left behind, it was quite easy to work on.

I'll keep you in touch.

[SpidFightFR]

So, tiny update:

Webcord is back on flathub, and i'll probably do most of the maintaining part of that side.
@SpacingBat3 hey there, sorry for the ping. If you need to contact me, my email is on my profile. Don't hesitate ! 😄
Should be good for the most part: i'll keep an eye out for major releases and make the updates. But in case of a problem, now you know.

Have a great day everyone.

[SpacingBat3]

I think I'll close this in favour of #116. My stance is basically the same – I both don't want to maintain multiple repos manually (i.e. I might setup an OBS in case of Linux repos) neither work on package formats that I have no experience with packaging to. You might see me working with the ReForged and eventually implementing the support for the other packaging format, not only just for Linux (e.g. I plan to learn about crafting the Windows installers and even portable executables with NSIS).

Also, as a side note, due to the overall sandboxing that is also troublesome a lot with the Electron, I might not be able to provide the same quality of support for Flatpaks and (for the same reason) Snaps as with the other distributable formats, if I will ever consider supporting both of these packaging formats.

[klaribot]

Just realized this is related enough to #116 for my issue to potentially be a duplicate, but it was also last updated 2 years ago, so I thought I'd bring this back to light now that Flathub is starting to become substantially more popular.

After reading a bit farther down the thread, I also now see that you had success with a couple of the members in this issue who have henceforth maintained the Flathub for you, which makes them marking the repo as End-of-Life even more concerning.

[SpacingBat3]

Yeah, so far this is a duplicate of #116. The main reasons why I don't maintain Flatpaks myself is that I have very little idea to manage them myself. I would also love to produce Flatpaks using Forge directly (I consider toying with GitHub Actions, maybe I'll try running act locally instead of doing a series of temporary commits I overwrite with git push -f), eventually only needing to republish them to Flathub if that's possible.

I've honestly didn't made any re-approaches around packaging the flatpaks with the Forge for a long time. Maybe the installer has gotten improved enough to handle the errors and configuration by itself. This was the tricky part and the main reason why I didn't want to enable Flatpak packaging by the default, I think it was possible to package it via Forge but troublesome overall.

Also, as a maintainer of the ReForged, I could also work on writting a publisher specifically for Flathub, I think there was one for Snapcraft / Snap store but none for Flathub so I guess that could come in handy for the other Electron devs that are willing as well.

[SpidFightFR]

I guess everyone saw this already but the flatpak maintainer must have step down from the project, it's unlisted on flathub as of now and is marked as EOL.

This will become an issue for people relying on it.

[TerohsLab]

Much appreciated .. thank you.