Onboarding repository gazetteer

[birkskyum]

WIP

https://github.com/birkskyum/gazetteer moved to https://github.com/maplibre/gazetteer

Motivation

We currently rely on an abandoned mapbox library, with no way to maintain it: https://github.com/mapbox/gazetteer

Acceptance

• Any two board members must agree to accept a new repository.
  Approved by: <@user1> <@user2>

Licensing

• BSD-2, so smilar to MIT - The repo license is BSD-3 or MIT.
  Repos may allow dual-licensing under other open source licenses, e.g. MIT OR Apache.
• No, because none of our libraries have this - The repo contains Copyright (c) <year> MapLibre contributors in license file(s) and in the readme.

Special files

• /README.md
  Description, link to the main maplibre.org page, name of the OSM-US Slack channel for discussions and an invite link, etc
• /LICENSE
  Dual-licensed repos may have additional files like LICENSE-MIT and LICENSE-APACHE
• /CONTRIBUTING.md
• The repo has Pull Request and Issue Templates in /.github dir.
• The repo has /.github/FUNDING.yml file copied from maplibre-gl-js/funding
• /CODE_OF_CONDUCT.md
  This file should only link to our primary code of conduct. Use this markup for consistency:
  # Contributor Covenant
[![Contributor Covenant](https://img.shields.io/badge/Contributor%20Covenant-2.1-4baaaa.svg)](https://github.com/maplibre/maplibre/blob/main/CODE_OF_CONDUCT.md)

Repo Settings

General page

• [Features] Disable unused features like wiki.
• [Features] Enable Sponsorships checkbox (see also FUNDING.yaml above).
• [Features] Enable Preserve this repository.
• [Pull Requests] Community is encouraged to use squash merge. Disable other merge types if possible.
• [Pull Requests] Enable Automatically delete head branches.

Access

• The repo has at least one admin who is ideally not part of the Governing Board: <@user>

Branches

• The primary branch is named main.
• Set up branch rules to require CI pass and an approval before merge.
  For smaller projects it might be OK to ignore this rule.

Miscelaneous

• The repo must not have any personal branches.
  All work should be done on forks and submitted via PRs, including by the admins.
• Repo has a proper GitHub description and an optional web site
  Use the gear icon in the upper right corner of the repo page.
• CI automatically runs on all pull requests before merging using GitHub actions
• Grant admin rights to the board members and automation accounts for packages
  • npmjs.com: package settings / invite: maplibreorg nyurik klokan lseelenbinder wipfli
  • crates.io: package settings / add owner: nyurik klokan lseelenbinder wipfli

Community

• The new repo has been announced in the #maplibre OSMUS slack channel.
• The new repo has been announced in the next monthly meeting of the Technical Steering Committee.
• The new repo has been announced in the @maplibre twitter.

[wipfli]

@birkskyum what is the status on gazetteer?

[birkskyum]

It stalled a bit - didn't know if there was interest in proceeding.