You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Over on the Flathub Discource, I started a debate related to the 'verified' status of commercial packages who don't get any upstream support or attention... In other words, it's about this Discord package.
I commented a bit more verbosely on the thread, but I'll leave some shorter thoughts here.
Discord have just actively taken an interest in working on and improving the Flatpak. Transitioning a community-submitted and -maintained manifest for a proprietary app to something that Discord themselves want to get behind and promote has some growing pains, but we've just taken our first steps. I think it's wildly premature—and would greatly damage our image and relationship with ISVs—to just turn around and say "remove verification because we still have work to do."
For example, you mention not being able to integrate certain library fixes. If this Flatpak has their blessing and is ultimately under their control, that should remove that barrier. Longer-term the goal should be to have Discord build the Flatpak out as part of their regular build and release process; they now have a space where they can move in that direction since they have ownership over their app ID. I know several Discord employees are already using the Flatpak, and they’re excited to move forward to improve it; let's work together on a way forward instead of backwards.
Over on the Flathub Discource, I started a debate related to the 'verified' status of commercial packages who don't get any upstream support or attention... In other words, it's about this Discord package.
https://discourse.flathub.org/t/make-the-verified-status-more-strict-i-e-remove-discords-verified-status/5385
I welcome you all to join the discussion
The text was updated successfully, but these errors were encountered: