-
Notifications
You must be signed in to change notification settings - Fork 2
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #123 from etf-validator/sg41-2
add minutes (41st SG meeting)
- Loading branch information
Showing
1 changed file
with
113 additions
and
0 deletions.
There are no files selected for viewing
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,113 @@ | ||
# ETF Steering Group (ETF SG) - 41st meeting | ||
|
||
## Logistics | ||
|
||
Location: Webex | ||
|
||
Date/Time: 11/03/2024, 11:00-11:45 CEST | ||
|
||
## Attendance | ||
|
||
- SG members: | ||
- JRC: Marco Minghini (main), Pierpaolo Cira | ||
- ii: Clemens Portele (main), Jon Herrmann | ||
|
||
## Minutes of previous meeting and open actions | ||
|
||
- [Minutes by JRC](https://github.com/etf-validator/governance/blob/master/Meetings/SG/20231113.md) were accepted and merged. | ||
|
||
There is one open task from the previous meeting: | ||
|
||
- [ ] ii to update the ToR. | ||
|
||
## Repositories | ||
|
||
The following responsibilities and changes to the ETF repositories were agreed. | ||
|
||
- General: | ||
- main branches are abandoned and should be deleted in all repos (unless there is no more up-to-date "next" or similar branch) | ||
- repositories exclusively for version 2.0.x are prefixed with „legacy-„ and are maintained by JRC | ||
- etf-webapp | ||
- ii manages repo | ||
- forks like https://github.com/guadaltel/etf-webapp/tree/ogc-api contain INSPIRE Validator specific code and can be maintained by JRC | ||
- there are no legacy branches; JRC can create a legacy branch and maintain it, if needed | ||
- etf-bsxds | ||
- as long as there are no changes it should remain archived | ||
- rename to legacy-etf-bsxds | ||
- JRC maintains repository | ||
- etf-webapp-docker | ||
- archived | ||
- etf-web-resources | ||
- ii manages repo | ||
- etf-validator.github.io | ||
- ii manages repo | ||
- etf-validator.net | ||
- ii manags repo | ||
- .github | ||
- ii manages repo | ||
- etf-unittest | ||
- ii manages repo | ||
- etf-spi | ||
- as long as there are no changes it should remain archived | ||
- rename to legacy-etf-spi | ||
- JRC maintains repository | ||
- etf-core | ||
- as long as there are no changes it should remain archived | ||
- rename to legacy-etf-core | ||
- JRC maintains repository | ||
- etf-bda | ||
- ii manages repo | ||
- JRC will create a branch ensuring legacy builds will work in the future | ||
- etf-stdtot | ||
- as long as there are no changes it should remain archived | ||
- rename to legacy-etf-stdtot | ||
- JRC maintains repository | ||
- etf-result-checker | ||
- ii manages repo | ||
- etf-client | ||
- ii manages repo | ||
- etf-sui-ae | ||
- as long as there are no changes it should be archived | ||
- rename to legacy-etf-sui-ae | ||
- JRC maintains repository | ||
- etf-suitd | ||
- rename to legacy-etf-suitd | ||
- JRC maintains repository | ||
- docs | ||
- ii manages repo | ||
- OSGEOLive-doc | ||
- JRC maintains repository | ||
- OSGEOLive-ETF | ||
- JRC maintains repository | ||
- etf-gmlgeox | ||
- rename to legacy-etf-gmlgeox | ||
- JRC maintains repository | ||
- etf-tetd | ||
- is currently not used by ii and no interest to maintain it for ETF v2.1 | ||
- rename to legacy-etf-tetd | ||
- JRC maintains repository | ||
- etf-bsxtd | ||
- ii manages repository | ||
- JRC can create branch and maintain it | ||
|
||
- [x] ii will rename the repositories | ||
- [x] ii will tag all repositories with their maintainer | ||
- [x] JRC will create "their" branches as needed and adjust | ||
|
||
ii still has to update the ToR (see action fromprevious meetings). | ||
|
||
Two approvers to pull requests are only needed in the governance repository. In all other repositories, the maintainer decides about changes. Significant changes to repositories should be documented through pull requests and issues. | ||
|
||
## Updates | ||
|
||
ii is working on a new Domain Specific Language for testing web services / APIs, but the language can also be used for data tests. A modular structure for tests will be supported. A first release is planned for the end of 2024. Test suites covering multiple test drivers will also be supported. | ||
|
||
JRC regularly releases new versions of the INSPIRE Validator. Updates include performance optimizations for monitoring / reporting, security vulnerability fixes, tests for data-service linking. | ||
|
||
The planned survey was not sent out. | ||
|
||
## Next meeting | ||
|
||
The next meeting will be on 8 July at 11:00. | ||
|
||
- [x] JRC to send the invite for the next meeting. |