Attending
-
Torben Barsballe
-
Nuno Oliveira
-
Alessandro Ricchiuti
-
Kevin Smith
-
Andrea Aime
-
Pierre Mauduit
-
Peter Smythe
-
Jody Garnett
Actions from prior meetings:
- Jody: Proposal to adopt maven standard (..-) in GeoTools and GeoWebCache so projects are aligned.
- Nuno: Proposal to amend release process
- AA: Amend GSIP 241 to add a warning when a custom RAM is used and disk quota is not enabled
Actions
-
Andrea: Adjust communications guidelines in AI policy GSIP to be more target about how these should/shouldn’t be written
-
Jody: Follow up on geotools#5741
AI policy GSIP
https://github.com/geoserver/geoserver/wiki/GSIP-242
Summary:
-
Permits use of AI tools for coding and project assistance.
-
For code, a contributor is fully responsible for code they submit, in particular its correctness and maintainability.
-
Wholly AI Generated text is forbidden. Do use such content in discussion, issue reports, and pull request descriptions etc.
Discussion:
-
Add a checkbox to CONTRIBUTING.md saying “I have read the AI policy”
-
How do we determine AI generated content?
- Wholly AI generated content is pretty obvious (at least for now)
-
Submitter should be responsible for comprehending the output of their tooling and not the other party.
-
Action: Reword communication guidelines slightly to be more targeted.
Clarification on GeoTools property accessors and filter functions
GEOT-7928 - https://github.com/geotools/geotools/pull/5741
A number of filter functions target Features specifically instead of any object
An argument has been raised that these functions are broken according GeoTools guidelines
However, there is no clear guidance one way or another in existing GeoTools design & javadocs, this seems to be more unofficial project convention rather than strict guidelines
Action: Jody will follow up on PR
Chit chat
Upcoming Releases
-
Scheduled release window for GeoServer 2.28.5 coming up soon
-
Do we want to do a 3.0.1 for September as scheduled or delay? Users are still migrating to 3.0.0, a point release in September could feel like its too soon.
-
Suggestion: delay to October
-
This would also give us more time for development.
-
JIRA to Github transfer tool
-
The size of our issue archive coupled with platform rate-limits makes this a challenge
- Takes about a day to migrate one project
-
Labels migrated to tags
-
Authors preserved in comments, the actual author will be bot
-
Discussion around comment attribution, user deletion, and GDPR
-
In order to keep us in the clear, use only github handles, and only for users who agree to be referenced. This will be a semi-manual process
-
-
Attachments are included
-
Links between projects should be able to be maintained