Re: [QGIS-Developer] QGIS Full Stack Web Developer Report

[Lova Andriarimalala via QGIS-Developer]

Hello everyone.

LAST REMINDER FOR THE PLUGINS WEBSITE: As of 03 June 2024, providing a license 
file will be mandatory for any new updates to existing and new plugins 
published according to 
QEP#279.

I've included below the report on this week's maintenance and development of 
the QGIS-related websites.

Deployed PRs on the QGIS plugins website:

  *   Disable LDAP login in the environment template 
file
  *   Integrate sentry into the Django 
project
  *   Update and document makefile
  *   Show the path for the forbidden dir in the child 
folder
  *   Add delay notification in the approval 
email
  *   Show the number of results returned in the 
search
  *   Show the modified date in the model list and 
detail
  *   Fix the responsive navigation 
bar
  *   Explicitly list invalid metadata 
keys
  *   Add aggregate stats to the plugin manager's 
view

Newly merged PR on the QGIS plugins website:

  *   Make plugin license required as of 03 
June

New PR on PRJ.APP (changelog.qgis.org):

  *   Upgrade stacks to Django 4, Postgresql 
16

We successfully migrated the staging plugin server to the new infrastructure. 
You can check it at https://staging.plugins.qgis.org. Please note that login 
with an OSGEO account is not enabled.

Next week, we will deploy the merged changes to the QGIS plugins and QGIS feed 
repositories. I will also:

  *   Update the documentation and readme for each repository according to the 
latest update
  *   Set up an updated server for the changelog website
  *   Work on some of the open issues

Have a nice weekend,
Best regards,

Lova


—
[Image]

Lova Andriarimalala
QGIS Full Stack Developer
Visit 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





From: Lova Andriarimalala 
Date: Friday, 24 May 2024 at 1:58 PM
To: qgis-developer@lists.osgeo.org 
Subject: Re: QGIS Full Stack Web Developer Report
Hello everyone.

IMPORTANT NOTE FOR THE PLUGINS WEBSITE: As of 03 June 2024, providing a license 
file will be mandatory for any new updates to existing and new plugins 
published according to 
QEP#279.

Please find below the report on the maintenance and development of the 
QGIS-related websites for this week:

New PR on QGIS-Hugo:

  *   Fix roadmap counter

Merged PRs on the QGIS plugins website:

  *   Disable LDAP login in the environment template 
file
  *   Integrate sentry into the Django 
project
  *   Update and document makefile
  *   Show the path for the forbidden dir in the child 
folder
  *   Add delay notification in the approval 
email
  *   Show the number of results returned in the 
search
  *   Show the modified date in the model list and 
detail
  *   Fix the responsive navigation 
bar
  *   Explicitly list invalid metadata 
keys
  *   Add an aggregate stats to the plugin manager's 
view

Merged PR on QGIS-Feed:

  *   Remove second in feed form, change displayed format in the 
list

Work in progress:

  *   PRJ.APP (changelog.qgis.org): Upgrade stacks and docker 
compose

Next week, we will deploy the merged changes to the QGIS plugins and QGIS feed 
repositories. I will also:

  *   Continue working on updating the stack on the changelog website
  *   Submit a new PR for the plugins' license requirements.
  *   Migrate the plugins staging website to the new infrastructure

Best regards,

Lova


—
[Image]

Lova Andriarimalala
QGIS Full Stack Developer
Visit 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








___
QGIS-Developer mailing list

Re: [QGIS-Developer] QGIS Full Stack Web Developer Report

[Lova Andriarimalala via QGIS-Developer]

Hello everyone.

IMPORTANT NOTE FOR THE PLUGINS WEBSITE: As of 03 June 2024, providing a license 
file will be mandatory for any new updates to existing and new plugins 
published according to 
QEP#279.

Please find below the report on the maintenance and development of the 
QGIS-related websites for this week:

New PR on QGIS-Hugo:

  *   Fix roadmap counter

Merged PRs on the QGIS plugins website:

  *   Disable LDAP login in the environment template 
file
  *   Integrate sentry into the Django 
project
  *   Update and document makefile
  *   Show the path for the forbidden dir in the child 
folder
  *   Add delay notification in the approval 
email
  *   Show the number of results returned in the 
search
  *   Show the modified date in the model list and 
detail
  *   Fix the responsive navigation 
bar
  *   Explicitly list invalid metadata 
keys
  *   Add an aggregate stats to the plugin manager's 
view

Merged PR on QGIS-Feed:

  *   Remove second in feed form, change displayed format in the 
list

Work in progress:

  *   PRJ.APP (changelog.qgis.org): Upgrade stacks and docker 
compose

Next week, we will deploy the merged changes to the QGIS plugins and QGIS feed 
repositories. I will also:

  *   Continue working on updating the stack on the changelog website
  *   Submit a new PR for the plugins' license requirements.
  *   Migrate the plugins staging website to the new infrastructure

Best regards,

Lova


—
[Image]

Lova Andriarimalala
QGIS Full Stack Developer
Visit 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








___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] QGIS Full Stack Web Developer Report

[Lova Andriarimalala via QGIS-Developer]

Hello everyone.

Please find below the report on the maintenance and development of QGIS-Django, 
QGIS Feed and QGIS-Hugo for this week:

Migration of the QGIS feed website:

  *   We have successfully migrated the QGIS plugins website to an updated 
server. Many thanks to Tim and Dimas.
  *   The QGIS feed website now uses up-to-date stacks and packages such as 
Django 4, Postgresql 16, and the latest Metabase.
  *   Please feel free to share your feedback or create issues about them on 
the QGIS-Feed repository

PRs deployed on the QGIS plugins website:

  *   Scale the uwsgi container
  *   Use internal network to fix uwsgi load 
balancer

PRs deployed on the QGIS-Hugo:

  *   Fix in page anchor scroll
  *   Make the download link on top in the installation 
guide
  *   Change all product link occurrences to 
project
  *   Remove image's black border in get involved 
page
  *   Fix overlapping boxes in membership 
page
  *   Replace twitter with Mastodon
  *   Fix guideline page

New PR for the QGIS plugins website:

  *   Human validation download: 
this is the proposed fix to reduce the server load according to 
https://lists.osgeo.org/pipermail/qgis-user/2024-May/054439.html and 
#402
  *   Update and document makefile

Next week, I will attempt to fix and deploy some open PRs. I will also review 
the issues that need to be addressed in the recent update.

Best regards,

Lova


—
[Image]

Lova Andriarimalala
QGIS Full Stack Developer
Visit 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




From: Lova Andriarimalala 
Date: Monday, 13 May 2024 at 7:40 AM
To: qgis-developer@lists.osgeo.org 
Subject: Re: QGIS Full Stack Web Developer Report
Hello everyone.

Please find below the report on the maintenance and development of QGIS-Django 
and QGIS-Hugo for the last week:

Migration of the QGIS plugins website:

  *   We have successfully migrated the QGIS plugins website to an updated 
server. Many thanks to everyone who helped us achieve this.
  *   The QGIS plugins website now uses up-to-date stacks and packages such as 
Django 4, Postgresql 16, and the latest Metabase.
  *   Please feel free to share your feedback or create issues about them on 
the QGIS-Django repository

New PRs QGIS-Hugo:

  *   Fix in page anchor scroll
  *   Make the download link on top in the installation 
guide
  *   Change all project link occurrences to 
product

This week, I will work on fixing QGIS-Hugo issues, performing maintenance 
tasks, and updating the branding for the QGIS plugin website.

Best regards,
Lova


—
[Image]

Lova Andriarimalala
QGIS Full Stack Developer
Visit 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




From: Lova Andriarimalala 
Date: Friday, 3 May 2024 at 4:33 PM
To: qgis-developer@lists.osgeo.org 
Subject: QGIS Full Stack Web Developer Report
Hello everyone,

IMPORTANT NOTE FOR THE QGIS PLUGINS WEBSITE: We’ve scheduled the migration to 
the updated servers into production for 06 May 2024. During this time, 
uploading new plugins will be disabled and the ability to install plugins may 
be intermittently unavailable.

I mainly focused on the following tasks this week:

  *   Continue working with the QGIS Plugins Site branding 
updates. It’s based on the 
changes made for the PR #374

  *   Some final checks and fixes on the updated servers:

 *   Fix plugins download feature
 *   Fix all the warning status on the monitoring server

Next week, I will focus on post-migration tasks and maintenance. We will also 
continue with the branding update for the QGIS plugins website.

Have a great weekend.

Best regards,
Lova


—
[Image]

Lova Andriarimalala
QGIS Full Stack Developer
Visit 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



___
QGIS-Developer 

Re: [QGIS-Developer] QGIS Full Stack Web Developer Report

[Lova Andriarimalala via QGIS-Developer]

Hello everyone.

Please find below the report on the maintenance and development of QGIS-Django 
and QGIS-Hugo for the last week:

Migration of the QGIS plugins website:

  *   We have successfully migrated the QGIS plugins website to an updated 
server. Many thanks to everyone who helped us achieve this.
  *   The QGIS plugins website now uses up-to-date stacks and packages such as 
Django 4, Postgresql 16, and the latest Metabase.
  *   Please feel free to share your feedback or create issues about them on 
the QGIS-Django repository

New PRs QGIS-Hugo:

  *   Fix in page anchor scroll
  *   Make the download link on top in the installation 
guide
  *   Change all project link occurrences to 
product

This week, I will work on fixing QGIS-Hugo issues, performing maintenance 
tasks, and updating the branding for the QGIS plugin website.

Best regards,
Lova


—
[Image]

Lova Andriarimalala
QGIS Full Stack Developer
Visit 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




From: Lova Andriarimalala 
Date: Friday, 3 May 2024 at 4:33 PM
To: qgis-developer@lists.osgeo.org 
Subject: QGIS Full Stack Web Developer Report
Hello everyone,

IMPORTANT NOTE FOR THE QGIS PLUGINS WEBSITE: We’ve scheduled the migration to 
the updated servers into production for 06 May 2024. During this time, 
uploading new plugins will be disabled and the ability to install plugins may 
be intermittently unavailable.

I mainly focused on the following tasks this week:

  *   Continue working with the QGIS Plugins Site branding 
updates. It’s based on the 
changes made for the PR #374

  *   Some final checks and fixes on the updated servers:

 *   Fix plugins download feature
 *   Fix all the warning status on the monitoring server

Next week, I will focus on post-migration tasks and maintenance. We will also 
continue with the branding update for the QGIS plugins website.

Have a great weekend.

Best regards,
Lova


—
[Image]

Lova Andriarimalala
QGIS Full Stack Developer
Visit 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



___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] QGIS Full Stack Web Developer Report

[Lova Andriarimalala via QGIS-Developer]

Hello everyone,

Please find below the report for this week:

New PR submitted for QGIS-Django:


  *   Add Layer Definition File and 3D Model to the resource 
API
  *   Show the path for the forbidden dir in child 
folder

Still working on:

  *   QGIS-Django - Update site branding to match 
feed.qgis.org: I’ve proposed an 
approach for this issue. Please feel free to share your feedback about it.

New draft PR submitted for QGIS-Django:

  *   Site branding update: this 
is for the issue I’m working on. It’s based on the changes made for the PR 
#374
  *   Add Qt6 support, show min_qt_version and max_qt_version int the 
XML: This is the proposed change 
for #373 according to the (ongoing) discussion at 
https://github.com/qgis/QGIS-Documentation/pull/8982. This will be marked as 
ready depending on the output of the discussion.
  *   Change db collation: It’s 
based on the changes made for PR 
#374. This should fix the issue 
#45. However, it would be great 
if someone could advise me regarding the DB collation change, I was wondering 
if it will have another impact on the application. Considering that it will 
only be applied when migrating to the new server.

Important note: We’ve scheduled the migration to the updated servers into 
production for 06 May 2024. During this time, uploading new plugins will be 
disabled and the ability to install plugins may be intermittently unavailable.


Have a great weekend.

Best regards,
Lova


—
[Image]

Lova Andriarimalala
QGIS Full Stack Developer
Visit 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





From: Lova Andriarimalala 
Date: Friday, 19 April 2024 at 3:44 PM
To: qgis-developer@lists.osgeo.org 
Subject: Re: QGIS Full Stack Web Developer Report
Hello everyone,

Here is the report for this week regarding the maintenance and development of 
the QGIS-Django, QGIS-feed and QGIS Hugo websites:

New PR submitted for QGIS-Django:

  *   Explicitly list invalid metadata 
keys
  *   Show the modified date in the model list and 
detail
  *   Show the number of results returned in the 
search
  *   Add delay notification in the approval 
email
  *   Fix the responsive navigation 
bar

Merged PRs:

  *   QGIS Hugo: Make default currency to 
Euro
  *   QGIS Hugo: Make once-off payment the 
default

Updated server improvements:

  *   We have performed some performance tests on the updated websites using 
`ApacheBench`. We noticed that they were slower than the current ones. 
Therefore, we have put them under temporary domains to perform checks on the 
same configuration and get close results. Some of the static files might be 
cached by Cloudflare.
  *   We also tested the SSL certificate management and the updated websites 
are now available on temporary domains, which are as follows:

 *   https://plugins.kartoza.com for the QGIS plugins website
 *   https://feed.kartoza.com for the QGIS feed website

  *   We have updated the QGIS feed website (the one at 
https://feed.kartoza.com ) with the new look based on QGIS-Hugo (PR 
#72)

Important note: We’ve scheduled the migration of these updated servers into 
production for 06 May 2024. During this time, uploading new plugins will be 
disabled and the ability to install plugins may be intermittently unavailable.

If you have any questions or feedback on these updates, please let us know.

Have a great weekend.

Best regards,
Lova


—
[Image]

Lova Andriarimalala
QGIS Full Stack Developer
Visit 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





From: Lova Andriarimalala 
Date: Friday, 12 April 2024 at 2:35 PM
To: qgis-developer@lists.osgeo.org 
Subject: Re: QGIS Full Stack Web Developer Report
Hello everyone,

Please find below the report regarding the maintenance tasks and development of 
QGIS-Django, QGIS feed and QGIS Hugo websites:

New PR submitted:

  *   QGIS Hugo: Make default currency to 
Euro
 

Re: [QGIS-Developer] QGIS Full Stack Web Developer Report

[Lova Andriarimalala via QGIS-Developer]

Hello everyone,

Here is the report for this week regarding the maintenance and development of 
the QGIS-Django, QGIS-feed and QGIS Hugo websites:

New PR submitted for QGIS-Django:

  *   Explicitly list invalid metadata 
keys
  *   Show the modified date in the model list and 
detail
  *   Show the number of results returned in the 
search
  *   Add delay notification in the approval 
email
  *   Fix the responsive navigation 
bar

Merged PRs:

  *   QGIS Hugo: Make default currency to 
Euro
  *   QGIS Hugo: Make once-off payment the 
default

Updated server improvements:

  *   We have performed some performance tests on the updated websites using 
`ApacheBench`. We noticed that they were slower than the current ones. 
Therefore, we have put them under temporary domains to perform checks on the 
same configuration and get close results. Some of the static files might be 
cached by Cloudflare.
  *   We also tested the SSL certificate management and the updated websites 
are now available on temporary domains, which are as follows:
 *   https://plugins.kartoza.com for the QGIS plugins website
 *   https://feed.kartoza.com for the QGIS feed website
  *   We have updated the QGIS feed website (the one at 
https://feed.kartoza.com ) with the new look based on QGIS-Hugo (PR 
#72)

Important note: We’ve scheduled the migration of these updated servers into 
production for 06 May 2024. During this time, uploading new plugins will be 
disabled and the ability to install plugins may be intermittently unavailable.

If you have any questions or feedback on these updates, please let us know.

Have a great weekend.

Best regards,
Lova


—
[Image]

Lova Andriarimalala
QGIS Full Stack Developer
Visit 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





From: Lova Andriarimalala 
Date: Friday, 12 April 2024 at 2:35 PM
To: qgis-developer@lists.osgeo.org 
Subject: Re: QGIS Full Stack Web Developer Report
Hello everyone,

Please find below the report regarding the maintenance tasks and development of 
QGIS-Django, QGIS feed and QGIS Hugo websites:

New PR submitted:

  *   QGIS Hugo: Make default currency to 
Euro
  *   QGIS Hugo: Make once-off payment the 
default

Merged PR:

  *   QGIS Hugo: Fix header navigation bar and playwright 
test

Updated server improvements:

  *   Update the System Administration Documentation: this is generally related 
to issue #111 on QGIS Django 
but it’s divided into smaller issues on the private repo.
  *   Monitoring server: Add the new servers to a new group

Next week will work on performance improvements on the updated servers.

Have a great weekend.

Best regards,
Lova


—
[Image]

Lova Andriarimalala
QGIS Full Stack Developer
Visit 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





___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] QGIS Full Stack Web Developer Report

[Lova Andriarimalala via QGIS-Developer]

Hello everyone,

Please find below the report regarding the maintenance tasks and development of 
QGIS-Django, QGIS feed and QGIS Hugo websites:

New PR submitted:

  *   QGIS Hugo: Make default currency to 
Euro
  *   QGIS Hugo: Make once-off payment the 
default

Merged PR:

  *   QGIS Hugo: Fix header navigation bar and playwright 
test

Updated server improvements:

  *   Update the System Administration Documentation: this is generally related 
to issue #111 on QGIS Django 
but it’s divided into smaller issues on the private repo.
  *   Monitoring server: Add the new servers to a new group

Next week will work on performance improvements on the updated servers.

Have a great weekend.

Best regards,
Lova


—
[Image]

Lova Andriarimalala
QGIS Full Stack Developer
Visit 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





___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] QGIS Full Stack Web Developer Report

