Problem description: the extension system is great, but currently it's still pretty chaotic. there's an extension website, but it doesn't show how to contact extension-authors. Nor does it display the current state of the extension (broken/working).
Until that is fixed (and maybe even after having that solved) I propose to come up with a system that does the following:
- - - Workflow proposal for broken extensions - - -
Create and maintain a list of broken extensions / plugins. I'm sure each plugin has a unique ID or something similar. Collect those of the broken extensions.
Then if a user wants to install such a broken extension either simply prevent this from happening by showing an informative message that "This extension is not compatible with the current stable release of LO and known to cause big issues."
Softer approach: Display warning and offer "Cancel" "Continue" "Please only click continue if you are absolutely sure of what you are doing. Installing this extension might cause crashes and other huge pains."
Steps to reproduce:
1. install broken extension (e.g. Duden thingy, which is know to be dead - more (in german): https://www.duden.de/support/haeufige-fragen/duden-Rechtschreibpruefung-9-openoffice-libreoffice )
2. LO crashes and users flood the bug tracker with reports
this is both very frustrating and ineffective for the users as well as LO QA.
Current behavior: All extensions can be installed and cause severe issues and waste a lot of precious time of both users and LO QA.
Expected behavior: Once an extension is know to be broken it should no longer be possible to install it.
Operating System: All
Version: 18.104.22.168.alpha0+ Master
a starting point may be DescriptionInfoset::checkBlacklist (desktop/source/deployment/misc/dp_descriptioninfoset.cxx)
related is the "set black list for extension migration" code in MigrationImpl::runServices (desktop/source/migration/migration.cxx) to not migrate certain extensions from a LO 3 -> 4 user installation
Migrating Whiteboard tags to Keywords: (EasyHack)
JanI is default CC for Easy Hacks (Add Jan; remove LibreOffice Dev List from CC)
This seems to be working around the problem instead of fixing the core problem:
If there is an easy feedback channel for an extension where it was downloaded from (like e.g. in app-stores), broken extensions would collect negative comments and self-regulate themselves out of the market.
So the core issue is that there is no obvious and easy way to colllect feedback on extensions.