Repository navigation
Bring the legal files in line with the Eclipse progress review checklist - #1995
Merged
Merged
Conversation
added 2 commits
October 5, 2026 10:25
- NOTICE and README use the project's formal name, LocationTech GeoWave, in the first mention and the trademark line, as other LocationTech projects do. - SECURITY.md follows the Eclipse Foundation template: the vulnerability reporting policy, the confidential report tracker as the first channel, and GitHub private vulnerability reporting as the second. - CONTRIBUTING.md points to the build instructions and to SECURITY.md. Co-authored-by: Rich Fecher <richard.fecher@vantor.com>
The dependency set is unchanged. Ten entries the IP team approved since the file was last generated now say so: six Accumulo 2.1.6 artifacts, hbase-annotations and hbase-testing-util 2.6.6, grpc-services 1.83.1 and protobuf-java-util 3.25.9. 787 of 805 entries are approved, and the other 18 all have open IPLab requests. Co-authored-by: Rich Fecher <richard.fecher@vantor.com>
rfecher
force-pushed
the
progress-review-docs
branch
from
October 5, 2026 14:36
63fd80e to
8579d10
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Docs only, for the 2026.10 progress review (EMO issue #1386), whose checklist covers these files.
NOTICEandREADME.md: use the formal name, LocationTech GeoWave, in the first mention and in the trademark line. This matches LocationTech Proj4J'sNOTICE; the old text said "Eclipse GeoWave".SECURITY.md: follows the Eclipse Foundation template. It now has:CONTRIBUTING.md: links the build instructions andSECURITY.md. The checklist recommends both.Before the GitHub link works: private vulnerability reporting is currently disabled on this repository (
GET /repos/locationtech/geowave/private-vulnerability-reportingreturnsenabled: false). It is enabled through Otterdog inlocationtech/.eclipsefdn(private_vulnerability_reporting_enabled).Please check: the "Supported Versions" section says security fixes happen on
master, the 3.x line. Adjust it if2.x-jdk8is meant to receive them too.DEPENDENCIES: regenerated with Dash. The dependency set is unchanged; ten entries the IP team has approved since then now say so. 787 of 805 are approved, and the other 18 all have open IPLab requests.