[Lova Andriarimalala via QGIS-Developer]

Hello everyone,

Please look at the report below for updates on the maintenance and development 
of QGIS-Django and QGIS-Feed, for the last two weeks.
Updated sites are now online (not used in production yet) using recent stacks 
such as Django 4 and PostgreSQL 16:

  *   For the QGIS plugins website (QGIS-Django):
 *   Link: http://23.88.115.87/
 *   The PR for this update: https://github.com/qgis/QGIS-Django/pull/374
 *   I’ve submitted a new feed to communicate about the 
maintenance/migration day that is scheduled for 06 May 2024. Anyone with access 
can see it here: https://feed.qgis.org/manage/update/80/
  *   For the QGIS feed website (QGIS-Feed):
 *   Link: https://78.46.126.75/
 *   The PRs for this update: https://github.com/qgis/qgis-feed/pull/78 and 
https://github.com/qgis/qgis-feed/pull/80

Please take a look at them and let us know your thoughts. Your feedback is 
highly appreciated.
Next week, we will continue working on some improvements to these updated sites.

Have a great weekend.

Best regards,
Lova

—
[Image]

Lova Andriarimalala
QGIS Full Stack Developer
Visit 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




From: Lova Andriarimalala 
Date: Friday, 22 March 2024 at 3:29 PM
To: qgis-developer@lists.osgeo.org 
Subject: Re: QGIS Full Stack Web Developer Report
Hello everyone,

Please find below the report for this week regarding the maintenance and 
development updates of QGIS-Django and QGIS-Feed:

  *   Continue with setting up an updated server for the QGIS-Feed
  *   Adding services to monitor the updated server
  *   Working on a new branch based on 
#310 to update the stacks for the 
QGIS-Django project (Django 4, docker-compose services based)

Next week, we will continue working on the maintenance tasks and submit the 
related PRs.

Have a great weekend.

Best regards,
Lova


—
[Image]

Lova Andriarimalala
QGIS Full Stack Developer
Visit 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






From: Lova Andriarimalala 
Date: Friday, 15 March 2024 at 3:57 PM
To: qgis-developer@lists.osgeo.org 
Subject: QGIS Full Stack Web Developer Report
Hello everyone,

Please see the report below for updates on the maintenance and development of 
QGIS-Django and QGIS-Feed, for this week.

  *   Deploy merged changes: QGIS-Django 
#356 and QGIS-Feed 
#70
  *   Submit new PRs:

 *   QGIS-Django #366: Fix GH actions 
test
 *   QGIS-Feed #77: Additional fix for spatial filter 
map

  *   Some improvements in an open PR: QGIS-Django #361: Add playwright CI test 
for plugin management
  *   Maintenance tasks: setting up a monitoring server for the QGIS-related 
websites and an updated server for the QGIS-Feed

Next week, we will continue with maintenance tasks and test some of the 
existing PRs.

Have a great weekend.

Best regards,
Lova


—
[Image]

Lova Andriarimalala
QGIS Full Stack Developer
Visit 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



___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] QGIS Full Stack Web Developer Report

[Lova Andriarimalala via QGIS-Developer]

Hello everyone,

Please find below the report for this week regarding the maintenance and 
development updates of QGIS-Django and QGIS-Feed:

  *   Continue with setting up an updated server for the QGIS-Feed
  *   Adding services to monitor the updated server
  *   Working on a new branch based on 
#310 to update the stacks for the 
QGIS-Django project (Django 4, docker-compose services based)

Next week, we will continue working on the maintenance tasks and submit the 
related PRs.

Have a great weekend.

Best regards,
Lova


—
[Image]

Lova Andriarimalala
QGIS Full Stack Developer
Visit 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






From: Lova Andriarimalala 
Date: Friday, 15 March 2024 at 3:57 PM
To: qgis-developer@lists.osgeo.org 
Subject: QGIS Full Stack Web Developer Report
Hello everyone,

Please see the report below for updates on the maintenance and development of 
QGIS-Django and QGIS-Feed, for this week.

  *   Deploy merged changes: QGIS-Django 
#356 and QGIS-Feed 
#70
  *   Submit new PRs:

 *   QGIS-Django #366: Fix GH actions 
test
 *   QGIS-Feed #77: Additional fix for spatial filter 
map

  *   Some improvements in an open PR: QGIS-Django #361: Add playwright CI test 
for plugin management
  *   Maintenance tasks: setting up a monitoring server for the QGIS-related 
websites and an updated server for the QGIS-Feed

Next week, we will continue with maintenance tasks and test some of the 
existing PRs.

Have a great weekend.

Best regards,
Lova


—
[Image]

Lova Andriarimalala
QGIS Full Stack Developer
Visit 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



___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] QGIS Full Stack Web Developer Report

[Lova Andriarimalala via QGIS-Developer]

Hello everyone,

Please find below a report detailing this week's progress. This week, my focus 
was on:

  *   Doing some maintenance tasks for the QGIS analytics dashboard
  *   Improving the playwright CI end-to-end test for the new website 
(QGIS-Hugo) according to #210. 
I’ve submitted a new PR for this at 
#205.

Next week, we plan to deploy merged changes in QGIS-Django and QGIS-Feed. We 
will also perform maintenance tasks.

Have a great weekend,
Lova


—
[Image]

Lova Andriarimalala
QGIS Full Stack Developer
Visit 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




From: Lova Andriarimalala 
Date: Friday, 1 March 2024 at 2:45 PM
To: qgis-developer@lists.osgeo.org 
Subject: Re: QGIS Full Stack Web Developer Report
Hello everyone,

Please find below a report which details the progress made this week on the 
development of the QGIS-Django, QGIS-Feed and QGIS-Hugo websites.

Deployed PR for QGIS-Django:

  *   Fix plugin detail rating: 
this is a fix for #354
  *   Add local timezone to XML: 
this is a fix for #353.

Merged PR for QGIS-Hugo:

  *   Implement Playwright CI test

Open PR for QGIS-Feed:

  *   Update the design to match 
https://qgis.github.io/QGIS-Hugo/

Still working on:

  *   Improve the playwright CI test

Have a great weekend,
Lova

—
[Image]

Lova Andriarimalala
QGIS Full Stack Developer
Visit 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




From: Lova Andriarimalala 
Date: Friday, 23 February 2024 at 3:59 PM
To: qgis-developer@lists.osgeo.org 
Subject: QGIS Full Stack Web Developer Report
Hello everyone,

Please find below a report which details the progress made this week on the 
development of the plugin and feed website.

Merged PR for plugins website:

  *   [Deployed on staging] Fix plugin detail 
rating: this is a fix for 
#354
  *   [Deployed on staging] Add local timezone to 
XML: this is a fix for 
#353. The cached XML files on 
the staging don’t show this change because they are copied from the production. 
However, we can request a non-cached XML file, for example, 
https://staging.plugins.qgis.org/plugins/plugins.xml?qgis=3.36
Still working on:

  *   Update the design of QGIS-Feed to match 
https://qgis.github.io/QGIS-Hugo/
  *   Implement Playwright CI testing on 
QGIS-Hugo

We will probably deploy the merged changes next week.

Have a great weekend,
Lova


—
[Image]

Lova Andriarimalala
QGIS Full Stack Developer
Visit 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



___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] QGIS Full Stack Web Developer Report

[Lova Andriarimalala via QGIS-Developer]

Hello everyone,

Please find below a report which details the progress made this week on the 
development of the QGIS-Django, QGIS-Feed and QGIS-Hugo websites.

Deployed PR for QGIS-Django:

  *   Fix plugin detail rating: 
this is a fix for #354
  *   Add local timezone to XML: 
this is a fix for #353.

Merged PR for QGIS-Hugo:

  *   Implement Playwright CI test

Open PR for QGIS-Feed:

  *   Update the design to match 
https://qgis.github.io/QGIS-Hugo/

Still working on:

  *   Improve the playwright CI test

Have a great weekend,
Lova

—
[Image]

Lova Andriarimalala
QGIS Full Stack Developer
Visit 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




From: Lova Andriarimalala 
Date: Friday, 23 February 2024 at 3:59 PM
To: qgis-developer@lists.osgeo.org 
Subject: QGIS Full Stack Web Developer Report
Hello everyone,

Please find below a report which details the progress made this week on the 
development of the plugin and feed website.

Merged PR for plugins website:

  *   [Deployed on staging] Fix plugin detail 
rating: this is a fix for 
#354
  *   [Deployed on staging] Add local timezone to 
XML: this is a fix for 
#353. The cached XML files on 
the staging don’t show this change because they are copied from the production. 
However, we can request a non-cached XML file, for example, 
https://staging.plugins.qgis.org/plugins/plugins.xml?qgis=3.36
Still working on:

  *   Update the design of QGIS-Feed to match 
https://qgis.github.io/QGIS-Hugo/
  *   Implement Playwright CI testing on 
QGIS-Hugo

We will probably deploy the merged changes next week.

Have a great weekend,
Lova


—
[Image]

Lova Andriarimalala
QGIS Full Stack Developer
Visit 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



___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] QGIS Full Stack Web Developer Report

[WhereGroup]

Ha, yeah pragmatism is a very good reason. I've battled with mail 
delivery recently in a much smaller project and it was not fun.


Thanks for all your work, you awesome people!

Cheers, Hannes

PS: To be honest, I get a deja vu, so if I ranted about this (without 
offering help or solutions :} ) before in the past, sorry!


On 22.02.24 15:51, Andreas Neumann wrote:


Hi Johannes and Lova,

The current reality is that the QGIS PSC is using Google 
infrastructure (Google Drive, Google Mail, youtube channels; sometimes 
Google Meet) quite extensively. It wouldn't be so easy to swap things 
out. In the PSC meetings we use JITSI, but for the QGIS Open Day it is 
also Google infrastructure, as it scales better for more users. We 
also use GSOC in order to bring in new developers.


We know that some people don't like our usage of Google services, but 
we also need to be pragmatic. Doing more things ourselves with open 
source tools or other alternatives would be possible, but would mean 
that we can spend less time directly on improving QGIS.


Greetings,
Andreas

On 2024-02-22 15:34, Johannes Kröger via QGIS-Developer wrote:


Hi Lova,

if I understand it right, using smtp.gmail.com *will* send all mails 
via Google. I don't know which SMTP host is currently used.


