Add Pending Places

Pending-Places.md

@@ -0,0 +1,21 @@
+# Adding Pending Places
+
+Pending Places can be submitted to BTC Map via our [Submit Place APIs](https://github.com/teambtcmap/btcmap-api/blob/master/docs/rpc/import/README.md). This enables 3rd parties (e.g. Sqaure, Blink, etc.) to submit Pending Places for consideration to add to BTC Map / OpenStreetMap.
+
+When submitted via the API, these Pending Places are stored in our DB with a separate lifecycle to regular Places/Merchants. Once a Pending Place is created, an Issue is also created in Gitea with the usual `location-submission` label and, additionally the `import/<origin>` label denoting the source of the Pending Place.
+
+These Issues should be processed by our Shadowy Supertaggers as usual, but depending on the origin/source can be treated as trusted. Trusted sources do not require direct verification with the merchant, be we should of course check location details and existing OSM elements as usual.
+
+The following are trusted sources:
+
+- Square (label `import/square` [Issue query here](https://gitea.btcmap.org/teambtcmap/btcmap-data/issues?q=square&type=all&state=open&labels=1307))
+
+The API monitors the status of Gitea issues and will change the status of the Pending Place accordingly when the Issue is closed.
+
+# Revoking Places
+
+Sources can also revoke Places.
+
+If the Gitea Issue is still open, it will be closed. If it has already been processed (and likely added to OSM) then a new Issue will be created with the `location-removal` label.
+
+Care should be taken when processing the removal as it may just be a Place/Merchant changing the way they accept Bitcoin. e.g. If they close their Square account and begin accepting bitcoin via a different method, we would create a `location-removal` Issue. Also, this may not mean the whole element needs to be removed on OSM, as they may just have ceased accepting bitcoin.