Merge openstreetmap/id-tagging-schema and ideditor/schema-builder repos

[tordans]

This came up a few times in conversations, so lets track it as an issue:

I think we should merge the openstreetmap/id-tagging-schema and ideditor/schema-builder repos into one.

Why…

• Most documentation is in the schema-builder but all usage is here; this makes it hard to search for docs and understand the repo
• I will be a lot easier for new and recurring users to get into the schema when you can search in browse in one place
• I don't see any technical advantage into having separate repos

How…
Its quite simple technically speaking. I found those blog post a great help:

• https://developers.netlify.com/guides/migrating-git-from-multirepo-to-monorepo-without-losing-history/
• https://medium.com/@chris_72272/keeping-git-history-when-converting-multiple-repos-into-a-monorepo-97641744d928

[k-yle]

see also: ideditor/schema-builder#35

[matkoniecz]

Do we know why this repositories were split?

[1ec5]

name-suggestion-index also uses schema-builder. Not sure if combining it with id-tagging-schema would make anything harder – or easier.

[bhousel]

name-suggestion-index also uses schema-builder.

Are you sure? I don't think it does?

[1ec5]

Oh, my bad, it’s actually using id-tagging-schema to generate the presets. All good then. 😅

[tordans]

Another though: We could also use this opportunity to rename the repo to something less iD specific since many editors use the presets here (Rapid, GoMap, SC to some extend AFAIK, MapComplete to some extend AFAIK, …)

Maybe just "tagging-schema"? Or "editor-tagging-schema" to not be too presumptuous.

[matkoniecz]

I think it is fine to say "StreetComplete uses iD presets" (and yes, it does in several places - especially in shops and things overlays and for object descriptions).

Note that describing it as more general will encourage people to ask for changes improving things in say StreetComplete but breaking iD. Now such changes can be easily rejected (or are not asked in the first place)

Also, deprecations like this will create general confusion and will make this specific tagging schema harder to uniquely identify.