Managing a Map Fix

Introduction

In the past, fixing maps would be used via the map fixing hub, which was generally untraceable and only made of notice when investigated. Now, tracking map states have been simplified by using Issues and Pull Requests to track progress and directly make an update to the main branch.

Beginner Resources

If you are not familiar with Git or GitHub, we recommend going through a quick overview at the following links:

• lab.github.com/githubtraining/introduction-to-github
• lab.github.com/githubtraining/communicating-using-markdown
• docs.github.com/en/get-started/quickstart/communicating-on-github

Starting a Map Fix

Maintainers and users can create tracking issues for map fixes, it is optional, since some map fixes can be fixed in a minute, but as long as the publishing commit is detailed, nothing matters all too much. (If you're going to make an issue, you might as well continue the tidiness.)

Using and Specifying Issues/Pull Requests with Labels

These issues can be labeled to have specific identifiers that can show what kind of issue this is and in what state.

label	description
duplicate	This has already been reported/resolved.
in-progress	This is currently being fixed, reviewed, and/or worked on.
question	Further information is requested.
report	Map bug report.
reported	Reposted to issues site.
won't fix	This will not be worked on.

Maintainers can also cross reference issues by simply linking them together to unify those issues to combine as a simple topic, for example, 4 issues stating map bugs for map X, maintainers can create a single issue to track all map X bugs and link them together.