On Fri, 21 Aug 2026 at 03:22, Lova Andriarimalala via QGIS-Developer <[email protected]> wrote: >
> I agree. So, in my understanding, the consensus is that we can safely remove > it from the plugin manager and then from plugins.qgis.org. Removing it from > plugins.qgis.org would probably require some communication so that people > relying on it are aware of the removal. If there are strong motivations or > suggestions regarding the system, is it possible to re-open the discussion? I think there's still value in it, and showing it as a read-only property directly in the plugin manager. Nyall > > Best regards, > > Lova Andriarimalala > QGIS Full Stack Developer > > T : +27(0) 87 809 2702 E : [email protected] W : kartoza.com > > > > This email and any attachments are confidential and intended solely for the > use of the individual or entity to whom they are addressed. If you > have received this email in error, please notify the sender immediately and > delete it from your system. Unauthorised use, disclosure, or copying > of the contents is prohibited. > > > On Wed, 19 Aug 2026 at 16:28, Greg Troxel <[email protected]> wrote: >> >> Lova Andriarimalala <[email protected]> writes: >> >> > Hi Laurențiu and Greg, >> > >> >> Stepping back, why does the QGIS project feel the need to support a >> >> rating system for third-party code at all? >> > >> > Unfortunately, I don't have the direct answer to that. I was involved in >> > implementing download statistics by country for each plugin and I think >> > this is similar. Basically, they provide insights/metrics for plugin >> > developers and maybe for users as well. >> >> Makes sense about statistics. That has the same faking problem. I do >> realize that there is some insight. >> >> But the real question is whether the insight gained is worth the cost of >> implementing ratings in a way which >> - has adequate protection from fake ratings >> - complies with GDPR and other rules >> - complies with Free Software community ethics >> >> There's a lot of cost to doing it right. >> >> >> Why not just remove all rating data, and remove the code in qgis to >> >> fetch ratings and vote? >> > >> > Technically, that aligns with part of my suggestion earlier. However, this >> > should include (re)-implementing a clean proper rating system that requires >> > users to be authenticated and leave a comment, which would help plugin >> > developers improve their plugins as Denis and Nyall mentioned. >> >> Why do you it "should include reimplementing..."? That's a decision >> that the answer to the previous question is that ratings are so >> important that any cost to properly implement is justified. I see no >> basis to decide that. >> >> IMHO plugins should have a public forge or at least an issue tracker. >> (Speaking of Free Software norms, that shouldn't be on github!) People >> that want to make suggestions to plugin authors can use that. I have >> filed issues to plugins, with varying effects. >> >> >> Another aspect of this is that popular voting, even if we somehow ensure >> that each voter is a community member, that all votes are cast by >> humans, and that no human community member can vote with two or more >> identities, is that opinions need to be considered in light of the >> experience/reputation of the voter. >> >> >> I see this voting system as sufficiently problematic that I don't find >> it of much value. > > _______________________________________________ > QGIS-Developer mailing list > [email protected] > List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer > Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer _______________________________________________ QGIS-Developer mailing list [email protected] List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
