Clerk-Fetchers
This repository lets the community contribute additional fetchers for municipal government meeting minutes and agendas to extend Clerk. Check out the Contributor Guide and included example to get started!
Description
A community-contributed repository that extends Clerk with fetchers for non-standard municipal government meeting minutes and agendas. Each fetcher targets a specific municipality, scraping meeting listings and downloading associated PDFs.
Anyone can add new fetchers following the included example and Contributor Guide.
These fetchers, if accepted, will feed PDFs into CivicBand's pipeline. Data will be available for search approximately 24 business hours after the first successful fetcher run.
Getting Started
Dependencies
- Python 3.12+
- UV package manager
- clerk >= 0.0.1
- Dev dependencies:
pytest>=7.4.0,respx>=0.23.0,hatchlingbuild system
Developer Setup
See Adding a fetcher to clerk-fetchers in the Contributor Guide for full setup instructions. At a high level:
- Fork this repo and create a feature branch
- Add your fetcher under
src/clerk_fetchers/fetchers/<municipality_name>/ - Register it in
src/clerk_fetchers/_registry.py - Write tests in
tests/fetchers/<municipality_name>/ - Open a PR — CI will run the full test suite
Testing
Run pytest locally to check your fetcher before submitting. CI also runs the full test suite automatically once you open a PR.
After Submission
One of the maintainers will review your PR at our earliest convenience. We might have follow-up questions, which we'll post either as a comment on the PR (for overall/general feedback) or using the GitHub reviews workflow (for line-specific feedback). If we don't get a response to questions about your PR within a month, we'll close the PR to avoid stale PR buildup. You should feel free to reopen it when you come back, though!
Help
Open a GitHub issue to report bugs or request help with a fetcher you're trying to add. To reach the maintainers privately, email Philip at hello@civic.band.
License
This project is licensed under the BSD 3-Clause License - see the LICENSE file for details.
Metadata
Release files for clerk-fetchers 0.0.6
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| clerk_fetchers-0.0.6.tar.gz | 126.4 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| clerk_fetchers-0.0.6-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 143.6 kB
Release files / clerk_fetchers-0.0.6.tar.gz
| Download URL | clerk_fetchers-0.0.6.tar.gz |
|---|---|
| Size | 126.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0b503c7b77cf487fe9e739a8dc25e013fe7be7d9bf4b16c4af31c9ab82bfe609
|
|
BLAKE2b-256 checksum How to use checksums |
477dfd74583df223573313e498a5721343c122582c3bc64284d4cad1d84a9f28
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 21, 2026.
Transparency logRelease files / clerk_fetchers-0.0.6-py3-none-any.whl
| Download URL | clerk_fetchers-0.0.6-py3-none-any.whl |
|---|---|
| Size | 17.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9accb5f244712629d040895c4424b189e9853e96ed91d8992334e430cd2e58c2
|
|
BLAKE2b-256 checksum How to use checksums |
f119666768aa1d4c206c8dde54225913d85835ca5a1b694a395a099707737d26
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 21, 2026.
Transparency logSecurity for clerk-fetchers 0.0.6
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for clerk_fetchers-0.0.6.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 21, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
