<div dir="ltr">Thanks Richard, <div>It does not show up in new anymore. However it also doesn't have the Deprecated warning that I see in your screenshot.</div><div>I would think that it would be as important for people who are currently using a plugin to know that it is depreciated as those who are wanting to install one. </div><div>See screenshot below. An alert, like what happens with plugins with updates, for deprecated plugins might be a good idea. </div><div><img src="cid:ii_md4vxccd0" alt="image.png" width="225" height="129" style="margin-right: 0px;"></div><div><br></div><div>Out of curiosity where would the discussion around the issue happen? Here? <a href="https://github.com/qgis/QGIS-Plugins-Website/issues">https://github.com/qgis/QGIS-Plugins-Website/issues</a></div><div><br></div><div><br></div></div><br><div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">On Sat, Jul 12, 2025 at 4:04 AM Richard Duivenvoorde <<a href="mailto:rdmailings@duif.net">rdmailings@duif.net</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">On 11-07-2025 16:33, Sebastian Gutwein via QGIS-Developer wrote:<br>
> Is there a way to determine why it was depreciated?<br>
<br>
Nope, I think it is a decision of the plugin maker.<br>
And I see you are already approaching the dev (using an issue on github).<br>
Another way would be to sent the dev an email (see metadata.txt on github)<br>
<br>
> If there was a security issue or licensing issue would that be reported somewhere?<br>
<br>
There is <a href="mailto:security@qgis.org" target="_blank">security@qgis.org</a>, but I haven't seen something about this plugin.<br>
<br>
If during the approval process 'we' discuss a licensing issue that is mostly discussed via an issue (and I do not see that).<br>
Not sure if Google would play that transparently...<br>
<br>
> It doesn't seem that there is any indication in the plugins manager that flags plugins as depreciated. Is this a security risk?<br>
<br>
You need to check the 'also show deprecated plugins' to actually SEE the plugin.<br>
<br>
With me then the name is grayed out and it is very clear the plugin is deprecated (see screenie).<br>
<br>
Deprecation does not have to do anything with security, it can also be the coder does not want to develop the plugin anymore, or are other (personal) issues. (in this case, maybe Google hinted the person to it's rules about the user of Google services....).<br>
<br>
I see there is no license in the code or rep... but there should be a gpl-licence there, so (then) you would have been free to fork it....<br>
<br>
IF you did not see the plugin normally (without the 'deprication'-checkbox checked), but it showed up in the NEW, THAT would be an bug, I'd say...<br>
<br>
Regards,<br>
<br>
Richard Duivenvoorde</blockquote></div><div><br clear="all"></div><div><br></div><span class="gmail_signature_prefix">-- </span><br><div dir="ltr" class="gmail_signature"><div dir="ltr">___________________________<br><div dir="ltr"><span>Sebastian "Bas* " Gutwein</span></div><div><span><span>*rhymes with Josh <br></span></span></div><div><span><span><br></span></span></div>Regenerative Design Group<br>1 Chevalier Ave<br>Greenfield, Ma 01301<br>Web: <a href="http://regenerativedesigngroup.com" target="_blank">regenerativedesigngroup.com</a><br>(631) 241-1018<br><br><div dir="ltr"><i><span><span>Look close, think big, make change. </span></span></i></div><div dir="ltr"><span></span></div></div></div>