GEOME Governance & Requests

This repository is the front door for proposing, discussing, approving, and tracking changes related to GEOME overall:

• Vocbulary changes, including entity/schema updates (new fields, relationships, validation rules)
• UI/UX and backend/API change requests
• Governance & process decisions (e.g., steering committee formation)

Implementation does not happen here. Once approved, work is routed to the relevant repositories (e.g., geome-db, geome-ui, geome-configurations, docs repos).

How to request changes

Open a GitHub issue and choose the correct template:

• Vocbulary Change Request
• Functionality Change Request
• Governance / process

Maintainers will triage with labels: type:*, scope:*, team:*, and repo:*.

Typical lifecycle

1. Issue opened (template)
2. Triage: label scope:team (Team request) or scope:geome-wide (Network request) + add team:<slug> and repo:*
3. For Network requests (scope:geome-wide): record a decision in /decisions/ linked to the issue
4. Create implementation issues in the target repo(s) and link back
5. Close the governance issue when implemented + documented

Repo contents

• /registry/ — optional registries (controlled vocabularies, entity proposals)
• /decisions/ — decision records (ADR-style)
• /.github/ISSUE_TEMPLATE/ — issue forms to standardize requests