Looking at the MX records of qgis.org it seems like Google is used 
already anyways so I might be barking up an old and rotten tree. :(


It really should not be any of Google's business when people 
communicate with qgis.org addresses.


Thank you!

Cheers, Hannes

On 19.02.24 06:37, Lova Andriarimalala wrote:


Dear Hannes,

Thanks for your feedback. I appreciate that.

> Does this mean that Gmail will be involved in all those mails?

I apologise for that. Indeed, we propose using smtp.gmail.com as 
EMAIL_HOST instead of smtp to fix the email-sending feature since it 
sometimes goes into the spam folder.


However, I think this won't change the account type because we use 
the same as the current email and keep the part `@qgis.org` unless 
I'm mistaken. But maybe my PR's name doesn't reflect that. For now, 
I will update the PR and convert it to a draft.


> Can't a OSGeo mail account be used instead?

I'm not sure of the answer to this, sorry.

Dear @Tim Sutton <mailto:t...@kartoza.com>, could you please advise 
me on that?Thank you.


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 

*From: *QGIS-Developer  
<mailto:qgis-developer-boun...@lists.osgeo.org> on behalf of 
Johannes Kröger (WhereGroup) via QGIS-Developer 
 <mailto:qgis-developer@lists.osgeo.org>

*Date: *Friday, 16 February 2024 at 5:24 PM
*To: *qgis-developer@lists.osgeo.org 
<mailto:qgis-developer@lists.osgeo.org> 
 <mailto:qgis-developer@lists.osgeo.org>

*Subject: *Re: [QGIS-Developer] QGIS Full Stack Web Developer Report

Hey Lova,

thanks for all your great work!

This caught my eye:

> Use Gmail as the email provider 
<https://github.com/qgis/QGIS-Django/pull/356>


Does this mean that Gmail will be involved in all those mails? I 
would be strongly against proactively exposing any data to such a 
company if not absolutely necessary.


Can't a OSGeo mail account be used instead?

It's bad enough that so much mail is already centralized and thus 
available to a single party/company but as long as a user is not 
willingly using Gmail themselves already, it would be great if 
Google (or any other similar third party) was not involved in such 
mails.


Cheers, Hannes

On 16.02.24 13:52, Lova Andriarimalala via QGIS-Developer wrote:

Hello everyone,

I'm starting a new thread because the previous one exceeds the
limit. I've included for you a report which details the progress
made this week on the development of the plugin and feed website.

*New PR for the plugins website:*

  * Use Gmail as the email provider
<https://github.com/qgis/QGIS-Django/pull/356>
  * Set media and static path as the same as in production
<https://github.com/qgis/QGIS-Django/pull/357>
  * Fix plugin detail rating
<https://github.com/qgis/QGIS-Django/pull/359>: this is a
fix for #354 <https://github.com/qgis/QGIS-Django/issues/354>
  * Add local timezone to XML
<https://github.com/qgis/QGIS-Django/pull/360>: this is a
fix for #353 <https://github.com/qgis/QGIS-Django/issues/353>

*New PRs for the feed website:*

  * Use Gmail as the email provider
<https://github.com/qgis/qgis-feed/pull/70>

Next week, I will try to plan the deployment of some of these
PRs. I will also continue to implement the components developed
by Kontur on the QGIS Feed website.

   

Re: [QGIS-Developer] QGIS Full Stack Web Developer Report

[Andreas Neumann via QGIS-Developer]

Hi Johannes and Lova,

The current reality is that the QGIS PSC is using Google infrastructure 
(Google Drive, Google Mail, youtube channels; sometimes Google Meet) 
quite extensively. It wouldn't be so easy to swap things out. In the PSC 
meetings we use JITSI, but for the QGIS Open Day it is also Google 
infrastructure, as it scales better for more users. We also use GSOC in 
order to bring in new developers.


We know that some people don't like our usage of Google services, but we 
also need to be pragmatic. Doing more things ourselves with open source 
tools or other alternatives would be possible, but would mean that we 
can spend less time directly on improving QGIS.


Greetings,
Andreas

On 2024-02-22 15:34, Johannes Kröger via QGIS-Developer wrote:


Hi Lova,

if I understand it right, using smtp.gmail.com *will* send all mails 
via Google. I don't know which SMTP host is currently used.


Looking at the MX records of qgis.org it seems like Google is used 
already anyways so I might be barking up an old and rotten tree. :(


It really should not be any of Google's business when people 
communicate with qgis.org addresses.


Thank you!

Cheers, Hannes

On 19.02.24 06:37, Lova Andriarimalala wrote:

Dear Hannes,

Thanks for your feedback. I appreciate that.


Does this mean that Gmail will be involved in all those mails?


I apologise for that. Indeed, we propose using smtp.gmail.com as 
EMAIL_HOST instead of smtp to fix the email-sending feature since it 
sometimes goes into the spam folder.


However, I think this won't change the account type because we use the 
same as the current email and keep the part `@qgis.org` unless I'm 
mistaken. But maybe my PR's name doesn't reflect that. For now, I will 
update the PR and convert it to a draft.



Can't a OSGeo mail account be used instead?


I'm not sure of the answer to this, sorry.

Dear @Tim Sutton, could you please advise me on that? Thank you.

Best regards,

Lova

--

Lova Andriarimalala

QGIS Full Stack Developer

Visit http://kartoza.com [2] to find out about open source:

* Desktop GIS programming services

* Geospatial web development

* GIS Training

* Consulting Services

Office: +261(0)34 09 524 73 [3]

From: QGIS-Developer  on behalf 
of Johannes Kröger (WhereGroup) via QGIS-Developer 


Date: Friday, 16 February 2024 at 5:24 PM
To: qgis-developer@lists.osgeo.org 
Subject: Re: [QGIS-Developer] QGIS Full Stack Web Developer Report

Hey Lova,

thanks for all your great work!

This caught my eye:


Use Gmail as the email provider [4]


Does this mean that Gmail will be involved in all those mails? I would 
be strongly against proactively exposing any data to such a company if 
not absolutely necessary.


Can't a OSGeo mail account be used instead?

It's bad enough that so much mail is already centralized and thus 
available to a single party/company but as long as a user is not 
willingly using Gmail themselves already, it would be great if Google 
(or any other similar third party) was not involved in such mails.


Cheers, Hannes

On 16.02.24 13:52, Lova Andriarimalala via QGIS-Developer wrote:

Hello everyone,

I'm starting a new thread because the previous one exceeds the limit. 
I've included for you a report which details the progress made this 
week on the development of the plugin and feed website.


New PR for the plugins website:

* Use Gmail as the email provider [4]
* Set media and static path as the same as in production [5]
* Fix plugin detail rating [6]: this is a fix for #354 [7]
* Add local timezone to XML [8]: this is a fix for #353 [9]

New PRs for the feed website:

* Use Gmail as the email provider  [10]

Next week, I will try to plan the deployment of some of these PRs. I 
will also continue to implement the components developed by Kontur on 
the QGIS Feed website.


Have a great weekend,

Lova

--

Lova Andriarimalala

QGIS Full Stack Developer

Visit http://kartoza.com [2] to find out about open source:

* Desktop GIS programming services

* Geospatial web development

* GIS Training

* Consulting Services

Office: +261(0)34 09 524 73 [3]

___

QGIS-Developer mailing list

QGIS-Developer@lists.osgeo.org

List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

--

Johannes Kröger / GIS-Entwickler/-Berater

*

FOSSGIS Konferenz

20.-23. März 2024 in Hamburg

https://www.fossgis-konferenz.de/2024/

WhereGroup-Beiträge auf der FOSSGIS

https://wheregroup.com/unternehmen/aktuelles/

*

WhereGroup GmbH

c/o KK03 GmbH

Lange Reihe 29

20099 Hamburg

Germany

Tel: +49 (0)228 / 90 90 38 - 36

Fax: +49 (0)228 / 90 90 38 - 11

johannes.kroe...@wheregroup.com

www.wheregroup.com [1]

Geschäftsführer:

Olaf Knopp, Peter Stamm

Amtsgericht Bonn, HRB 9885

---


--
Johannes Kröger / GIS

Re: [QGIS-Developer] QGIS Full Stack Web Developer Report

[WhereGroup]

Hi Lova,

if I understand it right, using smtp.gmail.com *will* send all mails via 
Google. I don't know which SMTP host is currently used.


Looking at the MX records of qgis.org it seems like Google is used 
already anyways so I might be barking up an old and rotten tree. :(


It really should not be any of Google's business when people communicate 
with qgis.org addresses.


Thank you!

Cheers, Hannes

On 19.02.24 06:37, Lova Andriarimalala wrote:


Dear Hannes,

Thanks for your feedback. I appreciate that.

> Does this mean that Gmail will be involved in all those mails?

I apologise for that. Indeed, we propose using smtp.gmail.com as 
EMAIL_HOST instead of smtp to fix the email-sending feature since it 
sometimes goes into the spam folder.


However, I think this won’t change the account type because we use the 
same as the current email and keep the part `@qgis.org` unless I’m 
mistaken. But maybe my PR’s name doesn’t reflect that. For now, I will 
update the PR and convert it to a draft.


> Can't a OSGeo mail account be used instead?

I’m not sure of the answer to this, sorry.

Dear @Tim Sutton <mailto:t...@kartoza.com>, could you please advise me 
on that?Thank you.


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 

*From: *QGIS-Developer  on 
behalf of Johannes Kröger (WhereGroup) via QGIS-Developer 


*Date: *Friday, 16 February 2024 at 5:24 PM
*To: *qgis-developer@lists.osgeo.org 
*Subject: *Re: [QGIS-Developer] QGIS Full Stack Web Developer Report

Hey Lova,

thanks for all your great work!

This caught my eye:

> Use Gmail as the email provider 
<https://github.com/qgis/QGIS-Django/pull/356>


Does this mean that Gmail will be involved in all those mails? I would 
be strongly against proactively exposing any data to such a company if 
not absolutely necessary.


Can't a OSGeo mail account be used instead?

It's bad enough that so much mail is already centralized and thus 
available to a single party/company but as long as a user is not 
willingly using Gmail themselves already, it would be great if Google 
(or any other similar third party) was not involved in such mails.


Cheers, Hannes

On 16.02.24 13:52, Lova Andriarimalala via QGIS-Developer wrote:

Hello everyone,

I’m starting a new thread because the previous one exceeds the
limit. I've included for you a report which details the progress
made this week on the development of the plugin and feed website.

*New PR for the plugins website:*

  * Use Gmail as the email provider
<https://github.com/qgis/QGIS-Django/pull/356>
  * Set media and static path as the same as in production
<https://github.com/qgis/QGIS-Django/pull/357>
  * Fix plugin detail rating
<https://github.com/qgis/QGIS-Django/pull/359>: this is a fix
for #354 <https://github.com/qgis/QGIS-Django/issues/354>
  * Add local timezone to XML
<https://github.com/qgis/QGIS-Django/pull/360>: this is a fix
for #353 <https://github.com/qgis/QGIS-Django/issues/353>

*New PRs for the feed website:*

  * Use Gmail as the email provider
<https://github.com/qgis/qgis-feed/pull/70>

Next week, I will try to plan the deployment of some of these PRs.
I will also continue to implement the components developed by
Kontur on the QGIS Feed website.

Have a great weekend,

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 



___

QGIS-Developer mailing list

QGIS-Developer@lists.osgeo.org

List info:https://lists.osgeo.org/mailman/listinfo/qgis-developer

Unsubscribe:https://lists.osgeo.org/mailman/listinfo/qgis-developer

--
Johannes Kröger / GIS-Entwickler/-Berater
*
FOSSGIS Konferenz
20.-23. März 2024 in Hamburg
https://www.fossgis-konferenz.de/2024/
WhereGroup-Beiträge auf der FOSSGIS
https://wheregroup.com/unternehmen/aktuelles/
*
WhereGroup GmbH
c/o KK03 GmbH
Lange Reihe 29
20099 Hamburg
Germany
Tel: +49 (0)228 / 90 90 38 - 36
Fax: +49 (0)228 / 90 90 38 - 11
johannes.kroe...@wheregroup.com
www.wheregroup.com  <http://www.wheregroup.com>
Geschäftsführer:
Olaf Knopp, Peter Stamm
Amtsgericht Bonn, HRB 9885
---


--
Johannes Kröger / GIS-Entwickler/-Berater

***

Re: [QGIS-Developer] QGIS Full Stack Web Developer Report

[Lova Andriarimalala via QGIS-Developer]

Dear Hannes,

Thanks for your feedback. I appreciate that.

> Does this mean that Gmail will be involved in all those mails?
I apologise for that. Indeed, we propose using smtp.gmail.com as EMAIL_HOST 
instead of smtp to fix the email-sending feature since it sometimes goes into 
the spam folder.
However, I think this won’t change the account type because we use the same as 
the current email and keep the part `@qgis.org` unless I’m mistaken. But maybe 
my PR’s name doesn’t reflect that. For now, I will update the PR and convert it 
to a draft.

> Can't a OSGeo mail account be used instead?
I’m not sure of the answer to this, sorry.
Dear @Tim Sutton<mailto:t...@kartoza.com>, could you please advise me on that? 
Thank you.

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




From: QGIS-Developer  on behalf of 
Johannes Kröger (WhereGroup) via QGIS-Developer 
Date: Friday, 16 February 2024 at 5:24 PM
To: qgis-developer@lists.osgeo.org 
Subject: Re: [QGIS-Developer] QGIS Full Stack Web Developer Report

Hey Lova,

thanks for all your great work!

This caught my eye:

> Use Gmail as the email provider<https://github.com/qgis/QGIS-Django/pull/356>

Does this mean that Gmail will be involved in all those mails? I would be 
strongly against proactively exposing any data to such a company if not 
absolutely necessary.

Can't a OSGeo mail account be used instead?

It's bad enough that so much mail is already centralized and thus available to 
a single party/company but as long as a user is not willingly using Gmail 
themselves already, it would be great if Google (or any other similar third 
party) was not involved in such mails.

Cheers, Hannes
On 16.02.24 13:52, Lova Andriarimalala via QGIS-Developer wrote:
Hello everyone,

I’m starting a new thread because the previous one exceeds the limit. I've 
included for you a report which details the progress made this week on the 
development of the plugin and feed website.

New PR for the plugins website:

  *   Use Gmail as the email 
provider<https://github.com/qgis/QGIS-Django/pull/356>
  *   Set media and static path as the same as in 
production<https://github.com/qgis/QGIS-Django/pull/357>
  *   Fix plugin detail rating<https://github.com/qgis/QGIS-Django/pull/359>: 
this is a fix for #354<https://github.com/qgis/QGIS-Django/issues/354>
  *   Add local timezone to XML<https://github.com/qgis/QGIS-Django/pull/360>: 
this is a fix for #353<https://github.com/qgis/QGIS-Django/issues/353>

New PRs for the feed website:

  *   Use Gmail as the email provider 
<https://github.com/qgis/qgis-feed/pull/70>

Next week, I will try to plan the deployment of some of these PRs. I will also 
continue to implement the components developed by Kontur on the QGIS Feed 
website.

Have a great weekend,
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






___

QGIS-Developer mailing list

QGIS-Developer@lists.osgeo.org<mailto:QGIS-Developer@lists.osgeo.org>

List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

--

Johannes Kröger / GIS-Entwickler/-Berater



*

FOSSGIS Konferenz

20.-23. März 2024 in Hamburg

https://www.fossgis-konferenz.de/2024/



WhereGroup-Beiträge auf der FOSSGIS

https://wheregroup.com/unternehmen/aktuelles/

*



WhereGroup GmbH

c/o KK03 GmbH

Lange Reihe 29

20099 Hamburg

Germany



Tel: +49 (0)228 / 90 90 38 - 36

Fax: +49 (0)228 / 90 90 38 - 11



johannes.kroe...@wheregroup.com<mailto:johannes.kroe...@wheregroup.com>

www.wheregroup.com<http://www.wheregroup.com>

Geschäftsführer:

Olaf Knopp, Peter Stamm

Amtsgericht Bonn, HRB 9885

---
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] QGIS Full Stack Web Developer Report

[Greg Troxel via QGIS-Developer]

"Johannes Kröger (WhereGroup) via QGIS-Developer"
 writes:

> https://github.com/qgis/QGIS-Django/pull/356;>Use Gmail
> as the email provider
>
> Does this mean that Gmail will be involved in all those mails? I
> would be strongly against proactively exposing any data to such a
> company if not absolutely necessary.
>
> Can't a OSGeo mail account be used instead?
>
> It's bad enough that so much mail is already centralized and thus
> available to a single party/company but as long as a user is not
> willingly using Gmail themselves already, it would be great if
> Google (or any other similar third party) was not involved in such
> mails.

me too

I don't really understand what is going on, but I think the less
anything uses google anything, the better.
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] QGIS Full Stack Web Developer Report

[WhereGroup]

Hey Lova,

thanks for all your great work!

This caught my eye:

Use Gmail as the email provider 



Does this mean that Gmail will be involved in all those mails? I would 
be strongly against proactively exposing any data to such a company if 
not absolutely necessary.


Can't a OSGeo mail account be used instead?

It's bad enough that so much mail is already centralized and thus 
available to a single party/company but as long as a user is not 
willingly using Gmail themselves already, it would be great if Google 
(or any other similar third party) was not involved in such mails.


Cheers, Hannes

On 16.02.24 13:52, Lova Andriarimalala via QGIS-Developer wrote:


Hello everyone,

I’m starting a new thread because the previous one exceeds the limit. 
I've included for you a report which details the progress made this 
week on the development of the plugin and feed website.


*New PR for the plugins website:*

  * Use Gmail as the email provider

  * Set media and static path as the same as in production

  * Fix plugin detail rating
: this is a fix for
#354 
  * Add local timezone to XML
: this is a fix for
#353 

*New PRs for the feed website:*

  * Use Gmail as the email provider


Next week, I will try to plan the deployment of some of these PRs. I 
will also continue to implement the components developed by Kontur on 
the QGIS Feed website.


Have a great weekend,

Lova

—**

Image

*Lova Andriarimalala***

*QGIS Full Stack Developer***

Visit 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 


___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info:https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe:https://lists.osgeo.org/mailman/listinfo/qgis-developer


--
Johannes Kröger / GIS-Entwickler/-Berater

*
FOSSGIS Konferenz
20.-23. März 2024 in Hamburg
https://www.fossgis-konferenz.de/2024/

WhereGroup-Beiträge auf der FOSSGIS
https://wheregroup.com/unternehmen/aktuelles/
*

WhereGroup GmbH
c/o KK03 GmbH
Lange Reihe 29
20099 Hamburg
Germany

Tel: +49 (0)228 / 90 90 38 - 36
Fax: +49 (0)228 / 90 90 38 - 11

johannes.kroe...@wheregroup.com
www.wheregroup.com
Geschäftsführer:
Olaf Knopp, Peter Stamm
Amtsgericht Bonn, HRB 9885
---
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] QGIS Full Stack Web Developer Report

[Lova Andriarimalala via QGIS-Developer]

Hello everyone,

Please find below a report which details the progress made this week on the 
development of the plugin and feed website.

Merged PRs for the plugin website:

  *   [Deployed] Show review form for style 
managers
  *   [Deployed] Fix icons in style list for 
mobile
  *   [Deployed] Preserve non-ASCII characters when downloading a 
zip
  *   [Deployed] Show the ID in plugin detail 
page
  *   [Deployed] Add note for email usage in the plugin upload 
page
  *   [Deployed] Get static and media root from the 
environments
  *   [Deployed] Fix svg icons display issue in plugin list and plugin 
detail
  *   [Deployed] Multi parent folders 
validator
  *   [Deployed] Update repository url when creating or updating a plugin 
version

Merged PRs for the plugin website:

  *   [Not deployed yet] Subclass OSMWidget to use ol 7.2.2 in Django 
3

Next week, I will work on the email-sending issue for both sites and also try 
to solve some of the issues on the QGIS Django repo.

Have a great weekend,
Lova


—
[Image]

Lova Andriarimalala
QGIS Full Stack Developer
Visit 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




