Skip to content

[CHORE] Add maintainers, keywords, and URLs to pyproject#454

Draft
John McCall (lowlydba) wants to merge 1 commit intodevfrom
lowlydba-258-add-pypi-meta
Draft

[CHORE] Add maintainers, keywords, and URLs to pyproject#454
John McCall (lowlydba) wants to merge 1 commit intodevfrom
lowlydba-258-add-pypi-meta

Conversation

@lowlydba
Copy link

This pull request standardizes and improves the project metadata across all Python package modules in the repository.

The main changes are:

  • addition of maintainer information
  • relevant keywords
  • project URLs

These changes collectively make the packages more maintainable and user-friendly for both contributors and end users.

Partially resolves https://github.com/OvertureMaps/ops-team/issues/258

Update multiple packages' pyproject.toml files to add a maintainers list, common keywords, and a [project.urls] section (Homepage, Source, Issues). Affects core, system, cli, annex, and all theme packages under packages/overture-schema-*. This centralizes package metadata to improve discoverability, attribution, and tooling integration.
@lowlydba
Copy link
Author

Victor Schappert (@vcschapp) , Seth Fitzsimmons (@mojodna) - I didn't see an email on your GH profiles, so left that out, but happy to include it if you'd like to.

@lowlydba John McCall (lowlydba) added the automation 🦾 Change/enhance automation of a process label Feb 27, 2026
Copy link

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Standardizes Python package metadata across the packages/* workspace modules to improve PyPI/project discoverability and maintenance (maintainers, keywords, and project URLs).

Changes:

  • Added maintainers metadata across package pyproject.toml files.
  • Added keywords metadata across package pyproject.toml files.
  • Added [project.urls] (Homepage/Source/Issues) to most package pyproject.toml files.

Reviewed changes

Copilot reviewed 11 out of 11 changed files in this pull request and generated 2 comments.

Show a summary per file
File Description
packages/overture-schema/pyproject.toml Adds maintainers/keywords for the umbrella package (note: URLs not added here in this PR).
packages/overture-schema-transportation-theme/pyproject.toml Adds maintainers/keywords and [project.urls].
packages/overture-schema-system/pyproject.toml Adds maintainers/keywords and [project.urls].
packages/overture-schema-places-theme/pyproject.toml Adds maintainers/keywords and [project.urls].
packages/overture-schema-divisions-theme/pyproject.toml Adds maintainers/keywords and [project.urls].
packages/overture-schema-core/pyproject.toml Adds maintainers/keywords and [project.urls].
packages/overture-schema-cli/pyproject.toml Adds maintainers/keywords (incl. cli) and [project.urls].
packages/overture-schema-buildings-theme/pyproject.toml Adds maintainers/keywords and [project.urls].
packages/overture-schema-base-theme/pyproject.toml Adds maintainers/keywords and [project.urls].
packages/overture-schema-annex/pyproject.toml Adds maintainers/keywords and [project.urls] (placed after [tool.uv.sources]).
packages/overture-schema-addresses-theme/pyproject.toml Adds maintainers/keywords and [project.urls].

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@lowlydba John McCall (lowlydba) added change type - cosmetic 🌹 Cosmetic change and removed automation 🦾 Change/enhance automation of a process labels Feb 27, 2026
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is there a way we could define a maintainers.yml or something and reuse it?

Or generally put a generic "Overture" as the maintainer? I'm not sure who the right maintainer is here.

{name = "Vic Schappert"},
{name = "Jennings Anderson", email = "jenningsa@meta.com"},
]
keywords = ["schema", "pydantic", "overture", "geospatial", "validation"]
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There's a chance we're going to use this field for extension discovery (still being debated), so I'd rather omit this (for PyPI purposes).

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No problem, will get those removed

Comment on lines +2 to +7
maintainers = [
{name = "Dana Bauer", email = "dana@overturemaps.org"},
{name = "Seth Fitzsimmons"},
{name = "Vic Schappert"},
{name = "Jennings Anderson", email = "jenningsa@meta.com"},
]
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1 to Jennings Anderson (@jenningsanderson)

I'm unclear who the right maintainers are for this project. It's the Schema WG more broadly.

@lowlydba
Copy link
Author

Is there a way we could define a maintainers.yml or something and reuse it?

Or generally put a generic "Overture" as the maintainer? I'm not sure who the right maintainer is here.

Yeah, generic Overture is totally fine - no pressure for anyone.

@lowlydba John McCall (lowlydba) marked this pull request as draft February 27, 2026 22:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants