Extensions
Developer Experience
From the developer’s perspective, the Community Extensions repository performs the steps required for publishing extensions, including building the extensions for all relevant [platforms](#docs:dev:building:platforms), signing the extension binaries and serving them from the repository.  
For the [maintainer of `h3`](https://github.com/isaacbrodsky/), the publication process required performing the following steps:  
1. Sending a PR with a metadata file `description.yml` contains the description of the extension:  
```yaml
extension:
name: h3
description: Hierarchical hexagonal indexing for geospatial data
version: 1.0.0
language: C++
build: cmake
license: Apache-2.0
maintainers:
- isaacbrodsky

repo:
github: isaacbrodsky/h3-duckdb
ref: 3c8a5358e42ab8d11e0253c70f7cc7d37781b2ef
```  
2. The CI will build and test the extension. The checks performed by the CI are aligned with the [`extension-template` repository](https://github.com/duckdb/extension-template), so iterations can be done independently.  
3. Wait for approval from the DuckDB Community Extension repository’s maintainers and for the build process to complete.