From: Lova Andriarimalala 
Date: Friday, 2 February 2024 at 3:51 PM
To: Lova Andriarimalala 
Subject: Re: QGIS Full Stack Web Developer Report
Hello everyone,

Please find below a report detailing the progress made this week on developing 
the plugin and feed website.

Newly open PRs:

  *   Fix icons in style list for 
mobile: this is for 
#131
  *   Subclass OSMWidget to use ol 7.2.2 in Django 
3: this is another method to fix 
#56

Merged PRs for the plugin website:
Most of these PRs have been deployed on staging.plugins.qgis.org for now. 
Please feel free to check them or submit feedback. We are planning to deploy 
them on the production next week.

  *   [Deployed on staging] Fix/logout on profile 
button
  *   [Deployed] Split media and static 
folders
  *   [Deployed on staging] Preserve non-ASCII characters when downloading a 
zip
  *   [Deployed on staging] Show the ID in plugin detail 
page
  *   [Deployed on staging] Add note for email usage in the plugin upload 
page
  *   [Deployed on staging] Get static and media root from the 
environments
  *   [Deployed on staging] Fix svg icons display issue in plugin list and 
plugin detail
  *   [Deployed on staging] Multi parent folders 
validator
  *   [Deployed on staging] Update repository url when creating or updating a 
plugin version
  *   [Deployed] Show plugins with patch versions in plugin 
list

Merged PRs for the feed website:

  *   [Deployed] Add dbbackups service to 
docker-compose
  *   [Deployed] Show a raw version of the 
feeds
  *   [Deployed] Add content char counter, improve invalid form 
handling
  *   [Deployed] Add a field to specify reviewers when submitting a new feed 
item: needs to configure email 
variables on the server.
  *   [Not yet deployed] Use python 3.8 to install Django 
4 and Upgrade to Django 4 to fix OL 
map: they need other stack updates.

Next week, we will continue the deployment on plugins.qgis.org.

Have a great weekend,
Lova


—
[Image]

Lova Andriarimalala
QGIS Full Stack Developer
Visit 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





From: Lova Andriarimalala 
Date: Friday, 26 January 2024 at 4:22 PM
To: Lova Andriarimalala 
Subject: Re: QGIS Full Stack 

Re: [QGIS-Developer] QGIS Full Stack Web Developer Report

[Lova Andriarimalala via QGIS-Developer]

Hello everyone,

I've included a report below which details the progress made this week on the 
development of the plugin and feed website.

PRs open:

  1.  QGIS-Django (plugins.qgis.org):

  *   Add maintainer field to plugin 
update
  *   Fix different displayed date
  *   Upgrade project to Django 3/Python 
3.7
  *   Hide login button when logged 
out
  *   Show plugins with patch versions in plugin 
list
  *   Add token based authentication 
feature: some improvements have 
been made according to the latest comments
  *   Add command to organize old plugin version 
packages
  *   Keep approve status when updating 
style
  *   Add an aggregate stats to the plugin manager's 
view
  *   Disable matomo cookies 
tracking


  1.  QGIS-Feed (feed.qgis.org):

  *   Add characters counter, improve invalid form 
handling
  *   Upgrade to Django 4 to fix OL 
map
  *   Show a raw version of the feeds
  *   Add a field to specify reviewers when submitting a new feed 
item

PR merged for QGIS-Feed (feed.qgis.org):

  *   Configure makefile, update README for docker 
usage

Just to inform you, the 
QEP concerning 
the license requirements is now closed.

Wishing you a joyful holiday season and a fantastic New Year!

Lova
—
[Image]

Lova Andriarimalala
QGIS Full Stack Developer
Visit 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





From: Lova Andriarimalala 
Date: Friday, 15 December 2023 at 7:23 PM
To: qgis-developer@lists.osgeo.org 
Subject: Re: QGIS Full Stack Web Developer Report
Hello everyone,
I've included below a report detailing this week's progress on developing the 
plugin and the feed website.

PRs open:

  *   Add maintainer field to plugin 
update
  *   Fix different displayed date
  *   Upgrade project to Django 3/Python 
3.7
  *   Hide login button when logged 
out
  *   Show plugins with patch versions in plugin 
list
  *   Add token based authentication 
feature: some changes have been 
made to this PR. Please find the updated description at: 
https://github.com/qgis/QGIS-Django/pull/326#issuecomment-1853678895
  *   Add command to organize old plugin version 
packages
  *   Keep approve status when updating 
style
  *   Add an aggregate stats to the plugin manager's 
view
  *   Add characters counter, improve invalid form 
handling

Still working on:

  *   Expose somewhere the xml feed address in the QGIS feed admin 
backend

Just to inform you, the 
QEP concerning 
the license requirements is currently open. The deadline for submitting 
comments and making a decision about it is scheduled for 22 December 2023.

Have a great weekend,
Lova



From: Lova Andriarimalala 
Date: Friday, 8 December 2023 at 3:48 PM
To: qgis-developer@lists.osgeo.org 
Subject: Re: QGIS Full Stack Web Developer Report
Hello everyone,
I've included below a report detailing the progress made on developing the 
plugin and the feed website for this week.
Please note that the 
QEP concerning 
the license requirements is currently open. The deadline for submitting 
comments and making a decision about it is scheduled for 22 December 2023.
PRs open:

  *   Add maintainer field to plugin 
update
  *   Fix different displayed date
  *   Upgrade project to Django 3/Python 
3.7
  *   Hide login button when logged 
out
  *   Show plugins with patch versions in 

Re: [QGIS-Developer] QGIS Full Stack Web Developer Report

[Lova Andriarimalala via QGIS-Developer]

Hello everyone,
I've included below a report detailing this week's progress on developing the 
plugin and the feed website.

PRs open:

  *   Add maintainer field to plugin 
update
  *   Fix different displayed date
  *   Upgrade project to Django 3/Python 
3.7
  *   Hide login button when logged 
out
  *   Show plugins with patch versions in plugin 
list
  *   Add token based authentication 
feature: some changes have been 
made to this PR. Please find the updated description at: 
https://github.com/qgis/QGIS-Django/pull/326#issuecomment-1853678895
  *   Add command to organize old plugin version 
packages
  *   Keep approve status when updating 
style
  *   Add an aggregate stats to the plugin manager's 
view
  *   Add characters counter, improve invalid form 
handling

Still working on:

  *   Expose somewhere the xml feed address in the QGIS feed admin 
backend

Just to inform you, the 
QEP concerning 
the license requirements is currently open. The deadline for submitting 
comments and making a decision about it is scheduled for 22 December 2023.

Have a great weekend,
Lova



From: Lova Andriarimalala 
Date: Friday, 8 December 2023 at 3:48 PM
To: qgis-developer@lists.osgeo.org 
Subject: Re: QGIS Full Stack Web Developer Report
Hello everyone,
I've included below a report detailing the progress made on developing the 
plugin and the feed website for this week.
Please note that the 
QEP concerning 
the license requirements is currently open. The deadline for submitting 
comments and making a decision about it is scheduled for 22 December 2023.
PRs open:

  *   Add maintainer field to plugin 
update
  *   Fix different displayed date
  *   Upgrade project to Django 3/Python 
3.7
  *   Hide login button when logged 
out
  *   Show plugins with patch versions in plugin 
list
  *   Add token based authentication 
feature
  *   Add command to organize old plugin version 
packages
  *   Keep approve status when updating 
style
  *   Add characters counter, improve invalid form 
handling

PR merged:

  *   Fix errors in GH action coverage 
test

Still working on:

  *   Design/Approach for updating site branding to match 
feed.qgis.org. I’ve made a 
proposed approach for it. Please don't hesitate to share your comments or ask 
any questions you may have.
  *   Testing model upload on plugins.qgis.org

Have a great weekend,
Lova

—
[Image]

Lova Andriarimalala
QGIS Full Stack Developer
Visit 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




From: Lova Andriarimalala 
Date: Friday, 1 December 2023 at 4:20 PM
To: qgis-developer@lists.osgeo.org 
Subject: Re: QGIS Full Stack Web Developer Report
Hello everyone,
Please find below a report detailing the progress made on the development of 
the plugin website for this week.
QEP Open:

  *   License requirements for plugins on 
plugins.qgis.org

PRs open:

  *   Fix errors in GH action coverage 
test
  *   Add maintainer field to plugin 
update
  *   Fix different displayed date
  *   Upgrade project to Django 3/Python 
3.7

PR merged:

  *   Add links to plugin details 
tabs
  *   Making license file not required for 
now

Still working on:

  *   Hide logout button when logged 
out

Have a great weekend,
Lova

—
[Image]

Lova Andriarimalala
QGIS Full Stack Developer
Visit http://kartoza.com to find out 

Re: [QGIS-Developer] QGIS Full Stack Web Developer Report

[Lova Andriarimalala via QGIS-Developer]

Dear Nicolas Cadieux,

Sure, I’ve opened an issue for this improvement at 
https://github.com/qgis/QGIS-Django/issues/330.

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




From: Nicolas Cadieux 
Date: Friday, 8 December 2023 at 8:53 PM
To: Lova Andriarimalala 
Cc: qgis-developer@lists.osgeo.org 
Subject: Re: [QGIS-Developer] QGIS Full Stack Web Developer Report
Hi,

If possible, can we place all 3 models in a “group” or “project?” Each model 
depends on the other one but currently, they must be upload one at a time.  
That could be a good improvement to the server.

Good luck!
Nicolas Cadieux


Le 7 déc. 2023 à 21:57, Lova Andriarimalala  a écrit :

Dear Nicolas Cadieux,

I apologize for the delay and appreciate your patience. We are actively 
addressing the issue to enhance both the efficiency of the model feature and 
the reliability of the backup system. We will notify you as soon as you can 
proceed with re-uploading.

Thank you for your understanding and cooperation.

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





From: Nicolas Cadieux 
Date: Sunday, 3 December 2023 at 3:40 AM
To: Lova Andriarimalala 
Cc: qgis-developer@lists.osgeo.org 
Subject: Re: [QGIS-Developer] QGIS Full Stack Web Developer Report
Hi,
Any news on when I can upload?
Keep up the good work!
Nicolas Cadieux

Le 30 nov. 2023 à 05:45, Lova Andriarimalala via QGIS-Developer 
 a écrit :

Hello everyone,

The PR regarding the soft requirements (non-blocking warning) for the plugin 
license is now merged and deployed.

Best regards.
Lova
—


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




From: Lova Andriarimalala 
Date: Monday, 27 November 2023 at 4:34 PM
To: Julien Moura , qgis-developer@lists.osgeo.org 

Subject: Re: [QGIS-Developer] QGIS Full Stack Web Developer Report
Dear Julien,

I've created a new PR for this fix 
here<https://github.com/qgis/QGIS-Django/pull/314>. Please feel free to ask or 
add comments if you have any concerns about it.

Best regards.

—


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




From: Lova Andriarimalala 
Date: Monday, 27 November 2023 at 4:12 PM
To: Julien Moura , qgis-developer@lists.osgeo.org 

Subject: Re: [QGIS-Developer] QGIS Full Stack Web Developer Report
Dear Julien,

It is a pleasure for me to work on the project.
I’ve created a 
QEP<https://github.com/qgis/QGIS-Enhancement-Proposals/issues/279> that 
summarizes this discussion. As suggested, I think we can go forward with the 
non-blocking warning for now and implement licensing requirements on schedule. 
I'll be creating a documented PR for this fix shortly.

Best regards,
Lova
—


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





From: QGIS-Developer  on behalf of 
Julien Moura via QGIS-Developer 
Date: Monday, 27 November 2023 at 2:41 PM
To: qgis-developer@lists.osgeo.org 
Subject: Re: [QGIS-Developer] QGIS Full Stack Web Developer Report

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 honor to 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 t

Re: [QGIS-Developer] QGIS Full Stack Web Developer Report

[Nicolas Cadieux via QGIS-Developer]

Hi,If possible, can we place all 3 models in a “group” or “project?” Each model depends on the other one but currently, they must be upload one at a time.  That could be a good improvement to the server.Good luck!Nicolas CadieuxLe 7 déc. 2023 à 21:57, Lova Andriarimalala  a écrit :







Dear Nicolas Cadieux,
 
I apologize for the delay and appreciate your patience. We are actively addressing the issue to enhance both the efficiency of the model feature and the reliability of the backup system. We will
 notify you as soon as you can proceed with re-uploading.
 
Thank you for your understanding and cooperation. 
 
Best regards,
Lova
 


—

 
Lova Andriarimalala
QGIS Full Stack Developer
Visit 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
 


 
 
 
 



From:
Nicolas Cadieux 
Date: Sunday, 3 December 2023 at 3:40 AM
To: Lova Andriarimalala 
Cc: qgis-developer@lists.osgeo.org 
Subject: Re: [QGIS-Developer] QGIS Full Stack Web Developer Report

Hi,

Any news on when I can upload?


Keep up the good work!

Nicolas Cadieux






Le 30 nov. 2023 à 05:45, Lova Andriarimalala via QGIS-Developer  a écrit :




 
Hello everyone,
 
The PR regarding the soft requirements (non-blocking warning) for the plugin license is now merged and deployed.
 
Best regards.
Lova


—



 
Lova Andriarimalala
QGIS Full Stack Developer
Visit 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
 


 
 
 



From:
Lova Andriarimalala 
Date: Monday, 27 November 2023 at 4:34 PM
To: Julien Moura , qgis-developer@lists.osgeo.org 
Subject: Re: [QGIS-Developer] QGIS Full Stack Web Developer Report

Dear Julien,
 
I've created a new PR for this fix
here. Please feel free to ask or add comments if you have any concerns about it.
 
Best regards.
 


—



 
Lova Andriarimalala
QGIS Full Stack Developer
Visit 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
 


 
 
 



From:
Lova Andriarimalala 
Date: Monday, 27 November 2023 at 4:12 PM
To: Julien Moura , qgis-developer@lists.osgeo.org 
Subject: Re: [QGIS-Developer] QGIS Full Stack Web Developer Report

Dear Julien,
 
It is a pleasure for me to work on the project.
I’ve created a 
QEP that summarizes this discussion. As suggested, I think we can go forward with the
 non-blocking warning for now and implement licensing requirements on schedule. I'll be creating a documented PR for this fix shortly.
 
Best regards,
Lova


—



 
Lova Andriarimalala
QGIS Full Stack Developer
Visit 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
 


 
 
 
 



From:
QGIS-Developer  on behalf of Julien Moura via QGIS-Developer 
Date: Monday, 27 November 2023 at 2:41 PM
To: qgis-developer@lists.osgeo.org 
Subject: Re: [QGIS-Developer] QGIS Full Stack Web Developer Report

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 honor to 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
 
 


—



 
Lova Andriarimalala
QGIS Full Stack Developer
Visit 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
 


 
 



From:
QGIS-Developer 
 on behalf of Matthias Kuhn via QGIS-Developer 
Date: Monday, 27 November 2023 at 12:24 PM
To: Tim Sutton 
Cc: qgis-developer@lists.osgeo.org

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 wi

Re: [QGIS-Developer] QGIS Full Stack Web Developer Report

[Lova Andriarimalala via QGIS-Developer]

Hello everyone,
I've included below a report detailing the progress made on developing the 
plugin and the feed website for this week.
Please note that the 
QEP concerning 
the license requirements is currently open. The deadline for submitting 
comments and making a decision about it is scheduled for 22 December 2023.
PRs open:

  *   Add maintainer field to plugin 
update
  *   Fix different displayed date
  *   Upgrade project to Django 3/Python 
3.7
  *   Hide login button when logged 
out
  *   Show plugins with patch versions in plugin 
list
  *   Add token based authentication 
feature
  *   Add command to organize old plugin version 
packages
  *   Keep approve status when updating 
style
  *   Add characters counter, improve invalid form 
handling

PR merged:

  *   Fix errors in GH action coverage 
test

Still working on:

  *   Design/Approach for updating site branding to match 
feed.qgis.org. I’ve made a 
proposed approach for it. Please don't hesitate to share your comments or ask 
any questions you may have.
  *   Testing model upload on plugins.qgis.org

Have a great weekend,
Lova

