Grant programme 2024 #60
Comments
|
Proposal information for voters: Authentication System: allow Database (initially Postgres) storage for authentication DBby @elpaso | €8,500.00 | qgis/QGIS-Enhancement-Proposals#248 This proposal aims to abstract out the actual storage of the encrypted credentials allowing to optionally use a client/server DB as the authentication DB, Postgres being the primary target. The main goal is to be able to use a client/server authentication DB in QGIS Server. The discussion touched on other options like LDAP and services like Bitwarden or LastPass. Overall the discussion showed wide agreement. Use pre-commit to automate installation and management of all pre-commit hooksby @elpaso | €5,500.00 | qgis/QGIS-Enhancement-Proposals#265 This proposal aims to switch to https://pre-commit.com/ to manage our pre-commit hooks. This framework provides automated installation and configuration of the hooks, it has also a set of pre-defined hooks ready to use. The discussion showed wide agreement. Update older annotation items to new frameworkby @nyalldawson | €8,000.00 | qgis/QGIS-Enhancement-Proposals#269 This proposal aims to move the old annotation types "text" and "svg" over to the newer framework, in order to provide a more consistent and user friendly interface to QGIS users. No issues were raised during the discussion. PyQGIS linter warningsby @troopa81 | €5,200.00 | qgis/QGIS-Enhancement-Proposals#287 This proposal aims to smooth plugins migrations from QGIS 3 to QGIS 4 (with Qt 6 support) by providing a static linter able to detect QGIS deprecated classes and methods, Qt 5 deprecated classes and methods, and to actively inform plugin owners on plugins.qgis.org with current warnings. No issues were raised during the discussion. Authentication system revision (v1.1)by @nyalldawson | €1,500.00 | qgis/QGIS-Enhancement-Proposals#289 This proposal aims to perform the necessary deeper research for revising the authentication system (as discussed in #278) The discussion suggested to also consider the related proposal qgis/QGIS-Enhancement-Proposals#248. Clean up point cloud index and improve its thread safetyby @wonder-sk | €3,000.00 | qgis/QGIS-Enhancement-Proposals#290 This proposal aims to improve QgsPointCloudIndex and its derived classes to make sure that the code is robust and maintainable in the future. This includes thread safety, better interface to fetch hierarchies and less code duplication. No issues were raised during the discussion. Mitigate Abusive Tile Fetching on OpenStreetMap (OSM)by @nirvn | €3,300.00 | qgis/QGIS-Enhancement-Proposals#291 This proposal aims to enhance QGIS's handling of tile fetching on the OpenStreetMap (OSM) servers to mitigate abusive tile fetching practices. The key objective is to prevent excessive strain on OSM servers by implementing measures to reduce fetching of tiles during ‘normal’ usage of the OSM tile server as well as discourage mass downloading of tiles through QGIS desktop. *The discussion revolved around potential optimization options and whether OSM could still do something server-side to reduce the load on their serevers. * Implementing CI Qt6 Windows Builds through vcpkgby @m-kuhn | €14,000.00 | qgis/QGIS-Enhancement-Proposals#292 This proposal aims to establish a CI build process for QGIS on Windows using Qt6 and vcpkg to cover Windows platforms, where most QGIS users are coming from. This approach not only facilitates the identification of MSVC-specific issues at an earlier stage but also simplifies the maintenance of OSGeo4W. The discussion touched on how this could help with the setup of a working development environment on Windows for the purpose of developing and debugging. Fix access to remote data sources in WebAssembly buildsby @wonder-sk | €4,000.00 | qgis/QGIS-Enhancement-Proposals#294 This proposal aims to fix WebAssembly (WASM) builds of QGIS to enable the use of projects with COG, vector and XYZ raster tiles, and WMS or WMST (which currently fail to load). The discussion discussed the question if WASM builds are (going to be) a core part of the QGIS ecosystem, like QGIS Desktop, Server, Web Client, ... Embedded end-user feedbackby @Guts | €6,500.00 | qgis/QGIS-Enhancement-Proposals#295 This proposal aims to integrate a feedback form/widgets as a QGIS in-app tool in order to improve the way we gather end-user feedback, particularly for non-English-speaking users who may be hindered by the English-only Github interface. The discussion focused on how sustainable this would be due to the dependency on the Github API and the already existing difficulties of triaging tickets. |
|
Dear devs, please have a look at the mini summaries of your proposals above and let me know if any need to be changed. cc @Guts @wonder-sk @m-kuhn @nirvn @nyalldawson @troopa81 @elpaso |
|
This is perfect, thanks @anitagraser |
|
Thanks for summarizing this, @anitagraser LGTM |
|
LGTM thank you. |
|
Thanks Anita, looks good to me too! |
|
All good, thanks!
…On Wed, Apr 10, 2024, 04:00 Nyall Dawson ***@***.***> wrote:
Thanks Anita, looks good to me too!
—
Reply to this email directly, view it on GitHub
<#60 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AANGBENPJU6BP344JDQFFI3Y4RJHBAVCNFSM6AAAAABDG3T6LWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANBWGAZTQOBQGM>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
Looks good, thanks! |
|
Thanks @anitagraser, okay for me. |
Process description:
https://docs.google.com/document/d/1CNmSJxztrHrqLfillDH8v1zWaMzxFUyYSPT3sut55eQ/edit?usp=sharing
2024-02-15: Call for proposals (4 weeks)
2024-03-23: QEP discussion period (2 weeks)
2024-04-06: Writing discussion summaries (1 week)
2024-04-13: Voting starts (2 weeks)
2024-04-27: Publication of results
--- 6 months of project work ---
2024-10-27: Deadline for follow-up reports
The text was updated successfully, but these errors were encountered: