Re: [QGIS-Developer] Deprecated plugin
Dear Sebastian and Richard, Sorry for the late reply. The deprecated flag can be set mainly by the plugin's author, but I agree with the idea of adding some notes on why it's marked as such. Out of curiosity , where would the discussion around the issue happen? > Here? https://github.com/qgis/QGIS-Plugins-Website/issues Yes, that would be the main entry. Please feel free to suggest the idea there. I can also help with creating the issue if needed (please just let me know) and work on it later. However, please note that this new field will probably be shown only in the plugin's details on the website. I wonder if some modification is needed from the plugin manager on the desktop side. 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 Tue, 15 Jul 2025 at 22:27, Sebastian Gutwein via QGIS-Developer < [email protected]> wrote: > Thanks Richard, > It does not show up in new anymore. However it also doesn't have the > Deprecated warning that I see in your screenshot. > 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. > See screenshot below. An alert, like what happens with plugins with > updates, for deprecated plugins might be a good idea. > [image: image.png] > > Out of curiosity where would the discussion around the issue happen? Here? > https://github.com/qgis/QGIS-Plugins-Website/issues > > > > On Sat, Jul 12, 2025 at 4:04 AM Richard Duivenvoorde > wrote: > >> 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 > > > > -- > ___ > Sebastian "Bas* " Gutwein > *rhymes with Josh > > Regenerative Design Group > 1 Chevalier Ave > Greenfield, Ma 01301 > Web: regenerativedesigngroup.com > (631) 241-1018 > > *Look close, think big, make change. * > ___ > 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
Re: [QGIS-Developer] Deprecated plugin
Thanks Richard, It does not show up in new anymore. However it also doesn't have the Deprecated warning that I see in your screenshot. 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. See screenshot below. An alert, like what happens with plugins with updates, for deprecated plugins might be a good idea. [image: image.png] Out of curiosity where would the discussion around the issue happen? Here? https://github.com/qgis/QGIS-Plugins-Website/issues On Sat, Jul 12, 2025 at 4:04 AM Richard Duivenvoorde wrote: > 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 -- ___ Sebastian "Bas* " Gutwein *rhymes with Josh Regenerative Design Group 1 Chevalier Ave Greenfield, Ma 01301 Web: regenerativedesigngroup.com (631) 241-1018 *Look close, think big, make change. * ___ 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
Re: [QGIS-Developer] Deprecated plugin
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
[QGIS-Developer] Deprecated plugin
I posted a version of this in the QGIS user list last month and didn't get a response there so I am wondering if this is something that Lova or someone else on the development side would know. I recently installed a plugin called Google Maps LocationSync that showed up in the NEW section of the plugins manager. https://plugins.qgis.org/plugins/GoogleMapsLocationSync/ https://github.com/hrko9gis/GoogleMapsLocationSync I found it to be quite useful and recommended it to a colleague a few days later only to discover that it had been deprecated. Is there a way to determine why it was depreciated? If there was a security issue or licensing issue would that be reported somewhere? It doesn't seem that there is any indication in the plugins manager that flags plugins as depreciated. Is this a security risk? Thanks -Bas-- ___ Sebastian "Bas* " Gutwein *rhymes with Josh Regenerative Design Group 1 Chevalier Ave Greenfield, Ma 01301 Web: regenerativedesigngroup.com (631) 241-1018 *Look close, think big, make change. * ___ 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