—
[Image]

Lova Andriarimalala
QGIS Full Stack Developer
Visit 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




From: Lova Andriarimalala 
Date: Friday, 1 December 2023 at 4:20 PM
To: qgis-developer@lists.osgeo.org 
Subject: Re: QGIS Full Stack Web Developer Report
Hello everyone,
Please find below a report detailing the progress made on the development of 
the plugin website for this week.
QEP Open:

  *   License requirements for plugins on 
plugins.qgis.org

PRs open:

  *   Fix errors in GH action coverage 
test
  *   Add maintainer field to plugin 
update
  *   Fix different displayed date
  *   Upgrade project to Django 3/Python 
3.7

PR merged:

  *   Add links to plugin details 
tabs
  *   Making license file not required for 
now

Still working on:

  *   Hide logout button when logged 
out

Have a great weekend,
Lova

—
[Image]

Lova Andriarimalala
QGIS Full Stack Developer
Visit 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



From: Lova Andriarimalala 
Date: Friday, 24 November 2023 at 4:06 PM
To: qgis-developer@lists.osgeo.org 
Subject: QGIS Full Stack Web Developer Report
Hello everyone,

Please find below a report detailing the progress made on the development of 
the feed and plugins website for this week.
I'm writing in a new email object because of the ongoing discussion about the 
plugin LICENSE requirements and the management changes: 
https://lists.osgeo.org/pipermail/qgis-developer/2023-November/066257.html



PRs open:

  *   Upgrade project to Django 3/Python 
3.7

 *   This PR is based on an existing PR: Upgrade stacks and docker compose 
#257
 *   Upgrade Django package according to this issue: Upgrade project to 
Django 4/Python 3.7+? #54
PR merged:

  *   Add support for changing the plugin 
name
  *   Add command to fix none in search 
results
  *   Show more records, records items per 
page
  *   Specify tag page title and other plugin page 
title
  *   Make LICENSE file as required in the plugin 
package
  *   Fix license requirement
  *   Remove lat filters on the home 
page
Still working on:

  *   No image preview for models and 3D models and they are not 

Re: [QGIS-Developer] QGIS Full Stack Web Developer Report

[Lova Andriarimalala via QGIS-Developer]

Dear Nicolas Cadieux,

I apologize for the delay and appreciate your patience. We are actively 
addressing the issue to enhance both the efficiency of the model feature and 
the reliability of the backup system. We will notify you as soon as you can 
proceed with re-uploading.

Thank you for your understanding and cooperation.

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





From: Nicolas Cadieux 
Date: Sunday, 3 December 2023 at 3:40 AM
To: Lova Andriarimalala 
Cc: qgis-developer@lists.osgeo.org 
Subject: Re: [QGIS-Developer] QGIS Full Stack Web Developer Report
Hi,
Any news on when I can upload?
Keep up the good work!
Nicolas Cadieux


Le 30 nov. 2023 à 05:45, Lova Andriarimalala via QGIS-Developer 
 a écrit :

Hello everyone,

The PR regarding the soft requirements (non-blocking warning) for the plugin 
license is now merged and deployed.

Best regards.
Lova
—


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




From: Lova Andriarimalala 
Date: Monday, 27 November 2023 at 4:34 PM
To: Julien Moura , qgis-developer@lists.osgeo.org 

Subject: Re: [QGIS-Developer] QGIS Full Stack Web Developer Report
Dear Julien,

I've created a new PR for this fix 
here<https://github.com/qgis/QGIS-Django/pull/314>. Please feel free to ask or 
add comments if you have any concerns about it.

Best regards.

—


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




From: Lova Andriarimalala 
Date: Monday, 27 November 2023 at 4:12 PM
To: Julien Moura , qgis-developer@lists.osgeo.org 

Subject: Re: [QGIS-Developer] QGIS Full Stack Web Developer Report
Dear Julien,

It is a pleasure for me to work on the project.
I’ve created a 
QEP<https://github.com/qgis/QGIS-Enhancement-Proposals/issues/279> that 
summarizes this discussion. As suggested, I think we can go forward with the 
non-blocking warning for now and implement licensing requirements on schedule. 
I'll be creating a documented PR for this fix shortly.

Best regards,
Lova
—


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





From: QGIS-Developer  on behalf of 
Julien Moura via QGIS-Developer 
Date: Monday, 27 November 2023 at 2:41 PM
To: qgis-developer@lists.osgeo.org 
Subject: Re: [QGIS-Developer] QGIS Full Stack Web Developer Report

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 honor to 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


—


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



From: QGIS-Developer 
<mailto:qgis-developer-boun...@lists.osgeo.org>
 on behalf of Matthias Kuhn via QGIS-Developer 
<mailto:qgis-developer@lists.osgeo.org>
Date: Monday, 27 November 2023 at 12:24 PM
To: Tim Sutton <mailto:t...@kartoza.com>
Cc: qgis-developer@lists.osgeo.org<mailto:qgis-developer@lists.osgeo.org> 
<mailto:qgis-developer@lists.osgeo.org>
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 si

Re: [QGIS-Developer] QGIS Full Stack Web Developer Report

[Nicolas Cadieux via QGIS-Developer]

Hi,Any news on when I can upload?Keep up the good work!Nicolas CadieuxLe 30 nov. 2023 à 05:45, Lova Andriarimalala via QGIS-Developer  a écrit :







Hello everyone,
 
The PR regarding the soft requirements (non-blocking warning) for the plugin license is now merged and deployed.
 
Best regards.
Lova


—

 
Lova Andriarimalala
QGIS Full Stack Developer
Visit 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
 


 
 
 



From:
Lova Andriarimalala 
Date: Monday, 27 November 2023 at 4:34 PM
To: Julien Moura , qgis-developer@lists.osgeo.org 
Subject: Re: [QGIS-Developer] QGIS Full Stack Web Developer Report

Dear Julien,
 
I've created a new PR for this fix
here. Please feel free to ask or add comments if you have any concerns about it.
 
Best regards.
 


—

 
Lova Andriarimalala
QGIS Full Stack Developer
Visit 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
 


 
 
 



From:
Lova Andriarimalala 
Date: Monday, 27 November 2023 at 4:12 PM
To: Julien Moura , qgis-developer@lists.osgeo.org 
Subject: Re: [QGIS-Developer] QGIS Full Stack Web Developer Report

Dear Julien,
 
It is a pleasure for me to work on the project.
I’ve created a 
QEP that summarizes this discussion. As suggested, I think we can go forward with the non-blocking warning for now and implement licensing requirements on schedule. I'll be creating a documented PR for this fix shortly.
 
Best regards,
Lova


—

 
Lova Andriarimalala
QGIS Full Stack Developer
Visit 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
 


 
 
 
 



From:
QGIS-Developer  on behalf of Julien Moura via QGIS-Developer 
Date: Monday, 27 November 2023 at 2:41 PM
To: qgis-developer@lists.osgeo.org 
Subject: Re: [QGIS-Developer] QGIS Full Stack Web Developer Report

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 honor to 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
 
 


—

 
Lova Andriarimalala
QGIS Full Stack Developer
Visit 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
 


 
 



From:
QGIS-Developer 
 on behalf of Matthias Kuhn via QGIS-Developer

Date: Monday, 27 November 2023 at 12:24 PM
To: Tim Sutton 
Cc: qgis-developer@lists.osgeo.org

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 <t...@kartoza.com> wrote:





Hi all


 


On Mon, Nov 27, 2023 at 1:32 AM Nyall Dawson <nyall.daw...@gmail.com> wrote:




On Mon, 27 Nov 2023 at 00:19, Tim Sutton via QGIS-Developer <qgis-developer@lists.osgeo.org> 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, t

Re: [QGIS-Developer] QGIS Full Stack Web Developer Report

[Lova Andriarimalala via QGIS-Developer]

Hello everyone,
Please find below a report detailing the progress made on the development of 
the plugin website for this week.
QEP Open:

  *   License requirements for plugins on 
plugins.qgis.org

PRs open:

  *   Fix errors in GH action coverage 
test
  *   Add maintainer field to plugin 
update
  *   Fix different displayed date
  *   Upgrade project to Django 3/Python 
3.7

PR merged:

  *   Add links to plugin details 
tabs
  *   Making license file not required for 
now

Still working on:

  *   Hide logout button when logged 
out

Have a great weekend,
Lova

—
[Image]

Lova Andriarimalala
QGIS Full Stack Developer
Visit 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



From: Lova Andriarimalala 
Date: Friday, 24 November 2023 at 4:06 PM
To: qgis-developer@lists.osgeo.org 
Subject: QGIS Full Stack Web Developer Report
Hello everyone,

Please find below a report detailing the progress made on the development of 
the feed and plugins website for this week.
I'm writing in a new email object because of the ongoing discussion about the 
plugin LICENSE requirements and the management changes: 
https://lists.osgeo.org/pipermail/qgis-developer/2023-November/066257.html


PRs open:

  *   Upgrade project to Django 3/Python 
3.7

 *   This PR is based on an existing PR: Upgrade stacks and docker compose 
#257
 *   Upgrade Django package according to this issue: Upgrade project to 
Django 4/Python 3.7+? #54
PR merged:

  *   Add support for changing the plugin 
name
  *   Add command to fix none in search 
results
  *   Show more records, records items per 
page
  *   Specify tag page title and other plugin page 
title
  *   Make LICENSE file as required in the plugin 
package
  *   Fix license requirement
  *   Remove lat filters on the home 
page
Still working on:

  *   No image preview for models and 3D models and they are not 
downloadable

 *   Each creator that has an issue with the model was notified.
Have a great weekend,
Lova

--


[cid:ii_lpcmfwoi0]



Lova Andriarimalala

QGIS Full Stack Developer

Visit 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

___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] QGIS Full Stack Web Developer Report

[Lova Andriarimalala via QGIS-Developer]

Hello everyone,

The PR regarding the soft requirements (non-blocking warning) for the plugin 
license is now merged and deployed.

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




From: Lova Andriarimalala 
Date: Monday, 27 November 2023 at 4:34 PM
To: Julien Moura , qgis-developer@lists.osgeo.org 

Subject: Re: [QGIS-Developer] QGIS Full Stack Web Developer Report
Dear Julien,

I've created a new PR for this fix 
here<https://github.com/qgis/QGIS-Django/pull/314>. Please feel free to ask or 
add comments if you have any concerns about it.

Best regards.

