<div dir="ltr"><div>Hi Greg,</div><div><br></div><div>Thanks so much for your inputs.</div><div><br></div><div>> Why do you it "should include reimplementing..."? That's a decision<br>> that the answer to the previous question is that ratings are so<br>> important that any cost to properly implement is justified. I see no<br>> basis to decide that.</div><div><br></div><div>I apologize if it sounds like a decision. I was just explaining the idea based on previous suggestions.</div><div><br></div><div>> IMHO plugins should have a public forge or at least an issue tracker.<br>> (Speaking of Free Software norms, that shouldn't be on github!) People<br>> that want to make suggestions to plugin authors can use that. I have<br>> filed issues to plugins, with varying effects.</div><div><br></div><div>Sure, that makes total sense.</div><div><br></div><div>> Another aspect of this is that popular voting, even if we somehow ensure<br>> that each voter is a community member, that all votes are cast by<br>> humans, and that no human community member can vote with two or more<br>> identities, is that opinions need to be considered in light of the<br>> experience/reputation of the voter.<br>> I see this voting system as sufficiently problematic that I don't find<br>> it of much value.</div><div><br></div><div>I agree. So, in my understanding, the consensus is that we can safely remove it from the plugin manager and then from <a href="http://plugins.qgis.org">plugins.qgis.org</a>. Removing it from <a href="http://plugins.qgis.org">plugins.qgis.org</a> 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?</div><div><br></div><div>Best regards, </div><div><br></div><div><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div style="color:rgb(34,34,34)">Lova Andriarimalala</div><div style="color:rgb(34,34,34)"><b>QGIS Full Stack Developer <br><br></b></div><div style="color:rgb(34,34,34)"><b>T </b>: +27(0) 87 809 2702 <b>E </b>:<b> </b><a href="mailto:lova@kartoza.com" style="color:rgb(17,85,204)" target="_blank">lova@kartoza.com</a> <b>W</b> : <a href="http://kartoza.com" style="color:rgb(17,85,204)" target="_blank">kartoza.com</a><br></div><div style="color:rgb(34,34,34)"><br></div><div style="color:rgb(34,34,34)"><div><img src="https://erp.kartoza.com/files/KartozaEmailSignatureTest.gif"><br></div><div><br></div><i>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 </i><div><i>have received this email in error, please notify the sender immediately and delete it from your system. Unauthorised use, disclosure, or copying</i></div><div><i>of the contents is prohibited.</i></div></div></div></div></div><br></div><br><div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">On Wed, 19 Aug 2026 at 16:28, Greg Troxel <<a href="mailto:gdt@lexort.com">gdt@lexort.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Lova Andriarimalala <<a href="mailto:lova@kartoza.com" target="_blank">lova@kartoza.com</a>> writes:<br>
<br>
> Hi Laurențiu and Greg,<br>
><br>
>> Stepping back, why does the QGIS project feel the need to support a<br>
>> rating system for third-party code at all?<br>
><br>
> Unfortunately, I don't have the direct answer to that. I was involved in<br>
> implementing download statistics by country for each plugin and I think<br>
> this is similar. Basically, they provide insights/metrics for plugin<br>
> developers and maybe for users as well.<br>
<br>
Makes sense about statistics. That has the same faking problem. I do<br>
realize that there is some insight.<br>
<br>
But the real question is whether the insight gained is worth the cost of<br>
implementing ratings in a way which<br>
- has adequate protection from fake ratings<br>
- complies with GDPR and other rules<br>
- complies with Free Software community ethics<br>
<br>
There's a lot of cost to doing it right.<br>
<br>
>> Why not just remove all rating data, and remove the code in qgis to<br>
>> fetch ratings and vote?<br>
><br>
> Technically, that aligns with part of my suggestion earlier. However, this<br>
> should include (re)-implementing a clean proper rating system that requires<br>
> users to be authenticated and leave a comment, which would help plugin<br>
> developers improve their plugins as Denis and Nyall mentioned.<br>
<br>
Why do you it "should include reimplementing..."? That's a decision<br>
that the answer to the previous question is that ratings are so<br>
important that any cost to properly implement is justified. I see no<br>
basis to decide that.<br>
<br>
IMHO plugins should have a public forge or at least an issue tracker.<br>
(Speaking of Free Software norms, that shouldn't be on github!) People<br>
that want to make suggestions to plugin authors can use that. I have<br>
filed issues to plugins, with varying effects.<br>
<br>
<br>
Another aspect of this is that popular voting, even if we somehow ensure<br>
that each voter is a community member, that all votes are cast by<br>
humans, and that no human community member can vote with two or more<br>
identities, is that opinions need to be considered in light of the<br>
experience/reputation of the voter.<br>
<br>
<br>
I see this voting system as sufficiently problematic that I don't find<br>
it of much value.<br>
</blockquote></div>