On 11-07-2025 16:33, Sebastian Gutwein via QGIS-Developer wrote:
Is there a way to determine why it was depreciated?
Nope, I think it is a decision of the plugin maker.
And I see you are already approaching the dev (using an issue on github).
Another way would be to sent the dev an email (see metadata.txt on github)
If there was a security issue or licensing issue would that be reported
somewhere?
There is [email protected], but I haven't seen something about this plugin.
If during the approval process 'we' discuss a licensing issue that is mostly
discussed via an issue (and I do not see that).
Not sure if Google would play that transparently...
It doesn't seem that there is any indication in the plugins manager that flags
plugins as depreciated. Is this a security risk?
You need to check the 'also show deprecated plugins' to actually SEE the plugin.
With me then the name is grayed out and it is very clear the plugin is
deprecated (see screenie).
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....).
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....
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...
Regards,
Richard Duivenvoorde
_______________________________________________
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