—
[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




From: Lova Andriarimalala 
Date: Monday, 27 November 2023 at 4:12 PM
To: Julien Moura , qgis-developer@lists.osgeo.org 

Subject: Re: [QGIS-Developer] QGIS Full Stack Web Developer Report
Dear Julien,

It is a pleasure for me to work on the project.
I’ve created a 
QEP<https://github.com/qgis/QGIS-Enhancement-Proposals/issues/279> that 
summarizes this discussion. As suggested, I think we can go forward with the 
non-blocking warning for now and implement licensing requirements on schedule. 
I'll be creating a documented PR for this fix shortly.

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





From: QGIS-Developer  on behalf of 
Julien Moura via QGIS-Developer 
Date: Monday, 27 November 2023 at 2:41 PM
To: qgis-developer@lists.osgeo.org 
Subject: Re: [QGIS-Developer] QGIS Full Stack Web Developer Report

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 honor to 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



From: QGIS-Developer 
<mailto:qgis-developer-boun...@lists.osgeo.org>
 on behalf of Matthias Kuhn via QGIS-Developer 
<mailto:qgis-developer@lists.osgeo.org>
Date: Monday, 27 November 2023 at 12:24 PM
To: Tim Sutton <mailto:t...@kartoza.com>
Cc: qgis-developer@lists.osgeo.org<mailto:qgis-developer@lists.osgeo.org> 
<mailto:qgis-developer@lists.osgeo.org>
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 
mailto:t...@kartoza.com>> wrote:
Hi all

On Mon, Nov 27, 2023 at 1:32 AM Nyall Dawson 
mailto:nyall.daw...@gmail.com>> wrote:

On Mon, 27 Nov 2023 at 00:19, Tim Sutton via QGIS-Developer 
mailto:qgis-developer@lists.osgeo.org>> wrote:
>
> @Matthias Kuhn and @Julien Moura I fixed the permissions, the board for Lova 
> is public now. Please feel fre

Re: [QGIS-Developer] QGIS Full Stack Web Developer Report

[Lova Andriarimalala via QGIS-Developer]

Dear Julien,

I've created a new PR for this fix 
here<https://github.com/qgis/QGIS-Django/pull/314>. Please feel free to ask or 
add comments if you have any concerns about it.

Best regards.

—
[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




From: Lova Andriarimalala 
Date: Monday, 27 November 2023 at 4:12 PM
To: Julien Moura , qgis-developer@lists.osgeo.org 

Subject: Re: [QGIS-Developer] QGIS Full Stack Web Developer Report
Dear Julien,

It is a pleasure for me to work on the project.
I’ve created a 
QEP<https://github.com/qgis/QGIS-Enhancement-Proposals/issues/279> that 
summarizes this discussion. As suggested, I think we can go forward with the 
non-blocking warning for now and implement licensing requirements on schedule. 
I'll be creating a documented PR for this fix shortly.

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





From: QGIS-Developer  on behalf of 
Julien Moura via QGIS-Developer 
Date: Monday, 27 November 2023 at 2:41 PM
To: qgis-developer@lists.osgeo.org 
Subject: Re: [QGIS-Developer] QGIS Full Stack Web Developer Report

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 honor to 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



From: QGIS-Developer 
<mailto:qgis-developer-boun...@lists.osgeo.org>
 on behalf of Matthias Kuhn via QGIS-Developer 
<mailto:qgis-developer@lists.osgeo.org>
Date: Monday, 27 November 2023 at 12:24 PM
To: Tim Sutton <mailto:t...@kartoza.com>
Cc: qgis-developer@lists.osgeo.org<mailto:qgis-developer@lists.osgeo.org> 
<mailto:qgis-developer@lists.osgeo.org>
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 
mailto:t...@kartoza.com>> wrote:
Hi all

On Mon, Nov 27, 2023 at 1:32 AM Nyall Dawson 
mailto:nyall.daw...@gmail.com>> wrote:

On Mon, 27 Nov 2023 at 00:19, Tim Sutton via QGIS-Developer 
mailto:qgis-developer@lists.osgeo.org>> 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 /

Re: [QGIS-Developer] QGIS Full Stack Web Developer Report

[Lova Andriarimalala via QGIS-Developer]

Dear Julien,

It is a pleasure for me to work on the project.
I’ve created a 
QEP<https://github.com/qgis/QGIS-Enhancement-Proposals/issues/279> that 
summarizes this discussion. As suggested, I think we can go forward with the 
non-blocking warning for now and implement licensing requirements on schedule. 
I'll be creating a documented PR for this fix shortly.

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





From: QGIS-Developer  on behalf of 
Julien Moura via QGIS-Developer 
Date: Monday, 27 November 2023 at 2:41 PM
To: qgis-developer@lists.osgeo.org 
Subject: Re: [QGIS-Developer] QGIS Full Stack Web Developer Report

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 honor to 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



From: QGIS-Developer 
<mailto:qgis-developer-boun...@lists.osgeo.org>
 on behalf of Matthias Kuhn via QGIS-Developer 
<mailto:qgis-developer@lists.osgeo.org>
Date: Monday, 27 November 2023 at 12:24 PM
To: Tim Sutton <mailto:t...@kartoza.com>
Cc: qgis-developer@lists.osgeo.org<mailto:qgis-developer@lists.osgeo.org> 
<mailto:qgis-developer@lists.osgeo.org>
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 
mailto:t...@kartoza.com>> wrote:
Hi all

On Mon, Nov 27, 2023 at 1:32 AM Nyall Dawson 
mailto:nyall.daw...@gmail.com>> wrote:

On Mon, 27 Nov 2023 at 00:19, Tim Sutton via QGIS-Developer 
mailto:qgis-developer@lists.osgeo.org>> 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 w

Re: [QGIS-Developer] QGIS Full Stack Web Developer Report

[Julien Moura via QGIS-Developer]

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 

*From: *QGIS-Developer  on 
behalf of Matthias Kuhn via QGIS-Developer 


*Date: *Monday, 27 November 2023 at 12:24 PM
*To: *Tim Sutton 
*Cc: *qgis-developer@lists.osgeo.org 
*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  wrote:

Hi all

On Mon, Nov 27, 2023 at 1:32 AM Nyall Dawson
 wrote:


On Mon, 27 Nov 2023 at 00:19, Tim Sutton via QGIS-Developer
 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=t...@kartoza.com
repository=https://github.com/timlinux/QGISAnimationPl

Re: [QGIS-Developer] QGIS Full Stack Web Developer Report

[Lova Andriarimalala via QGIS-Developer]

Hello everyone,

Thank you all. It's truly an honor to 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



From: QGIS-Developer  on behalf of 
Matthias Kuhn via QGIS-Developer 
Date: Monday, 27 November 2023 at 12:24 PM
To: Tim Sutton 
Cc: qgis-developer@lists.osgeo.org 
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 
mailto:t...@kartoza.com>> wrote:
Hi all

On Mon, Nov 27, 2023 at 1:32 AM Nyall Dawson 
mailto:nyall.daw...@gmail.com>> wrote:

On Mon, 27 Nov 2023 at 00:19, Tim Sutton via QGIS-Developer 
mailto:qgis-developer@lists.osgeo.org>> 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=t...@kartoza.com<mailto:t...@kartoza.com>
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 -


--
--
[https://kartoza.com/files/KartozaNewLogoThumbnail.jpg]

Tim Sutton
Kartoza Co-Founder
Visit http://kartoza.com<http://kartoza.com/> to find out about open source:
 * Desktop GIS programming services
 * Geospatial web development
* GIS Training
* Consult

Re: [QGIS-Developer] QGIS Full Stack Web Developer Report

[Matthias Kuhn via QGIS-Developer]

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  wrote:

> Hi all
>
> On Mon, Nov 27, 2023 at 1:32 AM Nyall Dawson 
> wrote:
>
>>
>> On Mon, 27 Nov 2023 at 00:19, Tim Sutton via QGIS-Developer <
>> qgis-developer@lists.osgeo.org> 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=t...@kartoza.com
> 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
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] QGIS Full Stack Web Developer Report

[Tim Sutton via QGIS-Developer]

Hi all

On Mon, Nov 27, 2023 at 1:32 AM Nyall Dawson  wrote:

>
> On Mon, 27 Nov 2023 at 00:19, Tim Sutton via QGIS-Developer <
> qgis-developer@lists.osgeo.org> 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=t...@kartoza.com
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
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] QGIS Full Stack Web Developer Report

[Nyall Dawson via QGIS-Developer]

v 24, 2023 at 8:08 AM Lova Andriarimalala via QGIS-Developer <
qgis-developer@lists.osgeo.org> wrote:
>>>>
>>>> Dear Julien,
>>>>
>>>>
>>>>
>>>> That’s well noted. Thank you.
>>>>
>>>> I will add a detailed description in each PR in the future.
>>>>
>>>> Regarding the issue of LICENSE file requirements, I totally agree with
you. I will also ask Tim if he has suggestions about it.
>>>>
>>>>
>>>>
>>>> Best regards,
>>>>
>>>> Lova
>>>>
>>>>
>>>>
>>>> —
>>>>
>>>>
>>>>
>>>> Lova Andriarimalala
>>>>
>>>> QGIS Full Stack Developer
>>>>
>>>> Visit 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
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> From: Julien Moura 
>>>> Date: Friday, 24 November 2023 at 10:47 AM
>>>> To: Lova Andriarimalala ,
qgis-developer@lists.osgeo.org 
>>>> Subject: Re: [QGIS-Developer] QGIS Full Stack Web Developer Report
>>>>
>>>> Thanks for your quick reply here Lova,
>>>>
>>>> I've no special legibility that my opinion would be greater than
yours, so I can't tell if it has to be reverted or not. That's why I ask
for discussion before deploying some breaking change, without any warning
or information. After having looked to others PR, I would like to see more
description about what a PR does exactly, especially when it breaks
something.
>>>>
>>>> In this case, even after the last PR, this is a breaking and
undocumented change. For now, a plugin developer has no way to see that a
LICENSE file is now required in its plugin's zip. An error message in a log
is not a suitable information, even it's well formulated and clear,
especially in the era of automated CI/CD deployments.
>>>>
>>>> Regards,
>>>> Julien
>>>>
>>>> On 24/11/2023 08:35, Lova Andriarimalala wrote:
>>>>
>>>> Dear Julien,
>>>>
>>>>
>>>>
>>>> Many thanks for your feedback.
>>>>
>>>>
>>>>
>>>> In the new PR, the license file is only required for new plugins. For
existing plugin updates, it generates just a warning (but doesn't fail)
when the license file is missing.
>>>>
>>>> However, I'm not sure if we should also just generate a warning for
new plugin uploads for now. If so, I will also fix the new plugin upload.
>>>>
>>>>
>>>>
>>>> Kind regards.
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> —
>>>>
>>>>
>>>>
>>>> Lova Andriarimalala
>>>>
>>>> QGIS Full Stack Developer
>>>>
>>>> Visit 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
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> From: QGIS-Developer  on
behalf of Julien Moura via QGIS-Developer 
>>>> Date: Friday, 24 November 2023 at 10:30 AM
>>>> To: qgis-developer@lists.osgeo.org 
>>>> Subject: Re: [QGIS-Developer] QGIS Full Stack Web Developer Report
>>>>
>>>> Hello Lova,
>>>>
>>>> I cross post my comment to this issue related to the PR mentioned
below as "Make LICENSE file as required in plugin package", because I did
not have any answer there but saw that some changes still have been applied
without any comment.
>>>>
>>>> While trying to publish or update a plugin, we faced the new error
message related to the deployment of this PR:
>>>>
>>>> > Fault string: 
>>>>
>>>> See downstream issue on qgis-plugin-ci project (disclaimer: I'm one of
the maint

Re: [QGIS-Developer] QGIS Full Stack Web Developer Report

[Tim Sutton via QGIS-Developer]

;>>
>>> Regarding the issue of LICENSE file requirements, I totally agree with
>>> you. I will also ask Tim if he has suggestions about it.
>>>
>>>
>>>
>>> Best regards,
>>>
>>> Lova
>>>
>>>
>>>
>>> —
>>>
>>> [image: Image]
>>>
>>>
>>>
>>> *Lova Andriarimalala*
>>>
>>> *QGIS Full Stack Developer*
>>>
>>> Visit 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 <+261340952473>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> *From: *Julien Moura 
>>> *Date: *Friday, 24 November 2023 at 10:47 AM
>>> *To: *Lova Andriarimalala ,
>>> qgis-developer@lists.osgeo.org 
>>> *Subject: *Re: [QGIS-Developer] QGIS Full Stack Web Developer Report
>>>
>>> Thanks for your quick reply here Lova,
>>>
>>> I've no special legibility that my opinion would be greater than yours,
>>> so I can't tell if it has to be reverted or not. That's why I ask for
>>> discussion before deploying some breaking change, without any warning or
>>> information. After having looked to others PR, I would like to see more
>>> description about what a PR does exactly, especially when it breaks
>>> something.
>>>
>>> In this case, even after the last PR, this is a breaking and
>>> undocumented change. For now, a plugin developer has no way to see that a
>>> LICENSE file is now required in its plugin's zip. An error message in a log
>>> is not a suitable information, even it's well formulated and clear,
>>> especially in the era of automated CI/CD deployments.
>>>
>>> Regards,
>>> Julien
>>>
>>> On 24/11/2023 08:35, Lova Andriarimalala wrote:
>>>
>>> Dear Julien,
>>>
>>>
>>>
>>> Many thanks for your feedback.
>>>
>>>
>>>
>>> In the new PR, the license file is only required for new plugins. For
>>> existing plugin updates, it generates just a warning (but doesn't fail)
>>> when the license file is missing.
>>>
>>> However, I'm not sure if we should also just generate a warning for new
>>> plugin uploads for now. If so, I will also fix the new plugin upload.
>>>
>>>
>>>
>>> Kind regards.
>>>
>>>
>>>
>>>
>>>
>>> —
>>>
>>> [image: Image]
>>>
>>>
>>>
>>> *Lova Andriarimalala*
>>>
>>> *QGIS Full Stack Developer*
>>>
>>> Visit 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 <+261340952473>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> *From: *QGIS-Developer 
>>>  on behalf of Julien Moura via
>>> QGIS-Developer 
>>> 
>>> *Date: *Friday, 24 November 2023 at 10:30 AM
>>> *To: *qgis-developer@lists.osgeo.org 
>>> 
>>> *Subject: *Re: [QGIS-Developer] QGIS Full Stack Web Developer Report
>>>
>>> Hello Lova,
>>>
>>> I cross post my comment to this issue
>>> <https://github.com/qgis/QGIS-Django/issues/38#issuecomment-1824010198>
>>> related to the PR mentioned below as "Make LICENSE file as required in
>>> plugin package <https://github.com/qgis/QGIS-Django/pull/309>", because
>>> I did not have any answer there but saw that some changes still have been
>>> applied without any comment.
>>>
>>> While trying to publish or update a plugin, we faced the new error
>>> message related to the deployment of this PR
>>> <https://github.com/qgis/QGIS-Django/pull/309>:
>>>
>>> > Fault string: >> plugin compressed archive. Cannot find LICENSE in plugin package.'>
>>>
>>> See downstream issue on qgis-plugin-ci project (disclaimer: I'm one of
>>> the mainteners but speaking on my own here):
>>> https://github.com/

Re: [QGIS-Developer] QGIS Full Stack Web Developer Report

[Matthias Kuhn via QGIS-Developer]

Hi,

Thank you very much Lova for working on this application, it's a very
important piece in the QGIS ecosystem!

For the current discussion, I would also suggest making the license
recommended for now and only start enforcing it on a schedule. And I was
wondering if a license field in the metadata.txt would be even better (cmp.
https://python-poetry.org/docs/pyproject/#license), that would be easier to
show on the plugin page?

Is there any way to help prioritizing the issues? I have some wishes that I
would love to see land on the backlog

Kind regards and thanks again for all the good work on this !
Matthias

On Fri, Nov 24, 2023 at 11:49 AM Julien Moura via QGIS-Developer <
qgis-developer@lists.osgeo.org> wrote:

> Dear Tim,
>
> Thanks for taking in account my thoughts and make the discussion possible.
>
> Regarding the second about change management, I totally agree and feel
> really thankful that you make those changes. I can imagine the work it
> represents for your teams maintaining a project like this one. So thank you
> again.
>
> Regarding your proposal about the license requirements, why not starting
> apply the change management to this? It's a breaking change, even for new
> plugins, right? So, it should be lowered to a non blocking warning,
> documented in PyQGIS cookbook and then deployed as a blocking error in a
> known time windows. This way, in the meanwhile, the plugins ecosystem can
> adapt to new rules (new versions for tools like minimal plugin,
> qgis-plugin-ci, plugin builder...) and make this change more acceptable and
> frictionless.
>
> Moreover, the rationale behind the required license file into the plugin
> archive is still not solved.
>
> If you want, I can make a PR to change the warning but I'm pretty sure
> that's not the question here.
>
> https://github.com/orgs/qgis/projects/6
>
> Just to let you know this hyperlink leads to a 404 (probably a Github
> rights access setting somewhere).
>
> Regards
> On 24/11/2023 10:50, Tim Sutton wrote:
>
> Dear Julien
>
> Thank you so much for your engagement and suggestions. Fully agreed that
> breaking changes should be well communicated first. So splitting the
> discussion in two:
>
>
> 1) License requirements: for now I have chatted with Lova and we propose:
>
> a) Change the logic such that a license is required for newly registered
> plugins
> b) When updates are made to existing plugins that do not include a
> license, the uploader will be shown a warning indicating that in future the
> license will  be mandatory
>
> This is already implemented in
> https://github.com/qgis/QGIS-Django/pull/311 and I propose we deploy this
> today / ASAP to address the previously raised issues.
>
> 2) Change management:
>
> Yes I think we can introduce more rigour in the process.
>
> * breaking changes: discuss with the community first, implement, deploy in
> a known time window
> * non-breaking changes: for simple bug fixes, just fix, test and deploy as
> needed
> * non-breaking changes: for features etc. these will be managed on the
> project board here, anyone who wants to be engaged in the process can see
> the planned upcomming work and interact with Lova via the ticket queue.
> https://github.com/orgs/qgis/projects/6
> * requests to improvements: please file tickets here
> https://github.com/qgis/QGIS-Django/issues
>
> Regarding a staging site, currently we do not run a staging environment,
> developers have local test environments and I am on the fence as to whether
> there is a lot of value in us maintaining a long running staging site.
>
> Regards
>
> Tim
>
>
>
>
> On Fri, Nov 24, 2023 at 8:08 AM Lova Andriarimalala via QGIS-Developer <
> qgis-developer@lists.osgeo.org> wrote:
>
>> Dear Julien,
>>
>>
>>
>> That’s well noted. Thank you.
>>
>> I will add a detailed description in each PR in the future.
>>
>> Regarding the issue of LICENSE file requirements, I totally agree with
>> you. I will also ask Tim if he has suggestions about it.
>>
>>
>>
>> Best regards,
>>
>> Lova
>>
>>
>>
>> —
>>
>> [image: Image]
>>
>>
>>
>> *Lova Andriarimalala*
>>
>> *QGIS Full Stack Developer*
>>
>> Visit 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 <+261340952473>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> *From: *Julien Moura 
>> *Date: *Friday, 24 No

Re: [QGIS-Developer] QGIS Full Stack Web Developer Report

[Julien Moura via QGIS-Developer]

Dear Tim,

Thanks for taking in account my thoughts and make the discussion possible.

Regarding the second about change management, I totally agree and feel 
really thankful that you make those changes. I can imagine the work it 
represents for your teams maintaining a project like this one. So thank 
you again.


Regarding your proposal about the license requirements, why not starting 
apply the change management to this? It's a breaking change, even for 
new plugins, right? So, it should be lowered to a non blocking warning, 
documented in PyQGIS cookbook and then deployed as a blocking error in a 
known time windows. This way, in the meanwhile, the plugins ecosystem 
can adapt to new rules (new versions for tools like minimal plugin, 
qgis-plugin-ci, plugin builder...) and make this change more acceptable 
and frictionless.


Moreover, the rationale behind the required license file into the plugin 
archive is still not solved.


If you want, I can make a PR to change the warning but I'm pretty sure 
that's not the question here.



https://github.com/orgs/qgis/projects/6
Just to let you know this hyperlink leads to a 404 (probably a Github 
rights access setting somewhere).


Regards

On 24/11/2023 10:50, Tim Sutton wrote:

Dear Julien

Thank you so much for your engagement and suggestions. Fully agreed 
that breaking changes should be well communicated first. So splitting 
the discussion in two:



1) License requirements: for now I have chatted with Lova and we propose:

a) Change the logic such that a license is required for newly 
registered plugins
b) When updates are made to existing plugins that do not include a 
license, the uploader will be shown a warning indicating that in 
future the license will  be mandatory


This is already implemented in 
https://github.com/qgis/QGIS-Django/pull/311 and I propose we deploy 
this today / ASAP to address the previously raised issues.


2) Change management:

Yes I think we can introduce more rigour in the process.

* breaking changes: discuss with the community first, implement, 
deploy in a known time window
* non-breaking changes: for simple bug fixes, just fix, test and 
deploy as needed
* non-breaking changes: for features etc. these will be managed on the 
project board here, anyone who wants to be engaged in the process can 
see the planned upcomming work and interact with Lova via the ticket 
queue. https://github.com/orgs/qgis/projects/6
* requests to improvements: please file tickets here 
https://github.com/qgis/QGIS-Django/issues


Regarding a staging site, currently we do not run a staging 
environment, developers have local test environments and I am on the 
fence as to whether there is a lot of value in us maintaining a long 
running staging site.


Regards

Tim




