-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Grant programme 2023 #58
Comments
@3nids would you be willing to compile the QEP discussions this year again? |
Proposal information for voters: QGIS Bug Tracker cleanupby @gioman | €6,000.00 | qgis/QGIS-Enhancement-Proposals#266 This proposal aims to do a big cleanup of the bug tracker, including: closing all bug reports created prior QGIS 3.0, going through all remaining bug reports and ensuring that: it is a valid issue, has a proper title/description etc., evaluating all feature requests. The discussion suggested further useful labels and cautioned with regards to language used so to not alienate users who file tickets Switch to clang-format for C++ code and implement pre-commit hooksby @elpaso | €5,000.00 | qgis/QGIS-Enhancement-Proposals#264 and qgis/QGIS-Enhancement-Proposals#265 This proposal would move all C++ code from astyle (Artistic Style) to the more powerful and modern clang-format which is much more usable in practice since it understands more of the syntax of C++. The discussion showed wide agreement and raised the point that all active branches will have to be reformatted. Add vertical CRS handling to QGISby @nyalldawson | €20,000.00 | qgis/QGIS-Enhancement-Proposals#267 This proposal aims to resolve the current lack of vertical CRS handling (for legacy reasons, QGIS actively removes all vertical CRS information from datasets). The proposed solution relies on the PROJ library's support for vertical CRS and the PROJ CRS database as much as possible. The discussion focused on how to expose the new functionality to users, including the need for docs of this fundamental change which can be tricky for users to understand. Improve test result handling on QGIS CIby @nyalldawson | €1,000.00 | qgis/QGIS-Enhancement-Proposals#268 This proposal aims to simplify the workflow when a rendering test fails, by automatically adding a descriptive message and rendered images for debugging to the PR instead of having to dive into tons of logs and manually download zip files full of images. The proposer notes that this is a high-risk project but the discussion was optimistic. Update older annotation items to new frameworkby @nyalldawson | €8,000.00 | qgis/QGIS-Enhancement-Proposals#269 This proposal concerns moving some of the older annotation types (specifically "text" and "svg") over to the new framework (introduced in version 3.16), in order to provide a more consistent and user friendly interface to QGIS users. There were no issues raised in the discussion. QGIS Project Loading Performanceby @m-kuhn | €16,500.00 | qgis/QGIS-Enhancement-Proposals#261 This proposal aims to improve project loading performance by managing cachable metadata of QgsDataProvider. This includes control over cache invalidation, populating the cache explicitly from a different location than the provider itself, populating the cache later than at layer init time (lazy load), and collection of cache contents in a thread. The discussion touched on related parallel developments towards parallel loading of projects: qgis/QGIS-Enhancement-Proposals#261 (comment) Conda Installer for macOSby @m-kuhn | €12,100.00 | qgis/QGIS-Enhancement-Proposals#270 This proposal aims to build an installer for macOS (including M1) on top of conda to replace the old existing installer which suffers from outdated dependencies and high maintenance requirements. No issues were raised during the discussion phase. Unify the geometric and topological verification and correction features in QGISby @Koyaani & @lbartoletti | €25,000.00 | qgis/QGIS-Enhancement-Proposals#236 This proposal aims to unify the exiting multiple geometric and topological verification and correction features, including geometrical verifications in the corresponding geometric classes, a set of classes for topological verifications, and a dedicated class for the topological and geometric errors. The issue of potential further fragmentation of the code base was raised. Porting to C++ and harmonization of Processing algorithmsby @wonder-sk & @alexbruy | €10,000.00 | qgis/QGIS-Enhancement-Proposals#271 This proposal aims to continue the efforts of porting more QGIS algorithms from Python to C++ (including Voronoi polygons and Delanuay triangulation, Concave Hull, Generate XYZ Tiles, Raster Calculator, and Align Rasters) mainly to improve the robustness, code quality and speed. The discussion touched on specific hurdles that may complicate porting certain algorithms. |
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 @gioman @elpaso @nyalldawson @m-kuhn @Koyaani @lbartoletti @wonder-sk @alexbruy |
Looks good to me @anitagraser . Thanks a lot for this work |
@anitagraser LGTM, thank you for the summary! |
@anitagraser looks good to me, thank you also from my side! |
LGTM @anitagraser many thanks |
@anitagraser all fine for me too! |
@m-kuhn To avoid any doubt, please add a note to the QEP that indicates the deviations between the submitted proposal and the (potentially larger) full extent of the QEP. As in previous years, the voting members make their decisions based on the short summaries and the QEPs. |
Just to thank about this selection and transparent work. |
@anitagraser many thanks for the summary! |
Thanks again @anitagraser for your sterling work! |
Process description:
https://docs.google.com/document/d/1CNmSJxztrHrqLfillDH8v1zWaMzxFUyYSPT3sut55eQ/edit?usp=sharing
2023-04-04: Call for proposals (4 weeks)
2023-05-02: QEP discussion period (2 weeks)
2023-05-16: Writing discussion summaries (1 week)
2023-05-232023-05-30: Voting starts (2 weeks)2023-06-062023-06-26: Publication of results--- 6 months of project work ---
2023-12-062023-12-26: Deadline for follow-up reportsRound 1:
Round 2:
The text was updated successfully, but these errors were encountered: