Docs: Extended guidelines for presets, fields, deprecations #1229
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This is heavily inspired by https://github.com/streetcomplete/StreetComplete/blob/master/QUEST_GUIDELINES.md – thanks a lot
tordans
changed the title
tordans
changed the title
|
🍱 You can preview the tagging presets of this pull request here. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
@tyrasd following our conversation on the last iD community call I created this draft of a separate document that outlines the decisions that guide adding presets, fields and so on.
I suggest we collect some feedback but the start using it which will be the best way to improve it over time.
This is heavily inspired by https://github.com/streetcomplete/StreetComplete/blob/master/QUEST_GUIDELINES.md – thanks a lot