From 9eb562154969792e9c2f3cd47e1dbd3bb190eaf6 Mon Sep 17 00:00:00 2001 From: Nathan Day Date: Wed, 29 Oct 2025 07:50:55 +0000 Subject: [PATCH] Added Issue lifecycle guidance. --- Tagging-Merchants.md | 18 +++++++++++++++--- 1 file changed, 15 insertions(+), 3 deletions(-) diff --git a/Tagging-Merchants.md b/Tagging-Merchants.md index eaa64b6..34e354a 100644 --- a/Tagging-Merchants.md +++ b/Tagging-Merchants.md @@ -38,7 +38,7 @@ Add new locations or update existing ones directly as you see fit, or help with If you're a serious tagger, please consider joining the Shadowy Supertagger Team on Gitea so you can manage issues. We have a Supertagger [Discord](https://discord.gg/f88bzkDA4u) channel to get you on-boarded. -Please use the following guidance when editing locations: +Please use the following guidance when contributing: ### Physical Verification and Local Knowledge @@ -149,6 +149,18 @@ If an existing Node or Way exists, use whatever is already in place. If you are More information on element types can be found [here](https://wiki.openstreetmap.org/wiki/Elements). -## Completing Issues +## Gitea Issue Workflow -It is good practice to leave comments listing any additional steps you took to verify the accuracy of the data on the Issue. Before closing the Issue, please also paste the URL of the changeset on OSM. +If you want to contribute to tagging globally, you can request a BTC Map Gitea account [here](https://gitea.btcmap.org/user/sign_up) so that you can work on tagging Issues. + +If you are working on verifying an Issue with the `location-submission` label then please self-assign this so others know you are working on it. + +An Issue can have three states donated by the following labels: + +- `status/pending`: The submission is being verified. +- `status/added`: The submission has been verified and has been added to OSM. +- `status/rejected`: The submission could not be verified and was not added to OSM. + +It is good practice to leave comments listing any additional steps you took to verify the accuracy of the data on the Issue or reasons for rejection. + + Before closing the Issue, please also paste the URL of the OSM changeset in the comments.