[QGIS-Developer] Are there any real mandatory rules for publishing a plugin?

[Régis Haubourg]

Good, we have lots of ideas to process here.
Does someone would take the lead for a workshop during the contributor 
meeting next week ?
The process is simple : just add a track at 
https://github.com/qgis/QGIS/wiki/29th-Contributor-Meeting-in-Switzerland#thursday-sessions 
and send a message to the list and our brand new Signal contributor channel


Best regards,

Régis Haubourg
Elected member at the Program Steering Comitee of QGIS.org.
-

On 30/09/2026 16:25, Nicolas Godet wrote:
> Hi Régis,
>
> Indeed, 2 categories were what I had in mind: official/trusted/approved/name_TBD and community (all other plugins).
>
> To be listed in the first one would require a large amount of downloads/stars, should work on current supported QGIS versions (to filter heavily downloaded old plugins which are not useful anymore but maintainers did not deprecate them), new plugins could apply on motivated candidature proving why they should be listed, automatic listing from trusted users…
> All above are raw ideas.
>
> New checkbox in plugin manager to enable community plugins with a clear warning that using these plugins is at your own risk.
>
> I do not know the current workflow for plugin approval, how many people have approving rights, the approval checklist, etc. I know some work has been done to document the process, but looking at Admire’s answer in a separate thread, approval rules need some polishing and hardening to avoid the loss of trust in the QGIS plugin repository.
>
> Kind regards,
> Nicolas
>
>> Le 30 sept. 2026 à 13:59, Régis Haubourg via QGIS-Developer <qgis-developer at lists.osgeo.org> a écrit :
>> Hi, I agree that our community repository is really large now and the world has changed. What should be the direction we should take according to you? Something like an official repo, with a real security triage, and a filter of really up to date and active tools?
>> And besides this, community repositories, not activated by default ? Thanks for your ideas, user conference and community meeting is next week and a dedicated session would be wonderful
>> Cheers
>> Régis
>>
>>
>> On 30/09/2026 13:31, Nicolas Godet via QGIS-Developer <qgis-developer at lists.osgeo.org> wrote:
>>> Dear all,
>>> I can’t agree more on the fact that the plugin repo has become a wild jungle with less and less interest in digging into it to find an innovative one.
>>> A few years ago, I spent a few minutes each week looking at each new plugin (because there were only ten or so). Now, I don’t look at new plugins anymore because there are too many of them and most of them are a duplicate of another plugin or, even worse, of a core feature.
>>> I think new rules should be put in place or at least a way to distinguish good, community-approved plugins from the nonsense garbage in the quest for likes for their LinkedIn post.
>>> Kind regards,
>>> Nicolas
>>>> Le 29 sept. 2026 à 17:45, Stefano Campus via QGIS-Developer <qgis- > developer at lists.osgeo.org> a écrit :
>>>> 
>>>> Good morning,
>>>> a few days ago, a plugin [1] was released that is a fork of an > existing plugin which had been updated (without the original plugin > author being notified) to QGIS 4.
>>>> The GitHub repository has issues disabled, so it is not possible to > report bugs that are present.
>>>> But shouldn’t it be mandatory to have issue reporting enabled?
>>>> Furthermore, the proliferation of plugins makes it difficult to find > the truly innovative ones.
>>>> So we see plugins that replicate core functions, perhaps giving them a > more appealing user interface
>>>> Where can I report this to the team that coordinates the plugins?
>>>> Do you think we should report these anomalies?
>>>> Many thanks
>>>> stefano
>>>> [1] https://github.com/veogeo/go3streetview <https://github.com/ > veogeo/go3streetview>
>>>> _______________________________________________
>>>> QGIS-Developer mailing list
>>>> QGIS-Developer at lists.osgeo.org
>>>> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>>>> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>>> _______________________________________________
>>> QGIS-Developer mailing list
>>> QGIS-Developer at lists.osgeo.org
>>> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>>> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>> _______________________________________________
>> QGIS-Developer mailing list
>> QGIS-Developer at lists.osgeo.org
>> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer