Apologize for the delayed response and assure you that these are addressed on high priority.
Following our review of the changeset, we can confirm our edits accurately reflect the actual ground conditions. The gate is clearly visible in Bing Streetview, and as per OpenStreetMap documentation access=private, we appropriately tagged this gated community as 'access:private'. While we currently don't use the tag combination 'access:destination+ownership:private', however if you can provide more context or references for the use of these tags it would help us to look the feasibility to incorporate in our SOPs.

Thank you for reverting the changes. Apologies for the delayed response and assure you that these are addressed on high priority.
Upon reviewing the changeset, we identified that while creating the Carriage Way, the mapper omitted several necessary corresponding tags that should have been added at the same time. We have communicated this feedback to the mapper and will ensure all future edits strictly comply with OSM community platform guidelines.

Thanks for reverting the edits. Apologies for the delay in the response and will ensure that these are addressed on priority.
We have looked into the changeset and could identify that the mapper has missed on adding the traffic signals and crossing tags while creating the Carriage Way on this segment and she accidently moved the "Cafe" point from one location to another, hence this was a manual miss. We have shared the feedback with the mapper and will ensure that the future edits are inline with the guidelines from OSM community platform.

Thanks for reverting the edits. Apologies for the delay in the response and will ensure that these are addressed on priority.
We have looked into the changeset and could identify that the mapper has incorrectly added direction due to ambiguity based on the lane marking which can be seen on satellite imagery. However, that lane marking does not indicate one way, hence the edit done was incorrect,. We have reverted the edit and can be referred in this changeset: 162206660. We have shared the feedback with the mapper and will ensure that the future edits are inline with the guidelines from OSM community platform.

Thanks for reverting the edits. Apologies for the delay in the response and will ensure that these are addressed on priority.
We have looked into the changeset and could identify that the mapper has incorrectly added direction due to ambiguity based on the lane marking which can be seen on satellite imagery. However, that lane marking does not indicate it as one way, hence the edit done was incorrect. We have reverted the edit and can be referred in this changeset: 162206421. We have shared the feedback with the mapper and will ensure that the future edits are inline with the guidelines from OSM community platform.

Thanks for reverting the edits. Aplogies for the delay in the response and will ensure that these are addressed on priority.
We have looked into the changeset and could identify that the mapper has missed on adding the traffic signals while creating the Carriage Way on this segment.

To address the second part of the query, the Amazon OSM wiki page currently has the outdated list of editors and reviewers, due to the restriction of updating the lists it wasn't addressed in the past and put on hold. The team will rework on the issue and update the Amazon users list by 03/31.

Thank you for the quick response. To ensure that there is no further delay in acknowledging the feedback shared by you, I have responded on behalf of the mapper as she is on timeoff for the day. As correctly said by you, while we have access to the driver feedbacks, we proritize editing in accordance to the guidelines shared on OSM community platform. In this changeset, based on deep dive, we have observed that this is a miss made by the mapper due to knowledge gap as she is newly onboarded on these specific set of edits related to Carriage way. Going forward, we will ensure all our mappers are contributing to OSM only when they have evidences supporting their edit based on the resources available on OSM.

Once the mapper is back, we will have her respond and acknowledge to your feedback.

Aplogies for the delay in the response and will ensure that these are addressed on priority.
We have looked into the changeset and the edit done was true to ground reality https://www.bing.com/maps?cp=51.507183%7E-0.137638&lvl=17.0&v=2&sV=1&pi=-14.3&style=x&dir=276.6, and this is alternative way of tagging directions which is not used very often oneway=-1 hence we have revised the syntax but retained the edit.
Thanks!

Thanks for reverting the edits. Aplogies for the delay in the response and will ensure that these are addressed on priority.
We have looked into the changeset and could identify that the mapper has missed on modifying the traffic signal while creating the Carriage Way on this segment. The mapper was onboarded on 2023 onto OSM platform, however recently starting working on OSM. From ourside, we have sensitized the feedback with the mapper and will ensure the mapper will not be doing any further edit on OSM until the mapper is fully trained in the region and rules. We will ensure that these kind of incorrect edits is not done in future.