Hello,
Thanks again for the technical work and improving the workflow.
+1 for the lazy consensus on non breaking changes.
Regarding the license topic:
+1 for the metadata field with a spdx license. But take care, it's not
so easy to a have an exhaustive list. Maybe we should move to the PyPi
classifiers since plugins are Python packages and there is already a
work on maintaining a metadata ecosystem, including tooling to check it
(pip install packaging).
Are we okay with the step back to only a non-blocking warning?
Regards
On 27/11/2023 10:50, Lova Andriarimalala via QGIS-Developer wrote:
Hello everyone,
Thank you all. It's truly an honorto work on this project.
I will begin by utilizing QEP to create a QEP that summarizes this
discussion and going forward with the suggestion to make the license
file recommended for now.
I have reviewed the tickets in the backlog and will evaluate their
size. If I come across anything that I don't understand, I will add
comments to seek clarification.
Best regards,
Lova
—**
Image
*Lova Andriarimalala***
*QGIS Full Stack Developer***
Visit http://kartoza.com <http://kartoza.com/> to find out about open
source:
* Desktop GIS programming services
* Geospatial web development
* GIS Training
* Consulting Services
Office: +261(0)34 09 524 73 <tel:+261340952473>
*From: *QGIS-Developer <[email protected]> on
behalf of Matthias Kuhn via QGIS-Developer
<[email protected]>
*Date: *Monday, 27 November 2023 at 12:24 PM
*To: *Tim Sutton <[email protected]>
*Cc: *[email protected] <[email protected]>
*Subject: *Re: [QGIS-Developer] QGIS Full Stack Web Developer Report
Hi Tim,
For the workflow, that sounds great, thanks a lot!
I agree only breaking changes should go "the long way" and for simple
fixes and improvements we should just get them done with low overhead.
Going forward with a small QEP for the license sounds very good.
Regarding the metadata, I would suggest we use the ids from
https://spdx.org/licenses/.
So for the usual QGIS plugin case, that would be
license=GPL-2.0-or-later
On another note, I just added a couple of tickets to the backlog, I am
not able to estimate the size of them, so if they are too complicated,
just don't prioritize them.
Thank you and best regards
Matthias
On Mon, Nov 27, 2023 at 10:15 AM Tim Sutton <[email protected]> wrote:
Hi all
On Mon, Nov 27, 2023 at 1:32 AM Nyall Dawson
<[email protected]> wrote:
On Mon, 27 Nov 2023 at 00:19, Tim Sutton via QGIS-Developer
<[email protected]> wrote:
>
> @Matthias Kuhn and @Julien Moura I fixed the permissions,
the board for Lova is public now. Please feel free to add
items to the backlog and mark them as priority as needed. I
also asked Lova to try to work through all the old issues and
fix / close them as appropriate so we can try to get the
number of tickets down to a small number.
Tim/Lova, thanks for your outstanding efforts and
commitment here!
It's really exciting to see all the love and attention that
the web and plugin infrastructure is getting as a result! 😍
Thanks so much Nyall and all credit goes to Lova who is doing
fantastic work! What I suggest is that moving forward, Lova uses
QEP's too propose and discuss breaking / major workflow changes on
the plugins site. In that QEP he can address:
* what the change is (link back to ticket in QGIS-Django for example)
* what the impact will be
* proposed roll out time line
etc.
And we can discuss and agree these changes there before he goes
ahead with it. For smaller changes, I suggest he 'just get on with
it' - his scrum board is public and you are all welcome to help
prioritise his work.
For the current issue under discussion (license requirements for
plugins), I have asked Lova to make a QEP and synthesize the
discussion there, mainly so he can have a practice run at going
through the QEP process, although I will add my 2c that I like
Matthias' simple solution to the problem (adding license as a line
to the metadata.txt). If I understand you right Matthias, our
metadata would then look like this?:
-----------------------------
[general]
name=QGIS Animation Workbench
description=A plugin to let you build animations in QGIS
about=QGIS Animation Bench exists because we wanted to use all the
awesome cartography features in QGIS and make cool, animated maps!
QGIS already includes the Temporal Manager which allows you to
produce animations for time-based data. But what if you want to
make animations where you travel around the map, zooming in and
out, and perhaps making features on the map wiggle and jiggle as
the animation progresses? That is what the animation workbench
tries to solve...
version=1.1
qgisMinimumVersion=3.0
author=Tim Sutton
[email protected]
repository=https://github.com/timlinux/QGISAnimationPlugin
license=GPLv2
-----------------------------
There is probably another thread to this discussion which is to
understand which license are accepted and which not, but that is a
job for another QEP I guess...!
Regards
Tim
Nyall
8< ----------- snip -----------------
--
------------------------------------------------------------------------------------------
Tim Sutton
Kartoza Co-Founder
Visit http://kartoza.com to find out about open source:
* Desktop GIS programming services
* Geospatial web development
* GIS Training
* Consulting Services
Tim is a member of the QGIS Project Steering Committee
-------------------------------------------------------------------------------------------
_______________________________________________
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
BEGIN:VCARD
VERSION:4.0
EMAIL;PREF=1:[email protected]
EMAIL:[email protected]
FN:Julien Moura
NICKNAME:jmo
ORG:Oslandia;
TITLE:Consultant - Ingénieur développeur
N:Moura;Julien;;;
ADR:;;;;;;France
URL;VALUE=URL:https://static.geotribu.fr
X-MOZILLA-HTML;VALUE=BOOLEAN:TRUE
UID:c6b195b1-5100-402f-bb73-b312bb7289c0
END:VCARD
_______________________________________________
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