On Fri, Nov 24, 2023 at 8:08 AM Lova Andriarimalala via QGIS-Developer 
 wrote:


Dear Julien,

That’s well noted. Thank you.

I will add a detailed description in each PR in the future.

Regarding the issue of LICENSE file requirements, I totally agree
with you. I will also ask Tim if he has suggestions about it.

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 

*From: *Julien Moura 
*Date: *Friday, 24 November 2023 at 10:47 AM
*To: *Lova Andriarimalala ,
qgis-developer@lists.osgeo.org 
*Subject: *Re: [QGIS-Developer] QGIS Full Stack Web Developer Report

Thanks for your quick reply here Lova,

I've no special legibility that my opinion would be greater than
yours, so I can't tell if it has to be reverted or not. That's why
I ask for discussion before deploying some breaking change,
without any warning or information. After having looked to others
PR, I would like to see more description about what a PR does
exactly, especially when it breaks something.

In this case, even after the last PR, this is a breaking and
undocumented change. For now, a plugin developer has no way to see
that a LICENSE file is now required in its plugin's zip. An error
message in a log is not a suitable information, even it's well
formulated and clear, especially in the era of automated CI/CD
deployments.

Regards,
Julien

On 24/11/2023 08:35, Lova Andriarimalala wrote:

Dear Julien,

Many thanks for your feedback.

In the newPR, the license file is only required for new
plugins. For existing plugin updates, it generates just a
warning (but doesn't fail) when the license file is missing.

However, I'm not sure if we should also just generate a
warning for new plugin uploads for now. If so, I will also fix
the new plugin 

Re: [QGIS-Developer] QGIS Full Stack Web Developer Report

[Tim Sutton via QGIS-Developer]

Dear Julien

Thank you so much for your engagement and suggestions. Fully agreed that
breaking changes should be well communicated first. So splitting the
discussion in two:


1) License requirements: for now I have chatted with Lova and we propose:

a) Change the logic such that a license is required for newly registered
plugins
b) When updates are made to existing plugins that do not include a license,
the uploader will be shown a warning indicating that in future the license
will  be mandatory

This is already implemented in https://github.com/qgis/QGIS-Django/pull/311
and I propose we deploy this today / ASAP to address the previously raised
issues.

2) Change management:

Yes I think we can introduce more rigour in the process.

* breaking changes: discuss with the community first, implement, deploy in
a known time window
* non-breaking changes: for simple bug fixes, just fix, test and deploy as
needed
* non-breaking changes: for features etc. these will be managed on the
project board here, anyone who wants to be engaged in the process can see
the planned upcomming work and interact with Lova via the ticket queue.
https://github.com/orgs/qgis/projects/6
* requests to improvements: please file tickets here
https://github.com/qgis/QGIS-Django/issues

Regarding a staging site, currently we do not run a staging environment,
developers have local test environments and I am on the fence as to whether
there is a lot of value in us maintaining a long running staging site.

Regards

Tim




On Fri, Nov 24, 2023 at 8:08 AM Lova Andriarimalala via QGIS-Developer <
qgis-developer@lists.osgeo.org> wrote:

