[QGIS-Developer] Adding "Requirements" as optional field/entry/line in metadata.txt

[Stefan Keller]

Ciao Paolo

Thanks for replying.
I've opened this ticket https://issues.qgis.org/issues/21715 .
I'm sorry not being able to promise help. I'm focusing my time on QGIS
Vector Tiles Reader plugin, QGIS bug reporting and providing
educational material for QGIS like OpenSchoolMaps (see English version
of worksheets [1]).

:Stefan

[1] https://openschoolmaps.ch/pages/materialien.html


Am So., 31. März 2019 um 17:10 Uhr schrieb Paolo Cavallini
<cavallini at faunalia.it>:
>
> Agreed, thanks. I suspect there is already a suggestion for this, could
> you please check and open a ticket if not?
> Would you be available helping us to implement it?
> Thanks.
>
> On 31/03/19 15:22, Tom Kralidis wrote:
> > Good idea. Perhaps listing actual Python requirements or pointing to / assessing a requirements.txt type file is pushing it?
> >
> > ..Tom
> >
> > Sent from my iPhone
> >
> >> On Mar 31, 2019, at 08:49, Stefan Keller <sfkeller at gmail.com> wrote:
> >>
> >> Hi
> >>
> >> As a user when searching and browsing for a plugin in QGIS extension
> >> manager or on the website https://plugins.qgis.org/ , I think users
> >> should be informed before hand about the requirements, dependencies
> >> and restrictions of a plugin.
> >>
> >> These are possible requirements, dependencies and restrictions which
> >> come to my mind: The plugin...
> >> * is running only on one platform
> >> * is depending on some other SW to be installed separately (because
> >> it's not included in the QGIS installation),
> >> * requires some registration or account.
> >>
> >> My suggestion is to add an optional field/entry/line in metadata.txt
> >> called "Requirements" where requirements, dependencies and
> >> restrictions are to be described.
> >>
> >> This entry would be mandatory if there exist such requirements. Some
> >> dependencies and restrictions could potentially even be potentially
> >> validated automatically.
> >>
> >> :Stefan
> >>
> >> P.S. I actually also thought about adding a "spatial extends"
> >> attribute in metadata.txt in order to indicate that this plugin only
> >> works for some specific countries or regions. But for now I'd just
> >> prefer that the chapter "Recommendations" on
> >> https://plugins.qgis.org/publish/ is being extended to mention that
> >> spatial limitations to be mentioned in the plugin description!
> >> _______________________________________________
> >> QGIS-Developer mailing list
> >> QGIS-Developer at lists.osgeo.org
> >> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> >> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> > _______________________________________________
> > QGIS-Developer mailing list
> > QGIS-Developer at lists.osgeo.org
> > List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> > Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> >
>
> --
> Paolo Cavallini - www.faunalia.eu
> QGIS.ORG Chair:
> http://planet.qgis.org/planet/user/28/tag/qgis%20board/
> _______________________________________________
> QGIS-Developer mailing list
> QGIS-Developer at lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer