Thanks for the input.
As stated previously, I am not actively tagging anything new. With this challenge, I am just converting data that is already there. I am not adding parking:*=yes to anything where data implicating that fact wasn't available previously

Hey, I've noticed a lot of parking:lane:left=no in this area added by you. How come?

I will try to make some clarifying statements to avoid confusion.

- This challenge only converts existing data into the new scheme.
- parking:<side> does not state anything about if parking is allowed
- The challenge uses the generic yes only if there is incomplete data to begin with
- The generic yes should be avoided and a more specific tag should be used if the mapper has the knowledge
- Tagging that parking is not forbidden (parking:<side>:restriction=none) is indeed not needed if there is parking
- e.g. StreetComplete marks the physical availability of parking as something that indeed all residential roads should have

If you think this challenge does something systematically wrong, I would encourage you to join the discussion in the forum [1] or open an issue on the GitHub [2]

If you think StreetComplete should not be marking every residential road as missing physical parking data, I would encourage you to open an issue in the GitHub [3] so that e.g. Australia could be excluded.

[1] https://community.openstreetmap.org/t/organized-mapping-maproulette-challenge-convert-old-street-parking-tags-to-new-scheme/129253/8
[2] https://github.com/wielandb/maproulette-tagfixes/tree/main/challenges/parking_converter
[3] https://github.com/streetcomplete/StreetComplete/issues

But now there is no parking:left tag which is not good i think.
Some value should exist for parking:left if there is a value for parking:left:restriction:conditional.