> Dear Julien,
>
>
>
> That’s well noted. Thank you.
>
> I will add a detailed description in each PR in the future.
>
> Regarding the issue of LICENSE file requirements, I totally agree with
> you. I will also ask Tim if he has suggestions about it.
>
>
>
> Best regards,
>
> Lova
>
>
>
> —
>
> [image: Image]
>
>
>
> *Lova Andriarimalala*
>
> *QGIS Full Stack Developer*
>
> Visit 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 <+261340952473>
>
>
>
>
>
>
>
>
>
> *From: *Julien Moura 
> *Date: *Friday, 24 November 2023 at 10:47 AM
> *To: *Lova Andriarimalala ,
> qgis-developer@lists.osgeo.org 
> *Subject: *Re: [QGIS-Developer] QGIS Full Stack Web Developer Report
>
> Thanks for your quick reply here Lova,
>
> I've no special legibility that my opinion would be greater than yours, so
> I can't tell if it has to be reverted or not. That's why I ask for
> discussion before deploying some breaking change, without any warning or
> information. After having looked to others PR, I would like to see more
> description about what a PR does exactly, especially when it breaks
> something.
>
> In this case, even after the last PR, this is a breaking and undocumented
> change. For now, a plugin developer has no way to see that a LICENSE file
> is now required in its plugin's zip. An error message in a log is not a
> suitable information, even it's well formulated and clear, especially in
> the era of automated CI/CD deployments.
>
> Regards,
> Julien
>
> On 24/11/2023 08:35, Lova Andriarimalala wrote:
>
> Dear Julien,
>
>
>
> Many thanks for your feedback.
>
>
>
> In the new PR, the license file is only required for new plugins. For
> existing plugin updates, it generates just a warning (but doesn't fail)
> when the license file is missing.
>
> However, I'm not sure if we should also just generate a warning for new
> plugin uploads for now. If so, I will also fix the new plugin upload.
>
>
>
> Kind regards.
>
>
>
>
>
> —
>
> [image: Image]
>
>
>
> *Lova Andriarimalala*
>
> *QGIS Full Stack Developer*
>
> Visit 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 <+261340952473>
>
>
>
>
>
>
>
>
>
> *From: *QGIS-Developer 
>  on behalf of Julien Moura via
> QGIS-Developer 
> 
> *Date: *Friday, 24 November 2023 at 10:30 AM
> *To: *qgis-developer@lists.osgeo.org 
> 
> *Subject: *Re: [QGIS-Developer] QGIS Full Stack Web Developer Report
>
> Hello Lova,
>
> I cross post my comment to this issue
> <https://github.com/qgis/QGIS-Django/issues/38#issuecomment-1824010198>
> related to the PR mentioned below as "Make LICENSE file as required in
> plugin package <https://github.com/qgis

Re: [QGIS-Developer] QGIS Full Stack Web Developer Report

[Lova Andriarimalala via QGIS-Developer]

Dear Julien,

That’s well noted. Thank you.
I will add a detailed description in each PR in the future.
Regarding the issue of LICENSE file requirements, I totally agree with you. I 
will also ask Tim if he has suggestions about it.

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




From: Julien Moura 
Date: Friday, 24 November 2023 at 10:47 AM
To: Lova Andriarimalala , qgis-developer@lists.osgeo.org 

Subject: Re: [QGIS-Developer] QGIS Full Stack Web Developer Report

Thanks for your quick reply here Lova,

I've no special legibility that my opinion would be greater than yours, so I 
can't tell if it has to be reverted or not. That's why I ask for discussion 
before deploying some breaking change, without any warning or information. 
After having looked to others PR, I would like to see more description about 
what a PR does exactly, especially when it breaks something.

In this case, even after the last PR, this is a breaking and undocumented 
change. For now, a plugin developer has no way to see that a LICENSE file is 
now required in its plugin's zip. An error message in a log is not a suitable 
information, even it's well formulated and clear, especially in the era of 
automated CI/CD deployments.

Regards,
Julien
On 24/11/2023 08:35, Lova Andriarimalala wrote:
Dear Julien,

Many thanks for your feedback.

In the new PR, the license file is only required for new plugins. For existing 
plugin updates, it generates just a warning (but doesn't fail) when the license 
file is missing.
However, I'm not sure if we should also just generate a warning for new plugin 
uploads for now. If so, I will also fix the new plugin upload.

Kind regards.


—
[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




From: QGIS-Developer 
<mailto:qgis-developer-boun...@lists.osgeo.org>
 on behalf of Julien Moura via QGIS-Developer 
<mailto:qgis-developer@lists.osgeo.org>
Date: Friday, 24 November 2023 at 10:30 AM
To: qgis-developer@lists.osgeo.org<mailto:qgis-developer@lists.osgeo.org> 
<mailto:qgis-developer@lists.osgeo.org>
Subject: Re: [QGIS-Developer] QGIS Full Stack Web Developer Report

Hello Lova,

I cross post my comment to this 
issue<https://github.com/qgis/QGIS-Django/issues/38#issuecomment-1824010198> 
related to the PR mentioned below as "Make LICENSE file as required in plugin 
package<https://github.com/qgis/QGIS-Django/pull/309>", because I did not have 
any answer there but saw that some changes still have been applied without any 
comment.

While trying to publish or update a plugin, we faced the new error message 
related to the deployment of this 
PR<https://github.com/qgis/QGIS-Django/pull/309>:

> Fault string:  compressed archive. Cannot find LICENSE in plugin package.'>

See downstream issue on qgis-plugin-ci project (disclaimer: I'm one of the 
mainteners but speaking on my own here): 
https://github.com/opengisch/qgis-plugin-ci/issues/255

I think this kind of change, which breaks the plugins'publication flow, should 
be discussed before to be implemented (an issue from 1 person seems to be too 
light to decide without any discussion), announced to the community, a warning 
campaign should be run and a transitional phase should be implemented (warning 
for 6 months, then error). This has a direct impact on hundreds (thousands?) of 
plugin developers on a community project with several million end users.

I understand that this process may seem too cumbersome, and that since the QGIS 
Django project hasn't been so dynamic for a few years, it's nice to see it get 
a new lease of life, even if it means merging and deploying on an ongoing basis.

As for the underlying principle, I'm generally in favor of strengthening the 
control mechanisms (automatic or otherwise) for extensions on the official 
repository, but I think it's really important to do this gradually, or at least 
to avoid unilateral change "descended from the skies of the developers".

Concerning the idea of integrating the license in the plugin package, I'm not 
really convinced of the interest since most plugins are contaminated by the 
GPL2+ of QGIS <-- Qt and the license is never displayed to the end user. But 
why not. After all, it's always a good practice to include licence and spread 
the word about (re)usage rules.

Reverting sounds maybe too rought so I suggest modyfing the behavior to lower 
the level and make it a simple warning and in the meanwhile starting a 
communication and prevent

Re: [QGIS-Developer] QGIS Full Stack Web Developer Report

[Julien Moura via QGIS-Developer]

Thanks for your quick reply here Lova,

I've no special legibility that my opinion would be greater than yours, 
so I can't tell if it has to be reverted or not. That's why I ask for 
discussion before deploying some breaking change, without any warning or 
information. After having looked to others PR, I would like to see more 
description about what a PR does exactly, especially when it breaks 
something.


In this case, even after the last PR, this is a breaking and 
undocumented change. For now, a plugin developer has no way to see that 
a LICENSE file is now required in its plugin's zip. An error message in 
a log is not a suitable information, even it's well formulated and 
clear, especially in the era of automated CI/CD deployments.


Regards,
Julien

On 24/11/2023 08:35, Lova Andriarimalala wrote:


Dear Julien,

Many thanks for your feedback.

In the newPR, the license file is only required for new plugins. For 
existing plugin updates, it generates just a warning (but doesn't 
fail) when the license file is missing.


However, I'm not sure if we should also just generate a warning for 
new plugin uploads for now. If so, I will also fix the new plugin upload.


Kind regards.

—**

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 

*From: *QGIS-Developer  on 
behalf of Julien Moura via QGIS-Developer 

*Date: *Friday, 24 November 2023 at 10:30 AM
*To: *qgis-developer@lists.osgeo.org 
*Subject: *Re: [QGIS-Developer] QGIS Full Stack Web Developer Report

Hello Lova,

I cross post my comment to this issue 
<https://github.com/qgis/QGIS-Django/issues/38#issuecomment-1824010198> 
related to the PR mentioned below as "Make LICENSE file as required in 
plugin package <https://github.com/qgis/QGIS-Django/pull/309>", 
because I did not have any answer there but saw that some changes 
still have been applied without any comment.


While trying to publish or update a plugin, we faced the new error 
message related to the deployment of this PR 
<https://github.com/qgis/QGIS-Django/pull/309>:


> Fault string: plugin compressed archive. Cannot find LICENSE in plugin package.'>


See downstream issue on qgis-plugin-ci project (disclaimer: I'm one of 
the mainteners but speaking on my own here): 
https://github.com/opengisch/qgis-plugin-ci/issues/255


I think this kind of change, which breaks the plugins'publication 
flow, should be discussed before to be implemented (an issue from 1 
person seems to be too light to decide without any discussion), 
announced to the community, a warning campaign should be run and a 
transitional phase should be implemented (warning for 6 months, then 
error). This has a direct impact on hundreds (thousands?) of plugin 
developers on a community project with several million end users.


I understand that this process may seem too cumbersome, and that since 
the QGIS Django project hasn't been so dynamic for a few years, it's 
nice to see it get a new lease of life, even if it means merging and 
deploying on an ongoing basis.


As for the underlying principle, I'm generally in favor of 
strengthening the control mechanisms (automatic or otherwise) for 
extensions on the official repository, but I think it's really 
important to do this gradually, or at least to avoid unilateral change 
"descended from the skies of the developers".


Concerning the idea of integrating the license in the plugin package, 
I'm not really convinced of the interest since most plugins are 
contaminated by the GPL2+ of QGIS <-- Qt and the license is never 
displayed to the end user. But why not. After all, it's always a good 
practice to include licence and spread the word about (re)usage rules.


Reverting sounds maybe too rought so I suggest modyfing the behavior 
to lower the level and make it a simple warning and in the meanwhile 
starting a communication and preventive work upstream:


 1. update documentation:

https://docs.qgis.org/3.28/en/docs/pyqgis_developer_cookbook/plugins/plugins.html
 2. communicate on the QGIS Dev list **before** the implementation to
discuss the rationale
 3. integrate a warning mechanism
 4. manage the QGIS versions concerned (only applicable to new QGIS
released versions after this being merged)

A last question: did you have some pre-production environment where to 
deploy new changes in order to evaluate them before publishing widely? 
Or some versioning logic, milestone workflow where PRs are grouped 
before being deployed?


Regards,
Julien

On 17/11/2023 13:59, Lova Andriarimalala via QGIS-Developer wrote:

Hello everyone,

Please find below the report summarizing the progress on the feed
and plugins websitedevelopment for this week.

*PRs open:*

1.Add sup

Re: [QGIS-Developer] QGIS Full Stack Web Developer Report

[Lova Andriarimalala via QGIS-Developer]

Dear Julien,

Many thanks for your feedback.

In the new PR, the license file is only required for new plugins. For existing 
plugin updates, it generates just a warning (but doesn't fail) when the license 
file is missing.
However, I'm not sure if we should also just generate a warning for new plugin 
uploads for now. If so, I will also fix the new plugin upload.

Kind regards.


—
[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




From: QGIS-Developer  on behalf of 
Julien Moura via QGIS-Developer 
Date: Friday, 24 November 2023 at 10:30 AM
To: qgis-developer@lists.osgeo.org 
Subject: Re: [QGIS-Developer] QGIS Full Stack Web Developer Report

Hello Lova,

I cross post my comment to this 
issue<https://github.com/qgis/QGIS-Django/issues/38#issuecomment-1824010198> 
related to the PR mentioned below as "Make LICENSE file as required in plugin 
package<https://github.com/qgis/QGIS-Django/pull/309>", because I did not have 
any answer there but saw that some changes still have been applied without any 
comment.

While trying to publish or update a plugin, we faced the new error message 
related to the deployment of this 
PR<https://github.com/qgis/QGIS-Django/pull/309>:

> Fault string:  compressed archive. Cannot find LICENSE in plugin package.'>

See downstream issue on qgis-plugin-ci project (disclaimer: I'm one of the 
mainteners but speaking on my own here): 
https://github.com/opengisch/qgis-plugin-ci/issues/255

I think this kind of change, which breaks the plugins'publication flow, should 
be discussed before to be implemented (an issue from 1 person seems to be too 
light to decide without any discussion), announced to the community, a warning 
campaign should be run and a transitional phase should be implemented (warning 
for 6 months, then error). This has a direct impact on hundreds (thousands?) of 
plugin developers on a community project with several million end users.

I understand that this process may seem too cumbersome, and that since the QGIS 
Django project hasn't been so dynamic for a few years, it's nice to see it get 
a new lease of life, even if it means merging and deploying on an ongoing basis.

As for the underlying principle, I'm generally in favor of strengthening the 
control mechanisms (automatic or otherwise) for extensions on the official 
repository, but I think it's really important to do this gradually, or at least 
to avoid unilateral change "descended from the skies of the developers".

Concerning the idea of integrating the license in the plugin package, I'm not 
really convinced of the interest since most plugins are contaminated by the 
GPL2+ of QGIS <-- Qt and the license is never displayed to the end user. But 
why not. After all, it's always a good practice to include licence and spread 
the word about (re)usage rules.

Reverting sounds maybe too rought so I suggest modyfing the behavior to lower 
the level and make it a simple warning and in the meanwhile starting a 
communication and preventive work upstream:

  1.  update documentation: 
https://docs.qgis.org/3.28/en/docs/pyqgis_developer_cookbook/plugins/plugins.html
  2.  communicate on the QGIS Dev list **before** the implementation to discuss 
the rationale
  3.  integrate a warning mechanism
  4.  manage the QGIS versions concerned (only applicable to new QGIS released 
versions after this being merged)

A last question: did you have some pre-production environment where to deploy 
new changes in order to evaluate them before publishing widely? Or some 
versioning logic, milestone workflow where PRs are grouped before being 
deployed?

Regards,
Julien
On 17/11/2023 13:59, Lova Andriarimalala via QGIS-Developer wrote:
Hello everyone,

Please find below the report summarizing the progress on the feed and plugins 
website development for this week.
PRs open:

1.   Add support for renaming plugin 
name<https://github.com/qgis/QGIS-Django/pull/302>

2.   Add command to fix none in search 
results<https://github.com/qgis/QGIS-Django/pull/304>

3.   Show more records, records items per 
page<https://github.com/qgis/QGIS-Django/pull/306>

4.   Specify tag page title and other plugin page 
title<https://github.com/qgis/QGIS-Django/pull/308>

5.   Make LICENSE file as required in plugin 
package<https://github.com/qgis/QGIS-Django/pull/309>

PR merged:

6.   Update dockerfile and requirements for 
production<https://github.com/qgis/qgis-feed/pull/44>

7.   Update requirements according to 
production<https://github.com/qgis/qgis-feed/pull/47>

8.   Add geoip2 in production, setting up 
log<https://github.com/qgis/qgis-feed/pull/48>

9.   Use contry code when testing 
dai

Re: [QGIS-Developer] QGIS Full Stack Web Developer Report

[Julien Moura via QGIS-Developer]

Hello Lova,

I cross post my comment to this issue 
 
related to the PR mentioned below as "Make LICENSE file as required in 
plugin package ", because 
I did not have any answer there but saw that some changes still have 
been applied without any comment.


While trying to publish or update a plugin, we faced the new error 
message related to the deployment of this PR 
:


> Fault string: plugin compressed archive. Cannot find LICENSE in plugin package.'>


See downstream issue on qgis-plugin-ci project (disclaimer: I'm one of 
the mainteners but speaking on my own here): 
https://github.com/opengisch/qgis-plugin-ci/issues/255


I think this kind of change, which breaks the plugins'publication flow, 
should be discussed before to be implemented (an issue from 1 person 
seems to be too light to decide without any discussion), announced to 
the community, a warning campaign should be run and a transitional phase 
should be implemented (warning for 6 months, then error). This has a 
direct impact on hundreds (thousands?) of plugin developers on a 
community project with several million end users.


I understand that this process may seem too cumbersome, and that since 
the QGIS Django project hasn't been so dynamic for a few years, it's 
nice to see it get a new lease of life, even if it means merging and 
deploying on an ongoing basis.


As for the underlying principle, I'm generally in favor of strengthening 
the control mechanisms (automatic or otherwise) for extensions on the 
official repository, but I think it's really important to do this 
gradually, or at least to avoid unilateral change "descended from the 
skies of the developers".


Concerning the idea of integrating the license in the plugin package, 
I'm not really convinced of the interest since most plugins are 
contaminated by the GPL2+ of QGIS <-- Qt and the license is never 
displayed to the end user. But why not. After all, it's always a good 
practice to include licence and spread the word about (re)usage rules.


Reverting sounds maybe too rought so I suggest modyfing the behavior to 
lower the level and make it a simple warning and in the meanwhile 
starting a communication and preventive work upstream:


1. update documentation:
   
https://docs.qgis.org/3.28/en/docs/pyqgis_developer_cookbook/plugins/plugins.html
2. communicate on the QGIS Dev list **before** the implementation to
   discuss the rationale
3. integrate a warning mechanism
4. manage the QGIS versions concerned (only applicable to new QGIS
   released versions after this being merged)

A last question: did you have some pre-production environment where to 
deploy new changes in order to evaluate them before publishing widely? 
Or some versioning logic, milestone workflow where PRs are grouped 
before being deployed?


Regards,
Julien

On 17/11/2023 13:59, Lova Andriarimalala via QGIS-Developer wrote:


Hello everyone,

Please find below the report summarizing the progress on the feed and 
plugins websitedevelopment for this week.


*PRs open:*

  * Add support for renaming plugin name

  * Add command to fix none in search results

  * Show more records, records items per page

  * Specify tag page title and other plugin page title

  * Make LICENSE file as required in plugin package


*PR merged:*

  * Update dockerfile and requirements for production

  * Update requirements according to production

  * Add geoip2 in production, setting up log

  * Use contry code when testing daily_visit.country


*Still working on:*

  * Fresh plugin includes obsolete stuff


Changes to the QGIS Feed website are now deployed and available at 
https://feed.qgis.org.


Have a great weekend,

Lova

—**

Image

*Lova Andriarimalala***

*QGIS Full Stack Developer***

Visit 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 

*From: *Lova Andriarimalala 
*Date: *Friday, 10 November 2023 at 5:32 PM
*To: *qgis-developer@lists.osgeo.org 
*Subject: *Re: QGIS Full Stack Web Developer Report

Hello everyone,

Please find below the report summarizing the progress on the feed and 
plugins websitedevelopment for this week.


*PRs open:*

  * Add support for renaming plugin name

Re: [QGIS-Developer] QGIS Full Stack Web Developer Report

[Lova Andriarimalala via QGIS-Developer]

Hello everyone,

Please find below the report summarizing the progress on the feed and plugins 
website development for this week.
PRs open:

  *   Add support for renaming plugin 
name
  *   Add command to fix none in search 
results
  *   Show more records, records items per 
page
  *   Specify tag page title and other plugin page 
title
  *   Make LICENSE file as required in plugin 
package

PR merged:

  *   Update dockerfile and requirements for 
production
  *   Update requirements according to 
production
  *   Add geoip2 in production, setting up 
log
  *   Use contry code when testing 
daily_visit.country

Still working on:

  *   Fresh plugin includes obsolete stuff 


Changes to the QGIS Feed website are now deployed and available at 
https://feed.qgis.org.

Have a great weekend,
Lova


—
[Image]

Lova Andriarimalala
QGIS Full Stack Developer
Visit 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



From: Lova Andriarimalala 
Date: Friday, 10 November 2023 at 5:32 PM
To: qgis-developer@lists.osgeo.org 
Subject: Re: QGIS Full Stack Web Developer Report
Hello everyone,

Please find below the report summarizing the progress on the feed and plugins 
website development for this week.
PRs open:

  *   Add support for renaming plugin 
name
  *   Update dockerfile and requirements for 
production

PR merged:

  *   Add web page UI on the root URL

Still working on:

  *   Deployment of the feed updates

Have a great weekend,
Lova
—
[Image]

Lova Andriarimalala
QGIS Full Stack Developer
Visit 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


From: Lova Andriarimalala 
Date: Friday, 3 November 2023 at 5:05 PM
To: qgis-developer@lists.osgeo.org 
Subject: Re: QGIS Full Stack Web Developer Report
Hello everyone,

Please find below the report summarizing the progress on the feed site 
development for this week.

PRs open:

  *   Add web page UI on the root URL
PR merged:

  *   Using rich editor for content, check data 
validity
Still working on:

  *   Some checks and fixes on the 
entirety
Have a great weekend,
Lova

—

[Image]

Lova Andriarimalala

QGIS Full Stack Web Developer

Visit 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



From: Lova Andriarimalala 
Date: Friday, 27 October 2023 at 4:53 PM
To: qgis-developer@lists.osgeo.org 
Subject: Re: QGIS Full Stack Web Developer Report
Hello everyone,

I'm grateful for your warm welcome, and I'm truly thrilled to join this 
wonderful community.
Here is the report summarizing the progress on the feed site development for 
this week.
PRs open:

 *   Form submission management
PR merged:

 *   Feeds list page with filter and 
sorting
 *   Feed item form with preview
 *   Feed form review step
 *   Implement webpack and use it for Bulma 
CSS
Still working on:

 *   Improve feed item form: Check data 
validity

Have a great weekend,
Lova

—

[cid:9A13FDC2-2DFE-48D9-9736-E7E67663BF60]

Lova Andriarimalala

QGIS Full Stack Web Developer

Visit 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



From: Lova Andriarimalala 
Date: Friday, 20 October 2023 at 2:54 PM
To: qgis-developer@lists.osgeo.org 
Subject: QGIS Full Stack Web Developer Report
Hello everyone,

Currently, I am working on the website that administers the feeds displayed in 
the news area of QGIS. The website's repository is available on GitHub: 
https://github.com/qgis/qgis-feed

Please find below the report for the 

Re: [QGIS-Developer] QGIS Full Stack Web Developer Report

[Lova Andriarimalala via QGIS-Developer]

Hello everyone,

Please find below the report summarizing the progress on the feed and plugins 
website development for this week.
PRs open:

  *   Add support for renaming plugin 
name
  *   Update dockerfile and requirements for 
production

PR merged:

  *   Add web page UI on the root URL

Still working on:

  *   Deployment of the feed updates

Have a great weekend,
Lova
—
[Image]

Lova Andriarimalala
QGIS Full Stack Developer
Visit 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


From: Lova Andriarimalala 
Date: Friday, 3 November 2023 at 5:05 PM
To: qgis-developer@lists.osgeo.org 
Subject: Re: QGIS Full Stack Web Developer Report
Hello everyone,

Please find below the report summarizing the progress on the feed site 
development for this week.

PRs open:

  *   Add web page UI on the root URL
PR merged:

  *   Using rich editor for content, check data 
validity
Still working on:

  *   Some checks and fixes on the 
entirety
Have a great weekend,
Lova

—

[Image]

Lova Andriarimalala

QGIS Full Stack Web Developer

Visit 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



From: Lova Andriarimalala 
Date: Friday, 27 October 2023 at 4:53 PM
To: qgis-developer@lists.osgeo.org 
Subject: Re: QGIS Full Stack Web Developer Report
Hello everyone,

I'm grateful for your warm welcome, and I'm truly thrilled to join this 
wonderful community.
Here is the report summarizing the progress on the feed site development for 
this week.
PRs open:

 *   Form submission management
PR merged:

 *   Feeds list page with filter and 
sorting
 *   Feed item form with preview
 *   Feed form review step
 *   Implement webpack and use it for Bulma 
CSS
Still working on:

 *   Improve feed item form: Check data 
validity

Have a great weekend,
Lova

—

[image.png]

Lova Andriarimalala

QGIS Full Stack Web Developer

Visit 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



From: Lova Andriarimalala 
Date: Friday, 20 October 2023 at 2:54 PM
To: qgis-developer@lists.osgeo.org 
Subject: QGIS Full Stack Web Developer Report
Hello everyone,

Currently, I am working on the website that administers the feeds displayed in 
the news area of QGIS. The website's repository is available on GitHub: 
https://github.com/qgis/qgis-feed

Please find below the report for the past two weeks.
PRs open:

 *   Feeds list page with filter and 
sorting
 *   Feed item form with preview
 *   Feed form review step
PR merged:

 *   Create a login page, add test cases, configure GH 
actions
Still working on:

 *   Use web pack for bulma CSS

Please do not hesitate to provide any feedback regarding the report structure 
or layout. Your suggestions are highly appreciated, as they will enable us to 
improve the report's quality and readability. Thank you for taking the time to 
review the report.

Have a great weekend,
Lova

—

[image.png]

Lova Andriarimalala

QGIS Full Stack Web Developer

Visit 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



___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] QGIS Full Stack Web Developer Report

[Lova Andriarimalala via QGIS-Developer]

Hello everyone,

Please find below the report summarizing the progress on the feed site 
development for this week.

PRs open:

  *   Add web page UI on the root URL

PR merged:

  *   Using rich editor for content, check data 
validity

Still working on:

  *   Some checks and fixes on the 
entirety

Have a great weekend,
Lova

—

[image.png]

Lova Andriarimalala

QGIS Full Stack Web Developer

Visit 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



From: Lova Andriarimalala 
Date: Friday, 27 October 2023 at 4:53 PM
To: qgis-developer@lists.osgeo.org 
Subject: Re: QGIS Full Stack Web Developer Report

Hello everyone,

I'm grateful for your warm welcome, and I'm truly thrilled to join this 
wonderful community.
Here is the report summarizing the progress on the feed site development for 
this week.
PRs open:

 *   Form submission management

PR merged:

 *   Feeds list page with filter and 
sorting
 *   Feed item form with preview
 *   Feed form review step
 *   Implement webpack and use it for Bulma 
CSS

Still working on:

 *   Improve feed item form: Check data 
validity

Have a great weekend,
Lova


—

[image.png]

Lova Andriarimalala

QGIS Full Stack Web Developer

Visit 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



From: Lova Andriarimalala 
Date: Friday, 20 October 2023 at 2:54 PM
To: qgis-developer@lists.osgeo.org 
Subject: QGIS Full Stack Web Developer Report

Hello everyone,

Currently, I am working on the website that administers the feeds displayed in 
the news area of QGIS. The website's repository is available on GitHub: 
https://github.com/qgis/qgis-feed

Please find below the report for the past two weeks.
PRs open:

 *   Feeds list page with filter and 
sorting
 *   Feed item form with preview
 *   Feed form review step

PR merged:

 *   Create a login page, add test cases, configure GH 
actions

Still working on:

 *   Use web pack for bulma CSS

Please do not hesitate to provide any feedback regarding the report structure 
or layout. Your suggestions are highly appreciated, as they will enable us to 
improve the report's quality and readability. Thank you for taking the time to 
review the report.

Have a great weekend,
Lova

—

[image.png]

Lova Andriarimalala

QGIS Full Stack Web Developer

Visit 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



___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] QGIS Full Stack Web Developer Report

[Lova Andriarimalala via QGIS-Developer]

Hello everyone,

I'm grateful for your warm welcome, and I'm truly thrilled to join this 
wonderful community.
Here is the report summarizing the progress on the feed site development for 
this week.
PRs open:

 *   Form submission management

PR merged:

 *   Feeds list page with filter and 
sorting
 *   Feed item form with preview
 *   Feed form review step
 *   Implement webpack and use it for Bulma 
CSS

Still working on:

 *   Improve feed item form: Check data 
validity

Have a great weekend,
Lova


—

[image.png]

Lova Andriarimalala

QGIS Full Stack Web Developer

Visit 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



From: Lova Andriarimalala 
Date: Friday, 20 October 2023 at 2:54 PM
To: qgis-developer@lists.osgeo.org 
Subject: QGIS Full Stack Web Developer Report

Hello everyone,

Currently, I am working on the website that administers the feeds displayed in 
the news area of QGIS. The website's repository is available on GitHub: 
https://github.com/qgis/qgis-feed

Please find below the report for the past two weeks.
PRs open:

 *   Feeds list page with filter and 
sorting
 *   Feed item form with preview
 *   Feed form review step

PR merged:

 *   Create a login page, add test cases, configure GH 
actions

Still working on:

 *   Use web pack for bulma CSS

Please do not hesitate to provide any feedback regarding the report structure 
or layout. Your suggestions are highly appreciated, as they will enable us to 
improve the report's quality and readability. Thank you for taking the time to 
review the report.

Have a great weekend,
Lova

—

[image.png]

Lova Andriarimalala

QGIS Full Stack Web Developer

Visit 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



___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer