https://bugs.documentfoundation.org/show_bug.cgi?id=75273
Heiko Tietze <[email protected]> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |WONTFIX
Status|NEW |RESOLVED
--- Comment #7 from Heiko Tietze <[email protected]> ---
(In reply to retired from comment #0)
> extension website, ... doesn't show how to contact extension-authors.
/fixed
> Nor does it display the current state of the extension (broken/working).
Should be done by community/admin. Idea is to somehow flag extensions that are
not working properly and archive in case of inactivity. Seems Bjoern has the
same opinion in comment 4.
> Create and maintain a list of broken extensions / plugins.
Requires to know what "broken" means. Could be for a certain and perhaps
outdated version, one platform only, a special system theme etc.
> Then if a user wants to install such a broken extension...
Would rather remove/hide it on the platform.
Putting all together I don't see need to fix something on the code.
@Moaz: If you want to work on the extensions, we have many topics at the
platform https://redmine.documentfoundation.org/projects/extensions
(Silverstripe/Python) and some open bits from last year's GSoC at bug 133026.
You are very welcome to work on this topic.
(In reply to Stephan Bergmann from comment #1)
> a starting point may be DescriptionInfoset::checkBlacklist
> (desktop/source/deployment/misc/dp_descriptioninfoset.cxx)
This has been renamed to checkDenylist().
--
You are receiving this mail because:
You are the assignee for the bug._______________________________________________
Libreoffice-bugs mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
